The EDI 210 · Motor Carrier Freight Details and Invoice is how a motor carrier asks to be paid for a load it moved. It is the last message in the freight chain — the 204 · Motor Carrier Load Tender asks, the 990 · Response to a Load Tender decides, the 214 · Transportation Carrier Shipment Status Message narrates, and the 210 bills.
That position is what makes the 210 different from an ordinary invoice. A carrier's invoice is not payable because it arrived, and it is not payable because its arithmetic is clean. It is payable when three earlier records agree with it: the rate the shipper offered and the carrier accepted, the stops and service the tender described, and the times and events the status messages reported. When those three disagree with the bill, the honest answer is not "pay it and sort it out later" — it is a dispute that reopens work the delivery was supposed to close.
What is the EDI 210 · Motor Carrier Freight Details and Invoice?
The 210 is an X12 transaction set a motor carrier sends to the party that tendered the load — a shipper, broker, or 3PL — after delivery. It carries the charge for the movement: the base linehaul, fuel surcharge, and any accessorial charges such as detention, layover, lumper, or stop-off fees, each tied to the shipment it belongs to.
Three ideas define it:
- It bills against a commitment, not a trip. The reference point is the accepted 204: the rate, equipment, origin, destination, and service level both sides agreed to when the carrier answered with a 990. Charges that were never part of that agreement need evidence, not just a line item.
- Accessorials stand or fall on the 214 record. Detention claims depend on arrival and departure times. A layover claim depends on what happened and when. The status messages the carrier sent during the trip are now the evidence for — or against — the charges on the invoice.
- One 210, one shipment's truth. A freight invoice that bundles, splits, or re-references shipments differently from how they were tendered forces the payer to reconstruct the load before they can audit it. Most "slow pay" in freight is reconstruction work, not reluctance.
A 210 is usually generated from the carrier's billing system after the proof of delivery is in hand, which is why its quality depends on how cleanly the dispatch, status, and document records were joined before billing ever started.
How is the 210 different from the 204, the 990, and the 214?
The 204 · Motor Carrier Load Tender is the offer: this load, at this rate, with these stops and requirements. It sets the price the movement was supposed to cost.
The 990 · Response to a Load Tender is the carrier's answer — accept or decline — and the moment that offered rate becomes a committed rate.
The 214 · Transportation Carrier Shipment Status Message is the narration during the trip: pickup, departure, arrival, delay, and delivery events, with the times that later justify or undermine accessorial charges.
The 210 · Motor Carrier Freight Details and Invoice is the bill that must be reconciled against all three. Tender says what was agreed, the acceptance says who committed to it, the status record says what actually happened — and the invoice is only as trustworthy as its agreement with that history.
Why do freight invoices get disputed so often?
Not because carriers bill carelessly and not because shippers pay slowly by nature. Freight invoices get disputed because the audit is a three-way match performed on records that were created by different systems, at different times, under different references — and any mismatch parks the invoice in a queue where a person has to rebuild the story of one load by hand.
That reframes what a good 210 flow is. The goal is not a prettier invoice. The goal is an invoice that arrives already attached to its evidence: the accepted tender it bills against, the status events that support its accessorials, and the delivery confirmation that proves the work finished. An invoice that audits itself gets paid. An invoice that needs archaeology waits.
Where do 210 flows usually break?
The first break is the rate mismatch. The invoice bills a different linehaul or fuel surcharge than the accepted tender carried — because the rate changed verbally, the tender was amended without a clean version, or billing worked from a quote instead of the commitment. The fix is boring and total: bill from the accepted tender record, and make a rate change produce a new agreed record, not a phone call.
The second break is the unsupported accessorial. Detention is billed, but the 214 record shows arrival and departure times that make the detention window impossible — or shows no arrival event at all. The charge may be legitimate; without the status evidence it is unpayable, and the dispute costs more than the fee. Carriers who report times carefully are, in effect, pre-filing the evidence for their own invoices.
The third break is the orphan invoice. The 210 references a shipment the payer cannot match — a tender under a different number, a load that was re-brokered, a reference typed one character differently. Like an orphan status message, an unmatched invoice is real work that cannot be processed, and it ages in a queue while both sides believe the other is at fault.
The fourth break is billing before the story is complete. The invoice arrives before the final delivery status or the proof of delivery, so the payer holds it — correctly — and the carrier reads the hold as slow payment. Sequence matters on the money side too: tender, acceptance, status, proof, then invoice, each step making the next one checkable.
The fifth break is duplicate billing of the same movement: a corrected invoice sent without clearly voiding the first, or the same load billed by both a broker and the underlying carrier. Deduplication here is the same discipline as anywhere else in integration — a correction must replace a specific earlier document, identifiably, or a payer protecting themselves will pay neither until a human sorts it out.
What should you check in a 210 flow?
Five checks keep freight billing honest:
First, three-way match by construction: does every 210 resolve automatically to its accepted 204 and its 214 history — and how large is the queue of invoices that cannot, and who owns it?
Second, accessorial evidence: for each accessorial charge, can the system point to the specific status events that justify it, with times that make the charge arithmetically possible?
Third, rate provenance: is the billed rate provably the rate from the accepted tender, with any change represented as its own agreed record rather than an edit nobody can see?
Fourth, completeness before billing: is the final delivery event and proof of delivery on file before the invoice is generated — or are holds doing that check expensively, one invoice at a time?
Fifth, correction discipline: does a corrected 210 identify exactly which invoice it replaces, so the payer never faces two live bills for one load?
A flow that runs those checks turns the 210 from an argument into a formality: the last message in the chain simply states what the earlier three already proved.
Frequently asked questions
Who sends the EDI 210 · Motor Carrier Freight Details and Invoice?
The motor carrier that moved the load sends it to the shipper, broker, or 3PL that tendered the load. It is the carrier's invoice for the linehaul, fuel surcharge, and any accessorial charges for that shipment.
What is the difference between the EDI 210 and the EDI 810 · Invoice?
The 810 is the general-purpose invoice used for goods — it bills against a purchase order for products. The 210 is specific to motor carrier freight: it bills for a transportation service against an accepted load tender, and its accessorial charges are audited against shipment status events.
Why would a valid 210 be held instead of paid?
Usually because its evidence is missing or mismatched: the billed rate differs from the accepted tender, an accessorial lacks supporting arrival or departure times, the delivery proof has not arrived, or the invoice cannot be matched to a shipment. The hold is the audit working, not failing.
How do 214 status messages affect a 210 invoice?
Directly. Detention, layover, and similar accessorials are calculated from the arrival, departure, and delay events reported in 214 messages. Gaps or contradictions in that record are the most common reason an otherwise correct accessorial charge gets disputed.
Can a carrier send more than one 210 for the same load?
A corrected invoice can replace an earlier one, but it must identify the document it replaces. Two live, unlinked invoices for the same movement look like duplicate billing to any payer's controls, and both will typically be held until the duplication is resolved.
A freight invoice is not the end of paperwork — it is the moment every earlier message gets graded. The 210 gets paid quickly when the tender it bills against is unambiguous, the status record supports its charges, and the delivery it closes is already proven. At SignalEDI, we treat the freight chain — 204 · Motor Carrier Load Tender, 990 · Response to a Load Tender, 214 · Transportation Carrier Shipment Status Message, 210 · Motor Carrier Freight Details and Invoice — as one reconciled story, because carriers get paid on the strength of the whole chain, not the last document alone. I'm Chris, founder of SignalEDI, and we build EDI that keeps those records in agreement for shippers, brokers, and the carriers hauling for them.
Top comments (0)