New Bridge, Same One-Hour Clock: Cross-Border Border-Data Controls for Winter 2026

Gordie Howe is open, flying trucks end Nov 24 and AMPS still escalates. Where ACI and ACE border data breaks between carriers, brokers and customs brokers.

Golden-hour mountain landscape with a semi truck pulling a long white box trailer at a small border checkpoint booth in a field of wildflowers

A Windsor-bound load is running late out of Detroit. The dispatcher sees the Ambassador Bridge backed up and sends the driver to the Gordie Howe International Bridge instead. It is the right traffic call, but it is also a border-data decision, and nobody treated it as one. The ACI eManifest still names the old port. The customs broker filed the PARS against the original crossing. The driver reaches the CBSA booth with a manifest that no longer describes the trip.

The truck might clear late, sit in secondary, or earn the carrier a Notice of Penalty Assessment for a decision a dispatcher made in thirty seconds. Cross-border failures in 2026 rarely come from people who don't know the rules. They come from handoffs where the rules live in one person's head and the data lives in three different systems.

What changed on the border-data side in 2026

Tariffs got the headlines, but the systems behind the border changed too.

A new port in Canada's busiest corridor. The Gordie Howe International Bridge opened on July 27, 2026. CBSA's July 24 backgrounder describes 24 primary inspection lanes (configurable up to 16 commercial), dedicated NEXUS/FAST lanes, and 12 commercial secondary docks. CBSA says the Windsor-Detroit corridor carries about 30% of Canada-U.S. trade by truck, more than $274 million a day. Statistics Canada reported on September 11 that 34,800 commercial trucks entered Canada over the new bridge in August 2026, its first full month, while truck entries at Windsor's other ports rose 0.4% year over year to 87,400. The new bridge added capacity without pulling trucks off the old crossings. That means more port choices, and more chances to file for the wrong one.

Crossing-level identifiers on the U.S. side. CBP's Port of Detroit trade notice of July 22, 2026 lists all three crossings under port code 3801, each with its own firms code: H0E1 for Gordie Howe, H726 for the Ambassador Bridge cargo facility, H727 for the tunnel. The notice says filing for "the correct Port of Entry / Crossing (via Firms Code) is essential."

Driver identity in ACE. Effective February 24, 2026, CBP retired the ACE ID as the FAST identifier in truck manifest EDI. Filers must now use the driver's FAST ID.

"Flying trucks" ends November 24. On August 26, 2026, CBP rescinded the long-running practice of using air manifest data for cargo that crosses by truck. CBP said the practice violates 19 CFR 123.92, which requires advance data that matches the mode actually crossing the border. The 90-day transition ends November 24, 2026. It mainly affects express operations, but the obligation follows the freight to the linehaul carrier.

An export clock is being tested. A Federal Register notice of September 23, 2026 opened a voluntary ACE Electronic Export Manifest test for truck cargo. It started October 23, 2026, is capped at nine carriers, and runs about two years. Participants file limited data at least 24 hours before departure from the United States and complete the filing no later than two hours before arrival at the final port of export.

Separately, CBSA notices of August 19, 2026 confirmed that the highway sufferance warehouse licences at St-Cesaire and East Farnham, Quebec, were surrendered effective August 10. Bonded carriers clearing at those ports now have to declare at another sufferance warehouse.

The clocks have not moved, and the penalties escalate

CBSA must still receive and validate highway cargo and conveyance data at least one hour before arrival at the first port of arrival. Memorandum D3-4-2 says data that arrives inside the hour is accepted with an "insufficient review time" warning, and AMPS may apply. CBSA's highway guidance adds two rules that catch good operators. A correction does not restart the clock; only cancelling and resubmitting does. And drivers cannot use a different port of entry unless the ACI is updated first.

On the U.S. side, 19 CFR 123.92 requires CBP to receive truck cargo data either 30 minutes or one hour before the first U.S. port, depending on the approved system used. The shorter window goes with FAST shipments. The rule also requires a precise description or a six-digit HTS number and bars entries like "FAK," "general cargo," and "said to contain."

CBSA's Master Penalty Document escalates by occurrence within a 12-month retention period:

Contravention

Trigger

1st / 2nd / 3rd+

C378

No pre-arrival data (data sent upon or after arrival counts as none)

$2,000 / $4,000 / $8,000

C379

Data sent late or by an unapproved method

$250 / $375 / $750

C380

Failure to comply with a CBSA notice about goods on board

$2,000 / $4,000 / $8,000

C381

Correction not sent without delay

$500 / $750 / $1,500

C382

Information not true, accurate and complete

$500 / $750 / $1,500

Two details matter operationally. Under C379, timing and method are separate obligations, so one transmission can draw two penalties. And data sent at the booth counts as no data, which moves the shipment from the $250 row to the $2,000 row. New highway carriers also have 30 days after receiving a carrier code to get bar-coded labels. After that, arriving without them carries a $1,000 penalty.

Where the handoffs break

The carrier owns the conveyance and cargo report. The customs broker owns release and accounting. The freight broker or shipper owns the commercial data both of them depend on. Failures happen in the gaps between them.

Port changes that never reach the manifest. This is the opening scenario. Because CBSA requires corrections without delay, a port change that never makes it into the ACI can show up as a C381 or C382. With three Windsor crossings and firms-code precision on the U.S. side, the diversion habits that worked in 2025 now create data-quality problems.

