EDI 404 Rail Carrier Shipment Information for Carload Shippers

The loaded boxcar sits on the plant siding with seals applied, the shipping clerk has pressed "send", and the translator shows a clean functional acknowledgment from the railroad. The next morning the switch crew leaves the car behind. The 404 carried car number 204471; the car on the track is 204417. The railroad had shipping instructions for a car that did not exist and none for the car it found, so the plant lost a day and the consignee's receiving appointment slipped with it.

The X12 404 is the rail bill of lading in electronic form, and most of its value sits in a handful of fields: the car initial and number, the commodity code, the weight and its basis, the stations and the route. Getting those right before transmission removes most missed pulls, re-rated invoices and freight audit disputes on carload traffic.

• What this guide explains: the segments a carload 404 carries, what each key field controls downstream in the yard, in freight audit and in tax records, and how a 404 differs from the shipping instructions an Indian rail shipper gives through the forwarding note and FOIS.
• What you can reuse: an annotated sample transaction, a worked carload in US dollars beside an Indian rake in rupees, a validation table and a go-live checklist for a new railroad partner.

What a 404 tender does when a loaded car is released

A 404 tells the railroad what is in a car, who sent it, where it goes, who pays and by which route. X12 describes the transaction as the consignor's initial tender of a shipment to a rail carrier, which can also serve as notification of equipment release and as a legal bill of lading.

That last point matters. In the US, 49 U.S.C. 11706(a) requires a rail carrier to issue a receipt or bill of lading for property it receives, and the 404 is commonly how the railroad gets the facts it needs to do so. The same section stops a carrier from setting a claim-filing period shorter than nine months, or a lawsuit period shorter than two years from written disallowance, so the 404's data later becomes evidence in any loss or damage claim.

An X12 404 Rail Carrier Shipment Information transaction is the consignor's electronic bill of lading to a railroad; under 49 U.S.C. 11706, the carrier's bill of lading anchors a loss claim that cannot be time-barred in under 9 months, so the car number, commodity and weight must match the loaded car.

The 404 travels inside the usual X12 envelope, with functional group identifier SR in the GS segment. A railroad usually answers with a 997 functional acknowledgment, which proves the file was readable, not that the car is billed. Our guide to reconciling missing 997s covers that control; this page deals with what the 404 must say for the car to move and be invoiced correctly.

Segment by segment: the carload 404 a railroad expects

A basic single-car 404 needs about fifteen segments. Railroads publish their own implementation guides, and Canadian National's generic carload guide, written against version 005050, is a clear public example. Treat any guide as partner-specific and confirm the release your railroad uses before mapping.

ST*404*00410001~
BX*00*R*PP**RRCO*L*B~                     purpose 00 original; R rail; PP prepaid; carrier SCAC; L pounds; B single B/L
BNX*R**S~                                 R = railroad scale weight; S = single shipment billing
M3*R*20261110*1430~                       release with shipment information, date, time
N9*BM*BL2611100417**20261110*1430~        bill of lading number (CN allows 15 characters for BM)
N9*PO*4500918832~                         buyer's purchase order
N7*NELX*204417*190000*E*******RR~         car initial, car number, weight, E = estimated, RR = railcar
F9**MILLTOWN*OH~                          origin station
D9**RIVERBEND*TX~                         destination station
N1*SH*NORTHERN BOARD MILL~                shipper
N1*CN*GULF BUILDING SUPPLY~               consignee
R2*RRCO*S****R~                           one R2 per railroad in the route; S = origin carrier
LX*1~
L5*1*WALLBOARD*3275440*T~                 7-digit STCC, qualifier T
L0*1***190000*E***1*CLD~                  weight, qualifier, quantity 1, CLD = carload
SE*16*00410001~
(illustrative values; station names, SCAC and reporting mark are placeholders)

The X12 standard defines many more optional segments: ZC1 for corrections, M7 seal numbers inside the equipment loop, E1 to E5 for empty car disposition, H3 and PS for special handling and protective service, and the LH1 loop for hazardous materials. Map only what your railroad's guide asks for, and keep a list of which optional segments each partner rejects.

Car initial and number: tying N7 to the railcar on your siding

The car initial and number in N7 must be read from the car, not typed from the order. That single rule prevents the most expensive 404 error, because a car with no matching billing usually stays where it is while the railroad works out what to do with it.

In Canadian National's guide, N701 is the equipment initial, up to four characters, and N702 is the equipment number, up to ten. The pair is the reporting mark and number stencilled on the car. Carry them through the warehouse system as two fields, never one concatenated string, so that a leading zero or a space cannot change the match with the railroad's records.

