Customs Explorer
⌕

Customs Explorer

AES rollout

EU CUSTOMS DIGITAL TRANSFORMATION

AES Rollout. From transition to operation.

The transition from the Export Control System (ECS-P2) to the Automated Export System (AES) transformed how export declarations, customs decisions and exit information are exchanged across the European Union.

The EU-wide transition for AES core functionalities concluded in December 2025. The next challenge is understanding the operational environment, national implementation differences and the continuing deployment of additional features.

ECS-P2 migration AES-P1 deployment EU interoperability National implementation
EU EXPORT SYSTEM EVOLUTION EU / AES
PREVIOUS SYSTEM
ECS-P2

Export Control System — Phase 2

LEGACY EXPORT ENVIRONMENT
EU-WIDE CORE OPERATION
AES

Automated Export System

INTERCONNECTED NATIONAL SYSTEMS
15 DECEMBER 2025 EU-wide AES core deployment achieved
MILESTONE
01 / CORE FUNCTIONALITIES 1 Dec 2023

Original deployment milestone for core AES capabilities.

02 / NON-CORE FUNCTIONALITIES 2 Dec 2024

Work Programme milestone for additional AES capabilities.

03 / TRANSITION END 14 Dec 2025

End of the extended EU transitional arrangements.

04 / EU-WIDE CORE OPERATION 15 Dec 2025

All Member States operating AES core functionalities.

Deployment milestone does not mean identical national functionality.

The EU-wide rollout of AES core functionalities is complete. National trader interfaces, software connectivity and certain non-core functionalities may still differ. Historical deployment deadlines must not be mistaken for current national operating instructions.

OFFICIAL BASIS

European Commission reporting on the UCC electronic systems programme and Commission Implementing Regulation (EU) 2025/512, Article 56.

EU deployment progress report ↗ Implementing Regulation 2025/512 ↗
SYSTEM EVOLUTION / TECHNICAL COMPARISON

ECS-P2 vs AES-P1. More than a system replacement.

AES Phase 1 introduced changes to declaration data, electronic exchanges and customs business processes to support the requirements of the Union Customs Code. The transition required customs administrations and economic operators to adapt their systems and workflows.

PREVIOUS ENVIRONMENT LEGACY
ECS-P2

Export Control System — Phase 2

The previous trans-European export environment, based on its earlier declaration data structure and electronic message specifications.

PRE-AES TECHNICAL FRAMEWORK
MODERNISED ENVIRONMENT AES-P1
AES

Automated Export System — Phase 1

A modernised framework supporting UCC-aligned export and exit processes, structured data requirements and electronic interoperability between national customs systems.

UCC-ALIGNED EXPORT PROCESSING
Area ECS-P2 AES-P1
01 Declaration data Earlier declaration structure, formats and data requirements. Revised data groups and elements aligned with UCC Annex B and EUCDM.
02 Electronic messages Previous ECS message specifications and validation arrangements. Updated message structures, rules and exchanges for AES processes.
03 Export procedures Earlier processes and supported export scenarios. Revised procedures and support for additional UCC export scenarios.
04 Exit processing Existing electronic export and exit supervision workflows. Updated exit, enquiry and related communication processes.
05 Interoperability Previous trans-European export communication environment. Updated national AES exchanges, with interfaces to other customs and excise systems where applicable.
06 Trader connectivity National ECS interfaces and previous software integrations. National AES trader portals and updated integration requirements.

This comparison describes the evolution of the common framework. It does not imply that every function was absent from ECS-P2 or introduced simultaneously in every Member State.

DECLARATION DATA MODEL

The structural change behind AES.

One of the most significant changes was the adaptation of declaration information to the data requirements defined by the Union Customs Code and represented in the EU Customs Data Model.

AES EXPORT DECLARATION — CONCEPTUAL STRUCTURE
LEVEL 01 Export Operation Declaration-level information
LEVEL 02 Goods Shipment Shipment-level information
LEVEL 03 Goods Item Item-specific information
LEVEL 03 Goods Item Additional item, if applicable

Simplified illustration of the three-level declaration structure described in AES Business Guidance. Actual message schemas contain additional groups, elements and validation rules.

01 / NEW UCC CAPABILITY

Centralised Clearance at Export

