Portal Messages Delayed, Paper Fallback Active — What It Actually Means for Your Monday Filing Slate

Update 45 Means the System Works, Sort Of

The CBSA posted its forty-fifth Systems Outage Contingency Plan notice Friday morning. The inbound data pipe is open, EDI and eManifest submissions are landing, and the agency is processing them. The problem sits on the return trip: outbound acknowledgements, release confirmations, and accounting receipt messages are running late. Some clear in minutes, others take hours, and a handful sit in limbo long enough that you start drafting the paper CAD just to hedge the clock.

The SOCP remains active, which means CBSA will accept paper entries at the border and at inland offices. That’s the safety valve, but it’s not the default you want to reach for unless the delay threatens a genuine deadline — a perishable release window, a just-in-time production cutoff, or a Friday afternoon where waiting until Monday isn’t an option.

Most of the time, the outbound message shows up. The question is whether it shows up in time for the next step in your workflow, and that depends entirely on what you’re filing and when the cargo is moving.

Where the Delay Hits Hardest

PARS releases rely on the ACE/ACI exchange and the outbound cargo control message. If that message lags by two hours, your carrier may not have the green light when the truck rolls to the primary inspection lane. The driver waits, or gets waved to secondary, or the whole load sits at the CFS until the status updates. RMD (Release on Minimum Documentation) entries are less sensitive because the release decision happens upstream of the full CAD accounting, but the same outbound lag can stall your ability to close the accounting window on time if you’re filing within the five-day clock.

CAD submissions under CARM post to the declarant’s ledger once CBSA accepts and processes the entry. The outbound receipt confirms that posting and triggers the payment or RPP bond draw. If that confirmation message is delayed, you lose visibility into whether the entry hit the ledger, whether the bond was accessed, and whether any errors or holds were applied. You can check the CARM Client Portal manually, but that adds time and you’re still waiting for the same backend process to finish.

For NRI (Non-Resident Importer) filings, the stakes are higher because the importer of record may not have direct portal access and is relying on the broker to confirm the entry cleared and the duty or GST account was charged correctly. A four-hour outbound delay turns into a same-day question from the client, and you’re stuck answering “submitted, waiting on CBSA” without hard proof.

When to File Paper and When to Wait

The SOCP exists because CBSA knows some shipments can’t wait. Perishables, pharmaceuticals under cold-chain, just-in-time automotive components, anything with a hard delivery window — those are the loads where paper makes sense. You walk the entry to the border or the inland office, the officer stamps it, and the cargo moves.

Everything else is a judgment call. If you’re filing a standard commercial PARS entry Monday morning for a load that arrived Sunday night and isn’t scheduled for pickup until Tuesday, the outbound delay is annoying but not fatal. You submit EDI, you wait, and if the confirmation doesn’t land by end of business Monday, you escalate or file paper Tuesday morning.

If you’re filing Friday afternoon for a Monday pickup, the risk is real. The outbound message might not arrive until Saturday or later, and your client’s drayage team is expecting release confirmation before they dispatch. That’s when you consider paper from the start, or you file EDI early Friday and plan to re-file paper Monday if needed.

We’re running dual-track on anything time-sensitive right now: EDI first, paper standby. It doubles the admin load, but it keeps cargo from sitting an extra day because we bet on the system and lost.

The CARM Ledger and Payment Timing

Under CARM, the CAD posts to your ledger and the payment or bond access happens as part of the same transaction. The outbound receipt is your proof that it went through. If that receipt is delayed, you don’t know for certain whether the bond was drawn, whether a hold was placed, or whether CBSA flagged the entry for verification.

The CARM Client Portal will eventually reflect the posting, but “eventually” can mean hours or the next business day, and that lag creates a blind spot. If you’re managing a portfolio of entries across multiple importers and you’re waiting on a dozen outbound receipts, you lose the ability to reconcile the day’s filings in real time. The K84 monthly statement will catch it, but that’s backward-looking. You need to know today whether the entry cleared and the bond got hit.

For clients operating on thin RPP bond margins, that visibility gap matters. If you can’t confirm the bond draw, you can’t tell them how much headroom remains, and they can’t decide whether to pause the next shipment or top up the account. We’ve been pulling portal snapshots twice a day just to close that loop manually.

eManifest and the ACI Reporting Window

The eManifest side of this outage is less disruptive for most brokers because the ACI (Advance Commercial Information) submission happens before the truck crosses, and the acceptance message usually lands fast enough to keep the carrier moving. The problem shows up when the outbound acknowledgement is delayed and the carrier’s dispatch system doesn’t update, or when a correction or amendment is needed and the confirmation of that change doesn’t come back in time.

For shipments with OGD (Other Government Department) holds — CFIA inspections, Health Canada permits, anything requiring a FIRMS code or an import license — the outbound delay can stall the release even if the ACI itself was clean. CBSA may have cleared the entry internally, but if the release message doesn’t reach the warehouse or the CFS, the cargo sits.

Our Montreal sufferance warehouse team has been checking portal status manually for any load flagged by OGD or exam, rather than waiting for the outbound message to hit the WMS. It’s a workaround, not a solution, but it keeps the dock moving.

How Long This Lasts and What Comes Next

CBSA hasn’t given a firm end date for the SOCP. “Residual delays” is the language in Update 45, which suggests the worst is over but the system isn’t back to normal. The inbound side is stable, the processing queues are clearing, and most outbound messages are landing within an acceptable window. The tail risk is the occasional multi-hour lag or the message that never arrives at all.

If you’re filing high-volume PARS entries daily, you’re already building buffer time into your schedule. If you’re handling lower-volume but high-stakes loads — NRI filings, SIMA-subject goods, CUSMA origin claims under verification — you’re probably running parallel paper just in case.

We expect the SOCP to lift once CBSA sees a week of clean outbound message flow with no reported escalations. Until then, treat EDI as the primary path and paper as the backup you keep in your pocket.

The CAD filing calendar doesn’t stop for system lag. If your EDI submissions are piling up without confirmation and your client’s cargo is sitting at the port, that’s the call we’re built to take. Get in touch.

Source: CSCB