CBSA EDI and eManifest Outbound Delay: What a Two-to-Four-Hour Lag Actually Costs

The Current State

CBSA has been running a two-to-four-hour delay on outbound EDI and eManifest portal messages since April 25. Inbound transmissions—your cargo reports, PARS filings, CAD submissions—are processing without delay. The lag sits entirely on the outbound side: acknowledgements, reject messages, release confirmations, and the status codes your warehouse and drayage carriers are waiting on.

Update 43 came through on May 5. The delay has been consistent enough that CBSA is numbering the updates. That tells you two things: this isn’t a brief overnight maintenance window, and the agency expects the problem to persist long enough that importers and brokers need operational workarounds.

Where the Delay Hits

If you file a PARS pre-arrival declaration at 08:00 and the driver arrives at the border at 10:00, you’re normally watching for the RNS (Release Notification System) confirmation within minutes. A two-to-four-hour outbound delay means that confirmation might not land until noon or later. The truck is already at primary inspection. The driver has no release code. CBSA officers at the booth see the filing in their system, but your broker and your carrier are flying blind until the outbound message finally arrives.

For commercial highway shipments, that delay usually resolves itself by the time the truck clears primary and moves to the commercial lane. The officer can see the release status on their end. But for rail intermodal, marine containers arriving at the port, and air cargo sitting in a cargo warehouse, the lack of an outbound confirmation creates a coordination gap. Your 3PL doesn’t know whether to dispatch a chassis. Your Montreal sufferance warehouse doesn’t know whether to stage the container for cross-dock or hold it for exam. The shipment sits in limbo while everyone waits for a message that should have arrived two hours ago.

PARS and RMD Workflows

PARS (Pre-Arrival Review System) depends on tight timing. You file the declaration before the truck or container arrives. CBSA reviews it, runs the risk score, and sends back a release or an exam hold. The entire point is that the goods are cleared before they hit the border or the inland sufferance facility.

When outbound messages lag by two to four hours, that pre-arrival clearance becomes functionally post-arrival. A container discharged at the Port of Montreal at 06:00 and filed under PARS at 05:30 should have release confirmation by the time it’s available for pickup at 08:00. A four-hour delay means the release notice doesn’t land until 09:30 or later. Your drayage carrier has already missed the morning dispatch window. The container sits another day, and you’re paying demurrage and per-diem because the confirmation was late.

RMD (Release on Minimum Documentation) has the same problem but worse. RMD relies on a streamlined data set—no full CAD at time of release, just enough information for CBSA to make a release decision. The CAD gets filed within five business days. If the outbound RMD release confirmation is delayed by four hours, you lose the benefit of the program. The shipment was supposed to release immediately. Instead, it sits at the warehouse waiting for a message that’s stuck in the outbound queue.

CAD Rejects and ACI NAKs

A two-to-four-hour delay on reject messages is worse than a delay on release confirmations. If you file a CAD (Commercial Accounting Declaration) in the morning and there’s a data error—wrong HS classification, missing CUSMA certificate number, mismatched invoice currency—CBSA’s system catches it immediately. But the reject message doesn’t reach you for another two to four hours. By the time you see the error, correct it, and refile, you’ve burned half a business day.

The same timing problem hits ACI (Advance Commercial Information) filings and cargo control. If your eManifest submission gets a NAK (negative acknowledgement) because the carrier code or conveyance reference number is malformed, you need that NAK immediately so you can correct and retransmit before the shipment arrives. A four-hour delay means the truck or container is already at the border or the rail yard, and CBSA has no advance cargo data on file. The shipment gets held for missing ACI, even though you filed it hours ago—the outbound error message just didn’t arrive in time for you to fix it.

What You Can Do

Call your broker before you assume a filing went through clean. If you’re used to seeing an ACK or release confirmation within ten minutes and it hasn’t landed after thirty, pick up the phone. Most brokers have access to CBSA’s internal portals and can see the filing status even if the outbound message hasn’t been sent. That call saves you two hours of waiting for a message that’s stuck in the queue.

Build buffer into your cross-dock and just-in-time schedules. If your current SOP assumes a PARS filing at 06:00 and a release confirmation by 06:15, add three hours to that assumption until CBSA closes this incident. A same-day cross-dock schedule that depends on morning release confirmations is not reliable right now.

For high-value or time-sensitive shipments, consider filing earlier. If you normally file PARS two hours before arrival, file it four hours before arrival. That gives the outbound message delay room to resolve before the shipment is physically available for pickup. It’s not a perfect fix—you’re still waiting on CBSA’s outbound queue—but it keeps the delay from colliding with your dispatch window.

If you’re managing NRI (Non-Resident Importer) programs or coordinating brokerage filings across multiple carriers, the lack of real-time acknowledgements makes it harder to track which shipments have cleared and which are still in process. Centralize your status checks. Have one person or one team responsible for calling brokers and checking CBSA portals, rather than waiting for outbound messages that may not arrive until the afternoon.

How Long This Lasts

CBSA has published forty-three updates since April 25. The agency is not calling this resolved. The delay has been stable at two to four hours, which suggests the underlying issue is systemic—probably related to message queue capacity or database replication lag—not a transient network problem.

If you’re planning Q2 shipments that depend on tight release timing, assume this delay persists through the end of May. Build that assumption into your drayage contracts, your warehouse scheduling, and your customer delivery commitments. A two-to-four-hour delay doesn’t sound like much until it’s the reason your shipment misses the cross-dock cutoff and sits an extra day at the sufferance warehouse.

We’re filing CADs and PARS declarations through this delay every day. If your current broker isn’t calling you when a message is late, or if you’re waiting on outbound confirmations that should have arrived hours ago, that’s a workflow problem we can fix. Get in touch.

Source: CSCB