Supports the UCC framework for lodging declarations with a supervising customs office while goods may be presented at another customs office, subject to the applicable conditions and deployment.

02 / SYSTEM INTERFACE

AES and EMCS

Provides for electronic interaction between export processing and the excise movement environment in relevant export scenarios.

03 / SYSTEM INTERFACE

AES and NCTS

Supports coordination between export and transit procedures where the relevant customs scenario requires it.

04 / DECLARATION PROCESSING

Simplified and supplementary declarations

Incorporates dedicated processing arrangements for relevant simplified export declaration scenarios under the UCC framework.

05 / ADAPTED PROCESS

Amendment and invalidation

Existing declaration management processes were revised to reflect updated UCC rules and AES electronic specifications.

06 / ADAPTED PROCESS

Exit and enquiry procedures

Electronic procedures for exit supervision, communication and investigation were updated within the AES environment.

EU HARMONISATION / NATIONAL IMPLEMENTATION

Common rules do not mean one common trader portal.

AES combines trans-European communication components with national customs systems. Economic operators interact through national trader interfaces and applicable national connectivity arrangements. Consequently, software onboarding, authentication and operational instructions must be checked with the relevant customs administration.

EU DEPLOYMENT / HISTORICAL TIMELINE

The AES rollout. Planned, extended, completed.

The deployment of the Automated Export System followed a phased EU programme. Initial milestones were followed by national implementation delays, transitional interoperability arrangements and the eventual completion of EU-wide core deployment.

DEPLOYMENT HISTORY 2023 — 2026
01
1 DECEMBER 2023 PROGRAMME MILESTONE

Core functionalities milestone

The UCC Work Programme established this milestone for AES core functionalities. National deployments were progressing, but the date did not represent a simultaneous EU-wide go-live.

INTERPRETATION Planned milestone, not EU-wide completion
02
2 DECEMBER 2024 DEPLOYMENT DEADLINE

Broader AES deployment deadline

The Work Programme set this deadline for the wider deployment of AES. However, some national administrations and economic operators had not completed their transition.

INTERPRETATION Legal programme deadline with outstanding migrations
03
11 FEBRUARY 2025 ORIGINAL TRANSITION END

Previously scheduled end of transitional rules

The 2023 Work Programme envisaged the end of the AES Component 1 transitional arrangements on this date. Subsequent delays led to an extension through a separate legal measure.

INTERPRETATION Superseded transition date
04
13 MARCH 2025 LEGAL ADAPTATION

Extended interoperability arrangements

Commission Implementing Regulation (EU) 2025/512 was adopted, providing for continued transitional mechanisms until 14 December 2025. These included common components and message conversion supporting communication between different deployment environments.

INTERPRETATION Business continuity during staggered national migration
05
14 DECEMBER 2025 TRANSITION END

Extended transitional period concluded

The extended EU arrangements allowing temporary interoperability with Member States still migrating to AES reached their specified end date.

INTERPRETATION End of the extended EU transition mechanism
06
15 DECEMBER 2025 CONFIRMED OUTCOME

EU-wide AES core deployment achieved

The European Commission reported that all Member States had deployed AES core functionalities. Portugal, France and Greece were among the last administrations to complete this stage.

INTERPRETATION Confirmed EU-wide core operational milestone
HOW THE TRANSITION WORKED

Two system environments. One continuing export flow.

During the authorised transitional period, temporary conversion mechanisms helped maintain electronic communication between administrations operating in different technical environments.

LEGACY ENVIRONMENT ECS-P2 Member States still migrating
TRANSITIONAL CONVERSION Temporary interoperability support
MODERNISED ENVIRONMENT AES Member States already deployed
Historical architecture: this diagram illustrates the temporary interoperability arrangements under Article 56 of Implementing Regulation (EU) 2025/512. It does not represent the current production architecture or imply that the central converter remains in operation.
WHAT THIS MEANS FOR ECONOMIC OPERATORS

Three lessons from the rollout.

01 / SYSTEM READINESS

EU dates and national readiness are different.

A common EU deployment programme does not eliminate the need to consult national customs instructions and implementation notices.

02 / SOFTWARE CONNECTIVITY

Trader migration required local adaptation.

