X12 transaction code
X12 211 Motor Carrier Bill Of Lading
X12 211 Motor Carrier Bill Of Lading: explore its business purpose, mapping identifiers, validation tests and 2 partner references across 2 listed channels.
- Standard
- X12
- Code
- 211
- Partner references
- 2
Implementation guide
X12 211 mapping and validation
X12 211 Motor Carrier Bill Of Lading is used when shipment details are ready for the carrier. Preserve bill of lading, shipment and handling-unit references so the motor-carrier bill of lading 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.
| Document or decision | Record and matching IDs | What to test |
|---|---|---|
| Match the business record | motor-carrier bill of lading bill of lading, shipment and handling-unit references |
|
| Update the receiving system | Processing the motor-carrier bill of lading ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the motor-carrier bill of lading Original document reference and matching response |
|
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.
- X12 210 Motor Carrier Freight Details And Invoice
freight invoice: transport charges are ready for audit.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when shipment details are ready for the carrier. Name the operational owner of the motor-carrier bill of lading and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map bill of lading, shipment and handling-unit references. 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 motor-carrier bill of lading 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 motor-carrier bill of lading processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 211 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic motor-carrier bill of lading 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 motor-carrier bill of lading without processing it twice.
Document structure
X12 211 Motor Carrier Bill Of Lading at the element level
The X12 211 reference contains 22 segment entries and 78 data elements; 43 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 22
- Data elements
- 78
- Mandatory elements
- 43
| Segment | Elements | Mandatory |
|---|---|---|
| BOL | 4 | 4 |
| B2A | 1 | 1 |
| K1 | 1 | 1 |
| N1 | 4 | 1 |
| N2 | 1 | 1 |
| N3 | 2 | 1 |
| G61 | 4 | 2 |
| AT1 | 1 | 1 |
| AT2 | 8 | 3 |
| MAN | 2 | 2 |
- Standard Carrier Alpha Code
- Shipment Method of Payment
- Shipment Identification Number
- Date
- Transaction Set Purpose Code
- Free-form Information
- Entity Identifier Code
- Name
Find your trading partner for X12 211
2 partners, 2 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 211 Motor Carrier Bill Of Lading appears in this catalog
The largest groups of classified 211 catalog entries are in grocery & food and automotive.
By industry
- grocery & food 1 channel
- automotive 1 channel
FAQ
X12 211 questions
What is X12 211 Motor Carrier Bill Of Lading used for?
211 is used when shipment details are ready for the carrier. It carries information for the motor-carrier bill of lading. Match it to your business system using bill of lading, shipment and handling-unit references.
Which partners list X12 211?
The directory on this page links 2 partner entries that list this message. Choose your partner and channel, then confirm which messages and versions your account requires.
What should I map for X12 211?
Start with bill of lading, shipment and handling-unit references and the target motor-carrier bill of lading. 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 211 error handling?
Reconcile package counts and weight across multiple commodity lines. Test a consignee change without silently rewriting a bill already used at pickup. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 211 relate to other EDI messages?
X12 204 Motor Carrier Load Tender; X12 214 Transportation Carrier Shipment Status Message; X12 210 Motor Carrier Freight Details And Invoice are related documents linked from this page. Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
What is the difference between 211 and 204?
211 is used when shipment details are ready for the carrier. 204 is used when a shipper offers a load to a carrier. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
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.
