X12
Inbound

Burlington Northern Santa Fe Railway (BNSF) X12 410 Rail Carrier Freight Details and Invoice

Burlington Northern Santa Fe Railway (BNSF)
The EDI 410 (Rail Carrier Freight Details and Invoice) document is used by Burlington Northern Santa Fe Railway (BNSF) for electronic data interchange. It enables automated processing and compliance with Burlington Northern Santa Fe Railway (BNSF)'s trading partner requirements.
26segments
4loops
14mandatory
Book a demo
← All Burlington Northern Santa Fe Railway (BNSF) transactions

Schema Reference

26 segments · X12 410 Rail Carrier Freight Details and Invoice

ISA ISA Interchange Control Header
Mandatory Max: 1
ISA01 Authorization Information Qualifier
M ID 2-2
ISA02 Authorization Information
M AN 10-10
ISA03 Security Information Qualifier
M ID 2-2
ISA04 Security Information
M AN 10-10
ISA05 Interchange ID Qualifier
M ID 2-2
ISA06 Interchange Sender ID
M AN 15-15
ISA07 Interchange ID Qualifier
M ID 2-2
ISA08 Interchange Receiver ID
M AN 15-15
ISA09 Interchange Date
M DT 6-6
ISA10 Interchange Time
M TM 4-4
ISA11 Interchange Control Standards Identifier
M ID 1-1
ISA12 Interchange Control Version Number
M ID 5-5
ISA13 Interchange Control Number
M N0 9-9
ISA14 Acknowledgment Requested
M ID 1-1
ISA15 Usage Indicator
M ID 1-1
GS GS Functional Group Header
Mandatory Max: 1
GS01 Functional Identifier Code
M ID 2-2
GS02 Application Sender's Code
M AN 2-15
GS03 Application Receiver's Code
M AN 2-15
GS04 Date
M DT 8-8
GS05 Time
M TM 4-8
GS06 Group Control Number
M N0 1-9
GS07 Responsible Agency Code
M ID 1-2
GS08 Version / Release / Industry Identifier Code
M AN 1-12
ST Transaction Set Header
Mandatory Max: 1
ST01 Transaction Set Identifier Code
M ID 3-3
ST02 Transaction Set Control Number
M AN 4-9
B3B Beginning Segment for Carrier's Invoice
Mandatory Max: 1
B3B01 Invoice Number
M AN 1-22
B3B02 Shipment Method of Payment
M ID 2-2
B3B03 Date
M DT 8-8
B3B04 Net Amount Due
M N2 1-12
B3B05 Date
O DT 8-8
B3B06 Standard Carrier Alpha Code
M ID 2-4
B3B07 Transportation Method/Type Code
M ID 1-2
B3B09 Weight Unit Code
O ID 1-1
B3B10 Correction Indicator
O ID 2-2
B3B11 Currency Code
O ID 3-3
N9 Reference Identification
Optional Max: 30
N901 Reference Identification Qualifier
M ID 2-3
N902 Reference Identification
C AN 1-30
N903 Free-form Description
C AN 1-45
N904 Date
O DT 8-8
N905 Time
C TM 4-8
N906 Time Code
O ID 2-2
CM Cargo Manifest
Optional Max: 2
CM01 Flight/Voyage Number
O AN 2-10
CM02 Port or Terminal Function Code
C ID 1-1
CM03 Port Name
O AN 2-24
CM04 Date
O DT 8-8
CM05 Booking Number
O AN 1-17
CM06 Standard Carrier Alpha Code
O ID 2-4
CM07 Standard Carrier Alpha Code
O ID 2-4
CM08 Date
O DT 8-8
CM09 Vessel Name
O AN 2-28
CM10 Pier Number
O AN 1-4
CM11 Pier Name
O AN 2-14
CM12 Terminal Name
O AN 2-30
CM13 State or Province Code
O ID 2-2
CM14 Country Code
O ID 2-3
CM15 Reference Identification
O AN 1-30
NTE Note/Special Instruction
Optional Max: 2
NTE01 Note Reference Code
O ID 3-3
NTE02 Description
M AN 1-80
N7 Loop Repeat: 500
N7 Equipment Details
Mandatory Max: 1
N701 Equipment Initial
O AN 1-4
N702 Equipment Number
M AN 1-10
N703 Weight
C R 1-10
N704 Weight Qualifier
C ID 1-2
N705 Tare Weight
C N0 3-8
N706 Weight Allowance
O N0 2-6
N707 Dunnage
O N0 1-6
N710 Ownership Code
O ID 1-1
N711 Equipment Description Code
O ID 2-2
N712 Standard Carrier Alpha Code
O ID 2-4
N714 Position
O AN 1-3
N715 Equipment Length
O N0 4-5
N716 Tare Qualifier Code
C ID 1-1
N718 Equipment Number Check Digit
O N0 1-1
N720 Height
O R 1-8
N721 Width
O R 1-8
N722 Equipment Type
O ID 4-4
N723 Standard Carrier Alpha Code
O ID 2-4
N724 Car Type Code
O ID 1-4
VC Motor Vehicle Control
Optional Max: 21
VC01 Vehicle Identification Number
M AN 1-25
VC02 Vehicle Deck Position Code
O ID 2-2
VC03 Vehicle Type Code
O ID 1-1
VC04 Dealer Code
O AN 2-9
VC05 Route Code
O AN 1-13
VC10 Factory Car Order Number
O AN 6-10
M7 Seal Numbers
Optional Max: 5
M701 Seal Number
M AN 2-15
M702 Seal Number
O AN 2-15
M703 Seal Number
O AN 2-15
M704 Seal Number
O AN 2-15
M12 In-bond Identifying Information
Optional Max: 1
M1201 Customs Entry Type Code
M ID 2-2
M1202 Customs Entry Number
C AN 1-15
M1203 Location Identifier
O AN 1-30
M1204 Location Identifier
O AN 1-30
M1205 Customs Shipment Value
O AN 2-8
M1206 In-bond Control Number
C AN 1-25
M1208 Reference Identification Qualifier
C ID 2-3
M1209 Reference Identification
C AN 1-30
M1210 Transportation Method/Type Code
C ID 1-2
M1211 Vessel Name
C AN 2-28
N8 Waybill Reference
Mandatory Max: 499
N801 Waybill Number
M N0 1-6
N802 Date
M DT 8-8
N803 Cross Reference Type Code
C ID 1-1
N804 Equipment Initial
C AN 1-4
N805 Equipment Number
C AN 1-10
N806 Waybill Number
C N0 1-6
N807 Date
C DT 8-8
N808 City Name
C AN 2-30
N809 State or Province Code
C ID 2-2
N810 Standard Carrier Alpha Code
C ID 2-4
N811 Freight Station Accounting Code
C ID 1-5
F9 Origin Station
Mandatory Max: 1
F901 Freight Station Accounting Code
O ID 1-5
F902 City Name
M AN 2-30
F903 State or Province Code
M ID 2-2
F908 Standard Point Location Code
O ID 6-9
F909 Postal Code
O ID 3-15
D9 Destination Station
Mandatory Max: 1
D901 Freight Station Accounting Code
O ID 1-5
D902 City Name
M AN 2-30
D903 State or Province Code
M ID 2-2
D908 Standard Point Location Code
O ID 6-9
D909 Postal Code
O ID 3-15
N1 Loop Repeat: 10
N1 Name
Optional Max: 1
N101 Entity Identifier Code
M ID 2-3
N102 Name
C AN 1-60
N103 Identification Code Qualifier
C ID 1-2
N104 Identification Code
C AN 2-80
N105 Entity Relationship Code
O ID 2-2
N106 Entity Identifier Code
O ID 2-3
N3 Address Information
Optional Max: 2
N301 Address Information
M AN 1-55
N302 Address Information
O AN 1-55
N4 Geographic Location
Optional Max: 1
N401 City Name
O AN 2-30
N402 State or Province Code
O ID 2-2
N403 Postal Code
O ID 3-15
N404 Country Code
O ID 2-3
N405 Location Qualifier
C ID 1-2
N406 Location Identifier
O AN 1-30
R2 Route Information
Optional Max: 13
R201 Standard Carrier Alpha Code
M ID 2-4
R202 Routing Sequence Code
M ID 1-2
R203 City Name
O AN 2-30
R204 Standard Point Location Code
O ID 6-9
R205 Intermodal Service Code
O ID 1-2
R207 Intermediate Switch Carrier
C ID 2-4
R208 Intermediate Switch Carrier
O ID 2-4
PS Protective Service Instructions
Optional Max: 5
PS01 Protective Service Rule Code
M ID 3-9
PS02 Protective Service Code
M ID 1-4
PS03 Unit or Basis for Measurement Code
C ID 2-2
PS04 Temperature
C R 1-4
PS05 Standard Carrier Alpha Code
O ID 2-4
PS06 Freight Station Accounting Code
O ID 1-5
PS07 City Name
O AN 2-30
PS08 State or Province Code
O ID 2-2
PS10 Pre-Cooled (Rule 710) Code
O ID 1-1
PS11 Yes/No Condition or Response Code
O ID 1-1
PS12 Yes/No Condition or Response Code
O ID 1-1
PS13 Yes/No Condition or Response Code
O ID 1-1
PS14 Temperature
C R 1-4
LX Loop Repeat: 25
LX Assigned Number
Mandatory Max: 1
LX01 Assigned Number
M N0 1-6
L5 Description, Marks and Numbers
Mandatory Max: 15
L501 Lading Line Item Number
O N0 1-3
L502 Lading Description
O AN 1-50
L503 Commodity Code
C AN 1-30
L504 Commodity Code Qualifier
C ID 1-1
L505 Packaging Code
O AN 3-5
L506 Marks and Numbers
C AN 1-48
L507 Marks and Numbers Qualifier
O ID 1-2
L508 Commodity Code Qualifier
C ID 1-1
L509 Commodity Code
C AN 1-30
L510 Compartment ID Code
O ID 1-1
L0 Loop Repeat: 25
L0 Line Item - Quantity and Weight
Mandatory Max: 1
L001 Lading Line Item Number
O N0 1-3
L002 Billed/Rated-as Quantity
C R 1-11
L003 Billed/Rated-as Qualifier
C ID 2-2
L004 Weight
C R 1-10
L005 Weight Qualifier
C ID 1-2
L006 Volume
C R 1-8
L007 Volume Unit Qualifier
C ID 1-1
L008 Lading Quantity
C N0 1-7
L009 Packaging Form Code
C ID 3-3
L010 Dunnage Description
O AN 2-25
L011 Weight Unit Code
O ID 1-1
L012 Type of Service Code
O ID 2-2
L013 Quantity
C R 1-15
L014 Packaging Form Code
O ID 3-3
L015 Yes/No Condition or Response Code
C ID 1-1
L1 Rate and Charges
Mandatory Max: 10
L101 Lading Line Item Number
O N0 1-3
L102 Freight Rate
C R 1-9
L103 Rate/Value Qualifier
C ID 2-2
L104 Charge
C N2 1-12
L105 Advances
C N2 1-9
L106 Prepaid Amount
C N2 1-9
L107 Rate Combination Point Code
O AN 3-9
L108 Special Charge or Allowance Code
O ID 3-3
L109 Rate Class Code
O ID 1-3
L110 Entitlement Code
O ID 1-1
L111 Charge Method of Payment
O ID 1-1
L112 Special Charge Description
O AN 2-25
L113 Tariff Application Code
O ID 1-1
L114 Declared Value
C N2 2-12
L115 Rate/Value Qualifier
C ID 2-2
L116 Lading Liability Code
O ID 1-1
L117 Billed/Rated-as Quantity
C R 1-11
L118 Billed/Rated-as Qualifier
C ID 2-2
L119 Percent
O R 1-10
L120 Currency Code
O ID 3-3
L121 Amount
O N2 1-15
PI Price Authority Identification
Optional Max: 30
PI01 Reference Identification Qualifier
M ID 2-3
PI02 Reference Identification
M AN 1-30
PI03 Primary Publication Authority Code
O ID 2-2
PI04 Regulatory Agency Code
O ID 3-5
PI05 Tariff Agency Code
O ID 1-4
PI06 Issuing Carrier Identifier
O AN 1-10
PI07 Contract Suffix
O AN 1-2
PI08 Tariff Item Number
O AN 1-16
PI09 Tariff Supplement Identifier
O AN 1-4
PI10 Tariff Section
O AN 1-2
PI11 Contract Suffix
O AN 1-2
PI12 Date
C DT 8-8
PI13 Date
C DT 8-8
PI14 Alternation Precedence Code
O ID 1-1
PI15 Alternation Precedence Code
O ID 1-1
L3 Total Weight and Charges
Mandatory Max: 1
L305 Charge
O N2 1-12
L306 Advances
O N2 1-9
L307 Prepaid Amount
O N2 1-9
SE Transaction Set Trailer
Mandatory Max: 1
SE01 Number of Included Segments
M N0 1-10
SE02 Transaction Set Control Number
M AN 4-9
How It Works

