A technology exporter operating between the United States and the European Union faces a question that arises on almost every significant dual-use transaction: which standing authorisations apply, and do the US and EU conditions align closely enough to rely on both simultaneously? The answer is rarely straightforward. As of May 2026, the BIS / EAR and EU dual-use systems each maintain their own catalogues of licence exceptions and general export authorisations – standing permissions that authorise defined categories of exports without a case-by-case licence application – but the eligibility conditions for those standing permissions diverge in ways that create real transactional risk.
General licence eligibility under BIS / EAR turns primarily on the item's Export Control Classification Number (ECCN – the designation under the US Commerce Control List that determines what controls apply to an item), the destination, the end-user, and the end-use. Under the EU dual-use regime, general export authorisations are destination-anchored and technology-category-specific, but the control criteria include additional Member State discretion that the EAR does not carry. A shipment that qualifies under one system may fall squarely within a prohibited category under the other.
This analysis sets out the governing authority for each system, maps the eligibility tests side by side, identifies the points of sharpest divergence, and closes with the practical steps a cross-border business should take before treating a general authorisation as the end of the analysis.
What governs general licence eligibility under the EAR?
Under the Export Administration Regulations, administered by the Bureau of Industry and Security within the US Department of Commerce, a licence exception is a standing permission that authorises an otherwise-controlled export without a separate BIS licence. The legal basis sits in the Export Control Reform Act and in IEEPA where national-security executive authority supports specific controls.
The eligibility test has four sequential filters. First, the item must have an ECCN that makes it eligible for the exception in question. Second, the destination country must not be excluded from that exception – country chart restrictions remove eligibility for a wide range of technology categories depending on the reason for control (national security, nuclear non-proliferation, regional stability, and others). Third, the consignee and end-user must not appear on the Entity List, the Denied Persons List, or the Unverified List, and must not be a Specially Designated National under OFAC. Fourth, the end-use must not be a prohibited end-use under BIS end-use controls or a nuclear, chemical, biological, or missile programme.
In our export-control practice, the sequence matters. Practitioners sometimes confirm the ECCN and stop there. The end-user and end-use screens are equally dispositive, and they operate independently of the item classification. A product eligible for an exception in principle becomes ineligible the moment the end-user appears on a restricted-party list, regardless of the item's technical parameters.
BIS also imposes specific knowledge requirements. An exporter that has knowledge – defined broadly to include reason to know – that the item will be diverted or used in a prohibited end-use cannot rely on a licence exception even if all four eligibility conditions appear satisfied. That knowledge element is not a formality. Regulators examine contemporaneous communications, due-diligence records, and transaction patterns when assessing whether an exporter should have known of a diversion risk.
How does the EU general export authorisation system differ?
The EU dual-use regime, established by the relevant Council Regulation (the successor to the earlier general dual-use regulation), administers general export authorisations at two levels: Union General Export Authorisations issued by the Commission and applicable across all Member States, and National General Export Authorisations issued by individual Member States for additional destination-item combinations they choose to permit under the framework the Regulation allows.
Union General Export Authorisations cover specific technology categories to a defined set of destination countries. The authorisation is self-executing – an exporter that meets the conditions notifies the competent authority (the relevant national agency) in its Member State and may proceed. No case-by-case approval is required. But the eligibility conditions are strictly territorial: each Union general authorisation specifies the permitted destinations by name, the item categories by reference to the EU control lists, and the end-use restrictions that must be satisfied. An item that falls outside those parameters requires either a national general authorisation (where one exists) or a specific individual licence.
Where the EU system diverges most sharply from the EAR is in the Member State discretion layer. A Union general authorisation may be suspended or restricted by a Member State where that state has grounds to believe the authorisation would be used inconsistently with national-security interests or foreign-policy commitments. In our cross-border practice, this discretion introduces a variable that has no direct equivalent in the US system: eligibility under a Union general authorisation does not guarantee that the competent authority in the exporter's Member State will treat it as available without condition.
The EU regime also imposes an internal compliance programme requirement on exporters wishing to use certain general authorisations for sensitive technologies. The exporter must maintain documented procedures for screening, end-use verification, and record-keeping. The EAR does not condition licence exception eligibility on a formalised compliance programme, though BIS strongly encourages one and may consider its absence an aggravating factor in enforcement.
Where do the regimes diverge on general licence eligibility?
The sharpest points of divergence between the EAR and the EU regime fall into four areas: the item-classification architecture, the destination logic, the end-user screening obligation, and the role of national discretion.
On item classification, the EAR uses the ECCN system, which assigns a multi-character code to each controlled item and maps controls to a country chart. The EU uses the Combined Nomenclature and the EU control list, which aligns closely with the Wassenaar Arrangement, the Nuclear Suppliers Group, and the Australia Group – as does the Commerce Control List. The alignment is substantial but not complete. An item that sits in one control category under the EAR may sit in a different category under the EU list, particularly for emerging technology areas where the two systems have moved at different speeds.
On destination logic, the EAR structures controls through the country chart, where different reasons for control activate for different country groups. The EU structures controls through the specific destination lists in each general authorisation. A country that is eligible under a US licence exception may not appear on the destination list of the applicable Union general authorisation, and vice versa. Cross-checking both sets of destination conditions is non-negotiable for any dual-jurisdiction shipment.
On end-user screening, both systems require checks against restricted-party lists, but the lists themselves are different instruments. The EAR requires screening against the Entity List, the Denied Persons List, and the Unverified List. The EU requires screening against the EU Consolidated List of persons subject to EU restrictive measures, which overlaps with but is not identical to US restricted-party lists. A counterparty absent from one set of lists may appear on the other. The correct approach is to screen against all applicable lists for every jurisdiction involved in the transaction.
On national discretion, the EU introduces a layer of competent-authority judgment that the EAR, as a federal US instrument, does not. BIS exceptions are uniform across the United States; a US exporter faces the same eligibility test regardless of the state from which goods ship. An EU exporter faces a federal floor (the Union authorisation) plus a Member State ceiling that can restrict what the federal floor permits.
The practical consequence is that a business relying on both a US licence exception and an EU general authorisation for the same transaction must confirm eligibility independently under each system. A conclusion under one system does not carry over to the other. This is the point that, in our experience, most often causes compliance gaps in dual-jurisdiction export transactions.
Which regime is stricter on general licence eligibility?
Neither regime is categorically stricter than the other; the answer depends on the item, the destination, and the end-user in a given transaction.
For technology exports to countries that fall into sensitive control categories under the EAR, BIS licence exceptions are often unavailable or subject to significant conditions. The country chart structure means that high-priority controls – particularly those associated with national security – remove exception eligibility for a large share of destinations. An exporter may find that an EU general authorisation covers a destination that no US licence exception reaches.
Conversely, for certain dual-use items involving emerging and foundational technologies – areas where BIS has expanded controls through successive regulatory updates – the EU regime may permit exports under a Union general authorisation that BIS would treat as requiring a specific individual licence. The EU's control list has in some areas moved more slowly to capture software and technology categories that BIS has already subject to heightened controls.
There is also an extraterritorial dimension that the EU regime does not replicate. US export controls under the EAR can reach re-exports and transfers of US-origin items or items containing US-controlled technology, wherever they occur. An EU exporter that receives US-origin components or technology remains subject to EAR re-export controls when it subsequently ships from an EU country to a third-country buyer. The EU regime does not impose equivalent extraterritorial reach over non-EU-origin items. This asymmetry means that for dual-use goods with US-origin content, the EAR is effectively the binding constraint even where an EU general authorisation would otherwise permit the export.
Have you mapped whether the goods in question carry US-origin content or US technology? That single question determines whether the EAR applies to an otherwise EU-governed transaction.
The position above covers the standard analysis. Your facts – the item's origin, the destination, the specific end-user, and the transaction structure – will determine which regime is binding and whether a general authorisation is available at all.
For an eligibility assessment tailored to your transaction, contact Calder & Vance at info@caldervance.com.
What are the key risk flags in a dual-jurisdiction eligibility analysis?
A transaction that appears eligible under both systems at the point of initial review can lose that status at several later stages. Practitioners advising on BIS and EU matters identify the following as the highest-frequency sources of error.
The first risk flag is the de minimis rule. Under the EAR, exports of non-US-origin items are subject to EAR jurisdiction when controlled US content exceeds the applicable de minimis threshold. An EU exporter that applies only the EU regime to a product with US-origin components may unknowingly be in violation of US re-export controls. The EU general authorisation does not provide a defence to an EAR violation.
The second risk flag is the treatment of deemed exports. Under the EAR, the release of controlled technology to a foreign national within the United States is treated as an export to that national's country of nationality. The EU regime has no direct equivalent concept, though some Member States have developed national controls on technology transfer in employment and research contexts. A business that manages joint development teams across the Atlantic needs to account for deemed export obligations under the EAR independently of any EU authorisation.
The third risk flag is end-use change. Licence exceptions and general authorisations are condition-specific. If the end-use changes after export – if a buyer redirects goods to a different facility or programme – the original authorisation does not cover the new use. Both systems impose post-export obligations on exporters who become aware of a diversion. Under BIS rules, reporting obligations can arise in those circumstances.
The fourth risk flag is the interaction with financial sanctions. A transaction eligible under an export licence exception or a general authorisation may still be prohibited by financial sanctions administered by OFAC (in the US) or by the EU Council regulations (in the EU). Export authorisations and financial sanctions are parallel control systems; clearance under one does not provide clearance under the other. In a recent matter, a manufacturer in the chemicals sector confirmed EAR eligibility for a transaction but did not screen the buyer's parent entity for OFAC-administered financial sanctions. The exposure only came to light during post-closing due diligence. We have seen this pattern recur across sectors.
How should a cross-border business manage the eligibility determination?
The practical decision sequence for a dual-jurisdiction transaction has distinct steps, each of which must be completed before the next is treated as resolved.
Step one is item classification under both systems. Classify the item under the ECCN to establish whether it is controlled under the EAR and, if so, for what reasons. Simultaneously, classify the item under the EU control list to establish its EU control category. Where the two classifications diverge, the more restrictive position governs that jurisdiction's controls.
Step two is destination screening. Map the destination against the US country chart for the relevant reason-for-control columns. Then check whether the destination appears on the applicable Union general authorisation's destination list, or on a relevant national general authorisation if one is available in the Member State concerned.
Step three is end-user and restricted-party screening. Screen the consignee, the end-user, and all intermediaries against the Entity List, the Denied Persons List, the Unverified List, the SDN List, and the EU Consolidated List. Document the screening, the database versions used, and the date of the check. Record-keeping obligations under both systems require contemporaneous documentation; under the EAR, the standard period is five years from the date of export or the date the transaction terminates, whichever is later.
Step four is end-use verification. Obtain and document the end-use statement from the buyer. Assess whether the stated end-use falls within any prohibited category under either regime. Where the end-use involves a government buyer, military application, or a research institution in a sensitive sector, enhanced verification is appropriate before relying on a general authorisation.
Step five is the US-origin content check. For EU exporters, determine whether the goods or technology contain US-origin items or US-controlled technology at or above the applicable de minimis threshold. If they do, the EAR applies as a parallel control and BIS eligibility must be confirmed independently.
Step six is financial-sanctions clearance. Confirm separately that the transaction is not prohibited by OFAC-administered financial sanctions or by applicable EU Council regulations. This step runs in parallel with, not after, the export-control analysis.
If a transaction has already been flagged, or a prior export is under review, early advice can preserve options that narrow with time. For a confidential review of a potential compliance issue, contact Calder & Vance at info@caldervance.com.
When does a general authorisation fail and a specific licence become necessary?
A specific individual licence is required whenever the goods, destination, end-user, or end-use falls outside the scope of any available general authorisation or licence exception. Under the EAR, BIS processes specific licence applications through a structured interagency review, and the timeline varies by the sensitivity of the application. Under the EU regime, a specific licence application goes to the national competent authority of the exporter's Member State; timelines and information requirements differ across Member States.
Situations that reliably require a specific licence include: exports of items controlled for nuclear non-proliferation or chemical- and biological-weapons reasons to non-allied destinations; exports to entities on the Entity List or their affiliates where no licence exception applies; and exports of certain emerging technology categories where BIS has designated controls without a corresponding licence exception.
Under the EU regime, a specific licence is required when the transaction does not fit any Union or national general authorisation, when the competent authority has suspended a general authorisation for the relevant destination, or when the exporter's own compliance assessment identifies a concern that the general authorisation does not address. Some Member States also require individual licences for technology transfers in sensitive sectors regardless of the EU general framework.
Is a specific licence always slower than relying on a general authorisation? Not necessarily. Where eligibility under a general authorisation is genuinely uncertain – where the item classification is ambiguous, the end-use is not fully documented, or the end-user sits close to a restricted party – the time spent resolving the eligibility question can exceed the time a well-prepared specific licence application takes to process. We regularly advise clients to weigh that comparison before defaulting to a general authorisation that has not been rigorously validated.
A common misconception: item classification is sufficient for eligibility
Many compliance teams treat the ECCN determination – or its EU equivalent – as the primary and often final step in the eligibility analysis. This is the most common structural error we see in export-control compliance across sectors. Item classification establishes only that a licence exception or general authorisation exists in principle. It does not confirm that the exception is available for this destination, this end-user, this end-use, or these goods on this date.
The EAR makes this explicit: even an item that qualifies for a named exception requires that all the conditions of the exception are met, including the restricted-party checks and the knowledge standard. The EU regime mirrors that logic: the Union general authorisation sets out eligibility conditions that extend beyond the item category to the destination, the end-use, and the exporter's compliance procedures.
In our cross-border practice, we regularly see the consequences of treating classification as a proxy for eligibility. The correction requires a full eligibility review under both systems, documentation of the analysis, and in some cases a voluntary self-disclosure (VSD – a self-initiated report to the relevant authority disclosing a potential or actual violation, which can be a significant mitigating factor in enforcement) where a prior shipment is found to have been improperly authorised. The VSD route is available under the EAR and is a recognised mechanism; its terms and effects differ from the UK and EU equivalents, and early advice on whether and how to make a disclosure is important.
Related practices
- Licensing and frozen-account management under BIS / EAR – navigating account restrictions and export authorisations in tandem
- General licence eligibility: OFAC vs BIS / EAR – a parallel analysis of the US financial sanctions and export-control licensing systems
- General licence eligibility: further OFAC and BIS / EAR comparison – extended cross-regime analysis for complex dual-jurisdiction transactions