AES Shipper: Who Is Responsible for Filing and Accuracy?

The short answer is simple, but the operating reality is not: AES shipper is not a formal legal title by itself. In U.S. export compliance, responsibility is tied to defined parties such as the USPPI, the FPPI in routed transactions, and any authorized agent that files Electronic Export Information in AES.

That distinction matters because using a freight forwarder, courier, broker, warehouse, or overseas buyer's nominated agent does not automatically transfer every accuracy obligation away from the U.S. seller or exporter. The party filing must transmit accurate data, but the party that owns the commercial and product facts must provide correct information in the first place.

For exporters, BCOs, logistics managers, shipping supervisors, and forwarders, the goal is not just to ask who files. The better question is: who owns each data element, who verifies it, who submits it, and who corrects it when operations change?

What people usually mean by AES shipper

AES is the Automated Export System used to transmit Electronic Export Information, known as EEI, to the U.S. government. The filing generates an Internal Transaction Number, or ITN, when accepted. Carriers and forwarders use that ITN, or a valid NOEEI exemption citation when EEI is not required, to move export cargo.

The U.S. Census Bureau AES program and the Foreign Trade Regulations in 15 CFR Part 30 define the core filing framework. In everyday shipping language, however, teams often use AES shipper to mean different things.

Term	What it means in practice	Why it matters
AES	The electronic system used to file EEI	AES is the platform, not the responsible party
EEI	The export shipment data transmitted through AES	This is the data that must be accurate and timely
ITN	The acceptance number returned after AES filing	Carriers need it before export when EEI is required
USPPI	U.S. Principal Party in Interest	Usually the U.S. party receiving the primary benefit of the export transaction
FPPI	Foreign Principal Party in Interest	The foreign buyer or party abroad, especially important in routed exports
Authorized agent	A party authorized to file EEI, often a forwarder	The agent can file, but needs correct data and written authorization
Routed export transaction	A transaction where the FPPI controls export movement through a U.S. agent	Responsibility and data access must be defined carefully

A commercial invoice, bill of lading, air waybill, shipper's letter of instruction, and AES record may all use similar words for shipper, exporter, consignee, and agent. They are not always the same party. That is why export teams should identify the USPPI and filing party before cargo is picked up.

For a broader overview of EEI triggers and data requirements, see SHIPIT's guide to EEI filing explained.

Who is responsible for filing and accuracy?

Responsibility depends on whether the shipment is a standard export transaction or a routed export transaction. It also depends on whether the USPPI self-files, authorizes a freight forwarder, or the FPPI appoints a U.S. agent.

Party	Filing role	Accuracy role	Practical control
USPPI	Files directly or authorizes an agent in a standard transaction	Responsible for the accuracy of data it provides, including commercial, classification, value, and origin information	Owns product knowledge, invoice data, and many export-control facts
Authorized agent or filer	Files EEI when properly authorized	Responsible for timely and accurate filing based on the information received, and for flagging missing or inconsistent data	Controls AES submission, correction workflow, and ITN communication
FPPI	In a routed export, authorizes a U.S. agent to facilitate export and file when EEI is required	Provides routing and consignee information it controls through its agent	Controls movement in a routed transaction
Carrier	Requires ITN or valid exemption citation before export acceptance when applicable	Generally relies on the filing citation and transport documents, unless acting in another role	Controls loading, tender, and departure cutoffs
Warehouse, transload provider, or trucker	Usually not the AES filer unless separately authorized	Provides physical cargo facts such as piece count, weight, load status, container, seal, and departure readiness	Controls operational facts that can affect whether AES data remains accurate

The key point: filing responsibility and data responsibility are connected, but they are not identical. A forwarder may file as an authorized agent, yet the USPPI still needs to provide accurate product descriptions, Schedule B or HTS information, values, license information when applicable, and other facts it controls.

Standard export transaction: the USPPI leads the filing decision

In a standard export transaction, the USPPI typically controls the export movement or authorizes a forwarder to act on its behalf. The USPPI can self-file through AESDirect in ACE, or it can provide a power of attorney, shipper's letter of instruction, and shipment data to an authorized agent.

If a freight forwarder files, the forwarder is not guessing. The forwarder is relying on the USPPI's instructions and source documents. That is why an SLI should not be treated as an afterthought. It is the operational bridge between sales, compliance, warehouse, trucking, and the AES filing.

A good standard export workflow includes three basic checks before submission: the invoice and packing list agree with the SLI, the product classification and value have been approved by the exporter, and the carrier or forwarder has confirmed the actual export mode, port, and departure timing.

For a step-by-step process, SHIPIT's How to File EEI in AESDirect walks through the filing path and what to prepare before logging in.

Routed export transaction: do not let control become confusion

Routed exports create more confusion because the foreign buyer, or FPPI, controls the movement of the goods out of the United States. The FPPI normally appoints a U.S. agent, often a freight forwarder, to arrange the export and file EEI if required.

That does not mean the U.S. seller should ignore the filing. The USPPI still needs to provide the data required under the Foreign Trade Regulations, such as its identity, origin information, product description, classification, quantity, and value. For controlled goods, the exporter should also coordinate export-control responsibilities carefully, because classification, licensing, end use, and end user determinations may involve rules beyond the AES filing itself.

