Duplicate Payment

A duplicate payment means a company has paid a supplier twice for one obligation, and it can occur even when the accounting system has duplicate-invoice checks. Two invoices may have slightly different numbers, or the same bill may be paid by card and bank transfer, so the business needs a way to identify the underlying obligation, not just identical text.

The Washington State Auditor's Office describes controls for preventing vendor double payments, and SAP's documentation shows how software can flag duplicate supplier invoices. These sources illustrate useful controls, but no automated rule can decide every case, and human review remains important for near-matches and legitimate repeat charges.

Start with invoice capture by giving each supplier invoice one intake route or a single queue that recognises repeat submissions. Staff should label a forwarded copy as already received, since a supplier sending an overdue reminder is not issuing a second bill, and should avoid creating a new payable whenever a PDF reappears.

Match supplier identity, invoice number, date and amount, normalising harmless differences such as spaces or punctuation, but do not assume every same amount is a duplicate, because monthly rent can recur at the same value and partial payments can share references. Supplier master records can add confusion, since a vendor may appear under two spellings or entities, or an old account may remain active after a merger, so check the purchase order and goods receipt when in doubt.

Verify legal identity and bank details through trusted channels, because a fake vendor record can also be a fraud route and merging records should be controlled and logged. Payment scheduling needs visibility, because if one team starts a bank transfer while another uses a company card the system may not see both immediately.

Reconcile card, bank and accounts-payable records before paying an urgent "overdue" invoice, and mark invoices as committed to a payment run, not only after the bank statement arrives. Segregate preparation and approval where practical so the approver sees the invoice, prior payments and beneficiary details, because a second signature that checks only the amount will not catch an invoice paid yesterday.

Configure warnings for same supplier, amount and close dates, then investigate rather than automatically block all repeats. Suppose an invoice for $10,000 is paid on Monday and again on Wednesday; the duplicate cash outflow is $10,000, not $20,000.

The first payment settled the liability, and the second creates a recovery claim or supplier credit if confirmed, with the accounting treatment depending on whether reimbursement is probable under the relevant framework. When a possible duplicate is found, trace both payments to bank statements and remittance references, contact the supplier through a known route and ask for its ledger, keeping notes of who confirmed what and when, because a supplier may have applied one transfer to a different valid invoice.

A recovery can be a cash refund or credit against future purchases, so verify that any credit is actually applied and does not expire unnoticed, and if the supplier disputes the case, retain invoice and payment evidence and do not net unrelated invoices without checking contractual rights. Measure preventable duplication by tracking confirmed duplicate count and value, root cause and time to recover, reconcile supplier statements periodically and investigate old credit balances, since unclaimed overpayments can remain hidden for years, and treat a suspicious look-alike invoice as a prompt for a fraud check before any money moves.