If your customs software and your ERP aren't talking to each other, someone on your team is manually re-entering data. Probably every single shipment. That's not just tedious — it's where mistakes that trigger CBSA audits come from.
We've seen it dozens of times. An importer keys a value into their ERP, their broker keys a slightly different value into the customs entry, and six months later CBSA's trade compliance verification team is asking why the two don't match. The answer is always the same: human error in a manual process. The fix is integration.
This isn't about buying expensive software for the sake of it. It's about closing the gap between what your business knows and what gets declared at the border.
And right now, in mid-2026, that gap is more dangerous than it's ever been. CBSA updated its trade compliance verification priorities earlier this year to specifically target goods subject to retaliatory tariffs — the surtaxes Canada imposed in response to U.S. trade actions. If you're importing anything that touches those categories, your entries are getting more scrutiny. Inconsistent data between your ERP and your customs declarations is exactly the kind of thing that flags a file for review.
Why the Gap Between ERP and Customs Software Exists
Most businesses built their ERP first — SAP, Oracle, Microsoft Dynamics, NetSuite, whatever fits their size. Customs compliance got bolted on later, usually through a broker's portal or standalone software like MIC, Descartes, or a proprietary TMS. The two systems were never designed to speak to each other.
So what happens? Your purchase order lives in the ERP. Your commercial invoice gets generated there. But when the shipment arrives, your broker or your in-house team is manually pulling that data and re-entering it into the customs declaration system. Every field is a chance to introduce an error — wrong HS code, transposed value, missing country of origin.
Under CARM (the CBSA Assessment and Revenue Management system), this matters more than it used to. Importers are directly accountable for their own declarations. You can't point at your broker and say "they filed it." The liability sits with your importer account. So if your internal data and your customs data don't match, that's your problem to explain.
What Integration Actually Looks Like
Let's be concrete. "Integration" can mean a few different things depending on your setup.
Level 1: Automated Data Export
The simplest version. Your ERP exports a structured file — usually CSV, XML, or EDI 856 (advance ship notice) — when a purchase order is confirmed or a shipment is created. That file gets pulled into your customs software automatically. No one re-types anything.
A food importer we worked with was manually entering commercial invoice data for 200+ shipments a month. After setting up a basic CSV export from their ERP to their broker's portal, they cut data entry errors by about 80% in the first quarter. Nothing fancy. Just stopped asking humans to copy numbers from one screen to another.
Level 2: Bidirectional Data Flow
This is where it gets genuinely useful. Your ERP sends shipment data to your customs platform. Your customs platform sends back the final classification, duty rates, and entry numbers. Your ERP records the actual landed cost — including duties and taxes — against the purchase order automatically.
For your finance team, this is significant. They stop waiting for someone to manually update the PO with the final duty amount. Landed costs are accurate. Accruals are accurate. No more end-of-month scramble to reconcile what was estimated versus what was actually assessed.
With retaliatory surtaxes still in play as of June 2026 — CBSA extended the surtax remission period by two additional months, but that relief is narrow and product-specific — getting your landed cost data right in real time matters more than ever. Finance teams that are still estimating duty accruals manually are getting burned when the actual assessments come in.
Level 3: Full API Integration with Real-Time Sync
The most sophisticated setup. Your systems talk to each other continuously via API. When a shipment status changes in CARM — released, held for examination, duty assessed — your ERP knows within minutes. Your team gets alerts. Your finance system updates automatically.
Honestly, most mid-sized importers don't need this right away. But if you're clearing more than 500 entries a year and you're still on Level 0 (manual everything), you're carrying unnecessary compliance risk and your finance team probably hates you a little.
The CARM Factor
CARM changed the integration conversation in a specific way. Before CARM, your broker held your security bond and managed your account with CBSA. The data flow between your systems and CBSA ran through your broker. You were somewhat insulated from the technical requirements.
Now, under CARM, you need your own importer account in the CARM Client Portal. You need your own security instrument (either a bond or relying on your broker's surety, with explicit authorization). And you're responsible for your own compliance history.
That means the data in CARM needs to match the data in your ERP. If CBSA pulls a trade compliance verification and asks for your records, they're going to compare what was declared against what your internal systems show. If those two things were generated by different manual processes, inconsistencies are almost guaranteed.
The practical move: make sure your CARM portal data — your importer business number, your transaction history — is reconciled against your ERP at least monthly. If you're integrated, this happens automatically. If you're not, someone has to do it by hand. That someone is probably already overloaded.
The Retaliatory Tariff Problem
This is new territory that didn't exist when most importers set up their current workflows.
Canada's retaliatory surtaxes — applied to a broad range of U.S.-origin goods — created a classification and origin problem that manual processes handle badly. Whether a product qualifies for surtax remission depends on specific criteria that CBSA has been actively clarifying throughout 2026. McMillan and McCarthy Tétrault have both published guidance on how narrow that relief actually is. The short version: don't assume your goods qualify without checking.
Here's where integration matters. If your ERP product master has accurate country of origin data and your customs software is updated with current tariff treatments, you can identify which of your SKUs are potentially subject to surtax before the shipment arrives. You can flag items for review. You can make sourcing decisions with real numbers.
If you're doing this manually, you're probably finding out at entry time — or worse, after the fact when CBSA's verification team comes knocking. CBSA explicitly updated its compliance verification priorities to target retaliatory tariff goods. That's not a rumour. That's published guidance. Your integration needs to account for it.
HS Code Management: The Piece Nobody Talks About
Here's where integration pays for itself in ways that aren't obvious upfront.
Your ERP has product master data — item numbers, descriptions, costs. What it probably doesn't have is accurate, maintained HS codes. Most ERPs let you add a tariff classification field, but keeping it current is another matter. The WCO's 7th edition HS changes came into effect January 1, 2025. If your product master wasn't updated then, you may be classifying under codes that no longer exist — or that now carry different duty rates.
A well-integrated setup solves this. Your customs software — or your broker's classification tool — maintains the correct HS codes and pushes them back to your ERP product master. When a new item is added, there's a workflow to get it classified before the first shipment arrives. Not after.
We had a client importing industrial components who had about 340 active SKUs. When we audited their ERP product master, 60-something items had HS codes that were either outdated or just wrong. Some had been wrong for years. They'd been underpaying duty on a few items, overpaying on others. The underpayments were the scary part — that's a voluntary disclosure situation waiting to happen.
If your ERP and customs software are integrated and your classification workflow is solid, that kind of drift doesn't happen. The codes are maintained in one place and used consistently everywhere.
What to Look For in a Customs Software Integration
Not all customs platforms integrate equally well. Before you commit to anything, ask these questions:
- Does it support EDI or API connections to your ERP? If the answer is "we can export a CSV," that's Level 1 at best. Not bad for a start, but know what you're getting.
- Can it push landed cost data back to your ERP? This is the piece most platforms handle poorly. The entry gets filed, but the final duty and tax amounts never make it back to your purchase order.
- How does it handle CARM? Can it connect directly to the CARM Client Portal? Can it submit Release Prior to Payment entries? Can it pull your account statement from CARM automatically?
- Does it handle retaliatory tariff flags? Can it identify goods subject to Canadian surtaxes and apply remission codes where eligible? This wasn't a question you needed to ask two years ago. It is now.
- What does the HS code management workflow look like? Is there a classification review process? Does it flag items that haven't been classified? Does it update when the tariff schedule changes?
- Who maintains the integration? ERPs get updated. APIs break. Who's responsible for keeping the connection working — you, your broker, or the software vendor?
Descartes, MIC Customs Solutions, and Customs City are the platforms we see most often in Canadian import operations. Each has different strengths depending on your volume and ERP. Your broker may also have a proprietary portal that can connect to your systems — worth asking before you go buy something standalone.
The Audit-Readiness Angle
CBSA's trade compliance verification program isn't going away. CARM gives them better data to identify anomalies and target verifications more precisely. And as of this year, they've explicitly updated their verification priorities — retaliatory tariff goods are on the list. When they show up — and for active importers, it's usually when, not if — you need to be able to produce records fast.
An integrated system makes this dramatically easier. Your customs entries, your commercial invoices, your proof of origin, your valuation records — ideally all linked and retrievable by entry number, shipment date, or supplier. Not scattered across email threads, your broker's archive, and a shared drive folder nobody's organized in three years.
CBSA's D17-1-21 memorandum on record keeping requires you to keep import records for six years. That's a lot of paper if you're doing it manually. Digitally, with proper integration, it's searchable and auditable in minutes.
Pull up your last trade compliance verification — or imagine your first one. How long would it take you to produce the commercial invoice, the bill of lading, the B3 entry, and the proof of origin for 50 shipments from 18 months ago? If the answer is "a few days and a lot of stress," integration should be on your priority list.
Getting Started Without a Six-Month IT Project
You don't need to boil the ocean. Here's a realistic starting point:
- Audit your current data flow. Map exactly where data is being manually re-entered. Every handoff point is a risk. You might find three or four places where integration would eliminate 90% of your exposure.
- Talk to your broker first. Before buying any software, find out what your customs broker's platform can already connect to. Many brokers have EDI connections or portal APIs that your ERP vendor can hook into with relatively little work.
- Fix your product master. Before you integrate anything, make sure your HS codes and country of origin data in your ERP are accurate. Integrating bad data just spreads bad data faster. With retaliatory tariff verifications actively underway, this step is urgent — not optional.
- Start with one data flow. Pick the highest-volume, most error-prone handoff — usually commercial invoice data to customs entry — and integrate that first. Get it working before you try to do everything at once.
- Build in a reconciliation check. Even with integration, set up a monthly review. Compare your CARM account statement to your ERP records. Catch discrepancies before CBSA does.
Frequently Asked Questions
Our ERP is older and doesn't have a modern API. Can we still integrate?
Usually yes, just not as elegantly. Older ERPs like older versions of Dynamics or SAP can typically export structured flat files (CSV or fixed-width text). Most customs platforms can ingest those automatically on a schedule. It's not real-time, but it eliminates manual re-entry. That alone is worth doing.
Our broker handles everything. Why do we need our own customs software?
Under CARM, you're directly responsible for your import account regardless of who files the entries. Your broker is your agent — they act on your behalf, but the compliance obligation is yours. Having visibility into your own entry data, your own duty payments, and your own CARM account isn't optional anymore. It's how you protect yourself.
How much does this kind of integration typically cost?
Ranges wildly. A basic CSV export setup might cost you a few days of your IT team's time and nothing else if you're using a broker portal that already accepts file uploads. A full API integration between a major ERP and a customs platform could run $15,000–$50,000 in implementation costs depending on complexity. Most mid-sized importers land somewhere in between. The ROI calculation is usually straightforward — add up the staff hours spent on manual data entry and the cost of your last penalty or audit response, and the math tends to work out quickly.
What if our suppliers send invoices in different formats?
This is the real-world messiness that makes integration harder than the demos suggest. Supplier invoice formats vary — some are structured PDFs, some are spreadsheets, some are still faxes (yes, really). The practical answer is to standardize what you can by working with your key suppliers on a consistent invoice template, and use OCR or data extraction tools for the rest. Some customs platforms have built-in invoice ingestion tools. It's not perfect, but it's still better than manual entry.
We're worried about data security — our ERP has sensitive pricing and supplier information. Is it safe to connect it to external systems?
Reasonable concern. The answer is that you don't need to expose your entire ERP to integrate customs data. A well-designed integration only passes the specific fields needed for customs purposes — item descriptions, values, quantities, country of origin, HS codes. Your supplier contracts, internal pricing models, and financial data stay in your ERP. Talk to your IT team about field-level data mapping before you agree to anything with a vendor.
How do we handle free trade agreement claims in an integrated system?
This is where integration really earns its keep. FTA eligibility — whether you're claiming CUSMA, CPTPP, or CETA preferential rates — depends on origin data that should live in your product master. If your ERP has accurate country of origin and your integration passes that to your customs software, FTA claims can be applied consistently and automatically. The risk of inconsistent FTA treatment (claiming preferential rates on some entries but not others for the same product) is one of the things CBSA looks for in verifications. Integration makes your treatment consistent. Consistent treatment is defensible treatment.
How do retaliatory tariffs affect our integration setup?
More than most people realize. Canada's surtaxes on U.S.-origin goods require your system to correctly identify country of origin, apply the right tariff treatment, and — where applicable — flag goods that might qualify for remission. CBSA has been issuing guidance throughout 2026 to narrow the scope of that remission relief, so what qualified a few months ago may not qualify today. Your customs software needs to be current on those rules, and your ERP product master needs accurate origin data to feed it. If either piece is stale, you're either overpaying duty or — more dangerously — underpaying it on goods that are now a verification priority.