EEI Filing Explained: Who Files, When, and What Data
- SHIPIT Logistics
- 4 hours ago
- 7 min read
Export teams often discover EEI filing the hard way: a shipment that is packed, labeled, and booked gets held at the last mile because the AES record is missing, late, or rejected. The fix is rarely “just file it”, it’s knowing who is legally responsible, when the filing must be accepted by AES, and what exact data has to match across your commercial invoice, booking, and carrier documents.
This guide explains EEI filing (Electronic Export Information) in practical terms for U.S. exporters, logistics managers, and forwarding partners.
EEI filing, in plain English
EEI filing is the electronic export declaration the U.S. Government requires for certain exports from the United States. The information is submitted through the Automated Export System (AES), part of the Census Bureau’s Foreign Trade regulations.
Two terms matter operationally:
EEI is the data you declare.
AES is the system where you file it.
When AES accepts the filing, it issues an ITN (Internal Transaction Number). Carriers and forwarders commonly require that ITN (or a valid exemption citation) before cargo can load or depart.
For the legal framework, the primary reference is the Census Bureau’s Foreign Trade Regulations (FTR), 15 CFR Part 30 (see the official eCFR text).
Who files EEI (and who is responsible)
A common misconception is that “the freight forwarder files EEI.” Sometimes they do, but responsibility depends on the transaction type.
Key roles you will see in EEI filing
USPPI (U.S. Principal Party in Interest): generally the U.S. seller, manufacturer, or exporter that receives the primary benefit and is typically responsible for filing.
Authorized agent: a party the USPPI authorizes in writing to file EEI on their behalf (often a freight forwarder).
FPPI (Foreign Principal Party in Interest): the foreign buyer in a routed export transaction.
Standard vs routed transactions
In practice, there are two patterns.
Standard (non-routed) export
The U.S. exporter (USPPI) is responsible for the EEI filing, and may either:
File themselves in AES, or
Authorize a forwarder/agent to file
Routed export transaction
A routed export transaction is where the foreign buyer (FPPI) authorizes a U.S. agent or forwarder to arrange export shipping.
In many routed scenarios, the agent files the EEI. However, the USPPI still has obligations, especially to provide accurate data elements that only the USPPI controls (like their identity, commodity details, values, and licensing inputs). If your commercial team uses “routed” language in contracts, treat it as an operational trigger to clarify the filing workflow before the first shipment.
Quick responsibility table (operational view)
Scenario | Who typically files in AES | What the exporter (USPPI) must still provide | Common failure mode |
Standard export (USPPI controls shipping) | USPPI or USPPI’s authorized agent | Complete commodity, valuation, licensing, party data | Filing starts too late, missing Schedule B/ECCN |
Routed export (FPPI controls shipping via U.S. agent) | Authorized U.S. agent/forwarder | USPPI data set required by FTR, plus license determinations when applicable | USPPI withholds data, agent guesses, AES rejects |
Courier / small parcel workflows | USPPI or courier process, depending on program | Correct classification and value logic | “It’s FedEx/UPS so it’s covered”, then cargo gets held |
When EEI filing is required (and when it is not)
Whether EEI is required is not based on “international shipment” alone. It depends on value, licensing, destination, and other control triggers.
Common triggers that require EEI
EEI is commonly required when:
The value exceeds the reporting threshold for a Schedule B/HS line item, and/or
An export license is required, and/or
The shipment involves controlled items, restricted parties, or certain special movements
Because thresholds and rule details can depend on the exact fact pattern, many exporters operationalize this as a simple internal rule:
If you do not have a clear documented exemption, assume EEI might be required and validate early.
For official rule language and definitions, start with 15 CFR Part 30.
Common “NOEEI” situations exporters use
If EEI is not required, you typically must provide a NOEEI citation (the specific exemption reference) to the carrier/forwarder instead of an ITN.
Important: “NOEEI” does not mean “no compliance,” it means you are relying on a specific exemption and should be able to support it.
EEI filing deadlines (what “when” really means)
From an operations perspective, your deadline is not when you click submit, it is when AES accepts the filing and you have the ITN (or you have a correct NOEEI citation). If AES rejects the filing, you are effectively not filed.
Mode-based timing (how exporters should plan)
Legal filing timelines vary by mode and shipment type. Rather than memorizing edge cases, most shipping teams should build a repeatable internal cutoff:
Air: earlier, because airline tender cutoffs and security screening can be same-day.
Ocean: earlier than you think, because documentation cutoffs often occur days before vessel departure.
Truck / cross-border: filing must be completed before export, and driver and carrier paperwork must match.
A practical internal rule that prevents most misses is:
Start EEI data validation when the commercial invoice is issued (or when the shipment becomes “real”), not when the warehouse is ready.
If you want a deeper timeline-and-error guide, SHIPIT has a separate post that goes into the ITN workflow and common rejects: AES filing made simple: ITN, timeline, and common errors.
What data is required for EEI filing (the “EEI-ready packet”)
Most rejected or delayed EEI filings trace back to missing or inconsistent data. The best prevention is to standardize an EEI-ready packet that your internal team, forwarder, or broker can rely on.
The core data categories
You typically need:
Parties and addresses: USPPI (and EIN), consignee, intermediate consignee if applicable
Shipment details: origin state, port of export, mode of transport, export date, conveyance info depending on mode
Commodity line data: description, quantity/unit, weight, value, and classification
Classification and controls: Schedule B and/or HTS, ECCN (if applicable), license type/license number or license exception
Transaction flags: routed vs non-routed, related party indicator, hazard indicators where applicable
To stay aligned with the official definitions and required elements, reference the Census Bureau’s AES resources via Census Foreign Trade: AES.
A practical checklist table you can copy into your SOP
Data element | Who should own it internally | Why it matters in AES | Best practice |
USPPI legal name + EIN | Finance/compliance | Identifies the exporter of record in AES | Lock this as a “master data” field, do not retype each time |
Consignee name + address | Customer service / order ops | Party mismatch is a common reject cause | Match commercial docs and booking exactly |
Schedule B (or appropriate classification) | Trade compliance | Determines reporting logic and statistics | Maintain a controlled item master, not spreadsheet guesses |
ECCN / license determination (if applicable) | Trade compliance | Controls whether licensing fields are required | Document your determination and keep evidence |
Value per line item | Finance / order ops | Threshold logic and reporting accuracy | Use consistent valuation rules across invoice and EEI |
Weight and units | Warehouse | AES expects coherence with commodity details | Validate UOM conversions before filing |
Routed flag and authorization | Legal / logistics | Changes the filing workflow responsibilities | Confirm in writing who files and who provides data |
Who can file on your behalf (and what you must authorize)
If a freight forwarder or logistics provider files EEI as your authorized agent, you should expect:
A written authorization (often via Power of Attorney or separate authorization language)
A defined responsibility split (who supplies commodity data, who validates licensing, who submits)
A clear handoff milestone for “ITN issued” (or NOEEI citation confirmed)
This matters most when you are running fast-moving exports, multi-warehouse shipping, or multiple modes (air plus ocean) because one missed filing can blow a flight, a vessel cutoff, or a truck appointment.
Common EEI filing errors that cause holds
EEI problems tend to be boring, but expensive. The repeat offenders:
Party mismatches: the USPPI/consignee names and addresses differ across invoice, booking, and AES.
Incorrect classification: wrong Schedule B, or missing ECCN/licensing logic.
Value logic errors: value keyed at a header level but required per line item, or inconsistent currency handling.
Late filing: the filing is started after warehouse tender or after the carrier’s documentation cutoff.
Routed confusion: FPPI-controlled moves where the USPPI does not provide the required data set, so the agent guesses.
How EEI filing connects to real-world logistics execution
EEI filing is not just “paperwork,” it is a gating event that affects:
Air freight tendering (missed acceptance can mean missed uplift)
Ocean documentation cutoffs (late compliance data can roll a container)
Drayage and warehouse scheduling (a hold can burn free time and create detention/demurrage exposure)
That’s why many shippers prefer a single operating team to coordinate export forwarding, documentation, and the physical moves (pickup, warehousing, and tender).
Practical operating model: make EEI predictable
If you manage exports at scale (or you are trying to scale), build your process around these controls:
Define an internal “compliance data cutoff”
Set a time-based cutoff that is earlier than your physical cutoff. Example mindset: “No cargo moves until EEI is cleared (ITN or NOEEI).” This prevents last-minute escalations that burn premium freight.
Use a single source of truth for classification and party master data
Most EEI rejections come from typing, not trade policy. Master data discipline beats heroics.
Treat routed export transactions as a special lane type
For routed moves, write down:
Who files
What data the USPPI provides
Who performs license determination
Where the ITN is stored and how it is transmitted to the carrier
FAQ
What is EEI filing? EEI filing is the electronic export declaration submitted through AES for certain U.S. exports, and it results in an ITN when accepted.
Who is responsible for EEI filing? Typically the USPPI is responsible, but a freight forwarder or other party can file as an authorized agent, and routed transactions change the workflow.
When should we file EEI to avoid delays? File early enough that AES acceptance (ITN) is secured before carrier documentation and tender cutoffs, not after the cargo is packed.
What data do we need for EEI filing? Party details (including USPPI EIN), commodity line details, classification (Schedule B and sometimes ECCN), values, weights, routing/mode details, and license information when applicable.
Is EEI filing required for every export shipment? No, some exports qualify for NOEEI exemptions, but you still must use the correct exemption citation and retain support.
If you want help building an EEI-ready process that aligns documentation, export forwarding, and pickup or drayage to hit cutoffs consistently, contact SHIPIT Logistics.
