Article
What Are Duplicate Payments and How to Prevent Them
A duplicate payment is when the same invoice, or two different invoices for the same goods or services, gets paid twice. It is one of the most common and most preventable forms of accounts payable (AP) leakage: research from APQC puts duplicate or erroneous payments at 0.8%-2% of a company's total annual disbursements, with the gap between top and bottom performers coming down almost entirely to process discipline.
That range sounds small until you put a real number against it. A services firm paying out $6 million a year in subcontractor and vendor bills, sitting at the bottom of that range, is losing roughly $120,000 a year to payments that never should have gone out. Most of it is recoverable if caught before the money leaves, and most of it is preventable with the right checks in the first place.
What actually causes a duplicate payment?
Duplicate payments almost never come from one big mistake. They come from small gaps in a process that otherwise looks fine on paper. The patterns AP teams see most often:
- The same invoice enters the system twice. A vendor emails the invoice, then mails a paper copy, then re-sends it because nobody replied. Each version gets keyed in separately.
- A credit memo gets missed. The vendor issues a credit for a return or an error, but the credit never gets applied, so the original invoice gets paid in full and the reissued corrected invoice gets paid too.
- Two people touch the same invoice. One person in AP enters it, another approves and pays it without checking whether it was already keyed in, especially common when approvals happen over email or across two systems.
- A slightly different invoice number for the same charge. A vendor's system appends a suffix or reissues the invoice with a new number after a dispute, and matching software built to check only exact invoice numbers waves it through as new.
- Recurring or subscription billing is paid manually alongside an automatic draft. The vendor's bank draft goes through, and a bookkeeper who does not see the bank feed also cuts a check for the same invoice.
None of these require anyone to do anything wrong. They are what happens when invoice volume grows past what a manual, single-person review can reliably catch. Manual AP processes catch far fewer of these errors than teams assume, which is exactly why the checks below matter more as a business scales past a handful of vendors.
How much do duplicate payments actually cost a company?
The APQC figure above, 0.8%-2% of total disbursements, is the benchmark most finance teams cite because it is measured across a large cross-industry sample, not a vendor's own case studies. On a $10 million annual spend base, that is $80,000 to $200,000 a year, before you count the staff time spent finding the error, requesting the refund, and reconciling the books once it is found.
Duplicate payments sit inside a bigger pattern. The ACFE's 2024 Report to the Nations estimates that a typical organization loses 5% of its annual revenue to occupational fraud of all kinds, and billing schemes, which include manipulating invoices so they get paid more than once, account for 22% of all asset misappropriation cases. Most duplicate payments are not fraud; they are process gaps. But the same weak spot, an invoice that gets approved without being checked against what was already paid, is what both an honest mistake and a deliberate scheme rely on.
How do you catch a duplicate payment before it goes out?
Catching a duplicate before the money leaves is always cheaper than getting it back afterward. The core checks, in order of how much of the problem they close:
- Match on more than the invoice number. Check vendor name, amount, and invoice date together, not just the invoice number field, so a reissued invoice with a new number still gets flagged.
- Centralize invoice intake. One inbox, one place invoices land, so the same bill cannot enter the system twice through two different channels.
- Separate who enters an invoice from who approves it. This is basic segregation of duties, and it is also the single control most likely to catch a duplicate before payment, because a second set of eyes is looking at the vendor and amount fresh.
- Check against paid history, not just open invoices. A duplicate check that only looks at unpaid invoices will miss a bill that already went out weeks ago.
- Reconcile the vendor statement monthly. A vendor statement shows every invoice they think you owe; comparing it to what you have actually paid surfaces a double payment fast, usually before the vendor even notices and refunds it.
These are the same fundamentals covered in how invoice matching software works, and they are also where a lot of matching setups quietly fail: the common causes of invoice matching errors are largely the same gaps that let a duplicate slip through.
Hire vs. software: what's the honest math on preventing duplicate payments?
This is where the owner or the person who pays the bills has to run real numbers, not vibes. An Accounts Payable Specialist's national base salary runs $51,750-$63,250, and that is before benefits: BLS data shows benefits make up roughly 29-30% of total employer compensation costs, so a fully loaded hire runs meaningfully above the base number once payroll tax, insurance, and paid leave are added in.
Hiring dedicated AP help absolutely closes this gap if the volume justifies it. Published guidance on when automation pays off is inconsistent, some vendors put the break-even as low as 100 invoices a month, others put it well into the hundreds, but the pattern across sources agrees on the shape: below the low hundreds of invoices a month, a careful person with a checklist and a vendor-statement habit will often out-perform any tool, because the volume is too low for automation to earn back its setup cost. Above that, manual review starts missing things simply because there is too much to check by hand every day.
The honest framing for a firm somewhere in the middle, too many invoices for one person to double-check everything, not enough to justify a second AP hire, is that software should absorb the repetitive matching work before the next hire, not replace the person doing it now. A human still has to look at the flags, approve the payment, and own the vendor relationship. What changes is how much gets caught before it becomes a problem someone has to chase down after the fact. And the math runs in both directions: the software pays for itself first in the hours it gets back, then again in the overbillings and duplicates it catches that a busy person would have missed.
Hire vs. outsource vs. software, at a glance
| Approach | Rough cost basis | What it catches | Where it falls short |
|---|---|---|---|
| Dedicated AP hire | $51,750-$63,250 base, Robert Half, plus ~30% in benefits load (BLS) | Whatever the person has time to check by hand, plus institutional vendor knowledge | Volume outgrows one person's attention faster than most owners expect |
| Manual process, no dedicated hire | Whoever's time it eats, usually the owner or bookkeeper | Obvious errors, when there's time to look | Duplicate checks and vendor-statement reconciliation are the first things to slip under time pressure |
| Matching or AP automation software | Not published by Quittance; varies by vendor and volume | Duplicate invoice numbers, amount/vendor mismatches, and, where the tool checks the full agreement, terms the invoice violates | Still needs a human to approve what it flags; weakest below roughly a hundred invoices a month, where setup cost isn't earned back |
What does this look like once an invoice is cleared to pay?
Once an invoice passes the checks above, it should land in the accounting system as a bill waiting for a person to approve, not as a payment that has already gone out. Xero, for example, puts a created bill into a Draft tab that requires action before it moves toward being paid. That extra step, a clean bill sitting in draft rather than money already moved, is what keeps the fix for duplicate payments from creating a new risk: a tool that pays on its own without anyone checking first.
Frequently asked questions
What is a duplicate payment in accounting? A duplicate payment is when the same invoice, or two invoices covering the same charge, gets paid twice, usually because it entered the accounting system through two different channels or was approved by two people who did not know the other had already processed it.
How common are duplicate payments? Organizations report duplicate or erroneous payments at 0.8%-2% of total annual disbursements, according to APQC's Open Standards Benchmarking research, with the gap between best and worst performers driven mainly by process controls rather than company size.
Can you get a duplicate payment back from a vendor? Most duplicate payments are recoverable if the vendor is legitimate and reachable; the standard route is a written request citing both invoice numbers, payment dates, and amounts, asking for a refund or a credit against the next invoice. The sooner it is caught, the faster and cleaner the recovery.
Does 3-way matching stop duplicate payments? Three-way matching, which checks the invoice against the purchase order and the receipt, is built to catch billing errors and unauthorized charges, but it does not automatically catch a duplicate unless the process also checks the invoice against payment history, not just against open, unpaid invoices.
Is a duplicate payment the same thing as invoice fraud? No. Most duplicate payments are honest process gaps, not fraud. But the ACFE's research on billing schemes shows the same weak point, an invoice approved without being checked against what has already been paid, is also what a deliberate billing scheme relies on, which is why the same controls address both.
How many invoices a month does it take before automation is worth it? There is no single agreed-upon number. Vendor and industry guidance on the break-even point ranges from around 100 invoices a month to several hundred, depending on invoice complexity and staff time available; below that range, a disciplined manual process with vendor-statement reconciliation often performs just as well.