The motor carrier sends the 210 to the shipper or broker to bill for completed freight services.
EDI 210 - Motor Carrier Freight Details and Invoice
What is an EDI 210?
EDI 210 (Motor Carrier Freight Details and Invoice) is the electronic version of a paper freight bill or invoice. It is sent by a carrier to a shipper, consignee, or logistics provider after a shipment is completed. The 210 includes freight charges, reference numbers, service dates, and payment terms, helping organizations eliminate paper billing, speed up payments, and maintain accuracy across accounting and transportation systems.
- Primary purpose: To invoice for freight services provided by a carrier.
- Typical senders: Motor carriers and logistics providers.
- Receivers: Shippers, consignees, or third-party billing departments.
Why EDI 210 Matters in 2025
- Faster payment cycles: Automated invoicing reduces manual data entry and billing delays.
- Accuracy: Electronic validation ensures that billed charges match the original tender and shipment data.
- Compliance: Meets digital invoicing and audit requirements for shippers and carriers worldwide.
- AI-driven analytics: Structured 210 data feeds finance dashboards for cost control and performance analysis.
EDI 210 Structure & Key Segments
Typical Segment Order
ST– Transaction Set HeaderB3– Beginning Segment for Carrier’s InvoiceB3A– Invoice Type (Original, Adjustment, etc.)L11– Reference Numbers (PRO, BOL, PO, Shipment ID)N1/N3/N4– Name and Address Information (Bill To, Ship From, Ship To)G62– Dates (shipment, delivery, invoice date)L5– Line Item Description (commodity details)L0– Line Item – Weight and QuantityL1– Rate and ChargesL3– Total Weight, Charges, and DiscountsSE– Transaction Set Trailer
Core Data Elements (Pointers)
- Invoice Number:
B3-02(unique invoice identifier). - Dates:
G62(shipment, delivery, and invoice dates). - References:
L11(PO, BOL, Shipment ID). - Charges:
L1(base freight, fuel surcharge, accessorials). - Totals:
L3(net charges, discounts, weight, quantity).
Common Billing Elements
| Field | Where | Example |
|---|---|---|
| Invoice Number | B3 |
INV12345 |
| Shipment Date | G62 |
2025-10-05 |
| Freight Charge | L1 |
$1,250.00 |
| Fuel Surcharge | L1 |
$180.00 |
| Total Invoice | L3 |
$1,430.00 |
Note: Actual segments and qualifiers vary by trading partner Implementation Guide (IG).
210 in the Freight Billing Lifecycle
- Tender: 204 offers the load to the carrier.
- Acceptance: 990 confirms the booking.
- Status Updates: 214 provides transit milestones.
- Invoice Submission: 210 transmits billing and charge details.
- Reconciliation: 997 confirms receipt and validation.
Implementation Checklist (Pointers)
- Review partner billing specifications (required rates, taxes, discounts, and currencies).
- Ensure invoice numbers and shipment references match 204/214 documents.
- Validate weight, charges, and line items before submission.
- Include complete address and remittance details (
N1/N3/N4segments). - Automate 997 acknowledgments and handle error reprocessing promptly.
- Integrate with accounting or ERP systems for automatic posting and reconciliation.
- Pilot one customer or lane, then expand network-wide after approval.
Validation & Compliance
- Syntax: ISA/GS envelope,
ST/SEcontrol, terminators, and delimiters. - Semantic: Consistent identifiers, matching 204–214–210 data.
- Business rules: Check accessorial calculations, fuel surcharges, and discounts.
- Security: Secure transmission via AS2/AS4, VAN, or SFTP with encryption and digital certs.
Quick FAQ
Who sends the EDI 210?
What information does it include?
How does it help automate billing?
2025 Search & AI-Result Optimization
Search-Engine Signals
- Intent match: Targets “what is EDI 210,” “EDI 210 segments,” “freight invoice EDI,” “motor carrier billing.”
- Topical depth: Explains definition, segments, lifecycle, validation, and FAQs.
- Entity SEO: Links to related EDI pages (204, 214, 990, 997) to strengthen entity graph connections.
- UX/Core Web Vitals: Mobile-friendly, scannable sections, fast load speed, accessible tables.
AI Overviews (AEO) Best Practices
- Answer core questions early in the content (within first 120 words).
- Use exact segment names (
B3,L1,L3) for structured data extraction. - Provide clear, hierarchical headings for LLMs to map content accurately.
- Include author, date, and organization details to meet EEAT signals.
