EDI 210 Freight Invoices: A Complete Guide for Shippers

What Is EDI 210?

The EDI 210, formally known as the Motor Carrier Freight Details and Invoice, is the standard electronic data interchange transaction set used by freight carriers to send invoices to shippers. It is part of the ANSI X12 EDI standard maintained by the Accredited Standards Committee (ASC) X12.

In simpler terms: the EDI 210 is how carriers send you freight invoices electronically instead of on paper or PDF.

While paper and PDF invoices still dominate in many parts of the freight industry, EDI 210 is the backbone of automated freight billing for large shippers, 3PLs, and any organization that processes high volumes of carrier invoices. Understanding its structure is essential for anyone involved in freight payment, audit, or transportation management.

Why EDI 210 Matters

The EDI 210 exists to solve a fundamental problem: freight invoices are complex documents with dozens of data elements — carrier information, shipment details, origin and destination, weight, class, line-haul charges, fuel surcharges, accessorials, reference numbers, and more. When this information is transmitted on paper or in unstructured PDFs, extracting and validating it requires manual data entry or advanced document parsing.

EDI 210 provides a structured, machine-readable format that enables:

• •Automated invoice processing. No manual data entry needed. Invoice data flows directly into TMS, ERP, or freight payment systems.
• •Systematic audit. Because every charge is in a defined field, automated systems can validate each element against contracted rates and business rules.
• •Faster payment cycles. Automated processing reduces the time from invoice receipt to payment, improving carrier relationships.
• •Data consistency. Standardized fields eliminate ambiguity about what each charge represents.

EDI 210 Transaction Structure

An EDI 210 transaction follows a hierarchical structure. Each transaction contains header-level information about the invoice, followed by detail segments for each shipment and charge. Here is the high-level anatomy:

Envelope Segments

• •ISA (Interchange Control Header): Identifies the sender and receiver, includes date/time and control numbers
• •GS (Functional Group Header): Groups related transactions and identifies the transaction type
• •ST (Transaction Set Header): Marks the beginning of an individual 210 transaction

Header Segments

• •B3 (Beginning Segment for Carrier's Invoice): Contains the invoice number, shipment identification, payment method, delivery date, and total charges. This is the primary header segment.
• •C3 (Currency): Specifies the currency (usually USD for domestic U.S. shipments)
• •N9 (Reference Identification): Contains reference numbers — PRO number, BOL number, PO number, and other tracking identifiers
• •G62 (Date/Time): Ship date, delivery date, and other relevant dates
• •N1/N3/N4 (Name and Address): Shipper, consignee, and bill-to party names and addresses

Detail Segments

• •LX (Assigned Number): Line item sequence number — marks the beginning of each line item
• •L5 (Description, Marks, and Numbers): Commodity description and NMFC item number
• •L0 (Line Item - Quantity and Weight): Weight, quantity, pieces, and packaging type
• •L1 (Rate and Charges): The charge for this line item — rate, charge amount, and freight class
• •L4 (Measurement): Dimensions (length, width, height) for dimensional pricing
• •L7 (Tariff Reference): Tariff number and rate basis used to calculate the charge

Summary Segments

• •L3 (Total Weight and Charges): Summary of total weight, total charges, and freight rate
• •SE (Transaction Set Trailer): Marks the end of the transaction and includes a segment count
• •GE/IEA: Close the functional group and interchange envelope

Key Segments for Freight Audit

For freight audit purposes, certain EDI 210 segments are particularly important:

B3 Segment: The Invoice Header

The B3 segment contains the invoice number, net amount due, delivery date, and payment terms. This is your starting point for matching the invoice to a shipment in your system.

Audit check: Verify that the total amount in B3 matches the sum of all L1 charge segments. Discrepancies indicate a data integrity issue.

L1 Segments: Rate and Charges

Each L1 segment represents a charge line — line-haul, fuel surcharge, or accessorial. The segment includes the charge amount, rate, and charge qualifier (a code identifying the charge type).

Common charge qualifier codes:

• •400: Line-haul (base freight charge)
• •420: Fuel surcharge
• •430: Accessorial charge
• •440: Minimum charge
• •460: Discount

Audit checks:

• •Compare line-haul rate (400) against contracted rate for the origin-destination-class combination
• •Validate fuel surcharge (420) against the DOE index for the ship date
• •Verify each accessorial (430) was requested on the BOL and is priced per contract
• •Confirm discounts (460) match negotiated discount percentages

L0 Segments: Weight and Quantity

The L0 segment contains the billed weight, number of pieces, and packaging type.

Audit check: Compare billed weight against the shipper's recorded weight. Flag discrepancies above a threshold (commonly 5% or 50 lbs, whichever is greater).

L5 Segments: Commodity Description

The L5 segment includes the NMFC item number and commodity description.

Audit check: Verify that the NMFC item number corresponds to the correct freight class. Cross-reference against the NMFC tariff to catch classification errors.

Implementing EDI 210

Requirements

To receive EDI 210 invoices, you need:

1. An EDI platform or VAN (Value-Added Network). This is the communication layer that receives EDI transmissions from carriers. Options include traditional VANs (SPS Commerce, OpenText), cloud-based EDI platforms (TrueCommerce, Cleo), or direct AS2 connections.

1. An EDI translator/mapper. This converts the raw EDI format into a structure your systems can process — typically flat files, XML, or direct database inserts.

1. Integration with your TMS, ERP, or freight payment system. The translated invoice data needs to flow into whatever system manages your freight payments.

1. Trading partner setup with each carrier. Each carrier that will send EDI 210s needs to be registered as a trading partner with agreed-upon communication protocols and data standards.

Common Challenges

• •Carrier adoption varies. Large national carriers (FedEx, UPS, XPO, Old Dominion) fully support EDI 210. Smaller regional carriers may not.
• •Implementation variations. While EDI 210 is a standard, carriers implement it with variations — optional segments, custom qualifiers, and different interpretations of data elements. Testing with each carrier is essential.
• •Maintenance burden. EDI maps need updating when carriers change their implementation, when you add new carriers, or when the X12 standard is revised.

EDI 210 vs. Other Invoice Formats

The Future: APIs and AI

EDI 210 has been the freight invoice standard since the 1980s. While it remains widely used, the industry is gradually shifting toward API-based integrations (RESTful JSON) that are easier to implement, more flexible, and do not require VANs or specialized translation software.

At the same time, AI-powered document parsing has made the invoice format less important. Modern vision models can extract structured data from PDFs, scanned documents, and even photographs with accuracy comparable to EDI parsing. This means shippers no longer need to wait for every carrier to support EDI or API integration — they can upload invoices in whatever format the carrier provides and still get automated, structured data extraction.

How Overcharge.ai Handles All Invoice Formats

Overcharge.ai is designed to work with invoices in any format:

• •PDF invoices: Our vision AI extracts every line item, charge code, surcharge, and reference number from carrier PDFs — including scanned and photographed documents.
• •CSV files: Upload bulk invoice data exported from your TMS, carrier portal, or ERP system.
• •EDI 210: EDI integration is on our near-term roadmap, enabling direct carrier connections for fully automated invoice ingestion.

Regardless of the input format, the output is the same: structured invoice data, automated audit against your contracted rates, and flagged overcharges ready for dispute.

The format your carriers use should never be a barrier to freight audit. [Start your free trial](https://www.overcharge.ai/sign-up) and upload invoices in whatever format you have — PDF, CSV, or exported spreadsheets. Our AI handles the rest.