Duplicate Payment 2026 [Full Data Report]

Even the best-run accounts payable departments pay the same invoice twice. APQC’s Open Standards Benchmarking survey found that 0.8% of annual disbursements are duplicate or erroneous among top-performing organizations, and more than double that share, over 2%, among bottom performers.

How many payments are actually duplicates?

Top-performing teams, the top quartile in APQC’s survey, see 0.8% of their total annual disbursements come back duplicate or erroneous. Bottom-performing teams see more than double that share, over 2% of disbursements. That range covers three related failure types together: a straight duplicate payment, a payment sent to the wrong vendor, and a payment for the wrong amount, all counted as the same category of AP error.

Figure 1: Share of annual disbursements that are duplicate or erroneous, by AP team performance tier. Source: APQC Open Standards Benchmarking, Accounts Payable survey, cited by CFO.com (2020).

The gap matters more than either number looks at first glance. A business paying out $50 million a year loses roughly $400,000 to duplicate or erroneous disbursements at the top-performer rate, and more than $1 million at the bottom-performer rate. Neither figure is a fraud loss; both are the cost of a payment control that did not catch a bill it had already paid.

It is also a different failure mode than the one covered in late payment statistics: late payment is money moving too slowly, while a duplicate payment is money moving twice for the same bill. Both come down to weak visibility into what has already been sent and what is still outstanding.

How much does the average duplicate payment cost?

SAP Concur’s own invoice data offers the clearest per-transaction picture. Across a year of small and mid-sized business customer data, the company found that a typical SMB processing about 450 invoices in a busy month flagged roughly 1.29% of them as duplicates, about 6 invoices. The average value of one of those duplicate invoices was $2,034, which puts the monthly exposure for a single mid-size business at close to $12,000 if none of the 6 were caught before payment went out.

Figure 2: Share of processed invoices a typical small business flags as duplicates. Source: SAP Concur, SMB invoice data study.

That per-invoice figure is dated; it comes from an SAP Concur data set covering invoice activity before wider adoption of automated invoice matching. It still holds up directionally, because the same dollar-value pattern shows up in a separate estimate from the Institute of Finance & Management (IOFM), which puts the industry-wide loss at up to 1.5% of an organization’s total outgoing cash flow, a range consistent with APQC’s disbursement-level figures even though it comes from a different measurement method. Scaled up, that 1.5% figure is not a rounding error for a larger business: a company with $10 million in annual outgoings could be losing anywhere from $80,000 to $150,000 a year to duplicate payments alone, spread thin enough across hundreds of individual bills that no single payment looks alarming on its own. For a small business running on tighter margins, even the SAP Concur-scale numbers matter: $12,000 a month in unrecovered duplicate spend is real payroll, real rent, or a real supplier discount missed because cash that should have stayed in the account went out twice and has to be chased back from a vendor instead.

Figure 3: Average dollar value of a single duplicate invoice at a typical small business. Source: SAP Concur, SMB invoice data study.

That is also why duplicate payments are so easy to miss on a bank statement. Each one is a normal-looking transaction to a normal-looking vendor, for a normal-looking amount; the only thing wrong with it is that a nearly identical transaction already went out weeks earlier. Catching that pattern by eye, across hundreds of monthly disbursements, is exactly the kind of matching problem software is better suited for than a person scanning a ledger.

How accurate are AP teams at avoiding payment errors in the first place?

Duplicate payments are one symptom of a broader accuracy problem, and APQC’s more recent benchmarking breaks that out directly. Top-performing organizations get 98% of disbursements right on the first attempt, meaning correct amount, correct vendor, correct timing, with no rework needed. The median organization manages 95%. Bottom-quartile organizations fall to 88%, which APQC frames plainly: roughly 12 out of every 100 payments they send are late or otherwise incorrect the first time. That accuracy figure covers more ground than duplicates alone, but a payment that goes out to the wrong vendor or in the wrong amount tends to travel through the same weak controls that let a duplicate slip past, which is why the two benchmarks move together across the same performance tiers.

Figure 4: Share of disbursements processed correctly on the first attempt, by AP team performance tier. Source: APQC, cited by CFO.com (February 2025).

The 10-point gap between top and bottom performers on this measure lines up closely with the 0.8%-to-2%-plus spread on duplicate and erroneous payments specifically, which is not a coincidence: a team that gets more payments right the first time also has fewer invoices sitting in a queue long enough to get paid twice by accident.

Why do duplicate payments happen, and who catches them?

Most duplicate payments are not one dramatic mistake; they are the predictable output of a few repeatable process gaps. A vendor resubmits an invoice it believes is unpaid, unaware the first copy already cleared. Two people in different departments approve the same bill because neither can see the other’s queue. An invoice gets re-entered under a slightly different reference number after a system migration, breaking the match against the original. Each of these is a control gap, not a fraud attempt, which is part of why APQC’s own guidance on the topic points toward matching automation as the fix: 69% of the organizations it surveyed had either partially or fully implemented electronic invoice-matching systems for accounts payable by the time of that benchmark, precisely because matching an incoming bill against what has already been paid is the step that catches a duplicate before the money moves.

