To start and identify an interchange of zero or more functional groups and interchange-related control segments
Burlington Northern Santa Fe Railway (BNSF) X12 404 Rail Carrier Shipment Information
Plan X12 404 Rail Carrier Shipment Information for Burlington Northern Santa Fe Railway (BNSF). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 51
- Loops
- 10
- X12 404
- Partner references ↗
Implementation guide
Burlington Northern Santa Fe Railway (BNSF): 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.
This document is listed for Burlington Northern Santa Fe Railway (BNSF). Confirm the version, required fields and responses that apply to your account.
| 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 |
|
The document reference includes 51 segments. Use the segment reference below to locate the relevant parts of the message. Check required fields and repetition limits in the partner guide.
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 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 Burlington Northern Santa Fe Railway (BNSF) 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.
Transaction context
Where 404 Rail Carrier Shipment Information fits on Burlington Northern Santa Fe Railway (BNSF)
- Burlington Northern Santa Fe Railway (BNSF) channels
- 1 of 1
1 of Burlington Northern Santa Fe Railway (BNSF)'s 1 channel list 404
- Trading partners
- 8
partner references list 404
- Channels
- 8
channel entries list 404
Frequently listed alongside 404
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 |
Key identifiers in 404
- 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
Segment reference — 51 segments 10 loops · X12 404 Rail Carrier Shipment Information
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 identifying numbers, dates, and other basic data relating to the transaction set
To transmit identification numbers and other basic shipment data
To transmit rail-specific shipment data
To indicate that the equipment is or is not to be released
To transmit identifying information as specified by the Reference Identification Qualifier
To identify specific flight or voyage information for multimodal shipments
To specify pertinent dates and times
N7 Loop Repeat: 500
To identify the equipment
VC Loop Repeat: 21
To define motor vehicle identification and logistics
N1 Loop Repeat: 2
To identify a party by type of organization, name, and code
To identify the rail origin of the shipment
To identify the rail destination of the shipment
To specify the location of the named party
To specify the geographic place of the named party
To identify a person or office to whom administrative communications should be directed
S1 Loop Repeat: 12
To identify a stop-off party
To specify the address of the stop-off party
To specify location details for a stop-off
To specify carrier and routing sequences and details
To specify special handling instructions in coded or free-form format
To specify mechanical protective service and ventilation instructions
LX Loop Repeat: 25
To reference a line number in a transaction set
To specify the line item in terms of description, quantity, packaging, and marks and numbers
L0 Loop Repeat: 25
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 specify the total shipment in terms of weight, volume, rates, charges, advances, and prepaid amounts applicable to one or more line items
LS Loop Repeat: 1
To indicate that the next segment begins a loop
LH1 Loop Repeat: 100
To specify the hazardous commodity identification reference number and quantity
To specify the hazardous notation and endorsement information
To specify the hazardous material shipping name and additional descriptive requirements
To transmit specific hazardous material reference numbers
To specify the name of the person certifying that the shipment complies with the regulations and/or the actual certification
This segment is used to specify a pro forma invoice and B13 Canadian Customs Export Declaration information, required by U.S. and Canadian customs
To indicate customs information
To indicate the end of the transaction set and provide the count of the transmitted segments (including the beginning (ST) and ending (SE) segments)
To record seal numbers used and the organization that applied the seals
To specify the chassis equipment details in terms of identifying numbers, weights, and ownership
To transmit in-bond information
E1 Loop Repeat: 2
To identify the party receiving the empty car
To specify the geographic place of named party receiving the empty car
To specify the routing of the empty car
REF Loop Repeat: 99
To specify identifying information
To communicate basis of pricing, such as contract number, quote number, or tariff number
To uniquely identify the variable information required by government regulation covering the transportation of hazardous material shipments
To specify the Environmental Protection Agency (EPA) information relating to shipments of hazardous material
To specify additional Transport Canada requirements covering transportation of dangerous goods in Canada
To specify the placard information required by the second government agency when shipment is to cross into another country
To indicate that the loop immediately preceding this segment is complete
Related references
Other transactions in Burlington Northern Santa Fe Railway (BNSF)
Other EDI documents listed on this channel.
Rail Carrier Freight Details And Invoice X12 410 Terminal Operations And Intermodal Ramp Activity X12 322
No references match your search.
Showing 2 of 2 references
Browse the full directoryBurlington Northern Santa Fe Railway (BNSF) EDI 404 questions
Common questions about 404 Rail Carrier Shipment Information on the Burlington Northern Santa Fe Railway (BNSF) channel.
What is X12 404 Rail Carrier Shipment Information used for?
404 is used when rail movement instructions are ready for carrier use. It carries information for the rail shipment. Match it to your business system using rail shipment reference, equipment and route.
Is 404 required for Burlington Northern Santa Fe Railway (BNSF)?
404 is listed for Burlington Northern Santa Fe Railway (BNSF). Confirm the required version and direction for your business unit and account with the partner.
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.
How does 404 relate to other EDI messages?
X12 410 Rail Carrier Freight Details And Invoice is a related document also listed on Burlington Northern Santa Fe Railway (BNSF). Match these documents through their order, shipment or invoice references. Agree which response marks each business step as complete.
Connect Burlington Northern Santa Fe Railway (BNSF) 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.
