Recovery playbooks · Duplicate payments

Duplicate payments from invoice numbers keyed differently

The same supplier invoice entered twice with the number written differently, such as INV-01043 and 1043, passes an exact-match duplicate check and is paid twice.

In short

  • Prefixes (INV, IN, #), leading zeros, spaces, dashes and slashes are the usual differences.
  • Character confusions such as O and 0, I and 1, or S and 5 come from scanning and hand keying.
  • Comparing numbers after stripping prefixes, punctuation and leading zeros, within the same vendor and a similar amount, finds most of them.
  • The second payment often goes out weeks later, when a reminder or copy arrives.
  • Agreeing one keying rule for invoice numbers, and enforcing it at entry, removes most of the cause.

How it happens

A packaging supplier emails an invoice numbered INV-01043. An AP clerk keys it into the vendor record. Weeks later, a reminder arrives with the same invoice shown as 1043. Another clerk treats it as a new invoice because the characters do not match, and the payment run releases a second payment. The exact-match duplicate check compares the two strings, sees INV-01043 and 1043 as different, and lets the second entry through.

The differences are usually ordinary formatting. Prefixes such as INV, IN or #, leading zeros, spaces, dashes and slashes are the common variations. A services supplier's portal might display #1043 while the paper copy reads INV-01043. A scanned copy of INV 01043 can be read as INV O1043, and hand keying produces the same confusions between O and 0, I and 1, or S and 5. None of these look like a duplicate to an exact-match check, but they are the same underlying invoice number.

The second payment often goes out weeks later, when a reminder or copy arrives. By then the first payment has cleared, the original entry may be closed, and the reminder looks like an open item. The clerk has no reason to search paid history for a number that looks new. A single keying rule for invoice numbers, enforced at entry, removes most of the cause.

Finding it in your payment history

Start with the payment history rather than the invoice register. Compare payment lines within the same vendor after stripping prefixes, punctuation and leading zeros. INV-01043 and 1043 both reduce to 1043. Then look for payments to the same vendor, with a similar amount, on separate payment dates or in separate runs. That short list is where formatting duplicates appear.

Do not rely on an exact-match duplicate report alone. Build a working list of candidates using the normalized number, the vendor and a similar amount, and include payments made weeks apart. Check the vendor record, the remittance advice and the payment reference for each candidate. If a reminder or copy triggered a second payment, the paid history will show the same normalized number under different original strings.

Character confusions need a second look. O and 0, I and 1, or S and 5 can turn one invoice into two plausible records. Normalize carefully and keep the original strings visible during review so you can see what changed. A person should compare the invoice copy, the purchase order or receipt, and the vendor statement before treating a pair as a duplicate; over-normalizing can merge genuinely different invoices.

Prioritize suppliers whose invoices arrive by several routes, such as email, portal and paper, and those with recurring charges that are keyed by hand. Those are the places where a prefix, a leading zero or a scanned character is most likely to create a second entry.

Getting the money back

Once you confirm a duplicate, contact the supplier with the invoice copy, each payment date and each payment reference. Ask the supplier to confirm the duplicate in writing and to issue either a refund or a credit. Keep the message factual and attach the evidence that lets the supplier trace the receipts on their side.

If the supplier offers a credit, apply it to a specific open invoice and record it against the vendor so it is not lost. If the supplier offers a refund, reconcile it against both payment records so the same duplicate is not credited and refunded. When a supplier proposes offsetting the duplicate against future invoices, check the contract terms; whether offset is available and how it is treated depend on the contract, the jurisdiction and advice from an adviser.

If the supplier says the second payment was not received, obtain a payment trace from your bank and provide it to the supplier. Escalate through the procurement owner or the relationship owner if the supplier does not respond. Keep the correspondence and the corrected vendor statement with the payment records. Do not close the item as resolved until the cash or credit is actually received and matched.

Stopping the next one

Agree one keying rule for invoice numbers and enforce it at entry. For example, strip prefixes, punctuation and leading zeros for the matching key, and record the supplier's original string alongside it. The rule must be the same for email invoices, portal downloads, paper copies and scanned images. A rule that exists only in a procedure document will not stop a clerk who is keying a reminder under time pressure.

At entry, compare the normalized number with the vendor's open and paid records before the invoice is released. Exact matching is not enough when INV-01043 and 1043 can both exist. Require a second person to review new invoices from suppliers with recurring charges or multiple submission routes. Treat every reminder, copy or statement line as a possible duplicate until paid history has been checked.

Train clerks on the character confusions that come from scanning and hand keying: O and 0, I and 1, S and 5. Ask suppliers to quote the purchase order and invoice number consistently, and correct the vendor record when a supplier changes how it displays numbers. Review duplicate candidates regularly and fix the entry rule when the same formatting difference keeps appearing. The aim is fewer candidates and cleaner payment history, not a promise that every duplicate will be caught.

Questions

Why did our duplicate payment check miss INV-01043 and 1043?

An exact-match check compares the characters as keyed, so INV-01043 and 1043 look different even though they are the same invoice number. Strip prefixes, punctuation and leading zeros before comparing, then review payments within the same vendor and a similar amount.

What is the quickest way to find invoice numbers keyed differently?

Compare payment history within each vendor after removing prefixes such as INV, IN or #, plus spaces, dashes, slashes and leading zeros. Focus on candidates with a similar amount and separate payment dates, then check the invoice copy and vendor statement before confirming a duplicate.

The supplier received two payments. Should we ask for a refund or a credit?

Either can work if the supplier confirms the duplicate in writing. A credit must be applied to a specific open invoice and recorded against the vendor; a refund must be reconciled against both payments. Offset terms depend on the contract and jurisdiction, so take advice where needed.

How should we key invoice numbers to prevent duplicates?

Use one rule at entry: strip prefixes, punctuation and leading zeros for the matching key, and keep the supplier's original string alongside it. Enforce that rule for email, portal, paper and scanned invoices, and check every reminder or copy against paid history before releasing payment.

Updated Nov 7, 2026. Figures on this page are calculated by ERPSav from the definitions shown. The explanatory text is drafted with AI from those figures and checked automatically before it is published. General information only, not legal, tax or financial advice.