When CBSA's EDI and eManifest Acknowledgements Go Dark: What the TCC26-0086 Outage Means for Your Release Flow

The Outage Nobody Called You About

TCC26-0086 dropped April 22 at 11:28 ET: CBSA was still receiving EDI and eManifest transmissions, but outbound acknowledgements, reject messages, RNS notices, and completeness flags weren’t going out. If you were waiting for a PARS release number or watching the eManifest portal for a convoy release to flip green, you were staring at a frozen screen while your driver sat at the border.

This wasn’t a full blackout. Cargo was still being processed. Officers could still query ACROSS. The problem was the feedback loop—brokers and carriers had no confirmation that CBSA actually saw the data, no reject codes to fix, no release authority to show the driver. That’s the operational nightmare: you don’t know if your CAD is sitting in a queue waiting to be worked, or if it bounced on a validation error you’ll never see until someone picks up the phone.

What Actually Broke

CBSA’s EDI infrastructure has two lanes: inbound (your transmission to them) and outbound (their response back). The inbound side kept working. Your broker’s software sent the CAD, the cargo control document hit the system, the ACI eManifest went through. But the outbound acknowledgements—the CCN confirmation, the PARS release code, the RNS (Release Notification System) ping that tells your TMS the shipment is clear—those all stalled.

For eManifest portal users, the delay was worse. Portal filers don’t have the luxury of automated polling; they’re refreshing a browser waiting for a status change. If you’re a smaller importer filing your own customs entries or a carrier managing your own ACE-to-ACI handoff, you had no visibility. The data was in, but you had no proof, and no way to know if CBSA flagged it for exam or released it outright.

The CBSA notice said “initial investigation underway” and didn’t commit to a timeline. That’s standard—they never do. But here’s the thing: this outage pattern has shown up before, and it’s almost always a middleware choke point between the legacy ACROSS system and the newer CARM Client Portal infrastructure. CARM Phase 2 brought the CAD and the payment/bonding workflow into one system, but the actual release decision and the EDI acknowledgement flow still run through ACROSS. When those two systems don’t sync cleanly, you get exactly this: data goes in, nothing comes back.

What Kept Moving

PARS and RMD (Release on Minimum Documentation) shipments that were already in the system before the outage could still clear if an officer manually authorized release. The problem was proving it. If your driver showed up at the warehouse or the Canadian Food Inspection Agency yard without a printed RNS or a PARS number to reference, they weren’t getting waved through. Some brokers called the local CBSA office directly and got verbal confirmation, then emailed a screenshot or the cargo control number to the driver. Not elegant, but it worked.

Release prior to payment didn’t stop either—if you had an RPP bond in place and the shipment met the criteria under https://www.cbsa-asfc.gc.ca/publications/dm-md/d17/d17-1-5-eng.html, CBSA still processed it. The bottleneck was confirmation, not authority. Officers could see your bond, they could see the CAD, they just couldn’t send you the receipt.

For time-sensitive commercial shipments—CFIA-inspected perishables, just-in-time manufacturing inputs, anything with a driver detention clock running—this was expensive. If your freight partner couldn’t confirm release and the driver sat for three hours, that’s demurrage, detention, or a missed backhaul. If your warehouse in Montreal or the FENGYE sufferance facility was waiting for an in-bond transfer to complete, you couldn’t move the goods until CBSA confirmed the A8A arrival and the subsequent CAD filing. No acknowledgement, no movement.

What You Should Have Done (and What to Do Next Time)

If you were caught in this outage, the playbook was simple: call your CBSA port of entry directly. The national service desk couldn’t help—this was a systems issue, not a policy question—but the local office could look up your cargo control number and confirm whether the shipment was released, held, or flagged for exam. Most brokers have a warm contact at their primary port; if you don’t, get one.

For portal filers, the workaround was uglier. You couldn’t rely on the portal to update, so you had to phone in and reference your CCN or eManifest trip number. If you were filing highway cargo under ACI eHBL, you needed the cargo control number and the conveyance reference. CBSA could see it, but you had to ask.

Going forward, the lesson here is redundancy. If your brokerage software doesn’t log inbound acknowledgements separately from release notices, you’re flying blind when the outbound feed dies. If you’re managing trade compliance internally and relying solely on the eManifest portal, you need a backup plan—either a broker on standby or a direct line to CBSA.

The other takeaway: don’t assume silence means acceptance. A missing acknowledgement isn’t the same as implicit release. If your CAD has a classification dispute (say, you’re importing subject goods under a SIMA finding and you’re claiming an exclusion), a missing reject message doesn’t mean CBSA agreed with you—it means they haven’t told you yet that they didn’t. When the outbound feed comes back online, you might get a retroactive reject, and now you’re fixing a filing that’s already past the penalty window.

Why This Matters More Under CARM

Pre-CARM, the B3 and the payment were separate. You could file, get a release, and deal with the accounting later. Under CARM, the CAD bundles filing, classification, valuation, and payment authorization into one transaction. If the acknowledgement doesn’t come back, you don’t know if CBSA accepted your statement of value, your tariff treatment claim under CUSMA or CETA, or your origin declaration. You’re in limbo until the system confirms or rejects.

That’s a bigger problem for high-volume importers who rely on automated release-to-pay workflows. If your WMS is waiting for an RNS to trigger the next step in your duty deferral or drawback process, a delayed acknowledgement breaks the chain. You can’t pull goods for delivery, you can’t invoice your customer, and you can’t reconcile your RPP bond draw until CBSA’s system tells yours that the transaction is complete.

The CARM Client Portal has a fallback dashboard where you can check payment status manually, but it’s not real-time, and it doesn’t substitute for an EDI feed your TMS can actually parse. If you’re still treating the portal as a primary tool instead of a last-resort lookup, you’re going to have a bad time every time the EDI pipeline hiccups.

The Bottom Line

Most CBSA processing delay notices are noise—wait it out, file your shipments, and everything catches up by morning. TCC26-0086 wasn’t that. This one broke the confirmation loop, and that’s operationally expensive. If you didn’t have a plan for the next outage, you do now: know your port contact, log your transmissions separately from acknowledgements, and don’t rely on the portal if you have any other option.

If you’re running a lean trade compliance team and you need someone who can pivot when the systems go sideways, get in touch. We do this all day.

Source: CSCB