TCC26-0084 and the Real Cost of ACK Delays

When the ACK doesn’t come back

TCC26-0084 dropped on April 20 at 09:30 ET with the usual CBSA phrasing: “receiving and processing… however, there is a delay.” Translation: they’re accepting your EDI transmissions and eManifest portal data, but the outbound acknowledgements, rejects, RNS notices, and completeness messages are sitting in a queue somewhere. The inbound pipe works. The outbound pipe is clogged.

Most brokers will shrug and say this is just another CBSA systems hiccup. It’s not. This one has teeth.

The operational trap

When you file a PARS or RMD and don’t get the standard ACK within seconds, you’re stuck in limbo. Did CBSA receive the file? Did it validate? Is the transaction number live? You don’t know. Your software doesn’t know. Your driver sure as hell doesn’t know.

The instinct is to re-transmit. Don’t. If the first file made it through and CBSA just hasn’t sent the acknowledgement yet, you’ve now created a duplicate transaction. That means two B3s or two cargo control documents on the same shipment. One of them will need to be voided or amended later, and if the driver shows up at primary with a CCN that’s been superseded, you’re looking at a referral to secondary and a very unhappy phone call.

The safer play is to wait — but waiting costs time, and time costs money. If your carrier is sitting at the warehouse waiting for an RNS to confirm release on a Friday afternoon, that’s detention. If your client’s production line is waiting on a just-in-time shipment and you can’t confirm the goods cleared, that’s a much bigger conversation.

eManifest and the ACI window

For highway shipments, the ACI eManifest rules give you a one-hour advance filing window before arrival. In practice, most brokers file closer to two hours out to leave room for corrections. But when the acknowledgements aren’t flowing, you can’t tell if your A8A got accepted or if there’s a data error that needs fixing.

If the cargo control document wasn’t received clean and you arrive without a valid CCN, the carrier eats a $1,000 ACI penalty under section 12.1 of the Administrative Monetary Penalty System. The driver gets turned around. The shipment goes back to the warehouse or sits in a holding yard until the paperwork is straightened out.

This is where having a customs broker who monitors the CBSA trade notices in real time matters. If we know TCC26-0084 is active and ACKs are delayed, we’re not re-filing blindly. We’re calling the CBSA Regional Processing Centre directly, confirming receipt by transaction number, and advising the carrier to proceed with caution. That’s not heroic — that’s just reading the room.

CARM makes this worse

Pre-CARM, most of us were working in ACROSS or legacy EDI systems where the feedback loop was faster and the error handling was more forgiving. CARM Client Portal’s promise was real-time visibility into your account, your releases, your payment status. In practice, when the EDI acknowledgements don’t come back, the portal doesn’t update either. Your dashboard shows “Pending” and you’re back to phoning the 1-800 line or your local CBSA officer.

If you’re using release prior to payment under CARM and the completeness notice doesn’t arrive, you can’t confirm whether your commercial accounting declaration was accepted. That means you don’t know if your GST and duty are being calculated correctly, and you don’t know when the payment deadline is ticking. Miss the payment window by even a day and CBSA can suspend your RPP privilege. We’ve seen it happen. The bond stays in place, but your release authority gets yanked, and every shipment goes to exam until you’re reinstated.

If your RPP bond is sized tight or your client’s import volumes spiked this quarter, this kind of systems delay can cascade into a compliance issue fast. Our compliance team has walked more than a few importers back from the edge on this exact scenario.

What to do right now

If you’re filing today and TCC26-0084 is still active, here’s the checklist:

• Transmit once. Don’t double-file unless you get a hard reject or a “not received” confirmation from CBSA.
• Log your transaction numbers manually. If your software isn’t getting ACKs, you need a fallback audit trail.
• Call the RPC or your local CBSA office with the CCN or transaction number in hand. Confirm receipt verbally if the EDI loop is broken.
• If you’re using a freight forwarder for drayage or warehouse services — especially in Montreal where port volumes are high — make sure they know there may be delays in release confirmation. FENGYE’s Montreal sufferance warehouse has been flagging this to clients proactively, but not every facility will.
• If you’re clearing goods under SIMA, anti-dumping, or any provisional duty scenario where the release type is conditional, do not assume silence means approval. Wait for the explicit RNS or contact CBSA’s Trade Programs Division.

This isn’t a “wait and see” situation. This is a “log everything and have a backup plan” situation.

When CBSA says “initial investigation underway”

That phrase in the TCC notice means they don’t know the root cause yet. Could be a server issue. Could be a queue overload from CARM transaction volume. Could be something in the EDI gateway that broke after a patch. We won’t know until they issue a follow-up TCC or a post-mortem memo.

What we do know is that EDI and eManifest delays have real dollar consequences. If your broker isn’t monitoring these notices and adjusting workflow in real time, you’re flying blind. If your internal trade compliance team is managing releases in-house, make sure someone is checking the CBSA systems status page and the CSCB digest daily.

Most CBSA processing delays are noise. This one isn’t. When the acknowledgement loop breaks, everything downstream breaks with it.

If you’re dealing with delayed ACKs on active shipments or you want to pressure-test your release workflows before the next systems outage, we’re around. This is the kind of call we take every day.

Source: CSCB