---
title: "Does a license exception mean you skip AES? Usually not"
description: "An EAR license exception is not a no declaration required rule. It does not lift the AES filing threshold, and record keeping applies either way."
canonical: https://exportdocshub.com/blog/ear-license-exception-aes-filing
published: 2026-08-25
updated: 2026-09-02
---

# Does a license exception mean you skip AES? Usually not

> An EAR license exception is not a no declaration required rule. It does not lift the AES filing threshold, and record keeping applies either way.

The single most-searched question that lands on this site right now is a long, oddly-worded one, typed the way people type when they are staring at a form:

> "ear license exception no declaration required aes filing threshold"

Underneath the keyword soup is a real and reasonable question:

**"I found a license exception that covers my shipment. Does that mean I don't have to file?"**

Almost always, no. In fact using a license exception is one of the more reliable ways to *guarantee* you have to file. The word "exception" is doing a lot of damage here, and it is worth ten minutes to fix, because getting it backwards produces exactly the kind of unfiled shipment that draws penalties.

## The short answer

**There is no "no declaration required" rule attached to a License Exception.** The three-letter symbol is a value you report inside the AES filing, not a reason to skip it, so a license exception shipment normally still requires an EEI filing. The $2,500 filing threshold is a separate rule that lives in the Foreign Trade Regulations, it is measured per Schedule B number rather than per shipment, and it is unavailable whenever 15 CFR 758.1(b) fires. And the record-keeping obligation applies either way.

