A freight invoice is a request to pay for a shipment. It is not, by itself, proof that the load, rate, or extra services match what the parties agreed. The audit starts by tying the invoice to the right shipment, then checking its charge lines against the records that support them.
A useful first pass
- Match the carrier and shipment references before comparing dollars.
- Recalculate the base charge using the rate basis in the agreement.
- Review each accessorial against its approval and event evidence.
- Keep the source page and unresolved differences attached to the exception.
What does a freight invoice audit compare?
The X12 Motor Carrier Freight Details and Invoice transaction set, known as 210, is an electronic format for motor-carrier invoice and freight-charge detail. It can carry details of charges for transportation services. The format makes a charge record more structured; it does not decide whether a billed amount is supported by a particular agreement.
That decision comes from comparing the invoice with the shipment packet and the applicable rate record. Keep the fields separate so a mismatch has a clear source:
| Check | Compare | Review signal |
|---|---|---|
| Shipment identity | Invoice, PRO or load number, bill of lading, carrier, pickup and delivery dates | A valid invoice is attached to the wrong load or carrier account. |
| Lane and rated basis | Origin, destination, equipment, weight or other contracted rating unit | The lane or quantity used for rating differs from the agreed shipment details. |
| Base charge | Rate confirmation, tariff or contract terms and the matching rated unit | The billed line cannot be reproduced from the applicable rate and basis. |
| Additional charges | Accessorial line, contract rule, approval and the event record | A charge is duplicated, unapproved, or lacks the evidence required by the parties' process. |
| Delivery record | Bill of lading and proof of delivery for the same shipment | Delivery exceptions or dates need review before a deduction or release. |
Start with the agreed rate
First confirm that the invoice belongs to the shipment being audited. A reused reference, similar lane, or same-day pickup can make a correct-looking amount land on the wrong record. Compare the carrier's identifier and shipment number with the bill of lading and the internal load record. Preserve leading zeros and distinguish a PRO number from a purchase-order number; they identify different records.
Then read the rate basis before doing the arithmetic. A flat lane rate, a weight-based charge, a mileage rate, and a minimum charge produce different comparisons. Normalize units and currency only when the contract or source document tells you how. If the input quantity is missing or unclear, mark it as unknown and route it for review instead of treating blank as zero.
For example, an invoice might show a base charge of $2,100 and a separate $150 detention line. The total of $2,250 is arithmetically sound. The audit question is whether the base line follows the agreed lane rate and whether the detention line has the approval and recorded wait event required by the agreement. The example does not make the charge valid or invalid; it shows why total-only checks miss the reason for a variance.
Review accessorials one line at a time
Fuel, detention, layover, re-delivery, stop-off, toll, and other accessorials should remain distinct from the base freight line. Names and rules vary by agreement. Compare each line with the contract's trigger, rate, unit, cap if any, and approval path, then look for the document or operational record that supports the event.
- Keep the trigger visible — record whether the line depends on a timestamp, extra stop, equipment, or another stated event.
- Check the calculation — preserve the quantity, unit rate, minimum, and any rounding used to reach the amount.
- Look for duplicate billing — compare invoice number, shipment reference, line description, amount, and corrected-invoice status.
- Route missing evidence — a charge with no supporting record is an exception for a person to resolve, not an automatic finding of fraud.
A difference may have a valid explanation: a documented change, an approved service, or an invoice correction. Keep the earlier and later values together with who approved the change and when. That lets the reviewer distinguish a contract change from a data-entry mismatch.
Keep invoice evidence distinct from shipment evidence
The bill of lading identifies the shipment and its transport instructions; a proof of delivery records what was presented and acknowledged at delivery. Neither document automatically proves every charge on the carrier invoice. A signature, for example, does not settle a disputed detention interval or explain a separate accessorial line.
For delivery shortages and damage, the proof-of-delivery dispute workflow focuses on counts, annotations, signer details, and timestamps. For the shipment itself, air waybill reconciliation compares cargo fields across transport documents; it is not an audit of the carrier's billed rate.
Similarly, a freight charge on a purchase order may reflect a separately approved commercial change. The purchase-order change-order workflow establishes that approval trail; it does not replace matching the carrier invoice to its shipment and rate record. And a fuel bill of lading is a tax document about fuel volumes and destinations, not the freight bill of lading or the carrier's invoice.
Make every exception reviewable
A useful audit result is a short explanation with evidence: the invoice line, the compared rate or event, the difference, the source page, and the next reviewer. Keep the raw value beside any normalized value, and retain the document region used for extraction. If a field is unreadable or absent, say so; do not infer the value from a nearby line.
This is the same reason invoice matching reports line-level comparisons instead of a single “matched” flag. A reviewer can correct the carrier, load number, unit, or approval record without losing how the exception was first identified.
Freight invoice review does not decide contract interpretation, liability, tax treatment, or whether a party owes a disputed amount. Apply the parties' current agreement and review policy. The document comparison narrows the question and shows which evidence is still missing.
Sources
- X12 transaction set 210: Motor Carrier Freight Details and Invoice — describes the EDI transaction's use for carrier invoices and freight-charge detail.