972-836-7750 Request a demo Talk to an expert
Talk to an expert Request a demo Call sales 972-836-7750

X12 transaction guide · Finance

EDI 424 Rail Carrier Services Settlement

The X12 document a rail carrier uses to give another rail carrier the detailed charges for services performed on its behalf.

Sent by
Rail carrier that performed the services
Received by
Rail carrier on whose behalf the services were performed
Standard
ANSI ASC X12

What is an EDI 424?

The EDI 424 Rail Carrier Services Settlement is the ANSI X12 transaction set that provides detailed information on charges associated with rail services. A rail carrier sends it to the rail carrier on whose behalf the services were performed.

Railroads perform services for each other, such as switching cars at shared terminals, handling cars or providing equipment. The settlement lists each service with its charges, so the receiving carrier can verify and pay. Settlements are typically exchanged monthly between the carriers involved.

How the EDI 424 worksDiagram of the EDI 424 Rail Carrier Services Settlement. Rail carrier that performed the services sends it to rail carrier on whose behalf the services were performed. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BSW (Beginning Segment for Carrier's Services Settlement) and CUR (Currency). 1 optional loops are listed by their first segment.How the EDI 424 worksRail Carrier Services Settlement: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 424SENDERRail carrier thatperformed the servicesRECEIVERRail carrier on whosebehalf the serviceswere performed997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code SBGS … GETransaction set 424ST … SEHEADINGBSWBeginning Segment for Carrier's Services SettlementCURCurrency+ 1 optional loop, starting with:N1Blue box: required loop. Optional loops are listed by the segment that starts them; when a loop is used, that first segment is required. Optional segmentsoutside loops are not drawn.Structure: required segments and loops in the X12 008010 listing for the 424. Your trading partner's implementation guide adds its own requirements.
How the EDI 424 worksDiagram of the EDI 424 Rail Carrier Services Settlement. Rail carrier that performed the services sends it to rail carrier on whose behalf the services were performed. It usually starts the exchange. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BSW (Beginning Segment for Carrier's Services Settlement) and CUR (Currency). 1 optional loops are listed by their first segment.How the EDI 424 worksRail Carrier Services Settlement: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 424SENDERRail carrier thatperformed theservicesRECEIVERRail carrier onwhose behalfthe serviceswere performed997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code SB (GS … GE)Transaction set 424 (ST … SE)HEADINGBSWBeginning Segment forCarrier's Services SettlementCURCurrency+ 1 optional loop, starting with:N1Blue box: required loop. Optional loops are listedby the segment that starts them; when a loop isused, that first segment is required. Optionalsegments outside loops are not drawn.Structure: required segments and loops in the X12008010 listing for the 424. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 424, to whom, and which documents usually come before and after it. The lower part shows what X12 release 008010 itself requires: the envelopes around the 424 and the segments and loops the standard marks as required, area by area. Optional loops are listed by the segment that starts them rather than drawn in full. This is the standard's minimum, not a trading partner's requirement: each partner's implementation guide usually makes some optional loops mandatory, restricts the codes and may use a different release.

Expand diagram Download SVG

When it is used

  • Billing another railroad for switching services
  • Settling charges for services at joint facilities
  • Reporting detailed service charges

Where it fits in the document flow

This document 424 Rail Carrier Services Settlement
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 424 (X12 release 008010)

The segments X12 release 008010 marks as mandatory at their level, in order. Segments inside optional loops are needed only when the loop is used. This is the standard's requirement, not your trading partner's: each partner's implementation guide names the release it uses, adds the optional segments it requires and restricts the values. The requirement status comes from one published X12 reference listing and has not been checked against a second source.

  • ST
  • BSW
  • CUR
  • N1
  • CI
  • SWC
  • ED
  • SE

Practical example

The 424 in practice

A terminal railroad switches cars for three line-haul railroads at a busy interchange. Each month it sends each railroad a 424 listing the cars switched on its behalf, the services performed and the charges. The railroads verify the cars against their records and pay the settlements.

Implementation

Implementation considerations for the 424

  • List services by car so charges can be verified.
  • Apply the agreed rates for each type of service.
  • Reconcile settlements with interchange and switching records.
  • Resolve disputes within the agreed time periods.

How ECOM helps

Automate the 424 with ECOM

Industry

Trucking and Transportation

Load tenders, responses, status and freight invoices for carriers, brokers and shippers, integrated with the TMS.

Solution

Financial Document Automation

Automate invoices, remittances, payment files and bank statements from capture to posting.

Solution

EDI Integration

Exchange X12 and EDIFACT documents with partners and integrate them directly with your ERP.

More general questions about EDI are answered in the EDI FAQ.

Related transactions

Related finance documents

All 58 finance documents

Need help with the EDI 424?

ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.

Request a Demo Contact us