Overview
Understanding BNSF Railway integration
Who this is for: Shippers, intermodal marketing companies and logistics providers that move freight by rail with BNSF, and the transportation and finance teams that send shipment information and pay freight charges.
Scope: Onboarding and testing steps for EDI are not described on BNSF's public page. The 997 acknowledgment is listed as commonly used.
Shipping by rail with BNSF means getting four things right: the shipment instruction that starts the move, the terminal events that show where equipment is, the freight invoice, and the payment that closes it. BNSF publishes implementation guides (version 4010) for four X12 documents on its bnsf.com tools page: the 404 Shipment Information, which sends bill of lading information to the railroad and is the initial shipment tender; the 322 Intermodal Ramp Activity, which reports rail events such as arrivals and departures and terminal activity such as ingates and outgates; the 410 Freight Details and Invoice, which gives the freight payer the detailed charges; and the 820 Payment Order/Remittance Advice, which gives the payee the detail for cash application.
BNSF says customers who can build their own EDI documents can exchange them directly over FTP, and customers who cannot can use a value-added network, with a recommendation to go direct because VANs carry costs. BNSF also offers bnsf.com tools such as Shipping Instructions (an electronic waybill), shipment tracking, unit history and account status, and describes APIs for retrieving data and managing shipments in real time. BNSF lists a registration process for bnsf.com in which a representative contacts you to set up and train you.
ECOM helps you map the 404, 322, 410 and 820 to your TMS, ERP and payables systems, configure the connection, test, and monitor every file after go-live, as software, as a managed service or both. The 214 status message is the motor-carrier document; BNSF's published rail set is built around the 322 and the bnsf.com tracking tools.