When two invoices look alike, compare vendor identity, original document numbers, document type, date, currency and amount, then check which orders and receipts each covers. An equal amount or a nearly identical number is a reason to investigate, not proof of a duplicate charge. Preserve both originals, document the review and obtain the authorized decision before approving another record.
1. Separate another copy from another charge
On a construction project, a document may reach the field manager, purchasing and finance through different channels. A file forwarded twice does not necessarily represent two invoices, and two equal-value invoices do not necessarily represent the same charge. The question is whether both records represent the same payment request for the same delivery or work.
Check what has happened to each record: uploaded, under review, approved or processed by finance. “Already in the system” does not mean “paid.” If payment status is held elsewhere, ask finance to verify it rather than inferring it from a document status.
2. Gather comparison fields and retain the originals
Start with the recorded vendor identity, not only the short name on the file. Retain the invoice number exactly as printed, along with its date, document type, amount and currency. Then add the PO, project, delivery tickets or work acceptance, billed lines and covered period. A filename or upload date does not replace the invoice’s own number and date.
A separate comparison column can remove spaces or hyphens to flag similar numbers. Do not overwrite the original number: normalization can merge distinct identifiers. Confirm the relationship against the vendor’s documents. Also check whether the same vendor has more than one record in your system.
Oracle describes an additional duplicate check using vendor, invoice type, amount, currency and date together. Microsoft documents invoice-number checks that depend on workflow configuration. These examples show why the scope of a check matters; they do not establish that every duplicate is caught or that Novapro provides those features.
Further reading: Oracle: duplicate checks beyond invoice number · Microsoft: vendor invoices and approval workflows
3. Four similar-looking cases with different decisions
These are fictional examples, not customer records or results from an automated detector. Amounts are unnecessary here: document and delivery identity must be established before interpreting a financial total.
- The same number from two different vendors does not by itself identify the same invoice. Verify the vendor before comparing numbers.
- For an invoice combining receipts, check coverage line by line. Two distinct invoices can overlap for only part of a delivery.
| Case | Key evidence | Review decision |
|---|---|---|
| The same PDF arrives from the field and again from the vendor | Same vendor, original number, lines and delivery ticket | Check whether this is a resend of the existing record; retain the reference between copies. |
| Numbers AB-104 and AB104 | Original documents, vendor identity and confirmation of the number | A match after removing the hyphen warrants review, but does not authorize deletion or merging. |
| Equal charges for two deliveries | Separate receipts R21 and R22, quantities and each invoice’s coverage | Do not reject based on amount alone; verify that no receipt was billed twice. |
| A document arrives labeled “corrected” | What changed, the earlier document and what the vendor intends to replace | Obtain clarification and link the earlier version; the label alone does not determine finance’s treatment. |
4. Keep one review record with an owner and a decision
Record a review ID, both document references, the reason for suspicion, verified facts and who will fill the gaps. Give purchasing or finance clear ownership of the vendor clarification so two people do not collect conflicting explanations. The resulting decision should identify its owner, date and supporting evidence.
Suggested clarification: “We have documents ___ and ___ for PO ___. Are these a resend, a correction or separate charges? Please identify the receipts and billed lines covered by each document and explain their relationship.” This is a neutral request; similar documents do not prove intentional wrongdoing.
If it is confirmed as another copy, document which record it belongs to under company procedure. For separate charges, retain the distinguishing evidence. Finance determines the appropriate treatment of a correction, credit or payment already made. Do not erase an original or change a field receipt simply to make the discrepancy disappear.
5. Connect the review to project documents
Once you know whether the document is separate, continue matching it to the order and receipt. Use the three-way matching guide for coverage, the invoice-discrepancy guide for quantity or price differences, and supplier statement reconciliation for account movements. Related guides appear below.
Novapro brings orders and documents into the project context and supports reviewing how they match. This checklist is a suggested manual process, not a promise of automatic duplicate detection, payment blocking or an existing accounting-system integration. In a demo, review two sample documents without sensitive data and the investigation workflow your team needs.
Practical checklist
- Both originals retained with separate references and known processing status.
- Vendor identity, original number, document type, date, amount and currency checked.
- Covered orders, receipts and lines compared, including earlier billing.
- Similar numbers or amounts treated as a flag rather than an automatic decision.
- One owner coordinates clarification; response, decision and date retained.
- Correction, credit or payment handling referred to the authorized owner.
In a demo, explore how the order, receipt and invoice connect within the project context.
Request a document review demoFrequently asked questions
Does the same amount prove an invoice is a duplicate?
No. Different deliveries can have the same total. Check vendor identity, original numbers, items and covered receipts, not only the total amount.
Should I delete a file that looks like another copy?
Compare and clarify first. Preserve the original and its reference to the existing record, and document the decision under company procedure. Early deletion can remove evidence of a difference between the documents.
What if a suspected duplicate invoice has already been paid?
Verify payment with finance and attach the documents and payment references to the review. Do not infer a double payment or make an offset from similarity alone; the authorized owner determines the response after verification.
Keep reading
Three-Way Matching: Purchase Orders, Delivery Tickets and Invoices →
Invoice vs. Purchase Order Discrepancies: How to Review and Resolve Them →