Type F CADs: Why CBSA-Created Adjustments Lock You Out (And What to Do Instead)

The Rule That Trips Up Adjustment Workflows

CBSA bulletin 5420 is a reminder, not a new policy, but it catches brokers mid-workflow often enough that the agency felt the need to restate it: you cannot adjust a Type F CAD that CBSA created on your behalf to process a pre-CARM correction.

Type F CADs exist to handle adjustments. In the CARM environment, when you need to correct duty, value, classification, or origin on a previously released shipment, you file a Type F. The problem surfaces when CBSA itself generates a Type F to complete a cutover adjustment, such as converting an old B2 correction or processing a pre-CARM blanket request that straddled the May 2024 transition date. Those agency-created Type F CADs are locked. If you discover a second error or receive a further CBSA verification notice, you can’t file another Type F against the CBSA-created one.

The workaround requires you to step back to the original B3. You have two paths: convert the B3 into a “Pre-CARM As Declared CAD,” ensuring that Version 1 of that converted CAD reflects the data from the CBSA-created Type F adjustment, or submit a new Pre-CARM Blanket Request if you’re correcting more than one hundred lines. Neither option is fast. Both force you back into pre-CARM procedural formats even though the transaction now lives in the CARM Client Portal.

What This Means for Day-to-Day Correction Cycles

Most importers encounter this when a verification letter arrives after a cutover adjustment has already closed. You filed a B2 in March 2024 to correct an HS classification error on a December 2023 entry. CBSA converted that B2 into a Type F CAD during cutover. Now, in November 2024, CBSA’s verification unit issues a letter challenging the country of origin you declared on that same December 2023 shipment. You need to file a second adjustment, but the Type F the agency created is a dead end.

You go back to the original B3, convert it into an As Declared CAD, manually input the classification correction that CBSA already processed via the Type F, then layer on the new origin correction as Version 2. If the original entry was a consolidated shipment with dozens of line items, you’re re-keying data that should already be in the system. The conversion process itself is manual entry in the CARM portal, and if you miss a detail from the CBSA-created Type F when building Version 1, the audit trail breaks.

For high-volume importers who run monthly blanket adjustments to true up provisional values or allocation errors, this becomes a recurring pain point. If CBSA processed your January blanket request as a Type F during cutover, and you later discover that three shipments within that blanket need further correction due to a tariff preference claim you initially missed, you can’t file a second Type F. You file a new blanket request, which triggers another round of documentation and CBSA review, even though the underlying transactions already cleared release and payment months ago.

Why CBSA Locks Agency-Created Type F CADs

The restriction exists because CBSA-created Type F CADs are system-generated reconciliation records, not declarations filed by a trade chain partner. The agency treats them as internal accounting entries to close out pre-CARM transactions that couldn’t be completed under the old B3 framework. Allowing further adjustments on those system-generated records would create version-control problems and audit trail ambiguity, especially when the original B3 still exists in CBSA’s legacy database.

From a compliance perspective, this makes sense. From a workflow perspective, it’s a trap if you don’t catch it early. The bulletin doesn’t change the rule, but it does confirm that CBSA won’t be loosening the restriction. If you have a pipeline of pre-CARM corrections that may require follow-on adjustments, you need to build the conversion step into your process now, not when a verification notice lands.

The Hundred-Line Threshold and Blanket Request Strategy

The bulletin specifies that if you need to adjust more than one hundred lines, you must submit a new Pre-CARM Blanket Request rather than convert individual B3s into As Declared CADs. That threshold is firm. CBSA will reject a batch of individual As Declared CAD conversions if the total line count exceeds one hundred, even if you split them across multiple filings.

Blanket requests under pre-CARM rules required a cover letter, detailed schedules, and often took two to four weeks for CBSA to process. The timeline hasn’t improved under CARM. If you’re correcting a quarter’s worth of provisional entries and the first adjustment was processed by CBSA as a Type F during cutover, expect the second correction cycle to add at least three weeks to your true-up timeline. That delay can push your duty refund into the next fiscal quarter, which matters if you’re managing cash flow against monthly RPP bond settlements.

For importers who rely on post-release adjustments to manage valuation, transfer pricing true-ups, or retroactive tariff preference claims under CUSMA or CETA, this procedural bottleneck is now a planning variable. You can’t assume that a second correction will move as quickly as the first.

What to Check in Your Adjustment Queue Now

If you filed B2s, B9s, or blanket requests in Q1 or Q2 2024 that were still pending when CARM went live in May, check whether CBSA processed them as Type F CADs. You can see this in the CARM Client Portal under transaction history. If the Type F was created by CBSA rather than filed by your broker, flag it. If any of those transactions are likely to require further adjustment due to ongoing verifications, transfer pricing reviews, or SIMA margin updates, start the B3-to-As-Declared-CAD conversion now, before you’re doing it under a thirty-day CBSA response deadline.

For transactions with high line counts, evaluate whether consolidating the corrections into a single blanket request is faster than converting dozens of individual B3s. The hundred-line threshold is the decision point, but the real breakpoint is often lower, around fifty lines, because the manual entry time for As Declared CAD conversions starts to outweigh the blanket-request processing delay.

If you’re working with a brokerage that handles both pre-CARM and CARM filings, this conversion work should be part of the adjustment workflow they offer. If you’re handling corrections in-house, the time cost is significant. We’ve seen importers spend two full days converting a single month’s worth of cutover adjustments into As Declared CADs because they didn’t realize the CBSA-created Type F CADs were locked until a verification response deadline forced the issue.

The Larger Pattern: Pre-CARM Cleanup Will Take Years

This bulletin is part of a broader reality: pre-CARM transactions will remain in the correction pipeline for at least another three years. CBSA’s verification cycle runs on a four-year statute of limitations under the Customs Act, and the agency is still working through 2022 and 2023 entries. Every verification letter, SIMA scope ruling, or origin challenge that touches a pre-CARM entry carries the risk of triggering this Type F adjustment lockout.

For importers with high adjustment volumes, especially those managing transfer pricing, allocation models, or provisional valuation, the procedural cost of corrections just went up. The old B2 workflow was slow but predictable. The new CARM adjustment process is faster when it works, but the cutover edge cases create procedural dead ends that didn’t exist under the B3 system.

If you’re running monthly or quarterly true-ups and any portion of your correction inventory predates May 2024, build the conversion step into your SOP now. The alternative is discovering the lockout when you’re three days from a verification response deadline and your broker tells you they need to go back to the original B3 and start over.

We handle these conversions daily. If your adjustment queue includes CBSA-created Type F CADs and you’re not sure whether a second correction will trigger the lockout, that’s a fifteen-minute conversation. Get in touch.

Source: CSCB