X12 transaction code
EDI 404 Rail Carrier Shipment Information (X12 404)
EDI 404 is the X12 Rail Carrier Shipment Information transaction set, used when rail movement instructions are ready for carrier use. The shipper (consignor) or its agent sends the 404 to the railroad that will move the equipment, either directly or through a value-added network.
- Standard
- X12
- Code
- 404
- Partner references
- 8
At a glance
EDI 404 at a glance
What the 404 carries, who sends it to whom, when it goes out, and the segments trading partners list for it.
| Document | X12 404 Rail Carrier Shipment Information |
|---|---|
| Business record | Rail shipment |
| Who sends it to whom | The shipper (consignor) or its agent sends the 404 to the railroad that will move the equipment, either directly or through a value-added network. |
| When it is sent | A shipper finishes loading a railcar or intermodal unit and releases the equipment to the railroad for movement. |
| Match on | Rail shipment reference, equipment and route |
| Partner references | 8 trading partners in this directory |
| Related documents | X12 417 Rail Carrier Waybill Interchange, X12 410 Rail Carrier Freight Details and Invoice |
Key segments in an EDI 404
The business segments that appear in at least half of the 8 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 |
|---|---|---|---|
| BX | General Shipment Information | To transmit identification numbers and other basic shipment data. | 8 of 8 |
| BNX | Rail Shipment Information | To transmit rail-specific shipment data. | 8 of 8 |
| M3 | Release | To indicate that the equipment is or is not to be released. | 8 of 8 |
| N9 | Reference Identification | To transmit identifying information as specified by the Reference Identification Qualifier. | 8 of 8 |
| N7 | Equipment Details | To identify the equipment. | 8 of 8 |
| F9 | Origin Station | To identify the rail origin of the shipment. | 8 of 8 |
| D9 | Destination Station | To identify the rail destination of the shipment. | 8 of 8 |
| N1 | Name | To identify a party by type of organization, name, and code. | 8 of 8 |
| N3 | Address Information | To specify the location of the named party. | 8 of 8 |
| N4 | Geographic Location | To specify the geographic place of the named party. | 8 of 8 |
Stacksync connects EDI documents such as the X12 404 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 404 mapping and validation
X12 404 Rail Carrier Shipment Information is used when rail movement instructions are ready for carrier use. Preserve rail shipment reference, equipment and route so the rail shipment 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 | rail shipment rail shipment reference, equipment and route |
|
| Update the receiving system | Processing the rail shipment ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the rail shipment 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 417 Rail Carrier Waybill Interchange
rail waybill interchange: rail shipment information passes between carriers.
- X12 410 Rail Carrier Freight Details and Invoice
rail-freight payable: rail transport charges are ready to reconcile.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when rail movement instructions are ready for carrier use. Name the operational owner of the rail shipment and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map rail shipment reference, equipment and route. 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 rail shipment 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 rail shipment processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 404 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic rail shipment 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 rail shipment without processing it twice.
Document structure
X12 404 Rail Carrier Shipment Information at the element level
The X12 404 reference contains 117 segment entries and 755 data elements; 124 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- Segments
- 117
- Data elements
- 755
- Mandatory elements
- 124
| Segment | Elements | Mandatory |
|---|---|---|
| ZC1 | 9 | 6 |
| BX | 12 | 3 |
| M3 | 4 | 1 |
| N9 | 6 | 1 |
| M1 | 12 | 1 |
| DTM | 4 | 1 |
| N7 | 19 | 1 |
| VC | 8 | 1 |
| N1 | 4 | 1 |
| N3 | 2 | 1 |
| M7 | 4 | 1 |
| IC | 9 | 2 |
- Equipment Number
- Transaction Reference Number
- Transaction Reference Date
- Correction Indicator Code
- Standard Carrier Alpha Code
- Transportation Method/Type Code
- Transaction Set Purpose Code
- Shipment Method of Payment Code
Find your trading partner for X12 404
8 partners, 8 channels. Choose a channel to inspect its listed document reference and implementation context.
Catalog breakdown
Where X12 404 Rail Carrier Shipment Information appears in this catalog
The largest groups of classified 404 catalog entries are in logistics & transport.
By industry
- logistics & transport 8 channels
FAQ
EDI 404 questions
What is an EDI 404?
EDI 404 is the X12 Rail Carrier Shipment Information transaction set. Trading partners use it when rail movement instructions are ready for carrier use. It carries the data for the rail shipment, and your system matches it on rail shipment reference, equipment and route.
Who sends an EDI 404 and who receives it?
The shipper (consignor) or its agent sends the 404 to the railroad that will move the equipment, either directly or through a value-added network. Your trading partner agreement confirms the direction and version for your account.
When is an EDI 404 sent?
A shipper finishes loading a railcar or intermodal unit and releases the equipment to the railroad for movement. Your partner guide sets any deadline or schedule for the document.
What are the key segments in an EDI 404?
Across 8 partner document references listed here, the business segments that appear most often include BX (General Shipment Information), BNX (Rail Shipment Information), M3 (Release), N9 (Reference Identification), N7 (Equipment Details), F9 (Origin Station). Each partner guide sets which segments and elements your account must send.
What is the difference between EDI 404 and EDI 417?
The 404 carries the rail shipment and is used when rail movement instructions are ready for carrier use. The 417 carries the rail waybill interchange and is used when rail shipment information passes between carriers.
What should I map for X12 404?
Start with rail shipment reference, equipment and route and the target rail shipment. 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 404 error handling?
Test a route involving more than one carrier and retain interchange details. Separate repeated equipment numbers across different shipment dates. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
Which partners list X12 404?
The directory on this page links 8 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.