Automating Burlington Northern Santa Fe Railway (BNSF) EDI 410

Stacksync validates, transforms, and delivers your 410 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate
Transform
Route
Monitor
Stacksync processes Burlington Northern Santa Fe Railway (BNSF) EDI 410 (Rail Carrier Freight Details and Invoice) documents automatically — syncing data to your system in real time with no manual intervention required.
Related Documents

Other Burlington Northern Santa Fe Railway (BNSF) EDI transactions

Explore all supported EDI transaction types for Burlington Northern Santa Fe Railway (BNSF). Stacksync handles every document from a single platform.

404In
Rail Carrier Shipment Information
Burlington Northern Santa Fe Railway (BNSF)
322In
Terminal Operations and Intermodal Ramp Activity
Burlington Northern Santa Fe Railway (BNSF)
View all Burlington Northern Santa Fe Railway (BNSF) EDI documents →

Burlington Northern Santa Fe Railway (BNSF) EDI 410 FAQ

Common questions about 410 Rail Carrier Freight Details and Invoice transactions with Burlington Northern Santa Fe Railway (BNSF).

What is a Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice?

The Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice is an X12 transaction set used to exchange Rail Carrier Freight Details and Invoice data electronically between trading partners. As a inbound document, it standardizes the communication of Rail Carrier Freight Details and Invoice information between Burlington Northern Santa Fe Railway (BNSF) and their suppliers, carriers, or partners. Stacksync processes Burlington Northern Santa Fe Railway (BNSF) 410 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Burlington Northern Santa Fe Railway (BNSF)'s requirements in real time.

