eManifest Portal Forced Re-Logon June 13–14: What Breaks When the Session Drops

The Notice

CBSA published TCC26-0111 on May 29: eManifest portal users will experience forced re-logon Saturday June 13 from 06:00 to 07:00 ET and again Sunday June 14, same window. Portal functionality stays live—you can still create and submit trade documents, update user access, file eManifest records—but your session will drop and you’ll need to log back in.

The notice says one hour. That’s the maintenance window, not the re-logon delay. If your broker is in the middle of updating a cargo control number or correcting an ACI transmission when the session kicks at 06:00, the update doesn’t post until someone logs back in and resubmits. On a Saturday or Sunday morning, that someone may not be at a desk.

What Actually Breaks

Most customs brokerage work doesn’t touch the eManifest portal. We file CADs through EDI, we submit PARS and RMD releases through the CBSA Assessment and Revenue Management (CARM) Client Portal, and cargo control updates usually flow automatically when the carrier transmits the ACI record and we reference the CCN in the CAD.

But there are three scenarios where a forced logout at 06:00 on a weekend morning costs you a release window:

1. Manual Cargo Control Corrections

Carrier transmitted the wrong piece count, wrong consignee BN15, wrong description. CBSA won’t release until the ACI record matches the CAD. If the carrier isn’t staffed to fix it, the broker logs into the eManifest portal and submits the correction. That correction posts immediately—unless your session drops mid-transaction. Now the correction sits in limbo until someone notices, logs back in, and resubmits. A container that should have cleared Saturday morning sits until Monday.

2. Split Shipments and Supplementary CAD Filing

One CCN, two importers. You file the first CAD Friday night, CBSA releases part of the shipment, and you need to update the eManifest record to reflect the partial release before filing the second CAD. If that update happens at 06:05 Saturday and your session just dropped, the second CAD won’t post clean. CBSA’s system sees a mismatch between the CAD and the cargo control record, flags it, and you’re into Monday morning cleanup.

3. Late-Arriving PARS Updates for Weekend Exam Release

CBSA exams a PARS shipment Saturday morning, issues the K84 release notation, and the broker updates the eManifest portal to close the file. If the session drops before that update posts, the shipment shows as still under exam in CBSA’s system. The drayage carrier shows up Sunday to pull the container, the terminal won’t release it because CBSA’s portal still shows “exam pending,” and the container sits until Monday when someone notices the update never went through.

None of these are catastrophic. They’re all fixable Monday morning. But if your weekend drayage window is tight—especially inbound to a Montreal sufferance warehouse with a Monday cross-dock cutoff—burning Saturday and Sunday release capacity because a session dropped at 06:00 turns a small maintenance notice into a two-day delay and a missed delivery window.

What You Can Do

The fix is procedural, not technical. If you know your broker is filing cargo control updates or ACI corrections manually through the eManifest portal, and you have shipments scheduled to clear Saturday June 13 or Sunday June 14, tell them to avoid the 06:00–07:00 window. File the updates Friday night or wait until 07:30 Saturday. If the shipment is already under exam and the release depends on a Saturday morning update, make sure someone is actually watching the portal after 07:00 to confirm the session reconnected and the update posted.

Most brokers who run weekend operations already have a protocol for this. The ones who don’t are the ones who treat Saturday filings like weekday filings—submit and assume it posted. That assumption breaks when the session drops.

The Bigger Pattern

This is the fourth scheduled eManifest portal maintenance notice since CARM full deployment in October 2024. CBSA schedules them for early Saturday or Sunday mornings because that’s when trade volume is lowest, and the one-hour window is short enough that most filers won’t notice. But “most filers won’t notice” isn’t the same as “no operational impact.” If you run weekend release cycles, you notice.

The CBSA’s CARM Client Portal has been stable. The eManifest portal is older infrastructure—pre-CARM, pre-RPP bond, pre-CAD—and it still handles cargo control, ACI transmission, and carrier-level updates. CBSA isn’t going to retire it until the eManifest modernization project finishes, and that’s not scheduled until 2027. Until then, expect these maintenance windows every quarter, always early weekend mornings, always with the same one-hour forced re-logon.

If your compliance program includes weekend clearance SLAs, make sure your broker knows when these windows are and has a protocol to avoid filing during them. If your broker is still treating eManifest portal updates as fire-and-forget, that’s a gap.

What We’re Doing

We don’t file cargo control updates between 05:45 and 07:30 on scheduled maintenance days. If a shipment needs an ACI correction or a cargo control close-out during that window, we either file it Friday night or wait until 07:30 and confirm the session reconnected before submitting. If CBSA releases a container Saturday morning and the eManifest update has to post before drayage pulls it, we log back in at 07:00, resubmit if the session dropped, and confirm the update shows in CBSA’s system before we tell the carrier to dispatch.

It’s not complicated. It’s just a step that doesn’t exist on weekday filings, and if you don’t know the maintenance window is happening, you don’t take the step.

If you’re running weekend inbound and your broker hasn’t mentioned the June 13–14 eManifest maintenance window, ask them how they’re handling it. If the answer is “we didn’t know,” that’s a problem. Get in touch.

Source: CSCB