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
Plan X12 410 Rail Carrier Freight Details and Invoice for Burlington Northern Santa Fe Railway (BNSF). Connect document identifiers to your business records, test exception handling and track each exchange to completion.
- Segments
- 26
- Loops
- 4
- X12 410
- Partner references ↗
Implementation guide
Burlington Northern Santa Fe Railway (BNSF): 410 mapping and validation
X12 410 Rail Carrier Freight Details and Invoice is used when rail transport charges are ready to reconcile. Preserve rail invoice, shipment reference and equipment so the rail-freight payable 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-freight payable rail invoice, shipment reference and equipment |
|
| Update the receiving system | Processing the rail-freight payable ID assigned by the receiving system and processing result |
|
| Check the processing result | Processing status for the rail-freight payable Original document reference and matching response |
|
The document reference includes 26 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 404 Rail Carrier Shipment Information
rail shipment: rail movement instructions are ready for carrier use.
Implementation steps
-
Choose the starting event and owner
Decide which application acts when rail transport charges are ready to reconcile. Name the operational owner of the rail-freight payable and the team that resolves rejected or ambiguous messages.
-
Keep record IDs connected
Map rail invoice, shipment reference and equipment. 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-freight payable 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-freight payable processing. Give unresolved errors an owner and check the receiving system before approving retries.
Go-live checklist
- An approved 410 sample and the agreed version and partner guide are available.
- The mapping tests pass with realistic rail-freight payable 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-freight payable without processing it twice.
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
1 of Burlington Northern Santa Fe Railway (BNSF)'s 1 channel list 410
- Trading partners
- 4
partner references list 410
- Channels
- 4
channel entries list 410
Frequently listed alongside 410
Document structure
X12 410 Rail Carrier Freight Details and Invoice at the element level
The X12 410 reference contains 32 segment entries and 224 data elements; 55 are marked mandatory in this reference. Use the version and partner guide agreed for your account to confirm required fields.
- 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
Segment reference — 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
Related references
Other transactions in Burlington Northern Santa Fe Railway (BNSF)
Other EDI documents listed on this channel.
Burlington Northern Santa Fe Railway (BNSF) EDI 410 questions
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 used for?
410 is used when rail transport charges are ready to reconcile. It carries information for the rail-freight payable. Match it to your business system using rail invoice, shipment reference and equipment.
Is 410 required for Burlington Northern Santa Fe Railway (BNSF)?
410 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 410?
Start with rail invoice, shipment reference and equipment and the target rail-freight payable. 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 410 error handling?
Match one invoice covering several cars to the correct shipments. Test revised charges without duplicating the previously posted payable. Also test a lost response after destination processing so that a retry cannot create an unintended duplicate or repeated adjustment.
How does 410 relate to other EDI messages?
X12 404 Rail Carrier Shipment Information 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.
What is the difference between 410 and 404?
410 is used when rail transport charges are ready to reconcile. 404 is used when rail movement instructions are ready for carrier use. Each message represents a different business step. Keep their record references connected and track the processing result for each message.
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.