What is a Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice?

The Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice is an X12 transaction set used to exchange Rail Carrier Freight Details and Invoice data electronically between trading partners. As a inbound document, it standardizes the communication of Rail Carrier Freight Details and Invoice information between Burlington Northern Santa Fe Railway (BNSF) and their suppliers, carriers, or partners. Stacksync processes Burlington Northern Santa Fe Railway (BNSF) 410 transactions automatically, parsing the X12 segments and mapping them to the corresponding records in your ERP, WMS, or database. This eliminates manual data entry, reduces errors, and ensures your systems stay in sync with Burlington Northern Santa Fe Railway (BNSF)'s requirements in real time.

How does Stacksync automate Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice transactions?

Stacksync handles Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 410 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Burlington Northern Santa Fe Railway (BNSF) 410 document meets their specific formatting requirements before transmission or after receipt.

How does Stacksync automate Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice transactions?

Stacksync handles Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice transactions through an automated pipeline: receive the X12 document, validate the envelope and segment structure, map fields to your system's schema, and sync the data in real time. For inbound 410 transactions, Stacksync either generates the document from your system's data or processes incoming documents and routes them to the correct records. The platform includes built-in compliance validation so every Burlington Northern Santa Fe Railway (BNSF) 410 document meets their specific formatting requirements before transmission or after receipt.