A routed export process should include written authorization, a defined data handoff, and confirmation that the USPPI receives the ITN or the filing data it needs for records. If the foreign buyer's forwarder will not provide clarity, treat that as a compliance red flag before releasing cargo.

Accuracy is a data ownership problem, not just a filing problem

Many AES errors happen because teams treat the filing as a clerical task after the shipment is already in motion. In reality, accurate EEI depends on data from several owners.

Data element	Best source owner	Common failure mode
USPPI name, address, and EIN	Exporter or finance team	Using the wrong corporate entity or outdated EIN
Schedule B or HTS number	Trade compliance or product team	Copying an import HTS without confirming export classification
Commodity description	Product, sales, or compliance team	Vague descriptions that do not match the invoice or classification
Value and currency	Sales, finance, or ERP system	Reporting a sample value, transfer value, or consolidated value incorrectly
Quantity and unit of measure	Warehouse, packing list owner, or compliance team	Filing cartons or pallets when the Schedule B requires a different unit
ECCN, EAR99, license, or exemption	Export compliance team	Treating export-control data as optional
Port, mode, carrier, and departure date	Forwarder, carrier, or transportation team	Not updating AES after a routing or mode change
Container, seal, pallet count, and gross weight	Warehouse, transload, or drayage provider	Filing before the final physical load is confirmed

The filer should check for obvious inconsistencies, but the filer may not know whether a technical classification, end-use statement, or valuation basis is correct. The company that knows the product and transaction must own those facts.

Filing deadlines are minimum legal benchmarks, not your internal cutoff

AES timing is often misunderstood. The regulatory deadline may be close to departure, but the operational cutoff is usually earlier. Ocean carriers, airlines, terminals, warehouses, and forwarders need time to validate data, issue transport documents, and resolve rejects.

Mode	General pre-departure EEI timing benchmark	Operational planning note
Ocean vessel	Generally 24 hours before cargo is loaded aboard the vessel at the U.S. port	Complete the filing before shipping instruction and documentation cutoffs whenever possible
Air	Generally 2 hours before scheduled departure	Airport tender and screening cutoffs can require earlier completion
Truck	Generally 1 hour before arrival at the border	The driver and border documents need the ITN or exemption citation before departure to the crossing
Rail	Generally 2 hours before arrival at the border	Rail billing and export data should be aligned before interchange

Always verify the applicable FTR requirement, carrier rules, and any special requirements for licensed or controlled cargo. Late, missing, or inaccurate EEI can create penalties, holds, rollovers, carrier refusal, and downstream documentation issues.

SHIPIT's AES filing made simple explains common timing and ITN issues in more detail.

Common AES shipper mistakes that trigger holds or corrections

The most expensive AES mistakes are rarely caused by one bad keystroke. They usually come from unclear ownership, rushed data, or a physical operation that changes after filing.

Mistake 1: naming the wrong USPPI

The USPPI is not automatically the freight payer, warehouse, forwarder, drop shipper, or overseas buyer. It is the U.S. principal party in interest under the FTR. If your company has multiple entities, divisions, or seller-of-record structures, confirm which entity is receiving the primary benefit of the export.

Mistake 2: treating classification as a forwarder task only

A freight forwarder can help identify data gaps, but the exporter usually has better access to product specifications, technical characteristics, origin details, and value basis. Schedule B, HTS, ECCN, EAR99, license codes, and exemption statements should be reviewed by the party with product knowledge.

Mistake 3: filing before the warehouse confirms the final load

If the warehouse short-ships, over-ships, substitutes SKUs, changes pallet counts, or splits a booking, the AES filing may need to be amended. The same issue appears when cargo moves through a transload facility and the final container or air tender differs from the first plan.

Mistake 4: changing modes without updating the filing

A shipment planned for ocean may be expedited by air. A truck export may move by rail. An FCL load may become LCL. These changes can affect port, carrier, departure timing, conveyance, and other filing details. The filing process must be connected to the transportation control tower, not buried in a separate email thread.

Mistake 5: losing the ITN between systems

The ITN should appear where operational teams need it: shipping instructions, booking notes, carrier documentation, pickup instructions, and export records. If the ITN sits only in one person's inbox, the shipment can still miss a cutoff.

Why warehousing, transloading, drayage, and trucking affect AES accuracy

AES is a data filing, but the data must match a physical shipment. That is where warehousing and transloading become important.

For exports, cargo may be picked up from multiple suppliers, consolidated at a warehouse, labeled or palletized, loaded into an ocean container, tendered to an airline, or transferred from a domestic trailer to international equipment. Each of those steps can change the facts behind the AES filing.

A transload or warehouse operation may confirm the actual piece count, weight, dimensions, pallet count, container number, seal number, hazardous documentation, and final readiness for drayage. If that information does not flow back to the filer, the AES record can become stale before the cargo ever reaches the port or airport.

