CBSA's New Systems Working Group: Will It Fix What's Actually Broken?

The Canada Border Services Agency held the first meeting of its Business Systems Enhancements Working Group on July 16, 2026. This is the inaugural working group under the Commercial and Trade Industry Forum (CTIF), which replaced the Border Commercial Consultative Committee (BCCC) earlier this year. Minutes aren’t public yet, but the fact that “business systems enhancements” got its own dedicated forum tells you how much operational friction has built up since CARM went mandatory.

What CTIF Actually Is

CTIF is the new government-industry consultation structure. BCCC served that role for years, but CBSA reorganized the forum structure in 2026. The working group model is supposed to allow deeper technical discussion on specific problem areas. Business systems—meaning the CARM Client Portal, eManifest, ACI transmission, release processing, and all the other digital infrastructure brokers and importers touch daily—got first priority.

That priority ranking is not a coincidence. The portal has been the single largest source of filing friction since the October 2023 CARM transition. When a system that governs every commercial import into Canada has this many sharp edges, eventually the Agency has to sit down with the industry and figure out what’s broken.

The Real Issues Brokers and Importers Face

If you file CADs regularly, you know the pain points. Portal session timeouts that kill half-finished declarations. Amendment workflows that fail on shipments still in transit. Release status queries that return stale data. The gap between what the duty estimate on the release notice says and what the final accounting shows when you close the CAD. The RPP bond reconciliation process that requires manual comparison of the K84 statement against your own records because the portal doesn’t surface discrepancies in real time.

None of these issues stop you from filing. They just add time, rework, and risk. An import manager trying to track whether a flagged shipment cleared can’t get a reliable answer from the portal, so they call the broker, who calls the CBSA officer, who checks the internal system and relays the status. That’s three people doing work the portal should handle.

The eManifest side has its own friction. ACI transmission errors that require manual correction at the port. Cargo control numbers that don’t match between the carrier’s manifest and the CBSA system. In-bond shipments that get flagged for examination because the linking data didn’t transmit cleanly. These aren’t catastrophic failures, but they’re frequent enough that every broker has a workflow for handling them.

What the Working Group Needs to Fix

The hard part of any government-industry consultation is distinguishing between “this is annoying” and “this is actually costing money and creating compliance risk.” Portal session timeouts are annoying. A CAD amendment function that fails silently and requires a broker to call the CBSA help desk to unlock the file is a compliance risk, because it delays correction of classification or valuation errors that trigger AMPS penalties if not fixed within the statutory window.

Release prior to payment has been a particular stress point. The RPP bond is supposed to let importers take delivery before duties and taxes are finalized, but the reconciliation process between what CBSA estimates on release and what the final CAD accounting shows is still largely manual. If the estimate is off, the importer’s bond gets hit, and the portal doesn’t flag the discrepancy until the monthly K84 statement arrives. By then you’re weeks past the shipment and trying to reconstruct what went wrong.

SIMA filings are another area where the portal workflow doesn’t match the operational reality. If you’re importing subject goods and need to file normal value and export price data, the form structure in the portal assumes you have all the supplier documentation at the time of release. In practice, you often don’t. The workaround is to file preliminary data and amend later, but the amendment path for SIMA-related fields is not straightforward. The working group should address that.

Will This Actually Change Anything?

Consultation forums like CTIF are useful when they produce specific fixes. BCCC had a mixed track record. Some technical issues got resolved; others got discussed for years without movement. The test for this working group is whether it results in portal updates, clearer D-memoranda on system requirements, or operational changes at the port level that reduce the manual workarounds brokers and importers currently rely on.

The fact that CBSA made business systems the first dedicated working group suggests they know the current state is not sustainable. Whether that translates into budget, developer time, and actual system improvements is a different question. Government IT projects move slowly. The industry’s job in this forum is to be specific about what breaks, how often, and what the downstream cost is.

If the working group produces a prioritized backlog of fixes and CBSA commits to a delivery timeline, that’s progress. If it becomes a recurring meeting where the same issues get discussed without resolution, it’s just BCCC under a new name.

What Import Managers Should Watch For

When the meeting minutes get published, look for whether the discussion stayed at a high level or got into specific system behaviors. Generic statements about “improving user experience” don’t mean much. Specific commitments like “we will fix the CAD amendment timeout issue in Q3” or “we will add real-time bond utilization reporting to the portal” are what matter.

If your operation relies on RMD releases, pay attention to any discussion of PARS processing times and the release-prior-to-payment workflow. If you import subject goods under SIMA, watch for any mention of normal value filing improvements. If you run a sufferance or bonded warehouse, anything touching in-bond movement and cargo control documentation is relevant.

The other thing to watch is whether CBSA treats this as a one-way briefing or an actual working session. Industry input only matters if the Agency is willing to adjust priorities based on what brokers and importers say is breaking. The structure of CTIF is supposed to enable that, but structure and practice are not always the same thing.

The meeting minutes will tell us whether this working group has teeth. If your CARM filing workflow hits the same friction points we covered here, talk to us. We track what breaks and what the workarounds are.

Source: CSCB