What are common Burlington Northern Santa Fe Railway (BNSF) EDI 410 errors and how do I fix them?

Common errors in Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Burlington Northern Santa Fe Railway (BNSF) 410 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

What are common Burlington Northern Santa Fe Railway (BNSF) EDI 410 errors and how do I fix them?

Common errors in Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice transactions include missing mandatory segments, invalid qualifier codes, incorrect date or time formats, and data values exceeding maximum field lengths. Reference number mismatches between related documents (e.g., PO numbers that don't match) also cause rejections. Stacksync validates Burlington Northern Santa Fe Railway (BNSF) 410 documents against known requirements before transmission and after receipt, catching errors proactively. When issues occur, the platform provides human-readable error descriptions with the specific segment and element that failed, rather than raw X12 error codes.

How long does it take to set up Burlington Northern Santa Fe Railway (BNSF) EDI 410 with Stacksync?

Most Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Burlington Northern Santa Fe Railway (BNSF)'s 410 format and your system, running test transactions, and completing Burlington Northern Santa Fe Railway (BNSF)'s certification process if required. Stacksync includes pre-built mappings for Burlington Northern Santa Fe Railway (BNSF)'s most common 410 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

How long does it take to set up Burlington Northern Santa Fe Railway (BNSF) EDI 410 with Stacksync?

Most Burlington Northern Santa Fe Railway (BNSF) EDI 410 Rail Carrier Freight Details and Invoice integrations with Stacksync go live within 3 to 5 business days. The setup involves authenticating your EDI connection (AS2, SFTP, or VAN), configuring field mappings between Burlington Northern Santa Fe Railway (BNSF)'s 410 format and your system, running test transactions, and completing Burlington Northern Santa Fe Railway (BNSF)'s certification process if required. Stacksync includes pre-built mappings for Burlington Northern Santa Fe Railway (BNSF)'s most common 410 configurations, which accelerates the setup. Your team can monitor the integration from a single dashboard without managing EDI infrastructure directly.

Can I customize Burlington Northern Santa Fe Railway (BNSF) EDI 410 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Burlington Northern Santa Fe Railway (BNSF) EDI 410 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Burlington Northern Santa Fe Railway (BNSF) updates their 410 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Can I customize Burlington Northern Santa Fe Railway (BNSF) EDI 410 field mappings in Stacksync?

Yes. Stacksync provides a visual field mapping tool that lets you define exactly how Burlington Northern Santa Fe Railway (BNSF) EDI 410 segments and elements map to your system's fields. You can set data transformations (date format conversion, code translation tables), conditional routing rules, and default values for optional fields. The mappings are version-controlled, so changes can be reviewed and rolled back if needed. If Burlington Northern Santa Fe Railway (BNSF) updates their 410 specification, Stacksync highlights the affected mappings and suggests adjustments, ensuring your integration stays compliant without a full reconfiguration.

Ready to automate Burlington Northern Santa Fe Railway (BNSF) EDI?

a blue checkmark icon
POC from integration engineers
a blue checkmark icon
No-code EDI setup
a blue checkmark icon
Real-time compliance monitoring
a blue checkmark icon
White-glove onboarding
Book a demo
"We've been using Stacksync across 4 different projects and can't imagine working without it."

Alex Marinov

VP Technology, Acertus Delivers
Vehicle logistics powered by technology