A technology distributor based in the EU signs a supply agreement with a South-East Asian partner. The shipment includes items with potential military end-uses. Before the goods leave the warehouse, a member of the compliance team raises a question: does a general authorisation (a standing permission under the Export Administration Regulations that permits a defined class of transaction without a separate application) cover this destination and end-user, or does the exporter need to file a case-by-case licence application? The answer shapes the entire transaction timeline.
General licence eligibility under BIS / EAR rules explained: the Bureau of Industry and Security administers the EAR, which controls the export, re-export, and in-country transfer of dual-use and commercial items on the Commerce Control List. A licence exception (the EAR term for what practitioners and the EU regime both call a general licence) authorises a defined class of transaction without a separate application, but eligibility depends on the item's classification, the destination, the end-user, and the end-use. Where no exception applies, and no other authorisation covers the transaction, a specific licence application to BIS is required. As of June 2026, the EAR exception structure remains active and under ongoing review.
This briefing sets out who administers BIS / EAR general licence eligibility, the key prohibitions, the eligibility tests, how BIS enforces the rules, and where the US regime diverges from OFSI, the EU, and other regimes that cross-border businesses must also manage.
Who administers BIS / EAR and what is its legal basis?
The Bureau of Industry and Security, a division of the US Department of Commerce, administers the EAR under the authority of the Export Control Reform Act and, where applicable, the International Emergency Economic Powers Act. BIS operates the Commerce Control List (CCL), which assigns each controlled item an Export Control Classification Number (ECCN) that indicates the reason for control and the licence requirements by destination.
The EAR's reach is deliberately broad. It governs not only exports from US territory but also re-exports of US-origin items from third countries and transfers of technology and software to foreign nationals, whether inside or outside the United States. The concept of the de minimis rule and the foreign direct product rule extend BIS jurisdiction to foreign-made goods that incorporate above-threshold US content or that are the direct product of certain US technology. In our cross-border practice, clients are regularly surprised to learn that a transaction conducted entirely outside US territory can still require a BIS authorisation.
The position above covers the standard case. Your facts – the item's ECCN, the destination country, the end-user's profile, and any red-flag indicators – change the analysis materially.
For matters requiring both export-control and financial-sanctions analysis, our team assesses the interaction between BIS restrictions and the OFAC designation picture. See our service page on licensing and authorisations under the BIS / EAR regime for how we structure that work.
What does the EAR prohibit, and what does general licence eligibility depend on?
The EAR prohibits export, re-export, or in-country transfer of a controlled item to a controlled destination or end-user without authorisation. Authorisation takes three forms: a licence exception (standing permission), a specific licence (individual application), or an EAR99 determination (the item is not on the CCL and no licence is required absent a restricted end-use or end-user concern).
Eligibility for a licence exception rests on a multi-part test. First, the item must qualify: the ECCN and the reason for control determine which exceptions are available. Second, the destination must qualify: some exceptions are available only for countries in the lower-tier country groups and are not available for countries subject to comprehensive country-level controls or to specific multilateral-regime restrictions. Third, the end-user must qualify: individuals and entities on the Entity List, the Denied Persons List, or the Unverified List administered by BIS are typically ineligible for most exceptions, regardless of item or destination. Fourth, the end-use must qualify: where the stated end-use is military, nuclear, chemical, or biological, heightened restrictions apply.
The interaction between the four factors creates a matrix. A single disqualifying element – an Entity List hit, a prohibited end-use, a controlled destination – removes exception eligibility entirely and forces a specific licence application. In our experience, exporters most often misapply the end-user screen: they check the ECCN and destination but do not run a full restricted-party screen before assuming an exception applies.
How do licence exceptions under the EAR work in practice?
A licence exception operates as a standing authorisation: an exporter who meets all eligibility conditions does not need to apply to BIS before each shipment but must maintain records sufficient to demonstrate that the conditions were met at the time of each transaction. The EAR sets a record-keeping requirement; documents supporting an exception claim must be retained for a defined period so that BIS can verify compliance in a post-shipment review or enforcement investigation.
Several exceptions are particularly relevant to cross-border B2B transactions. The Technology and Software Unrestricted exception covers certain low-sensitivity technology released to the public domain. The Temporary Imports, Exports, and Re-exports exception covers goods that will return to the original exporter. The Shipments of Limited Value exception covers small-value consignments, subject to per-transaction and per-year value limits. Each of these has specific conditions, and the conditions differ by ECCN and country group.
A practical risk arises when a business relies on an exception without first confirming the item's classification. If the ECCN was self-determined incorrectly – a common occurrence with items at the boundary between controlled and EAR99 – the exception claim fails retrospectively. We regularly advise clients to obtain a formal commodity jurisdiction or classification determination before an export programme begins, not after a compliance review surfaces a discrepancy.
If a transaction has already been flagged, or a classification has been questioned by BIS, an early review can preserve options that narrow with time. Contact Calder & Vance at info@caldervance.com for a confidential assessment.
How does BIS enforce general licence eligibility, and what are the risk flags?
BIS enforces the EAR through both administrative and criminal channels. On the administrative side, BIS's Office of Export Enforcement can issue Warning Letters, impose civil penalties, and refer matters to the Department of Justice for criminal prosecution. A voluntary self-disclosure (VSD) – a proactive report to BIS of an apparent violation – is the principal mitigant; BIS guidance formally recognises a VSD as a significant mitigating factor in the penalty calculation, and our practice engages with this mechanism regularly in enforcement-defence matters.
The risk flags that most commonly precede an enforcement action are: continued dealings with an Entity List entity after the listing date; failure to re-screen counterparties against updated restricted-party lists before shipment; reliance on a licence exception that did not in fact apply because the ECCN was incorrect; and failure to maintain the records necessary to support an exception claim. A fifth risk flag – red-flag indicators of diversion – is particularly important. BIS guidance sets out specific indicators that an exporter should recognise as warning signs that a transaction may involve a prohibited end-use or a front company. Ignoring a red flag and proceeding without further due diligence is itself an aggravating factor in any subsequent enforcement proceeding.
The enforcement posture of BIS has intensified in recent years. Matters involving items with potential military end-uses have attracted particular scrutiny, and BIS has expanded the Entity List substantially. The practical implication: periodic screening of existing customer and supplier bases against the current CCL-related lists is a compliance necessity, not an optional check. When should a business conduct that rescreening? At minimum, when a new restricted-party designation is published and the business operates in the relevant sector or geography.
How does BIS / EAR general licence eligibility compare with the EU and UK regimes?
The structural divergence between the US, EU, and UK export-control regimes creates real compliance risk for cross-border exporters. Under EU rules, the EU Dual-Use Regulation provides a set of general export authorisations for defined item-destination combinations; the eligibility test is broadly comparable to the EAR exception test, but the item classifications, control reasons, and restricted-destination lists differ in ways that matter. An item that qualifies for a general export authorisation under the EU rules may still require a specific licence under the EAR, or vice versa.
Under the UK regime, the Export Control Order and the licences issued by the Export Control Joint Unit (ECJU) create a third set of conditions. The UK has broadly retained an item-classification list that tracks the EU-origin structure but has made adjustments since the UK's departure from the EU, and the administrative processes differ. In our practice, clients exporting dual-use goods from a UK base to a destination that also falls within US re-export jurisdiction must manage three sets of conditions simultaneously.
One consistent rule across all three regimes: where two or more regimes apply to the same transaction and they diverge, the stricter prohibition governs the transaction. A general authorisation under the EU regime does not override a US licence requirement. This is the point most often overlooked by in-house teams operating with regime-specific checklists rather than a cross-regime map.
For a direct comparison of general licence eligibility under the EU regime, see our briefing on general licence eligibility under EU dual-use rules. For the OFAC side of the US picture, our companion briefing on general licence eligibility under OFAC covers the financial-sanctions dimension that often runs alongside export-control questions in the same transaction.
When does a business need a specific licence rather than a licence exception?
A specific licence application to BIS is required whenever no licence exception is available and the transaction is not otherwise authorised. Determining whether an exception is available requires the four-part test above; when any element fails, the specific licence route applies.
BIS assesses specific licence applications against a policy framework that weighs national security, foreign policy, non-proliferation, and anti-terrorism considerations against the economic and foreign-policy interest in permitting the transaction. The review process varies in duration depending on the sensitivity of the item and destination; there is no published guarantee of outcome, and BIS may return without action, issue an advisory opinion, or refer the application to interagency review. Applicants who submit incomplete or internally inconsistent applications face longer review periods and a higher rate of return without action.
A common misunderstanding – and one we encounter frequently in advisory work – is that a specific licence application signals wrongdoing. It does not. Many routine dual-use transactions require specific licences simply because the item and destination combination does not fit any exception, and the application process is the normal commercial path. The reputational risk arises only if a business proceeds without required authorisation, not from applying for one.
What should a cross-border business do before relying on a licence exception?
The practical sequence for an exporter assessing whether a general authorisation covers a proposed transaction runs as follows. First, classify the item correctly: obtain or confirm the ECCN through a defensible review of the CCL, and if there is genuine uncertainty, consider a formal determination. Second, identify the applicable exceptions for that ECCN and the destination country group. Third, run a full restricted-party screen: check the Entity List, the Denied Persons List, and the Unverified List, and cross-check against OFAC's SDN List (OFAC's list of Specially Designated Nationals and blocked persons) for financial-sanctions exposure. Fourth, assess the end-use: review the stated purpose, the buyer's profile, and any red-flag indicators. Fifth, document the analysis contemporaneously, including the list versions used and the date of each screen.
Documentation is the element most often deferred until it is too late. In a post-shipment review, BIS will ask for the records that support the exception claim. A business that relied on an exception correctly but has no records to demonstrate it is in a materially weaker position than one that maintained a complete compliance file. The record-keeping obligation is not administrative overhead; it is the evidentiary foundation of a compliance defence.
In a recent matter, a manufacturing business exporting components for commercial telecommunications equipment assumed that a licence exception covered all shipments to a particular market. A routine compliance review identified that one intermediary in the distribution chain had been added to the Entity List months earlier. The exception was unavailable for those shipments. We assessed the exposure, advised on a voluntary self-disclosure, and prepared the submission to BIS. The matter was resolved through the disclosure process without criminal referral.
Related practices
- Licensing and authorisations under the BIS / EAR regime – case-by-case licence applications, exception reviews, and compliance structuring
- General licence eligibility under EU dual-use rules – how the EU general export authorisation structure compares with the EAR