Export License Types: Which BIS Authorization Fits Your Shipment

BIS processes tens of thousands of export license applications annually (BIS.gov, 2025). Most of those applications never needed to be filed. The wrong authorization type on your electronic export information filing doesn't just slow down your shipment. It creates a compliance exposure that carries penalties up to $374,474 per violation (15 CFR Part 764, effective January 15, 2025). Knowing which export license types apply before you book freight saves weeks and keeps your export compliance program off BIS enforcement radar.

Key Takeaways:

• Over 95% of U.S. commercial exports ship under No License Required (NLR) or EAR99 designations, not individual (export licenses) (BIS.gov, 2025)
• BIS must resolve all license applications within 90 calendar days of registration, but pre-license checks and interagency review can extend that timeline significantly (15 CFR 750.4)
• License exceptions under Part 740 of the export administration regulations cover specific scenarios (LVS, TMP, GOV, STA, ENC), each carrying distinct conditions and reporting requirements
• The BIS Entity List grew by over 170 entries across multiple final rules in 2025 alone (Federal Register, 2025), each addition changing which authorization types remain available for affected transactions
• In February 2025, BIS paused processing of all new export license applications filed after February 5, creating weeks of uncertainty for exporters with pending shipments

NLR and EAR99: When no export license applies

Most U.S. commercial goods fall into EAR99, meaning items subject to the Export Administration Regulations but not listed on the Commerce Control List under a specific ECCN. For EAR99 items going to non-embargoed destinations with no restricted end-users or end-uses, your AES filing code is NLR: No License Required.

That sounds simple enough. The catch is in the determination process. You can't just assume your product qualifies as EAR99 because it feels commercial. Every ECCN on the Commerce Control List needs to be checked against your item's technical specifications. A CNC machine component with positioning accuracy under a certain threshold might look like standard industrial equipment but fall under 2B001. A polymer compound with specific tensile strength properties could land in 1C008. We've seen classification reviews that took 3 weeks of back-and-forth with the engineering team before confirming EAR99 status. Not exactly the "no license needed" quick win people expect.

BIS classification request get answered within 14 calendar days (15 CFR 748.3). If you're unsure about your ECCN and want official confirmation, that's the fastest route. Filing a self-classification without proper technical review? That's where companies get into trouble during BIS audits.

One thing that trips up mid-market exporters: NLR doesn't mean "no restrictions." General Prohibitions 4 through 10 under Part 736 of the EAR still apply. Shipping an EAR99 item to a party on the BIS Entity List requires a license regardless of the classification. BIS added over 80 entities in a single March 2025 action covering China, Iran, Pakistan, South Africa, Taiwan, the UAE. Another 32 went on in September 2025. Your NLR determination from Q1 could be invalid by Q3 if a counterparty shows up on a new list.

Individual export licenses: The full BIS application process

When your ECCN, destination, end-use, or end-user triggers a license requirement under the Commerce Country Chart or Part 744 controls, you need an individual export license from BIS. The SNAP-R application (the Simplified Network Application Process Redesign system) is where you submit all transaction details for interagency review.

On paper, BIS gets 90 calendar days to resolve or refer your application to the President (15 CFR 750.4). In practice, that clock pauses for pre-license checks and additional information requests. Interagency disagreements add further delays. A straightforward application for a controlled item to a Country Group B destination might clear in 30-45 days. An application involving an ECCN with multiple reasons for control going to a Country Group D destination with a new end-user? Budget 60-90 days minimum, and that's without complications.

February 2025 made this worse. BIS put all new applications filed after February 5, 2025 on "hold without action" with no formal guidance or estimated timeline. Applications from December were still "pending" while February submissions sat frozen. Semiconductor equipment orders, defense subcontractor deliveries, contract fulfillment deadlines. All stuck. That pause created real operational damage across the export community.

License review policies vary by entity and destination. The BIS Entity List assigns either a "presumption of denial" or "case-by-case review" to each listed party. Presumption of denial means exactly what it sounds like. You can still apply, but the odds aren't in your favor. The September 2025 Affiliates Rule added another layer: entities 50% or more owned by listed parties now inherit the most restrictive license requirements of their owners (90 Fed. Reg., September 30, 2025).

License exceptions under part 740: The middle ground

Between NLR and a full individual license sits a set of authorization shortcuts called license exceptions. Part 740 of the EAR defines over 20 of these, each with eligibility criteria tied to ECCN, destination, value, end-use, or end-user.

From what we see across export operations, these show up most often:

LVS (Shipments of Limited Value) covers exports where the total value under a single ECCN on one order stays below the dollar threshold listed in that ECCN's entry on the Commerce Control List. Thresholds vary by ECCN. We see this exception get misused constantly. Companies apply it to consolidated orders that should have been treated as separate shipments, or they miss that LVS isn't available for certain Country Group D destinations.

TMP (Temporary Imports, Exports, Reexports, and Transfers) handles items going out temporarily and coming back. Exhibition equipment, tools for on-site repair, items for testing. The 12-month return requirement catches people. For more context, see our guide on China Export Controls: Products Requiring BIS Licenses for Export. Exceed it without extending, and your TMP authorization is retroactively invalid.

STA (Strategic Trade Authorization) allows certain CCL items to go to low-risk destinations without individual licenses. STA requires an end-use statement from the consignee and carries significant recordkeeping obligations. BIS audits STA usage more than most other exceptions. It's a known enforcement focus area.

