Financial control guide
How to run a duplicate-invoice audit from the files you already have
Duplicate invoices are easy to suspect and easy to misclassify. A reliable review starts with the source rows, then checks vendor, invoice number, date, amount, currency and payment status before anyone calls a payment a loss.
Why this review matters
A duplicate-invoice review is valuable because it turns a vague concern into a small, reviewable queue. The purpose is not to label every matching row as fraud; it is to surface the combinations that deserve a human check before payment or reconciliation is closed.
Signals to review
- The same vendor and invoice number appear more than once.
- Two rows share a vendor, amount and nearby invoice date but use different references.
- Credit notes, reversals or payments are missing from an otherwise matching pair.
- The same invoice appears in more than one file, period or payment run.
- Currency, tax, rounding or split-payment differences explain part of the apparent match.
A conservative workflow
- Start with a payment or accounts-payable export that contains vendor, reference, date and amount fields.
- Group possible matches conservatively instead of deleting or netting rows automatically.
- Open the source evidence for each candidate and check payment status, credit notes and approval context.
- Assign a control owner and record whether the candidate is supported, not supported or unclear.
- Repeat the review on the next period to see whether the same control weakness is recurring.
Questions before you act
- Do the matching rows refer to the same legal entity and currency?
- Was one row a credit note, reversal, split payment or correction?
- Is there a payment reference or approval trail for each row?
- Can the vendor confirm which invoice is valid?
Important limitation: A matching row is a review signal, not proof of a duplicate payment. Confirm the underlying documents and payment records before changing a ledger or claiming recovered cash.