Why was my AES submission rejected?

Rejections commonly result from mismatched party names or TINs, incorrect Schedule B/HTS codes, missing license citations, or invalid date formats. Review the AES error message, correct the specified fields, and resubmit or file an AES correction per carrier and Census procedures.

Can the Export Declaration be signed electronically?

Yes. Electronic signatures meet U.S. legal standards under the ESIGN Act (15 U.S.C. ch. 96) and state UETA rules where adopted, provided the signature meets intent, consent, attribution, and retention requirements for the transaction.

Who is authorized to sign the declaration?

An authorized company representative such as an officer, owner, or delegated agent should sign. Document signer authority in internal policy or power-of-attorney to ensure attestations are enforceable in audits or enforcement reviews.

How do I correct a filed EEI?

Submit an AES correction per Census instructions; act promptly to minimize enforcement exposure. Retain copies of the original filing, the correction request, and acknowledgment receipts for audit trails and potential investigations.

Do supporting documents require notarization or RON?

AES filings themselves typically do not require notarization, but supporting documents (commercial invoices, powers of attorney) may require notarization or RON depending on destination or contracting parties; state RON laws vary, so verify local requirements.

How long should I retain Export Declaration records?

Retain EEI and supporting records per federal guidance — commonly five years for export records — and longer where industry rules or tax obligations apply; maintain searchable audit trails for enforcement or audit requests.

Electronic Signature
Templates
Tax
Export Declaration

Export Declaration

This template is fully customizable. Edit the text, fill out the fields, and send it for signature. Give it a try!

What an Export Declaration Is and where it fits

An Export Declaration records essential details about goods leaving the United States and is typically submitted as Electronic Export Information (EEI) via the Automated Export System (AES). The declaration captures shipper and consignee identities, commodity classification (Schedule B or HTS), value, quantity, transport data, and any required export license or ECCN. Federal agencies — including the Census Bureau, U.S. Customs and Border Protection, and the Bureau of Industry and Security — use the information for statistical reporting, licensing enforcement, and customs clearance, so accuracy and timely filing are critical.

Why the Export Declaration matters for compliance and logistics

A correct Export Declaration ensures lawful shipment, enables customs release, and supports trade statistics. Precise declarations reduce the risk of shipment delays, inspection holds, civil fines, and enforcement under U.S. export control regimes while preserving traceability for audits and commercial reconciliation.

Who typically prepares and reviews Export Declarations

Common users and stakeholders involved in preparing or signing Export Declarations include shippers, freight forwarders, customs brokers, and compliance officers.

Exporters and manufacturers who originate shipments and must provide accurate commodity and license information.
Freight forwarders and customs brokers that file EEI/AES on behalf of shippers and coordinate logistics.
Compliance teams, trade attorneys, and third-party agents advising on classification, licensing, and recordkeeping obligations.

Each party’s role should be documented in commercial contracts and shipping instructions to assign responsibility for accurate filing and retention.

Step-by-step checklist for preparing and filing an Export Declaration

Follow this sequential checklist to complete an Export Declaration accurately and file EEI via AES before export documentation is finalized.

01

Gather Data: Collect invoices, commodity codes, and party IDs.
02

Classify Goods: Determine Schedule B/HTS and ECCN as needed.
03

Prepare EEI: Enter data into AES or broker portal.
04

File & Record: Transmit EEI and retain proof of filing.

Where the Export Declaration goes and who reviews it

This routing overview describes where Export Declarations are submitted, what agencies receive them, and how interagency checks are performed.

AES Filing: EEI submitted to Automated Export System.
Census Review: Census Bureau validates statistical reporting fields.
BIS Screening: Bureau of Industry and Security checks controls.
Customs Release: CBP uses declaration for cargo clearance.

Online workflow settings to enforce accuracy and retention

Configure your online filing workflow to validate required fields, capture attestations, authenticate signers, and retain audit logs for compliance.

Automated Export System Field Name	Required configuration and validation rules.
Shipper and Consignee Identification Fields	Require full legal names and EIN/TIN.
Commodity Classification and Description Fields	Enforce Schedule B/HTS format and details.
License and ECCN Entry Fields	Validate license numbers and exceptions.
Transport and Routing Information Fields	Require BOL/AWB, ports, and carrier info.

Essential components to include on a professional Export Declaration

A professional Export Declaration includes identification, commercial and transport details, classification and license data, value statements, consignee information, and audit-ready metadata.

Shipper Details

Full exporter name, primary address, EIN or IRS TIN where applicable, contact phone and email; consistent legal name prevents TIN-mismatch issues and supports automated AES validation and customs processing.

Consignee

Complete consignee name and address, country of final destination, and intermediary party details; specify ultimate consignee to comply with screening, licensing checks, and U.S. export controls (EAR/ITAR) where relevant.

Commodity Code

Schedule B or HTSUS classification with precise six- to ten-digit code, product description, and unit quantity; correct coding determines licensing, quotas, and statistical reporting for Census AES.

Value & Terms

Declared commercial value, currency, Incoterm or shipment terms, and payment method; value affects export reporting, potential duties, and anti-dumping or licensing thresholds.

License Details

Export license number or license exception citation if required; include authorization references for controlled goods, ECCN classifications, and relevant agency determinations to avoid enforcement risk.

Transport Data

Vessel or flight information, bill of lading or airway bill number, departure port, routing, and HTS packaging details; critical for customs release and interagency tracking.

Key data elements required on an Export Declaration

Shipper Tax ID: Provide EIN or SSN.

Consignee Country: Two-letter ISO country code.

Commodity Code: Use Schedule B or HTSUS.

Export License: Include license number or exception.

Declared Value: Total invoice value in USD.

Transport ID: Bill of lading or AWB number.

