Carriers integration

CSX Transportation EDI integration

How EDI and API integration with CSX Transportation typically works: documents, workflows, onboarding and common problems, as typical practice to confirm with CSX Transportation.

At a glance

CSX Transportation integration, in three pictures

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

Illustration of a locomotive pulling freight cars, representing the carriers industry that CSX Transportation operates in.
Industry. Carriers: where CSX Transportation operates.
Workflow diagram: your TMS, ERP and finance systems exchange documents with CSX Transportation through ECOM. You send 404; you receive 214, 322; 997 acknowledgments go both ways. Your systems TMS · ERP · finance ECOM integration map · validate · connect · monitor CSX Transportation 404 404 214 322 214 322 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 CSX Transportation

Tell us which documents you exchange with CSX Transportation, 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 CSX Transportation.

  • Review of CSX Transportation'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
CSX Transportation

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 CSX Transportation integration fits your systems

Your systemsTMS, ERP and accounting
ECOMMapping, validation, connectivity and monitoringAS2, SFTP or VAN · Carrier API · Portal or TMS network
CSX TransportationIts program, documents and requirements
  1. ConfirmConfirm your CSX Transportation 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 CSX Transportation integration

Who this is for: Shippers, intermodal marketing companies and logistics providers that move freight by rail with CSX Transportation, and their transportation and finance teams.

Scope: This guide describes typical practice for this kind of trading relationship; CSX Transportation's own program details are confirmed during onboarding.

CSX Transportation is a freight railroad. ECOM's directory lists it under rail. Shippers and logistics providers working with railroads typically send shipment information, receive status events and ramp or terminal activity, and settle charges through the railroad's billing process.

With a railroad, the difficulty is keeping tenders, status events and invoices consistent with each other, and noticing a missing message early. CSX Transportation's own EDI or API specification is not part of this guide and no CSX Transportation document was read: treat what follows as typical practice for a railroad, and confirm the documents, X12 version, delivery method and testing steps with CSX Transportation.

ECOM maps the documents to your TMS, ERP and finance systems, tests them with the trading partner, monitors every file after go-live and handles partner changes, as software, as a managed service or both.

Business scenarios

Where CSX Transportation integration gets complicated

Typical requirements—confirm with your trading partner.

Car and container tracking

Cars and containers move across a network with many events. Identifiers must match between shipper, railroad and logistics provider.

How ECOM helps: ECOM connects tender, response and status messages (214) to your TMS or ERP and shows where each load stands, flagging missing or late status.

What you gain: Planners see current load status, and late or missing messages are noticed early.

Intermodal ramp activity

Ramp events show gate-in, load and release, helping plan drayage.

How ECOM helps: ECOM maps the documents to your systems and monitors every exchange, as software, as a managed service or both, so your team handles exceptions instead of re-keying.

What you gain: Less manual work and fewer surprises after go-live.

Cars, waybills and network events

Rail moves are tracked by car or container and waybill across a network, and charges follow the railroad's billing rules.

How ECOM helps: ECOM maps freight invoice and payment data to your ERP and finance systems and matches each charge to the load it belongs to, with differences listed for review.

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

Appointment and detention

Appointment data and dwell time affect detention charges.

How ECOM helps: ECOM matches freight invoices to the tender and status (214) history and lists charges that differ from the agreed rate or have no supporting event, so they can be reviewed before payment.

What you gain: Fewer overcharges paid, and less manual freight audit work.

Workflows

Typical CSX Transportation business workflows

Typical requirements—confirm with your trading partner. Typical flows in this industry, not CSX Transportation's published process.

Shipment to status

  1. 1Send 404 shipment information
  2. 2Railroad moves the car or load
  3. 3Receive 214 status
  4. 4Reconcile charges

Intermodal activity

  1. 1Load at the ramp
  2. 2Receive 322 terminal activity
  3. 3Match to the booking
  4. 4Plan the final leg

Documents and APIs

CSX Transportation documents by program

