ACE & ACI eManifest: A Step-by-Step Guide

Every truck crossing the Canada–US border must pre-notify customs before arrival. In the US, that system is ACE — the Automated Commercial Environment. In Canada, it's ACI — the Advance Commercial Information system. Both are mandatory, both have strict lead times, and both can reject your filing and hold your truck at the line if something is wrong. Here's how to navigate them correctly.

What Are ACE and ACI eManifest?

ACE (Automated Commercial Environment) is the US CBP's cargo control and manifest system. Before a commercial truck crosses into the United States, the carrier must submit an electronic cargo manifest through ACE. CBP uses this data to screen shipments for admissibility, security risk, and regulatory compliance before the truck physically arrives at the port of entry.

ACI (Advance Commercial Information) is the CBSA's equivalent system for trucks entering Canada. Also called eManifest when used in the highway mode, ACI requires carriers to electronically transmit cargo and conveyance data to CBSA in advance of arrival. The CBSA then issues a response — either a "May Proceed" or a hold — before the driver reaches the primary inspection booth.

Both systems serve the same purpose: push customs processing upstream so border officers can focus inspection resources on high-risk shipments and wave low-risk ones through quickly.

Who Files the eManifest?

The carrier is responsible for filing both ACE and ACI eManifest. This is non-negotiable — it cannot be delegated to the importer, exporter, or customs broker. The carrier (or a service provider acting on the carrier's behalf) must submit the conveyance and cargo data using the carrier's own credentials.

In practice, many owner-operators work with a dispatch service or a third-party eManifest service provider to handle the filing. The dispatch enters the trip data, the carrier's portal credentials are used to transmit, and confirmations are passed back to the driver. What matters is that the filing happens under the correct carrier code and within the required lead time.

Lead Times Before Arrival

Lead time requirements are strict. Missing them means the carrier arrives at the border without a valid eManifest — a guaranteed delay:

• ACI eManifest (entering Canada): Carriers must submit cargo and conveyance data at least 1 hour before arrival at the Canadian port of entry for highway shipments. CBSA strongly recommends filing earlier to allow time to resolve any rejections.
• ACE eManifest (entering the USA): CBP requires submission at least 1 hour before arrival for highway carriers as well. However, certain high-risk lanes and commodity types may require earlier filing.

These are minimums. A good practice is to file 2–3 hours before the driver reaches the crossing, especially on busy corridors like Windsor–Detroit or Niagara Falls. This gives time to catch rejections and refile.

Required Data Fields

Both systems require similar data sets, though the field names and specifics differ:

• Conveyance data: Carrier SCAC or carrier code, truck license plate, trailer plate, driver name, driver date of birth (ACI), port of arrival.
• Cargo data: Shipper name and address, consignee name and address, description of goods, quantity and unit of measure, weight, country of origin, Harmonized System (HS) tariff code (for some entries).
• PARS/PAPS linkage: For ACE, the cargo must be linked to a PAPS barcode (Pre-Arrival Processing System) that the customs broker has filed entry for. For ACI, cargo links to a PARS (Pre-Arrival Review System) number. The eManifest cargo reference number must match exactly what the broker has on file — mismatches cause rejections.
• Seal numbers: If the trailer is sealed, the seal number must be declared accurately.

Linking eManifest to PARS and PAPS

This is where many errors occur. The eManifest cargo entry references the same barcode that appears on the shipment's PARS or PAPS paperwork. The customs broker files the entry against that barcode; the carrier files the eManifest cargo referencing that same barcode. If the broker files under one number and the carrier files under a different number — or if there's a typo — the system cannot match the entry to the cargo, and the filing is rejected.

Best practice: confirm the PARS or PAPS barcode with the broker before the driver leaves the shipper. Do not rely on the driver to capture the barcode at pickup. Get it from the customs broker's confirmation and enter it manually into the eManifest filing.

Common Rejection Reasons

Rejections come back quickly — usually within minutes of submission. Common causes include:

• PARS/PAPS barcode not on file with the broker when the carrier files (broker hasn't submitted entry yet — sequence matters)
• Carrier code or SCAC not matching what CBP/CBSA has on file for the carrier
• Driver name spelled differently than the passport or border crossing record
• Trailer plate entered incorrectly (missing jurisdiction, wrong format)
• Port of arrival code wrong (filing for one crossing but crossing at another)
• Cargo description too vague ("freight" or "merchandise" without commodity detail)
• Weight or quantity missing or implausible

When a rejection comes back, read the specific rejection code carefully — each code points to a specific field. Correct only that field, refile, and confirm the new submission is accepted before the driver proceeds.

Service Providers and Software

Carriers can file eManifests through several channels:

• CBP's ACE portal (free, web-based, manual entry) for US filings
• CBSA's eManifest Portal (free, web-based) for Canadian filings
• Third-party EDI/API-connected software — providers like BorderConnect, MagicLogix, Descartes, and others offer carrier-facing eManifest tools with automated data entry, rejection alerts, and integration with dispatch software

For carriers running more than a handful of cross-border loads per month, third-party software pays for itself quickly in time savings and error reduction. Most dispatch services are already connected to one of these platforms.

The Dispatcher's Role

A good cross-border dispatcher doesn't just find loads — they own the eManifest filing process. This means collecting all required data before the driver leaves, filing with enough lead time, monitoring for rejections, coordinating with the customs broker to confirm PARS/PAPS are on file, and communicating the trip number or confirmation to the driver so border officers can locate the filing instantly.

Drivers should arrive at the primary inspection booth knowing their PARS or PAPS barcode, their trip number, and that their eManifest was accepted. Drivers who don't know these basics slow the line and get secondary referrals unnecessarily.

Running cross-border? We coordinate PARS/PAPS and eManifest so your loads clear smoothly. Get dispatched with TRUCC — carrier-side dispatch across Canada and the USA.