Manual review still catches most duplicates before they go out, but it is slower and inconsistent across a large invoice queue, which is the practical argument for structured invoice records over loose PDFs and email threads. A duplicate is far easier to catch when every invoice carries a unique number and a visible payment status than when the only record is a folder of attachments.

Is duplicate payment a fraud problem or a process problem?

Mostly a process problem, though the line blurs at the edges. The overwhelming majority of duplicate payments trace back to the causes above: resubmission, siloed approvals, and broken matching after a system change, not deliberate manipulation. But the broader payments-fraud environment they sit inside is getting worse, and it shapes how much attention finance teams can spare for the quieter, unglamorous problem of accidental duplicates. The AFP’s 2026 Payments Fraud and Control Survey found that 76% of US organizations experienced attempted or actual payments fraud in 2025, with 58% hit by check fraud specifically and 74% affected by business email compromise. Only 17% of those organizations use AI tools to help combat any of it.

Figure 5: Share of US organizations affected by different categories of payments fraud in 2025. Source: AFP, 2026 Payments Fraud and Control Survey Report.

That low AI-adoption number matters for duplicate payments too, even though the AFP survey measures fraud rather than accidental duplication specifically. The same detection tooling, matching an incoming invoice against everything already paid, catches both a resubmitted invoice and a fraudulent one; a finance team that has not automated that check is exposed to both problems for the same underlying reason.

Duplicate Payment Benchmarks at a Glance

Benchmark	Figure	Source
Duplicate or erroneous disbursements, top performers	0.8%	APQC (2020)
Duplicate or erroneous disbursements, bottom performers	Over 2%	APQC (2020)
Disbursements correct on first attempt, top performers	98%	APQC, via CFO.com (2025)
Disbursements correct on first attempt, bottom performers	88%	APQC, via CFO.com (2025)
SMB invoices flagged as duplicates	1.29%	SAP Concur
Average value of one duplicate invoice	$2,034	SAP Concur
Outgoing cash flow lost to duplicate payments	Up to 1.5%	IOFM
US organizations hit by payments fraud, 2025	76%	AFP (2026)

Table 1: Duplicate payment and disbursement-accuracy benchmarks compiled from named industry surveys. Sources as listed above.

The Bottom Line

The headline number here is not dramatic on its own: 0.8% of disbursements duplicated among the best-run AP teams sounds small until it is multiplied by a year of invoice volume, and it more than doubles for teams without the controls in place. What separates a top performer from a bottom performer is not a bigger budget; it is whether every invoice has a unique reference and a visible payment status that both sides of a transaction can check before money moves twice. BillyPaid’s invoice generator auto-numbers every invoice and tracks its payment status from sent to paid, which closes the exact gap that lets a vendor resubmit, or a business itself pay, the same bill twice.

Frequently Asked Questions

How common are duplicate payments? Even top-performing accounts payable teams see 0.8% of annual disbursements come back duplicate or erroneous, according to APQC’s Open Standards Benchmarking Accounts Payable survey. Bottom-performing teams see more than double that rate, over 2% of total disbursements.

How much does the average duplicate payment cost? SAP Concur’s study of small and mid-sized business invoice data found the average duplicate invoice was worth $2,034. A typical SMB processing about 450 invoices a month sees roughly 6 flagged as duplicates, worth a combined $12,000 in monthly exposure if none were caught.

What percentage of accounts payable spend is lost to duplicate payments overall? The Institute of Finance & Management estimates that up to 1.5% of an organization’s total outgoing cash flow is lost to duplicate payments, a figure cited widely across accounts payable industry guidance, though without a specific publication year attached.

Are duplicate payments a fraud problem? Mostly not, though the two overlap. Most duplicate payments trace back to process gaps, like a vendor resubmitting an unpaid invoice or two people approving the same bill, rather than intentional fraud. Still, 76% of US organizations experienced attempted or actual payments fraud in 2025, and only 17% use AI to help catch it, per the AFP’s 2026 Payments Fraud and Control Survey.

Sources and References

1. CFO.com, Metric of the Month: Detect and Prevent Duplicate or Erroneous Payments (2020), citing APQC Open Standards Benchmarking, Accounts Payable survey.
2. CFO.com, Percentage of Error-Free Disbursements: Metric of the Month (2025), citing APQC Open Standards Benchmarking data.
3. SAP Concur, How Much Money Is Your Business Throwing Away in Duplicate Invoice Payments?, SMB invoice data study.
4. Institute of Finance & Management, Duplicate Payments: An Ounce of Prevention, a Pound of Cure.
5. Association for Financial Professionals, 2026 Payments Fraud and Control Survey Report.

Note: All figures verified as of September 2026.