The Delay Profile
CBSA posted update 44 on May 5, 2026: inbound EDI and eManifest portal messages are processed without delay, but outbound messages (acknowledgements, rejects, release notifications, PARS cargo release codes) are running five to seven hours behind. The delay window opened April 25 at 08:00 ET and persists as of mid-day May 5.
Inbound flow is clean. Your ACI cargo reports, PARS pre-arrival data, and CAD filings reach CBSA systems on schedule. The bottleneck sits on the return path: the agency is consuming your data but cannot send confirmation, release authority, or error messages back to brokers, carriers, and warehouse operators at normal speed.
For most import managers, this reads like background noise. For anyone running just-in-time cross-dock windows, tight drayage slots, or late-Friday accounting closes, five hours is the difference between a same-day release and an overnight hold.
PARS Release Windows Slide Right
PARS (Pre-Arrival Review System) depends on a clean round-trip: broker transmits pre-arrival data, CBSA replies with a cargo release code or an exam flag, carrier presents at the border, and the truck rolls. Normal turnaround for a clean PARS file is minutes. A five-hour outbound delay pushes that release notification well past the carrier's scheduled appointment, the warehouse receiving window, or the last viable drayage slot of the day.
If your broker files PARS at 10:00 and the truck is scheduled to cross at 13:00, you're now waiting until 15:00 or later for the release code. The truck either sits at the port of entry or the driver cancels and reschedules. Drayage detention starts accruing. The warehouse slot goes to the next inbound unit. Your container sits another day.
For Port of Montreal import volumes routed through our Montreal sufferance facility, this kind of release lag collapses same-day cross-dock plans. A container that clears by 11:00 normally makes the 14:00 outbound cutoff. A container waiting until 16:00 for CBSA acknowledgement sits overnight and ships the next business day.
CAD Accounting and K84 Monthly Statement Reconciliation
Commercial Accounting Declarations (CADs) filed under CARM require acknowledgement from CBSA before the transaction is logged in the importer's RPP bond and monthly statement. A five-hour outbound delay means your CAD submission at 14:00 doesn't generate an acknowledgement until 19:00 or later, well after business hours for most accounting teams.
If you file CADs on Friday afternoon expecting same-day confirmation for month-end close, the acknowledgement arrives Monday morning. Your RPP bond utilization and K84 statement reconciliation now span two statement periods. The accounting is still correct, but the timing mismatch creates manual work: someone has to track which CADs landed in which statement cycle and reconcile the lag.
For importers managing tight RPP bond headroom, a five-hour acknowledgement delay can push a Friday filing into a Monday settlement date, meaning three additional business days of bond utilization. If your bond is already at 85% utilization mid-month, that timing slip can trigger a temporary over-limit state and a call from your brokerage team to either post additional security or defer shipments.
Reject Messages Arrive Too Late to Correct Same-Day
The other consequence: reject messages. If your CAD filing contains an error (wrong HS classification, missing CUSMA certificate reference, incorrect exporter BN), CBSA normally replies within minutes. You correct the filing, retransmit, and clear the shipment the same day.
A five-hour reject delay means you discover the error at 17:00 instead of 12:00. Your broker can fix and refile, but the corrected CAD acknowledgement now arrives after 22:00. The carrier has left. The warehouse has closed. The shipment holds until the next business day. For perishable goods, temperature-controlled LCL consolidations, or expedited fulfillment inventory, that one-day slip is a cost event.
What the CBSA Systems Status page Doesn't Tell You
CBSA's public service notices describe the delay in system terms: "outbound messages delayed by approximately 5 to 7 hours." The notice does not quantify the operational fallout: how many PARS releases missed their carrier window, how many CADs failed to confirm before month-end close, how many exam requests sat unacknowledged past the warehouse's last receiving hour.
From a broker's perspective, the issue is not the delay itself but the lack of a workaround. You cannot call the port of entry and ask for manual release authority. You cannot phone the CBSA systems team and request priority acknowledgement for a time-sensitive CAD. The queue is the queue. Your filing sits in the outbound buffer until the backlog clears.
The only mitigation is to file earlier. If you normally transmit PARS data two hours before crossing, add five hours. If your CAD accounting cutoff is Friday at 16:00, move it to Friday at 11:00. The delay is predictable, so the fix is procedural: shift every deadline left by the length of the lag.
Inbound Data Flow Is Not the Problem
One clarification: inbound EDI and eManifest messages are processed without delay. Your ACI cargo reports, PARS submissions, and CAD filings reach CBSA systems on time. The delay affects only the return messages—acknowledgements, release codes, exam flags, reject notices.
This matters because it means you should continue filing on schedule. Do not hold shipments waiting for CBSA systems to recover. The data is being received. The problem is the confirmation loop. If you delay your filing hoping for faster turnaround later, you simply push the entire release cycle further right.
When the Delay Ends, Expect a Flood of Outbound Messages
When CBSA clears the backlog, brokers and carriers will receive days' worth of acknowledgements, rejects, and release codes in a compressed window. If you filed fifty CADs over a three-day period, all fifty acknowledgements may arrive within an hour. Your accounting reconciliation, RPP bond utilization report, and CARM Client Portal transaction log will all update simultaneously.
Plan for that reconciliation surge. Make sure your compliance team has a clear audit trail linking each CAD to its acknowledgement timestamp, so you can explain the timing gap to your internal finance group or external auditors. CARM monthly statements (K84) will reflect the acknowledgement date, not the filing date, so expect some line-item timing mismatches in your May statement if this delay persists into month-end.
Filing Strategy While the Delay Persists
File PARS data and CADs earlier than normal. If your standard lead time is two hours before arrival, make it seven. If your accounting close is end-of-day Friday, move the cutoff to mid-morning. The delay is predictable, so treat it as a known variable in your release planning.
Don't resubmit filings hoping to jump the queue. The backlog is systemic. A second submission just adds another record to the buffer. Wait for the acknowledgement or rejection, even if it takes until the next business day.
If you operate cross-dock or just-in-time fulfillment programs that cannot absorb a five-hour release lag, talk to your carrier and warehouse operator about holding containers at the port of entry or the terminal yard until CBSA release confirmation is in hand. Drayage detention at the port may be cheaper than a missed warehouse slot and an overnight hold at commercial rates. Our Montreal operation has seen this calculus shift twice this week already.
If you're filing CADs for month-end accounting close and the acknowledgement delay pushes transactions into the next statement period, document the filing timestamp and the acknowledgement timestamp in your internal records. CBSA's K84 statement will reflect the acknowledgement date, so your reconciliation process needs to account for the gap.
This isn't the first time CBSA outbound message queues have run long, and it won't be the last. The difference this time is the delay window: five to seven hours is long enough to break same-day release assumptions but short enough that most importers won't notice unless they're running tight windows. If your operation depends on same-day PARS turnaround or Friday CAD confirmations, this is the kind of systems event that quietly doubles your dwell time. We track these lag windows daily. Get in touch if you want eyes on your current filing and release schedule.
Originally published at https://www.canflow-global.com/en/insights/cbsa-edi-and-emanifest-outbound-message-delays-what-five-to-seven-hour-lag-means/.
