The outage timeline
CBSA's EDI and eManifest portal went down the morning of April 25. For the first 72 hours, no electronic cargo or accounting data moved. ACI transmissions sat in queue. CAD filings bounced or disappeared. Release messages didn't come back. Carriers couldn't close trips. Brokers couldn't get payment codes.
As of May 6 (update eleven), inbound transmissions are accepted again. The system is receiving ACI, PARS requests, and CAD filings. But outbound messages are still delayed. That means you can file a CAD, but the CBSA may not return your K32 payment message, your RMD approval, or your trip-closure acknowledgment on the usual timeline. The Systems Outage Contingency Plan remains in effect, which means paper entries are still a legal fallback and sufferance warehouses are still accepting them.
If you haven't filed on paper since 2018, you're not alone. Most mid-market importers moved to full EDI years ago. But the SOCP never went away, and right now it's the only hedge when a CAD sits in limbo for six hours and your trucker is parked at the gate.
What "residual delays on outbound messages" actually means
The phrase sounds mild. It isn't.
When you file a CAD for release prior to payment under PARS or RMD, you need the outbound message to tell the warehouse the shipment is clear. If that message is delayed by three hours, the freight sits. If it's delayed past your trucker's detention window, you pay. If it's delayed overnight, your Monday morning production line waits until Tuesday.
The same applies to payment messages under CARM. You file the CAD, CBSA assesses duty, and the system should return a K32 code so you can authorize the draw against your RPP bond or make a direct payment in the CARM Client Portal. If that code doesn't come back, you can't finalize the transaction, and the shipment stays in bond.
Carriers have their own version of this problem. Trip closure depends on an outbound acknowledgment from CBSA. If that acknowledgment is delayed, the trip stays open in the system, the cargo control document can't be archived, and the next inbound load from the same truck may trigger a compliance flag. It's housekeeping pain, but it compounds fast when a carrier is running twenty trips a day into Montreal or the Pacific Highway.
Why paper entries are still on the table
The SOCP allows brokers to file paper B3 forms (or their CARM-era equivalent, the paper CAD) when EDI is unreliable. Most brokers stopped keeping blank stock years ago. We keep a supply because outages happen, even if this one is the longest in recent memory.
Paper entries are slower and they require a trip to the CBSA office or the warehouse. But when a shipment can't wait, they work. The officer stamps it, release happens, and the trucker leaves. You backfill the electronic record later when the portal is stable.
The catch is that paper entries bypass the real-time duty calculation in CARM. You're estimating duty at the time of filing, which means you may underpay or overpay, and the correction comes later on your K84 statement. For routine shipments that's fine. For shipments with complex HS classifications, SIMA provisional duties, or tight origin rulings under CUSMA, it's risky. You don't want to guess at a Section 20.1 determination or a dumping margin when the penalty for getting it wrong is an AMPS notice three months later.
If you're running perishable freight or time-sensitive ecommerce inventory through Montreal, paper entries are worth the hassle. If you're clearing industrial equipment with a three-week dwell tolerance, you can probably wait for the portal to catch up. The calculus depends on detention cost and line-down risk. Our Montreal partner has handled both scenarios in the last ten days, and the decision tree is shorter than you'd think: if waiting costs more than the paperwork hassle, file paper.
What this means for CAD filing through next week
The portal is accepting new transmissions, but the backlog is real. Messages that got stuck between April 25 and April 28 are still being processed. If your broker filed a CAD on April 26 and you're still waiting for a payment code on May 6, that's not unusual. CBSA is working through the queue, but there's no published estimate for when the backlog clears.
For new filings this week, expect longer turnaround on outbound messages. If you normally see RMD approval in thirty minutes, budget two hours. If you're filing late Friday for a Monday pickup, file Thursday instead. If your shipment has OGD holds (CFIA, Health Canada, ECCC), add another layer of buffer because those agencies coordinate through the same messaging infrastructure.
One practical change: if your brokerage team hasn't been copying you on CAD transmission receipts, ask them to start. When the portal is flaky, you want proof that the filing left your broker's system, even if CBSA's acknowledgment is delayed. That timestamp matters if you're disputing demurrage or arguing about a missed cutoff.
CARM and the fragility problem
This outage is not a CARM design flaw. The EDI and eManifest infrastructure predates CARM by a decade. But CARM has made the consequences of an outage more expensive.
Under the old B3 system, brokers could make manual duty payments at the border or phone in a release request. CARM centralized everything in the Client Portal and tied it to real-time EDI messaging. That's more efficient when it works. When it doesn't, there's no back door. You file the CAD, you wait for the outbound message, or you fall back to paper.
The RPP bond adds another wrinkle. Your bond is sized to cover fifteen days of duty liability. If CADs are delayed and payment codes don't post to your account on schedule, your rolling liability calculation in the CARM Portal may show higher exposure than you actually have, and you may hit your bond ceiling early. That doesn't stop release, but it does trigger a margin call if CBSA decides your security is insufficient. We've seen importers get flagged for bond top-ups during processing delays, not because their trade volume changed but because the system couldn't reconcile payments in real time.
If your bond was already tight before April 25, check your K84 statement this week. You may need to adjust your security or move some payments forward to keep the headroom clear. That's the kind of detail our duty and drawback team tracks daily, and it's worth a call if the numbers look wrong.
Where we are now
The system is stable enough to accept new data. Outbound messages are delayed but not stopped. The SOCP is still open, which means paper is still legal. The backlog is real, and it will take days to clear.
If you've got freight arriving this week and your broker is telling you to expect slower turnaround, they're right. If they're suggesting a paper filing for time-sensitive cargo, that's a reasonable call. If your CAD sat in queue for four days last week and you want to know whether to file a service complaint or just move on, the answer is move on. CBSA isn't processing those complaints until the backlog clears, and by then your shipment will be delivered.
If your last inbound release took longer than usual and you want to walk through what happened, or if you want a second set of eyes on your CARM payment reconciliation after two weeks of delays, get in touch. We've been filing through this since day one, and we know which delays matter and which ones don't.
Originally published at https://www.canflow-global.com/en/insights/portal-messages-still-backing-up-after-cbsa-edi-outage/.
