What it means
Use several identifiers: compare supplier legal entity and bank record, invoice number after careful normalisation, invoice date, currency, amount, purchase order, goods receipt and description. Similar invoices may be valid recurring charges, and identical amounts may arise every month.
A useful check flags candidates for review rather than automatically deleting them, and the original images or documents should be kept so a reviewer can compare actual content. Look across statuses and accounts, since a duplicate may be in draft, pending approval, paid, reversed or posted to another branch.
Search all relevant supplier records where policy permits, including aliases from mergers or a supplier name change. A credit note with a similar number should not be mistaken for a second bill, and payments to a different bank account on a purported repeat invoice may raise a separate fraud concern requiring stronger verification.
Check the business event: did goods or services arrive once or twice? A second invoice for a milestone may be legitimate if it covers a separate period or deliverable.
Compare contracts, purchase orders, delivery receipts and prior correspondence, and if the supplier sent a correction, determine whether the original was cancelled or credited rather than paying both. Resolve the flag with an audit trail, marking a true duplicate as rejected or linked to the original under the approved process.
If the payment was already made twice, coordinate a supplier credit or refund and preserve bank evidence, and do not quietly net the amount against an unrelated invoice without agreement. If the flag is false, document the distinct invoice and release it promptly, and review aged flags so valid suppliers are paid.
Improve upstream controls by encouraging one submission route, requiring purchase-order references where appropriate, limiting manual supplier creation and using duplicate detection at entry and before payment. Review near misses and repeated supplier patterns.
A high number of false positives may mean the matching rules are too blunt, while a low number may mean the process misses variations in invoice numbers. For owners, duplicate-payment checks protect cash and credibility.
The best control is a combination of data matching and a person who can inspect the underlying transaction before money leaves, without turning every similar invoice into a lengthy dispute.
In practice
Real-world examples.
Example
A supplier sends invoice INV-204 by email and uploads "INV 204" through a portal; the check flags the two documents before payment.
Example
A recurring monthly rent invoice has the same amount as last month but a different service period, so the reviewer confirms it is valid.
Example
A corrected invoice replaces an earlier bill, and finance checks that the first version was cancelled before scheduling the new one.
Formula
Calculation
Potential duplicate exposure = Sum of amounts on suspected second payments still pending review
Worked example. An invented payment run flags three candidate invoices for $4,000, $6,000 and $2,000.
- Potential exposure before review = $4,000 + $6,000 + $2,000 = $12,000.
- The reviewer confirms the first is a true copy, while the other two cover separate service periods; only $4,000 is prevented as a duplicate.
If the full payment run is $500,000, the flagged exposure of $12,000 is 2.4% of the run, and the confirmed duplicate of $4,000 is 0.8%. A flag is not a proven loss. Investigate the underlying invoices before reporting savings.Case study
Seen in the real world.
This illustrative and entirely fictional example follows Coastline Events, an invented events company. A supplier emailed an invoice for venue equipment and later uploaded the same bill with a revised file name. Different staff approved each document under separate event codes. A pre-payment comparison found the same supplier, date, amount and delivery receipt despite a space in one invoice reference. Accounts payable held the second item, checked both invoice images and confirmed that only one delivery occurred.
It linked the duplicate to the valid payable and told the supplier through the established contact that one invoice remained scheduled. The team then checked other open items from the supplier and adjusted the portal so resubmissions were tied to the first record. The owner avoided an unnecessary cash outflow and a later recovery request. The control also exposed a process gap between event approvals and the central supplier ledger.
Watch out
Common mistakes.
- Searching only exact invoice numbers and missing minor formatting differences or another submission channel.
- Rejecting a valid recurring invoice because its amount matches an earlier month.
- Clearing a flag without checking the original document and goods or services behind it.
Questions
People also ask.
Is the same invoice amount enough to prove a duplicate?
No. Compare supplier, reference, date, scope and supporting receipt; recurring charges often repeat.
What if a duplicate was already paid?
Confirm the transactions, contact the verified supplier route and follow the authorised credit or refund process.
When should the check run?
At invoice entry and again before payment release, especially when several channels feed the ledger.
From the founder's library
Take it further with the book.
Build your financial confidence beyond this definition. Shihan's full-length guide, Accounting Fundamentals, takes the same plain-English approach and turns it into a complete, practical playbook for non-finance managers, business owners and students - with chapter-end quiz answers and presentation slides included.
25% off with code MMHQ25, applied at checkout. Priced in USD - checkout may show the equivalent in your local currency.
View the book and save 25%