The ACE Electronic Export Manifest for truck cargo represents a significant shift in how export shipment data may be collected before cargo reaches the U.S. border. Beginning October 23, 2026, a small group of participating carriers will test new electronic filing workflows while maintaining existing Electronic Export Information responsibilities.
Understanding the ACE Truck Export Manifest Test
Test Scope and Participation Limits
U.S. Customs and Border Protection is launching the voluntary ACE Electronic Export Manifest test for truck cargo on October 23, 2026. The test is expected to operate for approximately two years and is limited to a maximum of nine truck carriers, making early enrollment important for carriers that want direct experience with the new process.
Participating carriers will electronically transmit export manifest information through the Automated Commercial Environment rather than relying exclusively on paper or legacy border processes. Filers may generally use either the ACE Portal or an Electronic Data Interchange connection, subject to the technical specifications and onboarding requirements provided during acceptance into the test.
Truck carriers interested in participating should contact CBP at cbptruckexportmanifest@cbp.dhs.gov. Because participation is capped, an application does not necessarily guarantee acceptance. Carriers should be prepared to explain their export operations, technical capabilities, intended filing method, and ability to support testing and issue resolution.
Why Early Participation Matters
The test gives participating carriers an opportunity to build practical ACE export filing expertise before any potential expansion or future mandatory implementation. Early participation can expose data-quality problems, booking-process gaps, communication failures, and system limitations while the program remains in a controlled testing phase.
The value extends beyond the carrier. U.S. Principal Parties in Interest, freight forwarders, customs brokerages, and export compliance teams may need to provide accurate data earlier than under existing operating models. Organizations that treat the test as a broader process-transformation initiative will generally be better positioned than those that approach it as a narrow carrier filing requirement.
Even companies that do not participate directly should evaluate the potential downstream effect on export booking cutoffs, document collection, shipment changes, and border arrival procedures. The test provides a useful model for how truck export manifest processes may evolve across U.S. land-border operations.
Filing Deadlines and Operational Readiness
The 24-Hour Limited-Data Requirement
Participating carriers must submit limited export manifest data at least 24 hours before departure. This requirement creates a substantially earlier operational milestone than many truck export workflows currently support.
A carrier cannot consistently meet the deadline if shipment details arrive only when the driver is dispatched or when cargo is already approaching the border. Booking teams will need to obtain the necessary preliminary information early enough to validate, format, and transmit it while preserving time to correct rejected or incomplete submissions.
Carriers should define what constitutes “departure” within their operating model and align that interpretation with current test instructions. Dispatch schedules, terminal departures, relay arrangements, consolidation activity, and last-minute equipment changes can complicate the calculation. A documented control should identify the relevant departure event, the filing owner, the transmission timestamp, and the escalation path when required data is missing.
The Complete Manifest Deadline
The complete electronic export manifest must be filed no later than two hours before arrival at the final U.S. port of export. Operationally, the transmission should be completed by the point that is two hours before arrival—not delayed until the vehicle enters the final two-hour window.
This deadline requires coordination among shippers, forwarders, carrier operations teams, drivers, and filing personnel. Route changes, border congestion, cargo substitutions, and revised departure times can alter the expected arrival calculation. Automated alerts and exception queues can help identify shipments whose complete manifests remain unfinished as the deadline approaches.
Building a Sustainable Filing Workflow
Readiness should include more than selecting the ACE Portal or EDI. Participating carriers should map every required data element to its system of record, assign responsibility for data validation, and define how corrections will be handled after initial submission.
The ACE Portal may be suitable for lower-volume or manually managed operations. EDI connectivity is generally more scalable for carriers with recurring export traffic, although it requires message development, testing, monitoring, and technical support. The appropriate method will depend on shipment volume, internal IT capabilities, customer integration, and the complexity of the carrier’s network.
Regardless of the transmission channel, accepted participants should confirm current technical and onboarding requirements before development begins. Test specifications, validation rules, response messages, and amendment procedures may change as CBP gains operational experience.
Managing EEM and EEI as Separate Compliance Controls
The Truck Manifest Does Not Replace EEI
The ACE Electronic Export Manifest test does not eliminate Electronic Export Information filing obligations. When EEI is required, the USPPI—or an authorized agent acting under the appropriate authorization—must continue filing through the established export reporting process under 19 CFR 192.14.
EEM and EEI serve related but distinct purposes. The electronic export manifest is a carrier-focused cargo and conveyance submission. EEI is an export transaction filing that supports government trade statistics, export controls, enforcement, and other regulatory functions. Submitting one does not automatically satisfy the other.
This distinction is critical because similar shipment data may appear in both transmissions. Export teams should not assume that duplication means interchangeability. Each filing has its own responsible parties, timing, data requirements, validation rules, and correction procedures.
Establishing Dual-Filing Reconciliation
Carriers and USPPIs should create controls that reconcile EEM information with EEI data without merging the two responsibilities. Key fields may include parties to the transaction, destination, commodity descriptions, quantities, transportation details, and references used to associate the export movement with the relevant filing.
A robust workflow should confirm whether EEI is required, identify the responsible filer, obtain the appropriate proof of filing or exemption citation, and ensure the carrier receives that information before the applicable operational cutoff. Exceptions should be routed to personnel who understand both export reporting and carrier manifest procedures.
Data changes require particular attention. A quantity adjustment, commodity substitution, routing change, or vehicle reassignment may affect one or both submissions. Standard operating procedures should define when an EEM update is necessary, when EEI must be corrected, and who communicates the change across organizations.
Recommended Internal Controls
Compliance teams should maintain separate status indicators for EEM and EEI rather than using a single “export filed” flag. A shipment should not be released solely because one transmission was accepted.
Useful controls include timestamp capture, filing-response retention, automated mismatch detection, missing-data alerts, amendment tracking, and audit histories. Brokerages and forwarders advising exporters should also revise customer guidance so that the new carrier deadlines do not obscure the USPPI’s continuing EEI filing requirements.
Frequently Asked Questions
When Does the ACE Electronic Export Manifest Truck Test Begin?
The voluntary test begins October 23, 2026, and is expected to run for approximately two years. CBP may adjust technical, operational, or participation requirements during that period, so accepted carriers should monitor program communications and keep their procedures configurable.
Who Can Participate in the Test?
Participation is limited to truck carriers, with a maximum of nine carriers accepted. Interested carriers should apply through cbptruckexportmanifest@cbp.dhs.gov. Applicants should evaluate their technical readiness, export volume, staffing, and ability to coordinate data collection with USPPIs and forwarders before applying.
What Are the Main EEM Filing Deadlines?
Limited export manifest data must be filed at least 24 hours before departure. The complete electronic export manifest must be transmitted no later than two hours before arrival at the final U.S. port of export. Carriers should build internal buffers rather than treating either deadline as the preferred filing time.
Does EEM Replace the USPPI’s EEI Filing?
No. EEM does not replace EEI. When an export transaction requires EEI, the USPPI or its authorized agent must continue meeting applicable filing obligations under 19 CFR 192.14. Carriers should verify the relevant EEI proof of filing or exemption information separately from the manifest submission.
Can Carriers File Through the ACE Portal or EDI?
Participating carriers may generally use the ACE Portal or EDI connectivity under the test’s technical framework. The ACE Portal may support more manual workflows, while EDI may be more appropriate for higher shipment volumes and system-driven processing. Accepted carriers should confirm current specifications before implementation.
What Should Nonparticipating Exporters and Forwarders Do Now?
They should review booking cutoffs, carrier data requirements, EEI handoffs, and change-management procedures. Even when a company is not directly enrolled, a participating carrier may require shipment information earlier to meet the 24-hour and two-hour deadlines.
How Stable Software Can Help
Automating Export Compliance Workflows
Stable Software helps customs brokers, carriers, and trade compliance teams replace fragmented spreadsheets, email handoffs, and manual status tracking with structured digital workflows. Organizations preparing for ACE Electronic Export Manifest processes can use configurable automation to collect shipment data, monitor deadlines, manage exceptions, preserve audit trails, and distinguish EEM status from continuing EEI obligations.
By connecting operational and compliance activities, teams can identify missing information before a truck approaches the border and reduce the risk of inconsistent filings across parties. To explore how workflow automation can support scalable land-border export compliance, visit Stable Software.
