FINANCE OPERATIONS / PRACTICAL GUIDE
How to Find Duplicate Invoices and Supplier Cost Discrepancies
A clear review process helps small and midsize finance and procurement teams spot possible duplicate invoices, compare billed costs with agreed terms, and verify every signal before anyone takes action.
An invoice that looks familiar is not automatically a duplicate, and a difference from a purchase order is not automatically an overcharge. The useful question is whether the records describe the same obligation and whether the amount billed is supported by the terms and source documents that apply.
Start with a defined review population
Choose the period and invoice records you are reviewing before comparing amounts. Keep the supplier or vendor name, invoice reference, invoice date, currency, total, purchase order (PO) or contract reference, and source-row identifier together. A stable identifier makes it easier to return to the original record without changing its source values.
Standardise the format used for comparison—such as spacing, capitalisation, date format and currency code—while retaining the original value alongside it. Separate invoices from credit notes, reversals and corrected reissues. They may share details with a payable invoice while representing a different event.
Screen for possible duplicates using several identifiers
Begin with the supplier or vendor identity and invoice number or reference. Then compare the invoice date, currency, total, PO reference and available line details. Exact matches are useful clues; near matches can reveal a changed prefix, a typing difference or a supplier name entered in a different format.
Do not treat a shared amount as proof. Recurring services, staged deliveries, instalments and repeated monthly charges can legitimately have similar totals. A second record with the same supplier and date can also be a correction, a credit note or a reissued invoice. Check the invoice reference and the surrounding record history before labelling it a duplicate.
When an invoice reference is missing or inconsistent, use a combination of fields to build a candidate match: supplier identity, date range, currency, amount, PO reference and line descriptions. Keep the match as a review signal until the source documents confirm what happened.
Compare the invoice with the purchase order and contract
Match at line level when the records support it. An overall total can conceal an extra quantity, a changed unit rate or a discount that was not applied. Compare the invoice with the approved PO, contract and any authorised amendments that were in force for the work.
- Quantity and unit: confirm the billed quantity, unit of measure and accepted delivery or service quantity against the order and receiving record.
- Rate and currency: compare each unit rate with the applicable PO or contract rate, using the same currency and billing basis.
- Discounts and credits: check the agreed discount terms, the amount applied and any credit note or adjustment that belongs to the invoice.
- Additional charges: review freight, service fees, tax or VAT, and other charges against the invoice detail and the terms that authorise them.
- Authorisation: confirm that the invoice refers to the right PO, contract or approved change, and that the version is the one applicable to the billed period.
Treat a discrepancy as a question to resolve
A difference can have a valid explanation: an approved scope change, a partial shipment, a different tax treatment, a credit already issued, or a timing difference between records. Write down which fields differ and which source would resolve the question. Avoid describing a signal as an error until the relevant documents and approvals agree.
Hypothetical example
Hypothetical example only
A small business imports expense records for a review period and sees two rows with the same supplier, invoice reference, date, currency and total. The rows are a possible duplicate, not a confirmed error. A finance reviewer checks the original invoice, the related PO, any credit-note history and the payment record in the business’s source systems. The reviewer finds that one row is a voided re-entry and records the decision without treating it as another payable invoice.
This scenario is fictional, is not a MarginLeak customer case, and makes no claim about savings or recovered amounts. The conclusion comes from a person checking source records, not from the matching signal alone.
Verify every signal against source documents
Before correcting, disputing or paying an invoice, compare the candidate record with the supplier’s original invoice, the PO, the current contract and approved amendments. Check receiving or service-acceptance evidence, approval history, credit notes and payment status in the systems your organisation already uses. If a document and a data row disagree, resolve which version is authoritative and retain the reason for the decision.
A filename or stored document is not the same as verified evidence. Open the source and confirm the supplier, reference, billed period, line items and terms yourself. Keep the reviewer, decision, date and source references with the review record so a colleague can follow the reasoning later.
Make the review repeatable
Give each candidate a clear review status, such as confirmed duplicate, supported variance or more information needed. Record the fields that triggered the review, the PO or contract version checked, the source documents consulted and the person who made the decision. That creates a practical hand-off between accounts payable, finance and procurement without turning an unverified alert into a finding.
Where MarginLeak fits
MarginLeak analyses expense records imported from CSV or XLSX files within saved comparisons. It can surface possible duplicate records and differences involving authorisations, rates, quantities and discounts, with evidence linked to the records being compared. Those signals still require human verification against the relevant source documents before a conclusion is reached.
MarginLeak does not extract fields from invoice or contract PDFs and does not connect directly to accounting or procurement systems. The comparison is based on the imported records; it is not an automated confirmation that a supplier made an error.
MARGINLEAK INTELLIGENCE
Start with the records. Verify before concluding.
Explore the method already described on the MarginLeak home page.