Release status nobody checked. CBSA's Customs Notice 25-22 confirms the CARM Release Prior to Payment transition ended May 20, 2025. Importers without the required security must pay duties and taxes at release. A carrier can transmit a perfect ACI and still have the truck held because the importer's release path was never set up.

Carrier profile and code drift. Under section 32 of the Reporting of Imported Goods Regulations, carriers must report profile changes without delay, now through the CARM Client Portal. Every CCN and CRN starts with the carrier code, and that code has to belong to the carrier that physically arrives. Brokers that tender to partner carriers get burned when the paperwork shows one code and another carrier's truck shows up.

FAST treated as a lane preference. FAST eligibility is set shipment by shipment, and CBSA's eManifest notices (ECCRD Chapter 11, version 7.0) can tell a carrier that a shipment qualifies for a FAST lane or no longer does. A FAST-card driver hauling for a non-qualifying importer does not get the lane. If planning assumed FAST, the loss of the 30-minute U.S. window and the promised transit time comes as a surprise.

Outage days with no paper. CBSA's maintenance notice of October 22, 2026, covering October 24 and 25, repeated the standard contingency: drivers carry two copies of arrival paperwork, CBSA accepts paper during maintenance and for two hours after, and no penalties apply for failing to transmit in that window. Shops without a written outage procedure find out at 6:00 a.m. on a Sunday whether their drivers have printed copies.

Asset, broker, hybrid: who carries what

Asset carriers own the filings and the penalties, and they control the most inputs: driver, equipment, seals, and route. The tension is timing. Manifests built at dispatch are fast but unstable, and manifests built at pickup are accurate but squeeze the one-hour window on short runs to the bridge. The answer is to make the manifest a gated step. When the port, equipment, or driver changes, a correction is required, and the load cannot move to "en route to border" until the ACI is accepted and the customs broker's release status is visible.

Freight brokers usually don't file ACI, but they supply the data that makes filing possible. A broker that passes along "general merchandise" passes along the CBP rejection and the C382 exposure. Gate cross-border tenders on precise commodity descriptions, a confirmed customs broker, and a CBSA carrier code and SCAC that match the truck that will actually arrive. Name an owner for port changes after dispatch.

Hybrids carry both exposures plus one of their own: each side assumes the other filed. When the asset division takes a brokered load, assign ownership of the manifest, the PARS confirmation, and release follow-up explicitly.

Encode the border in the workflow

A reefer carrier running produce into Ontario, a flatbed fleet moving steel through Emerson, and a brokerage covering consolidated freight out of the Midwest face the same regulations and very different failure points. Serious shops write their own border rules into how their system behaves, instead of keeping them in a binder:

  • Statuses that mirror border reality: "ACI accepted," "PARS/PAPS confirmed," "release status known," and "FAST eligible" as separate states that gate the load.

  • Change triggers: any edit to the port, driver, tractor, or trailer automatically opens a timestamped correction task.

  • Owned reference data: port codes, Detroit firms codes, carrier codes, SCACs, and driver FAST IDs kept as validated fields, each with an owner.

  • Permissions that match liability: only people who understand the penalty exposure can reroute a manifested load.

  • Billing tied to border events: secondary exams and outage delays captured as accessorials, not absorbed.

  • A penalty ledger: every penalty notice logged against lane, customer, and root cause, because escalation runs on a 12-month window.

Before November 24

  1. Replace any stored ACE IDs with driver FAST IDs.

  2. Add Gordie Howe as its own crossing in routing and manifest reference data, with the correct firms code for each Detroit crossing.

  3. If you haul express-network freight, confirm in writing who files the truck manifest after November 24.

  4. Check lanes through St-Cesaire and East Farnham for the sufferance warehouse change.

  5. Write and test a one-page outage procedure.

  6. Sort the last 12 months of penalty notices by failed handoff.

FAQ

How far in advance must ACI eManifest data reach CBSA for a highway crossing?

CBSA must receive and validate highway cargo and conveyance data at least one hour before the truck arrives at the first Canadian port of arrival. Data sent inside that hour may draw a C379 penalty. Data sent on or after arrival is treated as none under C378.

Does correcting an ACI eManifest restart the one-hour clock?

No. Under CBSA guidance, only cancelling and resubmitting the transmission restarts the clock. A port change still has to be sent as a correction without delay.

What changes when CBP ends "flying trucks" on November 24, 2026?

Cargo crossing into the United States by truck must be reported on a truck e-manifest instead of with air manifest data. CBP rescinded the practice on August 26, 2026 under 19 CFR 123.92 and allowed a 90-day transition.

Which identifier should a U.S. truck e-manifest use for a FAST driver?

The driver's FAST ID, since CBP retired the ACE ID for this purpose effective February 24, 2026.

Who pays a CBSA AMPS penalty for bad eManifest data on a brokered load?

CBSA issues the penalty to the party responsible for transmitting the data, which for highway cargo and conveyance reports is normally the carrier. Inaccurate data supplied by a broker or shipper can still lead to a C382 penalty for the carrier that filed it.

Is the Gordie Howe International Bridge a separate crossing for e-manifest filing?

Yes. CBP identifies it within Port of Detroit 3801 by firms code H0E1, and CBSA requires the ACI to name the port the truck actually uses.

Every Business Deserves
Software as Unique as it is.

Every Business Deserves
Software as Unique as it is.

Every Business Deserves
Software as Unique as it is.