The filing happens before the truck moves, not when it reaches the booth. Here is what CBP and CBSA actually require, how early, and what it costs you to get it wrong.
An eManifest is an electronic pre-arrival filing that gives CBP or CBSA cargo, conveyance, crew, and shipment details before freight reaches the border. For US-Canada carriers, it is what lets customs assess risk early, cut manual paperwork, and keep legitimate freight moving.
So what goes in it, who has to file it, how early, and what happens when it is late? Let’s break it down in practical terms.
Key Takeaways
- An eManifest is advance electronic shipment information submitted to customs before the truck arrives at the border.
- ACE eManifest covers freight entering the United States through CBP. ACI eManifest covers freight entering Canada through CBSA. They are not the same system.
- Into the US, standard truck shipments need the filing accepted at least 1 hour before arrival, or 30 minutes for FAST.
- Late, missing, or inaccurate submissions can mean rejected manifests, customs holds, border delays, and monetary penalties.
- The filings that go wrong are usually the ones assembled from scattered sources: client emails, spreadsheet notes, portal rekeying, driver texts.
What Is a Truck eManifest?
An eManifest is a digital customs filing that reports commercial freight details before a shipment arrives at a border crossing. It tells customs who the carrier is, what vehicle and crew are moving the load, who shipped it, who receives it, and what documents support it.
For US-Canada trade, the term points to two systems. ACE eManifest for freight entering the United States, where ACE is the Automated Commercial Environment, CBP’s electronic trade processing platform. ACI eManifest for freight entering Canada, where ACI is Advance Commercial Information, CBSA’s program for receiving commercial data before arrival.
The purpose is simple. Customs wants the shipment story before the truck reaches the booth.
When the data is complete and accepted, the driver is not depending on paper alone. When it is missing, late, or mismatched, the crossing becomes a compliance problem before the freight ever reaches inspection.
Why CBP and CBSA Require eManifest Filing
Advance electronic data gives officers time to assess risk and verify shipment details before arrival, instead of discovering a problem at the primary inspection lane.
CBP describes ACE as the US electronic Single Window for trade processing, covering manifest and cargo release data. CBSA runs ACI for commercial cargo data. In both cases the goal is not digitization for its own sake. It is earlier visibility and cleaner compliance data.
For carriers, that reframes what eManifest is. It is not an administrative afterthought bolted onto dispatch. It is part of the transportation workflow.
Dispatch, operations, compliance, and the driver all depend on one filing matching the physical shipment. A typo in a trailer number, a missing consignee detail, or an incorrect shipment reference puts the team into correction mode when the freight should already be moving.
How Early Does an eManifest Have to Be Filed?
The deadlines are fixed, and they are the part worth memorizing.
- Into the United States: CBP must receive the ACE Truck eManifest at least 1 hour before the truck reaches the first port of arrival. For FAST-qualified shipments, 30 minutes (19 CFR 123.92).
- Into Canada: CBSA must receive and validate highway cargo and conveyance data at least 1 hour before the truck reaches the border, submitted by EDI or through the CBSA eManifest Portal.
Those are ceilings, not targets. Both can be transmitted well ahead of time (30 days), and the safest workflow files early and leaves room to fix a rejection. A filing that lands exactly at the deadline has no margin for the one thing that goes wrong.
Which Carriers and Freight Modes Need an eManifest
Commercial carriers moving freight across the US-Canada border generally need an eManifest when they transmit advance cargo and conveyance details to the customs agency for the destination country. The workflow depends on direction of travel, mode, carrier type, and which agency receives the data.
Highway carriers know this best, because the driver reaches a physical crossing where the filing gets checked against the truck, trailer, cargo, and paperwork. But the same advance-data expectation now applies across air, ocean, rail, and warehouse workflows.
Confirm the requirement for each move by answering five questions:
- Is the freight entering the United States or Canada?
- Which mode is moving the goods: truck, air, ocean, rail, or warehouse transfer?
- Who is responsible for the carrier, cargo, house bill, entry, or release data?
- Does the agency require a portal, an EDI connection, or a certified software provider?
- What acceptance, rejection, or secondary notice should the team watch before the driver arrives?
This is where one platform across modes matters. CustomsCity supports multi-modal customs compliance across ACE/ACI Truck eManifest, ACE Air eManifest and ACAS, and ACE Ocean eManifest, so a team handling more than one mode is not stitching together disconnected workflows.
What Happens If You Miss an eManifest Submission
A missed submission can mean a rejected manifest, a border delay, an inspection, a corrective filing, or a monetary penalty. The immediate cost is operational. The driver waits, dispatch troubleshoots, and the client gets no clear status until it is resolved.
The bigger risk is repetition. One late filing is manageable. A pattern erodes client trust and attracts scrutiny.
On the Canadian side, CBSA’s Administrative Monetary Penalty System (AMPS) issues monetary penalties to commercial clients for violations of trade and border legislation. One contravention is written specifically for this: C384 covers failing to submit advance information in the prescribed time or prescribed manner. On the US side, CBP can reject or require correction of incomplete or inconsistent manifest data before the freight proceeds.
Most missed submissions are not a team that stopped caring. They happen because the process depends on too many manual steps: emails from clients, spreadsheet notes, portal rekeying, driver updates by text, separate systems for different modes.
The more handoffs, the more chances for a preventable border problem.
How eManifest Software Simplifies the Filing Process
Software helps by centralizing shipment data, validating required fields, transmitting electronically, and tracking agency responses in one workflow instead of one portal per mode.
A practical eManifest platform should let your team:
- Create trips, shipments, conveyance records, and driver details without rekeying the same information repeatedly.
- Validate required fields before transmission so preventable errors surface earlier.
- Submit ACE and ACI filings through certified connections or approved electronic channels.
- Monitor accepted, rejected, amended, and pending statuses from one view.
- Keep an audit trail showing what was filed, when, and what changed.
CustomsCity was built around that pressure point. Our cloud-based platform connects carriers, customs brokers, freight forwarders, and importers to CBP and CBSA workflows across modes, with validation before transmission and 24/7 expert support.
On the classification side, CustomsAI works as a second set of eyes, not a replacement for yours. It suggests an HTS code with a confidence percentage shown next to it, reads commercial invoices and other trade documents to pre-fill entry data, and calculates duty. The broker reviews and confirms every suggestion before anything is filed.
ACE eManifest vs. ACI eManifest: What Is the Difference?
ACE eManifest is commercial freight data submitted to CBP for goods entering the United States. ACI eManifest is advance commercial data submitted to CBSA for goods entering Canada. Both support pre-arrival risk assessment. They are run by different agencies and follow different workflows.
For carriers running both directions, that difference shows up daily. A southbound move may require ACE data. A northbound move may require ACI data. Same parties, same documents, different agency rules, status messages, portals, and correction processes.
So do not treat eManifest as one generic form. Define a separate workflow for each agency, then run both through a system that keeps the user experience consistent. CustomsCity covers both sides of the lane with ACE/ACI Truck eManifest software, plus ACI Air eManifest for the Canadian air side, so your team does not have to become a portal specialist for every filing type.
How to Build a Reliable eManifest Workflow
A reliable workflow starts before dispatch and ends only when the filing status is confirmed and visible. The goal is catching incomplete data before submission, not after the driver is approaching the border.
- Collect shipment details early. Shipper, consignee, cargo description, quantity, weight, equipment, driver, document references.
- Confirm direction and agency. The team needs to know whether ACE, ACI, or another filing applies before anything moves.
- Validate required fields before transmission instead of waiting for a rejection notice.
- Submit through the approved channel: portal, EDI connection, or compliance platform.
- Monitor status and correct errors before the driver reaches the port.
- Keep the filing record for audit, customer service, and process improvement.
That sequence gives operations managers control, and it matches how compliance teams actually work: under time pressure, across multiple shipments, with clients asking for updates and drivers waiting on clear instructions.
Frequently Asked Questions
Commercial carriers or responsible trade chain partners file eManifest data when they are required to provide advance cargo and conveyance information to CBP or CBSA. The exact responsibility depends on the agency, freight mode, movement type, and commercial role. Verify the requirement before dispatch, especially when you move freight in both directions.
ACE eManifest supports freight entering the United States through CBP. ACI eManifest supports freight entering Canada through CBSA. Both involve advance electronic data, but they have different agency rules, portals, data requirements, and status messages. Cross-border teams should manage each workflow separately.
Into the United States, CBP must receive the ACE Truck eManifest at least 1 hour before the truck reaches the first port of arrival, or 30 minutes for FAST-qualified shipments. Into Canada, CBSA must receive and validate highway cargo and conveyance data at least 1 hour before the truck reaches the border. Both can be transmitted well ahead of time, so file early and leave room to correct a rejection.
A late or incorrect eManifest can lead to delays, rejected filings, corrective submissions, inspections, or monetary penalties. CBSA issues monetary penalties for trade and border legislation violations through its Administrative Monetary Penalty System. CBP can reject, hold, or require correction of manifest data when the filing does not meet agency requirements.
Conclusion: Keep Compliant Freight Moving
eManifest filing is one of the core compliance steps that keeps US-Canada freight moving with fewer avoidable border problems. When the data is accurate, submitted on time, and visible to the team, carriers protect schedules, clients, and margins.
If your team is still managing ACE and ACI filings through scattered portals, spreadsheets, and manual status checks, the next step is straightforward. Book your free CustomsCity demo and see how one platform handles eManifest compliance across your operation.
