Union Pacific Railroad EDI 404 Rail Carrier Shipment Information

Schema Reference

20 segments · X12 404 Rail Carrier Shipment Information

ISA01 Authorization Information Qualifier

M ID 2-2

ISA02 Authorization Information

M AN 10-10

ISA03 Security Information Qualifier

M ID 2-2

ISA04 Security Information

M AN 10-10

ISA05 Interchange ID Qualifier

M ID 2-2

ISA06 Interchange Sender ID

M AN 15-15

ISA07 Interchange ID Qualifier

M ID 2-2

ISA08 Interchange Receiver ID

M AN 15-15

ISA09 Interchange Date

M DT 6-6

ISA10 Interchange Time

M TM 4-4

ISA11 Interchange Control Standards Identifier

M ID 1-1

ISA12 Interchange Control Version Number

M ID 5-5

ISA13 Interchange Control Number

M N0 9-9

ISA14 Acknowledgment Requested

M ID 1-1

ISA15 Usage Indicator

M ID 1-1

GS01 Functional Identifier Code

M ID 2-2

GS02 Application Sender's Code

M AN 2-15

GS03 Application Receiver's Code

M AN 2-15

GS04 Date

M DT 8-8

GS05 Time

M TM 4-8

GS06 Group Control Number

M N0 1-9

GS07 Responsible Agency Code

M ID 1-2

GS08 Version / Release / Industry Identifier Code

M AN 1-12

ST01 Transaction Set Identifier Code

M ID 3-3

ST02 Transaction Set Control Number

M AN 4-9

BX01 Transaction Set Purpose Code

M ID 2-2

BX02 Transportation Method/Type Code

M ID 1-2

BX03 Shipment Method of Payment

M ID 2-2

BX04 Shipment Identification Number

O AN 1-30

BX05 Standard Carrier Alpha Code

O ID 2-4

BX06 Weight Unit Code

O ID 1-1

BX07 Shipment Qualifier

O ID 1-1

BNX01 Shipment Weight Code

O ID 1-1

BNX02 Referenced Pattern Identifier

O AN 1-13

BNX03 Billing Code

O ID 1-1

BNX04 Repetitive Pattern Number

O N0 5-5

M301 Release Code

M ID 1-1

M302 Date

C DT 8-8

M303 Time

C TM 4-8

M304 Time Code

O ID 2-2

N901 Reference Identification Qualifier

M ID 2-3

N902 Reference Identification

C AN 1-30

N7 Loop Repeat: 500

N701 Equipment Initial

O AN 1-4

N702 Equipment Number

M AN 1-10

N703 Weight

C R 1-10

N704 Weight Qualifier

C ID 1-2

N711 Equipment Description Code

O ID 2-2

F902 City Name

M AN 2-30

F903 State or Province Code

M ID 2-2

D902 City Name

M AN 2-30

D903 State or Province Code

M ID 2-2

N1 Loop Repeat: 10

N101 Entity Identifier Code

M ID 2-3

N102 Name

C AN 1-60

N103 Identification Code Qualifier

C ID 1-2

N104 Identification Code

C AN 2-80

N201 Name

M AN 1-60

N202 Name

O AN 1-60

N301 Address Information

M AN 1-55

N302 Address Information

O AN 1-55

N401 City Name

O AN 2-30

N402 State or Province Code

O ID 2-2

N403 Postal Code

O ID 3-15

N404 Country Code

O ID 2-3

R201 Standard Carrier Alpha Code

M ID 2-4

R202 Routing Sequence Code

M ID 1-2

R203 City Name

O AN 2-30

LX Loop Repeat: 25

LX01 Assigned Number

M N0 1-6

L501 Lading Line Item Number

O N0 1-3

L502 Lading Description

O AN 1-50

L503 Commodity Code

C AN 1-30

L504 Commodity Code Qualifier

C ID 1-1

L0 Loop Repeat: 25

L001 Lading Line Item Number

O N0 1-3

L004 Weight

C R 1-10

L005 Weight Qualifier

C ID 1-2

L006 Volume

C R 1-8

L007 Volume Unit Qualifier

C ID 1-1

L008 Lading Quantity

C N0 1-7

L009 Packaging Form Code

C ID 3-3

L011 Weight Unit Code

O ID 1-1

PI01 Reference Identification Qualifier

M ID 2-3

PI02 Reference Identification

M AN 1-30

PI03 Primary Publication Authority Code

O ID 2-2

PI05 Tariff Agency Code

O ID 1-4

PI06 Issuing Carrier Identifier

O AN 1-10

SE01 Number of Included Segments

M N0 1-10

SE02 Transaction Set Control Number

M AN 4-9

Automating Union Pacific Railroad EDI 404

Stacksync validates, transforms, and delivers your 404 transactions automatically — so your team can focus on operations, not EDI compliance.

Validate

Transform

Route

Monitor

Stacksync processes Union Pacific Railroad EDI 404 (Rail Carrier Shipment Information) documents automatically — syncing data to your system in real time with no manual intervention required.

Union Pacific Railroad EDI 404 FAQ

Common questions about 404 Rail Carrier Shipment Information transactions with Union Pacific Railroad.

How long does it take to set up Union Pacific Railroad EDI with Stacksync?

Most suppliers are fully connected and processing live Union Pacific Railroad EDI transactions within 3–5 business days. Stacksync's no-code setup means you don't need developers or EDI consultants — configure your field mappings through our visual interface, run a test cycle, and go live.

Do I need an existing VAN or AS2 connection to trade with Union Pacific Railroad?

No. Stacksync handles the entire EDI transport layer. We connect directly to Union Pacific Railroad's trading partner network through our certified connections. You don't need to manage a separate VAN subscription, AS2 certificates, or SFTP configurations.

How does Stacksync help with Union Pacific Railroad compliance?

Stacksync improves compliance scores by eliminating manual processing delays. Purchase Orders sync to your system in real time, ASNs are generated automatically when you ship, and invoices are validated with three-way matching before submission. Real-time monitoring alerts you to issues before they become chargebacks.

What EDI document types does Stacksync support for Union Pacific Railroad?

Stacksync supports all EDI document types required by Union Pacific Railroad — including Purchase Orders (850), Invoices (810), ASNs (856), PO Acknowledgments (855), and more. Our platform handles the full lifecycle from order to payment automatically.

Can I connect Union Pacific Railroad EDI to my existing ERP or WMS?

Yes. Stacksync integrates with any system that has a database or API — including SAP, Oracle, NetSuite, Microsoft Dynamics, and custom-built ERPs. Data flows bidirectionally between Union Pacific Railroad's EDI network and your system in real time.

What happens when Union Pacific Railroad updates their EDI specifications?

Stacksync monitors Union Pacific Railroad's EDI spec changes and updates our mappings proactively. When a change affects your integration, we notify you and apply updates — so you stay compliant without scrambling to decode new implementation guides.