> ## Documentation Index
> Fetch the complete documentation index at: https://docs.eftsureinsided365fo.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Frequently Asked Questions — Eftsure inside D365 FO

> Answers to the most common questions about deploying, configuring, and using Eftsure inside Dynamics 365 Finance & Operations (D365 FO).

Eftsure inside Dynamics 365 Finance & Operations is an ISV module that brings payment fraud prevention and vendor management directly into your D365 environment. The questions below cover the most common topics raised during implementation, day-to-day use, and administration — from deployment timelines through to licensing.

## General

<AccordionGroup>
  <Accordion title="How long does a typical deployment project last?">
    For existing D365 or Eftsure customers moving to Eftsure inside D365 FO, the typical implementation takes approximately **6–10 weeks**. This covers deployment, training, user acceptance testing (UAT), go-live, and hypercare.

    For new D365 implementations, the project follows the plan set by the customer and their implementation partner. Timelines typically range from **6–18 months** depending on your organisation's business requirements.
  </Accordion>

  <Accordion title="Which D365 features do you support?">
    Eftsure inside D365 FO supports all native D365 Finance & Operations features in all configurations, including:

    * Multi-company (multiple legal entities)
    * Multi-currency
    * Multi-language
    * Multiple bank accounts per vendor
    * Cross Company Data Sharing (CCDS) and copy vendor to another legal entity
    * **Vendor collaboration** — the standard D365 feature that lets your vendors maintain their own vendor card directly in D365

    Eftsure is committed to supporting all future Accounts Payable features released by Microsoft. See the [Feature support table](#feature-support) below for the full list of supported and unsupported capabilities.
  </Accordion>

  <Accordion title="How does Eftsure synchronise with D365?">
    Most actions happen in **real time** with no visible performance impact. Other actions use the standard D365 batch framework to synchronise data between Eftsure and D365. All communication between the two systems is invisible to end users.
  </Accordion>

  <Accordion title="How is Eftsure inside D365 deployed?">
    Eftsure is a cloud-based, ERP- and bank-agnostic platform. The Eftsure inside D365 FO extension is available on the [Microsoft Business Marketplace (AppSource)](https://appsource.microsoft.com/en-us/product/dynamics-365-for-finance-and-operations/pnew.eftsureinsided365fo). Deployment into your environment follows the same lifecycle as any other D365 module.
  </Accordion>
</AccordionGroup>

## Payments & Vendor Protection

<AccordionGroup>
  <Accordion title="Which vendor payments will be protected?">
    By default, Eftsure recommends protecting **all payments** across your organisation. You can exclude any number of vendors or vendor groups from verification at your discretion and re-include them later if needed.

    Protection operates at the **payment method** level, meaning all EFT payments are covered. Eftsure blocks users from generating incorrect payment files, providing a reliable last-line defence before funds leave your organisation.
  </Accordion>

  <Accordion title="How does Eftsure verify our vendors?">
    Vendor verification works in two phases:

    1. **Before go-live** — at the start of the project, your vendor master data is exported to a CSV file. Eftsure's verification team (or the Eftsure crowdsource database) performs the initial verification of all existing vendors.
    2. **After go-live** — new vendor invitations or change requests are sent directly from within D365 in real time.
  </Accordion>

  <Accordion title="How do you handle urgent payments and avoid late fees?">
    Eftsure recommends managing vendor details at **invoice time** rather than at payment time — this typically gives enough lead time for verification to complete and the vendor status to turn green before payment is due.

    When a vendor is not yet verified at payment time, you have two options:

    * **Urgent verification** — request an expedited verification, typically completed in under an hour (4-hour SLA).
    * **Self-certification** — two or more AP officers launch a workflow to mark the vendor as self-certified, allowing payment to proceed immediately after the workflow completes.
  </Accordion>

  <Accordion title="Can I configure exceptions to Eftsure verification?">
    Yes. Although Eftsure recommends no exceptions, the following are supported:

    * **Legal entities** — individual legal entities can be enabled or disabled for Eftsure services. Some customers only enable a subset of their legal entities.
    * **Vendor exclusions** — individual vendors or entire vendor groups can be excluded from Eftsure. A common use case is excluding employee or intercompany vendors.
    * **Payment methods** — you can configure multiple payment methods, some with Eftsure verification enforced and others without. Non-verified payment methods are often used for employee expenses or intercompany transactions.

    <Tip>
      In most scenarios, [self-certification](/user/self-certification) is a better alternative to blanket exclusions and keeps your audit trail intact.
    </Tip>
  </Accordion>
</AccordionGroup>

## Onboarding & Vendor Management

<AccordionGroup>
  <Accordion title="Can we add custom questions and attachments to onboarding?">
    Yes. On top of Eftsure's standard onboarding questions (name, contact, address, banking details, ABN, etc.), you can design your own onboarding questionnaires with any number of custom questions and file attachments — for example, certificates of currency or minority-ownership declarations.

    Vendor responses to these questions appear directly in D365 during the review step, helping you decide whether to create the vendor in the system. Contact your Eftsure administrator or refer to the in-product help for guidance on configuring vendor profiles and onboarding attachments.
  </Accordion>

  <Accordion title="How are vendors created in D365?">
    Vendors can be created in two ways:

    * **Manual creation** — directly in D365 by an AP officer.
    * **External creation** — via data entities, web services, or through the Eftsure onboarding workflow initiated from within D365 or the Eftsure portal.
  </Accordion>
</AccordionGroup>

## Compatibility & Integration

<AccordionGroup>
  <Accordion title="Is Eftsure compatible with other ISV solutions?">
    Yes. Eftsure inside D365 is compatible with all major ISV solutions and currently has certified extensions for:

    | Partner                       | Benefit                                      |
    | ----------------------------- | -------------------------------------------- |
    | **ExFlow**                    | Eftsure signals displayed on ExFlow invoices |
    | **Corpay**                    | Payment verification through Corpay          |
    | **Treasury Automation Suite** | Integrated payment protection                |
    | **Xe**                        | Blocks fraudulent Xe payments                |

    Contact your Eftsure representative for more information on partner integrations.
  </Accordion>
</AccordionGroup>

## Licensing

<AccordionGroup>
  <Accordion title="How does licensing work?">
    Eftsure provides access to **any number of users** — your user count is limited only by your D365 licences. API usage is **unlimited**, meaning you can validate as many payment journals as required without incurring additional fees.

    Monthly or annual Eftsure fees are based on the **number of vendor onboardings, verifications, and urgent verifications** performed in your environment. Contact your Eftsure account manager for pricing details specific to your organisation.
  </Accordion>
</AccordionGroup>

## Productivity & Comfort Pack

<AccordionGroup>
  <Accordion title="What additional productivity features are available?">
    To help you get started cleanly, Eftsure includes several **data reconciliation and bulk rename tools** accessible from the Admin workspace.

    The **Comfort Pack** adds the following optional features, depending on your configuration and access level:

    * **Government code lookups and validation** — ABN (Australia), NZBN (New Zealand), BRN (Malaysia), Siren (France), UEN (Singapore)
    * **VAT validation** — European VIES and UK HMRC
    * **Address validation** — Google and Bing address autocomplete and validation

    The extension also ships with pre-loaded **test cases** that you can replay to validate field mappings, default values, and workflows during testing and after upgrades.
  </Accordion>

  <Accordion title="Are there any hidden productivity shortcuts I should know about?">
    Yes — here are some useful features that are easy to miss:

    * **Payment journal validation shortcut** — the Eftsure icon on the payment journal header and lines acts as a clickable button to trigger verification directly, saving you a navigation step.
    * **Manage users from Excel** — use the **Open in Excel** button on the user list to import and export users across environments, which is especially useful after database refreshes.
    * **Hover for status details** — hovering over most Eftsure status icons reveals additional information about the current line status, which is helpful when assisting other users or resolving payment validation errors.
    * **Payment limits** — you can set a payment limit at the vendor or bank account level directly from the Eftsure menu.
    * **Vendor number sequences per group** — you can assign different number sequences to different vendor groups.
    * **Context-aware support tool** — the Support tool captures a screenshot of your current screen and attaches relevant vendor history, logs, and trace data automatically when you raise a ticket.
    * **Reset button (sandbox only)** — in sandbox environments, a Reset button lets you quickly re-run vendor creation scenarios for testing field mappings and default values.
  </Accordion>
</AccordionGroup>

***

## Feature Support

The tables below summarise which D365 and Eftsure features are supported in the current release.

### Supported Features

| Category                    | Supported Capabilities                                                                                                                                             |
| --------------------------- | ------------------------------------------------------------------------------------------------------------------------------------------------------------------ |
| **Eftsure actions**         | Create, Update, Expire, Self-certify, Limit, Comment vendors; Send, Accept, Reject, Incomplete, Cancel onboardings; Send and Cancel verifications; Verify payments |
| **International**           | All countries and international features; custom onboarding fields and attachments; Eftsure ID; using Eftsure in both the portal and D365 FO                       |
| **Vendor copying**          | Cross Company Data Sharing (CCDS); copy vendor across legal entities                                                                                               |
| **Multi support**           | Multiple legal entities; multiple bank accounts per vendor; multiple countries, currencies, and languages; bulk actions in the Eftsure menu                        |
| **Vendor creation**         | Manual creation; external creation via data entities or web services                                                                                               |
| **Invoices**                | Tax invoice journals; open vendor invoices; vendor invoice automation; ExFlow invoices; third-party invoices                                                       |
| **Payments**                | Consolidated payments; Corpay payments; Treasury Automation Suite; Xe payments                                                                                     |
| **Workflows**               | Proposed vendor changes workflow; vendor bank account approval workflow                                                                                            |
| **Exclusions & exceptions** | Enable/disable individual legal entities; exclude vendors and vendor groups; enable/disable payment method validation; self-certification                          |
| **Miscellaneous**           | Manual and continuous number sequences; vendor group number sequences                                                                                              |

### Not Supported

<Warning>
  The following features are **not supported** in Eftsure inside D365 FO and are unlikely to appear on the roadmap. Use the **Eftsure portal** to perform these actions.
</Warning>

| Category                          | Unsupported Capability                                  |
| --------------------------------- | ------------------------------------------------------- |
| **User management**               | Creating or managing Eftsure users                      |
| **Onboarding form management**    | Designing or editing onboarding form templates          |
| **Onboarding incomplete details** | Viewing or editing incomplete onboarding form responses |


## Related topics

- [Supplier Communication Tools in Eftsure Inside D365 FO](/user/supplier-communication.md)
- [Registering API Keys for Eftsure Inside D365 F&O](/integrations/api-keys.md)
- [Release Notes — Eftsure inside D365 FO (2024–2025)](/help/release-notes.md)
- [Eftsure inside Dynamics 365 FO: Payment Fraud Prevention](/introduction.md)
- [Troubleshooting Eftsure inside D365 Finance & Operations](/help/troubleshooting.md)