• Capture at loading: the loader scans or keys the car marks at the time the first pallet goes in, and the warehouse system locks the load to that car.
• Compare at release: before the 404 is generated, compare N7 with the car list from the railroad's latest placement notice for the siding.
• Use a gate reader where one exists: a reader for the car's identification tag at the plant gate gives an independent record that the car left with the load you billed.
• Carry it to the consignee: put the same car initial and number on the advance ship notice, because the consignee's receiving team books dock time and siding space by car.

Carload shippers should validate the N7 car initial and number in every X12 404 against the railroad's placement list before transmission; a single transposed digit in N702 leaves the loaded car without billing, and a release-time comparison stops the file before it can cost the 24 hours of a missed switch.

The incident at the top of this page shows how a syntax acknowledgment hides a content error. Times and documents are illustrative.

1. Tuesday 14:30, release: the shipping clerk releases car NELX 204417 in the warehouse system; the translator builds a 404 from the order record, where the car was keyed as 204471.
2. Tuesday 14:31, acknowledgment: the railroad returns an accepted 997 for the interchange. Nobody checks further.
3. Wednesday 06:50, switch: the crew finds 204417 loaded with no shipping instructions and leaves it; the railroad's customer service records an unbilled load.
4. Wednesday 11:20, discovery: the consignee asks why car 204471 shows no movement; the plant compares the siding with the 404 and finds the transposition.
5. Wednesday 12:05, correction: a corrected 404 goes out; the car moves on Thursday's switch, a day late, and the consignee rebooks its unloading slot.

STCC codes in L5 and the 49-series codes for hazardous loads

The commodity code in L503 decides which tariff item rates the car, so it belongs to master data, not to the shipping clerk. Changing a product description without reviewing its STCC is how a correct shipment ends up with a disputed invoice.

Railinc, which publishes the Standard Transportation Commodity Code, describes it as a seven-digit code used on waybills and shipping documents, with descriptions aligned to the rail and motor freight classifications. In CN's guide the code sits in L503 with qualifier T in L504, and is required only on the first L5 of the line; for example, wallboard is 3275440. Further L5 segments can carry additional description.

Hazardous materials use the 49-series. Railinc's hazardous materials file layout distinguishes 49 codes, for hazardous materials with an associated STCC, from 48 codes for hazardous waste. CN's sample for sodium chlorate puts 4918723 in L503 with qualifier T, repeats it in LH105, and carries UN1495 in LH103, class 5.1 in LH2 and the proper shipping name in LH3, with an emergency contact in the loop.

In the US, 49 CFR 174.24(a) bars a rail carrier from accepting hazardous material without a shipping paper prepared under Part 172, and paragraph (b) requires the recipient to keep a copy or electronic image for one year, or three years for hazardous waste. Before mapping the LH loop, check the segregation and placarding rules for the load; our hazmat segregation table guide covers the loading side.

Hazardous carload 404 transactions carry a 49-series code in L503 and LH105, the UN number in LH103 and the class in LH2; 49 CFR 174.24(b) then requires the rail carrier to keep the shipping paper or its electronic image for 1 year, or 3 years for hazardous waste.

Estimated weight, scale weight and the BNX weight code

The weight you send is rarely the weight you are billed. BNX01 tells the railroad which weight governs the invoice, and N703 with N704 says what kind of weight you sent, so freight audit must know both before it compares the invoice with the accrual.

CN's guide lists three BNX01 codes: R for rail carrier scale, A for a weight agreement number and N for a per-car charge. With code R, the shipper's figure in N703 is only an estimate, qualifier E, and the invoice will use the railroad's scale. With code A, CN also expects an N9 with qualifier WM carrying the agreement number. With a per-car rate, weight matters less to the charge but still matters to the car's load limit.

• Railroad scale: accrue on the estimate, then expect a variance; set a tolerance, such as 2% of weight, inside which the invoice auto-approves.
• Weight agreement: the agreed weight per package or car replaces weighing; a missing WM reference can push the car to the scale.
• Per car: the charge is flat; audit checks the car count and the STCC, not the weight.
• Units: BX07 and L011 carry L for pounds or K for kilograms; a unit mismatch makes every comparison wrong by a factor of 2.2.

Origin, destination and route segments that decide the tariff

F9, D9 and R2 decide the rate as much as the commodity does. Send rail station names spelt the way the railroad's tables spell them, and send a route only when the shipper is entitled to choose one.

