CanFlow Global
← All insights
carmlate-accounting-penaltiescbsacad-filingamps

CARM Late Accounting Penalties Issued in Error — May 19, 2026 System Glitch

CBSA cancelled all late accounting penalties issued May 19, 2026, after a system error on the Victoria Day stat holiday. More erroneous LAPs may appear through May 26 but will show zero dollars. What this means for your CAD cycle and appeal queue.

What Happened

CBSA posted a notice on the CARM Client Portal homepage confirming that late accounting penalties (LAPs) issued on May 19, 2026, were generated in error. The agency is cancelling all of them and asked brokers and importers to hold off on appeals. The glitch coincided with the Victoria Day stat holiday, and CBSA warns that additional erroneous LAPs may appear between May 20 and May 26, though those will carry a zero-dollar amount.

If you saw a penalty notice hit your CARM dashboard on the 19th, ignore it. If your importer already fired off an appeal or called in a panic, pull it back. CBSA is unwinding the batch on their end.

Why This Matters for Your CAD Cycle

Late accounting penalties under CARM are tied to the 40-day release-to-accounting window. If you release goods on day zero, the CAD is due by day 40. Miss that deadline and the system auto-generates a penalty — no human discretion, no grace period. The penalty amount scales with the duty liability on the entry, and repeat offences pull higher multipliers under the AMPS Master Penalty Document.

Most brokers run tight accounting cycles to avoid LAPs entirely. We batch CADs weekly, run pre-validation checks in the portal, and file before day 35 to leave margin for rejection or correction. A stat-holiday system error that spits out penalties on properly filed entries is noise, but it still burns time. Every penalty notice triggers an email, a dashboard flag, and usually a phone call from the importer asking what went wrong. When the answer is “nothing went wrong, CBSA’s system had a bad Monday,” that’s frustrating but manageable. When the penalty is real and you missed it, that’s a compliance fire.

The May 19 batch was the former. If you’re seeing zero-dollar penalties between now and May 26, same story. CBSA is aware, and the penalties will be cancelled. Don’t waste time drafting appeal letters or pulling entry records to reconstruct the timeline. Wait for the cancellation notice in the portal.

The Zero-Dollar Penalty Signal

CBSA’s note that erroneous LAPs issued through May 26 will show zero dollars is a useful detail. A zero-dollar penalty is a system record with no financial impact, but it still appears in your LAP history and can confuse audit trails if you’re not tracking closely. If you run monthly reconciliation between your brokerage software and the CARM portal, flag these entries now so they don’t muddy your penalty counts or compliance scoring later.

For importers with CSA (Customs Self Assessment) approvals or pre-load review privileges, a spike in penalty notices — even cancelled ones — can raise questions during your next CBSA audit. Document the May 19–26 glitch in your compliance log and keep a copy of the CARM homepage notice. If an auditor asks why your LAP count jumped in May 2026, you’ll have the answer ready.

What to Do If You Already Appealed

CBSA asked brokers to refrain from appealing, but some importers file appeals directly through the portal without looping in their broker. If your client already submitted an appeal on a May 19 penalty, send them the CBSA notice and ask them to withdraw it. The portal allows appeal withdrawals, and pulling it now saves CBSA’s recourse team from processing a moot case and saves your client from having an unnecessary appeal on file.

If you’re managing the appeal queue for a high-volume importer, check the portal daily through May 26. Any new zero-dollar LAPs should be flagged internally as system errors, not real penalties. Don’t let them sit in the queue and trigger automatic escalation workflows.

##Stat Holiday System Loads and CARM Timing

The May 19 error coinciding with Victoria Day isn’t shocking. Stat holidays compress filing windows, and brokers often batch-file the Friday before or the Tuesday after to avoid weekend and holiday downtime. That creates a spike in CAD submissions and payment transactions hitting the CARM system simultaneously. If the penalty-generation logic runs on a schedule tied to calendar days rather than business days, a Monday stat holiday can confuse the date math and trigger penalties that shouldn’t exist.

This is the kind of edge-case bug that’s hard to catch in testing but obvious in production once a few hundred brokers get hit. CBSA’s response — cancelling the batch and posting a public notice — is the right call. The zero-dollar penalty flag for May 20–26 suggests they patched the immediate issue but are still watching for residual errors as the fix propagates through the system.

For brokers, the lesson is the same as always: build margin into your accounting deadlines. If you’re filing CADs on day 39 because you can, you’re one system glitch or one stat-holiday scheduling conflict away from a real penalty. We file by day 35, and we run a second sweep at day 30 for entries with complex origin claims or OGD holds that might need extra validation time. That buffer absorbs most of the noise — stat holidays, portal outages, payment processing delays.

CARM System Stability and Importer Confidence

CARM replaced the old Integrated Import Declaration (IID) system in 2024, and the transition was rough. Portal downtime, payment loop failures, and bond-release mismatches were common in the first six months. By mid-2025 the system had stabilized, and most brokers settled into a rhythm. A batch of erroneous penalties in May 2026 isn’t a sign that CARM is falling apart again, but it’s a reminder that the system is still learning to handle edge cases — stat holidays, fiscal-year rollovers, retroactive tariff updates.

For importers who lived through the 2024 CARM launch, this kind of hiccup feels familiar. For importers who onboarded in 2025 or 2026 and only know the stable version of the system, a penalty notice that turns out to be fake can shake confidence. That’s where broker communication matters. If your client sees a penalty, you should already know whether it’s real or noise before they call you. Check the CARM homepage daily, subscribe to the CBSA mailing list, and monitor the CSCB digest. When CBSA posts a notice like this, forward it to your client base immediately with a two-line explanation: “Penalties issued May 19 were system errors. CBSA is cancelling them. Ignore any zero-dollar penalties through May 26.”

That kind of proactive update is what separates a broker who files entries from a broker who manages compliance programs. We send those updates as soon as CBSA posts them, and we log them in our compliance desk’s internal tracker so we can reference them during quarterly reviews.

Next Steps

If you saw a LAP on May 19, ignore it. If you see a zero-dollar LAP between now and May 26, same. If you already appealed, withdraw the appeal. If your importer is asking questions, send them the CBSA notice and move on.

If you’re still seeing non-zero LAPs after May 26 or if penalties are piling up because your accounting cycle is too tight, that’s a different problem. We run CAD cycles for a dozen importers who moved over from brokers who were filing on day 38 and catching penalties every other month. Tightening the cycle to day 30–35 and adding pre-validation checks cut their penalty rate to zero. Get in touch.

Source: CSCB

Talk to a broker