Customs Explorer
⌕

Customs Explorer

AES messages

EU CUSTOMS SYSTEMS / EXPORT COMMUNICATION

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.

Export declarations Customs responses Release messages Exit communication
AES COMMUNICATION MODEL ELECTRONIC EXCHANGE
TRADER / DECLARANT National electronic interface
CUSTOMS OFFICE OF EXPORT Declaration and release processing
CUSTOMS OFFICE OF EXIT Exit supervision and results
01 / SUBMISSION Declaration messages

Information sent for customs processing.

02 / RESPONSE Customs decisions

Acceptance, rejection, controls and release.

03 / EXIT Exit communication

Information supporting exit supervision and certification.

TECHNICAL SCOPE

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.

ELECTRONIC MESSAGE ARCHITECTURE

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.

01 / TRADER TO CUSTOMS
T TRADER
SUBMISSION
C CUSTOMS

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.

TYPICAL FUNCTIONS
  • Submitting an export declaration
  • Requesting a permitted amendment
  • Requesting declaration invalidation
  • Providing additional information when required
INITIATES AN ACTION
02 / CUSTOMS TO TRADER
C CUSTOMS
RESPONSE
T TRADER

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.

TYPICAL FUNCTIONS
  • Reporting validation or rejection results
  • Confirming declaration acceptance
  • Communicating control-related information
  • Notifying release or other decisions
COMMUNICATES A RESULT
03 / CUSTOMS TO CUSTOMS
E EXPORT
EXCHANGE
X EXIT

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.

TYPICAL FUNCTIONS
  • Transmitting export movement information
  • Supporting arrival and exit processing
  • Communicating relevant control results
  • Returning exit results to the export office
COORDINATES CUSTOMS OFFICES
SIMPLIFIED COMMUNICATION JOURNEY

How the message layers connect

CONCEPTUAL MODEL
01
TRADER → CUSTOMS Declaration submitted

The trader transmits the required export data.

02
CUSTOMS → TRADER Acceptance and processing

Customs communicates relevant declaration processing outcomes.

03
CUSTOMS ↔ CUSTOMS Export and exit exchange

Customs offices coordinate the movement towards exit.

04
CUSTOMS → TRADER Exit-related notification

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.

IMPORTANT TECHNICAL DISTINCTION

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.

MESSAGE LIFECYCLE

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.

STANDARD EXPORT SCENARIO

Six communication milestones

SIMPLIFIED FLOW
01
TRADER → CUSTOMS SUBMISSION

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.

WHAT THIS TELLS YOU Data has been submitted, but customs acceptance is not yet established.
02
CUSTOMS → TRADER ACCEPTANCE

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.

WHAT THIS TELLS YOU The declaration is accepted. The goods are not necessarily released.
03
CUSTOMS PROCESSING CONTROLS

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.

WHAT THIS TELLS YOU Processing is continuing. A control-related message is not itself confirmation of release.
04
CUSTOMS → TRADER RELEASE

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.

WHAT THIS TELLS YOU The goods may proceed towards exit under the applicable customs requirements.
05
CUSTOMS ↔ CUSTOMS EXIT PROCESSING

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.

WHAT THIS TELLS YOU The movement is being processed at exit; the exact outcome must be established from the relevant results.
06
CUSTOMS → TRADER EXIT CERTIFICATION

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.

WHAT THIS TELLS YOU Exit has been certified by customs, not merely anticipated from a release message.
RELATED PROCESS

Explore the legal journey behind the messages.

Electronic messages support customs processing, but their legal significance depends on the declaration and the applicable procedure.

AES DECLARATIONS
MESSAGE EXCEPTIONS / OPERATIONAL CONTROL

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.

01 / TECHNICAL LAYER

Transmission failure

A message may fail to reach the intended electronic interface, or its delivery status may remain uncertain.

POSSIBLE CAUSES Connectivity interruption Interface unavailability Communication timeout
OPERATOR RESPONSE

Verify delivery and processing status before resending. A timeout does not necessarily mean that the original message was not received.

02 / VALIDATION LAYER

Message validation error

An electronic submission may be rejected because its structure or content does not satisfy the applicable validation rules.

POSSIBLE CAUSES Missing required data Invalid data format Inconsistent data elements
OPERATOR RESPONSE

Read the returned error information, identify the affected data and correct the submission according to the applicable technical specifications.

03 / CUSTOMS PROCESSING

Control or customs intervention

An accepted declaration may require verification, supporting documents or examination before customs release.

POSSIBLE SITUATIONS Documentary verification Physical examination Request for additional information
OPERATOR RESPONSE

Follow the customs instructions. A control notification must not be treated as a technical rejection or as permission to move the goods.

04 / STATUS RECONCILIATION

Missing or delayed response

The trader’s software may not display an expected response even when processing has progressed in the customs system.

POSSIBLE CAUSES Delayed electronic notification Local software synchronisation issue Unresolved processing state
OPERATOR RESPONSE

Reconcile the available message history with the authoritative customs status before taking further action.

OPERATIONAL DECISION MODEL

What should you check first?

The same visible symptom can have different causes. Use the communication evidence to identify the correct next step.

01
Was the message transmitted?

Check the sending system’s transmission records and available acknowledgements.

02
Was the submission accepted or rejected?

Distinguish technical receipt, validation results and legal customs acceptance.

03
Is customs processing still ongoing?

Identify controls, pending requests, release decisions and other relevant events.

04
Does the displayed status match customs records?

Resolve inconsistencies before assuming that a message must be resent or a new declaration submitted.

CRITICAL OPERATIONAL RULE

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.

DIGITAL TRACEABILITY / EXPORT RECORDS

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.

ILLUSTRATIVE MESSAGE HISTORY

One declaration. Multiple recorded events.

AUDIT VIEW
REFERENCE KEY MRN Movement Reference Number
DECLARATION IDENTIFIER Assigned upon acceptance
01
SUBMISSION RECORD TRADER → CUSTOMS

Declaration transmitted

Record the submission reference, transmission time and available delivery or validation information.

02
ACCEPTANCE EVENT CUSTOMS → TRADER

Declaration accepted

Associate the allocated MRN with the accepted declaration and its relevant acceptance information.

03
RELEASE EVENT CUSTOMS → TRADER

Release communicated

Preserve the release communication and distinguish its date and meaning from the later exit-related events.

04
EXIT PROCESSING CUSTOMS ↔ CUSTOMS

Exit information exchanged

Where accessible, reconcile relevant exit-related information with the declaration and transport records.

05
FINAL EVIDENCE CUSTOMS → TRADER

Exit certification retained

Preserve the customs certification of exit when issued, together with the supporting commercial and transport documentation.

DOCUMENTARY EVIDENCE

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.

AES MESSAGES / KNOWLEDGE CENTER

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.

CUSTOMS EXPLORER / AES KNOWLEDGE HUB

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.

BACK TO AES HUB