This is especially important for fast-moving export programs that combine domestic trucking with ocean or air freight. A provider with freight forwarding, pickup and delivery, warehousing, transloading, air freight, ocean freight, and drayage coordination can reduce handoffs between the people who see the cargo and the people who file or update the export data.

SHIPIT Logistics can support shippers with integrated transportation, warehousing, transloading, air and ocean freight, and drayage or trucking services. Depending on the program, that can mean end-to-end execution or a narrower scope such as export drayage and transload support only. For related operational planning, see SHIPIT's guide on when to use transloading or cross docking services, the ocean shipment checklist, and air freight forwarding documents and cutoffs.

A practical RACI for AES filing responsibility

A RACI matrix clarifies who is responsible, accountable, consulted, and informed. You do not need a complicated system. You need a written workflow that survives vacations, rush orders, and routed export requests.

Task	Responsible	Accountable	Evidence to keep
Identify USPPI, FPPI, and transaction type	Export operations or trade compliance	Exporter	Order record, customer terms, Incoterms, routing instructions
Confirm EEI requirement or NOEEI citation	Trade compliance or authorized agent	Exporter or filing party, depending on scope	Value by Schedule B, destination, license trigger review
Approve Schedule B, value, origin, and product description	Exporter or compliance owner	USPPI	Classification record, invoice, packing list
Approve ECCN, EAR99, license, or exemption data	Export compliance owner	Exporter	License review, screening record, supporting notes
Provide SLI and authorization to forwarder	Export operations	USPPI	SLI, POA or written authorization
File EEI and obtain ITN	Self-filer or authorized agent	Filer for submission accuracy, USPPI for data provided	AES acceptance, ITN, timestamp
Place ITN or exemption on carrier documents	Forwarder, shipping team, or carrier-facing coordinator	Transportation owner	BOL, air waybill, booking, pickup docs
Amend AES after operational changes	Filer, using updates from warehouse or transport team	Filing owner and data owner	Amendment record and reason
Retain export records	Exporter and filer as applicable	Company compliance owner	EEI record, commercial docs, correspondence

This matrix can be built into an SOP or Statement of Work. If you are formalizing responsibilities with a provider, SHIPIT's guide to what to put in a freight forwarding SOW is a useful starting point.

Should the shipper self-file or use a freight forwarder?

Self-filing can work well for exporters with trained compliance staff, stable product lines, and direct control over routing. It gives the exporter direct visibility into AESDirect and can reduce dependency on third parties.

Using a forwarder or authorized agent can be a better fit when shipments involve multiple modes, tight cutoffs, airport or port execution, consolidated cargo, routed exports, international documentation, or warehouse and transload coordination. The forwarder can connect the filing process to booking, pickup, drayage, airline tender, ocean carrier instructions, and exception management.

The decision should not be based only on convenience. It should be based on control. If a forwarder files, the exporter still needs a process for approving classifications, values, license data, and routed export handoffs. If the exporter self-files, it still needs timely operational data from the warehouse, trucker, forwarder, or carrier.

A strong AES shipper process is one where the filing method is matched to the operating model.

Records, amendments, and audit readiness

AES accuracy does not end when the ITN is issued. Exporters and filers should retain records according to applicable FTR and export-control requirements, commonly five years for many export records. If data changes after filing, the EEI should be corrected as soon as the change is known.

Examples that may require review or amendment include a different export date, port, mode, carrier, quantity, value, Schedule B, license information, consignee, or cancellation. Not every operational note changes the legal filing, but every meaningful discrepancy should trigger a filing review.

The best audit defense is a clean trail: who approved the data, what source documents were used, when the filing was accepted, how the ITN was provided, and what changed later.

Frequently asked questions

• Is the AES shipper always the exporter? Not necessarily. AES shipper is a common business phrase, but the legal analysis should identify the USPPI, FPPI, authorized agent, and filer. The exporter or USPPI may provide the data while a forwarder files as agent.

• Can a freight forwarder file AES for me? Yes, if properly authorized and provided with the required data. The forwarder can file EEI and obtain the ITN, but the exporter must still provide accurate information for the data it controls.

• Who is responsible in a routed export transaction? The FPPI controls the movement and typically authorizes a U.S. agent to file. The USPPI still has required data responsibilities and should request the ITN or filing data needed for its records.

• If EEI is not required, does responsibility still matter? Yes. A valid NOEEI exemption citation must be correct. Using the wrong exemption can create the same operational and compliance problems as an incorrect AES filing.

• Does the warehouse or transload provider have AES responsibility? Usually not as the filer, unless separately authorized. However, the warehouse or transload provider controls physical shipment facts that may affect the filing, such as final piece count, weight, container, seal, and load status.

• When should AES be amended? AES should be reviewed and corrected when material shipment data changes after filing. Common triggers include value, quantity, classification, port, mode, carrier, departure, consignee, or license-related changes.

The safest AES process is straightforward: define the transaction type, assign each data element to an owner, set internal cutoffs earlier than carrier deadlines, and keep the filing connected to the real cargo movement from warehouse to port, airport, border, or final export handoff.

For help aligning AES and EEI responsibilities with export forwarding, warehousing, transloading, drayage, trucking, and air or ocean freight, contact SHIPIT Logistics.