ANSI X12 transaction set 210
Connect ANSI X12 210 freight invoices with UPS, FedEx Freight and your ERP, WMS or accounting system.
Tirnav helps logistics and finance teams automate EDI 210 workflows with partner-specific mapping, testing and exception handling. Receive carrier invoices and map billing references, shipment details and charges into your ERP or accounting system.
Message overview
EDI 210 is the ANSI X12 Motor Carrier Freight Details and Invoice Transaction Set. A carrier uses it to send freight charges and invoice details to a shipper or payer for billing review and reconciliation.
Typical message flow
Related carrier messages
Implementation workflow
Review the carrier implementation guide, X12 version and business requirements for EDI 210.
Agree connectivity, sender and receiver identifiers, and test data with the trading partner.
Receive carrier invoices and map billing references, shipment details and charges into your ERP or accounting system.
Validate required fields, qualifiers, references and business rules against the agreed implementation guide.
Test accepted and rejected messages, duplicate handling and acknowledgement requirements.
Launch with transaction monitoring, actionable alerts and controlled reprocessing.
X12 reference
Segment requirements vary by trading partner and implementation guide. These are common examples, not a universal requirement list.
| Segment | Business meaning | Implementation notes |
|---|---|---|
| ISA / GS | Control headers | Identify the interchange sender, receiver and functional group using the agreed partner identifiers. |
| ST / SE | Transaction envelope | Identify the 210 transaction set and validate its control number and segment count. |
| B3 | Beginning segment | Identifies the freight invoice, shipment reference, invoice date, payment terms and transaction purpose. |
| C2 | Administrative information | Provides additional shipment, carrier and freight-related administrative information when required. |
| N1 / N2 / N3 / N4 | Party and location | Identifies parties and locations such as carrier, shipper, consignee, bill-to and other transportation parties. |
| G62 | Date and time | Communicates pickup, delivery, invoice and other transportation-related dates and times. |
| L11 | Reference information | Carries bill of lading, purchase order, shipment, PRO, booking and other reference numbers. |
| MS3 | Interline information | Identifies participating carriers and transportation responsibilities when interline movement is involved. |
| L5 | Commodity information | Identifies commodities being transported and provides shipment-level commodity descriptions. |
| L0 | Line-item details | Communicates shipment quantities, packaging, weights and units of measure used for freight calculation. |
| L1 | Freight charges | Provides freight rates, charges, allowances, accessorial charges and other transportation billing details. |
| L3 | Invoice totals | Provides shipment-level totals including weight, quantity, freight charges and the total invoice amount. |
| SE / GE / IEA | Control trailers | Close the transaction, functional group and interchange with control counts and matching references. |
Mapping and operations
Tirnav transforms the partner message into the format required by your ERP, WMS, OMS, 3PL or custom application while applying partner-specific business rules.
Exception handling
Detect rejected, malformed or incomplete messages.
Diagnose source data, mapping or business-rule failures.
Resolve the issue with the right owner and correction.
Reprocess safely while preserving transaction history.
Trading partners
Related transaction sets
EDI 210 is the ANSI X12 Motor Carrier Freight Details and Invoice transaction set. Carriers use it to communicate freight charges, shipment details and invoice information to shippers or other responsible parties.
An EDI 210 can include freight invoice details, shipment references, carrier information, dates, commodities, quantities, weights, rates, accessorial charges and total freight charges, depending on the trading partner's implementation guide.
Tirnav receives the carrier's EDI 210, validates and maps the invoice data, and transforms it into the format required by your ERP, accounting or transportation system for processing and reconciliation.
EDI 210 is specifically designed for motor carrier freight details and invoicing, while EDI 810 is a general-purpose invoice transaction. The appropriate transaction depends on the trading partner and business process.
Yes, EDI 210 can be used for motor carrier freight billing with supported carrier implementations. Tirnav can map carrier-specific EDI 210 requirements and integrate the resulting invoice data with your ERP or accounting system.
Implementation typically requires the carrier's implementation guide, X12 version, sample EDI files, connectivity details, required business rules and destination-system field mappings. Testing validates the complete invoice flow before production.
Yes. EDI 210 data can be integrated with shipment, purchase order or contract information to validate freight charges and identify discrepancies before posting invoices to the ERP or accounting system.
Tirnav validates incoming EDI 210 transactions and identifies issues such as missing references, invalid data, mapping errors or charge discrepancies. Failed transactions can be reviewed, corrected and reprocessed.
Contact the FedEx Freight EDI team at [email protected] for invoice transmission requirements. Tirnav can map the agreed EDI 210 format to your ERP or accounting workflow and test reconciliation and exception handling.
Explore our latest thoughts on technology and business.
Learn how automotive EDI helps Indian OEMs and suppliers automate forecasts, purchase orders, ASN, invoices, ERP integration and supplier collaboration.
A practical plan to convert UB-04 claim data into HIPAA-compliant X12 837I, submit to a clearinghouse or payer, and track 999/277CA acknowledgments - with realistic timeline and cost.
Confused about how to start with EDI? We break down the three paths: SaaS Fulfilment Portals (like SPS Commerce Web), Integrated EDI (ERP Automation), and building your own In-House system.
Skip the backlog. Connect directly with our architects to discuss your business goals, technical challenges, and digital transformation roadmap.