Advance Traveler Information for Rail Compliance Guide

Cross-border rail operations may soon face a new layer of electronic border reporting. CBP's proposal for advance traveler information for rail would create firm deadlines for train notices, passenger and crew manifests, updates, and departure close-outs, making data readiness a core operational concern for both passenger and freight carriers.

What the CBP Rail Proposal Would Require

CBP's October 13, 2026 proposal would establish mandatory electronic reporting for trains arriving in, departing from, or transiting through the United States. The requirements would apply at both the Canadian and Mexican borders. Comments on the proposal are due December 14, 2026 under docket USCBP-2026-0992.

The proposal would replace a largely voluntary rail traveler reporting framework with standardized obligations similar in purpose to advance passenger information requirements used in other transportation modes. Although passenger rail carriers face the most extensive reporting burden, freight railroads would also be covered whenever engineers, conductors, or other crew members cross the border.

Covered Trains and Travelers

Rail carriers would generally need to report every passenger and crew member on an international train. Coverage would include inbound trains, outbound trains, and trains that enter the United States while traveling between two foreign points.

A carrier could use a third-party service provider to transmit the information. However, outsourcing would not transfer the carrier's legal responsibility for complete, accurate, and timely submissions. Contracts with technology providers should therefore address data quality, transmission monitoring, error resolution, system availability, and evidence of successful delivery.

Required Train and Traveler Data

The advance train notice would include the carrier code, trip number, train number, ordered car numbers, origin, destination, full itinerary, border crossing location, estimated times, and a 24-hour emergency contact.

Traveler records would contain substantially more personal information, including:

• Full name, date of birth, sex, citizenship, and country of residence
• Travel document type, number, issuing country, and expiration date
• Passenger or crew status, including conductor or engineer designation
• Travel itinerary and intended U.S. address, except for qualifying in-transit travelers
• Telephone number and email address

Carriers would transmit data through a CBP-certified carrier system or an approved channel such as eAPIS. The breadth of these fields makes data mapping, validation, privacy controls, and exception handling central to cross-border rail compliance.

Reporting Deadlines and Operational Workflows

The proposal creates several deadlines rather than a single manifest submission point. Rail carriers would need to coordinate reservations, crew management, dispatch, station operations, and border compliance systems to keep records synchronized throughout the trip.

A technically successful transmission would not necessarily establish compliance if the information were late, incomplete, or inconsistent with the individuals who actually boarded. Carriers should consequently design controls around both transmission status and underlying data quality.

The Proposed Reporting Timeline

An advance notice of arrival or departure would be due no later than 24 hours before the train reaches the U.S. border crossing. This notice concerns the train movement itself and would need to reflect the complete itinerary and expected operating details.

Passenger and crew information would be due no later than 60 minutes before departure. The requirement would apply to both trains entering the United States and trains leaving the country. Freight carriers would need a reliable process for finalizing crew assignments early enough to meet the deadline, even when operational disruptions require last-minute personnel changes.

For interactive transmissions, carriers would also send a close-out message no later than 30 minutes after departure. That message would identify the travelers who actually boarded, allowing CBP to distinguish booked or scheduled individuals from those physically aboard the train.

Changes, Delays, and Exception Management

When traveler information changes, the carrier would need to submit an update before the train leaves the station where the change was received. This requirement could affect walk-up passengers, crew substitutions, corrected travel documents, and itinerary changes.

If an estimated arrival time changes by 30 minutes or more, the carrier would need to contact CBP at the applicable border crossing. Effective procedures should define who monitors delays, who communicates with CBP, and how the contact is documented.

Rail operators should also prepare for rejected transmissions, missing fields, duplicate records, unavailable systems, and data received after ordinary cutoffs. A documented escalation path will generally be as important as the primary reporting workflow.

Compliance Risks and Industry Action Items

Advance passenger information is not merely a scheduling requirement. It combines border security reporting, personal data handling, operational communication, and recordkeeping. A breakdown in any one of those areas could create compliance exposure or delay a train at the border.

