CBSA Revised the DERO List for Export Reporting — Here's What Changed and Why It Matters

CBSA Cleaned Up the DERO List

CBSA published a notice effective June 5, 2026, revising the list of Designated Export Reporting Offices (DEROs) available in the Canadian Export Reporting System (CERS) and the G7-EDI Export Reporting method. The stated goal is to align what’s listed in the Directory of CBSA Offices and Services with what exporters and customs service providers actually see when they file. It’s a data-hygiene exercise, but it has operational consequences if your filing templates or broker SOP still point to an office that no longer accepts export declarations.

The short version: CBSA found mismatches between the DERO codes in the directory and the codes available in CERS and G7-EDI. Some offices listed in the directory were never added to the export filing systems. Some codes in the filing systems pointed to offices that had closed, merged, or changed service scope. The revision removes the orphaned codes and adds the missing ones. If you’ve been filing export declarations to the same DERO for years without issue, you’re probably fine. If your broker or freight forwarder has been getting “invalid office” rejections on G7-EDI submissions, this is why.

What Changed in Practice

The notice doesn’t publish a line-by-line diff. CBSA updated the CERS Portal dropdown and the G7-EDI office-code validation table to match the current directory. If your export declaration template hard-codes a DERO that’s no longer valid, the system will reject the transmission starting June 5. The rejection message will tell you the office code is invalid, but it won’t tell you which office to use instead. You’ll need to cross-reference the updated directory or ask your broker.

This matters most if you export from multiple points of exit and your internal workflow routes declarations based on where the truck crosses. A common pattern: your warehouse in southern Ontario ships LTL south, and the freight forwarder files the export declaration naming the DERO closest to the crossing. If that DERO code was retired in the cleanup, the declaration bounces. The truck still crosses, but the export record sits in limbo until someone notices and refiles to the correct office. CBSA won’t hold the shipment, but you’ll have an incomplete export record in CERS until the corrected declaration goes through.

For imports, this has no direct effect. DEROs handle export reporting, not CAD filing or PARS release. But if your business runs both import and export programs under the same BN15, and your broker manages both sides, the change can create coordination friction. The import team keeps working in CARM and PARS as usual. The export team suddenly finds that half their pre-set DERO templates throw errors. If the same person at the broker manages both, they notice and fix it. If import and export sit in different queues, the export side can lag.

Why CBSA Bothered

CBSA reorganized regional office footprints several times in the last decade, especially after budget cuts in 2012 and 2016, and again when CARM rolled out and shifted examination workload to larger hubs. Offices closed, merged, or changed mandate. The directory got updated, but the CERS and G7-EDI reference tables didn’t always follow. The result: exporters filed to offices that no longer existed, or couldn’t file to offices that did. The mismatch created support load for the CBSA technical help desk and produced incomplete export records that had to be manually corrected later.

The revision is administrative cleanup, but it signals something worth watching. CBSA is tightening data hygiene across all its filing systems. CARM already enforces stricter validation on CAD fields that the old paper B3 process let slide. The RPP bond reconciliation process catches discrepancies that used to disappear into monthly statements. The DERO cleanup is the export-side equivalent. If your templates and SOPs haven’t been reviewed since before CARM went mandatory, this is a reminder to audit them before the system does it for you.

What You Should Check Now

If your company exports, pull the export declaration templates your broker or forwarder uses and confirm the DERO codes against the updated directory. If you file in-house using CERS or G7-EDI, check your saved profiles and workflow scripts. If you haven’t filed an export declaration in six months, test one before you need it in production.

If you use our brokerage services for both import and export, we’ve already updated the DERO routing tables and tested the templates. If you handle export reporting in-house or through a different provider, it’s on you to confirm the codes still work.

For freight forwarders managing cross-border LTL or FTL, this is a good time to verify that your dispatch system and broker API integrations pull the DERO code dynamically from the directory rather than hard-coding it. Hard-coded references break when CBSA changes the table. Dynamic lookups adapt.

How This Connects to the Import Side

Most of our clients care more about import compliance than export reporting, but the two touch each other in three places. First, if you’re claiming duty drawback on re-exported goods, the export declaration has to name the same goods, same HS classification, and same value as the original CAD. A mis-routed or rejected export declaration delays the drawback claim. Second, if you’re running a bonded warehouse or sufferance operation (we operate Montreal sufferance space through our FENGYE partner), export declarations often accompany goods leaving bond. A rejected export filing can hold up the bond discharge, which holds up the accounting reconciliation. Third, if you’re an NRI (non-resident importer) importing to Canada and then re-exporting to the U.S., you need clean export records to prove you didn’t consume the goods in Canada. A broken DERO code creates a gap in the audit trail.

None of these are catastrophic, but they’re all annoying and time-consuming to fix after the fact. Better to confirm the DERO codes are current before June 5.

Timeline

The effective date is June 5, 2026. CBSA didn’t publish a grace period or a soft-launch window. After that date, invalid DERO codes will reject. If your export volume is low and you can tolerate a few rejected filings while you sort out the right codes, you can wait and fix on failure. If you run regular scheduled exports and can’t afford transmission errors, check the templates now.

CBSA hasn’t published a migration guide or a before-and-after DERO code table. The updated directory is live at cbsa-asfc.gc.ca, and the CERS Portal dropdown will reflect the new list on June 5. If you need a crosswalk between old codes and new codes, your broker should be able to pull that from the CERS user guide or the G7-EDI technical specs.

We’ve already mapped the changes for the DEROs our clients use most often. If you’re not sure whether your usual office is still valid, get in touch and we’ll confirm it in about two minutes.

Source: CSCB