A freight-forwarder in Singapore is asked to clear a shipment of items classified under the US Export Administration Regulations (EAR – the rules administered by the Bureau of Industry and Security, BIS, governing the export, re-export, and in-country transfer of dual-use and certain commercial goods). The shipper's compliance team believes a general licence covers the transaction. Three weeks later, a BIS licence-return letter arrives. The general licence conditions were misread; the end-user was ineligible; no record of the internal eligibility determination was kept. The shipment is held. This outcome is avoidable.
General licence eligibility under BIS / EAR guide 2 turns on three sequential questions: Does the item's Export Control Classification Number (ECCN) fall within the general licence's scope? Does the destination, end-user, and end-use satisfy every condition? And have the procedural requirements – including any recordkeeping and notification obligations – been met? All three must be answered affirmatively before a shipment proceeds without a specific authorisation.
This guide walks through the eligibility test step by step, compares the BIS position with the approach taken under other major regimes, maps the most common mistakes, and identifies when specialist export-control counsel should be engaged before rather than after the fact.
What governing authority administers general licences under the EAR, and what is their legal basis?
BIS administers the EAR under the authority of the Export Control Reform Act (ECRA), and it is ECRA – not the older Export Administration Act – that provides the current statutory foundation for US dual-use export controls. Within that authority, BIS publishes licence exceptions (the US equivalent of what other regimes call general licences – standing authorisations permitting defined categories of exports without a separate case-by-case licence application) directly in the EAR.
The terminology matters. Under the EAR, the term "general licence" is a legacy expression; the operative concept today is "licence exception". Each exception is narrowly scoped: it applies to specific ECCNs, specific destinations grouped into country-groupings (A through E), and specific end-uses and end-users. Relying on a licence exception therefore requires classifying the item first, confirming the country group, and verifying the end-user against applicable lists and prohibited-party conditions.
The Commerce Control List (CCL – the BIS schedule that classifies dual-use items by ECCN) is the starting point. Every item subject to the EAR has an ECCN or falls under the EAR99 residual classification (covering items not specifically controlled under any ECCN). EAR99 items generally have wider access to licence exceptions, but they are not unconditionally free of control: end-user and end-use restrictions still apply, and the general prohibitions in the EAR can still bite.
In our cross-border practice, the single most expensive compliance error we see is a firm that stops at "the item is EAR99" and proceeds without checking end-user prohibitions and licence-exception conditions. That shortcut is where enforcement exposure begins.
Related practices
- Frozen account management under BIS / EAR – legal support for accounts and property blocked under US export-control enforcement.
- General licence eligibility under Canadian sanctions – step-by-step guide to GAC authorisations and conditions.
Step 1 – Classify the item and identify the applicable licence exceptions
Accurate ECCN classification is the foundation of every general licence eligibility determination. Without it, no other step in the process is reliable. Classification requires examining the technical parameters of the item against the CCL entries across the ten product categories (from nuclear-related technology at category 0 through to miscellaneous items at category 9).
BIS offers a self-classification methodology, and exporters may also submit a Classification Request for a binding agency determination. For items near a control threshold – a chip at the edge of a performance specification, or software with both commercial and potentially controlled characteristics – a Classification Request is the conservative route. The determination will be on record and can be relied upon in the event of an enforcement enquiry.
Once an ECCN is confirmed, the exporter identifies which reasons for control apply (national security, regional stability, nuclear non-proliferation, anti-terrorism, and others). Each reason for control maps to specific licence exceptions. Not every exception is available for every reason. A common error is assuming that a broadly-named exception covers all controlled items; in practice, eligibility narrows significantly once the reasons for control are read alongside the exception conditions.
Does your ECCN appear on the CCL with multiple reasons for control? If so, each reason must be assessed separately. A single disqualifying reason removes the exception even if all other reasons would permit it.
Step 2 – Confirm the destination, end-user, and end-use conditions
BIS groups countries into groupings (A through E) that determine which licence exceptions are available for a given ECCN and reason for control. Country Group E contains destinations subject to the most restrictive treatment; exports to those destinations under a licence exception are generally unavailable for controlled items. The applicable grouping for the intended destination must be verified before relying on any exception.
Beyond country grouping, the end-user eligibility check is often more consequential in practice. The EAR prohibits exports – whether under a licence exception or otherwise – to parties on the Entity List (a BIS list of persons and organisations subject to specific licensing requirements), the Denied Persons List (DPL, covering persons whose export privileges have been revoked), and OFAC's SDN List (OFAC's list of Specially Designated Nationals and blocked persons, which runs in parallel and can block a transaction entirely under OFAC authority rather than BIS authority). Screening against all three lists – and against OFAC's list of persons subject to secondary-sanctions risk – is a precondition of any eligibility determination, not an afterthought.
End-use conditions add a third layer. Many licence exceptions contain prohibited-end-use clauses: the item may not be used in the development of weapons of mass destruction, in certain nuclear activities, or for surveillance of civilian populations, among other prohibitions. If an end-use certificate or an end-user statement is required under the applicable exception, that document must be obtained before shipment and retained on record.
In a recent matter, a technology exporter in a European country sought to use a specific licence exception for a transaction involving a buyer in a permitted country group. The buyer was clean on the Entity List and the DPL. However, a beneficial owner of the buyer appeared on the SDN List. The exception was unavailable because of the OFAC-side prohibition. We advised on the applicable OFAC general licence available for the specific category of person involved, a separate assessment entirely. The matter resolved, but only after the shipment had been held and re-screened. The lesson: BIS and OFAC screening are complementary, not alternative.
The position above covers a standard eligibility check. Your specific facts – the item's parameters, the buyer's ownership structure, the ultimate end-use, and the delivery route – can each change the analysis in ways that are not apparent from the exception text alone.
For a confidential review of your export transaction and its eligibility position, contact Calder & Vance at info@caldervance.com.
Step 3 – Meet the procedural and recordkeeping requirements
Satisfying the substantive eligibility conditions is necessary but not sufficient. Licence exceptions under the EAR carry procedural obligations – and failure to comply with those obligations can convert an otherwise lawful transaction into a violation even when the underlying goods and parties were eligible.
The EAR's recordkeeping requirements apply to exporters relying on licence exceptions just as they apply to holders of specific licences. The required retention period is five years from the date of export, re-export, or in-country transfer. Records that must be kept include the commercial invoice, the classification determination, the end-user statement (where required), shipping documentation, and the internal eligibility determination itself. An internal eligibility determination – a contemporaneous, written record setting out why the exporter concluded a particular exception applied – is the document BIS will look for first in an enforcement enquiry.
Some exceptions require prior notifications to BIS, or impose reporting conditions. Others include a per-shipment value cap or a quantity limit. Exporters that treat exceptions as unconditional standing permissions routinely miss these limits. The CCL entry and the applicable exception text must be read together, and any condition noted in either must be satisfied.
Procedural compliance is the element most often sacrificed under time pressure. A deal-team eager to close a transaction may proceed on a verbal conclusion that an exception applies, without producing the written eligibility analysis that would survive scrutiny. We regularly advise clients to institutionalise this step as a mandatory checklist item – not a post-export rationalisation.
How does the BIS / EAR general licence position compare with the approach under other regimes?
The BIS licence-exception model is substantively different from the general-licence architectures used by OFSI in the United Kingdom and the EU Council in its financial-sanctions regulations, and from the permit structures used by Canada's Global Affairs Canada (GAC) and Australia's DFAT. Understanding the differences protects a business that operates across jurisdictions from assuming that a determination made under one regime carries over to another.
Under OFSI, a general licence (the UK term, directly equivalent to the US licence exception) is published by His Majesty's Treasury and permits a specific class of otherwise prohibited financial activity for a defined period and under stated conditions. OFSI general licences are frequently time-limited and require monitoring for expiry or amendment. A UK-nexus party relying on an OFSI general licence must track the licence's duration actively; there is no automatic renewal. Under the EAR, licence exceptions are embedded in the regulation itself and do not expire as individual instruments – though they can be amended or rescinded by BIS rulemaking.
Under the EU dual-use regulation, general authorisations are published at EU level and may be supplemented by member-state authorisations. The EU regime requires exporters to register before first use of certain general authorisations, a procedural step with no direct BIS equivalent for most licence exceptions. Where the EU and the US both control an item, a dual-jurisdiction eligibility check is required before shipment.
For Singapore-based exporters, the Strategic Goods (Control) Act imposes its own permit requirements for controlled items. Japan's Foreign Exchange and Foreign Trade Act operates a separate classification and permit regime. The UAE's export-control regime has been developing steadily. In each case, the US EAR's extraterritorial reach – through the de minimis rule (the EAR provision that subjects foreign-made items to US jurisdiction when US-origin content reaches the applicable de minimis threshold) and the foreign direct product rule (the FDPR, which subjects foreign-made items produced using certain US technology or software to the EAR) – can mean that an item is subject to BIS authority even when it has left the United States and is being handled by a non-US party. A licence-exception analysis under the EAR may therefore be required by a Singapore, Japanese, or UAE exporter who has no US footprint but whose product is caught by FDPR.
The cross-border implication is direct. A business that has confirmed exception eligibility under the EAR may still need to obtain an authorisation under the applicable country regime before the item can be shipped. Stricter prohibition governs: where two regimes both apply and one imposes a condition the other does not, both sets of conditions must be met.
If a transaction has already been flagged, or a filing has been refused, early review can preserve options that narrow with time. Contact us at info@caldervance.com to discuss a cross-regime eligibility assessment.
What are the most significant risk flags and common pitfalls in BIS / EAR eligibility?
Risk flags in general licence eligibility determinations cluster around four recurring patterns. Each has produced enforcement action under the EAR, and each is detectable at the pre-shipment stage with the right process.
First: classification by analogy. A product team classifies a new item as EAR99 because it resembles a previously classified product. If the new item has higher performance parameters, or incorporates technology added since the last classification, the EAR99 determination may be wrong. Classification must track the item as it is at the date of export, not as it was when last assessed.
Second: country-group assumptions for multi-hop transactions. A transaction routed through an intermediary jurisdiction can change the applicable country group. The relevant test is the ultimate destination, not the first port of call. Where goods are transshipped, the exporter must know and verify the final destination. The EAR's re-export obligations extend US jurisdiction to the second and subsequent legs of a supply chain.
Third: stale screening. An end-user cleared six months ago may have been added to the Entity List or the SDN List since. BIS and OFAC update their lists without prior notice. Screening at the time of classification or contract negotiation is not a substitute for screening at the time of shipment. In our experience, a screening date and a shipment date that do not coincide are a common source of avoidable exposure.
Fourth: the ECCN / licence-exception mismatch. An exporter identifies the correct ECCN but then selects a licence exception that does not cover the item's reasons for control. The exception may cover national-security controls but not anti-terrorism controls; the item may be controlled for both. Only exceptions that cover all applicable reasons for control satisfy the EAR.
The myth that EAR99 classification removes all BIS risk is the most pervasive misconception we encounter. EAR99 items remain subject to the EAR's general prohibitions, end-user restrictions, and OFAC overlay. Clearing an item as EAR99 does not mean the transaction is unconditionally authorised. Has your compliance programme been calibrated to check EAR99 shipments for end-user and end-use conditions, not just for ECCN-based controls?
When should export-control counsel be engaged, and what does that engagement involve?
Counsel should be engaged before shipment whenever any one of the following is present: a novel classification question; a destination or end-user that has appeared in enforcement or list-screening results; a product that sits near a control threshold; a multi-hop routing; or any transaction involving technology subject to FDPR.
Counsel should also be engaged without delay if BIS has issued a licence-return letter, a transaction hold, a request for additional information, or if an apparent violation has been identified internally. An apparent violation is a transaction that, on review, may not have met all EAR conditions – and the decision about whether to make a voluntary self-disclosure (VSD – a proactive report of an apparent violation to BIS or OFAC, typically treated as a mitigating factor in penalty proceedings) is one of the most consequential decisions an exporter can face. The window for a well-structured VSD is short; acting after BIS has initiated contact removes much of the mitigation value.
At Calder & Vance, we assist exporters by classifying the item against the CCL, confirming licence requirements and exceptions, and designing end-use controls appropriate to the risk profile of the transaction and counterparty. Where an apparent violation is identified, we scope the issue, advise on VSD strategy, and prepare the penalty defence. We have acted for manufacturers, freight forwarders, and technology companies at the pre-shipment eligibility stage and in post-shipment enforcement enquiries.
For a confidential review of a licence-exception eligibility question or a potential EAR enforcement matter, contact Calder & Vance at info@caldervance.com.