| Question | The answer for a license exception shipment |
|---|---|
| **Does it still need an EEI filing?** | Normally yes. [15 CFR 758.1(g)](https://www.law.cornell.edu/cfr/text/15/758.1) has you report the License Exception symbol as the license authority inside the filing. The only genuine carve-outs are BAG under 758.1(c)(1) and tools of trade under TMP at 758.1(c)(6) |
| **Does the $2,500 filing threshold help?** | It exempts a line valued at $2,500 or less under a single Schedule B number, under FTR 30.37(a) only. It does not apply when any 758.1(b) trigger fires, and License Exception STA requires filing regardless of value under 758.1(b)(4) |
| **Do I have to keep records even when no filing is required?** | Yes. [15 CFR 762.2](https://www.law.cornell.edu/cfr/text/15/762.2) names License Exception provisions among the records that must be kept, including tools of trade under 740.9(a)(3)(i)(B), RPL under 740.10(c), GFT under 740.12, and STA eligibility responses under 740.20(g). [15 CFR 762.6](https://www.law.cornell.edu/cfr/text/15/762.6) sets the period: "All records required to be kept by the EAR must be retained for five years" |

The rest of this post is why each of those three answers is what it is.

## Two different regulations, two different questions

The confusion is structural. There are two separate rulebooks, written by two separate agencies, and they use words that sound like synonyms but are not.

| | License Exception | EEI exemption |
|---|---|---|
| **Rulebook** | EAR, 15 CFR Part 740 | FTR, 15 CFR 30.37 |
| **Agency** | Bureau of Industry and Security | Census Bureau |
| **Question it answers** | Do I need a **license** to send this? | Do I need to **file** this in AES? |
| **What it gets you out of** | Applying to BIS for a license | Filing at all |
| **What you write** | The symbol in the AES record | A NOEEI legend on the documents |

Read the last row twice, because it is the whole post. A license exception is something you **put into** an AES filing. An [FTR exemption](/blog/noeei-exemption-codes) is a reason you don't make one.

So the mental model is not a single gate. It is two gates, in order:

1. **Am I allowed to ship this without a license?** Answered by NLR, or by a license, or by a Part 740 license exception.
2. **Do I have to tell Census about it?** Answered by the FTR: file EEI, or claim a 30.37 exemption and write the legend.

Clearing gate 1 with an exception tells you nothing about gate 2. If anything, it makes gate 2 more likely to bind, for the reason below.

## What a license exception actually is

EAR Part 740 contains a long list of authorizations, each with a **three-letter symbol**. The ones a small exporter is most likely to meet:

| Symbol | Section | Short version |
|---|---|---|
| **LVS** | 740.3 | Shipments of limited value |
| **GBS** | 740.4 | Shipments to Country Group B countries |
| **TMP** | 740.9 | Temporary exports, imports, transfers |
| **RPL** | 740.10 | Servicing and replacement of parts |
| **GOV** | 740.11 | Governments and international organizations |
| **GFT** | 740.12 | Gift parcels and humanitarian donations |
| **TSU** | 740.13 | Technology and software, unrestricted |
| **BAG** | 740.14 | Baggage |
| **AVS** | 740.15 | Aircraft, vessels and spacecraft |
| **ENC** | 740.17 | Encryption commodities and software |
| **STA** | 740.20 | Strategic Trade Authorization |

Here is the part that matters. **You only need a license exception if your item would otherwise need a license.** That means the item is on the Commerce Control List with a real ECCN, and the destination or end use triggers a license requirement, and the exception is what lets you ship anyway.

An item that is EAR99, going somewhere unremarkable, to an ordinary commercial buyer, does not need an exception at all. It ships **NLR**, No License Required. If you are reaching for a Part 740 exception, you have already established that your shipment is [controlled enough to care about](/blog/do-i-need-an-export-license), which is precisely the population Census wants visibility into.

## The filing rule, in the government's own words

15 CFR 758.1(g) sets out what goes in the record. For each item, the filer reports:

- the **license authority**: a license number, a **License Exception symbol**, or the **No License Required (NLR)** designator
- the **ECCN**, where required
- the item description

That single sentence settles the question. The regulation contemplates the license exception symbol as a **field inside the EEI filing**. It is a value you report, not a reason to skip reporting.

So a shipment moving under LVS is filed with **LVS** in the license code field, next to the ECCN that made LVS necessary in the first place.

### The cases where you must file regardless of value

15 CFR 758.1(b) lists the situations requiring EEI **regardless of value**, which means the [$2,500 per Schedule B threshold](/blog/schedule-b-number-vs-hs-code) does not save you. The ones worth memorising:

| Trigger | Citation |
|---|---|
| Exports to Country Group **E:1 or E:2** | 758.1(b)(1) |
| Anything **requiring a license application**, any value, any destination | 758.1(b)(2) |
| **9x515 or "600 series"** items | 758.1(b)(3) |
| **All exports under License Exception STA** | **758.1(b)(4)** |
| Over **$2,500** under a single Schedule B / HTS number | 758.1(b)(5) |
| Transshipments through **Australia, Canada, or the UK** | 758.1(b)(6) |
| **Validated End User** exports | 758.1(b)(7) |
| Any party on the **Unverified List** | 758.1(b)(8) |
| Certain **firearms and ammunition** | 758.1(b)(9) |
| CCL items to **China, Russia, or Venezuela** | 758.1(b)(10) |
| ECCN **3A069** to Country Group D | 758.1(b)(11) |

Row four is the trap this post exists for. **License Exception STA requires an EEI filing regardless of value.** An exporter shipping $900 of STA-eligible hardware, who reasons "it's under $2,500, so 30.37(a) covers me," has just failed to file a shipment the EAR specifically names. The exception did not remove the obligation. It created one.

## The two exceptions that genuinely mean "don't file"

There are real carve-outs, and they are narrow.

- **License Exception BAG** is exempt from EEI filing under **758.1(c)(1)**. This is personal baggage accompanying a traveller.
- **License Exception TMP**, for **tools of trade**, has its own exemption at **758.1(c)(6)**. This is the laptop and the instrument case going out with an engineer and coming home again.

Separately, the Foreign Trade Regulations run their own exemption list at [15 CFR 30.37](/blog/noeei-exemption-codes), and that list names **TMP** (tools of trade), **GFT** (gift parcels and humanitarian aid), **AVS** (aircraft and vessels), **BAG** (baggage), and **GOV** (government shipments) among the shipments that do not require filing.

Notice the shape of that list. Every one of them is a **person or a vehicle carrying something**, not a commercial sale moving on a bill of lading. If your shipment is an invoice to a buyer, none of these is your answer.

> **Do not reason from the exception to the exemption.** The overlap between Part 740 symbols and FTR 30.37 exemptions is a coincidence of subject matter, not a rule. TMP appears in both lists but with different scopes: the FTR exemption is specifically tools of trade, while License Exception TMP under 740.9 is much broader. Check both rule sets separately.

## Where this leaves the $2,500 threshold

The low-value exemption at **FTR 30.37(a)** covers exports where the value shipped "from one USPPI to one ultimate consignee on a single exporting conveyance classified under an individual Schedule B number or HTSUSA commodity classification code is $2,500 or less."

That exemption is genuinely useful, and [it is calculated per code, not per shipment](/blog/schedule-b-number-vs-hs-code). But it sits underneath everything above. If any 758.1(b) trigger fires, the threshold is irrelevant. And by the time you are using a license exception, you have a controlled item on your hands, which makes a 758.1(b) trigger considerably more likely.

The clean way to hold it in your head:

1. Classify the item. ECCN or EAR99? See [the export license walkthrough](/blog/do-i-need-an-export-license).
2. If a license is needed, is there an exception? If yes, note the symbol.
3. **Now ask the filing question separately.** Run 758.1(b). If nothing fires, run [FTR 30.37](/blog/noeei-exemption-codes).
4. Filing? Put the license number, the exception symbol, or NLR in the license authority field, with the ECCN.
5. Not filing? Write the [NOEEI legend](/blog/noeei-exemption-codes) on the invoice, the [SLI](/blog/shippers-letter-of-instruction), and the bill of lading.

Steps 4 and 5 are mutually exclusive. One of them happens, never both, never neither. If you filed, you have an [ITN](/blog/what-is-an-itn-number) to write down. If you did not, you have a legend. A document carrying neither is the thing a carrier will bounce and an auditor will notice.

## The one-line answer

**A license exception is permission to ship. An exemption is permission to stay quiet. They are not the same permission, and the first one usually obliges you to do the second one's paperwork.**

If you take one operational habit from this: when you write a three-letter symbol on a shipment, treat it as a reminder to file, not a reason not to. The symbol has a field waiting for it in AES.

Everything above is reference guidance rather than a classification or licensing determination. Your ECCN, your destination, your parties, and your end use are yours to establish, and a licensed customs broker or export counsel is the right call when the answer is not obvious. What we can do is make sure that once you know the answer, the paperwork carries it consistently: [ExportDocsHub](/) puts the same shipment record behind your commercial invoice, packing list, certificate of origin, and bill of lading, so the ITN or the NOEEI legend lands on every document that needs it rather than the two you remembered.

---

Source: https://exportdocshub.com/blog/ear-license-exception-aes-filing (https://exportdocshub.com)