eManifest Portal Maintenance July 4–5, 2026: What Actually Gets Blocked and What Doesn't
CBSA scheduled a one-hour re-logon window each morning July 4 and 5, 2026. Portal stays up, EDI stays up, you can still file. Here's what that means for weekend ACI filings and Monday morning release work.
The Notice
CBSA published TCC26-0116 announcing eManifest Portal maintenance on Saturday July 4 and Sunday July 5, 2026, from 06:00 to 07:00 ET each day. The notice says portal users may experience forced re-logon during that window. It also says you can still create and submit all trade documents and update user accesses.
That second sentence matters. This is not a portal blackout. This is a session-timeout event during a one-hour window on a weekend morning when almost nobody is filing manually anyway.
What Actually Happens
If you’re logged into the eManifest Portal at 06:00 ET on either day, your session will probably drop and you’ll need to sign back in. That’s it. The portal itself stays up. You can still create ACI cargo reports, CCNs, amendment records, all of it. You just might need to re-authenticate mid-workflow if you happen to be in there during that hour.
EDI filers are untouched. If your software transmits ACI electronically through your service provider, this maintenance window does not affect you. The CBSA eManifest system processes EDI messages independently of the web portal login infrastructure.
Most brokers run EDI for volume work. The portal is for one-offs, corrections, and smaller carriers who don’t have integrated dispatch software. If you’re filing fifty PARS releases a day, you’re not doing it by hand.
Weekend ACI Filing Context
July 4 and 5, 2026 are a Saturday and Sunday. Most commercial highway freight that crosses Friday evening or Saturday morning had ACI filed Thursday or Friday during business hours. PARS pre-arrival filings typically go in one business day before estimated arrival, sometimes two if it’s a long-haul move from California or the southern states.
For maritime and rail, lead times are longer. Container vessels into Montreal usually have ACI transmission windows that close 24 hours before arrival at the first Canadian port. If you’re bringing a boxship into the Port of Montreal on Monday morning, your eManifest cargo reporting is done by Sunday morning at the latest, often earlier. A one-hour session timeout Saturday and Sunday between 06:00 and 07:00 is outside that workflow unless something went wrong and you’re filing a late amendment.
Rail movements follow a similar pattern. Class I carriers transmit consist data well ahead of the border. By the time the train is rolling through Cornwall or Emerson, the ACI is already in CBSA’s system and the release paperwork is either done or waiting on the CAD to clear.
What This Means for Monday Morning Release Work
Nothing, practically. If you’re a broker preparing PARS or RMD releases for Monday pickup, your ACI filing happened Friday or over the weekend outside that maintenance window. The CAD itself is filed through CARM Client Portal, not eManifest. Two different systems.
The eManifest Portal handles pre-arrival cargo reporting: ACE eManifest for highway, ACI cargo reports for marine and rail, close messages, amendment records. The CARM Client Portal handles the commercial accounting declaration, duty and tax payment, RPP bond authorizations, the whole release-and-accounting stack that replaced the old Form B3 process.
If your shipment is crossing Monday and you’re filing the CAD Monday morning for release prior to payment, the eManifest maintenance on Saturday and Sunday is irrelevant. You’re working in a different system entirely.
The One Scenario Where This Matters
You’re a small manual filer, you had a last-minute load cross Saturday morning or early Sunday, and you’re logging into the eManifest Portal by hand to create the ACI cargo report because you don’t have EDI transmission capability. You sit down at 06:15 ET, start entering the CCN and shipment details, and your session times out halfway through.
You log back in. It takes thirty seconds. You finish the record and submit. The shipment clears normally.
That’s the risk profile here. An annoyance, not a blockage.
Why CBSA Publishes These Notices
Because the portal is a transactional system tied to bond security, release authorization, and cross-border commercial movement that runs 24/7. Any service interruption, even a planned one-hour authentication refresh on a weekend morning, gets a formal technical client communication. It’s the same reason you see TCC notices for CARM Client Portal maintenance, AMPS processing delays, or temporary EDI message validation changes.
The notice format makes every event look like a crisis. Most of them aren’t. You learn to read the description block, not just the subject line. “Forced re-logon” during a weekend hour when the portal itself stays up and EDI is unaffected is not the same as “portal offline, no ACI transmission possible” during a weekday afternoon.
If you run a brokerage operation that files fifty to two hundred entries a day, you see these notices weekly. Half are routine patch cycles. A quarter are middleware updates that only affect specific message types you don’t use. The rest are real: extended outages during CARM system deployment, for example, or the multi-day portal lockouts that hit in early 2024 when the bond migration went sideways.
This one is routine.
What You Should Actually Do
Nothing, unless you’re one of the three people in Canada who manually files ACI through the web portal on a Saturday morning at 06:00 ET. If that’s you, plan to log in at 07:15 instead, or file Friday afternoon.
If you run EDI, ignore the notice. If you’re a carrier using integrated dispatch software that transmits ACI automatically, ignore the notice. If you’re an import manager whose broker handles all the pre-arrival filings, ignore the notice.
If you’re responsible for filing and you’re not sure whether your operation runs EDI or portal, ask your service provider now. That’s a more important question than this maintenance window. Manual portal filing doesn’t scale past a handful of entries a week. If your import volume is growing and you’re still clicking through web forms one shipment at a time, that’s the operational gap worth fixing.
We run EDI for everything except corrections and the occasional manual override. The eManifest Portal is a backup tool, not a daily workflow. When CBSA schedules weekend maintenance on the authentication layer and the actual transmission pipeline stays up, it doesn’t touch our release schedule.
If you’re stuck filing ACI by hand and want to know what an EDI setup looks like, get in touch. }
Source: CSCB