What Duplicate payment means, why it matters, and how finance teams control it in practice.
Paying the same supplier obligation more than once, usually because one invoice was entered twice in slightly different forms.
Exact duplicates are rare because most systems block them. Real duplicates usually differ in a small way: an invoice number with or without a leading zero or dash, a copy entered under a second supplier record, a scanned invoice and an emailed PDF of the same bill, or the same amount and date with a different reference.
Money paid twice is only recovered if someone notices, and suppliers rarely volunteer refunds. Duplicates also distort spend reporting and can hide deliberate fraud.
Test before each payment run, not only after. Compare a normalised invoice number (spaces, dashes and leading zeros removed), supplier, amount and date in several combinations, and review each match before release. A recovery check on past payments is worth running once a year.
Supplier statement to AP ledger. Finds invoices you haven't posted, credit notes still to come, price differences, duplicate postings and payments in transit, and builds the supplier reconciliation. Runs in your browser on your own computer: nothing is uploaded.
The Accounts Payable Control System runs four duplicate-invoice tests, supplier master fraud checks and a three-way match on every invoice, with a payment run release gate that blocks release while exceptions are open. Excel, no macros, one-time price.
All glossary terms · All accounts payable guides
Last updated 15 November 2026. General guidance for finance teams; check it against your own policies, systems and local rules.