To start and identify an interchange of zero or more functional groups and interchange-related control segments
Burlington Northern Santa Fe Railway (BNSF) X12 410 Rail Carrier Freight Details and Invoice
X12 410 (Rail Carrier Freight Details and Invoice) 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
- 26
- Loops
- 4
- X12 410
- All partners ↗
Transaction context
Where 410 Rail Carrier Freight Details and Invoice fits on Burlington Northern Santa Fe Railway (BNSF)
- Burlington Northern Santa Fe Railway (BNSF) channels
- 1 of 1
- Trading partners
- 4
- Channels
- 4
1 of Burlington Northern Santa Fe Railway (BNSF)'s 1 channel carries 410
partners across the Stacksync network trade 410
channels network-wide carry 410
Most common alongside 410
The X12 410 carries a rail carrier's freight invoice: the detailed charges associated with a specific rail movement, including waybill references, equipment, origin and destination stations, line-item weights, rates, and total charges. Freight payers require it to audit rail charges against the governing price authority and to feed freight payment systems without rekeying paper invoices. A rail carrier sends the 410 to the freight payer, which may be the shipper, the consignee, or a third party responsible for the charges.
When it fires: A rail movement is completed or reaches a billing milestone and the carrier rates the waybill and issues the invoice to the freight payer.
Common 410 rejection causes
- Charges that do not match the price authority or contract rate governing the shipment trigger freight audit disputes and delayed payment.
- Missing or incorrect waybill and equipment references (N8 and N7 segments) prevent the payer from tying the invoice to a specific rail movement.
- Invoice totals in the L3 segment that do not reconcile with the LX line-item charges fail validation in the payer's freight payment system.
- Duplicate transmissions of the same invoice create double-payment risk and manual reconciliation work for the freight payer.
Specification summary
X12 410 Rail Carrier Freight Details and Invoice at the element level
The X12 410 specification defines 32 segments carrying 224 data elements, 55 of which are mandatory.
- Segments
- 32
- Data elements
- 224
- Mandatory elements
- 55
| Segment | Elements | Mandatory |
|---|---|---|
| B3B | 11 | 6 |
| N9 | 4 | 1 |
| N7 | 21 | 1 |
| VC | 6 | 1 |
| M7 | 4 | 1 |
| M12 | 10 | 1 |
| N8 | 2 | 2 |
| F9 | 4 | 2 |
| D9 | 4 | 2 |
| N1 | 6 | 1 |
| N2 | 2 | 1 |
| N3 | 2 | 1 |
Key identifiers in 410
- Invoice Number
- Shipment Method of Payment
- Date
- Net Amount Due
- Standard Carrier Alpha Code
- Transportation Method/Type Code
- Reference Identification Qualifier
- Equipment Number
Full segment guideline — 26 segments 4 loops · X12 410 Rail Carrier Freight Details and Invoice
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 identifying information as specified by the Reference Identification Qualifier
To identify specific flight or voyage information for multimodal shipments
To transmit information in a free-form format, if necessary, for comment or special instruction
N7 Loop Repeat: 500
To identify the equipment
To define motor vehicle identification and logistics
To record seal numbers used and the organization that applied the seals
To transmit in-bond information
To identify the waybill and to specify the equipment used and the destination details
To identify the rail origin of the shipment
To identify the rail destination of the shipment
N1 Loop Repeat: 10
To identify a party by type of organization, name, and code
To specify the location of the named party
To specify the geographic place of the named party
To specify carrier and routing sequences and details
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
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 communicate basis of pricing, such as contract number, quote number, or tariff number
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 410 FAQ
Common questions about 410 Rail Carrier Freight Details and Invoice on the Burlington Northern Santa Fe Railway (BNSF) channel.
What is X12 410 Rail Carrier Freight Details and Invoice?
X12 410 (Rail Carrier Freight Details and Invoice) is the EDI transaction set used to exchange rail carrier freight details and invoice 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 410 for trading partners?
Yes, Burlington Northern Santa Fe Railway (BNSF) (Burlington Northern Santa Fe Railway (BNSF)) supports X12 410 Rail Carrier Freight Details and Invoice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Burlington Northern Santa Fe Railway (BNSF) 410 with Stacksync?
Most companies go live with Burlington Northern Santa Fe Railway (BNSF) 410 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.
Which documents accompany 410 on Burlington Northern Santa Fe Railway (BNSF)?
On Burlington Northern Santa Fe Railway (BNSF), X12 410 is typically exchanged alongside 404 Rail Carrier Shipment Information, 322 Terminal Operations And Intermodal Ramp Activity. 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.
