Our PARS and PAPS guide covers the barcode that ties a shipment to its customs entry. The eManifest is the other half of that pairing, and it is the part carriers actually own — not the broker, not the shipper. A perfectly filed PARS or PAPS entry does nothing if the eManifest behind it is late, wrong, or missing, and the truck finds that out at the booth, not before.
What ACE eManifest actually is
ACE — the Automated Commercial Environment — is US Customs and Border Protection’s system for receiving electronic cargo, conveyance, and crew data ahead of a truck’s arrival. For land border crossings, carriers transmit through the ACE Truck Manifest system, either through CBP’s web portal directly or through an EDI/API connection built into the carrier’s dispatch software. It replaced the paper manifest process years ago, and today a truck without a properly transmitted eManifest is not a paperwork problem — it is a truck that is not cleared to approach primary inspection.
The northbound equivalent, filed with CBSA for freight entering Canada, is the ACI eManifest — the system referenced in our PARS breakdown. The mechanics run in parallel on both sides of the border; the acronym and the receiving agency change, the underlying discipline does not.
What has to be in it
An ACE eManifest is not a summary — it is structured data tied to the specific truck, trailer, and shipment making the crossing:
- Carrier identity: the SCAC code, linked to the specific conveyance making the trip.
- Conveyance details: the truck’s identifying information and the trailer or container number physically on the load.
- Crew data: the driver’s name, date of birth, citizenship, and license information.
- Cargo detail per bill of lading: shipper, consignee, an HTS-level description of the goods (not a vague catch-all), weight, and quantity.
- Port and timing: the port of arrival and the estimated arrival time, which is what starts the filing-window clock.
A manifest that is technically transmitted but incomplete — a vague cargo description, a trailer number that does not match what is on the truck — functions the same as a late one. CBP’s system flags the mismatch, and the shipment gets referred rather than released.
The filing window, and who is racing it
The standard rule is that the eManifest must be transmitted at least one hour before arrival at the port of entry. For FAST-eligible shipments — covered in full in our FAST program guide — that window shrinks to 30 minutes, one of the concrete, measurable benefits of having all three FAST parties enrolled and active.
The filing obligation sits with the carrier by regulation, regardless of how the broker’s customs entry is progressing. It is common for a shipper to assume that once the broker has the paperwork, the crossing is handled. The broker’s entry and the carrier’s eManifest are two separate filings to two different systems, and both have to land inside the window independently. A broker who has everything ready does not help a truck whose dispatch desk transmitted the manifest late, or not at all.
What happens when it is missing or wrong
CBP does not process a truck against an incomplete or absent eManifest — the shipment is simply not clear to proceed, and the truck holds at the crossing until it is fixed, however long that takes during a busy period. Beyond the delay itself, carriers face liquidated-damages exposure under their CBP bond for manifest violations, and a pattern of late or defective filings draws exactly the kind of scrutiny that erodes the risk-scoring benefit CT-PAT certification is supposed to provide. One missed manifest is an inconvenience; a carrier with a habit of missing them is a carrier CBP starts watching more closely on every load.
Where it actually breaks
The failure points are rarely exotic:
- The estimated arrival time is stale. If dispatch does not update ETA as a load runs early or late, the one-hour window gets calculated against the wrong number, and the manifest transmits too close to actual arrival — or after it.
- Trailer or container swaps go unrecorded. A driver drops one trailer and picks up another en route, and nobody updates the conveyance data on file.
- Cargo descriptions get copied forward from a template instead of reflecting what is actually loaded, which reads as a mismatch against the broker’s entry.
- The transmission itself fails silently — an EDI connection error that nobody catches until the truck is already at the booth.
What disciplined dispatch does
- Locks in the eManifest transmission against a live ETA, not the schedule set at pickup.
- Confirms trailer and conveyance data matches the physical equipment before transmitting, especially after any swap.
- Verifies the transmission was accepted, not just sent — a failed EDI push looks identical to a successful one until someone checks.
- Treats FAST-eligible loads with the tighter 30-minute window as the higher-discipline case, not the easier one.
- Keeps a live dispatcher reachable if CBP has a question about the manifest once the truck is at primary.
How Alpha Trans handles it
eManifest transmission is built into our dispatch process the same way PARS and PAPS verification is: tied to a live ETA, checked for acceptance before the driver is committed to the crossing, and confirmed against the physical load rather than a template. Our CT-PAT, FAST, and PIP status keeps that discipline paying off in the risk-scoring system on the other end, and our 200 company tractors run it daily at Windsor-Detroit, Fort Erie-Buffalo, and Sarnia-Port Huron.
A held truck at the border is almost never a border problem — it is a filing problem that showed up at the border. Request a quote or reach live dispatch and put your freight on a carrier that treats the manifest as seriously as the load itself.