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 468 Rate Docket Journal Log

The X12 document used to transmit comments and associated data about rates contained in a rate docket.

Sent by
Railroad, pricing agent or shipper
Received by
Other parties to the rate docket
Standard
ANSI ASC X12

What is an EDI 468?

The EDI 468 Rate Docket Journal Log is the ANSI X12 transaction set used to transmit comments and associated data about rates contained in a rate docket.

Rate dockets go through proposals, reviews and approvals involving several parties. The journal log records comments, questions and notes about specific rates, so everyone working on the docket sees the same history. Comments can be attached to individual rate items or to the docket as a whole, and they remain part of its permanent record.

How the EDI 468 worksDiagram of the EDI 468 Rate Docket Journal Log. Railroad, pricing agent or shipper sends it to other parties to the rate docket. 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) and the required 0100 loop with DK (Docket Header). 0 optional loops are listed by their first segment.How the EDI 468 worksRate Docket Journal Log: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price DistributionRequest or ResponseEDI 468SENDERRailroad, pricing agentor shipperRECEIVEROther parties to therate docket997 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 468ST … SEHEADINGRENRate Request InformationRequired loop 0100 · repeats up to 100DKDocket HeaderBlue 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 468. Your trading partner's implementation guide adds its own requirements.
How the EDI 468 worksDiagram of the EDI 468 Rate Docket Journal Log. Railroad, pricing agent or shipper sends it to other parties to the rate docket. 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) and the required 0100 loop with DK (Docket Header). 0 optional loops are listed by their first segment.How the EDI 468 worksRate Docket Journal Log: who sends it, where itfits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price Distribution Request orResponseEDI 468SENDERRailroad, pricingagent or shipperRECEIVEROther parties tothe rate docket997 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 468 (ST … SE)HEADINGRENRate Request InformationRequired loop 0100 · repeats upto 100DKDocket HeaderBlue 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 468. Your trading partner'simplementation guide adds its own requirements.

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

  • Commenting on proposed rates
  • Recording notes during rate negotiations
  • Sharing the history of a rate docket

Where it fits in the document flow

Usually follows 460 Railroad Price Distribution Request or Response
This document 468 Rate Docket Journal Log
Usually followed by 997 Functional Acknowledgment

Structure

Mandatory segments in the 468 (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
  • SE

Practical example

The 468 in practice

Two railroads negotiate joint rates for an interline route. While reviewing the docket, one railroad sends a 468 commenting that a mileage block appears inconsistent with the route. The other railroad corrects the docket and records its reply in the journal log.

Implementation

Implementation considerations for the 468

  • Reference the docket and rate items commented on.
  • Keep the log as part of the docket history.
  • Use comments to resolve issues before rates take effect.
  • Agree which party maintains the journal log.

How ECOM helps

Automate the 468 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 468?

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

Request a Demo Contact us