Duplicate payments happen more often than most finance teams believe, and they are hard to spot because each one looks like a normal invoice. A supplier resends a bill by email after posting it, a corrected invoice arrives with a new number, or the same supplier sits twice in the vendor master. The second payment goes out and nobody notices until an audit, if then.
This guide explains what a duplicate invoice is, why duplicates get through, and the controls accounts payable teams use in 2026 to stop them: one intake point, a clean vendor master, purchase order matching and automated checks before payment.
What is a duplicate invoice?
A duplicate invoice is a second request for payment for goods or services that have already been invoiced. It may be an exact copy, or a near copy with a different invoice number, a slightly different date or a corrected amount. A duplicate payment happens when accounts payable pays both.
Duplicates are usually honest mistakes. They become expensive because they are paid quietly, and recovering money after the fact takes time and strains the supplier relationship.
Why do duplicate invoices get paid?
Most duplicates get through because of process gaps rather than carelessness. The usual causes:
- Duplicate vendor records: the same supplier exists twice in the enterprise resource planning (ERP) system, under slightly different names or addresses, so the same invoice can be posted to both.
- Multiple channels: an invoice arrives by email, then by post, then through a portal, and each copy is entered.
- Manual data entry: a typo in the invoice number or amount means an exact match check misses the copy.
- Disputed invoices: a disputed invoice sits unresolved, the supplier resends it, and once the dispute clears both versions are paid.
- Cancelled or corrected invoices: a supplier cancels and reissues an invoice, and the original is not voided in the system.
- Missing purchase order numbers: without a purchase order reference, there is nothing to tie the invoice to a single commitment.
- Expense claims: an employee submits the same receipt twice, or through both an expense report and a supplier invoice.
Where do duplicates come from in practice?
Duplicate vendors
A supplier that serves several departments may invoice each separately, or be set up more than once as different teams onboard it. Maintain one vendor master, check for duplicates when a new supplier is added, and merge records you find. Controlled vendor onboarding prevents most of this at the source.
Unresolved disputes
When an invoice is disputed, mark it on hold, notify the supplier and the approvers, and link any corrected invoice to the original. If the original stays in the queue, it can be released alongside the replacement.
Cancelled or adjusted invoices
Corrections should void the original in the system, not just in someone's inbox. Record the reason and keep both documents linked so an auditor can follow the trail.
How do you prevent duplicate payments?
Prevention is a set of controls rather than a single check.
- One intake point: route every invoice, however it arrives, into one queue. Tell suppliers where to send invoices and stop accepting them elsewhere.
- Clean vendor master: deduplicate supplier records, restrict who can create them, and validate tax and bank details on entry.
- Automated data capture: extracting invoice fields automatically removes most typing errors. See invoice data extraction.
- Purchase order matching: match each invoice to its purchase order and goods receipt before approval. Once a purchase order line is fully invoiced, a second invoice against it stands out.
- Fuzzy duplicate checks: compare supplier, amount, date and reference for close matches, not only identical invoice numbers.
- Hold and review: route suspected duplicates to a person with the original alongside, rather than rejecting them automatically.
- Regular audits: review paid invoices periodically to find duplicates that slipped through and fix the cause.
In Invoiceflow, Aavenir AI reads each invoice on arrival, checks it against earlier invoices, purchase orders and the contract, and flags likely duplicates with the matching record beside it. An accounts payable specialist approves or rejects every flag.
What should you do when a duplicate has been paid?
Contact the supplier quickly with both invoice references and payment details, and agree whether they will refund or credit the amount against a future invoice. Record the outcome, then find the cause: a duplicate vendor record, a second intake channel, a missing void. Fixing the cause matters more than recovering a single payment.
How does contract matching help?
Matching invoices to the contract, not only to the purchase order, catches a wider set of errors: prices above the agreed rate, charges for services not in scope, and billing after the term ended. Duplicates are one form of overbilling, and the same check finds the others. See invoice to contract compliance.
The bottom line
Duplicate invoices are a process problem with a process fix. Take invoices in through one door, keep one record per supplier, match every invoice to its purchase order and contract, check for near matches, and have a person review anything flagged before it is paid.