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
X12 404 (Rail Carrier Shipment Information) is the EDI transaction exchanged between Burlington Northern Santa Fe Railway (BNSF) (Burlington Northern Santa Fe Railway (BNSF)) and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.
- Segments
- 51
- Loops
- 10
- X12 404
- All partners ↗
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
- Trading partners
- 8
- Channels
- 8
1 of Burlington Northern Santa Fe Railway (BNSF)'s 1 channel carries 404
partners across the Stacksync network trade 404
channels network-wide carry 404
Most common alongside 404
The X12 404 transmits rail-carrier-specific bill of lading information to a railroad and is the initial tender of a shipment between a consignor and a rail carrier. It can serve as notification of equipment release and as the legal bill of lading. The receiving railroad uses it to create the waybill that releases the equipment, set up the revenue document, generate operating instructions, and, on interline moves, pass shipment data to the next rail carrier. 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 fires: A shipper finishes loading a railcar or intermodal unit and releases the equipment to the railroad for movement.
Common 404 rejection causes
- Missing mandatory segments or elements fail the railroad's format and alphanumeric edits; the carrier rejects the transaction on the 997 and does not process it further.
- Bill of lading data that fails the railroad's application edits is rejected or accepted with change on the 824 Application Advice, delaying waybill creation and equipment release.
- Incorrect equipment initial and number in the N7 segment prevents the railroad from matching the bill of lading to the released car or intermodal unit.
- Hazardous commodity shipments require the LH1 hazmat loop (classification, proper shipping name, emergency contact); incomplete hazmat data fails carrier validation.
Specification summary
X12 404 Rail Carrier Shipment Information at the element level
The X12 404 specification defines 117 segments carrying 755 data elements, 124 of which are mandatory.
- 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
Full segment guideline — 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
Trading partners
2+ 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.
No trading partner matches your search.
Browse the full directory
Burlington Northern Santa Fe Railway (BNSF) Burlington Northern Santa Fe Railway (BNSF) EDI 404 FAQ
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?
X12 404 (Rail Carrier Shipment Information) is the EDI transaction set used to exchange rail carrier shipment information data. Burlington Northern Santa Fe Railway (BNSF)'s Burlington Northern Santa Fe Railway (BNSF) channel requires it from trading partners.
Does Burlington Northern Santa Fe Railway (BNSF) Burlington Northern Santa Fe Railway (BNSF) require 404 for trading partners?
Yes, Burlington Northern Santa Fe Railway (BNSF) (Burlington Northern Santa Fe Railway (BNSF)) supports X12 404 Rail Carrier Shipment Information. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Burlington Northern Santa Fe Railway (BNSF) 404 with Stacksync?
Most companies go live with Burlington Northern Santa Fe Railway (BNSF) 404 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 404 on Burlington Northern Santa Fe Railway (BNSF)?
On Burlington Northern Santa Fe Railway (BNSF), X12 404 is typically exchanged alongside 322 Terminal Operations And Intermodal Ramp Activity, 410 Rail Carrier Freight Details And Invoice. 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 Burlington Northern Santa Fe Railway (BNSF) EDI?
Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.
