X12 transaction code

EDI 210 Motor Carrier Freight Details and Invoice (X12 210)

EDI 210 is the freight invoice, the X12 Motor Carrier Freight Details and Invoice transaction set, used when transport charges are ready for audit. The motor carrier sends the 210 to the shipper, the consignee, or a third-party freight audit and payment provider, depending on who pays the freight.

Standard: X12
Code: 210
Partner references: 113

Book an EDI demo ← All trading partners

At a glance

EDI 210 at a glance

What the 210 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.

X12 210 Motor Carrier Freight Details and Invoice summary
Document	X12 210 Motor Carrier Freight Details and Invoice
Business record	Freight invoice
Who sends it to whom	The motor carrier sends the 210 to the shipper, the consignee, or a third-party freight audit and payment provider, depending on who pays the freight.
When it is sent	The carrier completes delivery of a shipment and issues the freight bill for that PRO number to collect linehaul and accessorial charges.
Match on	Carrier invoice, shipment reference and charge line
Partner references	113 trading partners in this directory
Related documents	X12 204 Motor Carrier Load Tender, X12 214 Transportation Carrier Shipment Status Message

Key segments in an EDI 210

The business segments that appear in at least half of the 175 partner document references listed below, most common first. The table leaves out envelope segments (ISA, GS, ST, SE, GE, IEA). Your partner guide sets which segments and elements your account must send.

Segment	Name	Purpose	Partner references
B3	Beginning Segment for Carrier's Invoice	To transmit basic data relating to the carrier's invoice.	175 of 175
LX	Assigned Number	To reference a line number in a transaction set.	175 of 175
L1	Rate and Charges	To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements.	175 of 175
N1	Name	To identify a party by type of organization, name, and code.	170 of 175
L3	Total Weight and Charges	To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items.	170 of 175
N4	Geographic Location	To specify the geographic place of the named party.	165 of 175
N9	Reference Identification	To transmit identifying information as specified by the Reference Identification Qualifier.	162 of 175
N3	Address Information	To specify the location of the named party.	161 of 175
L0	Line Item - Quantity and Weight	To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data.	156 of 175
L7	Tariff Reference	To reference details of the tariff used to arrive at applicable rates or charge.	154 of 175

Stacksync connects EDI documents such as the X12 210 to your ERP, CRM and databases with two-way sync. Read the EDI overview, check pricing and security, or book a demo to walk through your partner guide.

Implementation guide

X12 210 mapping and validation

X12 210 Motor Carrier Freight Details and Invoice is used when transport charges are ready for audit. Preserve carrier invoice, shipment reference and charge line so the freight invoice in your business system stays connected to the original document.

Use the version and implementation guide agreed with your trading partner to confirm required fields and responses.

Map records and test the business result
Document or decision	Record and matching IDs	What to test
Match the business record	freight invoice carrier invoice, shipment reference and charge line	Define which combination of carrier invoice, shipment reference and charge line identifies one business record, its lines and any later revision.
Update the receiving system	Processing the freight invoice ID assigned by the receiving system and processing result	Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate. Test a second invoice for the same shipment and distinguish a revision from a duplicate.
Check the processing result	Processing status for the freight invoice Original document reference and matching response	Reconcile the freight invoice with the source after a timeout before sending it again. A lost response can occur after the destination has already processed the document.

How the related documents differ

Each message represents a different business event. Use shared references to connect the records while tracking each message’s outcome separately.

X12 204 Motor Carrier Load Tender
load tender: a shipper offers a load to a carrier.
X12 214 Transportation Carrier Shipment Status Message
shipment status event: the carrier reports a transport milestone or exception.

Implementation steps

