The SOCP isn't new, but this version is clearer on who does what when systems go down
CBSA published a revised System Outage Contingency Plan on April 16, 2026. The SOCP has been around for years, but this refresh separates import and export procedures more cleanly, adds definitions that should've been there from the start, and—most importantly—clarifies broker, carrier, and importer responsibilities when CARM Client Portal, EDI, or eManifest services drop.
If you've been through a CARM outage in the last two years, you know the drill: portal freezes, no one can pay duties, release grinds to a halt, and the CBSA service centres start fielding calls they can't answer because the fallback process was buried in a 40-page PDF no one read. This update tries to fix that last part.
What changed
The big operational shifts:
Import vs export is now split out. Previous versions lumped everything together. Now there are separate flowcharts and procedures for import data transmission (B3s, PARS, RMD, payment messaging) versus export data (eManifest ACI, ACAS). If your operations touch both sides, you need to bookmark both sections. If you're import-only, you can ignore half the document.
Role definitions are explicit. The old SOCP was vague on whether brokers, importers, or carriers were supposed to do certain things during an outage. The new version breaks it down: brokers handle release-related fallback (paper B3s, faxed release requests), carriers handle ACI/CCN fallback, importers handle payment if CARM CPP is down and you're outside the RPP envelope. It's still not perfect, but at least there's a rubric now.
Electronic data submission requirements are clarified. This matters for CARM RPP clients especially. If the portal is down but EDI is still up, you're expected to transmit your B3 and payment via EDI, not fall back to paper. If both are down, paper B3 is acceptable, but you'll need to re-key everything once systems recover, and CBSA won't backdate payment timestamps. That means if you're cutting it close on the RPP due date and an outage hits, you could land offside and trigger a compliance review.
The definitions section is long overdue. Terms like "unplanned outage," "degraded service," "partial availability," and "manual fallback" are now spelled out. In practice, CBSA sometimes calls a slowdown an "outage" and other times calls a full blackout "degraded service." The new SOCP at least tries to standardize the language, which should make TCC notices less ambiguous going forward.
What this means on the trade floor
If you're filing PARS or RMD at a high-volume BSA like Windsor or Lacolle, outages are rare but brutal. The new SOCP won't prevent them, but it does make the recovery path clearer. For example: if CBSA systems go down after a truck is in primary but before the cargo control number is transmitted, the carrier is now explicitly responsible for paper fallback on the CCN. Brokers handle the B3. Previously, that handoff was a grey zone and led to releases sitting in limbo while both sides waited for the other to act.
For air and marine, the import/export split helps. ACI eManifest is technically separate from CARM, but outages sometimes cascade. If eManifest is down but CARM is up, you can still pay and get a release number, but the cargo stays non-arrived in the system until ACI recovers. The SOCP now has a dedicated section on that scenario, including when CBSA will manually mark a shipment as "arrived" so release can proceed.
If you're an importer managing your own CARM account and not using broker services for every entry, pay attention to the payment fallback section. If CARM CPP goes down and you're on RPP, you're not off the hook for the payment deadline. CBSA expects you to submit payment via the alternate channel (usually EDI if your software vendor supports it, or a manual process through your financial institution). Miss the window and you're looking at penalty interest, possible RPP suspension, and a compliance file review that will eat weeks of your time.
The real risk is still CARM RPP payment timing
The SOCP update is fine, but it doesn't solve the underlying problem: CARM's payment architecture is fragile, and the RPP bond math is unforgiving. If you're importing high-duty goods—SIMA subject steel, textiles, anything with a hefty 9897 relief or provisional duty—your RPP envelope can swing wildly month to month. An outage that delays payment by 48 hours can push you over your bond limit, freeze future releases, and trigger a forced switch to release prior to payment (which kills your cash flow).
We've seen this happen twice in the last year. CBSA's contingency plan says they'll extend deadlines "where operationally feasible," but that's discretionary. The revenue officers handling your file won't know there was an outage unless you document it, escalate it, and reference the specific TCC notice. The SOCP now says brokers should log outage timestamps and include them in any fallback submissions, which is helpful, but it's still on you to make the case.
If your compliance setup doesn't include a process for tracking CBSA system status and logging outages in real time, add it now. When a payment deadline is at risk, you need contemporaneous evidence, not a vague memory that the portal was slow two weeks ago.
Bottom line
The updated SOCP is a modest improvement. It won't prevent outages, but it makes the fallback procedures less ambiguous and separates import from export in a way that's overdue. If you've never read the SOCP, skim it once. If you have a high release volume or tight RPP payment windows, read the import payment section carefully and make sure your team knows the drill.
Most outages are short and routine. The ones that aren't routine are the ones that cost you money, and the SOCP is your playbook for those.
If you're running RPP and want a second look at your bond sizing or fallback process, that's exactly the kind of operational review we do regularly. Get in touch.
Originally published at https://www.canflow-global.com/en/insights/cbsas-updated-system-outage-contingency-plan-what-actually-changed-and-why-you-s/.
