A duplicate payment is when a business pays the same vendor for the same goods or services more than once. It is also called a double payment. In accounts payable it usually starts with one invoice being entered twice, often under a slightly different number or vendor record, so the second payment looks legitimate when it goes out.
Nobody sets out to pay a bill twice. The second payment happens because the invoice, the vendor record or the payment method looked different enough the second time that nothing matched.
What does duplicate payment mean in accounting?
In accounting terms, a duplicate payment is an overpayment: cash left the business for an obligation that had already been settled. The US Government Accountability Office groups duplicates with other improper payments, which it describes as payments that should not have been made or were made in the wrong amount.
A duplicate is different from a vendor billing you twice, although the two are related. If the vendor sends the same charge on two invoices, that is double billing, and it only becomes a duplicate payment if you pay both. Duplicate payments are usually process errors. If you are worried about deliberate overbilling, the warning signs are covered separately in invoice fraud warning signs.
What causes duplicate payments in accounts payable?
The Washington State Auditor’s Office lists several recurring causes in its guidance on paying vendors twice, and they match what most AP teams see in practice.
The same invoice entered twice
An invoice arrives by email, gets keyed in, and then a paper copy or a “friendly reminder” arrives two weeks later and is keyed in again by someone else. If both entries use the same vendor and the same invoice number, most accounting systems will warn you. The trouble starts when one of those fields differs.
The invoice number is written differently
Your system sees these as three different invoices:
INV-10011001INV1001
The same happens with leading zeros (00458 and 458), trailing spaces, a letter O typed as a zero, or a vendor that reissues an invoice with a suffix such as INV-1001-R. Duplicate checks built into accounting software usually compare the invoice number exactly, so one stray character is enough to let the second entry through.
A resubmitted invoice or a credit memo mix-up
A vendor sends a corrected invoice to replace the original, but the original was never voided. Or a credit memo is issued against an invoice, then the corrected invoice is paid in full as well, and the credit is never applied. Both leave you paying more than you owed.
One vendor, two payment methods
The invoice is paid by check from the bank portal, and the same invoice is later paid by ACH through the AP system (or by company card). Because the payments came from different places, they never sit next to each other in one report.
Duplicate vendor records and multiple entities
If “Acme Supply” and “Acme Supply Inc.” exist as two vendor records, an invoice can be entered once under each, and a duplicate check that looks within a single vendor number will not connect them. Companies with several legal entities or locations have the same problem across books: the same invoice gets entered in two entities. Duplicate vendors in the master file are one of the most common root causes, which is why a vendor master cleanup is often the first control auditors recommend.
How do you identify duplicate payments?
Start from your paid invoice history, not from open invoices. You want every payment in a period (a quarter or a year is a reasonable first pass) with vendor, vendor ID, invoice number, invoice date, amount, payment date and payment method.
- Match on vendor, amount and date. Sort by vendor name, then amount, then invoice date. Look for rows with the same amount paid to the same vendor within a short window, say 30 or 60 days. This finds duplicates even when the invoice numbers differ.
- Normalize invoice numbers. Make a helper column that strips prefixes, spaces, dashes and leading zeros, so
INV-001001and1001both become1001. Then match on vendor plus the cleaned number. The spreadsheet formulas for this are in how to find duplicate invoices in Excel. - Match across vendor records. Group vendors by tax ID, bank account or address rather than by name. Two vendor IDs that share a bank account are probably the same vendor, and their invoices should be checked against each other.
- Match across payment methods. Combine check, ACH, wire and card payments into one list before you sort. Duplicates across methods only show up when they sit side by side.
- Reconcile vendor statements. Ask your larger vendors for a statement of account and compare it with your ledger. A credit balance on the vendor’s side usually means they received more than they billed. This is one of the few checks that can surface a duplicate you have no record of.
Here is what a typical candidate pair looks like after step 1:
| Vendor | Invoice no. | Invoice date | Amount | Paid by |
|---|---|---|---|---|
| Acme Supply | INV-2041 | Mar 4 | $1,240.00 | ACH, Mar 18 |
| Acme Supply Inc. | 2041 | Mar 4 | $1,240.00 | Check, Apr 2 |
Same amount, same date, the same number once you strip the prefix, and two vendor records. That is a strong candidate. It is still a candidate: two legitimate invoices can share a vendor, an amount and a date (monthly rent, a fixed retainer, identical shipments). Pull both invoices and check the line items before you contact anyone.
The Massachusetts Office of the Comptroller makes a similar point in its tips on duplicate payments: recurring payments of identical amounts need particular attention, and expenditure reports should be reviewed routinely by vendor, amount and invoice number. If you want to run this as part of a broader review, the accounts payable audit guide covers the rest of the scope.
How do you recover a duplicate payment?
Once a duplicate is confirmed, recovery is mostly a clear request and follow-up.
- Gather the evidence. Both invoice copies, both payment records (check number, ACH trace or remittance), dates and amounts.
- Contact the vendor’s accounts receivable team. Send a short written request that names the invoice, both payments and the amount overpaid. Most vendors have seen this before and will confirm quickly once they see the remittance details.
- Choose a credit memo or a refund. A credit memo reduces what you owe on future invoices. It is simpler for vendors you pay regularly. A refund (check or ACH back to you) is better when you buy from the vendor rarely, when the amount is large, or when the vendor account is being closed. Ask for the refund in writing if you prefer it, because many vendors default to a credit.
- Record it correctly. Post the credit memo or refund against the vendor account, and make sure a credit is actually applied to a future payment rather than sitting on the account. Unused vendor credits are easy to lose track of.
- Fix the cause. Merge the duplicate vendor record, void the second invoice entry, or correct the process that let it through, so the same pair does not come back next quarter.
Recover sooner rather than later. A vendor is more responsive about a payment from last month than one from two years ago, and a vendor that has gone out of business or changed ownership may not be able to pay you back at all.
How do you control duplicate payments?
No single control stops every duplicate. A few simple ones, used together, cut down how often they happen and make the rest easier to find.
- Keep one record per vendor. Limit who can create or edit vendor records to one or two people, check new vendors against existing tax IDs and addresses, and deactivate duplicates you find.
- Set an invoice number format for data entry. Decide whether staff type the prefix, the leading zeros and the suffixes, and write it down. Consistent entry makes your system’s own duplicate warning more useful.
- Centralize invoice entry. The Washington SAO guidance recommends keeping AP entry with a small number of trained people rather than letting each department key its own invoices.
- Pay from one place. When checks, ACH and card payments come from different systems, reconcile them together at least monthly.
- Void replaced invoices. When a vendor sends a corrected invoice, void or close the original in the same step you enter the new one.
- Apply credit memos when they arrive, and review open vendor credits during month end close.
- Review payment history on a schedule. Run the vendor, amount and date match from the section above every month or quarter.
Duplicates are only one kind of AP error. Mismatches between an invoice and what was agreed are covered in invoice discrepancy, and price changes on repeat purchases in invoice price variance.
How do you prevent duplicate invoices from being paid?
The controls above work best when duplicates are checked at the invoice stage rather than after payment. That means comparing each new invoice with the ones you already have, on more than the invoice number, while it is still in the approval queue.
In a small team this is often a person scanning the vendor’s recent history before approving. It works until volume grows, staff change, or the second copy arrives through a different inbox.
Where OverpayAlert fits
OverpayAlert is software for that comparison step. You forward invoices to a workspace email address or upload them, and each new invoice is compared with the ones already there on invoice number, vendor, amount and date, using exact, near and fuzzy matching. That lets it connect INV-2041 and 2041, or “Acme Supply” and “Acme Supply Inc.”, the way a person scanning the history would.
When it finds a close match it flags the invoice as a potential duplicate and shows both documents side by side for someone on your team to review. A flag is not a verdict and it does not block a payment: your team decides whether to pay, hold or dispute. It also flags unusual price increases from familiar vendors. On the Growth and Scale plans, results export as CSV for your accounting system, and the Scale plan adds an API. It will not find every duplicate, and it does not replace the vendor and payment controls above. What it changes is where review starts. The duplicate invoice detection page explains what gets compared, and how it works walks through the full workflow.
If you want to see what it flags on your own invoices, start a 7-day free trial.