Invoice 4471882 arrives in March for $2,840, clears the audit and gets paid. In May a second document arrives from the same carrier, for the same load, at the same amount, numbered 4471882R. Your duplicate check compares vendor, invoice number and value, finds no match on the number, and releases the payment.
Nothing in that second document announced itself as a copy. It was a re-bill the carrier issued after its own system rejected the first submission, and the first submission had already been paid. The control did exactly what it was built to do and the money still left.
What a standard duplicate check tests
Most ERP duplicate logic keys on vendor plus invoice number, sometimes with amount and a date window attached. That control is sound for a supplier who issues one numbered invoice per purchase order and never renumbers it. Freight billing breaks both halves of the assumption.
The invoice number belongs to the carrier's billing system, not to your shipment. A reweigh, a rejected EDI submission, a corrected accessorial, a change of billing entity or a handoff to a collections desk can each produce a fresh number for money you have already seen. The identifier that would actually settle the question, the load, travels as a PRO number, a BOL number, a load ID and a shipment reference, and your AP system treats none of those as a key.
The exposure is ordinary rather than exotic. APQC's Open Standards Benchmarking survey, reported by CFO.com, found top performers sending roughly 0.8 percent of annual disbursements out as duplicate or erroneous payments, with bottom performers at about 2 percent. That category is wider than duplicates alone, since it absorbs wrong vendor and wrong amount too, but it sets the scale. Cass Information Systems reported 8.4 million transportation invoices in the fourth quarter of 2025 at an average of $1,093 each. Freight risk accumulates through invoice count, not invoice size.
Three signals, three blind spots
A serious check runs three independent tests. Each one catches a failure the others cannot see, and each one is wrong in its own particular direction.
- Invoice number. Catches literal resubmission of the same bill, which is common enough on its own when a carrier's AR team chases an open item. It misses every case where the number changed, which is every case that matters most.
- Document checksum. A hash of the arriving file or EDI payload catches one document delivered through several channels, the routine situation where a carrier transmits EDI, emails a PDF and also uploads to your portal. It misses a re-render. Regenerate the same bill with a new timestamp in the footer and the hash moves while the charges sit still.
- Carrier plus load plus amount. This is the test that reaches the expensive case: identical money for identical work under new identifiers. It is also the only one of the three that produces false positives worth managing, because two truckloads on the same lane on the same day at the same contract rate are a normal Tuesday rather than a billing error.
None of the three is sufficient alone. Picking one and calling the control finished is the usual failure, and whichever you picked decides which duplicates you pay.
| Signal | Catches | Misses | False positive risk |
|---|---|---|---|
| Invoice number | Exact resubmission, AR follow-up copies | Re-bills, renumbered corrections, collections re-issues | Very low |
| Document checksum | Same file through EDI, email and portal | Re-rendered documents, re-keyed data, format changes | None in practice |
| Carrier, load and amount | Repeat charges for the same movement | Split bills where linehaul and accessorials arrive separately | Real, on repeating lanes and identical daily moves |
A correction is supposed to resemble a copy
EDI anticipated the problem, barely. In the X12 004010 210, element B3-08 is a two character Correction Indicator, defined as a code showing the transaction set contains information that corrects earlier information. The element is optional.
IBM's documentation for Sterling Transportation Management System shows what optional means once freight is moving. A carrier may submit only one original invoice. A second one still flagged as an original gets disregarded and logged as "Inbound Freight Invoice Ignored". To bill again the carrier has to attach a correction code: AD for an amendment, RB for a rebill. The same page notes that the resulting error notice reaches carrier users subscribed to data exchange emails, and that shippers do not receive it.
Read that from your side of the connection. A legitimate corrected bill that the carrier forgot to flag vanishes quietly, and you hear about it through a collections letter or at the next quarterly review. Strictness and leniency both carry a bill. Tighten the rule and you suppress corrections you owe; loosen it and you pay copies you do not.
The indicator only helps where the standard is in play. Much carrier billing arrives as a PDF by email or a portal upload, where nothing separates a correction from a copy except the word REVISED somewhere in the layout, if the carrier bothered.
The payment that duplicates an obligation, not a document
The worst version involves no second document at all. When a carrier factors its receivables, the factor delivers a notice of assignment. UCC section 9-406(a) is blunt about the consequence: once the account debtor has received authenticated notification that the amount is payable to the assignee, it "may not discharge the obligation by paying the assignor." Pay the carrier regardless and the factor can still collect from you. That is one movement paid twice, and not one of the three signals will raise a hand, because there is a single invoice number, a single load and a single amount. Only the payee changed.
Double brokering reaches the same place by another road. FreightWaves has reported that an unpaid carrier may pursue the shipper directly through a law firm or a collection agency, after the broker's money has gone to someone else. The Transportation Intermediaries Association covers that exposure in its white paper Safeguarding Shipments Against Freight Fraud and Double Brokering Risks.
The pattern underneath both is the same. Deduplication asks whether you have seen this document before. Cash protection asks whether this obligation has already been discharged, to the party actually entitled to receive it. Those are different questions, and only the second one is about money.
How Penny handles it
Penny resolves every arriving invoice to a load before comparing it with anything. Identifiers get normalised and matched against the shipment record, which is the step that makes the rest possible and the step most AP stacks skip, as load resolution rather than rate math turns out to be the bottleneck.
With the load established, the three signals run against a per-load ledger of what has been billed, approved and paid. A second bill for a charge already settled is held with the prior payment attached. A corrected bill that supersedes an unpaid one is recognised as a replacement rather than an addition, including when the carrier omitted the correction code. A split bill arriving in two legitimate pieces clears, because the ledger knows which charges are still open. She checks remit-to against the assignments on file at the same time, so a payment heading to the wrong party is caught before it moves, not after.
Timing is the whole advantage. Recovering a duplicate payment depends on carrier cooperation and a credit memo that may take two quarters to appear. Declining to make it depends on nothing, which is why the fourth leg of the match belongs before payment.
Where to start
Pull ninety days of paid freight invoices and group them by carrier and load reference instead of by invoice number. Look at every group that received more than one payment and classify it: a legitimate split bill, a correction you owed, or a copy you paid. The third category is your real duplicate rate, and it is almost never the number your ERP reports.
Then run a second pass on payees. List the carriers with a notice of assignment on file and compare it to where last month's payments actually went. Any mismatch is a payment you may owe again.
Book a walkthrough to see Penny run these checks against your own paid freight invoices.