AES Messages. Every customs event has a digital signal.
The Automated Export System uses structured electronic messages to exchange export declarations, customs decisions and exit information. Understand how messages move between traders and customs authorities, what they communicate and why their status matters.
Information sent for customs processing.
Acceptance, rejection, controls and release.
Information supporting exit supervision and certification.
This diagram is a conceptual representation of the standard export communication flow, not a complete technical message specification. Actual message codes, exchanges and interfaces depend on the AES component, applicable specifications and national implementation.
Three communication layers. One connected export process.
AES messages perform different functions depending on who sends them, who receives them and which stage of the customs procedure they support. Understanding these distinctions is essential when interpreting system responses and shipment status.
Declaration and request messages
Traders or their representatives transmit declarations and other permitted requests through the relevant electronic customs interface. These communications initiate or modify a customs process.
- Submitting an export declaration
- Requesting a permitted amendment
- Requesting declaration invalidation
- Providing additional information when required
Processing and decision messages
Customs communicates relevant processing outcomes to the trader. These responses may indicate acceptance, rejection, controls, release or other events affecting the declaration.
- Reporting validation or rejection results
- Confirming declaration acceptance
- Communicating control-related information
- Notifying release or other decisions
Export and exit coordination
Customs authorities exchange information needed to coordinate export and exit processing. These exchanges connect the office of export with the relevant office of exit, including cross-border movements.
- Transmitting export movement information
- Supporting arrival and exit processing
- Communicating relevant control results
- Returning exit results to the export office
How the message layers connect
The trader transmits the required export data.
Customs communicates relevant declaration processing outcomes.
Customs offices coordinate the movement towards exit.
The relevant outcome is communicated following the applicable exit process.
The sequence illustrates a simplified successful export scenario. It does not represent every message exchange, exception, control, amendment or national variation.
A message is not the same as a customs status.
A message is an electronic communication. A status describes the processing condition of a declaration or movement. Several messages may contribute to a status change, and not every message represents a new legal customs decision.
AES operates within the framework of the Union Customs Code and its delegated and implementing provisions. The precise electronic message structures, identifiers and exchange rules are defined in applicable technical specifications and national implementation documentation.
Union Customs Code — Regulation (EU) No 952/2013 ↗Follow the messages. Understand the customs event.
Each electronic communication has a specific role in the export process. A message may confirm that information was received, communicate a customs decision or report an event at the office of exit. The meaning depends on the message and its context.
Six communication milestones
Declaration transmitted
The declarant sends the export declaration through the applicable electronic interface. The submission is subject to the relevant technical and customs validation rules.
Declaration accepted and MRN allocated
When the legal conditions for acceptance are fulfilled, customs accepts the declaration and assigns an MRN to identify the accepted declaration.
Verification and possible intervention
Customs may verify the declaration, examine supporting records or inspect the goods. Relevant communications may request information or notify the trader of a control-related event.
Goods released for export
Once the applicable conditions are met, the customs office of export releases the goods. The relevant release communication enables the trader to distinguish release from earlier stages.
Movement information and exit results
The relevant customs offices exchange information supporting supervision at exit. Arrival, control and exit-related events are handled according to the applicable AES workflow.
Exit certified by the office of export
Following the applicable exit process, the customs office of export certifies exit to the exporter or declarant, using the relevant information or evidence recognised under customs law.
Explore the legal journey behind the messages.
Electronic messages support customs processing, but their legal significance depends on the declaration and the applicable procedure.
Regulation (EU) No 952/2013, including Articles 172, 188, 194, 267 and 269; and the applicable implementing provisions governing export and exit formalities. Technical message definitions are governed by the applicable AES specifications.
Not every failed message means a failed export.
AES communication problems can arise at different levels. Some concern the electronic connection, others concern declaration data or a customs decision. Identifying the category is the first step towards the correct response.
Transmission failure
A message may fail to reach the intended electronic interface, or its delivery status may remain uncertain.
Verify delivery and processing status before resending. A timeout does not necessarily mean that the original message was not received.
Message validation error
An electronic submission may be rejected because its structure or content does not satisfy the applicable validation rules.
Read the returned error information, identify the affected data and correct the submission according to the applicable technical specifications.
Control or customs intervention
An accepted declaration may require verification, supporting documents or examination before customs release.
Follow the customs instructions. A control notification must not be treated as a technical rejection or as permission to move the goods.
Missing or delayed response
The trader’s software may not display an expected response even when processing has progressed in the customs system.
Reconcile the available message history with the authoritative customs status before taking further action.
What should you check first?
The same visible symptom can have different causes. Use the communication evidence to identify the correct next step.
Check the sending system’s transmission records and available acknowledgements.
Distinguish technical receipt, validation results and legal customs acceptance.
Identify controls, pending requests, release decisions and other relevant events.
Resolve inconsistencies before assuming that a message must be resent or a new declaration submitted.
Never treat a missing response as automatic rejection.
If a submission times out or an acknowledgement is missing, the actual processing outcome may still be unknown. Blind resubmission can create duplicate submissions or additional processing problems. Verify the status using the available customs and software procedures first.
Technical validation, transport acknowledgements and legal customs decisions must be distinguished. The Union Customs Code governs acceptance, verification and release, while applicable AES specifications and national technical documentation define the relevant electronic exchanges.
Every message leaves a trace. Make the history readable.
An export declaration generates a sequence of electronic communications and customs events. Reconstructing that sequence helps operators investigate discrepancies, demonstrate the processing history and identify which evidence supports the final export outcome.
One declaration. Multiple recorded events.
Declaration transmitted
Record the submission reference, transmission time and available delivery or validation information.
Declaration accepted
Associate the allocated MRN with the accepted declaration and its relevant acceptance information.
Release communicated
Preserve the release communication and distinguish its date and meaning from the later exit-related events.
Exit information exchanged
Where accessible, reconcile relevant exit-related information with the declaration and transport records.
Exit certification retained
Preserve the customs certification of exit when issued, together with the supporting commercial and transport documentation.
Release evidence and exit evidence serve different purposes.
A release notification establishes a customs processing outcome. Certification of exit concerns departure from the customs territory under the applicable customs rules. For VAT or other regulatory purposes, additional legal requirements may apply to the evidence retained.
Article 15 of Regulation (EU) No 952/2013 concerns the provision of information to customs. Article 51 addresses the retention of documents and information required for customs control. Articles 172, 194 and 267 concern acceptance, release and exit supervision respectively. Specific recordkeeping obligations and retention periods must be assessed under the applicable rules.
AES messages. Frequently asked questions.
Clear answers to common questions about electronic export messages, message identifiers, customs responses and communication between the office of export and the office of exit.
01 What are AES messages? +
AES messages are structured electronic communications exchanged within the Automated Export System. They support export declaration processing, customs decisions and the exchange of information required for exit formalities. Different messages serve different purposes and may involve traders, national customs systems or customs authorities.
02 What do AES IE message codes mean? +
IE identifiers are used in technical specifications to distinguish particular information exchanges. Their meaning, sender, receiver, conditions and data requirements must be interpreted using the applicable AES message specifications. An IE identifier alone does not establish the legal status of an export declaration.
03 Is a technical acknowledgement the same as customs acceptance? +
No. A technical acknowledgement may confirm receipt or processing at an electronic interface. Customs acceptance is a distinct legal event governed by the Union Customs Code. Operators must identify which event a particular response actually confirms.
04 Does receiving an MRN mean the goods are released? +
No. An MRN identifies the accepted declaration. Release is a separate customs processing outcome. The trader should rely on the relevant release communication rather than assuming that MRN allocation authorises the movement of goods towards exit.
05 Who exchanges messages between the export and exit offices? +
The relevant customs systems exchange information between the office of export and the office of exit under the applicable AES workflow. These customs-to-customs exchanges support supervision of the movement and communication of exit results. Traders do not necessarily receive every internal customs message.
06 What should I do if an AES response is missing? +
Check the available transmission records, acknowledgements and customs processing status. A missing response does not prove that the submission was rejected or never received. Avoid resubmitting blindly before establishing the actual outcome through the applicable system procedures.
07 Which AES message proves that the goods have exited? +
The relevant exit certification communicated by the customs office of export is distinct from the declaration acceptance and release messages. The precise technical identifier depends on the applicable message specifications. An MRN or release notification alone does not certify exit.
08 Are AES messages identical in every EU Member State? +
AES is based on a common EU framework, but trader-facing interfaces and certain implementation details are managed nationally. Operators should consult the applicable EU technical documentation together with the instructions of the relevant national customs authority.
Understand the legal and technical framework.
Use EU legislation for the legal meaning of customs procedures and the official AES documentation for system architecture and electronic exchanges.
Union Customs Code
Regulation (EU) No 952/2013. The legal framework for customs declarations, acceptance, verification, release and exit supervision.
OPEN EUR-LEX ↗ 02 / DELEGATED RULESUCC Delegated Regulation
Regulation (EU) 2015/2446. Supplementary customs rules, including declaration requirements and provisions relevant to export procedures.
OPEN EUR-LEX ↗ 03 / IMPLEMENTING RULESUCC Implementing Regulation
Regulation (EU) 2015/2447. Detailed rules governing customs procedures, including export and exit formalities.
OPEN EUR-LEX ↗ 04 / EUROPEAN COMMISSIONDG TAXUD — Customs Systems
European Commission information on electronic customs systems, AES implementation and customs digitalisation. Consult the relevant AES documentation for technical message definitions.
EU COMMISSION WEBSITE ↗Legal provisions and technical specifications serve different functions. For exact IE message identifiers, structures and conditions, consult the applicable AES technical specifications and national implementation documentation.
Read the message. Understand the decision.
Reliable export processing requires more than recognising a message identifier. Every response must be interpreted in relation to its sender, purpose, customs procedure and legal effect.