When CBSA's IID Messaging Goes Dark

The CBSA’s Integrated Import Declaration system went quiet for seven and a half hours on Sunday, August 11. Incoming IID messages were received, but outbound responses (acknowledgments, rejects, release notices) sat in queue until 22:30 ET. The system has been stable since.

This one landed on a Sunday afternoon, so the operational fallout was light. Most brokers don’t file customs entries on Sunday unless a commercial urgency forces it. But if the same delay hits on a Tuesday morning during live import windows, the cost stack changes fast.

What IID Actually Is

IID is the CARM-era replacement for the old ACI/eManifest entry pathway. When a broker files a Commercial Accounting Declaration (CAD) electronically, the IID message carries the entire customs entry to CBSA in a single transmission: HS classification, declared value, duty and GST calculation, CUSMA or CETA origin claim, importer of record details, all of it.

The outbound messages matter just as much as the inbound filing. An ACK (acknowledgment) tells you CBSA received the entry and it’s in their system. A reject message tells you what’s wrong (missing SIN/BN15 registration, invalid HS code, SIMA flag on subject goods, whatever) so you can fix and refile. A release notice tells you the goods are legally released and the importer can take possession.

When those outbound messages stop flowing, brokers are flying blind. You don’t know if your CAD was accepted, rejected, or stuck in limbo. You don’t know if release has been granted. You can’t move cargo until you have confirmation.

When a Delay Matters

A Sunday afternoon delay is a non-event for most import workflows. Goods arriving Friday or Saturday are already released or sitting in exam. Monday arrivals haven’t hit the border yet. The few entries filed Sunday (usually perishables, time-sensitive consolidations, or importers trying to beat a long weekend) can wait a few hours without much consequence.

A Tuesday morning delay is a different animal. PARS pre-arrival filings for commercial trucks need release confirmation before the driver hits the border. If CBSA’s acknowledgment system is down, drivers sit in queue or get turned back. RMD (Release on Minimum Documentation) entries filed at 06:00 for an 08:00 warehouse delivery window need that release notice in hand before the carrier will unload. No notice, no unload, and your inbound schedule collapses.

Detention and dwell time costs start accruing immediately. A delayed release notice on a Tuesday morning import can push delivery to Wednesday, which pushes your cross-dock cutoff, which turns a same-day transload into an overnight hold. At Montreal rates, that’s the kind of cascading cost most importers don’t budget for.

What Brokers Do When Messaging Goes Dark

The first move is to check the CBSA technical notices page. In this case, CBSA posted the delay at 15:00 and the resolution at 22:30. If it’s a known system issue, you know it’s not your filing and you wait.

If the delay notice doesn’t cover your time window, you log into the CARM Client Portal and check entry status manually. The portal shows whether your CAD was received, whether it’s under examination, whether release has been granted. It’s slower than real-time EDI messaging, but it works when the automated system doesn’t.

If you’re filing a time-sensitive entry and the portal shows nothing, you call the CBSA commercial operations line for your port of entry. They can pull up the entry by cargo control number and confirm status. It’s not fast, but it’s the fallback when electronic messaging is down.

The worst case is when you have no confirmation at all and the importer is standing at the warehouse dock waiting for cargo. At that point, you’re making a judgment call: wait for CBSA to confirm release, or advise the importer to take possession and hope the release notice catches up. Most brokers won’t advise taking possession without confirmation. If CBSA later flags the entry for exam or issues a detention notice, the importer is on the hook for penalties.

The CARM Client Portal as Stopgap

CBSA built the CARM Client Portal as the universal interface for importers and brokers to manage entries, bonds, financial security, and accounting statements. It’s clunky compared to the old ACI/eManifest workflow, but it does have one advantage: when the IID messaging layer fails, the portal usually stays up.

You can file a CAD through the portal if your EDI channel is down. You can check release status, review K84 monthly statements, upload supporting documents for an exam, and confirm your Release Prior to Payment (RPP) bond balance. It’s not built for high-volume customs brokerage work (brokers moving 200 entries a day aren’t clicking through a web form for each one), but it works for the handful of critical entries that need to move when the automated system is offline.

If you’re an importer managing your own customs program without a broker, the portal is your only interface to CBSA. When IID messaging goes down, you won’t notice unless you’re actively waiting for a release notice. The portal will show the same status either way.

This One Was Low-Impact, But the Next One Might Not Be

Sunday afternoon, seven and a half hours, resolved same day: this delay was about as benign as they come. No one missed a commercial delivery window. No cargo sat in exam longer than it otherwise would have. The few entries filed during the outage were processed once the queue cleared.

But the same technical issue hitting Tuesday morning at 06:00 would have real operational cost. PARS filings for commercial trucks, RMD entries for tight delivery windows, release-prior-to-payment confirmations for high-value shipments all depend on real-time CBSA messaging. A seven-hour delay during live import hours would push deliveries, blow cross-dock windows, and rack up detention fees across every major port of entry.

The CBSA has been relatively stable since CARM went mandatory in May 2024, but the system still has rough edges. Outbound message delays, portal timeouts, and K84 statement discrepancies are routine enough that most brokers have a backup workflow ready. When the primary electronic channel fails, you fall back to manual portal checks and phone calls. It’s slower and it doesn’t scale, but it keeps cargo moving.

If your import program depends on tight delivery windows and just-in-time inventory, the broker you work with should have a documented escalation plan for when CBSA messaging goes dark. That plan should include portal access, direct CBSA contact numbers for your primary ports, and a threshold for when to hold cargo vs when to advise release without electronic confirmation. Our Montreal partner FENGYE LOGISTICS runs the same backup workflow on the physical side when release confirmations are delayed.

We run this playbook a few times a year. If your current broker doesn’t have one, get in touch.

Source: CSCB