Accounting
ERP
Duplicate Payment Detection in Accounts Payable
Last updated: October 8, 2026 · Independent guide · We do not sell rankings or coverage.
Duplicate payment detection in accounts payable means finding invoices that were entered or paid more than once, ideally before the payment run and, failing that, afterward through review or a recovery audit. Most duplicates get past the ERP because its duplicate invoice check compares fields exactly, so a reformatted invoice number, a second vendor record or a payment made outside the invoice workflow does not trigger it. APQC’s Open Standards Benchmarking shows a median of 1.5% of annual disbursements processed as duplicate or erroneous payments across 1,686 organizations (APQC, no date shown).
Symptoms, likely causes and fixes
| Symptom | Likely cause | Fix |
|---|---|---|
| Two bills, same amount, invoice numbers differ only by prefix, zeros or punctuation | Invoice number keyed in different formats, so the exact-match check missed it | Set a keying convention and compare normalized numbers before payment |
| Vendor statement shows a credit balance or an unapplied payment | Same invoice received by email, mail, EDI or portal and processed twice | Route all invoices through one intake point and reconcile vendor statements |
| One supplier appears under two names or IDs in spend reports | Duplicate vendor master records, so the per-vendor check never compares the two bills | Block the extra record and check new vendors against tax ID and bank details |
| The ERP accepted an invoice number you know was already used | Duplicate check is off, set to warn only, or keyed on fields that changed | Review the check settings and criteria described below |
| Bank shows a wire or manual check with no matching paid bill | Payment made outside the AP invoice workflow, then the invoice was paid again | Require every disbursement to clear against a posted invoice |
| A corrected or re-sent invoice was paid alongside the original | Reversal and re-entry, or a revised invoice number, bypassed the check | Tie corrections to the original document and review overrides |
Cause 1: The invoice number was entered in a different format
ERP duplicate checks compare stored values exactly. Intuit’s QuickBooks team explains that the QuickBooks Desktop warning for duplicate bill numbers appears only when “the bill number, vendor name, and transaction type match exactly,” and that even a small difference can stop it from appearing (Intuit QuickBooks Community, staff reply, July 13, 2026).
To confirm it, export paid and open bills for the last 12 to 24 months, add a column that strips letters, punctuation and leading zeros from the invoice number, and sort by vendor, that column and amount.
Illustration: a clerk enters invoice “INV-00482” for $14,250.00 from a packaging supplier in March. In April a reminder copy is keyed as “482”, and both are paid. The normalized column shows “482” twice for the same vendor and amount.
Fix it with a keying convention (for example, exactly as printed) and a pre-payment report that compares normalized values.
Cause 2: The same invoice arrived through more than one channel
Suppliers send copies by email, mail, portal and EDI, and each copy can enter your queue separately. If you receive EDI invoices, a retransmitted 810 can create a second bill unless your translator or ERP rejects it; our guide to the EDI 810 invoice covers how those documents map into the ERP.
To confirm it, check the source on both bills. Vendor statements are the other signal, because the supplier often shows the second payment as an unapplied credit.
Fix it by sending all invoices to one AP inbox or capture tool. Some capture tools check the file itself: Stampli says its AI bot, Billy, blocks an upload when a prior invoice has the same file name, size and content (Stampli, no date shown).
Cause 3: The vendor exists twice in your vendor master
Most ERP checks run per vendor. SAP S/4HANA Cloud’s standard check compares company code, vendor, reference number, invoice date and currency (SAP Knowledge Base Article 3774533, no date shown). If the same supplier exists as two vendor records, the vendor field differs and the check passes both bills.
Confirm it by grouping vendors by tax ID, bank account and normalized name, then rerun your duplicate report across each group rather than by vendor ID.
Fix it by blocking the extra record and checking tax ID and bank details before any new vendor is created.
Cause 4: The ERP check is off, warn-only or keyed on the wrong fields
| System | What the native check compares | Gap to watch |
|---|---|---|
| SAP S/4HANA Cloud Public Edition (FI) | Company code, vendor, reference, invoice date, currency; also checks reversed and cancelled documents | Amount is not a standard key field; adding it is a system-wide configuration change |
| SAP S/4HANA (Logistics Invoice Verification) | Company code, reference and invoice date can be selected as criteria; credit memos can be included from release 2023 | Criteria are configured, so confirm which ones are switched on |
| Oracle NetSuite | Document number against records of the same type | “Warn (UI only)” does not stop a save; only “Warn and Block” stops vendor bills and blocks duplicate imports |
| Microsoft Dynamics 365 Business Central | Vendor invoice number for the same vendor, checked at posting | The check runs at posting, after approval; the number is only required if Ext. Doc. No. Mandatory is selected |
| QuickBooks Desktop | Bill number, vendor name and transaction type, exact match | Warns rather than blocks; any formatting difference defeats it |
For SAP, SAP Learning documents the Logistics Invoice Verification criteria under the customizing step “Set Check for Duplicate Invoices” (SAP Learning, no date shown).
In NetSuite, the setting is at Setup > Accounting > Preferences > Accounting Preferences, on the Items/Transactions subtab under Duplicate Number Warnings (Oracle NetSuite Help, no date shown). If yours is on “No Warnings” or “Warn (UI only)”, imported bills can come in as duplicates without any message.
In Business Central, the Ext. Doc. No. Mandatory field on the Purchases & Payables Setup page decides whether a purchase invoice can post without a vendor invoice number (Microsoft Learn, October 3, 2025). NORRIQ, which sells a Business Central add-on that checks earlier, notes that the standard check runs at posting rather than when the invoice is created (NORRIQ, no date shown).
Cause 5: A payment was made outside the invoice workflow
Urgent wires, manual checks and card payments often go out before the invoice is posted. When the invoice arrives, it is paid again, and no invoice check catches it because the first payment was never tied to a bill.
Confirm it by matching bank disbursements to paid invoices and tracing any payment without a linked bill.
Fix it by requiring every disbursement to clear against a posted invoice or a prepayment record.
Cause 6: A corrected or re-sent invoice was paid with the original
When a supplier revises an invoice, staff may reverse the original and re-enter it with a suffix such as “-R”. SAP’s recommended workaround for re-entering a reversed invoice is to change the reference number with a suffix (SAP KBA 3774533, no date shown), which also means the duplicate check can no longer see the link.
Fix it by referencing the original document on every correction and reviewing suffix re-entries before the payment run.
Recovering duplicates that were already paid
Send the supplier both payment references and ask for a refund or a credit against open invoices.
For older history, a recovery audit firm reviews payments and vendor statements. apexanalytix, which sells recovery audits, says most providers work on contingency at 20 to 30 percent of recovered amounts and that some audits look back three years or more (apexanalytix, April 10, 2025). Corpay, which sells AP payment services, describes recovery audits as a backstop rather than a primary control (Corpay, July 23, 2026).
Tools that detect duplicates before payment
AP automation platforms check at capture and approval. Stampli says it warns when three of four fields (invoice number, vendor, date, total) match (Stampli, no date shown). Vic.ai requires an exact match on document type, vendor and invoice number, and blocks approval, posting and export until the flag is cleared (Vic.ai, May 20, 2026). Tipalti markets a duplicate bill detection agent without publishing its matching rules (Tipalti, no date shown).
Payment-risk tools review the payment run across ERPs. Fiscal Technologies says its product flags duplicate invoices before the pay run and works with any ERP, but its fact sheet does not describe the matching method (Fiscal Technologies, February 2026). None publishes pricing on the pages cited. For the broader fraud angle, see our guide to how AP tools detect false invoices.
How to prevent duplicate payments
- Set the ERP check to block, not warn, where your system allows it, and confirm which fields it compares.
- Make the vendor invoice number mandatory on every bill.
- Use one intake channel per supplier.
- Control the vendor master with tax ID and bank detail checks before any new record is created.
- Run a normalized duplicate report before each payment run.
- Reconcile vendor statements for top suppliers monthly.
- Review overrides and reversals weekly, by someone who did not enter them.
Track the duplicate rate as a share of disbursements; our article on AP and AR KPIs and dashboards covers how to build that view.
How we researched this
We read the top-ranking pages, mostly vendor blogs, and checked claims against documentation from SAP, Oracle NetSuite, Microsoft and Intuit and AP vendors’ own pages. Causes are ordered by how often vendor documentation and competing guides cite them, not by a survey. No vendor paid for inclusion.
Related guides
- Invoice Approval Workflow: Routing AP Invoices for Sign-Off
- Three-Way Match in AP: How It Works and Software Options
- Positive Pay: How It Stops Check Fraud (2026)
Frequently asked questions
Why didn’t my ERP catch a duplicate invoice?
Most ERP checks compare fields exactly and per vendor, so a changed invoice number format, a second vendor record or a different date lets the second bill through. Some systems only warn.
How common are duplicate payments?
APQC’s benchmark shows a median of 1.5% of annual disbursements processed as duplicate or erroneous payments across 1,686 organizations. The figure combines duplicates with other errors.
How do I get money back from a duplicate payment?
Send the supplier both payment references and ask for a refund or a credit against open invoices. A recovery audit firm can review older history for a contingency fee.
Do I need separate software to detect duplicate payments?
Not always. A blocking ERP check, mandatory invoice numbers, a clean vendor master and a normalized pre-payment report may be enough. High-volume or multi-ERP teams often add a dedicated tool.
Sources
- APQC, duplicate or erroneous payments benchmark (measure 105905), no date shown, checked October 8, 2026. apqc.org
- SAP, Knowledge Base Article 3774533, no date shown. support.sap.com
- SAP Learning, Invoice Verification customizing, no date shown. learning.sap.com
- Oracle NetSuite Help, Duplicate Number Warnings, no date shown. docs.oracle.com
- Microsoft Learn, Business Central external document numbers, October 3, 2025. learn.microsoft.com
- NORRIQ (sells a Business Central add-on), vendor invoice no. check, no date shown. docs.norriq.com
- Intuit QuickBooks Community, staff reply, July 13, 2026. quickbooks.intuit.com
- Stampli (sells AP automation), duplicate payments article, no date shown. stampli.com
- Vic.ai (sells AP automation), Duplicate detection, May 20, 2026. intercom.help
- Tipalti (sells AP automation), Finance AI, no date shown. tipalti.com
- Fiscal Technologies (sells payment-risk software), fact sheet, February 2026. fiscaltec.com
- apexanalytix (sells recovery audits), recovery audit cost, April 10, 2025. apexanalytix.com
- Corpay (sells AP payment services), duplicate payment detection, July 23, 2026. corpay.com
Sherman Hsieh
Independent analysis of enterprise software — ERP, CRM and more
