ediverse

Type to search across standards, messages, tools and glossary.

ediverse Explore the platform

Spotlight PEPPOL BIS Billing 3.0 The EU e-invoicing mandate is here — France Sept 2026, Belgium Jan 2026, Germany 2025.

— 01

Foundations

— 02

Standards

— 03

Flagship messages

— 04

Tools

X12 475 — Rail Route File Maintenance

The 475 maintains the route file table published by a railroad — create, update, delete — for shippers and 3PL pricing / routing systems.

Purpose

The 475 documents updates to a railroad route file: new corridor addition, junction modification, abandoned route removal, mileage update. It feeds the shipper routing database.

It is essential for correct revenue mileage computation, which drives the tariff. Acknowledged by 997. Emitted periodically by each Class I railroad.

Envelope structure

The 475 travels within the three X12 envelope levels (ISA/IEA, GS/GE with functional group GF, and ST/SE). Didactic example in release 004010:

x12 example-475.x12 
ISA*00*          *00*          *ZZ*RAILROAD      *ZZ*SHIPPER       *260515*1400*U*00401*000000475*0*P*>~
GS*GF*RAILROAD*SHIPPER*20260515*1400*1*X*004010~
ST*475*0001~
BGN*00*RTM-2026-Q2*20260515~
N1*RR*BNSF RAILWAY*24*EIN-BNSF~
DTM*090*20260601~
LX*1~
N4*FORT WORTH*TX*76101~
N4*HOUSTON*TX*77001~
REF*ZZ*ACTION-UPDATE~
AMT*MI*282~
SE*9*0001~
GE*1*1~
IEA*1*000000475~

Common segments

  • Header — ST, BGN.
  • Railroad — N1*RR.
  • Effective date — DTM*090.
  • Routes — LX loop: N4 (origin), N4 (destination), REF*ZZ (ACTION: ADD/UPDATE/DELETE), AMT*MI (mileage), REF*ZZ (junction).
  • Summary — SE.

Common pitfalls

  • ADD vs UPDATE confusion: an UPDATE on an existing mileage replaces it; an ADD on an existing route creates a duplicate — semantically distinct.
  • Effective date: a 475 issued on the 1st with effective the 1st of next month gives shippers time to sync; same-day effective breaks active bookings.
  • Junction key: without the official AAR Junction Point Code, a multi-rail 475 is not parseable — use the official codes.

Documentation

The code 475 and the name Rail Route File Maintenance are public and listed on x12.org/products/transaction-sets. The complete structure of loops, qualifiers and code lists is distributed by DISA via the proprietary Implementation Guides (TR3). ediverse.io covers only public concepts, the envelope and didactic examples.