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 485 Ratemaking Action

The X12 document used to transmit ratemaking activities such as concurrence, factor changes, publisher changes and proposal rejections.

Sent by
Railroad or rate publisher
Received by
Other railroads or publishers
Standard
ANSI ASC X12

What is an EDI 485?

The EDI 485 Ratemaking Action is the ANSI X12 transaction set used to transmit ratemaking activities related to concurrence, factor changes, publisher changes, proposal rejection or trace.

Joint rail rates over several railroads need each carrier's concurrence. Ratemaking actions record who agreed, what changed and which proposals were rejected, so all parties publish consistent rates. Each action records the parties involved, the rates affected and the effective date, so that the history of a joint rate can be reconstructed later. This matters in disputes over which rate applied to a shipment and when.

How the EDI 485 worksDiagram of the EDI 485 Ratemaking Action. Railroad or rate publisher sends it to other railroads or publishers. It usually follows 460. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: DK (Docket Header) and SA (Status Action). 1 optional loops are listed by their first segment.How the EDI 485 worksRatemaking Action: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price DistributionRequest or ResponseEDI 485SENDERRailroad or ratepublisherRECEIVEROther railroads orpublishers997 or 999 acknowledgment back, if the partners agreeUSUALLY FOLLOWED BY997FunctionalAcknowledgment2 WHAT X12 RELEASE 008010 REQUIRESInterchange: sender and receiver IDsISA … IEAFunctional group, ID code TPGS … GETransaction set 485ST … SEHEADINGDKDocket HeaderSAStatus Action+ 1 optional loop, starting with:SCBlue 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 485. Your trading partner's implementation guide adds its own requirements.
How the EDI 485 worksDiagram of the EDI 485 Ratemaking Action. Railroad or rate publisher sends it to other railroads or publishers. It usually follows 460. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: DK (Docket Header) and SA (Status Action). 1 optional loops are listed by their first segment.How the EDI 485 worksRatemaking Action: who sends it, where it fitsand what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price Distribution Request orResponseEDI 485SENDERRailroad or ratepublisherRECEIVEROther railroadsor publishers997 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 TP (GS … GE)Transaction set 485 (ST … SE)HEADINGDKDocket HeaderSAStatus Action+ 1 optional loop, starting with:SCBlue 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 485. Your trading partner'simplementation guide adds its own requirements.

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

  • Concurring in a joint rate proposal
  • Changing rate factors
  • Rejecting or tracing proposals

Where it fits in the document flow

Usually follows 460 Railroad Price Distribution Request or Response
This document 485 Ratemaking Action
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 485 (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
  • DK
  • SA
  • SC
  • RA
  • MC
  • SE

Practical example

The 485 in practice

A railroad proposes a joint rate with a connecting carrier. The connecting carrier reviews it and sends a 485 concurring with the proposal. The originating railroad publishes the joint rate with both carriers' agreement recorded.

Implementation

Implementation considerations for the 485

  • Reference the proposal or docket concerned.
  • Record the effective date of each action.
  • Keep a full history of concurrences for each rate.
  • Follow rail industry ratemaking procedures.

How ECOM helps

Automate the 485 with ECOM

Industry

Trucking and Transportation

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

Solution

EDI Integration

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

Solution

Financial Document Automation

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

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 485?

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

Request a Demo Contact us