CARM Portal Transaction Details Back Online: Rerun Your Month-End Downloads

The Bug

CARM Client Portal’s transaction list has been missing description details since late April. If you were pulling financial history downloads to reconcile what CBSA charged against what you expected, the description field was blank. That field tells you which CAD or shipment the line item belongs to. Without it, you have dollar amounts but no way to tie them back to specific declarations.

For brokers reconciling client accounts, that’s annoying but workable; we keep our own CAD records. For importers doing their own month-end close or validating RPP bond charges against the K84 monthly statement, it’s a real problem. You can see what CBSA charged, but you can’t match it to your books without the description field.

CBSA told CSCB last week that the missing details are now available in the CARM Client Portal. Rerun your financial history download and the descriptions should populate. If they don’t, CSCB wants to hear about it.

What It Broke

Month-end reconciliation for importers who file their own CADs or who review broker-filed declarations before approving payment. If your AP team closes books on the 5th of the following month and pulled CARM transaction history on May 5 to reconcile April imports, that download was missing the description field. They likely accrued based on commercial invoices or broker summaries but couldn’t validate line-by-line against CBSA’s actual posted charges.

RPP bond holders reconciling K84 monthly statements had the same issue. The K84 lists every CAD filed under your bond and the duties and fees CBSA applied. If you’re checking that statement against your own records, you need transaction-level detail with descriptions to match it up. CBSA’s auto-debit math has been wrong often enough this year to make that monthly check non-negotiable.

Import managers at multi-entity operations were stuck too. If you’re filing CADs under three different BN15s and trying to allocate costs back to the right business unit, a transaction list without descriptions is just a pile of dollar amounts. You end up cross-referencing commercial invoice dates and guessing.

What to Do Now

Rerun your financial history downloads for any month you’ve already closed. Go back to April if you were relying on CARM transaction history for your books. The description field should now populate.

If you closed April or May already and didn’t catch a discrepancy, you probably got lucky. Your accruals were close enough. But if you’re sitting on a variance you couldn’t explain at the time, this is likely why. Pull the corrected download and see if the missing descriptions resolve it.

For RPP bond holders, pull a fresh transaction list and cross-check your last two K84 statements. CBSA has been inconsistent this year about which period a late-filed CAD gets debited against. If a CAD you filed on May 2 for an April 28 release got debited on your May K84 instead of April, and your AP team accrued it in April, you’ll see the variance now.

The Broader Pattern

This isn’t the first CARM Client Portal issue that broke a reconciliation workflow and got fixed quietly. The portal’s financial history export has had intermittent timezone bugs, rounding inconsistencies on GST calculations, and at least two separate incidents where RPP bond debits posted to the wrong month.

Most of these get resolved within a few weeks. CBSA’s portal team has been responsive when CSCB escalates. But if you’re building your month-end close process around CARM data being correct and complete on the first pull, you’re setting yourself up for surprises.

The fix: don’t close your CBSA reconciliation until at least the 10th of the following month. Pull transaction history twice: once on the 5th for your preliminary close, once on the 10th to catch anything that posted late or got corrected. If there’s a variance, you’ll have a week to investigate before your final close.

For import operations that need faster closes, the practical answer right now is to reconcile at the CAD level using your broker’s records, not at the transaction level using CARM portal exports. Your broker has the CAD-level detail the day it’s filed. The portal catches up later.

If you’re filing your own CADs and need transaction-level assurance before you close books, you’re stuck waiting for CBSA’s systems to settle. That usually takes seven to ten days after month-end. Not ideal, but predictable.

We run our own internal reconciliation between CADs filed and CBSA transaction postings every month. We’ve started building a two-pass close: preliminary on the 5th using our CAD records, final on the 12th using CARM portal data. The gap between those two passes is where we catch CBSA posting errors, late debits, and portal bugs like this one.

If your compliance workflow depends on CBSA data being right the first time, add a review gate before you commit. CARM is getting better, but it’s not there yet.

Rerun your April and May downloads today. If the descriptions still don’t show, contact CSCB at [email protected]; they’re escalating portal issues to CBSA and tracking fixes. If you need a second set of eyes on the reconciliation or help building a close process that survives the next CARM hiccup, we run this every month.

Source: CSCB