CBP's Rail Export Manifest Rule: What Has to Be Right 24 Hours Before Departure

If you move goods out of the United States by rail, one date now sits in front of your paperwork. On 26 August 2026 U.S. Customs and Border Protection published a final rule, Automated Commercial Environment (ACE) Electronic Export Manifest for Rail Cargo. It takes effect 26 October 2026 and amends 19 CFR parts 103, 113, 123 and 192.

Most of the coverage so far has been written for carriers and customs lawyers. This one is written for the exporter, because the rule does not ask you to file anything new — it asks your documents to be finished earlier than they probably are today.

What actually changes on 26 October 2026?

CBP adds a new section, 19 CFR 123.93, that creates an initial filing for rail cargo leaving the United States. In CBP's words, that filing must be made "as early as practicable, but no later than 24 hours prior to departure from the U.S. port of export," while the remaining manifest data must be transmitted "at least two hours prior to such departure."

Two hours before departure is the part carriers will manage. Twenty-four hours is the part that reaches back into your office, because the initial filing is made of fields that come off your shipment documents.

Who has to file the rail export manifest?

Under 19 CFR 123.93(c), the outbound rail carrier is the party for whom "participation is mandatory." The carrier must transmit the transportation data and the empty container data, and if nobody else elects to send the initial filing, the carrier must send that too.

Other parties may elect to file: the U.S. Principal Party in Interest (USPPI) or its authorised agent, and the Foreign Principal Party in Interest or its agent. So there is a real choice to make with your carrier, and it is worth making it deliberately rather than discovering it in October.

Which seven fields does the initial filing need?

Section 123.93(d)(1) lists the mandatory data. Six of the seven are values that already exist somewhere in your shipment paperwork, which is why the deadline is really a document deadline.

Field required by 123.93(d)(1)	Where it normally comes from	What makes it fail
Bill of lading number	The carrier's master or house bill	House bills issued late, or a number that differs from the one on your invoice
Numbers and quantities of cargo	Your packing list	Counting pallets or containers instead of the lowest packaging unit
Total weight in pounds or kilograms	Your packing list	Gross and net weights that disagree between documents
Precise cargo description, or HTSUS to six digits	Your commercial invoice	Generic wording (see below)
Shipper's complete name and address	The bill of lading, for each house bill	A trading name on one document and a legal name on another
Consignee's complete name and address	The bill of lading	"To order" shipments, handled below
EIN, Importer Record Number, or CBP assigned number	Your own records	Nobody owning the field until the day it is due

The AES Internal Transaction Number is listed separately, as conditional initial data: the ITN or FTR exemption code "is conditional and must be transmitted if, and as soon as, applicable." It is not one of the seven mandatory fields, and it does not replace them.

Why can't we write "general cargo" any more?

Because the rule names that habit and rejects it. For the cargo description, CBP writes that generic descriptions, "specifically those such as “FAK” (“freight of all kinds”), “general cargo,” and “STC” (“said to contain”) are not acceptable."

If your commercial invoice carries a summary line that a forwarder has been quietly expanding for you, 26 October is the day that stops working. The description on the manifest has to be precise, or carry the HTSUS number to the six-digit level.

Do pallet counts still work as a quantity?

No, and this is the change most likely to bite a small exporter. The quantity field means "the quantity of the lowest external packaging unit," and the rule says plainly that "numbers or quantities of containers and pallets do not constitute acceptable information." CBP gives its own example: "a container holding 10 pallets with 200 cartons should be described as 200 cartons."

Plenty of packing lists stop at the pallet. If yours does, the fix is not complicated, but it has to happen before the train is loaded rather than after somebody asks.

What happens to a shipment consigned "to order"?

The rule handles it explicitly, and the handling is easy to get wrong. Where cargo is shipped “to order of [a named party],” CBP requires that "the “to order” party must be named as the consignee." If the bill of lading also lists another commercial party for delivery or contact purposes, the carrier must report that party's identity, contact information and address in the Notify party field.

So a letter-of-credit shipment that reads "to order of [bank]" does not get to put the buyer in the consignee box on the manifest. The buyer belongs in Notify party. If your own documents blur those two roles, the manifest inherits the blur.

Does this replace my EEI filing?

No. The EEI obligation is separate and it has not moved. Under 19 CFR 192.14(b)(1)(iv), the USPPI or its agent "must provide the EEI filing citation (the ITN), exclusion, and/or exemption legend to the exporting carrier no later than 2 hours prior to the arrival of the train at the border." And under 192.14(c)(4)(i), "The carrier may not load cargo without first receiving" that citation or an appropriate exemption legend.

Read the two together and the practical picture is a single earlier deadline rather than two competing ones: the manifest data has to be settled a day before departure, and the EEI citation still has to reach the carrier before loading and before the border.

How does rail compare with the vessel manifest change?

They are moving in the same direction at different speeds. The vessel side is still a proposal — we covered it in CBP's 24-and-2 rule for vessel export manifests, which was published as a Notice of Proposed Rulemaking in February 2026. Rail is now a final rule with a date on it. If you ship by both modes, rail is the one with a deadline you can already put in a calendar.

What should a small exporter do before 26 October?

1. Ask your rail carrier who files the initial data. The carrier must file if nobody else elects to; find out whether they expect the fields from you, and by when.
2. Count to the carton on your packing list. Pallet counts are no longer an acceptable quantity.
3. Replace summary cargo descriptions. Either a precise description or the HTSUS six-digit number, on the invoice your forwarder actually reads.
4. Decide who owns the EIN or IRN field so it is not looked up the morning of departure.
5. Check your "to order" shipments so the consignee and the notify party are not the same name in your own file.

None of that is new information. It is the same information, required to be correct a day earlier than your documents are usually finished.

Where ovrseas fits, and where it does not

To be direct about the limits first: ovrseas does not file export manifests, does not file EEI through AES, does not classify goods, and cannot tell you whether your carrier has transmitted anything. Those are the carrier's job and the filer's job.

What it does is narrower. Consignee, shipper, description, quantity and weight are entered once in a master file and read by every document generated from it, so the packing list and the commercial invoice cannot quietly disagree about how many cartons are in the container — which is the disagreement this rule now surfaces a day before the train moves. If you are still assembling that set by hand, our note on where invoices and packing lists diverge covers the failure mode, and the category page is honest about who this kind of tool is not for. Pricing is here.

Sources: CBP final rule 2026-17390, published 26 August 2026 (19 CFR 123.93); 19 CFR 192.14. Quotations are taken from the Federal Register text and the current text of 19 CFR 192.14. Checked 1 September 2026.