Calder & Vance International Sanctions & Compliance Counsel

Export Controls & Dual-Use · cross-border

EAR99 determinations across regimes: what businesses must know

An export compliance team at a mid-size technology company classifies its latest product line as EAR99 (goods subject to the US Export Administration Regulations but not listed on the Commerce Control List, therefore the lowest-restriction category under the EAR) and books shipments to three continents. Six months later, a European subsidiary receives a due-diligence questionnaire from a buyer's bank. The bank wants EU dual-use classification, an end-use statement, and evidence that the goods fall outside the UK's export-control schedules. The company has none of this. The deal is at risk. As of April 2026, this is one of the most frequent compliance gaps we encounter in cross-border export transactions.

EAR99 status is a US determination only. It means the item is not listed on the US Commerce Control List and does not carry a specific Export Control Classification Number (ECCN – the alphanumeric code that triggers licence requirements under the EAR). But a finding of EAR99 under the EAR says nothing about whether the same item requires a licence under EU dual-use rules, the UK Export Control Order, or the national regimes of Switzerland, Singapore, Japan, or Australia. Each regime has its own control list and its own classification logic. EAR99 is a starting point, not a universal clearance.

This guide walks through the EAR99 determination process step by step, explains how the parallel EU, UK, and broader international regimes interact with that finding, identifies the points where a US-only classification creates real legal exposure, and sets out when to involve specialist export-control counsel.

Step 1: What is an EAR99 determination and who makes it?

An EAR99 determination is a classification conclusion: after working through the US Commerce Control List, the exporter concludes that the item has no ECCN and therefore sits in the residual EAR99 category. The determination is made by the exporter, not by the Bureau of Industry and Security (BIS). BIS administers the EAR and maintains the Commerce Control List, but classification is a self-assessment obligation. The exporter carries the risk of getting it wrong.

The process begins with the product: its technical parameters, composition, function, and performance specifications. The exporter (or its counsel) maps those parameters against the Commerce Control List entries. If no entry matches, EAR99 is the result. That mapping requires technical knowledge of the item and legal knowledge of the list entries – neither alone is sufficient.

A voluntary self-disclosure (VSD – a proactive report to BIS of an apparent violation) is one of the tools available when a misclassification is discovered after shipments have gone out. Regulators treat a timely, complete VSD as a significant mitigating factor in penalty proceedings. But the practical lesson is earlier: classifying correctly the first time avoids the need for that conversation.

In our cross-border practice, we see the most classification errors in three categories: software with encryption functions, items with mixed civil-military potential, and technology that started life as commercial off-the-shelf goods but was subsequently modified. Each of those categories has dedicated list entries across multiple regimes. None of them should be characterised as EAR99 without a considered, documented analysis.

Step 2: How does the EU dual-use regime treat the same item?

The EU dual-use regime – administered under EU rules on the control of exports of dual-use items and technology, with individual EU member states issuing licences – operates its own Annex I control list. That list is harmonised with, but not identical to, the international export-control arrangements (the Wassenaar Arrangement, the Nuclear Suppliers Group, the Australia Group, and the Missile Technology Control Regime). An item that sits at EAR99 in the United States may appear on Annex I and therefore require an export authorisation from the relevant EU member state.

The EU regime also includes a catch-all provision. Under that provision, an exporter who knows or has been informed that items not listed on Annex I are intended for certain end uses – including weapons development or certain military end-use programmes in embargoed destinations – must seek a licence even without a list-based trigger. The catch-all is not theoretical. It applies whenever the exporter has knowledge of the end use, and regulators expect exporters to document that they asked the question.

One divergence worth flagging immediately: the EU regime extends in some circumstances to items passing through EU territory in transit, not only to items exported from an EU country of origin. A US company shipping EAR99 goods through Rotterdam may find that the transit creates a separate obligation under Dutch export-control rules. This is an area where the cross-border dimension of an EAR99 determination matters most.

The position above covers the standard case. Your facts – the counterparty, the goods, the destination, the end user, and the transit route – change the analysis. If your supply chain touches EU territory, an EU legal-entity subsidiary, or an EU-based distributor, the EU classification question needs to be resolved alongside the EAR classification.

For advice on your specific classification across the US and EU regimes, contact Calder & Vance at info@caldervance.com.

Step 3: How does the UK Export Control Order apply after EAR99?

