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 486 Rate Docket Expiration

The X12 document used to transmit the expiration date of a rate docket.

Sent by
Railroad or rate publisher
Received by
Shippers, railroads and other rate users
Standard
ANSI ASC X12

What is an EDI 486?

The EDI 486 Rate Docket Expiration is the ANSI X12 transaction set used to transmit the expiration date of a docket.

Rates in a docket apply until they expire. Communicating expirations electronically lets shippers' rating and audit systems stop using expired rates on time and alerts them to negotiate replacements before shipments move without an agreed rate. Expired rates must no longer be applied to shipments, so rating and audit systems need the expiration dates as soon as they are set. Expiration notices also prompt shippers and railroads to negotiate replacement rates in good time.

How the EDI 486 worksDiagram of the EDI 486 Rate Docket Expiration. Railroad or rate publisher sends it to shippers, railroads and other rate users. It usually follows 460. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information), DR (Docket Range) and SA (Status Action). 0 optional loops are listed by their first segment.How the EDI 486 worksRate Docket Expiration: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price DistributionRequest or ResponseEDI 486SENDERRailroad or ratepublisherRECEIVERShippers, railroads andother rate users997 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 486ST … SEHEADINGRENRate Request InformationDRDocket RangeSAStatus ActionBlue 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 486. Your trading partner's implementation guide adds its own requirements.
How the EDI 486 worksDiagram of the EDI 486 Rate Docket Expiration. Railroad or rate publisher sends it to shippers, railroads and other rate users. It usually follows 460. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information), DR (Docket Range) and SA (Status Action). 0 optional loops are listed by their first segment.How the EDI 486 worksRate Docket Expiration: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price Distribution Request orResponseEDI 486SENDERRailroad or ratepublisherRECEIVERShippers,railroads andother rate users997 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 486 (ST … SE)HEADINGRENRate Request InformationDRDocket RangeSAStatus ActionBlue 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 486. Your trading partner'simplementation guide adds its own requirements.

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

  • Announcing the expiration of a rate docket
  • Changing a docket's expiration date
  • Alerting users to renegotiate rates

Where it fits in the document flow

Usually follows 460 Railroad Price Distribution Request or Response
This document 486 Rate Docket Expiration
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 486 (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
  • DR
  • SA
  • SE

Practical example

The 486 in practice

A railroad's contract rates with a customer are due to end at the close of the year. It sends a 486 with the docket's expiration date. The customer's freight audit system flags the expiring rates, and its logistics team starts renewal talks.

Implementation

Implementation considerations for the 486

  • Load expiration dates into rating and audit systems.
  • Alert commercial teams ahead of expirations.
  • Make sure replacement rates are loaded in time.
  • Reference the rate docket exactly as published.

How ECOM helps

Automate the 486 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 catalogs and pricing documents

All 21 catalogs and pricing documents

Need help with the EDI 486?

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

Request a Demo Contact us