A technology exporter in the United States receives an inquiry from a distributor in a third country. The goods are dual-use. The distributor's end-use certificate looks clean. But the classification analysis has not been done, the Commerce Control List (CCL) entry has not been identified, and no one has asked whether a licence exception (a standing authorisation under the Export Administration Regulations that permits a defined category of exports without a separate application) might already cover the shipment. The deal is scheduled to close in two weeks. Choosing the wrong route – or missing an available route – can mean a delayed shipment, a refused export, or a civil penalty that runs well into the millions.
Choosing between specific and general licences under BIS / EAR starts with one question: does a licence exception already authorise the transaction? If not, the exporter must decide whether to pursue a specific licence (a case-by-case authorisation from BIS to conduct an otherwise controlled export, re-export, or in-country transfer) or re-structure the transaction so that a licence exception applies. As of June 2026, the EAR governs this analysis; BIS administers it through the Commerce Control List and a set of named licence exceptions under the Export Control Reform Act.
This guide walks through the classification step, the licence-exception analysis, the specific-licence option, cross-border considerations, and the risk flags that tell you when to involve export-control counsel.
Step 1: Classify the item against the Commerce Control List
The first step in any BIS / EAR licence analysis is classification: identifying whether the item, technology, or software has an Export Control Classification Number (ECCN – the alphanumeric identifier on the Commerce Control List that determines which controls and licence requirements apply) and, if so, which one.
An item without an ECCN sits in the EAR99 category – the residual category for items subject to the EAR but not listed on the CCL. EAR99 items generally require no licence for most destinations and end-users. They may still require a licence for controlled destinations, embargoed regimes, or parties listed on the Entity List (BIS's list of parties subject to specific licence requirements because of concerns about their conduct). Classification errors at this stage propagate through every subsequent step. In our experience, the single most common starting error is an exporter assuming an item is EAR99 without performing a written classification review.
Classification depends on the item's technical parameters: its function, performance characteristics, and the technology embedded in it. Software and technology for the development, production, or use of a listed item carry their own ECCN, which may differ from the ECCN of the hardware. Where an item is borderline between two ECCNs, BIS offers a formal classification request process – a commodity jurisdiction or classification request – but for most straightforward items an internal written determination, documented and dated, is the foundation of a defensible compliance posture.
Step 2: Determine the reason for control and the applicable licence requirements
Once the ECCN is identified, the next step is to map the reasons for control (the columns on the CCL entry that indicate why the item is controlled – for example, national security, nuclear non-proliferation, anti-terrorism, chemical or biological weapons) to the destination country and end-user.
The EAR uses a Country Chart alongside each ECCN entry. Cross-referencing the reasons for control against the destination country tells you whether a licence is required for that country. If the intersection is blank, no licence is required – subject to the end-user and end-use checks at Step 3. If it is marked, a licence is prima facie required unless a licence exception applies.
This step also determines the scope of available licence exceptions. Some exceptions are keyed to specific reasons for control. Others are tied to the ECCN classification. Knowing why an item is controlled – not just that it is – is therefore material to the route analysis. Compliance counsel working in the BIS / EAR regime routinely find that exporters who skip this step proceed on an incomplete picture of their options.
Step 3: Screen the end-user and end-use against the restricted-party lists
Even where no CCL-based licence requirement applies, a transaction may be prohibited or require a licence if the end-user or end-use is restricted. BIS maintains several lists that interact with the licence analysis: the Entity List, the Denied Persons List (parties debarred from receiving exports), and the Unverified List (parties for whom BIS has been unable to complete end-use verification).
A party on the Entity List typically requires a specific licence, and BIS regularly applies a policy of denial to such applications. A party on the Denied Persons List is a hard stop: no export, re-export, or in-country transfer may proceed. Parties on the Unverified List trigger a red flag that an exporter must resolve before proceeding. In our practice, we regularly advise exporters who discover a list hit mid-transaction and need to assess whether the transaction can continue at all.
The end-use check runs in parallel. The EAR contains general prohibitions – baseline restrictions that apply regardless of whether a licence is technically required – covering prohibited end-uses such as certain weapons programmes, certain launch vehicles, and certain unsafeguarded nuclear facilities. These must be checked even for EAR99 items. Have you checked all of the general prohibitions against your specific transaction facts?
A positive identification on any of these lists or prohibitions should trigger an immediate pause. Proceeding without counsel in these circumstances creates a strict-liability exposure that voluntary self-disclosure does not always cure.
The position above covers the standard case. Your facts – the item classification, the destination, the end-user, the end-use certificate, and the route the goods will travel – change the analysis materially.
For BIS / EAR licensing and authorisation support, see our Licensing & Authorizations service.
Step 4: Can a licence exception cover the transaction?
If the CCL analysis at Step 2 shows a licence requirement, the next question is whether a named licence exception removes that requirement for your specific transaction. Licence exceptions are the regulatory mechanism under the EAR that most exporters should exhaust before applying for a specific licence.
Several exceptions are widely used in cross-border trade. The Technology and Software – Unrestricted exception covers certain published technology and software. The Licence Exception STA (Strategic Trade Authorisation) permits exports to a defined list of lower-risk countries without a specific licence, subject to enhanced record-keeping obligations. The Licence Exception TMP covers temporary exports, such as equipment for trade shows or repair. Each exception has conditions: destination restrictions, end-user eligibility requirements, item-class limitations, and in some cases prior notification to or approval from BIS.
The conditions are not optional. An exporter who uses a licence exception but fails to meet its conditions has exported without a licence – the exception provides no retrospective cover. Record-keeping under the EAR requires the exporter to retain documentation supporting the exception claim, typically for a period that BIS guidance specifies (verify the current period before relying on it). In our cross-border practice, we find that licence-exception compliance is frequently under-documented: the determination is made verbally, the conditions are not checked against the specific facts, and the records that BIS would inspect in an end-use check are incomplete.
A useful test: could you reconstruct, from your records alone, exactly which exception you relied on, which conditions you verified, and how you verified them? If not, the exception claim is vulnerable.
Step 5: When is a specific licence the right route?
A specific licence is the appropriate route when no licence exception covers the transaction and the transaction has legitimate cross-border commercial, research, or humanitarian purposes. BIS reviews specific-licence applications under a policy of either general approval, case-by-case review, or general denial, depending on the ECCN, the reason for control, the destination, and the end-user.
The application is submitted through the SNAP-R system. BIS coordinates with other agencies – including the State Department, the Department of Defense, and the Department of Energy – for items reviewed under inter-agency referral procedures. The review timeline varies. Straightforward commercial applications for lower-risk destinations may resolve in a matter of weeks. Multi-agency referrals for higher-controlled items can take considerably longer. Exporters should not commit contractually to a delivery timeline before a specific licence is in hand.
The application package typically includes a description of the item and its intended use, information on the end-user and the ultimate consignee, a statement of the transaction's commercial purpose, and any supporting documents that speak to the legitimacy of the end-use. BIS may issue a return without action for an incomplete application. It may issue a denial where policy opposes the transaction. It may impose conditions on the licence, including reporting obligations, end-use checks, or shipment-by-shipment approval requirements.
We have acted for exporters where BIS issued a licence with conditions that, on their face, made the commercial transaction unworkable. Understanding what conditions BIS is likely to require – and negotiating the scope of those conditions at the application stage – is one of the less visible but practically important aspects of export-control counsel.
If a transaction has already been flagged, or a filing has been refused or returned, an early review can preserve options that narrow with time. The window to respond to a returned application or to supplement a record on review is real but finite.
How does choosing between specific and general licences under BIS / EAR compare to other regimes?
The BIS / EAR licence structure differs in material ways from equivalent regimes in the United Kingdom, the European Union, and Canada – differences that create practical compliance tensions for exporters who ship to multiple destinations.
Under the UK Export Control Order, administered by the Export Control Joint Unit (ECJU), the equivalent of a licence exception is an Open General Export Licence (OGEL). OGELs are published instruments; an exporter that meets the conditions may ship without a separate application. The structure is broadly analogous to the BIS / EAR licence exception, but the specific conditions differ – a shipment that qualifies under a BIS licence exception may not qualify under a corresponding OGEL, and vice versa. The UK and US controls are not mirrored, and a dual-regime exporter must satisfy both independently.
Under the EU dual-use rules, Union General Export Authorisations (UGEAs) play the same functional role. The EU dual-use regime is administered at the member-state level, meaning that the relevant national authority – and in some cases its procedural requirements – differs by the member state from which the goods are exported. An exporter based in multiple EU jurisdictions may face different procedural requirements for the same item and destination.
Canada's export-control regime, administered by Global Affairs Canada, uses a permit system. The difference in terminology – "permit" rather than "licence" – matters less than the substantive conditions. Our guide on choosing the right licence route under the Canadian regime addresses those conditions in detail.
The critical cross-border point is this: where a transaction touches goods or technology with US-origin content or US-origin technology, the de minimis rule and the foreign direct product rule under the EAR may bring the transaction within BIS jurisdiction even if the exporter is not a US person and the goods never physically transit the United States. Non-US exporters frequently overlook this. The extraterritorial reach of the EAR means that a European manufacturer of a product incorporating US-origin controlled content may need a BIS authorisation in addition to whatever their home-country regime requires. Ignoring the BIS dimension does not eliminate the exposure.
Risk flags: when the standard analysis does not resolve the question
Some transactions present risk indicators that require counsel regardless of how the CCL analysis resolves. Recognising these flags early – and pausing rather than proceeding – is the posture that distinguishes a defensible compliance programme from a reactive one.
The following patterns consistently warrant further review before a shipment proceeds:
- The end-user cannot provide a credible explanation for the intended use of controlled goods.
- The end-user's business profile or location is inconsistent with the stated application.
- The order quantity, configuration, or spare-parts profile is inconsistent with civil commercial use.
- The transaction is structured to route goods through an intermediate jurisdiction in a way that obscures the ultimate destination.
- A payment mechanism, currency, or intermediary is unusual relative to the commercial context.
- The buyer resists standard end-use certification or requests that documentation be omitted or altered.
- A name in the transaction chain is similar to, but not identical with, a name on a restricted-party list.
None of these flags is automatically disqualifying. Each creates an obligation to inquire further. The EAR's red-flag analysis requires that an exporter not proceed when it knows, or has reason to know, that the export will be used for a prohibited purpose. An exporter who identifies a flag and does not investigate it cannot later claim it had no reason to know. The difference between a compliant exporter and an exposed one is often whether the flag was documented and actioned.
A second category of risk arises from changes in the classification of an item after export. Regulatory updates to the CCL can re-classify items that were EAR99 at the time of export. While the change does not retroactively create a violation for past shipments, it does mean that a renewal order or a follow-on transaction must be re-evaluated. Exporters with continuing commercial relationships in multiple jurisdictions should build a re-classification review into their annual compliance cycle.
Common mistakes in the BIS / EAR licence-choice analysis
The most persistent errors in choosing between specific and general licences under BIS / EAR are procedural rather than substantive. The classification step is the most commonly skipped. The second most common error is assuming that an ECCN exists because a licence was granted in a prior transaction – licences are transaction-specific and do not carry forward as precedent for subsequent shipments.
A third error is treating the licence exception as equivalent to a no-action determination. A licence exception authorises the transaction; it does not insulate the exporter from scrutiny if the underlying facts turn out to be other than represented. BIS can pursue enforcement against an exporter who relied on a licence exception but whose records show the conditions were not met, or where the end-use was subsequently found to be prohibited.
There is a common assumption among first-time exporters that specific licences are difficult to obtain and should be treated as a last resort. That assumption is partially correct for higher-risk items and certain destinations, but it understates the utility of the application process for transactions that a commercial exporter can document convincingly. In our experience, a well-prepared, properly documented specific-licence application for a legitimate commercial transaction to a lower-risk destination often receives a timely and positive outcome. The obstacle is usually not BIS's policy; it is the quality of the application package.
Equally, exporters sometimes proceed on the basis that a transaction is "probably EAR99" without performing a written analysis. That posture is not a defence. The EAR places the classification obligation on the exporter; an undocumented assumption creates a strict-liability gap that BIS can exploit in an enforcement context.
Related practices
- BIS / EAR Licensing & Authorizations – end-to-end support for ECCN classification, licence exceptions, and specific-licence applications
- Choosing the right licence route under the Canadian regime – permit analysis and cross-border comparison for exporters shipping to or through Canada
- Cross-border licence choice guide – comparative analysis across BIS / EAR, UK ECJU, EU dual-use, and other regimes