The UK controls exports through the Export Control Order, administered by the Export Control Joint Unit (ECJU). The UK's control list was aligned with the EU's at the point of the UK's departure from the EU's internal market, but the two lists have since been maintained separately. Divergence between the UK list and the EU Annex I list is small but real, and it grows over time as each jurisdiction updates its schedules independently.

For a business exporting from the UK, EAR99 status has no legal relevance to whether a UK export licence is needed. The ECJU asks only whether the item appears on the UK control list, and whether any catch-all or end-use consideration applies. UK-based exporters who rely on a US EAR99 finding as their only classification record are not compliant with UK law.

The UK also maintains financial sanctions administered by the Office of Financial Sanctions Implementation (OFSI). While OFSI sanctions and export-control licensing are distinct legal regimes, they interact. An EAR99 determination does not screen the transaction against OFSI's consolidated list. We regularly advise businesses that discover this gap only after a compliance audit flags it.

There is a further practical point for businesses with US-origin goods that pass through UK warehousing or distribution before onward shipment to a third market. The re-export may engage both EAR obligations (under BIS jurisdiction because of the US origin) and UK export-control obligations (because the goods are leaving UK territory). A single EAR99 determination does not address both legs.

Step 4: Which other national regimes must a cross-border business check?

A cross-border business needs to ask, for each jurisdiction where it exports, manufactures, warehouses, or has a legal entity: does this country's export-control regime require a separate assessment of this item?

The answer is yes in several major trading jurisdictions, each with its own list and its own catch-all logic:

  • Switzerland: SECO administers the Swiss dual-use and export-control ordinances. Switzerland is not an EU member but participates in the same international arrangements. Swiss classification uses a distinct legal instrument.
  • Japan: The Ministry of Economy, Trade and Industry (METI) administers Japanese export controls. Japan's Foreign Exchange and Foreign Trade Act creates both list-based and catch-all obligations. For technology transfers to foreign nationals in Japan, a deemed-export equivalent rule applies.
  • Singapore: The Strategic Goods (Control) Act creates licensing obligations for items on the Strategic Goods Control List. Singapore's list references the international arrangements but is legislated separately. Re-export controls are particularly active in Singapore enforcement.
  • Australia: DFAT administers Australia's Defence Export Controls under the Defence Export Controls regime. The list draws on the same international arrangements. Australia's controls extend to the provision of services related to controlled goods, which is broader than many exporters expect.
  • Canada: Global Affairs Canada administers the Export and Import Permits Act. Canada's Export Control List again references the international arrangements but is maintained separately. North American businesses sometimes assume that a BIS licence or EAR99 determination covers Canada – it does not.

The common thread is that each national regime has its own legal instrument, its own update cycle, and its own catch-all test. EAR99 is a US domestic finding. It has no legal effect in any of these jurisdictions.

If a transaction has already been flagged by a regulator, or a filing has been challenged, an early review preserves options that narrow quickly. For a confidential review, contact us at info@caldervance.com.

What are the risk flags that signal a closer EAR99 review is needed?

Several patterns in a cross-border transaction should prompt a deeper review of any EAR99 finding, regardless of how straightforward the initial classification appeared.

End-use information changes everything. An EAR99 item shipped to a civilian electronics distributor presents a different risk profile from the same item ordered by a buyer whose other documented activities include defence procurement. The catch-all provisions in US, EU, and UK law all engage when the exporter has – or should have – awareness of a problematic end use.

The identity of the counterparty is a separate risk layer. EAR99 status does not clear a transaction where the buyer, a parent company, or an intermediate party appears on the Entity List (BIS's list of parties requiring a licence for all items subject to the EAR, including EAR99 items), the SDN List (OFAC's list of Specially Designated Nationals, where a US-nexus transaction with a listed party is generally prohibited regardless of the goods), or equivalent lists maintained by EU member states or the UK. In our experience, the Entity List is one of the most systematically missed controls in businesses that treat EAR99 as a final clearance.

A third risk flag is the destination. Certain destinations carry comprehensive controls or sector-specific restrictions that apply irrespective of the item's classification. An EAR99 determination does not remove destination-specific obligations.

A fourth flag is the technology transfer dimension. If engineers, technical documents, schematics, or software source code associated with the goods are being shared with non-US persons – whether by email, on a shared drive, or in a meeting room – the EAR's deemed export rule (treating the release of controlled technology to a foreign national as an export to that person's country of nationality) may apply even when the physical goods are EAR99. The deemed export rule catches technology and source code at a different, often more restrictive, ECCN than the hardware.

How does a cross-border compliance programme address EAR99 correctly?

