Skip to content
X12 Inbound

Union Pacific Railroad X12 410 Rail Carrier Freight Details and Invoice

X12 410 (Rail Carrier Freight Details and Invoice) is the EDI transaction exchanged between Union Pacific Railroad and its trading partners. Stacksync handles full compliance, mapping, and real-time delivery.

Segments
19
Loops
4
X12 410
All partners ↗

Schema reference

19 segments · 4 loops · X12 410 Rail Carrier Freight Details and Invoice

ISA

ISA Interchange Control Header

GS

GS Functional Group Header

ST

Transaction Set Header

B3B

Beginning Segment for Carrier's Invoice

N9

Reference Identification

Loop
N7

Equipment Details

N8

Waybill Reference

F9

Origin Station

D9

Destination Station

Loop
N1

Name

N2

Additional Name Information

N3

Address Information

N4

Geographic Location

Loop
LX

Assigned Number

L5

Description, Marks and Numbers

Loop
L0

Line Item - Quantity and Weight

L1

Rate and Charges

L3

Total Weight and Charges

SE

Transaction Set Trailer

Union Pacific Railroad EDI 410 FAQ

Common questions about 410 Rail Carrier Freight Details and Invoice with Union Pacific Railroad.

What is X12 410 Rail Carrier Freight Details and Invoice?
X12 410 (Rail Carrier Freight Details and Invoice) is the EDI transaction set used to exchange rail carrier freight details and invoice data. Union Pacific Railroad requires it from trading partners.
Does Union Pacific Railroad require 410 for trading partners?
Yes — Union Pacific Railroad supports X12 410 Rail Carrier Freight Details and Invoice. Stacksync handles the full integration so your team can focus on operations.
How fast can I integrate Union Pacific Railroad 410 with Stacksync?
Most companies go live with Union Pacific Railroad 410 on Stacksync in days. Pre-built mappings, no-code setup, and real-time monitoring make EDI compliance straightforward.

Ready to automate your Union Pacific Railroad EDI?

Most teams go live in days, not months. Talk to our team and we'll walk you through your specific setup.