Carriers integration

BNSF Railway EDI 404, 322, 410 and 820 integration

BNSF publishes implementation guides for the 404 shipment, 322 ramp activity, 410 freight invoice and 820 payment. See how these rail documents flow and how ECOM connects them.

At a glance

BNSF Railway integration, in three pictures

The industry, the document flow and the outcome for your team. Illustrations only: they show typical practice, not a specific BNSF Railway program or a customer relationship.

Illustration of a locomotive pulling freight cars, representing the carriers industry that BNSF Railway operates in.
Industry. Carriers: where BNSF Railway operates.
Workflow diagram: your TMS, ERP and finance systems exchange documents with BNSF Railway through ECOM. You send 404, 820; you receive 322, 410; 997 acknowledgments go both ways. Your systems TMS · ERP · finance ECOM integration map · validate · connect · monitor BNSF Railway 404 820 404 820 322 410 322 410 997 both ways
Workflow. Documents in each direction. Orange: you send. Blue: you receive. Typical, not confirmed.
Comparison diagram: without integration, documents are re-keyed, files are emailed and rejections are found late; with ECOM, documents are mapped to your ERP, validated and monitored, and exceptions are visible early. Without integration Tenders and invoices re-keyed Files emailed or uploaded Rejections found late With ECOM Documents mapped to your ERP Every file validated and monitored Exceptions visible early
Outcome. From manual handling to a monitored flow. No figures: results depend on your setup.

Talk to an EDI/API Expert about BNSF Railway

Tell us which documents you exchange with BNSF Railway, which ERP you run and when you need to be live. A specialist will outline the connection, mapping and testing plan. This page is a guide based on typical practice; it does not mean ECOM works with BNSF Railway.

  • Review of BNSF Railway's requirements with you, once you have them
  • EDI and API integration with your TMS, ERP and finance systems
  • Monitoring and managed service after go-live, if you want it

Prefer to call? Sales 972-836-7750 or email sales@ecom-specialist.com.

Takes about 30 seconds. Phone and note are optional.

Your request is about

Trading partner
BNSF Railway

When should we talk?

Times are in your time zone. We use this to schedule the conversation.

We use your details only to respond to your request. See our privacy notice. Prefer to talk? Call Sales at 972-836-7750.

Integration and onboarding

How BNSF Railway integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringFTP · Value-added network (VAN) · BNSF APIs and bnsf.com tools
BNSF RailwayIts program, documents and requirements
  1. ConfirmConfirm your BNSF Railway program, role and the documents it requires.
  2. MapMap each document to your ERP fields and business rules.
  3. ConnectConfigure the connection and security the program needs.
  4. TestTest against the applicable specifications and acknowledgments.
  5. Go liveGo live with monitoring, alerts and exception handling.
Typical implementation path. Exact requirements are confirmed against the applicable specifications during onboarding.

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.

Business scenarios

Where BNSF Railway integration gets complicated

Typical requirements—confirm with your trading partner.

Shipment instruction at tender

The 404 is BNSF's initial shipment tender and can also serve as an equipment release notice and a legal bill of lading, so errors at this step carry through the move.

How ECOM helps: ECOM validates the 404 against the implementation guide before it goes out and monitors acknowledgments.

What you gain: Fewer rejected tenders and corrections.

Intermodal ramp events

The 322 reports arrivals, departures, ingates and outgates, which drive drayage planning.

How ECOM helps: ECOM maps each 322 event to the booking in your TMS and flags containers with missing or late events.

What you gain: Drayage and yard plans follow actual ramp activity.

Freight invoice to remittance

The 410 gives detailed charges for a rail movement, and the 820 provides the detail for cash application.

How ECOM helps: ECOM matches each 410 to the 404 shipment, lists differences, and builds the 820 from your payment run.

What you gain: Faster payment and a clear trail for audit.

Workflows

Typical BNSF Railway business workflows

The steps summarize the documents below. Where a step is not in BNSF Railway's published documents, it reflects common practice.

Shipment to payment

  1. 1Send 404 shipment information
  2. 2Receive 322 ramp activity
  3. 3Receive 410 freight invoice
  4. 4Send 820 remittance

Intermodal ramp activity

  1. 1Send 404 for the container
  2. 2Receive 322 ingate
  3. 3Receive 322 outgate
  4. 4Plan the final leg

Documents and APIs

BNSF Railway documents by program

Every document this guide names, with the program it applies to and its status. Required, optional and conditional come from BNSF Railway's published documents cited below; documents marked general guidance are common in this industry but not confirmed for BNSF Railway.

DocumentNameDirectionProgramStatusPurpose
404 Rail Carrier Shipment Information To BNSF Railway BNSF EDI implementation guides Named; level not stated BNSF describes the 404 as the document that sends bill of lading information to the railroad. It is the initial shipment tender and can serve as an equipment release notice and a legal bill of lading.
322 Terminal Operations and Intermodal Ramp Activity From BNSF Railway BNSF EDI implementation guides Named; level not stated BNSF describes the 322 as communicating rail events such as arrivals and departures and terminal activities such as ingates and outgates.
410 Rail Carrier Freight Details and Invoice From BNSF Railway BNSF EDI implementation guides Named; level not stated BNSF describes the 410 as providing the detailed charges for a rail movement to the freight payer.
820 Payment Order/Remittance Advice To BNSF Railway BNSF EDI implementation guides Named; level not stated BNSF describes the 820 as providing the detail needed for cash application to the payee's accounts receivable system.
997 Functional Acknowledgment Both directions Not stated General guidance Commonly used to confirm that each file was received and could be read. BNSF does not list it on its EDI page.

