eManifest Portal Maintenance May 23–24, 2026: What the One-Hour Re-Login Window Actually Means

The Notice

CBSA published TCC26-0102 last week: eManifest Portal users will face forced re-login Saturday, May 23, 2026 from 06:00 to 07:00 ET and again Sunday, May 24, 2026 during the same window. Portal access stays live. You can still create cargo documents, submit ACI, and manage user permissions. You’ll just be logged out mid-session and need to sign back in.

Most importers won’t feel this. If your broker handles your ACI filing and you don’t touch the eManifest Portal yourself, this is background noise. If you’re filing your own PARS or RMD pre-arrival notifications, or if your inbound freight moves on weekends, you need to know what breaks.

What the eManifest Portal Actually Does

The eManifest Portal is CBSA’s web interface for carriers, freight forwarders, and brokers to transmit advance cargo data before goods arrive at the Canadian border. Pre-Arrival Review System (PARS) and RMD filings both flow through here, along with ACI cargo control documents, conveyance reports, and close messages.

If you’re an importer using a licensed broker for all inbound shipments, your broker’s software handles ACI submission in the background. You never log in. The maintenance window is invisible to you.

If you’re a non-resident importer filing your own ACI, or if you’re a 3PL managing multiple importers’ cargo documents, or if you run a bonded warehouse that closes PARS loads on weekends, you’re the user CBSA is warning.

The One-Hour Window Is Tight, Not Long

CBSA calls this “maintenance,” but the operational tell is the forced re-login. They’re not taking the system offline. They’re cycling sessions. That usually means certificate rotation, credential refresh, or security patch deployment that requires all active tokens to expire and re-authenticate.

One hour is short. Most CBSA system outages run four to six hours minimum when they’re patching the transaction layer. A one-hour forced logout means the back-end stays up and the front-end just kicks everyone out once. You log back in, your session resumes, and you keep working.

The risk isn’t downtime. The risk is timing.

Where This Bites: Weekend PARS and Sunday Morning Releases

Most commercial highway freight crosses Monday through Friday during daytime hours. PARS submissions happen Thursday and Friday afternoon for Monday delivery. Weekend ACI filings are rare unless you’re running perishables, JIT automotive, or e-commerce cross-border parcels.

But if you do run weekend releases, May 23–24, 2026 is a Saturday and Sunday. If your carrier delivers to a CBSA commercial port on Sunday morning and your broker files the PARS close message at 06:15 ET, they’ll be logged out mid-transaction. The submission won’t fail. It’ll just require a second login and re-send. That’s a five-minute delay, not a crisis.

The same applies to RMD filings. If you’re filing Release on Minimum Documentation for a rail container arriving Sunday at CN Brampton, and you hit submit at 06:30 ET, expect the timeout. Log back in, confirm the transaction posted, and move on.

If you’re using our brokerage for weekend customs work, we’ll handle the re-login. You won’t see it. If you’re self-filing ACI and this is your first forced logout, just know that CBSA’s System Outage Contingency Plan (SOCP) still applies even when the portal itself is live. You can call the CBSA commercial client line to confirm receipt if the web UI is acting up during the window.

The Bigger CARM Context: Why CBSA Is Cycling Credentials More Often

Since CARM went mandatory in October 2024, CBSA has been patching the Client Portal and eManifest authentication layers more frequently than they did under the old ACROSS system. The legacy B3 infrastructure ran for years without credential rotation. CARM’s token-based authentication model requires regular certificate updates, and CBSA is still calibrating the maintenance cadence.

We’ve seen three forced re-login events in the CARM Client Portal since launch. None lasted longer than 90 minutes. The eManifest Portal runs on separate infrastructure, but the authentication backend is now shared with CARM for single sign-on purposes. That’s why the maintenance notice mentions “Portal users will still be able to create and submit all trade documents” but doesn’t promise zero interruption. The session layer is what’s cycling, not the data submission layer.

If you’re managing multiple user accounts under your Business Account Manager (BAM) role, this is a good reminder to audit your delegated access list. Every user who’s logged into eManifest Portal during the maintenance window will need to re-authenticate. If you’ve got stale accounts or former employees still on the access list, clean them up now before May.

What to Do If You’re Filing Your Own ACI

If you’re a frequent eManifest Portal user, the action is simple: avoid starting a multi-step ACI submission or PARS close transaction at 05:55 ET on either Saturday or Sunday. If you’re mid-workflow when the logout hits, your draft should autosave, but CBSA’s portal autosave has been inconsistent since CARM. Finish your submission before 06:00 or wait until after 07:00.

If you’re filing cargo documentation for perishable goods or time-sensitive freight, coordinate with your carrier. A one-hour delay on ACI close won’t hold your truck at the border if the pre-arrival risk assessment already cleared. CBSA’s targeting happens when the ACI is first submitted, not when you close the document. The close message is administrative. A five-minute delay logging back in won’t trigger an exam.

If you’re running a bonded sufferance warehouse and you close PARS loads on Sunday mornings for Monday drayage pickup, this is the window that matters. Our Montreal sufferance operation doesn’t file PARS closes before 08:00 ET on weekends for exactly this reason. CBSA’s weekend support staffing is thin, and any portal hiccup that would take two minutes to resolve on a Tuesday can cost you 90 minutes on a Sunday.

Most Importers Can Ignore This

If you’re not logging into eManifest Portal yourself, this notice doesn’t touch you. Your broker’s EDI connection to CBSA isn’t affected. The maintenance is scoped to the web-based portal interface, not the underlying CAED (Customs Automated Exchange of Data) message layer that brokers use for high-volume ACI submission.

If your shipments move Monday through Friday and your broker handles all pre-arrival filings, you’ll never notice the logout. CBSA published this notice because they’re required to under their service standards, not because the operational risk is material.

If you’re filing your own ACI and you’ve never worked through a CBSA portal maintenance event, save the SOCP bookmark. It’s the fallback procedure for how to notify CBSA of cargo arrival when the electronic systems are unavailable. You won’t need it for a one-hour re-login window, but it’s the right reference document to keep on hand.

We run compliance reviews for importers who’ve switched from broker-managed to self-filed ACI and want a second set of eyes on their CBSA documentation workflow. The eManifest Portal is stable, but the error-handling when something goes sideways is still less forgiving than the old ACROSS fax-and-call fallback. If you’re self-filing and you’ve never stress-tested your contingency process, May 23–24 is a low-stakes weekend to dry-run it.

This is maintenance, not an outage. If your freight doesn’t move on weekends, you can skip this one. Talk to us if you’re not sure whether your ACI filing setup is affected.

Source: CSCB