X12 transaction guide · Catalogs and pricing

EDI 432 Rail Car Hire Rate Negotiation

The X12 document fleet owners use to distribute new car hire rates to other participants.

Sent by
Rail car fleet owner
Received by
Railroads and other participants
Standard
ANSI ASC X12

What is an EDI 432?

The EDI 432 Rail Car Hire Rate Negotiation is the ANSI X12 transaction set fleet owners use to distribute new car hire rates to other participants.

Car hire rates determine what a railroad pays a car owner for each hour and mile the car spends on its lines. When owners set or negotiate new rates, every railroad that may use the cars needs them to calculate settlements, which are then exchanged with the 414. Owners may negotiate rates with users under industry rules.

How the EDI 432 worksDiagram of the EDI 432 Rail Car Hire Rate Negotiation. Rail car fleet owner sends it to railroads and other participants. It usually starts the exchange. It is usually followed by 414 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and BLR (Transportation Carrier Identification). 1 optional loops are listed by their first segment.How the EDI 432 worksRail Car Hire Rate Negotiation: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 432SENDERRail car fleet ownerRECEIVERRailroads and otherparticipants997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY414Rail Carhire Settlements997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code RXGS … GETransaction set 432ST … SEHEADINGBGNBeginning SegmentBLRTransportation Carrier Identification+ 1 optional loop, starting with:LXBlue 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 432. Your trading partner's implementation guide adds its own requirements.
How the EDI 432 worksDiagram of the EDI 432 Rail Car Hire Rate Negotiation. Rail car fleet owner sends it to railroads and other participants. It usually starts the exchange. It is usually followed by 414 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: BGN (Beginning Segment) and BLR (Transportation Carrier Identification). 1 optional loops are listed by their first segment.How the EDI 432 worksRail Car Hire Rate Negotiation: who sends it,where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWSStarts the exchangeEDI 432SENDERRail car fleetownerRECEIVERRailroads andotherparticipants997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY414Rail Carhire Settlements997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code RX (GS … GE)Transaction set 432 (ST … SE)HEADINGBGNBeginning SegmentBLRTransportation CarrierIdentification+ 1 optional loop, starting with:LXBlue 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 432. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 432, 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 432 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

  • Distributing new car hire rates
  • Announcing rate changes for a fleet
  • Supporting car hire settlement calculations

Where it fits in the document flow

This document 432 Rail Car Hire Rate Negotiation

Structure

Mandatory segments in the 432 (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
  • BGN
  • BLR
  • LX
  • CIC
  • SE

Practical example

The 432 in practice

A leasing company acquires 2,000 new tank cars and sets their car hire rates. It sends railroads a 432 with the rates by car group and the effective date. The railroads load the rates so the next car hire settlements use them.

Implementation

Implementation considerations for the 432

  • State the effective date of each rate clearly.
  • Identify the cars or car groups each rate applies to.
  • Keep rate tables synchronized with settlements.
  • Follow the industry's car hire rules and timelines.

Need help with the EDI 432?

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