Who sends it
Sent by the carrier to the party responsible for payment — the shipper, the broker, or a third-party payer named on the bill of lading. It is an outbound message from the carrier’s point of view.
When it fires
After delivery, once the proof of delivery is in hand. The 210 replaces a mailed or emailed invoice and is what starts the payer’s pay cycle.
What it carries
- The invoice number, date, and the shipment and load references from the 204.
- Bill-to party and payment terms.
- Line items — linehaul, fuel surcharge, and each accessorial (detention, layover, stop-offs, lumper) with amounts.
- Total charges and the currency.
- Weight, distance, and equipment used, where the partner requires them for audit.
Where it breaks
- Charges that do not match the rate confirmation or the partner’s contracted rate, which route the invoice to a dispute queue instead of payment.
- A missing or unreferenced accessorial — billed without the supporting documentation the partner requires, so it is short-paid.
- An invoice sent before the POD is available, which the partner holds until the document arrives.
How Trailflow handles it
Trailflow EDI (beta) generates the 210 from the completed load, so the linehaul and the accessorials that were tracked in dispatch carry onto the invoice without re-entry.
See Trailflow EDI for the product. It is in beta; supported behavior may change.