Rail freight integration
Rail Freight EDI and API Integration
Rail freight is a network of railroads that hand cars to one another, and every handoff depends on data that railroads validate strictly. ECOM connects your shipping, ERP, transportation and logistics systems to railroads and rail partners, then maps, validates, tests and monitors each transaction across shipper-facing, railroad-to-railroad, carload and intermodal workflows.
Overview
What is rail freight EDI?
Rail freight EDI is the exchange of standardized transactions between shippers, railroads, equipment owners and freight payers. In ANSI X12 the core transactions include the 404 Rail Carrier Shipment Information, which tenders a shipment and its bill of lading to a railroad, the 417 Rail Carrier Waybill Interchange, which carries movement instructions between railroads, the 418, 419 and 421 for interchange and car scheduling, the 426 Rail Revenue Waybill, and the 410 Rail Carrier Freight Details and Invoice. Railinc coordinates EDI and XML standard setting for the railroad industry, and each railroad publishes its own implementation guidelines and versions. Intermodal moves, where containers and trailers travel on rail, add terminal and ramp activity such as ingates and outgates.
Overview
For shippers, rail carriers and intermodal operators
Rail data moves between railroads at every interchange, so roles matter.
Rail carriers
You receive shipment instructions from many shippers and exchange waybill, interchange and scheduling data with other railroads.
Intermodal operators and marketing companies
You coordinate ramp activity, drayage and rail legs and report equipment events to customers.
Shippers tendering by rail
You send bills of lading from your shipping system and need movement events and invoices in your ERP and TMS.
Equipment owners and lessors
You need interchange and movement events for the cars you own or lease.
How ECOM helps
How ECOM supports rail workflows
ECOM supports intermodal transportation today; carload and railroad-specific transaction scope is confirmed per engagement.
Bills of lading without paper
Shipment instructions go to the railroad electronically from the system that creates the shipment, so cars can be released without re-keying or paper.
Equipment and interchange you can follow
Interchange, scheduling and movement events reach your own systems, so planners can see where cars are and when they should arrive.
Fewer rejected transactions
Equipment numbers, commodity codes and required fields are checked before sending, so errors are fixed on your side instead of coming back from the railroad.
Freight invoices you can audit
Rail invoices that reference the same shipment can be compared with the bills of lading and agreed rates before they are paid.
How ECOM delivers it
Transaction mapping
Shipment, waybill, interchange, scheduling, status and invoice data mapped between your systems and the version of each transaction your railroad or partner specifies.
Validation before sending
Outbound transactions are checked against the partner implementation guideline, and acknowledgments and application errors are matched back to the shipment.
Connectivity
Connections over AS2, SFTP, HTTPS and APIs, hosted by ECOM or opened to the partner, according to what each railroad or rail partner supports.
Specification review and testing
ECOM reviews the railroad guideline, builds the maps and tests scenarios with the partner, including corrections, diversions and rejections, before go-live.
Monitoring and alerts
Missing acknowledgments, absent movement events and rejected transactions surface as exceptions so someone can act before a car sits.
Ongoing support
ECOM offers 24×7 support, with coverage hours and response targets defined in each service agreement.
ECOM offerings for this workflow
Systems Integrator
Connects TMS, ERP and WMS platforms with the shipment, waybill, interchange and invoice data exchanged with railroads. Hundreds of customers use the Systems Integrator today, and ECOM performs these integrations for customers.
Exception Management Center
Helps automate exception handling and manage internal and customer-facing SLAs, such as an unacknowledged waybill or a missed interchange.
Transaction Life Cycle Manager
Holds shipment paperwork and supporting evidence with the shipment record, including proof of delivery, signatures, damage reports and shortage reports.
Coordination with road legs and terminals
Where a rail move is part of an intermodal shipment, the road legs, ramps and terminals are connected as described on the intermodal page.
Freight Onboarding
Brings carriers and other freight partners live.
Trading Partner Onboarding
A self-service portal that supports almost all verticals, with customer click-through onboarding, protocol-specific setup and automated transaction testing.
Reconcile360 (invoice-to-cash)
Invoice-to-cash automation across all verticals, including air and ocean partners, so freight billing connects to cash.
Which offerings apply, and the partners, protocols and systems in scope, are agreed with you during scoping.
Workflow
From car order to freight invoice: the carload rail lifecycle
A carload shipment passes through several parties and several systems. The stages below follow the carload workflow; intermodal is shown on its own track in the diagram and compared in the table further down. The transactions named are the ones X12, Railinc and public railroad EDI pages describe.
- 01
Order equipment
A shipper or railroad orders the railcars needed for the transportation job.
Typical messages: X12 422 Equipment Order
- 02
Load and release the shipment
The shipper loads the car and tenders the shipment with its bill of lading, which can also notify the railroad that loaded equipment is released for movement.
Typical messages: X12 404 Rail Carrier Shipment Information
- 03
Create the waybill
The origin railroad waybills the shipment. The waybill is sent to Railinc’s Forward & Store system, which forwards it to the other railroads on the route.
Typical messages: X12 417 Rail Carrier Waybill Interchange; 997 or 824 from Forward & Store
- 04
Prepare the interchange
Before cars change railroads, the railroads exchange advance information about the equipment and cars offered for interchange.
Typical messages: X12 418 Rail Advance Interchange Consist; 419 Advance Car Disposition
- 05
Move and schedule
Railroads share estimated times of arrival and car scheduling as the shipment moves, and report movement events such as interchanges and passing events.
Typical messages: X12 421 Estimated Time of Arrival and Car Scheduling; railroad event reporting
- 06
Interchange between railroads
The car passes to the connecting railroad, which reports receipt. This is where equipment visibility gaps most often open.
Typical messages: Interchange events reported by the railroads; X12 456 for equipment inquiries
- 07
Arrive and place at the destination
The destination railroad reports arrival and placement at the consignee. Shippers and consignees want these events in their own systems.
Typical messages: Arrival and placement events; X12 214 or 456 where a partner provides them
- 08
Invoice and settle
The railroad invoices the freight payer, and the payer audits the invoice against the bill of lading and agreed rates. Railroads also settle revenue between themselves.
Typical messages: X12 410 Rail Carrier Freight Details and Invoice; X12 426 Rail Revenue Waybill between railroads
Who sends which rail transaction to whom
Shippers usually deal with the origin railroad, while railroads exchange most interchange and waybill transactions among themselves and through industry services. The diagram shows typical directions; the tables give purpose, trigger, data and systems for each transaction.
Illustrative example: one carload shipment of three cars
An illustrative shipment, followed step by step. Partners define their own messages and sequence.
| Step | Transaction | From → to | What the integration checks |
|---|---|---|---|
| Tender three loaded cars | Bill of lading data (404) | Shipper → origin railroad | Each car has a valid equipment number, commodity code and weight, and required hazardous materials data is present. |
| Acknowledge receipt | Acknowledgment (997 or 824) | Railroad or service → shipper | A 997 acknowledges receipt and syntax checks; an 824 reports application errors and is shown with them, corrected and resent. |
| Share the waybill | Waybill (417) | Origin railroad → connecting railroads | The shipper can see that the waybill exists and was acknowledged. |
| Prepare the handoff | Interchange notices (418, 419) | Railroad → connecting railroad | Cars offered for interchange match the cars tendered. |
| Update arrival | Scheduling (421) | Railroad → railroads and planners | A changed estimated arrival updates the receiving plant schedule. |
| Invoice the freight | Freight invoice (410) | Railroad → freight payer | Invoice references match the bill of lading and the agreed rate. |
Messages
Transactions and messages
Typical requirements—confirm with your trading partner.
Shipment instructions, bills of lading and waybills
These transactions start the movement. The shipper tenders the shipment, and the railroads create and share the waybill that carries movement instructions and revenue information.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| 422 Equipment Order ANSI X12 | Orders the equipment needed for transportation, between a shipper and a rail carrier. | Shipper or rail carrier to Rail carrier or shipper | Cars needed for loading | Equipment type and quantity, location, date needed | ERP, shipping or logistics system to railroad system | Cars requested electronically instead of by phone or portal |
| 404 Rail Carrier Shipment Information ANSI X12 | Tenders a shipment to a railroad with its bill of lading data, and can notify that loaded equipment is released for movement. | Shipper (consignor) or its agent to Rail carrier (first road haul) | Car loaded and ready for release | Equipment number, commodity code, weights, consignee, routing, hazardous materials data where required | ERP, shipping system or TMS to railroad system | Paperless bills of lading and faster release |
| 417 Rail Carrier Waybill Interchange ANSI X12 | Gives railroads movement instructions. The origin railroad sends it, and it is forwarded to the other railroads on the route. | Origin rail carrier to Other rail carriers on the route, through Railinc Forward & Store | Waybill created, corrected or diverted | Equipment, routing, commodity, origin and destination, billing and revenue details | Railroad systems and industry services | Every railroad on the route works from the same waybill |
| 425 Rail Waybill Request ANSI X12 | Requests a copy of a revenue or movement waybill from the origin or a previous rail carrier when the original transmission cannot be found. | Rail carrier to Origin or previous rail carrier | Waybill missing at the receiving railroad | Equipment and shipment identification | Railroad systems | Missing waybills recovered without phone calls |
| 426 Rail Revenue Waybill ANSI X12 | Responds to a waybill request with the revenue waybill a railroad needs to collect revenue from the paying parties. | Origin or previous rail carrier to Requesting rail carrier | Receipt of a 425 request | Waybill, revenue and billing details | Railroad and settlement systems | Railroads can bill and settle correctly |
Interchange, car disposition and scheduling
Interchange is the handoff of cars from one railroad to another. These transactions give the receiving railroad advance notice and keep arrival estimates current. Shippers, consignees and equipment owners benefit when the events reach their systems.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| 418 Rail Advance Interchange Consist ANSI X12 | Gives advance information on equipment being interchanged to a connecting railroad, from a consignor, or to a consignee. | Railroad, consignor or consignee to Connecting rail carrier | Equipment about to be interchanged | Equipment numbers, contents, sequence, interchange location | Railroad systems and shipper or consignee logistics systems | Receiving railroad prepared for incoming cars |
| 419 Advance Car Disposition ANSI X12 | Gives advance notice of cars being offered for interchange, directly or through a switching carrier. | Offering rail carrier to Receiving rail carrier | Cars offered for interchange | Equipment, disposition, interchange point | Railroad systems | Fewer surprises at the interchange point |
| 421 Estimated Time of Arrival and Car Scheduling ANSI X12 | Exchanges car scheduling and estimated time of arrival data between railroads. Forward & Store also receives these trip-plan messages from the origin railroad. | Rail carrier to Other rail carriers, and parties that receive the data | Trip plan created or ETA changed | Equipment, scheduled movement, estimated arrival | Railroad systems, TMS and planning tools | Arrival estimates that planners can use |
| 997 / 824 Functional acknowledgment and application advice ANSI X12 | Forward & Store acknowledges received messages with a 997 (receipt and syntax) and reports application errors with an 824 application advice. Neither is a railroad’s acceptance of the shipment. | Forward & Store or the receiving partner to Sending railroad or partner | Receipt of a file or message | Accepted or rejected status, error detail | EDI translation and monitoring layer | Rejected waybills found and fixed quickly |
Equipment movement and status
Equipment visibility comes from movement events and inquiries. Railroads report events to industry systems, and some partners provide status messages to shippers and consignees. Intermodal ramp activity is reported separately.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| Car events Movement and status events Railinc event reporting | Railroads report events such as release, interchange, passing, arrival at destination and placement to the rail industry’s event systems. | Railroad to Railinc event systems, then equipment owners and subscribers | A car moves, arrives or is placed | Equipment number, event type, location, date and time | Railroad operating systems and Railinc services | A common source of equipment location data |
| 456 Railroad Equipment Inquiry or Advice ANSI X12 | Provides information to a qualified customer, and inquires about the location of equipment or shipments. | Railroad or qualified customer to Qualified customer or railroad | Equipment or shipment inquiry | Equipment or shipment identification, location, status | Railroad systems and customer logistics systems | Location answers without phone calls |
| 214 Transportation Carrier Shipment Status Message ANSI X12 | Reports the status of shipments to shippers, consignees and their agents, for partners that provide it. | Carrier or provider to Shipper, consignee or agent | Shipment event | Status and reason codes, date and time, location, references | Carrier system to TMS or visibility tool | Consistent milestones across partners |
| 322 Terminal Operations and Intermodal Ramp Activity ANSI X12 | Communicates terminal and intermodal ramp activity, such as ingates and outgates, to authorized parties to a shipment. | Terminal, port authority or intermodal ramp to Authorized parties to the shipment | Container or trailer gates in or out at a ramp | Equipment identification, event, date and time, location | Ramp or terminal systems to TMS or logistics platform | Ramp events visible in your own systems |
Freight invoices and cross-border filings
Freight invoices close the shipment. For cross-border rail moves, customs data is filed through separate U.S. Customs and Border Protection messages.
| Transaction | Purpose | Sender → receiver | Trigger | Key data | Connected systems | Business benefit |
|---|---|---|---|---|---|---|
| 410 Rail Carrier Freight Details and Invoice ANSI X12 | Provides detailed information about the charges for a rail movement and is sent to the freight payer. | Rail carrier to Freight payer | Shipment delivered or billing event | Shipment and equipment references, rates, charges, weights | Railroad billing system to ERP or freight audit | Invoices audited against the bill of lading |
| 309, 350, 353, 355, 358 Customs manifest and status messages ANSI X12 (CBP ACE rail manifest) | CBP lists these X12 messages for rail manifest filing in ACE: the 309 customs manifest, and the 350, 353, 355 and 358 for status, events, acceptance or rejection and consist information. | Rail carrier, and CBP for responses to U.S. Customs and Border Protection, and the carrier for responses | Cross-border rail shipment | Manifest data, equipment, cargo description, consignee | Railroad and customs filing systems | Customs data filed and answered electronically |
Carload and intermodal rail workflows compared
Rail freight splits into carload movements, where railcars are loaded at a customer siding, and intermodal movements, where containers and trailers ride on rail through ramps. The workflows share some documents and differ in others, so scope them separately.
| Criteria | Carload (railcar) | Intermodal (container or trailer) |
|---|---|---|
| What moves | Loaded and empty railcars between customer sidings and yards | Containers and trailers carried on rail between terminal ramps |
| Typical parties | Shipper, origin railroad, connecting railroads, consignee and equipment owner | Shipper or beneficial cargo owner, intermodal provider, railroad, ramp operator and drayage provider |
| Documents that usually matter | 404 bill of lading, 417 waybill, 418, 419 and 421 interchange and scheduling, 410 invoice | 322 terminal and ramp activity for ingates and outgates, status messages, and the provider’s own booking and invoice formats |
| Where visibility gaps appear | Between railroads at interchange, and between arrival and placement at the siding | At ramp ingate and outgate, and between ramp and final delivery |
| What to confirm with the partner | Transaction versions, equipment rules and who reports each event | Which provider sends which events and how containers are identified |
Systems
How ECOM offerings connect your systems and your rail partners
The diagram replaces the earlier sample dashboard: it shows what ECOM connects, not a customer screen. Which offerings apply to a rail engagement is agreed during discovery, and each railroad’s own guideline governs the transactions.
Systems a rail EDI integration connects
Rail data starts in shipping and plant systems and ends in finance and planning systems. Integration scope typically covers the ones below.
| System | What flows | What to plan for |
|---|---|---|
| ERP and shipping system | Shipment instructions, bill of lading data, equipment orders and freight invoices. | Equipment numbers and commodity codes must be stored and reused exactly, not re-keyed. |
| TMS and logistics platform | Shipment plans, routing, status and equipment visibility. | ECOM integrates TMS environments including Oracle Transportation Management; connector availability depends on the product and version. |
| Yard, plant and terminal systems | Releases, placements, pulls and intermodal ramp events. | Event timing matters because partners measure dwell and transit from it. |
| Railroad and rail partner systems | Acknowledgments, waybills, interchange, scheduling and invoice transactions. | Each railroad defines its own versions, transaction mix and connection method. |
| Industry services | Waybill forwarding, event reporting and equipment tracking provided through rail industry services such as Railinc. | Participation and message rules come from the railroad and the service. |
| Freight audit and accounting | Rail invoices, payments and remittance. | Invoices are compared with the original bill of lading and agreed rates. |
Problems and exceptions
Rail integration problems and how ECOM addresses them
These are the problems that most often bring rail shippers and logistics teams to integration.
| Problem | Why it hurts | How ECOM addresses it |
|---|---|---|
| Manual shipment entry and disconnected systems | Bills of lading and equipment details are keyed into railroad systems, so errors creep in and the ERP, TMS and railroad records disagree. | Mapping from your shipping system or ERP to each railroad’s transaction version, with connectivity over the method the railroad supports, so data is entered once. |
| Rejected bills of lading and waybills | Invalid equipment numbers, commodity codes or missing hazardous materials data can stop a release and hold a car. | Validation before sending, rejection and error messages matched to the shipment, and scenario tests of corrections before go-live. |
| Rail equipment visibility gaps | Without movement, arrival and placement events in your own systems, planners phone the railroad to find a car. | Event and status data mapped into your TMS or visibility tools, with monitoring that flags cars with no expected event. |
| Interchange visibility gaps | Cars change railroads, and delays or missing advance notices at the handoff are hard to see from the shipper’s side. | Interchange and scheduling transactions captured and tracked against the shipment, with alerts when an expected message does not arrive. |
| Freight invoice discrepancies | Invoices that do not match the bill of lading, weights or agreed rate are disputed by hand and paid late. | Invoice data mapped to your ERP with shipment references intact, so it can be compared with what was tendered. |
| Slow railroad onboarding and version changes | Each railroad has its own guidelines and versions, and versions move on. One Class I railroad announced an upgrade of its 417, 418, 419, 420 and 421 requirements from version 8030 to 8050 effective February 11, 2025. | Specification review, reusable maps, partner testing and tracking through to production, then monitoring and 24×7 support as versions change. |
Handling rail exceptions before a car sits
Exceptions are normal in rail. What matters is that they are detected, routed to someone and corrected with the original shipment reference attached.
| Exception | Typical cause | How it is handled |
|---|---|---|
| Waybill diversion or correction | A change of route or consignee, or a data correction after the waybill was sent. | The change is sent as a correction or diversion with the original reference so every railroad on the route is updated. |
| Car not interchanged as scheduled | A missed handoff, a switching delay or a changed plan. | An alert when the expected interchange or updated arrival estimate does not arrive, with the car and routing attached. |
| Changed estimated time of arrival | Delays in transit or schedule changes. | Updated 421 data flows to planning systems so deliveries and consignee schedules adjust. |
Get started
How a rail EDI project works with ECOM
Every railroad and rail partner specifies its own requirements, so the work starts with your partner and the problem you are solving.
- 01
Tell us the railroad, systems and problem
Use the contact form or call, and describe who you ship with, which transactions you need and what is going wrong.
- 02
Review the guideline
An ECOM specialist reviews the railroad or partner guideline: transaction versions, required fields, equipment rules, connection method and test process.
- 03
Agree scope and approach
We outline the transactions, mapping, connections and testing involved, including whether carload, intermodal or both are in scope.
- 04
Build and test with the partner
Maps and connections are built, then tested with the partner using realistic scenarios such as multi-car shipments, corrections and rejections.
- 05
Go live and monitor
Production starts with monitoring in place, and 24×7 support is available with coverage defined in your service agreement.
Helpful to share, never required
- The railroad or rail partner you need to connect with
- Its EDI guideline or onboarding document, if you have one
- Your current systems, for example ERP, TMS, shipping and yard systems
- The transactions you need, for example 404, 417, 418, 421 or 410
- Whether the shipments are carload, intermodal or both
- The business problem you want to solve and your target timeline
Have a carrier specification? Send it for review Call Sales: 972-836-7750
Sources
Sources and related pages
Standards and partner requirements are revised over time, and each trading partner publishes its own. Confirm current versions with the partner before you build.
Standards and public sources
- ASC X12 transaction setsOfficial names and purposes of the 322, 404, 410, 417 to 422, 425, 426 and 456 transaction sets.
- ASC X12: 404 Rail Carrier Shipment InformationPurpose and usage of the 404.
- ASC X12: 426 Rail Revenue WaybillPurpose and usage of the 426.
- Union Pacific: EDI for customersHow one Class I railroad describes the 404 and 417 flow, Forward & Store and its version upgrade for the 417 to 421.
- Railinc: Guide for Railroads (May 2025)Forward & Store, the TRAIN II event reporting requirements, and Railinc’s role in rail EDI guidelines.
- Railinc: Product Descriptions (February 2025)Forward & Store, event reporting and equipment tracking products.
- U.S. CBP: ACE import manifest documentationX12 messages CBP lists for rail manifest filing.
Related pages
- EDI 404 Rail Carrier Shipment InformationThe tender and bill of lading in detail.
- EDI 417 Rail Carrier Waybill InterchangeWaybill interchange in detail.
- EDI 410 Rail Carrier Freight Details and InvoiceThe rail freight invoice in detail.
- EDI 322 Terminal Operations and Intermodal Ramp ActivityRamp ingates and outgates.
- Transportation and logistics EDIAll modes: truck, rail, ocean and air.
- Air cargo EDI and API integrationAir waybill, status and freight invoice integration.
- Ocean freight EDI and API integrationBooking, shipping instructions, VGM and container tracking.
- Hub Group trading partner guideAn intermodal and logistics provider guide.
- Trading partner onboardingHow certification and onboarding run.
- Carriers & Freight TransportationRoad, rail, ocean, air, intermodal and cross-border freight: freight onboarding, systems connectivity, exceptions and delivery evidence.
- Intermodal Transportation IntegrationIntegration for truck to rail to truck and truck to ocean to truck moves: references, equipment identifiers, handoff events, documents and exceptions.
- Logistics AutomationAutomate tenders, status updates, freight invoices and warehouse orders with logistics partners.
- Supply Chain VisibilityTrack orders, shipments and invoices across partners and catch exceptions early.
FAQs
Frequently asked questions
What is rail EDI?
Rail EDI is the exchange of standardized transactions between shippers, railroads and freight payers, such as bills of lading, waybills, interchange and scheduling messages, and invoices. Most use ANSI X12 transaction sets, and each railroad publishes its own implementation guidelines.
What is the EDI 404 rail transaction?
The 404 Rail Carrier Shipment Information is the initial tender of a shipment between a consignor and a rail carrier. It transmits rail-carrier-specific bill of lading information and can serve as notice that loaded equipment is released for movement. One Class I railroad states that the 404 is sent to the first road-haul railroad in the routing.
What is the difference between the 404 and the 417?
The 404 is sent by the shipper to a railroad to tender a shipment. The 417 Rail Carrier Waybill Interchange gives railroads movement instructions: the origin railroad sends it, and it is forwarded to the other railroads on the route. X12 describes the 417 as used by all Class I railroads in the United States and Canada.
What do the 418, 419 and 421 do?
The 418 gives advance information on equipment being interchanged to a connecting railroad. The 419 gives advance notice of cars offered for interchange, directly or through a switching carrier. The 421 exchanges car scheduling and estimated time of arrival between railroads.
What is the 426 Rail Revenue Waybill?
X12 describes the 426 as used to respond to a request for a rail revenue waybill, which a railroad needs to collect revenue from the paying parties. It is mostly exchanged between railroads, so shippers often do not send it themselves. Confirm with your railroad whether it applies to you.
Is intermodal EDI different from carload EDI?
Yes, in part. Intermodal moves add terminal and ramp activity, such as ingates and outgates reported in the 322, and many intermodal providers specify their own formats. Carload moves rely on the 404, 417 and interchange transactions. Many shippers run both, so scope each workflow separately.
What is Railinc Forward & Store?
Forward & Store is a rail industry system that receives waybill (417) messages from the origin railroad, checks them for format and syntax, and forwards them to the other railroads on the route. It acknowledges with a 997 or reports errors with an 824. Whether it applies to you depends on the railroad that sends your waybills.
What should I send ECOM to get started?
The railroad or rail partner you need to connect with, its EDI guideline if you have it, your current systems, the transactions you need, the business problem and your target timeline. You do not need a finished specification to start the conversation.
Discuss the rail transactions you need to send or receive
Tell us the railroad or rail partner, your systems and the problem you are trying to solve. An ECOM specialist will review the transactions, versions and testing involved.