AES Electronic Export Information Filing Audit
Audit AES Electronic Export Information filings to confirm each shipment was filed when required, classified correctly, and backed by source documents. Use it to catch missed EEI triggers, bad Schedule B data, and missing ITNs before they become compliance issues.
Trusted by frontline teams 15 years of frontline software AI customization in seconds
Built for: Manufacturing · Aerospace And Defense · Electronics · Logistics And Freight Forwarding · Life Sciences
Overview
This AES Electronic Export Information Filing Audit template is built to verify whether export shipments were required to be filed in AES, whether the filing was completed correctly, and whether the supporting record is complete. It walks the reviewer through shipment scope, EEI filing requirement determination, classification and license data, AES filing accuracy, ITN validation, and retention of the audit trail.
Use it when you need a repeatable check on export compliance for shipments that may involve Schedule B thresholds, mandatory filing triggers, ECCN-controlled items, or license codes and exceptions. It is especially useful when filings are handled by a broker or freight forwarder and the internal team still needs to confirm the filing decision and the data that was transmitted.
Do not use it as a generic export logistics checklist. If the shipment is purely domestic, if no EEI decision is needed, or if you are reviewing only transportation performance, this template is the wrong tool. It is also not a substitute for classification work; if Schedule B or ECCN data has not been established, that issue should be resolved before the audit is closed. The template is strongest when used after shipment execution, with source documents available for comparison and any deficiencies assigned to a named owner.
Standards & compliance context
- This template supports export compliance reviews aligned with U.S. Census Bureau AES requirements and general export reporting obligations under the Export Administration Regulations and related trade controls.
- The Schedule B, ECCN, and license fields help document classification and licensing decisions that are commonly reviewed under U.S. export control and customs compliance programs.
- Retention prompts support recordkeeping expectations commonly associated with export filings, internal controls, and audit readiness.
- If a broker or freight forwarder submits EEI on your behalf, the audit should still verify internal oversight and source-document support rather than relying only on the transmitted filing.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Inspection Setup & Shipment Scope
This section defines exactly which shipment is being reviewed so the audit stays tied to the correct transaction, party, and document set.
-
Shipment record identified and review period documented
Record the shipment identifier, export date, and audit period covered by this inspection.
-
USPPI identified for the shipment
Document the U.S. Principal Party in Interest responsible for the export filing determination.
-
Destination country confirmed
Confirm the final destination country used to evaluate mandatory filing exceptions and destination-specific requirements.
-
Shipment type and filing responsibility verified
Identify whether the shipment was filed by the USPPI, authorized agent, or freight forwarder.
-
Supporting export documents available for review
Confirm availability of commercial invoice, packing list, shipping instructions, and any export authorization documents.
EEI Filing Requirement Determination
This section tests whether the shipment actually required EEI filing and captures the reason behind the decision.
-
Commodity value per Schedule B number documented
Enter the declared commodity value associated with each Schedule B number reviewed.
-
EEI filing threshold evaluated for each Schedule B number
Confirm the review determined whether the value exceeded the applicable AES filing threshold for the Schedule B number.
-
Mandatory filing trigger identified when applicable
Select any mandatory filing triggers that applied to the shipment.
-
Filing decision supported by documented rationale
Verify the file contains a clear explanation for why EEI filing was required or not required.
Classification, ECCN, and License Data
This section verifies that the export classification and licensing details used for filing match the commodity and supporting records.
-
Schedule B number recorded for each commodity line
Confirm each commodity line has a Schedule B number recorded in the shipment file.
-
ECCN recorded where applicable
Verify the Export Control Classification Number is documented for controlled items when required.
-
License code or license exception documented where applicable
Confirm the AES filing includes the correct license code, license number, or license exception reference when required.
-
Commodity description matches classification and filing record
Verify the commodity description is consistent with the Schedule B number, ECCN, and any license information in the file.
AES Filing Accuracy & ITN Validation
This section confirms the AES submission itself was accurate, timely, and traceable through the ITN and any corrections.
-
AES filing submitted before export when required
Verify the EEI filing was transmitted in AES before export or within the required filing window.
-
Internal Transaction Number (ITN) recorded in shipment file
Record the ITN or other AES proof of filing associated with the shipment.
-
AES filing data matches source documents
Verify the filed EEI data matches the commercial invoice, Schedule B classification, destination, and license details.
-
Any filing amendments or corrections documented
Confirm that post-filing corrections, amendments, or cancellation/refile actions are documented when needed.
Record Retention & Corrective Actions
This section closes the loop by checking retention, documenting deficiencies, and assigning ownership for follow-up.
-
Export filing records retained for required retention period
Confirm the shipment file and supporting export records are retained for at least five years.
-
Deficiencies or non-conformances documented
Describe any missing, inaccurate, or late filing items identified during the audit.
-
Corrective action assigned and owner identified
Document the corrective action, responsible owner, and target completion date for each deficiency.
How to use this template
- Identify the shipment record, document the review period, and gather the commercial invoice, packing list, export order, and any broker or forwarder filing evidence.
- Confirm the USPPI, destination country, shipment type, and which party was responsible for filing EEI so the audit scope matches the actual transaction.
- Review each Schedule B line to determine whether the EEI threshold or another mandatory filing trigger applied, and record the rationale for the filing decision.
- Verify that each commodity line has the correct Schedule B number, ECCN where applicable, and any required license code or license exception, then compare the commodity description to the source documents.
- Check that the AES filing was submitted on time when required, that the ITN is recorded in the shipment file, and that the filed data matches the source documents.
- Document any deficiency or non-conformance, assign corrective action to an owner, and confirm export records are retained for the required period.
Best practices
- Review the filing decision by Schedule B line, not only at the shipment total, because mixed commodity shipments can have different filing triggers.
- Compare the AES record against the commercial invoice and packing list before closing the audit, since description mismatches are a common source of filing errors.
- Flag any missing ITN as a critical deficiency when EEI filing was required, because the shipment file should show proof of submission.
- Document the reason a filing was not required, especially when the shipment is near a threshold or involves a controlled commodity.
- Verify that ECCN and license fields are populated only when applicable and that the classification basis is consistent across the export file.
- Capture amendments or corrections in the same audit record so the final disposition is clear and the original error is not lost.
- Assign corrective action to the process owner, not just the reviewer, so recurring broker or master-data issues are addressed upstream.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
What shipments does this AES EEI filing audit template apply to?
Use it for export shipments where you need to determine whether EEI filing was required and whether the AES record was completed correctly. It is designed around shipment-level review, including USPPI, destination country, filing responsibility, Schedule B, ECCN, and license data. It works best when you are auditing actual export transactions rather than doing a general trade compliance review.
How often should this audit be run?
Most teams run it on a recurring sample basis, such as weekly, monthly, or per shipment batch, depending on export volume and risk. High-volume exporters often use it as a post-shipment audit to catch errors quickly while records are still easy to retrieve. If you have recent process changes, new commodities, or new brokers, increase the cadence until the process is stable.
Who should complete the audit?
A trade compliance specialist, export coordinator, customs broker manager, or internal auditor usually owns the review. The person running it should understand EEI filing triggers, Schedule B classification, and the difference between source documents and filed data. If the business relies on a freight forwarder or broker, the internal owner should still verify the filing decision and the ITN.
Does this template cover mandatory filing triggers and threshold-based filings?
Yes. The template is built to verify whether EEI was required based on shipment value, destination, commodity type, and other mandatory filing triggers. It also prompts the reviewer to document the rationale when a filing was not required. That makes it useful for both filed and non-filed shipments.
How does this audit handle ECCN and license information?
It includes fields to confirm that the Schedule B number, ECCN, and any license code or license exception are recorded where applicable. That helps you catch mismatches between the export classification and the AES filing record. If a commodity is not subject to ECCN or license reporting, the audit should still document why those fields were not used.
What are the most common mistakes this audit catches?
Common issues include missing ITNs, filing after export when pre-export filing was required, incorrect Schedule B numbers, and commodity descriptions that do not match the source documents. It also catches weak filing rationales, missing license codes, and amendments that were never documented. Those are the kinds of gaps that create repeat compliance risk.
Can this template be customized for brokers, ERP systems, or freight forwarders?
Yes. You can add fields for broker name, ERP export order number, commercial invoice number, or forwarder reference numbers without changing the audit logic. Many teams also add system-specific evidence fields so reviewers can link the audit to the exact source record in their ERP, TMS, or document repository. The core control points should stay the same.
How does this compare with an ad-hoc export review?
An ad-hoc review often checks only whether an ITN exists, which can miss the reason the filing was required in the first place. This template walks through scope, filing determination, classification, filing accuracy, and retention in a repeatable order. That makes it easier to spot non-conformances, assign corrective action, and prove the review was consistent.
Related templates
Go deeper on the topic
-
Predictive scheduling laws — also called fair workweek laws or secure scheduling — require employers in covered industries to publish employee schedules...
-
Overtime calculation is the process of applying federal, state, local, and contractual rules to hours worked to determine the correct pay — including...
-
A near-miss is an event that could have caused injury or damage but didn't — a slip that didn't fall, a load that shifted but didn't drop, a machine that...
-
Lockout/tagout (LOTO) is the procedure for controlling hazardous energy — electrical, hydraulic, pneumatic, mechanical, thermal, chemical — before...
-
Compare 11 frontline hiring platforms on mobile apply, automated screening, and onboarding handoffs to find the right fit for hourly and shift-based workforces.
-
Spring '26 brings AI Course Creation, Power BI-connected AI Agents, and smarter content governance to MangoApps. See what's new across the platform.
-
Integrated digital workplace task management tips to keep work moving, reduce stalls, and turn conversations into accountable action.
-
When scheduling tools lack leave and budget data, costly errors follow. See how integrated workforce management closes the context gap.
Ready to use this template?
Get started with MangoApps and use AES Electronic Export Information Filing Audit with your team — pricing built for small business.
