A repeated row is not enough
Two pick fees on the same order may be correct when the order shipped in two parcels. Two storage fees with the same amount may cover different pallets or months. A recurring account fee is expected to repeat. The reference type and contract unit decide whether repetition is suspicious.
This economic-identity rule came from a concrete false-positive lesson: one order can legitimately create several shipments. See how the versioned corpus changed duplicate detection.
Within-invoice duplicate test
A narrow within-invoice check can compare two lines on the same invoice when all economically meaningful fields match:
- Charge code and raw description.
- Quantity, unit rate, amount, currency, and service date.
- Facility, service level, and normalized charge family where present.
- A shipment-unique shipment or tracking reference appropriate to the fee.
- No offsetting credit, reversal, adjustment, or distinct package identity.
candidate variance = amount of the later unexplained instanceInvented rates, quantities, references and amounts; not a customer record or provider allegation.
Two invented $7.50 lines have the same code, description, quantity, unit rate, amount, date, and Tracking: TRK-101 reference on one invoice. If no reversal, reshipment, or distinct service event exists, the second line creates a $7.50 review candidate.
An order number alone would not support the same conclusion. The $7.50 is not automatically owed, claimable, submitted, credited, or recovered.
Why the reference type matters
Reference identity must match the contract’s billing grain. A single order can have several shipments; one shipment can have several cartons; a receipt can contain many pallets; and a recurring fee may legitimately have no shipment reference at all.
| Reference | What it can establish | Limitation |
|---|---|---|
| Order number | Lines relate to one customer order | Does not exclude split shipments or reshipments |
| Shipment / tracking | Stronger identity for a per-shipment fee | May still have multiple fee components or adjustments |
| Carton / pallet | Useful for container-grain fees | Needs the contract’s unit and event context |
| Invoice line ID | Preserves row identity | A unique row ID does not make the underlying event unique |
Cross-invoice and duplicate-statement checks
Pairs across invoices require period continuity, invoice identity, and adjustment history. The same event may be carried forward after a failed payment, credited and rebilled, or legitimately posted after period close. Two copies of one statement can also enter an export without representing two ledger charges.
For those reasons, cross-invoice pairs and duplicate-statement observations remain review-only even when their visible fields match.
Six innocent explanations to exclude
- Split shipment or reshipment: one order created two shipment events.
- Per-container composition: the fee repeats per pallet, carton, bin, package, or item.
- Recurring fee: the contract bills the service on each defined period or event.
- Overlapping export: two extracts contain the same underlying source row.
- Credit and rebill: an offset and corrected charge form one adjustment sequence.
- Period-boundary lag: an event posted later than its operational date under the normal billing process.
Also check for whitespace and formatting differences, but do not treat fuzzy text similarity as economic identity. Preserve the raw rows and source coordinates so a reviewer can reopen both entries.
How Auditario treats this check
Only a narrow identical within-invoice charge tied to a shipment-unique shipment or tracking reference can be Verified-eligible in principle. Repeated order numbers, cross-invoice pairs, recurring charges, and uncertain event grains stay in review.
Auditario is prelaunch: secure document intake is not open, there are 0 certified publication cells, and $0 is presently claimable. All current duplicate candidates remain review evidence. Read the methodology, inspect the synthetic sample, and see the current product status.
Related 3PL billing checks
Rate mismatch
Compare a billed rate with the active source-backed rule.
Check the rate →Ledger continuityMissing credits
Trace promised amounts through later statements and adjustments.
Trace a credit →Review every pattern in context
Compare the evidence requirements for five recurring billing checks.