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 463 Rail Rate Reply

The X12 document used to reply to a rail rate transaction with acceptance, rejection or other status from the receiving application.

Sent by
Receiver of a rail rate transaction
Received by
Sender of the rail rate transaction
Standard
ANSI ASC X12

What is an EDI 463?

The EDI 463 Rail Rate Reply is the ANSI X12 transaction set used to reply to a rail rate transaction from the receiver's application, based on the data content or business rules. It serves as an application acceptance, an application rejection or an indication of other status.

A rate transaction can be syntactically valid yet fail business checks, for example a reference to an unknown station or an overlap with existing rates. The rate reply tells the sender whether the rates were loaded and why not if rejected.

How the EDI 463 worksDiagram of the EDI 463 Rail Rate Reply. Receiver of a rail rate transaction sends it to sender of the rail rate transaction. It usually follows 460, 494 and 492. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information). 1 optional loops are listed by their first segment.How the EDI 463 worksRail Rate Reply: who sends it, where it fits and what the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price DistributionRequest or Response494Rail Scale Rates492Miscellaneous RatesEDI 463SENDERReceiver of a rail ratetransactionRECEIVERSender of the rail ratetransaction997 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 463ST … SEHEADINGRENRate Request Information+ 1 optional loop, starting with:DKBlue 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 463. Your trading partner's implementation guide adds its own requirements.
How the EDI 463 worksDiagram of the EDI 463 Rail Rate Reply. Receiver of a rail rate transaction sends it to sender of the rail rate transaction. It usually follows 460, 494 and 492. It is usually followed by 997. Inside the ISA, GS and ST envelopes, X12 release 008010 requires, in the heading: REN (Rate Request Information). 1 optional loops are listed by their first segment.How the EDI 463 worksRail Rate Reply: who sends it, where it fits andwhat the standard marks required1 WHERE IT FITSUSUALLY FOLLOWS460Railroad Price Distribution Request orResponse494Rail Scale Rates492Miscellaneous RatesEDI 463SENDERReceiver of arail ratetransactionRECEIVERSender of therail ratetransaction997 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 463 (ST … SE)HEADINGRENRate Request Information+ 1 optional loop, starting with:DKBlue 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 463. Your trading partner'simplementation guide adds its own requirements.

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

  • Accepting rates received
  • Rejecting rates that fail business rules
  • Reporting the status of rate processing

Where it fits in the document flow

Usually follows 460 Railroad Price Distribution Request or Response494 Rail Scale Rates492 Miscellaneous Rates
This document 463 Rail Rate Reply
Usually followed by 997 Functional Acknowledgment

Structure

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

Practical example

The 463 in practice

A shipper's audit system receives a 460 rate docket in which one rate references a station code it does not recognize. It loads the other rates and returns a 463 rejecting that item with the reason. The railroad corrects the station code and resends the rate.

Implementation

Implementation considerations for the 463

  • Give clear reasons for every rejected rate item.
  • Reference the rate items being answered.
  • Correct and resend rejected rates promptly.
  • Distinguish application replies from functional acknowledgments.

How ECOM helps

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

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

Request a Demo Contact us