Declaration software, national interfaces, validation rules and electronic message exchanges had to be adapted to the relevant AES environment.

03 / ONGOING DEVELOPMENT

Core deployment is not the final feature milestone.

Businesses should distinguish functions already operational from additional capabilities still subject to national implementation schedules.

OFFICIAL REFERENCES

Commission Implementing Decision (EU) 2023/2879 established the deployment programme. Commission Implementing Regulation (EU) 2025/512, Article 56, provided the extended transitional mechanisms. The Commission’s 2026 progress reporting documents the EU-wide completion of AES core deployment and outstanding non-core work.

MEMBER STATE IMPLEMENTATION / OPERATIONAL GUIDE

One European framework. Different national entry points.

AES supports harmonised electronic export processes across the European Union. Yet traders access the system through national customs environments, where authentication, technical onboarding and operational instructions are managed by the relevant administration.

EUROPEAN INTEROPERABILITY MODEL

How national AES systems connect.

CONCEPTUAL ARCHITECTURE
COMMON EU COMPONENTS European communication network

Enables electronic communication between national AES systems.

EU COMMON DOMAIN
MEMBER STATE A
National AES
National trader portal
Economic operator
MEMBER STATE B
National AES
National trader portal
Economic operator
MEMBER STATE C
National AES
National trader portal
Economic operator

Illustrative representation, not a network topology diagram. Each Member State operates its national AES components while using the common communication infrastructure for relevant cross-border exchanges.

OPERATIONAL DIFFERENCES

What may vary between Member States?

EU legislation establishes the common framework. The practical method of connecting to national customs systems may nevertheless differ.

01

Trader portal

The national web environment used to exchange information with customs, including the available declaration and consultation functions.

NATIONAL INTERFACE
02

Authentication

User registration, access verification, delegation and authentication arrangements determined by the Member State.

ACCESS CONTROL
03

Software connectivity

Technical connection procedures, integration documentation, onboarding requirements and test environments.

TECHNICAL ONBOARDING
04

Validation implementation

EU data requirements are common, while applicable national technical specifications and additional validation conditions must be checked.

DATA VALIDATION
05

Additional functionalities

The implementation status of certain non-core capabilities may differ, including relevant interfaces and centralised clearance functions.

FEATURE AVAILABILITY
06

Operational support

National helpdesks, maintenance notices, contingency instructions and procedures for resolving technical issues.

BUSINESS CONTINUITY
PRACTICAL VERIFICATION

Before using AES in another Member State.

Exporters, customs representatives and software providers should establish which national procedures and interfaces apply to their specific operations.

Important distinction

A national system being operational does not automatically establish that a particular trader is registered, authorised or technically connected to use every available function.

NATIONAL AES READINESS CHECKLIST
01
Identify the competent customs administration

Confirm the Member State and the customs office arrangements relevant to the declaration.

02
Locate the official national AES guidance

Consult the customs authority’s published operating instructions and technical documentation.

03
Verify access and representation

Check authentication, registration and any relevant representation or delegation arrangements.

04
Confirm the technical connection method

Establish whether the applicable interface and software integration are available to the operator.

05
Check the required functionality

Verify support for the relevant declaration scenario and any non-core or cross-system features.

06
Review contingency and support procedures

Identify the national instructions applicable when the normal electronic service is unavailable.

EU DEPLOYMENT STATUS / INTERPRETATION

Core operation and additional capabilities are separate milestones.

CORE AES EU-wide deployment achieved

The Commission reported all Member States operating AES core functionalities by 15 December 2025.

NON-CORE AES National schedules may differ

The Commission’s 2026 reporting identifies further deployment work for certain additional functionalities in individual Member States.

This is a distinction between deployment categories, not a real-time availability check for any specific country or feature.

OPERATIONAL READINESS / IMPLEMENTATION CONTROLS

AES migration checklist. From go-live to reliable operations.

A successful AES implementation is not measured only by the ability to submit an export declaration. Reliable operations require correct data, working electronic exchanges, clear responsibility for exceptions and a documented approach to system unavailability.

OPERATIONAL READINESS MODEL

Six control areas. One dependable export process.

Use this framework when connecting a new software solution, changing a customs service provider, deploying an additional AES feature or reviewing an existing national implementation.

