An exporter preparing to ship controlled technology to an overseas customer runs the item through its classification tool. The Export Control Classification Number (ECCN – the alphanumeric code assigned to items under the US Commerce Control List) triggers a licence requirement for the destination. No licence exception applies. The shipment cannot move without a specific licence from the Bureau of Industry and Security. What happens next, and how long will it take?
A specific licence (a case-by-case authorisation from BIS permitting an otherwise controlled export, re-export, or in-country transfer) is the principal route when no licence exception covers the transaction. The application is submitted through BIS's online SNAP-R system, reviewed against the Export Administration Regulations, and decided by BIS – often in consultation with other agencies. As of June 2026, processing times and approval outcomes vary considerably by item, destination, and end-use.
This guide walks through the application process step by step, identifies the points where applications fail, and explains how the BIS/EAR regime compares with the ECJU and OFSI/OFAC licensing routes that cross-border businesses often encounter at the same time.
Step 1: Classify your item and confirm that a licence is required
Before any application begins, you must know what you are exporting and whether a licence exception already covers the transaction. Every item subject to the EAR carries a classification: either a specific ECCN on the Commerce Control List, or the catch-all designation EAR99 for items not specifically enumerated. Even EAR99 items can require a licence to certain destinations or for certain end-uses, so classification alone does not end the analysis.
The licence-requirement determination asks four questions: what is the ECCN or EAR99 status; what is the destination country and its country chart column; who is the end-user; and what is the end-use. BIS maintains the Entity List, the Unverified List, and the Denied Persons List – each carrying different consequences. A match on the Entity List against a listed entity typically requires a licence, and BIS policy for those entries is often a presumption of denial. Confirm each list check before drafting the application.
In our practice, exporters most often miscalculate at this stage by relying on a supplier's classification without independently verifying it, or by failing to re-classify when an item is modified. A classification error discovered after shipment produces a far harder problem than one caught before the application is filed.
Step 2: Determine the correct application route and gather the required documentation
Once you have confirmed that a specific licence is required, the application route is SNAP-R – BIS's Simplified Network Application Process Redesign portal. Every application involves the same core elements, but the supporting documentation varies by commodity, destination, and end-use classification.
The core application requires:
- A full description of the item, including its ECCN and technical parameters.
- The identity and address of all parties: exporter, intermediate consignee, ultimate consignee, and end-user.
- A precise description of the intended end-use and the business rationale for the transaction.
- Supporting statements or certifications from the foreign end-user – typically an end-user statement or, for higher-risk items, a more detailed letter of assurance.
- Any relevant contract documents, technical specifications, or prior-approval correspondence.
For items with military, weapons-of-mass-destruction, or advanced-technology profiles, BIS will frequently request additional technical information or refer the application to the Departments of State, Defense, Energy, or Commerce's own technical advisory committees. Building that consultation time into your planning is not optional – it is a practical necessity.
In our cross-border practice, we regularly advise clients that the quality of the end-use documentation submitted at the outset directly shapes both the speed of the review and its outcome. A vague or incomplete end-user statement is the single most reliable predictor of a request for additional information, which can add many weeks to the process.
What are the most common grounds for refusal – and how do you address them?
BIS evaluates each application against a set of review policy factors set out in the EAR, including whether the transaction contributes to proliferation risk, whether the end-user has a credible compliance history, and whether an approval would be inconsistent with US foreign policy. Applications are subject to a multi-agency review process, and any reviewing agency can flag concerns.
The most frequent grounds for a difficult outcome include:
- End-user credibility concerns: where the ultimate consignee or end-user cannot be verified through standard channels, or appears on BIS's Unverified List, a red-flag analysis is mandatory and the application is likely to face heightened scrutiny.
- Destination or end-use profile: items controlled for national security, chemical/biological/radiological/nuclear, or missile-technology reasons face presumptions of denial to certain destinations.
- Incomplete or inconsistent documentation: a mismatch between the end-use statement and the technical specification, or between the stated consignee and the shipping records, will trigger a request for additional information at minimum.
- Transaction structure complexity: multi-party re-export chains, intermediaries in third countries, or split shipments all increase review time and the risk that one link in the chain carries a problem BIS will identify.
Where BIS issues a denial, an applicant may request reconsideration and, in some cases, proceed to an administrative appeal. The reconsideration process involves submitting new information or argument that addresses the basis for denial. In our experience, reconsideration requests that simply restate the original application rarely succeed; those that directly address the agency's stated concern and supply corroborating documentation fare markedly better.
Step 3: Submit through SNAP-R and manage the review process
The SNAP-R submission itself is largely mechanical once documentation is assembled, but several procedural points affect the review timetable. BIS assigns the application to a licensing officer and a commodity classification specialist. The application is then distributed to other agencies for inter-agency consultation when the item type or destination requires it.
The position above covers the standard case. Your facts – the counterparty, the goods, the route, and the regime in play – change the analysis significantly. For an assessment of how the review process applies to your specific transaction, contact Calder & Vance at info@caldervance.com.
During the review period, the licensing officer may issue a request for additional information (sometimes called an RFI). Responding promptly and completely to an RFI is important. An incomplete response restarts the review clock. A precise, well-documented response aligned exactly with the question asked tends to move the file forward with minimal further delay.
BIS's review period varies considerably. For straightforward commercial items destined for allied-country end-users with clean records, approval can come relatively quickly. For items touching strategic technologies – advanced semiconductors, certain machine tools, materials with dual-use potential – multi-agency consultations can extend the process materially. Plan accordingly when the transaction has a commercial deadline.
How does BIS / EAR differ from the UK ECJU and EU dual-use licensing routes?
Businesses operating across multiple jurisdictions frequently need to manage a BIS application alongside a UK ECJU or EU dual-use export authorisation request for the same or a related transaction. The regimes share a family resemblance but differ in ways that matter operationally.
Under the UK Export Control Order, the ECJU issues Standard Individual Export Licences and Open General Export Licences on broadly similar principles to BIS: item classification, end-user assessment, and a government-to-government review where the destination is sensitive. However, the UK regime uses its own rating system for items (UK strategic export control lists, aligned but not identical to the Commerce Control List) and the ECJU's review period and staffing differ from BIS. A transaction cleared by BIS is not automatically cleared by ECJU, and vice versa.
The EU dual-use regulation establishes a similar framework across EU member states, with national competent authorities handling applications. The EU regime explicitly requires a catch-all assessment for items that may not be formally listed but are destined for end-uses related to weapons proliferation. Under the EU approach, even an EAR99 item may require a member state authorisation if the exporter knows or suspects a problematic end-use. That is a materially broader trigger than BIS's equivalent provision in the EAR.
Extraterritoriality is a further dimension that distinguishes the BIS/EAR from both the ECJU and EU regimes. The EAR applies to the re-export of US-origin items and to items incorporating more than a de minimis level of US-controlled content, regardless of where the re-export occurs. A European company re-exporting US-origin technology to a third country may require a BIS licence even if its own national export authority has no objection. We regularly advise on exactly this scenario, where a client's local clearance is necessary but not sufficient.
One practical consequence: where the same transaction touches both BIS and ECJU or EU jurisdiction, it is generally advisable to begin the BIS application first if BIS is the more demanding regime for the specific item and destination. An ECJU or EU approval obtained before BIS review is complete creates no legal problem, but the sequencing affects commercial planning and the allocation of counsel time.
If a transaction has already been flagged by BIS, or a prior application has been refused, early specialist review preserves options that narrow with delay. For a confidential review of your position, contact us at info@caldervance.com.
Step 4: Post-approval obligations and ongoing compliance
Approval of a specific licence is not the end of the compliance obligation. BIS licences carry conditions – restrictions on re-export, requirements to notify BIS of changes to end-user or end-use, record-keeping obligations, and sometimes requirements to allow BIS to conduct a post-shipment verification at the foreign end-user's premises.
Record-keeping under the EAR is a specific and enforceable obligation. Exporters must retain the records that document the licence application, the approval, the associated export documents, and any related correspondence for a defined period. Those records must be produced on BIS request. An exporter that cannot produce complete records for a licensed transaction is exposed to enforcement action independently of whether the underlying shipment was itself compliant.
Post-shipment verifications are a BIS tool used selectively, particularly for higher-risk items and destinations. Where BIS or a cooperating foreign authority conducts a verification and cannot confirm that the item arrived and is being used as stated, the end-user may be added to the Unverified List and future licence applications involving that end-user become significantly harder. That risk should inform the due-diligence steps taken before submission, not after.
Licence conditions are not uniform. Read each approved licence carefully. In a recent matter, a trading company in the industrial-equipment sector received a BIS licence with a condition it had not anticipated: a prohibition on sub-licensing the technology without separate BIS approval. The condition was clearly stated in the licence. The company had not read it. We assisted in identifying the issue before a shipment occurred that would have violated the licence terms. The lesson is straightforward: the approved licence is a legal instrument, and its conditions bind the licensee.
Common myths and risk flags: what compliance teams get wrong
A widely held assumption among compliance teams – particularly those primarily familiar with financial sanctions – is that if no counterparty appears on a list, export-control issues do not arise. That assumption is incorrect. The EAR creates obligations tied to the item and the end-use, not only to the identity of the parties. An unlisted buyer acquiring a controlled item for an end-use that BIS prohibits requires a licence regardless of its screening-clean status.
A second common error is treating licence exceptions as automatic rather than as tested eligibility criteria. Licence exceptions under the EAR – provisions such as Technology and Software Unrestricted, License Exception ENC, or Governments and International Organisations – each carry conditions that must be affirmatively met and documented. Applying an exception without documenting the basis for it is itself a recordable compliance failure.
A third pattern we encounter regularly: exporters assume that because a transaction is below the value threshold where BIS enforcement historically concentrates, they are in a low-risk category. BIS enforcement does not have an explicit monetary floor in the EAR; the civil and criminal exposure for an unlicensed export of a controlled item exists irrespective of transaction size. The practical risk may be lower for small transactions, but the legal obligation is the same.
Specific risk flags that should always prompt specialist review:
- Any end-user on the Entity List, Unverified List, or Denied Persons List, even where the item seems clearly non-strategic.
- A transaction where the buyer requests removal of logos or markings from equipment – a recognised red flag for re-export to a restricted destination.
- Shipments routed through third countries where the commercial justification for the routing is unclear.
- Requests to split a shipment across multiple invoices in a way that brings each below a classification or reporting threshold.
- Payment structures that divert funds through unrelated third parties.
Each of these patterns surfaces regularly in BIS enforcement actions. Each should trigger an escalation before the transaction proceeds. Compliance counsel who have worked through BIS enforcement matters can map these patterns to the relevant risk-detection framework and advise on whether a voluntary self-disclosure (VSD – a proactive report of an apparent violation to BIS) is appropriate.
Related practices
- Frozen account management under BIS / EAR – specialist assistance where assets or accounts have been frozen pending licence review or enforcement.
- Specific licence applications under BIS / EAR: advanced issues – deeper treatment of multi-party re-export chains, deemed exports, and end-use controls.
- Specific licence applications under the Canadian export-control regime – a practical guide for exporters managing parallel BIS and Canadian authorisation requirements.