Business Central duplicate invoice detection that goes past the vendor invoice number

What Business Central checks out of the box

On purchase documents, the vendor's own invoice number goes in the Vendor Invoice No. field. Microsoft's documentation notes that Business Central doesn't check whether these numbers are unique when you enter them. Turning on Ext. Doc. No. Mandatory in Purchases & Payables Setup makes the field required, which is the foundation for any duplicate control. Some teams add an AL extension or a Power BI report that looks for exact repeats.

What still slips through

• A vendor invoice number with one character changed, such as INV-2026-0412 and INV-2026-0413, on the same amount a few days apart.
• A resent invoice whose amount differs by a rounding cent or a small fee.
• An invoice from a vendor whose amount breaks sharply from that vendor's usual pattern.
• A normal-looking invoice that asks you to pay a bank account the vendor has never used before.

How the Invogi connector works

1. Your Business Central admin registers an app in Microsoft Entra ID and grants it access to the Business Central API. Invogi uses the OAuth2 client-credentials flow; no user password is shared.
2. Invogi syncs vendors and purchase invoices every hour, or on demand.
3. Each invoice runs through the same controls as an API submission: exact duplicates, near-duplicates (invoice numbers at least 90% similar, amounts within 1%, issue dates within 14 days), supplier amount anomalies, and, with the custom vendor bank page, bank-account changes.
4. Your team reviews flagged invoices in Invogi, with the matching invoice and the evidence for each flag, before the payment run.

The connector is included with Invoice Firewall. Not ready to connect? Export your posted purchase invoices to Excel and run a free AP Risk Scan first.