Article
Why Duplicate Payments Happen in Accounts Payable
Duplicate payments happen in accounts payable when the same invoice is entered, approved, and paid more than once, usually because it enters the system through more than one channel, under more than one vendor code, or gets keyed in twice by different people who can't see each other's work. It is rarely one careless click. It is almost always a gap in how invoices are matched or routed that a single mistake simply walks through.
Even AP teams that consider themselves careful are not immune. APQC's Open Standards Benchmarking data shows that top-performing organizations still see about 0.8% of their annual disbursements come back as duplicate or erroneous payments. That is the best case, not the worst case. For a firm paying out $10 million a year to vendors and subcontractors, 0.8% is $80,000 moving out the door and then having to be clawed back.
What exactly counts as a duplicate payment?
A duplicate payment is any case where the same underlying obligation, one invoice, one delivery, one service period, gets paid twice. That includes the obvious version (the identical invoice number paid twice) and the less obvious versions AP teams miss more often: the same invoice entered under two different vendor codes, the same work billed once against a purchase order and again as a standalone invoice, or a credit memo that never got netted against the original charge. All of these show up on the bank statement the same way. Money left twice for one thing.
Why does the same invoice get paid twice?
Four patterns account for most of it.
The invoice arrives more than once, and each copy gets treated as new. A vendor emails an invoice, then mails a paper copy as a follow-up, then a subcontractor uploads it again to a vendor portal. If nothing links those three entries to one another, AP sees three invoices instead of one.
The vendor has more than one code in the system. A subcontractor gets set up as "J. Ramirez Consulting" in January and "Ramirez Consulting LLC" in June, maybe because someone typed the name differently or a new hire didn't check first. Most duplicate checks only compare invoice numbers within the same vendor record. According to the Washington State Auditor's Office, standard controls typically catch a repeated invoice number only when it's filed under the same vendor number, so the identical invoice filed under a second vendor code slides straight through.
A system migration re-imports history. Moving to a new ERP, or even just upgrading one, sometimes pulls in invoice history that was already paid in the old system. If the new system doesn't recognize those records as already settled, they sit in the queue looking exactly like open bills.
Approvals happen in parallel with no shared view. A services firm with several project managers, each approving invoices for their own engagements, has no natural place where someone checks whether a different manager already approved a matching bill from the same subcontractor for overlapping dates. NetSuite's guide to preventing duplicate payments points to exactly this: manual entry combined with decentralized processing is one of the most common root causes, because no single person, or system, has the full picture.
Where do duplicate payments hide from standard checks?
| Cause | What it looks like on the page | Why a standard check misses it |
|---|---|---|
| Same invoice, two vendor codes | Two invoice records, same amount, same date, different vendor name spelling | Duplicate checks usually compare invoice numbers within one vendor record, not across vendor codes |
| PO and non-PO for the same work | An invoice matched to a purchase order, plus a separate invoice for the same deliverable with no PO attached | 3-way matching checks the PO-linked invoice but has nothing to compare the unlinked one against |
| Re-imported history after a system migration | An already-paid invoice reappears as an open item post-migration | The new system has no record that the invoice was previously settled |
| Parallel approvals, no shared view | Two project managers each approve a bill from the same subcontractor for overlapping work | Approval routing is siloed by project or manager, with no cross-check at the point of payment |
| Credit memo not netted | A credit is issued for an error, but the original full invoice is paid anyway | The credit sits in a separate queue that isn't reconciled against the invoice it corrects |
Why does a growing business see more duplicates, not fewer?
It seems backwards, but volume and headcount both work against you. More invoices means more chances for the same bill to arrive twice. More people touching AP, whether that's a second bookkeeper, a project manager approving their own subcontractors, or an office manager filling in during a busy month, means more places the same invoice can get keyed in without anyone else seeing it happen first. Hiring another person to review invoices adds a second set of eyes, but it does not, on its own, close the gap that let the first duplicate through: the system still can't see across vendor codes, PO and non-PO invoices, or separate approval queues unless something is built to check across all of them.
Why do duplicate payments slip past 3-way matching?
Three-way matching compares the invoice, the purchase order, and the receipt of goods or services. It is effective at catching an invoice that doesn't match what was ordered or received. It is not designed to catch a second, separate invoice for the same work that was never tied to that PO in the first place, or one that was billed against a different PO entirely. If a subcontractor invoice skips the PO altogether, which is common for services firms running on SOWs and rate cards rather than purchase orders, there's no PO-based match to run at all. For more on where matching checks stop and where the money actually leaks, see our guide to invoice matching errors.
What does a duplicate payment actually cost, beyond the refund?
Getting the money back is not automatic. It means noticing the duplicate exists (often weeks or months later, during a reconciliation or an audit), contacting the vendor, and waiting for a refund or a credit against a future invoice, if the vendor cooperates at all. Some never get caught. Every hour spent chasing a refund is an hour not spent on the next invoice in the queue, and every uncaught duplicate is a small, permanent leak in the AP-manager's numbers. Our breakdown of measuring AP leakage at a services firm walks through how to put a number on that leak specifically.
What this means for the review process
None of this is really a training problem. It's a visibility problem. The person entering the invoice a second time isn't being careless, they simply can't see that a version of it already exists somewhere else in the system, under a different vendor code, a different PO, or a different manager's queue. Closing that gap for good means checking every new invoice against everything that's already been paid or approved, not just against the one purchase order it happens to cite, which is the same principle behind agreement-level matching rather than PO-only matching. For the CFO, that visibility is the difference between finding a duplicate in a quarterly audit and never finding it at all.
FAQ
Is a duplicate payment always caused by human error? Not entirely. Human error, like keying the same invoice in twice, is often the visible trigger, but the underlying cause is usually a system gap: no cross-check across vendor codes, no link between PO and non-PO invoices for the same work, or no shared view across approvers. Fixing the visible error without closing the underlying gap usually means the same type of duplicate recurs.
Can accounting software prevent duplicate payments on its own? Most accounting systems can catch an exact repeated invoice number under the same vendor record. They generally cannot catch a duplicate that shows up under a different vendor code, a different PO, or a separate approval queue, because that requires checking across records the software wasn't set up to compare.
Why do duplicate payments slip past 3-way matching? Three-way matching checks an invoice against its purchase order and the receipt of goods or services. It doesn't check whether a second, unrelated invoice already covers the same work, especially for services invoices that never had a PO attached in the first place.
How common are duplicate payments in accounts payable? APQC's benchmarking data shows that even top-performing AP teams see roughly 0.8% of their annual disbursements come back as duplicate or erroneous payments, meaning the risk exists at every level of process maturity, not just in disorganized teams.
What's the difference between a duplicate payment and an overpayment? A duplicate payment pays the exact same invoice or obligation twice. An overpayment pays the right invoice but for the wrong amount, for example paying a rate-card rate that's higher than what was actually agreed. Both are AP leakage, but they get caught by different checks.