06 CONTROL AREAS
18 VERIFICATION POINTS
01 OPERATIONAL OBJECTIVE
CONTROL AREA 01 01

Access & authorisation

Confirm that the operator can access the appropriate national AES environment and act in the intended customs capacity.

  • Verify the relevant EORI and trader identity.
  • Confirm national portal access and authentication.
  • Review representation, delegation and applicable authorisations.
CONTROL AREA 02 02

Declaration data & mapping

Establish whether source-system data correctly populate the fields required for the relevant AES declaration scenario.

  • Review applicable Annex B data requirements.
  • Check mapping, code lists and conditional data rules.
  • Validate item, shipment and declaration-level information.
CONTROL AREA 03 03

Messages & integration

Verify that the connection can transmit, receive, interpret and retain the relevant national AES communications.

  • Test submission, validation and acceptance outcomes.
  • Confirm receipt and interpretation of customs responses.
  • Check message correlation, duplicate handling and error logging.
CONTROL AREA 04 04

Export lifecycle & exit

Check that users understand the difference between declaration acceptance, release and certification of exit.

  • Test status updates and MRN correlation.
  • Verify the process for obtaining exit information.
  • Assign responsibility for unresolved export movements.
CONTROL AREA 05 05

Cross-system scenarios

Test additional procedures and interfaces only where they are relevant to the operator and supported by the applicable national implementation.

  • Assess export followed by transit through NCTS.
  • Assess excise movements involving EMCS.
  • Check simplified procedures and centralised clearance where applicable.
CONTROL AREA 06 06

Continuity & governance

Prepare the organisation to manage technical incidents, changing specifications and the retention of customs records.

  • Identify applicable national fallback instructions.
  • Define incident ownership, escalation and recovery.
  • Maintain version control and accessible customs records.
END-TO-END VERIFICATION

Do not stop testing when an MRN appears.

An accepted declaration is an important milestone, but it does not demonstrate that the entire export process has been completed successfully.

Common implementation mistake

Treating successful submission or MRN allocation as sufficient evidence that the system is ready for every operational export scenario.

EXPORT PROCESS / TEST COVERAGE
01
Declaration submission

Correct data transmitted to the national system.

INPUT
02
Customs acceptance

Acceptance response and MRN correctly recorded.

REFERENCE
03
Release for export

Release decision recognised and distinguished from acceptance.

DECISION
04
Exit processing

Relevant customs exit information handled correctly.

EVENT
05
Exit certification & records

Final customs outcome recorded and supporting evidence retained.

OUTCOME
Conceptual test sequence. Actual electronic exchanges, control decisions and exit scenarios depend on the applicable customs process and national specifications.
NEGATIVE TESTING / EXCEPTION MANAGEMENT

Four situations that deserve a test before production.

Positive test cases demonstrate that normal processing works. Negative tests help establish whether errors can be detected, investigated and resolved.

SCENARIO 01

Declaration rejected

Confirm that the user receives an understandable error and can identify the data or rule requiring attention.

VERIFY: VALIDATION & CORRECTION
SCENARIO 02

Response delayed or missing

Confirm that the software distinguishes a pending response from a rejected declaration and avoids uncontrolled duplicate submissions.

VERIFY: STATUS & RETRY CONTROL
SCENARIO 03

Exit not certified

Confirm that the operator can identify unresolved movements, investigate available information and follow the applicable customs enquiry process.

VERIFY: FOLLOW-UP & EVIDENCE
SCENARIO 04

Electronic service unavailable

Confirm that staff know the official national contingency procedure and the conditions for its use.

VERIFY: CONTINUITY & RECOVERY
BUSINESS CONTINUITY / IMPORTANT DISTINCTION

Fallback procedures are not interchangeable across Member States.

The European Commission’s AES Business Continuity Plan addresses common-domain communications and recommends arrangements for external-domain exchanges. Measures governing communication between traders and customs authorities are determined by the relevant national administration. A business must therefore follow the applicable official national instructions, rather than assuming that a self-created offline procedure is authorised.

READINESS ASSESSMENT

What should an internal sign-off actually confirm?

A practical internal approval can record the following outcomes before a new implementation or material software change is placed into routine use.

Applicable rules identified

EU and national requirements are understood.

Relevant scenarios tested