Connectivity

How companies connect

  • FTP

    BNSF says customers who can build their own EDI transaction sets can exchange data directly with BNSF over FTP.

    From BNSF Railway's published documents

  • Value-added network (VAN)

    BNSF says customers who cannot create EDI documents can use a VAN, and recommends direct transmission for customers who can because VANs carry costs.

    From BNSF Railway's published documents

  • BNSF APIs and bnsf.com tools

    BNSF describes APIs to retrieve data and manage shipments in real time, and tools for shipping instructions, tracking, unit history, notifications and account status.

    From BNSF Railway's published documents

Challenges

Common integration challenges

  • Version 4010 guides

    BNSF publishes its implementation guides at version 4010. Confirm the version your systems produce and the version BNSF expects.

  • Shipment errors carry through

    Because the 404 is a tender and a legal bill of lading, corrections after submission add effort. Validate before sending.

  • Ramp events and bookings

    322 events must match your equipment and booking references to be useful for drayage planning.

  • Invoice and payment matching

    The 410 and the 820 must tie back to the same shipment so cash application works at the railroad and audit works for you.

Automation options for BNSF Railway shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. BNSF Railway sets its own requirements; ECOM confirms which options fit yours.

PRISM Supply Chain Automation Foundation

One platform beneath every option. Use one, or combine them for different partners and documents.

Compliance and actionable visibility

Connect order processing, shipping documentation, trading partner requirements, and performance monitoring through one coordinated workflow. These capabilities help teams improve shipment accuracy, reduce manual work, address compliance risks, and respond to exceptions before they affect customers.

Discuss Your Trading Partner Requirements

General EDI flow

How EDI with BNSF Railway typically works

The documents, their order and the timing are BNSF Railway's to set; this is the general sequence most programs of this kind follow.

  1. 404 Rail Carrier Shipment Information

    From you to BNSF Railway

    BNSF describes the 404 as the document that sends bill of lading information to the railroad. It is the initial shipment tender and can serve as an equipment release notice and a legal bill of lading.

  2. 322 Terminal Operations and Intermodal Ramp Activity

    From BNSF Railway to you

    BNSF describes the 322 as communicating rail events such as arrivals and departures and terminal activities such as ingates and outgates.

  3. 410 Rail Carrier Freight Details and Invoice

    From BNSF Railway to you

    BNSF describes the 410 as providing the detailed charges for a rail movement to the freight payer.

  4. 820 Payment Order/Remittance Advice

    From you to BNSF Railway

    BNSF describes the 820 as providing the detail needed for cash application to the payee's accounts receivable system.

  5. 997 Functional Acknowledgment

    Both directions

    Commonly used to confirm that each file was received and could be read. BNSF does not list it on its EDI page.

Working from BNSF Railway's published specification?

Tell ECOM which program and documents apply to you. We read the published specification with you, map it to your systems and test against it. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your BNSF Railway program

Each request goes to an ECOM EDI specialist with BNSF Railway's name attached, so the reply starts from your program.

  • Review BNSF Railway's requirements

    Send us BNSF Railway's guide or your program details; we explain the documents, rules and options for meeting them.

    Request a requirements review
  • Connect BNSF Railway to your ERP

    Tenders, status and freight invoices in and out of the TMS, ERP and finance systems you already run.

    Discuss ERP integration
  • Testing and certification

    Build, test and certify each BNSF Railway document, then go live with monitoring from the first file.

    Plan testing and certification

BNSF Railway integration FAQs

Which EDI documents does BNSF publish guides for?

BNSF lists implementation guides (version 4010) for the 322 Intermodal Ramp Activity, 404 Shipment Information, 410 Freight Details and Invoice and 820 Payment Order/Remittance Advice.

Does BNSF use the 214 status message?

BNSF's EDI page does not list the 214. Rail status is reported through the 322 and through BNSF's tracking tools, so do not assume the motor-carrier document set applies.

How can I exchange EDI with BNSF?

BNSF says customers who can build their own EDI documents can use FTP directly, and others can use a value-added network. BNSF recommends direct transmission because VANs carry costs.

Does BNSF offer an API?

BNSF describes APIs for retrieving data and managing shipments in real time, in addition to its bnsf.com tools.

Is this page an endorsement by BNSF?

This is an independent integration guide. It does not indicate an endorsement, partnership or approval by BNSF.

Sources and accuracy

This guide summarizes publicly available information as of November 2026. BNSF Railway sets its own requirements and can change them at any time; your BNSF Railway implementation guide, supplier portal or account contact is the authoritative source for your program.

Request BNSF Railway integration assistance

Tell us about your BNSF Railway program, documents and ERP. We will outline the connection, mapping and testing plan.