X12 transaction code
X12 204 Motor Carrier Shipment Information
The X12 204 Motor Carrier Shipment Information is the name one trading partner uses for the X12 204 Motor Carrier Load Tender transaction set, used when a shipper offers a load to a carrier. The shipper or another party contracting for the transportation sends the 204 to the motor carrier that will move the shipment.
- Standard
- X12
- Code
- 204
- Partner references
- 1
At a glance
X12 204 Motor Carrier Shipment Information at a glance
What the 204 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
This page lists the partner reference that name the 204 this way. The full EDI 204 guide is on the X12 204 Motor Carrier Load Tender page.
| Document | X12 204 Motor Carrier Shipment Information |
|---|---|
| Business record | Load tender |
| Who sends it to whom | The shipper or another party contracting for the transportation sends the 204 to the motor carrier that will move the shipment. |
| When it is sent | A shipper transmits bill of lading, rating, and scheduling details to a motor carrier for a load it is arranging, typically on a trading relationship still mapped to an older X12 release. |
| Match on | Load reference, pickup and delivery stop identifiers |
| Partner references | 1 trading partner in this directory |
| Related documents | X12 990 Response to a Load Tender, X12 214 Transportation Carrier Shipment Status Message, X12 210 Motor Carrier Freight Details and Invoice |
Key segments in the X12 204 Motor Carrier Shipment Information
The business segments in the one partner document reference listed below. 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 |
|---|---|---|---|
| B2 | Beginning Segment for Shipment Information Transaction | To transmit basic data relating to shipment information. | 1 of 1 |
| B2A | Set Purpose | To allow for positive identification of transaction set purpose. | 1 of 1 |
| N9 | Reference Number | To transmit identifying numbers and descriptive information as specified by the reference number qualifier. | 1 of 1 |
| G62 | Date/Time | To specify pertinent dates and times. | 1 of 1 |
| R3 | Route Information - Motor | To specify carrier and routing sequences and details. | 1 of 1 |
| H3 | Special Handling Instructions | To specify special handling instructions in coded or free-form format. | 1 of 1 |
| H6 | Special Services | To identify forms of unitization, liability issues and special services. | 1 of 1 |
| K1 | Remarks | To transmit information in a free-form format, if necessary, for comment or special instruction. | 1 of 1 |
| N7 | Equipment Details | To identify the equipment. | 1 of 1 |
| S5 | Stop Off Details | To specify stop-off details in terms of weight, quantity and volume. | 1 of 1 |
Stacksync connects EDI documents such as the X12 204 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 204 mapping and validation
X12 204 Motor Carrier Shipment Information is used when a shipper offers a load to a carrier. Preserve load reference, pickup and delivery stop identifiers so the load tender 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 | load tender load reference, pickup and delivery stop identifiers |
|
| Update the receiving system | Processing the load tender ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the load tender 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 990 Response to a Load Tender
load-tender response: a carrier responds to a tender.
- 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 a shipper offers a load to a carrier. Name the operational owner of the load tender and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map load reference, pickup and delivery stop identifiers. 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 load tender 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 load tender processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 204 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic load tender 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 load tender without processing it twice.
Document structure
X12 204 Motor Carrier Shipment Information at the element level
The X12 204 reference contains 82 segment entries and 470 data elements; 63 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 82
- Data elements
- 470
- Mandatory elements
- 63
| Segment | Elements | Mandatory |
|---|---|---|
| B2 | 12 | 1 |
| B2A | 2 | 1 |
| MS3 | 5 | 2 |
| PLD | 4 | 1 |
| NTE | 2 | 1 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
| G61 | 5 | 2 |
| N7 | 24 | 1 |
| M7 | 5 | 1 |
| S5 | 11 | 2 |
- Shipment Method of Payment
- Transaction Set Purpose Code
- Standard Carrier Alpha Code
- Routing Sequence Code
- Quantity of Pallets Shipped
- Description
- Entity Identifier Code
- Name
Find your trading partner for X12 204
1 partner, 1 channel. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 204 Motor Carrier Shipment Information appears in this catalog
The largest groups of classified 204 catalog entries are in grocery & food.
By industry
- grocery & food 1 channel
FAQ
X12 204 Motor Carrier Shipment Information questions
What is the X12 204 Motor Carrier Shipment Information?
The X12 204 Motor Carrier Shipment Information is the name one trading partner uses for the X12 204 Motor Carrier Load Tender transaction set. Trading partners use it when a shipper offers a load to a carrier. It carries the data for the load tender, and your system matches it on load reference, pickup and delivery stop identifiers.
Who sends the X12 204 Motor Carrier Shipment Information and who receives it?
The shipper or another party contracting for the transportation sends the 204 to the motor carrier that will move the shipment. Your trading partner agreement confirms the direction and version for your account.
When is the X12 204 Motor Carrier Shipment Information sent?
A shipper transmits bill of lading, rating, and scheduling details to a motor carrier for a load it is arranging, typically on a trading relationship still mapped to an older X12 release. Your partner guide sets any deadline or schedule for the document.
What are the key segments in the X12 204 Motor Carrier Shipment Information?
The one partner document reference listed here includes B2 (Beginning Segment for Shipment Information Transaction), B2A (Set Purpose), N9 (Reference Number), G62 (Date/Time), R3 (Route Information - Motor), H3 (Special Handling Instructions). Each partner guide sets which segments and elements your account must send.
What is the difference between 204 and 990?
The 204 offers a load to a carrier. The 990 is the carrier's answer: it accepts or declines that tender.
What is the difference between 204 and 214?
The 204 tenders the load. Once the carrier has it, the 214 reports the shipment's status: pickup, in transit, delays and delivery.
What should I map for X12 204?
Start with load reference, pickup and delivery stop identifiers and the target load tender. 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 204 error handling?
Send an amended pickup appointment and retain the previous tender decision. Test a multi-stop load whose stop sequence differs from address sorting. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
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.