Choose the starting event and owner
Decide which application acts when transport charges are ready for audit. Name the operational owner of the freight invoice and the team that resolves rejected or ambiguous messages.
Keep record IDs connected
Map carrier invoice, shipment reference and charge line. Confirm qualifiers, code lists, units and date/time meaning against the agreed X12 version and partner guide. Preserve the source reference alongside any new destination identifier.
Test failures before launch
Run the failure cases in the mapping table against realistic freight invoice data. Check how the receiving system reports a rejection and how your team corrects it without creating a duplicate.
Track every document to completion
Record transport delivery and document validation separately from successful freight invoice processing. Give unresolved errors an owner and check the receiving system before approving retries.

Go-live checklist

An approved 210 sample and the agreed version and partner guide are available.
The mapping tests pass with realistic freight invoice data.
Each submitted document can be traced through delivery, validation and processing in the receiving system.
Your team knows how to investigate and recover a rejected or timed-out freight invoice without processing it twice.

Document structure

X12 210 Motor Carrier Freight Details and Invoice at the element level

The X12 210 reference contains 74 segment entries and 504 data elements; 91 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.

Segments: 74
Data elements: 504
Mandatory elements: 91

Segments with elements marked mandatory in this reference
Segment	Elements	Mandatory
B3	14	5
C2	7	3
C3	4	1
N9	6	1
R3	2	2
K1	2	1
N1	6	1
N2	2	1
N3	2	1
N7	24	1
M7	5	1

Key identifiers in 210

Invoice Number
Shipment Method of Payment
Date
Net Amount Due
Standard Carrier Alpha Code
Bank Client Code
Identification Code Qualifier
Identification Code

Find your trading partner for X12 210

113 partners, 176 channels. Choose a channel to inspect its listed document reference and implementation context.

Catalog breakdown

Where X12 210 Motor Carrier Freight Details and Invoice appears in this catalog

The largest groups of classified 210 catalog entries are in logistics & transport, grocery & food and retail.

By industry

logistics & transport 101 channels
grocery & food 28 channels
retail 10 channels
consumer goods 9 channels
building & hardware 8 channels
electronics & technology 6 channels

By network

E2open 31 channels
MercuryGate 24 channels
Ryder 21 channels
Manhattan Associates 9 channels
BluJay 4 channels
Blue Yonder 3 channels

Partner entries with the most listed channels

FAQ

EDI 210 questions

What is an EDI 210?

EDI 210 is the freight invoice, the X12 Motor Carrier Freight Details and Invoice transaction set. Trading partners use it when transport charges are ready for audit. It carries the data for the freight invoice, and your system matches it on carrier invoice, shipment reference and charge line.

Who sends an EDI 210 and who receives it?

The motor carrier sends the 210 to the shipper, the consignee, or a third-party freight audit and payment provider, depending on who pays the freight. Your trading partner agreement confirms the direction and version for your account.

When is an EDI 210 sent?

The carrier completes delivery of a shipment and issues the freight bill for that PRO number to collect linehaul and accessorial charges. Your partner guide sets any deadline or schedule for the document.

What are the key segments in an EDI 210?

Across 175 partner document references listed here, the business segments that appear most often include B3 (Beginning Segment for Carrier's Invoice), LX (Assigned Number), L1 (Rate and Charges), N1 (Name), L3 (Total Weight and Charges), N4 (Geographic Location). Each partner guide sets which segments and elements your account must send.

What is the difference between EDI 210 and EDI 204?

The 204 tenders the load. The 210 is the carrier's freight invoice for it after delivery, with line-haul, fuel and accessorial charges.

What should I map for X12 210?

Start with carrier invoice, shipment reference and charge line and the target freight invoice. Define duplicate detection, allowed updates and response correlation before mapping individual fields. Use the partner guide to check required fields and their formats.

How should I test 210 error handling?

Separate line-haul, fuel and accessorial charges before comparing the invoice with the agreed rate. Test a second invoice for the same shipment and distinguish a revision from a duplicate. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.

Which partners list X12 210?

The directory on this page links 113 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.

Connect EDI to your business systems

See how Stacksync can fit your enterprise EDI workflow. Bring one partner guide and a sample exchange to plan the system mapping, exception handling and production rollout.

Book an EDI demo Explore the EDI platform