Duplicate Payment

1. How does a duplicate payment happen?

A duplicate payment happens when the same underlying invoice enters the AP system twice under different identifiers: a resubmitted invoice with a new invoice number, a manual re-entry after a system timeout, or a paper invoice keyed in after the same document already arrived electronically. Each entry looks like a distinct transaction, so standard matching treats it as a distinct payment rather than a repeat of one already made.

Vendors often resend an invoice weeks after the original when a payment appears late in their own system, even though it already cleared. AP staff processing high volumes can key the resend as new.

ERP migrations and manual journal corrections add the same risk when historical invoices get re-entered under a new document number, with no link back to the original.

2. Why do existing AP controls miss it?

Three-way matching checks the invoice against the purchase order and the goods receipt to confirm a transaction is legitimate. It does not compare that invoice against every other payment already made to the same vendor, which is what catching a duplicate actually requires. A control built to stop unauthorized spend is not built to stop the same authorized spend from clearing twice.

Detecting a duplicate needs a separate pass across the full payment history, matching on vendor, amount, and date proximity rather than on PO reference. Most AP systems do not run that pass by default, and where they do, a changed invoice number is often enough to slip past a basic exact-match rule.

3. How is a duplicate payment found?

Finding a duplicate payment requires comparing every paid invoice against every other paid invoice for the same vendor, looking for matches or near-matches on amount within a set date window, even when the invoice number, PO number, or description differs. This is a full-ledger comparison, not a spot check, which is why it is usually done as a discrete recovery exercise rather than a routine AP task.

An analyst or audit tool sorts payments by vendor and amount, then reviews close matches within a short window, since a genuine second charge for a different shipment or period will usually carry a different amount or date.

The check runs across every category that generates recurring invoices: freight and 3PL, contract labor and staffing, maintenance and repair, IT and professional services, MRO and Class C consumables, and equipment rental.

4. How is duplicate payment different from an overpayment?

An overpayment is paying more than the contract or invoice amount owed on a single transaction, often traced back to a rate card violation or an unapplied rebate. A duplicate payment is paying the correct, contractually accurate amount, but doing it twice for the same underlying transaction. The dollar impact can look identical on a variance report; the root cause and the fix are different.

An overpayment fix usually means correcting a rate or a billing setup going forward. A duplicate payment fix means adding a check between invoice entry and payment release, so a second entry for a transaction already paid gets flagged before the check goes out rather than after.

5. What should a company do once a duplicate is found?

Once a duplicate payment is confirmed, the company requests a credit memo or direct refund from the vendor, documents the original and duplicate transaction, and corrects the internal process step that allowed the second entry, whether that was a manual re-key, a vendor resubmission, or a system migration artifact. Recovery and process correction are treated as two separate steps, not one.

Recovering the cash closes the specific finding. Fixing the process, such as adding a duplicate check before an invoice posts, addresses the condition that let it happen in the first place, independent of which vendor or category it showed up in.

For the wider pattern this sits inside, start with the margin drift guide.

6. Frequently Asked Questions (People Also Ask)

What is duplicate payment?

A duplicate payment is a second payment issued for a vendor obligation that was already paid, most often the same invoice paid twice under different invoice numbers, PO numbers, or entry dates. It appears in the general ledger as a normal disbursement, so it usually surfaces only through a dedicated recovery audit.

How is duplicate payment different from margin drift?

Margin drift is the gap between what a vendor contract says and what the invoice actually charges. A duplicate payment does not depend on the contract at all: it is paying the correct invoice amount twice, an AP process failure rather than a pricing or rate violation.

Why do duplicate payments happen if AP already has controls?

Standard AP controls check whether an invoice matches a purchase order and receipt. They do not always check whether that same invoice, under a different number or format, was already paid. A vendor resubmission or a manual re-entry after a system error can pass those checks a second time.

Does three-way matching prevent duplicate payments?

Three-way matching checks the invoice against the purchase order and the goods receipt. It confirms the invoice is legitimate for that transaction; it does not compare the invoice against every other payment already made to that vendor, which is what a duplicate check requires.

Can duplicate payments be recovered after the fact?

Yes. Duplicate payments are typically recovered through a credit memo from the vendor or a direct refund once identified, and identification is usually the harder part since the payment already cleared and reconciled normally.

What vendor categories are checked for duplicate payment?

A duplicate payment can occur in any category that generates recurring invoices, including freight and 3PL, contract labor and staffing, maintenance and repair, IT and professional services, MRO and Class C consumables, and equipment rental.

Is duplicate payment the same as an overpayment?

No. An overpayment is paying more than the contract or invoice amount owed on a single transaction, often from a rate or rebate error. A duplicate payment is paying the correct amount, but doing it twice for the same underlying transaction.

What data does a duplicate payment check require?

At minimum it requires the vendor name, invoice amount, invoice date, and payment date across the full AP ledger, so that near-matches on amount and vendor can be flagged even when the invoice number or description differs.