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 434 — Railroad Mark Register Update Activity

The 434 carries Railroad Mark Register updates: additions, changes, and withdrawals of equipment identifiers (marks) between rail carriers and administration entities.

Purpose

The 434 documents reference-data movements on the Railroad Mark Register, the AAR / Railinc-maintained registry that assigns and tracks marks (owner prefixes for cars and locomotives). It carries the mark, the action (add, change, withdraw), the owner, the effective date, and attributes (equipment type, serial range).

It is an administrative reference transaction, not an operational cargo flow. It is used in the Class I circuit and lessors (TTX, GATX, Trinity) to maintain registry consistency. Acknowledged by 997.

Envelope structure

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

x12 example-434.x12 
ISA*00*          *00*          *ZZ*AAR           *ZZ*BNSF          *260514*1200*U*00401*000000434*0*P*>~
GS*MR*AAR*BNSF*20260514*1200*1*X*004010~
ST*434*0001~
BMR*00*MR-2026-7741*20260514~
N1*PR*ASSOCIATION OF AMERICAN RAILROADS*92*AAR~
N1*RE*BNSF RAILWAY*92*BNSF~
LX*1~
REF*ZZ*MARK-BNSF~
DTM*007*20260601~
MSG*Add hopper car range BNSF-552000 to BNSF-552999~
SE*9*0001~
GE*1*1~
IEA*1*000000434~

Common segments

  • Header — ST, BMR (Beginning Segment for Mark Register), DTM.
  • Parties — N1*PR (Provider / registry authority), N1*RE (Reporting Party).
  • Activity — LX loop with REF*ZZ (mark identifier), DTM, MSG (action description).
  • Summary — SE.

Common pitfalls

  • Serial range: a range must be encoded either exhaustively or with clear bounds in MSG; an ambiguous text breaks deduplication on the registry side.
  • Effective date: DTM*007 (effective from) is mandatory; without it, the registry applies the receipt date, which can create overlaps with an existing mark.
  • Owner vs lessor: the mark belongs to the owner; a lessor cannot alter the mark alone — the 434 must be co-signed by the owner or rejected.

Documentation

The code 434 and the name Railroad Mark Register Update Activity 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.