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 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.
When it is used
- Concurring in a joint rate proposal
- Changing rate factors
- Rejecting or tracing proposals
Where it fits in the document flow
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
Transportation and Logistics
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
- 460Railroad Price Distribution Request or Response
- 486Rate Docket Expiration
- 490Rate Group Definition
- 492Miscellaneous Rates
- 494Rail Scale Rates
- 129Vehicle Carrier Rate Update
- 218Motor Carrier Tariff Information
- 432Rail Car Hire Rate Negotiation
- 463Rail Rate Reply
- 466Rate Request
- 468Rate Docket Journal Log
- 602Transportation Services Tender
From the guide to go-live
Put this into practice with ECOM
Reading about EDI is the first step. When you are ready to meet a trading partner's requirements, an ECOM specialist can help.
-
EDI compliance help
Check documents against the partner's rules before they are sent, and find out why labels, ship notices or invoices are rejected or short-paid for EDI 485.
-
EDI implementation
Map, test and certify the documents for EDI 485, and connect them to your ERP, warehouse or order system.
-
Managed EDI
Have ECOM run the day-to-day EDI: monitoring, error handling and new trading partner setup.
Need help with the EDI 485?
ECOM maps, tests and monitors X12 documents for your trading partners and integrates them with your ERP.