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 · Catalogs and pricing

EDI 460 Railroad Price Distribution Request or Response

The X12 document used to request or communicate rail prices, rates and associated information, including rate dockets.

Sent by
Railroad, shipper or pricing agent
Received by
Railroad, shipper or pricing agent
Standard
ANSI ASC X12

What is an EDI 460?

The EDI 460 Railroad Price Distribution Request or Response is the ANSI X12 transaction set used to request or communicate prices, meaning rates and associated information, between two or more parties. It can send or respond to a rate docket, which includes maintenance status, qualifying conditions, geographic data and other rate details.

Rail rates are complex, with conditions by commodity, origin, destination, route and equipment. Distributing them electronically lets shippers and railroads rate shipments and audit freight bills consistently. Responses can include rates for several movements.

How the EDI 460 worksDiagram of the EDI 460 Railroad Price Distribution Request or Response. Railroad, shipper or pricing agent sends it to railroad, shipper or pricing agent. It usually follows 466. It is usually followed by 463 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information), DK (Docket Header) and the required SB loop with SB (Docket Level) and the required SC loop with SC (Docket Sub-level) and the required LX loop with LX (Transaction Set Line Number) and RS (Rate Subset). 2 optional loops are listed by their first segment.How the EDI 460 worksRailroad Price Distribution Request or Response: who sends it, where it fits and what the standard marksrequired1 WHERE IT FITSUSUALLY FOLLOWS466Rate RequestEDI 460SENDERRailroad, shipper orpricing agentRECEIVERRailroad, shipper orpricing agent997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY463Rail Rate Reply997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TPGS … GETransaction set 460ST … SEHEADINGRENRate Request InformationDKDocket HeaderRequired loop SB · repeats up to 50SBDocket LevelRequired loop SC · repeats up to 300SCDocket Sub-levelRequired loop LX · repeats up to 60LXTransaction Set Line NumberRSRate Subset+ 2 optional loops, starting with:PTR9Blue 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 460. Your trading partner's implementation guide adds its own requirements.
How the EDI 460 worksDiagram of the EDI 460 Railroad Price Distribution Request or Response. Railroad, shipper or pricing agent sends it to railroad, shipper or pricing agent. It usually follows 466. It is usually followed by 463 and 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information), DK (Docket Header) and the required SB loop with SB (Docket Level) and the required SC loop with SC (Docket Sub-level) and the required LX loop with LX (Transaction Set Line Number) and RS (Rate Subset). 2 optional loops are listed by their first segment.How the EDI 460 worksRailroad Price Distribution Request orResponse: who sends it, where it fits and whatthe standard marks required1 WHERE IT FITSUSUALLY FOLLOWS466Rate RequestEDI 460SENDERRailroad,shipper orpricing agentRECEIVERRailroad,shipper orpricing agent997 or 999 acknowledgment back, if the partnersagreeUSUALLY FOLLOWED BY463Rail Rate Reply997Functional Acknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDs (ISA… IEA)Functional group, ID code TP (GS … GE)Transaction set 460 (ST … SE)HEADINGRENRate Request InformationDKDocket Header+ required SB (SB) and 2 optional loops,starting with:PTR9Blue 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 460. Your trading partner'simplementation guide adds its own requirements.

How to read this diagram: the top row shows who sends the 460, 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 460 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 rail rates to shippers
  • Requesting rates for specific moves
  • Sharing rate dockets between railroads

Where it fits in the document flow

Usually follows 466 Rate Request
This document 460 Railroad Price Distribution Request or Response
Usually followed by 463 Rail Rate Reply997 Functional Acknowledgment

Structure

Mandatory segments in the 460 (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
  • REN
  • DK
  • PT
  • SB
  • SC
  • LX
  • RS
  • R9
  • R2B
  • SE

Practical example

The 460 in practice

A railroad agrees new contract rates with a plastics producer. It sends the producer a 460 with the rate docket: commodities, origins and destinations, rates per car and the conditions that apply. The producer's freight audit system loads the rates and later checks every freight bill against them.

Implementation

Implementation considerations for the 460

  • Load rates with their effective dates and conditions.
  • Reconcile loaded rate data with the freight bills.
  • Acknowledge receipt with a rate reply (463) where agreed.
  • Protect confidential contract rates in transit and storage.

How ECOM helps

Automate the 460 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

Logistics Automation

Automate tenders, status updates, freight invoices and warehouse orders with logistics partners.

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

Related transactions

Related catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 460?

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

Request a Demo Contact us