A well-designed cross-border export compliance programme treats EAR99 as the output of one classification analysis and the input to at least four further checks, each governed by a separate regime. The practical workflow looks like this.

First, complete the US classification under the EAR: work through the Commerce Control List, document the technical parameters, and record the conclusion. If the conclusion is EAR99, record the reasoning, not just the label.

Second, run the EU classification for any goods destined for, transiting through, or controlled by an entity in an EU member state. Use the EU Annex I list and apply the catch-all test to the known or indicated end use. Document both analyses.

Third, if goods leave the UK, or if a UK legal entity is involved as exporter, consult the UK control list and ECJU guidance. Record the conclusion separately from the US and EU analyses.

Fourth, apply the same logic to each additional national regime in play: Switzerland, Japan, Singapore, Australia, Canada, or any other country where a legal entity in the supply chain is established or where the goods will enter the territory.

Fifth, screen all parties – buyer, end user, intermediate broker, freight forwarder, financial institution – against the Entity List, the SDN List, the UK consolidated list, the EU consolidated list, and the UN Security Council consolidated list. EAR99 status is irrelevant to this screening obligation.

Sixth, document everything. Export-control rules in every major jurisdiction impose record-keeping requirements. A decision that cannot be documented did not happen in regulatory terms.

We have acted for businesses across manufacturing, technology, and life sciences sectors that built this multi-regime classification workflow from scratch after identifying gaps in their existing programmes. The workflow is not especially complex once designed, but it does require deliberate structure. An EAR99 determination that exists as a Post-it note on a product file is not compliant documentation under any regime we work in.

For a practical review of your classification and screening process, reach our team at info@caldervance.com.

When should a business involve export-control counsel?

Counsel involvement is most valuable at four points in the EAR99 determination process across a cross-border footprint.

The first is at initial product classification, particularly when the item sits near the boundary of a listed category, has encryption or sensing functions, or is being modified from a previously EAR99 design. Classification decisions that are made quickly by non-specialist staff and never revisited carry a specific long-term risk: the product evolves, but the classification record does not.

The second is when a new market or a new distribution route is added. Each new jurisdiction may trigger a new licensing obligation. A classification that was complete for a business operating between two countries may become incomplete when a third country is added to the supply chain.

The third point is when a compliance audit, a due-diligence questionnaire, or a bank inquiry surfaces a classification that has not been documented to a standard the recipient finds credible. At that stage, the business needs counsel who can engage with the regulator, the bank, or the counterparty with authority and can document the position to an externally defensible standard.

The fourth is when an apparent violation has occurred: goods shipped without a required licence, or a counterparty identified on a restricted list after the transaction closed. VSD practice and penalty-defence strategy are areas where early counsel involvement materially improves the outcome, in our experience.

Related practices

Frequently asked questions

What are the steps to determine EAR99 status under cross-border?
The first step is a US classification under the EAR: map the item's technical parameters against the Commerce Control List and, if no entry matches, record the EAR99 conclusion with supporting reasoning. The second step is to run a parallel classification under each other applicable regime – EU dual-use Annex I, the UK control list, and any national list in the countries of export or transit. The third step is to screen all parties against the relevant restricted-party lists. EAR99 does not substitute for any of these subsequent checks, and the documentation for each must be maintained separately.
What is the most common mistake in EAR99 determinations?
The most common mistake is treating EAR99 as a universal clearance rather than a US-specific classification finding. Businesses that complete a US classification correctly and then ship internationally without checking EU, UK, or destination-country controls are exposed to licence violations under regimes that never accepted the US determination. A closely related error is failing to screen the counterparty against restricted-party lists – the Entity List in particular applies to EAR99 items and requires a licence for any transaction with a listed party, regardless of how the goods are classified.
How does cross-border differ from other regimes here?
In a purely domestic US context, EAR99 is the end of the analysis for most transactions: the item has no ECCN, and no BIS licence is required absent a sanctioned destination, a listed party, or a prohibited end use. Cross-border transactions add parallel legal obligations under the EU dual-use regime, the UK Export Control Order, and multiple national regimes, each with its own control list, catch-all test, and licensing authority. The cross-border context also raises the deemed-export question: technology transfers to foreign nationals connected to the transaction may be classified and licensed differently from the physical goods, even when the goods are EAR99.

Talk to Caldervance

For a scoped view of your exposure, contact info@caldervance.com.

Discuss your matter

This publication is general information and does not constitute legal advice. For advice on your situation, contact info@caldervance.com.