ENC (encryption Commodities, Software, and Technology) covers encryption items classified under 5A002 and 5D002. Some require classification requests to BIS before the exception becomes available. Mass market encryption products follow a different path under 740.17(b)(3). Getting this wrong means your cybersecurity hardware shipment sits at the port.

GOV (Governments and International Organizations) authorizes exports to U.S. government agencies worldwide and certain foreign governments For 600-series military items that moved from ITAR to EAR, the two primary exception paths are GOV and STA.

Not every exception works for every ECCN-destination combination. The CCL entry for your specific classification will list which exceptions apply. And none of these exceptions override Entity List restrictions, end-use prohibitions, or General Prohibitions 4-10.

How ECCN classification drives your authorization path

Your ECCN classification dictates everything downstream. Get the ECCN wrong and you pick the wrong authorization type, file the wrong code in AES, create a paper trail that BIS enforcement can follow straight back to your export compliance screening process.

Here's how the classification decision tree under the EAR works in practice: check the Commerce Control List for your item's technical parameters. If it matches an ECCN, the CCL entry tells you the reasons for control (National Security, Missile Technology, Nuclear Nonproliferation, among others). Cross-reference those reasons for control against the Commerce Country Chart for your destination An "X" in the corresponding box means a license is required. No "X" means NLR for that reason-destination combination.

Where most mid-market companies stumble is at the technical specification stage. A 5-axis CNC machine might fall under 2B001 or might be below the control threshold and qualify as EAR99. The difference often comes down to a single parameter: positioning accuracy, number of controlled axes, spindle speed. Engineering teams don't always document these parameters in formats that compliance officers can work with, and compliance officers don't always know which specs matter for export control purposes.

Haas Automation paid over $2.5M in combined civil penalties to BIS and OFAC in 2025 for selling CNC machine parts classified as EAR99 to Entity List parties in China and Russia across 32 separate transactions spanning multiple years (BIS.gov, 2025). The parts weren't controlled items. The buyers were. That distinction gets lost on a lot of compliance teams who stop at "our product is EAR99, we're fine." Classification alone doesn't clear a shipment, and export compliance screening against restricted party lists has to happen in parallel.

Picking the right authorization: A decision framework

Start with classification. Always. No shortcut exists here.

Once you have a confirmed ECCN (or EAR99), run the Commerce Country Chart check against your destination. If no license is required and no General Prohibitions apply, file NLR. If a license is required, check whether any Part 740 license exception covers your specific ECCN-destination-end-use combination before filing a SNAP-R application The export licensing process through SNAP-R costs you time (30 to 90+ days), so exhaust exception eligibility first.

Screen every party to the transaction against the BIS Entity List, the Denied Persons List, the Unverified List, and the Military End-User List. Since September 2025, you also need to screen for 50% or more aggregate ownership by listed parties (the Affiliates Rule). That screening requirement applies whether you're shipping under NLR, a license exception, or an individual license. Platforms like Lenzo and Descartes that consolidate export compliance screening across all BIS restricted party lists alongside OFAC and EU lists cut the manual cross-referencing work that buries 4-person compliance teams.

One operational reality most guides skip: authorization types can change mid-transaction. A new Entity List addition between your quote date and ship date invalidates your original NLR determination. A rule change that removes a license exception for certain ECCNs to specific destinations. The semiconductor controls restricting high-bandwidth memory exports, for instance, means re-evaluating transactions already in the pipeline. Export control platforms with regulatory monitoring, like Lenzo, flag affected open orders automatically and prevent the re-screening nightmare.

FAQ

What happens if I use the wrong license code on my AES filing?

AES has built-in validation that catches some mismatches between ECCN, destination, license code. Those mismatches generate fatal errors blocking the filing. But the system doesn't catch everything. Filing NLR for a shipment that actually requires a license constitutes a violation of the EAR, carrying civil penalties up to $374,474 per violation or twice the transaction value (15 CFR Part 764, effective January 15, 2025). BIS enforcement treats incorrect AES filings as evidence of inadequate compliance procedures.

How long does a BIS export license application take to process?

Officially, 90 calendar days from registration (15 CFR 750.4). That clock excludes pre-license checks and applicant-agreed delays. Interagency escalations pause it further. Practical processing times run 30-45 days for straightforward applications and 60-90+ days for transactions involving sensitive destinations or end-users. The February 2025 licensing pause added weeks of delay for applications filed after February 5.

Can a license exception be revoked or restricted after I've already shipped?

License exceptions are self-certifications. By using one, you certify the transaction meets all conditions at the time of export. BIS can and does modify exception availability through rulemaking. If conditions change post-shipment (for example, the end-user gets added to the Entity List), your original authorization remains valid for that completed transaction, but future shipments under the same arrangement require re-evaluation.

Export licensing under the EAR keeps shifting as BIS adds entities, modifies control parameters, adjusts review policies. In 2025 alone, BIS added over 170 entries to the Entity List across multiple actions, paused license processing for weeks, then introduced the 50% ownership Affiliates Rule. Companies that built their export compliance program around static spreadsheet-based classification lookups are running on outdated assumptions. The authorization that cleared your shipment last quarter might not clear it next quarter — and the penalty exposure gap between "we checked" and "we checked correctly" is $374,474 wide.

For more on how HTSUS, HS code, Schedule B, and ECCN differ, see our guide to HTSUS vs ECCN classification.