CBSA Processing Delays: When a Three-Hour EDI Lag Actually Matters
A 90-minute CBSA EDI processing delay resolved this morning, but most importers don't know when these notices matter and when they're just noise.
The piece resolved quickly—90 minutes total—but the TCC notice that went out this morning is worth unpacking, because most importers don’t know which CBSA processing delays they can ignore and which ones they can’t.
This one was EDI and eManifest portal messages running 1 to 3 hours behind on acknowledgements, reject messages, and notices. RNS (Release Notification System), completeness notices, the whole outbound stack. Resolved by 10:55 AM ET, back to normal.
What Was Actually Delayed
When your broker transmits a CAD (the Commercial Accounting Declaration that replaced the B3 under CARM Release 3), CBSA’s system sends back acknowledgements and sometimes reject messages. Same thing happens with cargo control documents through eManifest—the ACI, the conveyance reports, the trip sheets all generate responses.
A three-hour delay means your broker files at 9 AM and doesn’t get the acknowledgement until noon. In most cases, that’s just noise. The goods released hours ago under PARS or RMD, the truck is already at the warehouse, and the acknowledgement is just paperwork catching up.
But not always.
Where the Lag Bites
Release prior to payment works because CBSA’s system confirms that the CAD was filed, the RPP bond is valid, and the accounting has started. If the acknowledgement is delayed, the system doesn’t advance, and goods that should release at the border sit.
We don’t see this often—CBSA processing is usually fast—but when volumes spike and the queue backs up, the stuff that should be automatic stops being automatic. A broker files, expects the RNS within minutes, and instead waits. The truck driver is at the border. The warehouse has a dock door scheduled. The delay eats the margin.
The other place it matters is reject messages. If your broker files a CAD with a bad HS code, a missing certificate of origin, or an incorrect NRI declaration, CBSA kicks it back. Normally that happens fast enough to fix and refile the same day. If the reject message is delayed three hours, you’ve lost half a business day, and anything that was supposed to clear Friday now clears Monday.
CARM Made This Worse (Sort Of)
Under the old B3 system, brokers transmitted and CBSA acknowledged, but the consequences of a delay were smaller because release and accounting were more decoupled. You could get release with minimal data and clean up the B3 later.
CARM Release 3 tightened that. The CAD is both the release document and the accounting document, filed together, and the system won’t advance until it’s satisfied. That’s good for compliance—fewer shortcuts, cleaner data—but it also means delays upstream show up downstream faster.
The RPP bond math is tighter now, too. CBSA posts duties and taxes to your Statement of Account monthly, and if your bond isn’t sized right, you lose release privileges. A broker who can’t get acknowledgements back can’t confirm that the CAD posted correctly, which makes it harder to track the running bond balance. Most of the time that’s fine, but if you’re close to your bond limit and filing high-duty shipments, you want confirmation fast.
What Importers Should Actually Do
When CBSA posts a processing delay notice, the first question is: do you have goods in transit that are supposed to clear today? If yes, check with your broker. If the delay affects acknowledgements and your shipment is time-sensitive (perishable, dock door scheduled, retail replenishment with a hard deadline), you want to know if the CAD went through or if it’s sitting in the queue.
If no goods in transit, the delay is just a log entry. CBSA’s EDI system runs high volumes all the time, and a 90-minute spike is not a signal of anything structural.
The second question is: does your broker have a way to check filing status without waiting for the acknowledgement? Some do, some don’t. CARM Client Portal access helps, but not every importer is set up for it, and not every broker proactively monitors the queue.
Third: if you’re using release prior to payment as your standard workflow, make sure your broker knows your dock schedules and can escalate when things stall. A three-hour delay at 9 AM is nothing. A three-hour delay at 2 PM on a Friday with a Montreal sufferance warehouse cutoff at 4 PM is a weekend hold.
The Pattern
CBSA runs these delay notices a few times a year. Sometimes it’s system maintenance. Sometimes it’s volume spikes (end of month, post-holiday catch-up, SIMA deadline rush). Sometimes it’s unexplained.
The ones that matter are the ones that hit during peak filing windows—morning rush, end-of-week, month-end—and affect time-sensitive cargo. The ones that don’t matter are the ones that resolve in under two hours and happen outside critical windows.
This one was 90 minutes, resolved by late morning. Minimal real impact. But if you didn’t know what the notice meant, you’d just see “delays” and assume it was a problem.
It’s worth knowing the difference.
Most of these notices are noise. When one isn’t, you want to know within the hour, not Monday morning. We track these all day. Get in touch.
Source: CSCB