> ## 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.

# Partner ISV Extensions for Eftsure Inside D365

> ISV partner extensions that surface Eftsure fraud prevention signals inside ExFlow, Corpay, Xe, Treasury Automation Suite, and Microsoft Invoices.

Eftsure inside D365 F\&O partners with leading ISV solutions to extend payment fraud prevention further into your AP and payment workflows. Each partner extension surfaces Eftsure's vendor and bank account verification signals directly inside the partner's own interface, so your team can act on risk information without leaving the tools they already use.

All partner extensions are maintained by Eftsure's D365 F\&O team and are available as separate LCS packages alongside your base Eftsure extension. Each release notes entry lists compatibility details with the current partner versions.

<Note>
  Partner extensions are licensed separately as options to **Eftsure inside Dynamics 365 F\&O**. Each partner product is also sold separately — contact the relevant partner to arrange a demo or purchase.
</Note>

<Note>
  Interested in becoming a partner? Visit [https://www.eftsure.com/partners/](https://www.eftsure.com/partners/).
</Note>

***

## Available extensions

<CardGroup cols={2}>
  <Card title="Eftsure inside ExFlow" icon="file-invoice">
    Surfaces Eftsure vendor and bank account status inside ExFlow invoice processing workspaces and forms. Powered by **Truvio** (formerly SignUp Software).
  </Card>

  <Card title="Eftsure inside Microsoft Invoices" icon="microsoft">
    Adds Eftsure status icons and menus to Microsoft Invoice Capture invoice forms and the Vendor Invoice Automation Workspace.
  </Card>

  <Card title="Eftsure inside Corpay" icon="money-bill-transfer">
    Blocks fraudulent payments by surfacing Eftsure statuses on payment journal lines before you send payments via **Corpay Cross-Border**.
  </Card>

  <Card title="Eftsure inside Treasury Automation Suite" icon="building-columns">
    Integrates Eftsure validation into the **Treasury Automation Suite** payment journal workflow, with exceptions surfaced in the TAS Exception List.
  </Card>

  <Card title="Eftsure inside Xe" icon="globe">
    Prevents fraudulent payments by surfacing Eftsure statuses on payment journal lines before you send payments via **Xe Global Payments**.
  </Card>
</CardGroup>

***

## Eftsure inside ExFlow

[ExFlow](https://truvio.com/products/finance-operations/ap-automation), part of the [Truvio](https://truvio.com/) portfolio, processes supplier invoices in D365. The Eftsure inside ExFlow extension adds real-time Eftsure vendor risk signals at the point of invoice approval — giving AP teams visibility of vendor status well before payment time, leaving lead time for vendors to respond to any verification requests.

**Licensing:** ExFlow is sold separately by Truvio. Eftsure inside ExFlow is a licensed option on top of Eftsure inside D365 F\&O.

### What's added to the ExFlow UI

Four components are added on top of ExFlow screens:

| Component               | Location                       | Purpose                                                         |
| ----------------------- | ------------------------------ | --------------------------------------------------------------- |
| **Eftsure menu**        | Action panes                   | Triggers Eftsure actions and navigation                         |
| **Eftsure title icons** | Top-right corner of forms      | Shows vendor and bank account verification status at a glance   |
| **Bank account icons**  | Grids, next to vendor accounts | Displays the status of the matched bank account                 |
| **GST icons**           | Grids, next to GST amounts     | Enables reconciliation of GST amounts against vendor GST status |

These components appear in the **ExFlow supplier invoice management** and **My supplier invoices** workspaces, as well as all import forms, document forms, agreements, and posting proposals.

Vendor and bank account lookups are also extended to display Eftsure status colours and icons, so you can see verification status during record selection — not just after.

The standard Eftsure filter button is also available on all ExFlow screens, allowing you to filter by bank account colour or vendor blocking status.

**Activation:** Features are visible only for legal entities where Eftsure is enabled. No changes appear for other legal entities.

***

## Eftsure inside Microsoft Invoices

This extension brings Eftsure status visibility to invoices processed through **Microsoft Invoice Capture**. It adds the same five Eftsure UI components that appear in the standard extension, now available across the core D365 invoice forms.

**Licensing:** Microsoft Invoice Capture is sold separately by Microsoft. Eftsure inside Microsoft Invoices is included out of the box since v4.32.39.1164.

<Warning>
  Microsoft Invoice Capture is a separate application. The UI changes described here apply to invoices inside **Dynamics 365 Finance** — some of which may have been transferred from Invoice Capture.
</Warning>

### What's added to the invoice UI

| Component              | Location                                                   |
| ---------------------- | ---------------------------------------------------------- |
| **Eftsure Menu**       | Action panes on invoice forms                              |
| **Eftsure icons**      | Top-right corner of forms (vendor and bank account status) |
| **Eftsure Shortcuts**  | Form toolbars, next to the Office button                   |
| **Bank account icons** | Grids, showing matched bank account status                 |
| **GST icons**          | Grids, next to GST amounts                                 |

These components are available on the **Vendor Invoice Automation Workspace**, **Open vendor invoices**, **Tax Invoice Journal**, **Pending vendor invoices**, and **Tax Invoice Pool** forms.

The standard Eftsure filter button is also available on the workspace form parts, allowing you to filter by bank account colour or vendor blocking status.

***

## Eftsure inside Corpay

The Corpay extension prevents fraudulent payments by surfacing Eftsure verification statuses directly on payment journal lines before you send payments via **Corpay Cross-Border**.

**Licensing:** Corpay Cross-Border is sold separately by Corpay. Eftsure inside Corpay is a licensed option on top of Eftsure inside D365 F\&O.

### How it works

Once the extension is deployed, your payment journal lines are extended with Eftsure statuses:

* **On errors:** Payment journal lines with invalid or unverified payees are highlighted. The **Generate Payments** and **Send to Corpay** actions are blocked until all issues are resolved.
* **On success:** When all payment journal lines are green and valid, payments proceed normally through Corpay.

The typical workflow is:

<Steps>
  <Step title="Open a payment journal">
    Open an existing payment journal containing lines to be paid via Corpay.
  </Step>

  <Step title="Review Eftsure statuses">
    Examine the Eftsure status column on each payment line. Lines with issues are highlighted.
  </Step>

  <Step title="Resolve or remove problem lines">
    Fix validation issues for flagged vendors, or remove problematic lines for later processing.
  </Step>

  <Step title="Send to Corpay">
    Once all lines are green, proceed with **Generate Payments** and **Send to Corpay** as normal.
  </Step>
</Steps>

***

## Eftsure inside Treasury Automation Suite

The Treasury Automation Suite extension integrates Eftsure validation into the TAS payment journal workflow. Validation errors from both Eftsure and Treasury Automation Suite are surfaced together in the TAS **Exception List**, giving you a single place to manage all payment validation issues.

**Licensing:** Treasury Automation Suite is sold separately by Truvio/SKSoft. Eftsure inside Treasury Automation Suite is a licensed option on top of Eftsure inside D365 F\&O.

### How validation works

Before Eftsure validation runs, all payment journal lines have a verification status of **None**. Attempting to pay any of these lines is blocked until validation has been performed.

You can trigger validation in three ways:

* **Validate → Validate** — runs standard validation including Eftsure
* **Validate → Eftsure → Payments** — runs Eftsure-only validation
* The **Eftsure main icon** in the top-right corner of the payment journal — runs Eftsure-only validation

### Exception List

Validation errors from both Eftsure and Treasury Automation Suite appear together in the **Exception List**, accessible from the payment journal toolbar. Eftsure errors are highlighted with a light blue background for easy identification.

The Exception List has two display modes:

| Mode         | Description                                                                                        |
| ------------ | -------------------------------------------------------------------------------------------------- |
| **Advanced** | All errors on a single minimised line; includes Eftsure icons, filters, preview parts, and buttons |
| **Normal**   | Returns to the original TAS Exception List layout                                                  |

<Steps>
  <Step title="Open a payment journal">
    Open a payment journal with existing lines.
  </Step>

  <Step title="Run validation">
    Use **Validate → Validate** or trigger Eftsure validation via the Eftsure icon.
  </Step>

  <Step title="Review exceptions">
    Open the **Exception List** and review all errors. Eftsure errors appear with a light blue background.
  </Step>

  <Step title="Resolve or remove problem lines">
    Fix any flagged lines or remove them for later reprocessing.
  </Step>

  <Step title="Complete payment">
    Once the journal is 100% green, payment proceeds normally through Treasury Automation Suite.
  </Step>
</Steps>

***

## Eftsure inside Xe

The Xe extension prevents fraudulent payments by surfacing Eftsure verification statuses on payment journal lines before you send payments via **Xe Global Payments**.

**Licensing:** Xe Global Payments is sold separately by Xe. Eftsure inside Xe is a licensed option on top of Eftsure inside D365 F\&O.

### How it works

Once the extension is deployed, your payment journal lines are extended with Eftsure statuses:

* **On errors:** Payment journal lines with invalid or unverified payees are highlighted. The **Generate Payments** and **Pay with Xe** actions are blocked until all issues are resolved.
* **On success:** When all payment journal lines are green and valid, payments proceed normally through Xe.

The typical workflow mirrors the Corpay workflow:

<Steps>
  <Step title="Open a payment journal">
    Open an existing payment journal containing lines to be paid via Xe.
  </Step>

  <Step title="Review Eftsure statuses">
    Examine the Eftsure status column on each payment line.
  </Step>

  <Step title="Resolve or remove problem lines">
    Fix validation issues or remove problematic lines for later processing.
  </Step>

  <Step title="Pay with Xe">
    Once all lines are green, proceed with **Generate Payments** and **Pay with Xe** as normal.
  </Step>
</Steps>


## Related topics

- [Frequently Asked Questions — Eftsure inside D365 FO](/help/faq.md)
- [Eftsure inside Dynamics 365 FO: Payment Fraud Prevention](/introduction.md)
- [Integration Tools in Eftsure Inside D365 Finance & Ops](/integrations/overview.md)
- [Troubleshooting Eftsure inside D365 Finance & Operations](/help/troubleshooting.md)
- [Registering API Keys for Eftsure Inside D365 F&O](/integrations/api-keys.md)