Normal and exceptional processing have been assessed.

Responsibilities assigned

Errors, follow-up and incidents have clear owners.

Evidence retained

Test results and operating instructions remain accessible.

This sign-off model is an organisational recommendation. It is not an EU-prescribed AES certification, an official customs authorisation or a substitute for mandatory national conformance testing where required.

LEGAL AND TECHNICAL REFERENCES

Commission Implementing Regulation (EU) 2025/512, Articles 50–55, establishes the AES architecture and national components. UCC Regulation (EU) No 952/2013 governs customs declarations, decisions, records and export supervision. The European Commission’s AES Business Guidance and Business Continuity Plan provide explanatory and operational guidance; they do not replace binding legislation or applicable national instructions.

AES ROLLOUT / FREQUENTLY ASKED QUESTIONS

AES rollout. Questions that still matter.

The main EU transition milestones are historical, but businesses still need to understand the differences between ECS and AES, national connectivity, additional functionalities and the requirements of a reliable export process.

01 What is the AES rollout?

The AES rollout is the deployment of the Automated Export System across EU customs administrations, replacing the previous ECS-P2 environment with an updated system aligned with the Union Customs Code. It includes revised declaration data, electronic exchanges, export processes and interfaces with other customs systems.

02 What is the difference between ECS-P2 and AES-P1?

ECS-P2 was the previous electronic export environment. AES-P1 modernised its business processes and technical specifications to implement UCC data requirements and support additional export functionalities. Not every export or exit process was newly created by AES; several existing processes were revised or extended.

03 When did the EU transitional period for AES end?

Article 56 of Commission Implementing Regulation (EU) 2025/512 provided for transitional interoperability mechanisms until 14 December 2025. The earlier transition date of 11 February 2025 was superseded by the extension.

04 Is AES fully implemented in every EU Member State?

The European Commission reported EU-wide deployment of AES core functionalities from 15 December 2025. However, core deployment should not be confused with identical availability of every additional functionality. Operators should consult national customs guidance for the capabilities relevant to their operations.

05 Is there a single EU AES portal for exporters?

No single EU-wide trader portal replaces the national AES entry points. The AES architecture includes national trader portals and national export systems, connected through common communication components for the relevant exchanges. Access arrangements are determined by the applicable national environment.

06 Does AES support export followed by transit?

AES includes an interface with the New Computerised Transit System (NCTS) for relevant export-followed-by-transit scenarios. The applicable processing depends on the customs procedure, implementing rules and available national functionality. Export and transit remain distinct customs procedures.

07 What is the relationship between AES and EMCS?

AES provides for electronic interaction with the Excise Movement and Control System (EMCS) in relevant movements involving excise goods. The interface supports coordination between customs export processing and applicable excise movement procedures.

08 Does an existing exporter need to migrate again?

Completion of the EU-wide core rollout does not create a new general migration requirement for operators already correctly connected to their national AES. Further action may nevertheless be needed when national specifications change, additional functions become available or the operator changes its software or customs service provider.

09 Where can I find the technical requirements for AES?

Start with the European Commission’s AES documentation and the applicable UCC legislation. For implementation, consult the relevant national customs authority’s technical specifications, message documentation, access requirements and testing procedures. EU-level guidance alone may not provide everything required for a national software connection.

10 What should an exporter check after AES go-live?

Confirm that declarations are correctly accepted, customs responses are received and interpreted, release is distinguished from exit certification, unresolved movements can be investigated and applicable contingency instructions are available. These checks are recommended operational controls, not a separate EU certification scheme.

THE ESSENTIAL DISTINCTION

Three milestones. Three different meanings.

01 / PROGRAMME Deployment deadline

The date established in the EU electronic systems work programme.

02 / TRANSITION Interoperability period

Temporary arrangements supporting communication during migration.

03 / OPERATION Actual deployment

The operational milestone achieved by the customs administrations.

A completed core rollout does not establish that every non-core feature is available in every national implementation.

CUSTOMS EXPLORER / EU DIGITAL CUSTOMS

AES deployment is a milestone. Operational reliability is continuous.

Understanding the rollout is only the beginning. Effective export operations depend on accurate data, reliable electronic exchanges and a clear understanding of customs outcomes.

BACK TO AES HUB