IID Processing Delays Under CARM: What Actually Breaks When the System Freezes
The April 16 IID outage isn't routine noise. When CBSA's Integrated Import Declaration system goes down with no ETA, your whole release cadence collapses. Here's what's at risk and how to triage when you can't file.
The April 16 IID Outage: Not Your Usual Service Hiccup
CBSA posted TCC26-0078 on April 16 at 3:17pm ET. Integrated Import Declaration and Document Image Functionality transmission down, investigation ongoing, no estimated time of resolution. By the time Update 2 hit, they still had nothing. That’s not a blip. That’s a hard stop.
Most CBSA service notices are background noise. Regional Marine Messaging Unit slow? Fine, your Vancouver container can wait an extra hour. ACI eManifest reject codes acting up? Annoying, but you resubmit. IID going dark with no ETA is different. IID is the backbone of how brokers file B3s under CARM. When it’s down, you’re not releasing goods. Period.
What IID Actually Controls
IID replaced the legacy ACROSS Release system for all B3 filings after CARM’s October 2024 full cutover. Every commercial import declaration—whether you’re doing PARS pre-arrival release, RMD day-of release, or release prior to payment under bond—flows through IID now. The DIF component handles your 9000-series supporting docs: commercial invoices, CBSA Form 1s, CI1s for SIMA, CUSMAs, and anything else the officer at your service area flagged for review.
When IID stops processing, you can’t:
- File new B3 declarations
- Transmit document images for goods under exam or RFI
- Receive release confirmations or payment instructions
- Get finalization status on adjustments or re-determinations
Your freight doesn’t move. Your client’s production line waiting on that just-in-time shipment from Michigan stops. The perishable load sitting at the Pearson cargo facility starts aging out.
The Real Operational Mess
Here’s what breaks in practice. Say you’ve got a PARS load crossing the Ambassador Bridge Thursday night, expecting release confirmation by Friday morning. Your truck’s already dispatched. But IID went down Thursday afternoon and CBSA still can’t say when it’s back. That driver’s either sitting in the carrier’s yard burning detention time, or the warehouse is refusing to unload without a release number. Either way, you’re eating costs and your importer is on the phone.
Worse: if you’ve got goods that arrived pre-outage but were selected for exam or doc review, and you were waiting to transmit supporting documents via DIF, you’re stuck. The exam hold doesn’t clear without the docs. The docs don’t upload without DIF. The clock on your importer’s delivery commitment keeps running.
SIMA goods are especially ugly here. If you’re importing subject goods—say, certain steel or aluminum products—and you need to prove CUSMA or CPTPP origin to avoid the dumping duty, you’re transmitting a Certificate of Origin and possibly a detailed manufacturer’s declaration through DIF. No DIF, no proof, no release. CBSA won’t just wave it through. You’re waiting until the system comes back.
What You Can’t Do (And Shouldn’t Try)
You can’t file paper B3s as a workaround. CBSA killed that option when CARM went live for non-EDI filers. The old fallback of faxing a Form A to your local office and getting a manual release code? Gone. There’s no emergency paper process anymore. IID is the single point of failure by design.
Some brokers will tell their clients to just wait it out and hope for a same-day fix. That’s fine if your goods aren’t time-sensitive and you’re not burning demurrage at the port. But if you’ve got a reefer container of Chilean blueberries sitting at the Montreal Racine Terminal, waiting isn’t a strategy. You need to be on the phone with your freight team coordinating storage or rerouting before costs spiral.
Don’t try to get cute with filing a second B3 once the system’s back up, either. Duplicate transmissions under the same cargo control number will reject or worse, create split accounting entries that’ll haunt your CARM reconciliation for months. One declaration per CCN. File it once, file it right.
Triage Protocol When IID Is Down
First: confirm the outage scope. Check the CBSA TCC page directly, not just the CSCB digest. Sometimes regional systems are up even when national IID processing is lagging. If your primary service area is Toronto but the goods are actually sitting in Mississauga, you might have options with a different BSO.
Second: prioritize your release queue. Anything under exam or RFI goes to the bottom—it wasn’t releasing today anyway. Focus on PARS pre-arrival shipments that should have auto-released but didn’t get final confirmation. Those are your time-bombs. Contact the carrier and get confirmation the conveyance and cargo CCNs were transmitted via ACI at least 24 hours before arrival. If ACI is clean and IID is the only blocker, at least you know the delay isn’t your fault.
Third: communicate with your importers early. Don’t wait until 5pm to tell them the shipment that was supposed to deliver Friday morning is stuck. Give them the TCC reference number and the timestamp. Most supply chain leads would rather know at 3:30pm that there’s a system-wide outage than get a vague “delay” message at close of business.
Fourth: document everything. If you’re incurring demurrage, detention, or storage costs because of a CBSA system failure, you want timestamps, screenshots of the TCC notice, and a paper trail showing you attempted to file as soon as the system was available. Most carriers won’t waive fees just because CBSA’s infrastructure failed, but your importer might have recourse if the delay directly caused a contractual penalty. That’s a compliance documentation question, not a brokerage one, but the trail starts with you.
When the System Comes Back
Once IID is processing again, expect a tsunami of filings from every broker in the country who was sitting on releases. CBSA’s infrastructure isn’t great at handling spike load. If the outage lasted more than a few hours, plan for slower-than-normal processing even after the “resolved” notice goes out. Don’t promise your importer a 10am release if you’re filing at 9am the morning after a multi-hour outage. Build in buffer.
And double-check your CARM Client Portal account before you start filing. Sometimes outages coincide with unannounced changes to security token expiry or session timeout settings. Last thing you need is to finally have IID back online and discover your portal login is broken.
The Bigger CARM Reliability Question
This isn’t the first IID outage and it won’t be the last. CARM’s infrastructure has had rough patches since go-live. The October 2024 cutover was messy. The February 2025 payment processing issues were worse. Every time CBSA posts a TCC notice with “no estimated time of resolution,” it’s a reminder that the entire Canadian import clearance system now runs on a single platform with no manual bypass.
That’s fine when it works. It’s a serious operational risk when it doesn’t. If your supply chain can’t tolerate same-day release uncertainty, you need to be building buffer into your cross-border logistics. Extra dray day, earlier pickup windows, safety stock on the Canadian side of the border. It’s not elegant, but it’s reality under CARM.
If you’re running a lean JIT operation and need help stress-testing your cross-border timing assumptions against CARM’s actual performance, we’ve done that work for a lot of clients in the last six months. Get in touch and we’ll walk through it.
Source: CSCB