Overview
Understanding Union Pacific Railroad integration
Who this is for: Shippers, intermodal marketing companies and logistics providers that ship by rail with Union Pacific, and the transportation and finance teams that tender shipments and pay freight invoices.
Scope: Union Pacific's public pages do not describe EDI testing or onboarding steps, or name other documents such as 322 or 214. Those are not shown as Union Pacific documents.
A shipment with Union Pacific starts with your 404, the shipping instruction (bill of lading) that you create in EDI software and send to the first road-haul railroad in the routing. Union Pacific returns an acknowledgment, and the first road haul then passes the shipment to the other carriers in the routing. The waybill moves as a 417: it is sent to Railinc's Forward and Store system, which forwards it to the other road-haul carriers on the route. Freight invoices are handled as 410s through Union Pacific's e-invoicing contact.
Union Pacific has changed requirements recently. Customer notice CN2025-1 (January 27, 2025) moved its inter-carrier requirements from version 8030 to 8050, effective February 11, 2025, aligned with Railinc's Forward and Store upgrade. The 417s Union Pacific sends carry version 8050, and loaded bills of lading (404s) must now include a weight in the N7 segment. Customers who tender 404s are not required to upgrade their version, but the weight requirement applies during validation. The page also expects rail trading partners to use one of the two most current versions, and says Rail Industry EDI Implementation guidelines are ordered from Washington Publishing Company. It describes a value-added network option and mentions specialist EDI providers for help.
ECOM maps your 404 and 410 data to your TMS, ERP and payables systems, adds the weight and identifier checks before sending, tests and monitors every file after go-live, as software, as a managed service or both.