A North American technology distributor secures a purchase order for advanced signal-processing equipment. The US parent has classified the item under the Export Control Classification Number (ECCN – the alphanumeric code under the US Commerce Control List that determines what export authorisation, if any, a product requires) system it knows well. Its Canadian affiliate asks a reasonable question: does that classification carry across the border, or does Canada apply an entirely separate analysis? The answer shapes licence requirements, end-use obligations, and criminal-exposure for both entities.
The United States classifies dual-use and military-related goods under the Export Administration Regulations (EAR), administered by the Bureau of Industry and Security (BIS). Canada operates its own export-control regime under the Export and Import Permits Act and the associated Control Lists, administered by Global Affairs Canada (GAC). An ECCN does not travel across the border by default. A product classified as EAR99 in the United States may still appear on Canada's Export Control List, and a product requiring a licence under the EAR may be freely exportable from Canada – or subject to additional Canadian controls that US counsel never considered.
This analysis maps the key structural divergences between the two regimes on classification, compares their list architectures and licensing triggers, identifies the risk flags that arise in cross-border supply chains, and explains when a business operating in both jurisdictions needs dedicated counsel on each side.
How does ECCN classification work under the US EAR?
ECCN classification under the EAR is the starting point for every US export transaction: it determines the applicable controls, the available licence exceptions, and the end-use conditions that follow the goods wherever they travel. BIS administers the Commerce Control List (CCL), which is organised into ten categories (from 0 for nuclear materials to 9 for aerospace and propulsion) and five product groups (equipment, test and production equipment, materials, software, and technology). Each ECCN sits within that matrix and carries a set of Reasons for Control – national security, anti-terrorism, nuclear non-proliferation, missile technology, crime control, and others – that determine which destinations and end uses require a licence.
Classification is the exporter's responsibility. BIS does not pre-classify goods on request as a default service; instead, exporters are expected to self-classify by reviewing the CCL parameters and, where there is genuine uncertainty, submitting a Commodity Classification Request to BIS for a binding determination. In our experience, the gap between how companies believe they have classified a product and how BIS would actually classify it is one of the most common sources of enforcement exposure. The CCL parameters are technical and precise; a slight difference in processing speed, frequency range, or layer count can shift an item from one ECCN to another – or from a controlled ECCN into EAR99 status.
EAR99 is the residual category: items subject to the EAR but not listed on the CCL. EAR99 goods do not require a licence for most destinations, but they are not exempt from all controls. They remain subject to the General Prohibitions in the EAR, meaning that an EAR99 item destined for a party on the Entity List, a Denied Person, or a prohibited end use still requires a licence or cannot be shipped. This is a point that cross-border teams frequently misread as a clean pass.
What is Canada's equivalent classification system?
Canada's export-control regime rests on the Export Control List (ECL), a schedule to the Export and Import Permits Act maintained and updated by Global Affairs Canada. The ECL is Canada's sovereign list; it is not a copy of the US CCL and does not replicate ECCN designations. GAC structures the ECL into groups that broadly correspond to international control regimes – the Wassenaar Arrangement, the Nuclear Suppliers Group, the Australia Group, the Missile Technology Control Regime – but the precise item descriptions, parameters, and thresholds reflect Canadian legislative drafting choices, not US administrative decisions.
When Canada's ECL incorporates Wassenaar Arrangement entries, the parameter language often tracks the common Wassenaar text closely. The US CCL, which also implements Wassenaar, frequently adopts similar language. This creates an appearance of alignment that does not always hold in practice. Wassenaar member states retain discretion over how they transpose common entries into domestic law, and both Canada and the United States exercise that discretion differently. A product that clears the technical parameters of a Wassenaar entry under the CCL may still fall within a Canadian ECL entry – or vice versa – because the two jurisdictions have drawn the line at different points in the parameter range.
Canada also controls certain items under the Dual-Use List, which is a component of the ECL distinct from the munitions items. Software and technology that exist only in encrypted form, or that is publicly available, may be treated differently under the Canadian rules than under the EAR. In our cross-border practice, the software and technology controls are the category most likely to produce a classification mismatch between the two regimes.
Where do the regimes diverge on ECCN classification?
The deepest divergence is structural: the US EAR produces an ECCN, a globally portable identifier that appears on shipping documentation and export licences; Canada's ECL produces no equivalent code. A Canadian exporter classifies goods against the ECL entries directly, by reference to the item descriptions and technical parameters in each group. There is no Canadian analogue to the alphanumeric ECCN format. This means that a US ECCN cannot be "translated" into a Canadian classification mechanically. The analysis must be conducted independently against the Canadian list.
Several specific points of divergence are worth isolating.
List coverage and residual categories. The US EAR applies to all items in US commerce, whether or not they appear on the CCL; EAR99 is the default. Canada's EIPA applies to items that appear on the ECL; goods not on the ECL are not subject to export permit requirements under that regime (though other Canadian controls, including sanctions regulations administered under the Special Economic Measures Act (SEMA), may apply independently). This means that a product classified as a controlled ECCN in the United States may have no ECL entry, requiring no Canadian export permit to most destinations, while requiring a BIS licence from the US side of the same transaction.
Country coverage. The US EAR uses a four-tier country grouping (Country Groups A through E) that determines which licence exceptions are available and which Reasons for Control are triggered. Canada's permit requirements under the ECL are destination-specific but structured differently. Canada maintains an Automatic Firearms Country Control List and applies area controls selectively; the mapping of destination-specific controls does not replicate the US country-group architecture. A destination that falls into a favourable US country group may still require a Canadian permit, and vice versa.
Technology and software controls. The EAR controls technology and software "required for" the development, production, or use of a controlled item, even where the technology itself is intangible and never physically exported. Canada's technology controls under the ECL follow a similar "required for" approach but apply it through different ECL entries with their own parameter sets. The deemed export concept – the release of controlled technology to a foreign national within the United States – has no precise Canadian equivalent, though Canada has its own foreign-national controls for certain sensitive technology releases. This divergence matters acutely for joint development programmes and for companies that share technical data across the border.
Encryption. The EAR has a detailed and frequently updated set of controls for encryption items, with licence exceptions that permit many commercial encryption products to be exported or re-exported after a one-time notification to BIS. Canada's approach to encryption controls under the ECL is less granular. Products that qualify for a US licence exception may still require analysis under the Canadian list, and the notification mechanism has no direct Canadian counterpart.
How do OFAC sanctions interact with export-control classification?
OFAC and BIS are distinct regulators with different statutory bases and different enforcement priorities. OFAC administers economic sanctions – asset freezes, transaction prohibitions, and sectoral restrictions – under IEEPA, the Trading with the Enemy Act (TWEA), and other statutes. BIS administers export controls under the Export Control Reform Act and the EAR. A product can be EAR99 and still be subject to an OFAC prohibition. Conversely, a product can require a BIS licence and still be permissible under OFAC for a given counterparty and destination.
The interaction matters in a cross-border context because Canadian exporters and re-exporters of US-origin goods are subject to the EAR's re-export controls regardless of their location. If a Canadian company receives US-origin goods, re-exports them to a third country, or transfers controlled technology to a non-Canadian national, the EAR's re-export and deemed-export provisions may apply. OFAC's reach is similarly extraterritorial: a Canadian company that is a US person, that transacts in US dollars, or that deals in US-origin goods or services may face OFAC prohibitions that operate in parallel to the EAR's controls.
In our practice, the most common cross-border compliance failure is the assumption that OFAC and BIS controls are alternatives. They are not. A transaction that requires a BIS licence also requires a check for OFAC prohibitions, and a transaction that clears OFAC screening must still satisfy BIS classification and licensing requirements. Canadian companies that export goods with US-origin content face this dual-layer obligation on every controlled shipment.
The position above covers the standard cross-border case. Your facts – the origin of the goods, the ownership structure of the entities involved, the destination, and the end use – change the analysis. For a preliminary assessment of your classification and OFAC exposure, contact Calder & Vance at info@caldervance.com.
Which regime is stricter on ECCN classification?
Neither regime is uniformly stricter than the other; the comparison depends on the specific item, the destination, and the end use. The US EAR is broader in jurisdictional reach – it applies to all US-origin items wherever they travel and to all transactions with a US nexus, including transactions conducted by non-US persons outside the United States. Canada's ECL is narrower in jurisdictional reach but may apply stricter controls to specific items that the US has not listed on the CCL or has subjected only to lighter controls.
On specific technology categories, Canada has at times imposed controls that are more restrictive than the US position, reflecting Canadian domestic policy choices and, in some cases, obligations under the Wassenaar Arrangement that Canada has implemented more conservatively. On other categories, the US position is more restrictive, particularly for items with national-security or missile-technology Reasons for Control that the US applies to a broader parameter range than Canada's ECL covers.
The practical answer for a cross-border business is that the stricter prohibition governs. If a product requires a BIS licence and does not require a Canadian permit, the BIS licence is required. If it requires a Canadian permit and the EAR does not require a licence, the Canadian permit is required. If both regimes require authorisation, both must be obtained before the goods move. Attempting to structure a transaction so that one regime's control is avoided by routing through the jurisdiction of the other is precisely the kind of approach that exposes a business to enforcement risk under both sets of rules.
If a transaction has already been flagged – by a customs hold, a compliance review, or an agency inquiry – early legal review preserves options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential review.
What risk flags arise in cross-border US–Canada supply chains?
Cross-border supply chains between the United States and Canada generate a distinctive set of classification and licensing risks that do not arise in purely domestic transactions. In our experience, the following patterns account for the majority of compliance failures we see in this corridor.
Assuming USMCA eliminates export-control obligations. The Canada–United States–Mexico Agreement (CUSMA/USMCA) governs tariff treatment and facilitates customs procedures. It does not modify, suspend, or supersede the export-control obligations of either country. A company that ships goods across the border without export permits because "it's just Canada" is applying trade-facilitation logic to a separate regulatory regime. The two do not overlap in this way.
Relying on a US classification for Canadian re-export. A Canadian company that receives US-origin goods classified under a specific ECCN may re-export those goods to a third country. For that re-export, it must assess both the EAR re-export requirements (which may require a BIS licence) and the Canadian ECL requirements (which may require a GAC permit). The US ECCN is the starting point for the EAR analysis; it is not the answer to the Canadian ECL question.
Misidentifying the origin of goods in a mixed supply chain. When a Canadian manufacturer incorporates US-origin components into a finished product, the de minimis rule and the foreign-produced direct product rule under the EAR determine whether the finished product is subject to the EAR. If the US-origin content exceeds the applicable de minimis threshold, or if the product is the direct product of US-controlled technology, the EAR applies to the Canadian-manufactured finished good. This analysis requires input from both US and Canadian counsel and is frequently omitted from compliance programmes that treat the two regimes as entirely separate tracks.
Technology transfer in joint development and licensing arrangements. Cross-border technology-transfer arrangements – joint development agreements, licensing of software source code, sharing of technical specifications – trigger both the EAR's technology controls and Canada's ECL technology entries. The deemed-export analysis under the EAR (which applies to the release of controlled technology to a foreign national, including a Canadian national, within the United States) and the Canadian analysis of controlled technology releases must be conducted in parallel. In our experience, technology-transfer arrangements are the single category most likely to be structured without adequate export-control analysis.
Have you mapped the origin of every controlled component in your supply chain? Does your compliance programme address both the EAR's re-export controls and Canada's ECL separately, or does it treat them as a single analysis?
What should a cross-border business do about ECCN classification?
A cross-border business operating in both the United States and Canada should treat ECCN classification and Canadian ECL classification as parallel obligations, each requiring a dedicated analysis by reference to the applicable list. The following sequence reflects the approach we use when advising on cross-border classification matters.
- Determine US classification first. Classify each product against the CCL. For items where there is genuine parameter uncertainty, consider a Commodity Classification Request to BIS. Document the classification rationale, the CCL entry reviewed, and the Reasons for Control that apply. Record EAR99 determinations with equal rigour: the absence of a CCL entry must be confirmed, not assumed.
- Conduct an independent Canadian ECL analysis. Classify the same product against the ECL by reference to the applicable group and item description. Do not rely on the US ECCN as a proxy. Where the ECL uses Wassenaar text that appears similar to the CCL entry, verify that the parameter thresholds are identical; they frequently are not.
- Apply the destination and end-use overlay. For each regime, determine whether the destination is controlled and whether the end use or end user triggers additional restrictions. Under the EAR, check the Entity List, Denied Persons List, and Unverified List. Under SEMA (Canada's sanctions framework), check applicable Canadian sanctions measures that may prohibit or restrict the transaction independently of the ECL permit requirement.
- Check OFAC sanctions separately. Confirm that the transaction does not involve a Specially Designated National or Blocked Person, an OFAC-sanctioned territory, or a prohibited end use. OFAC sanctions apply in parallel to BIS export controls; satisfying one does not satisfy the other.
- Determine licence requirements under both regimes. If either regime requires a licence or permit, obtain it before the goods move. If both regimes require authorisation, both must be in hand. Document the authorisation basis for each shipment.
- Establish ongoing classification review. The CCL and the ECL are updated, sometimes significantly, through regulatory amendments, new Wassenaar Arrangement control entries, and unilateral changes. A classification that is correct today may be incorrect after the next amendment cycle. Build a periodic review into your compliance programme calendar.
In a recent matter, a Canadian technology company had been exporting a software product to markets in Asia and the Middle East for several years. Its compliance programme addressed the Canadian ECL but had not been updated to reflect changes to the relevant Wassenaar entry, which had been implemented in both the US CCL and the Canadian ECL. When the company's US parent conducted an internal audit ahead of a transaction, it identified that the product's performance parameters now fell within a controlled ECCN. Both BIS re-export controls and Canadian ECL permit requirements applied to past and future shipments. We assessed the classification history, advised on voluntary self-disclosure, and helped the company restructure its compliance programme. The matter resolved without enforcement proceedings, though no outcome can be guaranteed in any similar situation.
Related practices
- Deemed Export and Technology Controls (BIS/EAR) – US deemed-export analysis for technology transfers to foreign nationals
- ECCN Classification: OFAC vs EU – Key Divergences – comparative analysis of US and EU dual-use classification
- ECCN Classification: OFAC vs OFSI – Key Divergences – how UK export controls compare to the US EAR on classification
A common misconception: one classification covers both regimes
The most persistent misconception we encounter in cross-border US–Canada compliance is that a product classified under one regime is thereby classified for the other. It is not. The ECL and the CCL are separate legal instruments, maintained by separate regulators, updated on separate schedules, and subject to separate licensing and enforcement mechanisms.
The misconception is understandable. Canada and the United States are close trading partners, members of the same multilateral control regimes, and parties to the CUSMA. In many sectors, the practical effect of the two lists is similar, and goods that require a BIS licence to leave the United States will often also require a Canadian permit to leave Canada. But "often similar" is not "always identical", and the compliance obligation is binary: either you have the required authorisation, or you do not.
A second misconception is that EAR99 goods are automatically uncontrolled under Canadian law. EAR99 means the item is not listed on the CCL; it says nothing about the Canadian ECL. A product that BIS does not control may still appear on the ECL, requiring a GAC permit for certain destinations. Compliance counsel on both sides of the border should be involved before that assumption is embedded in a standard operating procedure.