Three duplicate patterns
Exact duplicate
The invoice number, carrier, load reference, amount, and document are the same. This is the simplest case, but it may still arrive through separate email addresses or uploads.
Altered duplicate
A suffix, spacing change, new date, or revised PDF makes the document look new while the underlying carrier, load, and amount remain the same.
Economic duplicate
Different invoice numbers request payment for the same charge or accessorial on the same load. Detecting it requires line-level history, not file hashes.
Match on multiple signals
| Signal | Useful for | Risk if used alone |
|---|---|---|
| Invoice number | Exact repeats | Easy to alter |
| Carrier + load | Economic event | One load may have valid multiple invoices |
| Amount + line items | Repeated charges | Common round amounts collide |
| Document fingerprint | Same file | Rescans and exports change the file |
| Payment status | Preventing double release | Depends on current AP data |
Treat similarity as a review signal
A probable duplicate should show both records side by side: invoice identifiers, carrier, load, dates, amounts, intake channel, and payment status. AP can then confirm whether the second submission is a duplicate, a corrected invoice, or a valid supplemental charge.
Do not reject an invoice solely because it resembles another one. Show the matching fields and preserve the reviewer’s reason.
Reduce duplicates upstream
- Route every submission into one normalized intake history.
- Use carrier and load identifiers in addition to invoice number.
- Make prior decisions visible when a corrected invoice arrives.
- Re-run duplicate checks immediately before payment release.
Related resources
Check your recent invoice history.
A free audit can surface duplicate patterns before you change your workflow.
Get a free audit