Why one matching field is not enough
Two invoices can have the same amount without being duplicates. One invoice can also appear more than once with different image crops, file names, or OCR interpretations. A useful review process treats a potential match as evidence to investigate, not an automatic verdict.
Define what you are trying to prevent: repeated capture of the same document, duplicate approval, or duplicate accounting posting. Those events can occur at different stages and need different checks.
A review checklist
| Check | What it can reveal | What can mislead you |
|---|---|---|
| Business identity | Whether records belong to the same entity | A shared finance team |
| Supplier identity | Whether the counterparty matches | Similar trading names |
| Invoice number | A repeated document reference | OCR confusion or punctuation differences |
| Date | A likely matching transaction | Recurring monthly invoices |
| Total and currency | Matching financial values | Standard recurring charges |
| Original image | Repeated document evidence | Different photos of the same page |
| Accounting reference | A record already handed off | Missing or delayed acknowledgement |
Normalize cautiously. Removing spaces from a reference may help comparison, but stripping all meaningful characters can merge distinct documents. Retain the original extracted and reviewed values so a person can understand why a match was suggested.
Three illustrative cases
The same invoice photographed twice. The filenames differ and one image is rotated. Supplier, invoice number, date, and amount match. Compare the originals and check whether either record is already approved or posted before resolving the duplicate.
A recurring monthly charge. Supplier and amount match, but document numbers and service periods differ. Treating amount equality as a duplicate rule would block legitimate work.
A retry after an uncertain handoff. The operator did not receive confirmation from accounting. Before sending again, determine whether the destination already accepted the record. This is an integration recovery problem as well as a document matching problem.
Who should resolve a suspected duplicate?
Give the finance reviewer enough context to compare the records and an explicit path for unresolved cases. Avoid deleting the evidence just to clear a queue. Agree how the retained record, duplicate candidate, and any accounting reference will be linked in your operational process.
Track both missed duplicates and false alarms during a pilot. Excessive false alarms can teach reviewers to dismiss warnings, while a detection percentage without a defined test set tells you little.
What to ask in an Invo evaluation
GrepEye Invo preserves original invoice photos and separates staff capture from finance review and approval. Use that workflow to demonstrate how your team would investigate repeated submissions. Confirm the available duplicate checks and resolution behavior during setup; this checklist does not assert automatic detection of every duplicate pattern.
Read the Tally handoff checklist for retry and reconciliation questions, or the invoice software guide for the wider evaluation.