The proposal contemplates civil penalties under 19 U.S.C. 1436, potential criminal consequences for intentional violations, and possible seizure or forfeiture of a conveyance. The application of penalties would typically depend on the facts, the carrier's conduct, and the final rule adopted by CBP.

Building a Defensible Compliance Program

Passenger and freight rail carriers should begin with a gap assessment covering data sources, transmission capabilities, responsible departments, and cutoff times. Key preparation steps include:

1. Map each proposed data element to a reliable system of record.
2. Identify fields that are not currently collected from passengers or crew.
3. Establish validation rules for names, dates, document numbers, and itinerary data.
4. Define controls for additions, cancellations, crew substitutions, and no-shows.
5. Test close-out, correction, rejection, and system outage procedures.
6. Retain evidence showing what was transmitted, when it was sent, and whether it was accepted.

Privacy and cybersecurity teams should participate early because the required records contain sensitive identity, contact, and travel document information. Access should generally be limited to personnel with a defined operational need.

Effects on Cargo Rail and Shippers

CBP is not proposing to change commercial cargo manifest requirements through this rail traveler rule. Trains carrying commercial cargo would still need to provide the required consist and cargo information. Separate electronic export manifest obligations should not be confused with the proposed passenger and crew reporting framework.

A train from Canada or Mexico without commercial cargo would generally no longer need to present a car manifest or train sheet when the new advance data had been submitted. Freight railroads would nevertheless need to report crossing crew members.

Shippers should ask rail providers whether new reporting cutoffs could affect crew scheduling, train assembly, interchange activity, or estimated border transit times. Service agreements may also need clearer responsibilities for disruptions caused by missing or corrected crew information.

Evaluating the Business Impact

CBP estimates an annualized net cost of $380,495 for cargo rail carriers. It also estimates annualized net benefits of $346,911 for passenger rail carriers, $8,170,861 for passengers, and $62,567 for CBP. Individual impacts may vary significantly based on traffic volume, existing systems, and participation in voluntary rail APIS processes.

Frequently Asked Questions

Is Advance Traveler Information for Rail Already Mandatory?

Not under the October 13, 2026 proposal itself. A proposed rule does not generally create a final compliance obligation. CBP must evaluate comments and complete the rulemaking process before mandatory requirements take effect. Carriers should still prepare early because data collection, system certification, testing, and workforce training can require substantial lead time.

Would the Rule Apply to Freight Railroads?

Yes. Freight railroads would be covered because engineers, conductors, and other crew members cross the U.S. border. The proposal focuses on traveler and train movement information, not only ticketed passengers. Freight carriers should map crew scheduling data and determine whether current dispatch systems can support timely electronic reporting.

Does the Proposal Change Rail Cargo Manifest Rules?

No. The proposal does not revise commercial cargo manifest obligations. Trains carrying commercial cargo would still need to provide the applicable consist and cargo information. Rail organizations should treat traveler reporting and cargo reporting as distinct compliance streams, even when both depend on shared trip, train, and border crossing data.

Can a Rail Carrier Use a Third Party to Submit the Data?

A carrier could generally use an authorized third party or service provider. The carrier would remain responsible for the accuracy and timeliness of the submission. Vendor oversight should include testing, service expectations, transmission records, error notifications, business continuity, and procedures for correcting rejected or incomplete data.

What Should Carriers Do Before the Comment Deadline?

Carriers should compare existing passenger and crew records against the proposed data elements, model each reporting deadline, and identify operational scenarios that may be difficult to manage. Material concerns or implementation recommendations can be submitted by December 14, 2026 through docket USCBP-2026-0992.

How Stable Software Can Help

Supporting Broader Broker and Importer Compliance

The proposed rail traveler requirements sit outside duty drawback and would need to be addressed through carrier-specific reporting processes. Customs brokers can still use the rulemaking period to discuss broader border compliance, data quality, and duty recovery opportunities with importer clients.

Stable Software provides DrawbackAI, flat-license duty drawback software that U.S. customs brokers can white-label for their importer clients. Brokers file claims under their own filer codes, retain control of the client relationship, and pay a flat software license. Stable Software never takes a percentage of the refund. Brokers seeking to expand importer services can learn more about Stable Software's approach for customs brokers.

Resources