B3
Beginning segment for carrier’s invoice: invoice number, shipment identification, payment method, total charges, and dates.
EDI 210: Motor Carrier Freight Details and Invoice
A trucking carrier’s invoice for a shipment, with the freight details the charges are based on. Carrier to shipper or bill-to party. This page covers what the 210 is for, the segments you meet when you open one, the documents it travels with, where it tends to go wrong, and how it moves over AS2 into your systems on Files.com, which receives, parses, validates, and routes it as configuration.
No credit card required · 7-day free trial · Live in minutes
#1 MFT vendor in Gartner Peer Insights
Trusted by 4,000+ companies
Every protocol included
What The 210 Is For
The 210 is the freight bill. After moving a load, the carrier sends it to the party responsible for the charges, with the invoice number and date, the shipment and bill of lading references, the origin and destination, the equipment, and each charge line: the description, weight or quantity, rate, and amount, totaling to the amount due.
Shippers and their freight-audit providers match the 210 against the 204 tender and the agreed rate to catch overbilling before payment. It is the transportation counterpart of the 810, and like the 810 it is paid with an 820.
The Segments You Meet First
In document order, the segments that carry the 210's meaning. A partner's implementation guide says which are required and which fields each must hold.
N1
Parties: shipper, consignee, and bill-to.
N7
Equipment details: the trailer or container.
LX
Assigned number: begins each charge or line group.
L5
Description of the freight in that line.
L0
Line item quantity and weight.
L1
Rate and charges: the rate, the charge amount, and the charge code.
L3
Total weight and charges for the invoice.
Where It Goes Wrong
Accessorial charges the shipper never agreed to, and weights on the L0 that do not match the bill of lading. Duplicate 210s for the same shipment under different invoice numbers are common enough that freight audit exists as an industry.
The Documents It Travels With
The 210 rarely moves alone. These are the documents that precede, answer, or settle it.
204 · Motor Carrier Load Tender
Travels with this document in the same exchange.
990 · Response to a Load Tender
A carrier’s acceptance or decline of a shipper’s request to move a load.
See The 990214 · Transportation Carrier Shipment Status Message
A carrier’s status update on a shipment in transit: picked up, in transit, out for delivery, delivered.
See The 214820 · Payment Order / Remittance Advice
A payer’s notice of payment: which invoices are being paid, for how much, and how.
See The 820How The 210 Moves On Files.com
A partner sends the 210 over AS2, SFTP, or FTPS, and it lands in that partner’s inbox folder on Files.com with the transport receipt recorded. From there it is a workflow, not a project: TransformScript parses the X12 natively into the JSON, CSV, or XML your ERP or WMS reads, content validation flags a document whose contents are wrong before anything ingests it, and an automation routes the result to the system and the people who act on it.
Outbound is the mirror image. Your system exports its record, TransformScript builds the 210 the partner’s guide specifies, and the file dropped in the partner’s outbox goes out over AS2 with automatic retries until the MDN confirms delivery. Every transmission in both directions is in the audit log, and delivery monitoring alerts when a 210 that was due never arrives. The full picture is on the EDI software page.
EDI 210 Questions
What teams ask about the 210 and how it moves on Files.com.
An EDI 210 is the X12 Motor Carrier Freight Details and Invoice. A trucking carrier sends it to bill for a shipment, listing the shipment references, freight details, and each charge with its rate and amount.
Both are invoices. The 810 bills for goods sold; the 210 bills for freight moved. Both are settled with an 820.
Yes. Files.com is a standards-compliant RFC 4130 AS2 endpoint, and a 210 sent by a trading partner lands in that partner’s inbox folder with a signed MDN receipt returned to the sender. Partners who exchange over SFTP or FTPS connect to the same platform and the document lands in the same place.
Yes. TransformScript parses the X12 210 natively and writes the JSON, CSV, or XML your systems ingest, as a step in the workflow that fires when the document arrives. Outbound, the same engine builds a 210 from your system’s export and drops it in the partner’s outbox for delivery.
Exchange The 210 Without The Legacy Stack
Start the 7-day trial, turn AS2 on, and exchange certificates with your partner. The 210 lands in their folder, parses into the record your system reads, and every transmission carries a signed receipt.
No credit card required • Free for 7 days • Live in minutes