A European engineering group prepares to ship a consignment of precision optics to a distributor in South-East Asia. The goods carry an EU dual-use classification already confirmed under the EU's own dual-use rules. The compliance team assumes the job is done. It is not. The same items may require a separate licence under the US Export Administration Regulations – the EAR (the rules administered by the Bureau of Industry and Security, BIS, governing the export of commercial and dual-use items from, or originating in, the United States) – because they contain US-origin technology or were produced using US equipment. One missed step and the exporter faces a potential denial of export privileges and a civil penalty.
As of May 2026, any item that has a US nexus – whether through US-origin content, US technology in its design, or US-sourced production equipment – must be assessed under both the EU dual-use rules and the BIS / EAR before it leaves the EU. The two regimes use different classification structures, different control triggers, and different licensing routes. An EU dual-use classification does not satisfy BIS / EAR requirements, and treating one as a substitute for the other is one of the most reliable routes to an enforcement action.
This guide walks through the practical steps for managing both regimes in parallel: from establishing whether BIS / EAR jurisdiction applies at all, through classification on the Commerce Control List, to licence determination and the record-keeping obligations that accompany every transaction.
Step 1: Establish whether BIS / EAR jurisdiction applies to your EU-origin item
Before any classification work begins, a business must answer a prior question: does the EAR reach this item at all? The EAR applies not only to items physically located in the United States but also to items of US origin wherever they are in the world, to items that incorporate more than a de minimis threshold of controlled US-origin content, and to items produced abroad using certain US-origin technology or software – a doctrine known as the foreign-produced direct product rule (a rule that captures foreign-made goods produced directly from certain US-controlled technology or software, or by certain US-controlled plant equipment).
An EU manufacturer working with components sourced partly from US suppliers, or using US-licensed chip-design software, may find that its finished product is subject to EAR jurisdiction even though it was designed, assembled, and will be shipped entirely from within the EU. The key questions to work through in sequence are: Does the item contain US-origin parts? Does the production process use US-origin technology transferred under a licence that triggers the direct product rule? Is the item itself of US origin, re-exported after importation into the EU?
In our practice, the single most common gap at this stage is the assumption that a product assembled in Germany or the Netherlands is automatically outside US jurisdiction. That assumption fails whenever the bill of materials or the technology-licence agreement has a US-origin thread running through it. Establishing jurisdiction is not a formality; it is the first classification gate.
Step 2: Classify the item on the Commerce Control List using the correct ECCN
Once EAR jurisdiction is confirmed, the item must be assigned an ECCN (Export Control Classification Number under the US Commerce Control List, the CCL) or confirmed as EAR99 – the residual category for items subject to the EAR but not listed on the CCL and therefore controlled only to a small set of restricted destinations. The CCL is divided into ten categories covering materials, electronics, computers, telecommunications, sensors, lasers, navigation, marine, aerospace, and propulsion items.
The classification process under the EAR is a technical one. For each item the analyst must identify the correct CCL category and group, match the item's specifications against the control parameters listed in the relevant entry, and determine which of the five control reasons applies: anti-terrorism, crime control, missile technology, national security, or nuclear non-proliferation, among others. Each control reason maps to a different set of Country Chart columns, which in turn determine whether a licence is needed for a specific destination.
This is where the EU parallel diverges sharply. The EU dual-use rules use a separate Annex I list with its own category structure and item specifications. A product might be controlled under EU dual-use Category 6 (sensors and lasers) without being listed under EAR Category 6A – or vice versa. Dual-use compliance counsel regularly encounter items that are EAR99 but controlled under the EU list, and items with a significant ECCN but no EU Annex I listing. Classification under one regime is not a cross-check for the other.
Where a company is uncertain of the correct ECCN – a common position with novel technology, software with evolving functionality, or items that straddle multiple CCL categories – it may submit a formal commodity classification request to BIS. BIS will provide a written classification determination. That determination does not, however, resolve the EU classification, which must be pursued separately through the competent authority of the relevant EU member state.
How does the EU dual-use classification process differ from the BIS / EAR process?
The EU dual-use classification process shares the same general structure as the EAR – a numbered list, technical control parameters, a residual category – but the administrative machinery and the legal basis are entirely distinct. Under the EU rules, the exporter classifies the item against Annex I of the relevant EU dual-use regulation. Where the item is not listed in Annex I, the exporter must still consider whether it could be caught by the catch-all control, which applies to items not on the list if the exporter has grounds to believe they may be intended for use in connection with certain controlled activities.
One significant procedural difference concerns the role of the competent authority. Under EU rules, exporters may seek a binding classification opinion from the national competent authority in the member state from which the export will take place. The opinion binds the issuing authority and gives the exporter a defensible basis for its classification. Under the EAR, the equivalent route is the commodity classification request to BIS, but the two instruments are not mutually recognised. Each stands only within its own regime.
A second divergence concerns intra-EU transfers. Items moving between EU member states are subject to simplified transfer obligations under the EU rules, with general transfer licences available for many items. The EAR, by contrast, does not distinguish between intra-EU and extra-EU movements in the same way. A re-export from one EU member state to another may still require BIS authorisation if the item is EAR-controlled and the end destination or end-use is a concern. Businesses operating integrated EU supply chains need to map both sets of obligations, not only the EU transfer rules.
The catch-all provisions also differ in scope and trigger conditions. The EU catch-all is broader in some respects, reaching certain weapons-of-mass-destruction-related concerns even for non-listed items. The EAR has its own end-use controls – including a general prohibition on exports to parties whose activities raise concerns about weapons development or diversion – but the conditions and the evidentiary threshold for invoking them differ from the EU standard. Compliance counsel must assess both independently for each transaction.
Step 3: Determine whether a BIS / EAR licence is required and which authorisation applies
Once an item has been classified with an ECCN, the licence determination requires cross-referencing the ECCN's control reasons against the Commerce Country Chart for the destination in question. If any column in the chart is marked for the relevant control reason and the destination country, a licence is required unless a licence exception applies. If the item is EAR99 or if no column is triggered, the item may proceed without a BIS licence – subject to end-use and end-user checks.
Licence exceptions (standing authorisations under the EAR that permit certain exports without a separately issued licence) are numerous and the conditions attaching to them are precise. The most commonly used exceptions in EU-origin export scenarios include those for low-value shipments, technology for end-users in allied countries, and certain intra-company transfers of technology. Each exception carries eligibility conditions, recordkeeping requirements, and, in some cases, notification obligations. Using an exception when the conditions are not met is itself a violation, and it is a pattern that BIS has pursued in enforcement.
Where no exception applies, the exporter must apply for a specific licence from BIS. BIS evaluates licence applications against a published set of review policies that vary by destination and by the type of item and end-use involved. Processing times vary. In our experience, straightforward applications for allied-country destinations resolve more quickly than applications involving restricted destinations or sensitive technologies, but no timeline can be guaranteed, and applications that generate requests for additional information can run significantly longer.
The EU parallel at this step is the national licence issued by the competent authority of the exporting member state. EU member states operate their own licensing systems within the EU framework. An EU licence does not substitute for a BIS licence and a BIS licence does not satisfy the EU licensing requirement. Where both regimes require a licence for the same shipment, both must be obtained before export.
The position above covers the standard classification-and-licence pathway. Your facts – the item's technical parameters, the origin of its components, the destination, and the end-user's profile – may alter the analysis at every step.
If you are at this stage of the assessment and have questions about jurisdiction, classification, or the applicable licence exception, contact Calder & Vance at info@caldervance.com for an assessment of your position under the EAR and the relevant EU rules.
Step 4: Screen the end-user and apply the denied-party and entity-list controls
Classification and licence determination do not exhaust the EAR obligations. BIS also maintains the Entity List (a list of foreign parties subject to specific licence requirements because of activities contrary to US national security or foreign-policy interests) and the Denied Persons List. Exports to parties on the Entity List require a licence regardless of the ECCN and regardless of whether a licence would otherwise be needed. The licence review policy for Entity List parties is generally a presumption of denial. A party that appears on the Denied Persons List may not receive any export from a US-origin source.
Screening obligations extend beyond the named buyer. The EAR requires the exporter to screen freight forwarders, ultimate consignees, and any intermediate parties involved in the transaction chain. A clean ECCN and a valid licence exception do not protect the exporter if the shipment is routed through a denied party. In our experience, exporters who automate their direct-buyer screening but conduct only manual checks on freight intermediaries carry a disproportionate enforcement risk at exactly this point.
The EU parallel is the EU Consolidated List of asset-freeze targets and the member-state designations. EU exporters must screen against both. The legal test for whether a transaction is prohibited differs between the EAR entity controls and the EU asset-freeze regime, but both require systematic pre-shipment screening and both impose record-keeping obligations. A business that screens only against one consolidated list and not the other has an incomplete process.
End-use controls add a further layer. If an exporter has knowledge, or reason to believe, that an item will be used in a prohibited activity – including certain military end-uses, weapons development, or diversion to a restricted destination – the EAR prohibits the transaction regardless of the ECCN or the licence status. The standard here is lower than actual knowledge. Indicators in correspondence, the buyer's line of business, an unusual routing through a transshipment hub, or a purchase quantity inconsistent with the stated end-use all give rise to a duty to inquire and, if inquiry is unsatisfactory, to decline the transaction.
What are the risk flags that should trigger a compliance review?
Certain transaction patterns, taken individually or together, indicate that a compliance review – and in some cases legal advice – is warranted before the export proceeds. These are not exhaustive but represent the patterns we encounter most frequently in our advisory work.
- A buyer in a third country requests a product that appears technically inconsistent with the stated end-use – for example, precision measurement equipment for a construction firm, or network-security hardware for an entity without an apparent technology function.
- The transaction involves a transshipment point in a jurisdiction known for diversion risk. Items consigned to an intermediary in a high-risk transshipment hub, even if the stated final destination is an unrestricted country, attract a higher duty of inquiry under the EAR.
- The bill of materials for a product being exported from the EU reveals a higher proportion of US-origin components than was apparent from prior classification work, potentially triggering the de minimis rules or the foreign-produced direct product rule.
- A technology-transfer agreement or a software licence granted to the EU entity by a US parent contains provisions suggesting that US export-control obligations attach to downstream exports of products incorporating that technology – a common issue in intra-group supply chains that is often identified only at the point of a third-party audit.
- The end-user is a state entity in a country subject to a country-wide arms embargo or to targeted controls under the relevant US regime, even if the item itself would not ordinarily require a licence for commercial exports to that destination.
- The proposed payment structure involves a party not identified in the original transaction documentation – a pattern that sometimes indicates an attempt to obscure the ultimate destination or the end-user, and which should prompt an enhanced due-diligence review.
If a transaction has already been flagged internally, or an export has already been made that may not have met all the applicable requirements, an early review with export-control counsel can establish the scope of any exposure, whether a voluntary self-disclosure is appropriate, and what remedial steps can preserve the company's relationship with BIS. Options that are available before a formal inquiry narrow after one has been opened.
For a confidential review of a potential compliance gap, contact Calder & Vance at info@caldervance.com.
Step 5: Establish and maintain the required records for every dual-use transaction
Both the EAR and the EU dual-use rules impose mandatory record-keeping obligations for every export transaction. Under the EAR, exporters, re-exporters, and transferors are required to retain records sufficient to reconstruct each transaction for a period of five years from the date of the export, re-export, or transfer. Records must include the Export Control Classification Number or the basis for treating the item as EAR99, evidence of the licence or licence exception used, the end-user statement or other end-use documentation, and the screening records demonstrating that the parties were checked against BIS and other applicable lists.
The EU rules impose a similar retention obligation. The precise period varies by member state because implementation is national, but the general standard is comparable to the EAR requirement, and in our experience most EU competent authorities conduct audits that extend back at least five years. Maintaining a unified transaction file that satisfies both regimes is operationally more efficient than maintaining separate records for the EU export and the BIS compliance file, and it produces a more coherent audit trail.
Record-keeping is not merely a procedural box. BIS has pursued enforcement actions in which the initial violation was relatively minor but the absence of adequate records transformed what might have been a remedied compliance gap into a sustained pattern of apparent violations. The record is also the primary basis on which a VSD (voluntary self-disclosure to a regulator, which under BIS practice is treated as a mitigating factor in the penalty calculation) is assessed. A VSD without a coherent transaction record is difficult to prepare and less likely to achieve the mitigation its disclosure would otherwise attract.
Records must be accessible. BIS can request documents at short notice, and an exporter that cannot retrieve its records in a form the agency can assess is, in practice, in a weaker position than one that maintains indexed, retrievable files. Digital storage with appropriate backup and access controls is the standard; paper-only archives present retrieval and integrity risks that become significant in an enforcement context.
A common myth: an EU authorisation covers the BIS / EAR requirement
The most resilient misconception in EU-based export-control practice is that an EU global export licence, or a member-state-specific licence, satisfies the BIS authorisation requirement for items with a US nexus. It does not, and this myth persists partly because the two regimes share terminology – "licence", "authorisation", "classification" – without sharing substance.
An EU global export licence authorises the exporter to export the item from EU territory under EU law. It has no effect on US law. An item subject to the EAR that is exported from the EU under an EU global licence without the required BIS authorisation is an unlicensed export under the EAR, regardless of the EU paperwork accompanying it. BIS has explicit jurisdiction over re-exports and transfers of EAR-controlled items, and that jurisdiction does not dissolve because the exporting country has its own licensing system.
The reverse is equally true. A BIS licence, or a BIS licence exception, does not satisfy the EU export authorisation requirement. A business that holds a BIS licence for a shipment from the EU but has not obtained the required EU authorisation has satisfied one regime and violated the other. Both must be in place before export.
A related misconception concerns the EU's open strategic technology licences and union general export authorisations. These instruments simplify EU licensing for certain allied-country destinations and certain categories of goods. They do not create any authorisation under the EAR. A shipment covered by a union general export authorisation still requires a full EAR licence analysis, including a check for any applicable licence exceptions and, where none applies, a BIS licence application.
Related practices
- Deemed export and technology controls under BIS / EAR – advising on technology-transfer obligations and deemed-export licence requirements for foreign nationals.
- EU dual-use classification guide – part 3 – deeper treatment of licence exceptions, end-use certificates, and post-shipment verification.
- EU dual-use classification guide – part 4 – managing classification divergences and building a dual-regime classification matrix.