CN's guide asks for station spellings that follow the Standard Point Location Code standard, published by the National Motor Freight Traffic Association in the US, and offers to supply them. The customer's street address belongs in N3 and N4 under the N1 party loops. Mixing the two is a common reason a car is rated from the wrong point.

• One R2 per railroad: each segment carries the carrier's SCAC, its routing sequence and, where the car changes hands, the junction point.
• Interline gaps: a missing second carrier on a two-road move leaves the origin road to route the car itself, which may not match the rate you contracted.
• Shipper routing: send R2 only where the contract lets the shipper choose the route; otherwise follow the railroad's guide on omitting it.

From the 404 tender to the 410 rail freight invoice

X12 defines the 410 Rail Carrier Freight Details and Invoice as itemised charges sent by the rail carrier to the party paying the freight. The bill of lading number from the 404's N9 is the key that joins tender, invoice and payment, so audit should match on it before it matches on anything else.

The worked example compares one US carload with one Indian rake. Rates are illustrative, not tariff quotes. The US car moves under BNX01 code R; the Indian rake is weighed on a railway weighbridge and the railway receipt records the chargeable weight.

The weight variance is normal and should pass silently. The commodity variance is not, and it shows why audit needs the STCC from the 404 on file: the 410 will rate whatever code was tendered, so the error is in your data, not the railroad's arithmetic. Fix the master record and file a correction before the next car ships.

India has no 404: forwarding note, e-Demand and the railway receipt

Indian Railways does not take X12 404 transactions. The same facts move through the forwarding note, demand registration in FOIS and the railway receipt, and the GST e-way bill links the receipt number back to the tax record. Treat the comparison as functional, not as a format mapping.

Section 64 of the Railways Act, 1989 requires every person entrusting goods to a railway for carriage to execute a forwarding note, and makes the consignor responsible for the correctness of its particulars. Section 65 requires the railway to issue a railway receipt, on completion of loading where the consignor loads, and makes it prima facie evidence of the weight and number of packages it states, with exceptions for unchecked wagon-load or train-load consignments.

• Demand and allotment: RailSAHAY lists the sequence as demand registration at the terminal or through e-Demand, payment of the wagon registration fee, allotment and supply of the rake, loading, weighment, freight payment and railway receipt generation.
• Tracking reference: the 11-digit Freight Number Record on the RR is the number used to track the consignment, much as the car initial and number track a US carload.
• Electronic receipt: registered customers can opt for the eT-RR, emailed to them and transferable to the consignee digitally through the e-Demand application.
• Tax link: rail freight carries GST at 5% under serial 9 item (i) of Notification 11/2017-Central Tax (Rate); the RR and freight documents support the recipient's credit claim.

The e-way bill is where a wrong RR number now gets caught. Rule 138(2A) of the CGST Rules puts generation on the registered supplier or recipient for rail movements and bars the railways from delivering goods unless the e-way bill is produced. GSTN's advisory of 18 December 2024 says FOIS is integrated with the e-way bill system and that RR numbers are validated against FOIS data, raising an alert on a mismatch.

Rail consignments booked through FOIS must carry the railway receipt number in the e-way bill as F, the origin station code and the RR number, such as FSJWT123456789, under GSTN's 18 December 2024 advisory; the e-way bill system validates each entry against FOIS data under CGST Rule 138(2A).

Our page on keeping rail demand, allotment and railway receipts connected covers the Indian record chain from indent to receipt. This article stays with the 404 and uses the Indian process only as the comparison an India-and-US shipper needs when one team runs both rail desks.

Validations to automate and decisions the rail desk keeps

Every field in a 404 can be checked by a fixed rule before transmission, except the few that depend on judgment about the commodity or the commercial route. Put the rules in the translator or the warehouse system, not in a clerk's checklist.

Ownership follows the same split. The data in a 404 comes from four teams, and the person who approves each source should be named before go-live, so that a failed car can be traced to a record and an owner within minutes.

Go-live checklist for a new 404 trading partner

Most 404 failures at go-live are master data failures, not EDI syntax failures. Run the checklist with the railroad's own test process and do not switch to production until test cars have matched end to end, from tender to invoice.

For the envelope layer itself, our guide to ISA, GS and ST control numbers explains how to stop duplicate transmissions. More rail, road and EDI topics are in the logistics and supply chain library, and if you want a 404 connection, car-number validation and 410 matching built around your plant and railroads, describe the setup in our request for proposal form.