X12 420 — Car Handling Information
The 420 carries car-handling instructions between rail carriers: switching, spotting, holding, sorting, classification orders.
Purpose
The 420 documents operational instructions between an issuing carrier and a receiving carrier or yard operator: car move within yard, industrial spot at a private consignee siding, classification, holding. It is the B2B instrument for rail handling operations.
It triggers downstream billing transactions (424 — Rail Carrier Services Settlement) and feeds yard-management operational systems. Acknowledged by 997, its operational accuracy drives correct accessorial billing.
Envelope structure
The 420 travels within the three X12 envelope levels (ISA/IEA,
GS/GE with functional group CH, and ST/SE).
Didactic example in release 004010:
ISA*00* *00* *ZZ*BNSF *ZZ*UPRR *260514*0830*U*00401*000000420*0*P*>~
GS*CH*BNSF*UPRR*20260514*0830*1*X*004010~
ST*420*0001~
ZD*ZZ*WB-26-44071*BNSF*HOPPER*BNSF-552032*RX*LD*20260514~
N7*HOPPER*BNSF-552032*LD~
N1*CA*BNSF RAILWAY*92*BNSF~
N1*CA*UNION PACIFIC*92*UPRR~
M7*CL*M7TYPE~
LX*1~
DTM*010*20260515~
MSG*Spot at ACME MILL INC private siding KC-22~
SE*9*0001~
GE*1*1~
IEA*1*000000420~ Common segments
- Header —
ST,ZD(Beginning Segment for Car Handling),DTM. - Equipment —
N7withLD/MTstatus and equipment type. - Parties —
N1*CAissuer / receiver. - Action —
LXloop withDTM(action date),MSG(instruction). - Summary —
SE.
Common pitfalls
- Action code:
ZDelement 01 must carry the exact action code (spot, hold, classify) — a generic code prevents yard-operator planning. - Siding identifier: encode the private siding via an AAR code or a receiver-known local identifier; a free-text name in
MSGis ignored by automated systems. - Operational timing:
DTMmust reflect a realistic operational window — a past-datedDTMtriggers an 824 rejection.
Related transactions
Documentation
The code 420 and the name Car Handling Information 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.