To start and identify an interchange of zero or more functional groups and interchange-related control segments
Yusen Logistics X12 210 Motor Carrier Freight Details and Invoice
X12 210 (Motor Carrier Freight Details and Invoice) is the EDI transaction exchanged between Yusen Logistics (Yusen Logistics (3GYUSEN)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 16
- Loops
- 2
- X12 210
- All partners ↗
Transaction context
Where 210 Motor Carrier Freight Details and Invoice fits on Yusen Logistics (3GYUSEN)
On Yusen Logistics (3GYUSEN), the X12 210 Motor Carrier Freight Details and Invoice follows the 204 Motor Carrier Load Tender, 990 Response To A Load Tender and 214 Transportation Carrier Shipment Status Message in the Logistics cycle.
- Yusen Logistics channels
- 1 of 1
- Trading partners
- 113
- Channels
- 176
1 of Yusen Logistics's 1 channel carries 210
partners across the Stacksync network trade 210
channels network-wide carry 210
Most common alongside 210
The 210 is the motor carrier's freight bill: it itemizes linehaul and accessorial charges, weights, reference numbers, and remittance detail for a shipment the carrier has moved, and requests payment. Shippers and freight-payment providers require it so freight audit can match billed charges against the tendered shipment records before releasing payment. An individual 210 is typically sent for each shipment the carrier moves. 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 fires: The carrier completes delivery of a shipment and issues the freight bill for that PRO number to collect linehaul and accessorial charges.
Common 210 rejection causes
- Charge coding that does not match the payer's specification: each shipper defines which shipping charges are acceptable and how they must be coded, and invoices outside that specification are rejected and payment is delayed.
- Reference numbers that fail matching: the PRO number, bill of lading number, and purchase order carried in B3 and N9 must tie back to the tendered shipment, and mismatches push the invoice into manual audit.
- Duplicate or combined billing: many payers expect one 210 per shipment moved, and duplicate invoice numbers or multi-shipment documents trigger rejections or payment holds.
- Line-item charges that do not sum to the invoice totals, so the document fails balancing checks in the payer's freight audit system.
Specification summary
X12 210 Motor Carrier Freight Details and Invoice at the element level
The X12 210 specification defines 74 segments carrying 504 data elements, 91 of which are mandatory.
- Segments
- 74
- Data elements
- 504
- Mandatory elements
- 91
| 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
Full segment guideline — 16 segments 2 loops · X12 210 Motor Carrier Freight Details and Invoice
To indicate the beginning of a functional group and to provide control information
To indicate the start of a transaction set and to assign a control number
To transmit basic data relating to the carrier's invoice
To transmit identifying information as specified by the Reference Identification Qualifier
To specify pertinent dates and times
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
LX Loop Repeat: 9,999
To reference a line number in a transaction set
To specify the line item in terms of description, quantity, packaging, and marks and numbers
To specify quantity, weight, volume, and type of service for a line item including applicable \"quantity/rate-as\" data
To specify rate and charges detail relative to a line item including freight charges, advances, special charges, and entitlements
To reference details of the tariff used to arrive at applicable rates or charge
To specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
Trading partners
3+ trading partners.
And every channel covered.
We connect to every major retailer, distributor, and 3PL on the EDI network. Type to search the directory, or browse the full catalogue.
MO Motor Carrier Load Tender TR Transportation Carrier Shipment Status Message RE Response To A Load Tender
No trading partner matches your search.
Browse the full directory
Yusen Logistics Yusen Logistics (3GYUSEN) EDI 210 FAQ
Common questions about 210 Motor Carrier Freight Details and Invoice on the Yusen Logistics (3GYUSEN) channel.
What is X12 210 Motor Carrier Freight Details and Invoice?
X12 210 (Motor Carrier Freight Details and Invoice) is the EDI transaction set used to exchange motor carrier freight details and invoice data. Yusen Logistics's Yusen Logistics (3GYUSEN) channel requires it from trading partners.
Does Yusen Logistics Yusen Logistics (3GYUSEN) require 210 for trading partners?
Yes, Yusen Logistics (Yusen Logistics (3GYUSEN)) supports X12 210 Motor Carrier Freight Details and Invoice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Yusen Logistics 210 with Stacksync?
Most companies go live with Yusen Logistics 210 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 210 on Yusen Logistics (3GYUSEN)?
On Yusen Logistics (3GYUSEN), X12 210 is typically exchanged alongside 204 Motor Carrier Load Tender, 990 Response To A Load Tender, 214 Transportation Carrier Shipment Status Message. Stacksync maps each document into the same ERP or WMS workflow, so the full cycle stays in sync end to end.
Ready to automate your Yusen Logistics EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