General guidance. We could not verify CSX Transportation's EDI requirements from a published source, so these are documents commonly exchanged in this industry, not CSX Transportation's confirmed requirements. Confirm the list, versions and programs with CSX Transportation.

DocumentNameDirectionProgramStatusPurpose
404 Rail Carrier Shipment Information To CSX Transportation Not stated General guidance Typically gives a railroad the shipment details it needs to move and bill a car or load.
214 Transportation Carrier Shipment Status Message From CSX Transportation Not stated General guidance Typically reports pickup, location updates and delivery.
322 Terminal Operations and Intermodal Ramp Activity From CSX Transportation Not stated General guidance Typically reports gate, ramp and container activity at terminals.
997 Functional Acknowledgment Both directions Not stated General guidance Typically confirms that each file was received and could be read.

Connectivity

How companies connect

  • AS2, SFTP or VAN

    Carriers and brokers commonly exchange EDI over AS2, SFTP or a value-added network.

    General guidance

  • Carrier API

    Many carriers also expose tracking, rating or tender APIs next to EDI.

    General guidance

  • Portal or TMS network

    Some carriers and brokers work through a customer portal or a transportation management network instead of, or beside, direct EDI.

    General guidance

Challenges

Common integration challenges

  • Identifiers

    Car, container and waybill references must connect.

  • Status gaps

    Events may arrive late or in a different format.

  • Billing

    Charges follow rail tariffs. Ask CSX Transportation how this applies to your program.

  • Multiple railroads

    A move can use more than one railroad. Requirements vary by program.

  • Program-specific details

    The documents, identifiers, versions and test steps for your program are set by CSX Transportation. ECOM works from them during mapping and testing.

Automation options for CSX Transportation shippers

Four ways to automate. One foundation.

ECOM helps you automate the exchange, connect it to your systems, and see what needs action. CSX Transportation 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 CSX Transportation typically works

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

  1. 404 Rail Carrier Shipment Information

    From you to CSX Transportation

    Typically gives a railroad the shipment details it needs to move and bill a car or load.

  2. 214 Transportation Carrier Shipment Status Message

    From CSX Transportation to you

    Typically reports pickup, location updates and delivery.

  3. 322 Terminal Operations and Intermodal Ramp Activity

    From CSX Transportation to you

    Typically reports gate, ramp and container activity at terminals.

  4. 997 Functional Acknowledgment

    Both directions

    Typically confirms that each file was received and could be read.

Need help with the specification?

Tell ECOM which program you are in and what the partner has given you. We help you read it, confirm the applicable requirements, map them to your systems and test against them. Do not send passwords or EDI identifiers with your request.

Next step

Get help with your CSX Transportation program

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

  • Review CSX Transportation's requirements

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

    Request a requirements review
  • Connect CSX Transportation 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 CSX Transportation document, then go live with monitoring from the first file.

    Plan testing and certification

CSX Transportation integration FAQs

Does CSX Transportation use EDI with shippers?

Railroads commonly exchange EDI with shippers and logistics providers. This page does not include CSX Transportation's requirements.

Which documents are typical for rail shipments?

Typically shipment information, status messages and, for intermodal, terminal activity. Exact usage varies by railroad and program.

Which EDI documents are typical for carriers?

Typical documents are 404, 214, 322, 997. That is general practice, not CSX Transportation's published list.

How does onboarding with CSX Transportation usually work?

Typically you get the specification from the trading partner, agree the connection, map to your systems, test until the partner accepts the documents, then go live with monitoring. Timing depends on CSX Transportation's requirements, test cycles and your ERP.

Does this guide mean CSX Transportation endorses ECOM?

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

Sources and accuracy

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

  • ASC X12: transaction set reference (standards body) Standards reference
  • CSX Transportation: company description Background, not checked against a company source The one-sentence description of CSX Transportation comes from general public knowledge and was not checked against CSX Transportation's own website for this page.
  • CSX Transportation: no company document read Background, not checked against a company source No CSX Transportation supplier, customer or integration document was read for this page. Everything shown is typical practice for this type of company.

Request CSX Transportation integration assistance

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