Practical practices to reduce filing errors and delays

Adopt consistent naming, validate codes, and centralize export documentation to reduce rework and compliance exposure.

Standardize party names and TINs across documents

Maintain a master shipper and consignee registry to ensure consistent names and TIN formats across invoices, bills of lading, and EEI filings to prevent AES rejects.

Verify commodity classification with technical teams

Use subject-matter experts or classification tools to confirm Schedule B/HTS and ECCN entries; document the rationale to support audits and classification challenges.

Pre-check license requirements before shipping

Screen transactions against denied-party lists and determine license needs early to avoid shipment holds and last-minute export license applications.

Retain automated proof of filing and audits

Preserve AES acknowledgements, submission timestamps, and audit trails in a secure repository to demonstrate compliance during reviews or enforcement.

Common pitfalls when preparing Export Declarations

Using an incorrect Schedule B or HTS code leads to misreporting, potential fines, and delayed clearance; verify classification with technical staff and customs resources.
Omitting or misidentifying the ultimate consignee can trigger enforcement actions under EAR or ITAR and may require post-filings corrections.
Failing to include required license numbers or citing incorrect license exceptions causes AES rejects and exposes the exporter to civil penalties.
Inconsistent party names or values between invoice, bill of lading, and EEI creates audits and backup withholding or cargo holds during customs inspection.

Penalties and risks from inaccurate or late Export Declarations

Civil Penalties: Fines for inaccurate filings.

Criminal Liability: Willful violations may lead to prosecution.

Shipment Seizure: Goods may be detained or forfeited.

Denial Privileges: Export privileges revoked.

Recordkeeping Violations: Failure triggers fines and penalties.

Licensing Errors: Unauthorized export of controlled items.

Timing and filing expectations for Export Declarations

Timely EEI filing supports customs release and carrier acceptance; internal schedules and carrier lead times affect when to prepare documentation.

File Before Export:

Submit EEI through AES prior to departure.

Carrier Lead Time:

Forwarder may require EEI 24–72 hours before loading.

License Timing:

Obtain export licenses before shipment for controlled items.

Corrections Window:

Submit AES corrections promptly to reduce penalties.

Record Retention Period:

Retain records for at least five years as federal guidance suggests.

E-signature vendor pricing and feature snapshot for Export Declaration workflows

Compare common vendor starting prices and selected feature availability relevant to signing, auditing, and retaining Export Declarations and supporting paperwork.

	signNow	DocuSign	Adobe Sign	PandaDoc	HelloSign
Starting Price	$8/user/mo	$15/user/mo	$14/user/mo	$19/user/mo	$15/user/mo
Free Trial	Yes, 7-day trial	Varies	Varies	Varies	Varies
Bulk Send	Yes	Yes	Yes	Yes	No
Audit Trail	Yes	Yes	Yes	Yes	Yes
HIPAA Compliant	Yes	Yes	Yes	No	No

Illustrative scenarios showing how Export Declarations are used

Two concise, realistic examples show common workflows and outcomes when export paperwork is prepared and filed correctly.

Large Manufacturer

A multinational manufacturer consolidates product codes across plants to file one consolidated EEI per shipment.

Centralized classification reduced classification errors by standardizing inputs.
The result: fewer AES rejects, faster customs release, and a single audit trail for compliance and commercial reconciliation across departments.

Freight Forwarder

A third-party forwarder prepares EEI on behalf of small shippers, validating ECCNs and screening consignees.

Proactive license checks reduced last-minute holds.
Improved accuracy decreased carrier delays and allowed predictable pickup windows for exporters and importers in cross-border logistics.

Technical considerations for eSubmission and integrations

When e-submitting Export Declarations, verify platform compatibility, file formats, and integration with logistics and ERP systems.

Integrations: Salesforce, NetSuite, Microsoft 365, and Google Workspace support.
File Formats: PDF, DOCX, XML, CSV supported.
Authentication: Email, SMS, or stronger KBA options.

Frequently asked questions and quick solutions

Answers below address common filing and e-signature issues when preparing Export Declarations and related documents.

Need help? Contact support

Why was my AES submission rejected?
Rejections commonly result from mismatched party names or TINs, incorrect Schedule B/HTS codes, missing license citations, or invalid date formats. Review the AES error message, correct the specified fields, and resubmit or file an AES correction per carrier and Census procedures.
Can the Export Declaration be signed electronically?
Yes. Electronic signatures meet U.S. legal standards under the ESIGN Act (15 U.S.C. ch. 96) and state UETA rules where adopted, provided the signature meets intent, consent, attribution, and retention requirements for the transaction.
Who is authorized to sign the declaration?
An authorized company representative such as an officer, owner, or delegated agent should sign. Document signer authority in internal policy or power-of-attorney to ensure attestations are enforceable in audits or enforcement reviews.
How do I correct a filed EEI?
Submit an AES correction per Census instructions; act promptly to minimize enforcement exposure. Retain copies of the original filing, the correction request, and acknowledgment receipts for audit trails and potential investigations.
Do supporting documents require notarization or RON?
AES filings themselves typically do not require notarization, but supporting documents (commercial invoices, powers of attorney) may require notarization or RON depending on destination or contracting parties; state RON laws vary, so verify local requirements.
How long should I retain Export Declaration records?
Retain EEI and supporting records per federal guidance — commonly five years for export records — and longer where industry rules or tax obligations apply; maintain searchable audit trails for enforcement or audit requests.

Explore Templates

Roanoke Valley Association of Realtors Purchase Agreement Ohio Vacant Land Purchase Agreement Ohio Purchase Agreement Michigan Purchase Agreement Minnesota Standard Residential Purchase Agreement California Residential Purchase Agreement

be ready to get more

Join over 28 million airSlate SignNow users

Sign Now