CanFlow Global
← All insights
cbsa-maintenancecarm-portalsocpcustoms-brokeragesystem-outage

CBSA July 16 Maintenance: Skip the Panic, Know the SOCP

CBSA's Thursday morning maintenance window is a non-event, but it's a good reminder to audit your System Outage Contingency Plan readiness before the next unplanned portal failure lands on a Friday afternoon.

CBSA sent another scheduled maintenance notice for Thursday, July 16, from 04:00 to 05:00 ET. No planned outages, services should stay up. The usual line: follow the System Outage Contingency Plan procedures during the window.

This one’s a non-event. A one-hour maintenance slot at 4 a.m. with no expected downtime means CBSA is patching something in the CARM stack and doesn’t expect commercial traffic to notice. You’ll file your morning CADs the same way you always do.

But the notice is a good reminder to revisit what the System Outage Contingency Plan actually means when things DO go sideways, because eventually they will.

The SOCP in Practice

The CBSA System Outage Contingency Plan is the fallback protocol when CARM Portal, eManifest, or ACI goes dark. In theory, it’s straightforward: revert to paper or fax procedures, notify the port, and file electronically once systems are back.

In practice, most brokers don’t touch the SOCP procedures until they’re forced to, which means the first time you need them you’re reading the manual while a driver is idling at the port waiting for a release.

The core pieces:

  • eManifest / ACI submissions: If the system is down before arrival, you fax the cargo control document to the CBSA office. You still need the cargo control number, which means you need the manifest lodged before wheels hit Canadian soil. If the system comes back up mid-transit, you submit electronically and reference the faxed copy.
  • Release requests: PARS and RMD releases default to manual clearance. You’re calling or faxing the port to confirm the release instead of polling the portal for an RNS (Release Notification System) message.
  • CAD filings: CARM Portal outages don’t excuse late payment. You file on paper or via the legacy fallback mechanism (if you still have access credentials), then reconcile once the portal is back. The due dates don’t move.

Most of this is documented. The part that isn’t is the timing lag when you’re working off-system. A normal PARS release might clear in 15 minutes during off-peak. The same release via fax during a CBSA outage can sit for two hours because every broker in the country is doing the same thing and the port staff are triaging by hand.

Where the Risk Sits

The real exposure isn’t a planned one-hour window at 4 a.m. It’s an unplanned outage during peak filing hours, which happens a few times a year and always seems to land on a Friday afternoon.

If CARM Portal goes dark at 2 p.m. on a Thursday and you’ve got a container that needs to cross-dock and ship Friday morning, you’re filing manually and hoping the release clears before end of business. If it doesn’t, your freight sits overnight.

For customs brokerage clients running release prior to payment (RPP) bonds, the stakes are higher. RPP release depends on real-time CARM Portal validation of your bond balance and account standing. If the portal is down, CBSA defaults to cash or certified payment for release. That means a container that would normally release in 20 minutes now requires a trip to the bank or a wire transfer, and you’ve just added four to six hours to your clearance timeline.

Warehouse operators feel this downstream. A delayed release means a delayed dock appointment, which cascades into drayage detention, missed cross-dock cutoffs, and LTL carriers bumping your freight to the next day. We work with FENGYE LOGISTICS on the Montreal dock side, and a four-hour clearance delay routinely turns into a 24-hour dwell time once you factor in dock scheduling and carrier windows. The math is simple: Port of Montreal inbound drayage window closes at 15:00 for same-day cross-dock. Miss it and your freight sits until tomorrow.

What to Have Ready

Most importers don’t think about SOCP procedures until they need them. By then it’s too late to fix the gaps.

Here’s what should be on file now:

  • CBSA port contact list: Direct phone and fax numbers for every port you clear through. Not the general 1-800 line. The actual commercial operations desk.
  • Carrier manifest copies: Hard copies or accessible PDFs of your last 30 days of manifests. If eManifest is down and you need to reference a prior shipment, you don’t want to be digging through email threads.
  • CAD filing credentials for legacy systems: CARM Portal is the primary interface, but the legacy Electronic Data Interchange (EDI) submission paths are still live as a fallback. If your brokerage doesn’t have credentials configured, you’re filing on paper.
  • RPP bond documentation: A current copy of your bond and a direct contact at your surety. If CBSA questions your bond balance during an outage, you need to be able to produce proof on the spot.

The one thing that doesn’t help: calling CBSA’s Border Information Service line during an outage. They’ll tell you the system is down and to follow SOCP procedures. You already knew that. What you need is the port operations contact who can manually verify your release.

Thursday Morning: Business as Usual

For this week’s maintenance window, you don’t need to do anything. CBSA expects no service interruption. File your CADs when you normally would. Your morning PARS releases will clear the same way they did yesterday.

But if you haven’t looked at your SOCP readiness in the last year, now’s a decent time. The next outage won’t send a calendar invite.

If your compliance program doesn’t have a documented CBSA outage procedure, or if you’re not sure whether your RPP bond would survive a portal failure during peak filing hours, that’s the kind of audit we run all day. Get in touch.

Source: CSCB

Talk to a broker