The Rule CBSA Just Reinforced
CBSA Bulletin 5422 shut down two practices that were common enough to warrant a public reminder: re-using mass adjustment case numbers across subsequent CAD versions, and stacking multiple mass adjustment case numbers on different lines within a single version.
Both are now explicitly forbidden. When you submit a new adjustment — whether it's a single-line correction or another mass batch — any previous case number sitting in the "CBSA Case No." field must be cleared. And each CAD version gets exactly one mass adjustment case number, period.
This sounds procedural until you realize how many post-release adjustment workflows were casually violating it.
Why This Matters More Than It Looks
Mass adjustments exist because importers routinely discover classification errors, missing CUSMA claims, or incorrect tariff treatment weeks after release. A sufferance warehouse unloads a container and finds six SKUs that don't match the commercial invoice. An accounting review catches a batch of entries where the broker applied general tariff rates instead of claiming CETA preference. A CBSA verification letter arrives three months later disputing the declared value on forty shipments.
In all of these scenarios, the importer needs to file corrected CADs. A mass adjustment case number is supposed to group related corrections so CBSA can process them as a single review instead of handling each CAD individually.
The problem: brokers and importers were treating these case numbers like folder labels. Submit a mass adjustment, get a case number, keep using that same case number on every subsequent tweak to the batch. Or worse — generate three different mass adjustment case numbers for three subsets of the same shipment and drop all three into one CAD version.
CBSA's processing system doesn't handle that. The case number is a single-use token tied to one specific submission event. Re-using it scrambles the audit trail. Stacking multiple case numbers in one version creates ambiguity about which subset of lines maps to which CBSA review.
Both patterns produce the same result: your adjustment gets rejected, and you're back to square one with a compliance file that now has extra explaining to do.
What Correct Practice Looks Like
You file a mass adjustment covering twenty CADs where the HS classification needs correction. CBSA assigns a case number. That case number lives on those twenty CAD versions, and nowhere else.
Two weeks later, you discover five more entries with the same issue. You do not append the old case number to the new batch. You submit a fresh mass adjustment request. CBSA assigns a new case number. The new batch carries the new number. The original twenty entries keep the original case number.
If you need to revise one of the original twenty CADs again — maybe CBSA came back with a question and you're filing a second correction — you clear the old case number from the "CBSA Case No." field before submitting the new version. That revision is now a separate event. It might generate its own case number if it's part of another mass adjustment, or it might go through as a standalone correction. Either way, the previous case number does not carry forward.
The system enforces a strict one-to-one mapping: one case number, one adjustment event, one CAD version. Anything else breaks the link between the case file and the actual data CBSA is reviewing.
The Warehouse Angle
Most of the classification and value discrepancies that trigger mass adjustments get discovered at the warehouse stage — during unload, inspection, or cross-reference against the packing list. A customs exam flags an issue. An importer's quality control team catches a supplier error. The sufferance warehouse operator notices that twelve pallets were declared as one HS code but the cartons are labeled with a completely different product description.
All of that happens after release, which means the CAD is already filed and the duties are already assessed. The correction has to come through as an adjustment. If the same issue shows up across multiple shipments, the importer wants to batch the fix — one mass adjustment submission instead of forty individual corrections.
That's where the case number discipline matters. CBSA needs to see a clean grouping: this batch of CADs, this issue, this correction, this case number. If the case number has been recycled from a previous unrelated adjustment, or if multiple case numbers are mixed into the same batch, the relationship between the case file and the actual corrections falls apart.
CBSA's bulletin is a reminder that the system won't tolerate that ambiguity. The adjustment either maps cleanly to one case number, or it gets rejected.
Compliance Workflows That Survive This
If your brokerage operation handles volume imports with frequent post-release corrections, the discipline to implement is straightforward:
- Track mass adjustment case numbers in your internal system the same way you track CAD transaction numbers — as unique, non-reusable identifiers tied to a specific filing event.
- When preparing a new mass adjustment batch, generate a fresh case number request. Do not pull a case number from a prior batch, even if the underlying issue is similar.
- If you're revising a CAD that already carries a mass adjustment case number, clear that number before submitting the new version. The revision is a new event.
- Audit your CAD templates and submission workflows to make sure the "CBSA Case No." field is being actively managed, not passively carried forward from previous versions.
This is basic compliance housekeeping, but it's the kind of detail that doesn't surface as a problem until CBSA starts rejecting submissions. The bulletin exists because enough importers and brokers were doing it wrong that CBSA decided a public reminder was necessary.
If your broker is re-using case numbers or stacking multiple mass adjustment IDs into one CAD, your next batch is going to bounce. Fix the workflow now, before it becomes a backlog problem.
What CBSA Actually Enforces
The CARM Client Portal enforces these rules at submission. A CAD version that carries a case number already tied to a previous submission will be flagged. A CAD version with multiple mass adjustment case numbers in the line-item fields will be rejected outright.
CBSA's processing team won't call you to fix it. The submission fails, you get a rejection notice, and you re-file with the correct case number structure. If this happens during a verification or a penalty review, the delay and the extra submission create their own compliance exposure.
The fix is procedural, not technical. Your broker or your internal compliance team needs to treat case numbers as single-use tokens, clear old numbers before filing new versions, and generate fresh case numbers for each distinct mass adjustment batch. That's it.
Most CBSA bulletins are clarifications of existing rules. This one is enforcement of a rule that was already written but widely ignored. If your adjustment workflow doesn't match what's described above, you're about to find out the hard way that CBSA's system won't accept it anymore. Clean it up now — the next batch you file will either follow the one-case-number rule, or it won't clear processing.
Originally published at https://www.canflow-global.com/en/insights/one-mass-adjustment-case-number-per-cad-version-cbsa-means-it/.
