Commission européenne/Europese Commissie, 1049 Bruxelles/Brussel, BELGIQUE/BELGIË - Tel. +32 22991111 PDF
Vsebina
Commission européenne/Europese Commissie, 1049 Bruxelles/Brussel, BELGIQUE/BELGIË - Tel. +32 22991111
EUROPEAN COMMISSION
DIRECTORATE-GENERAL
TAXATION AND CUSTOMS UNION
Digital Delivery of Customs and Taxation Policies
Processes and Data, Customer Relationship and Planning
FUNCTIONAL SYSTEM
SPECIFICATIONS – AES DOCUMENT
SECTION I A: BUSINESS PROCESS THREADS
FOR CORE BUSINESS
Date: 15/05/2025
Status: Submitted for acceptance (SfA)
Version: 7.10 EN
Author: SOFT-DEV
Approved by: DG TAXUD
Reference number: DLV-820-5.5-6-1-4
Public: DG TAXUD external
Confidentiality: Commission use (CU)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page ii / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
Document control information
Property Value
Title FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT
Subtitle SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS
Author SOFT-DEV
Project owner Head of Unit of DG TAXUD Unit B1 Processes & Data, Customer
Relationship and Planning
Solution provider DG TAXUD Unit B3 Customs Systems
DG TAXUD Project Manager Head of Unit of DG TAXUD Unit B3 Customs Systems
Version 7.10EN
Confidentiality Commission use (CU)
Date 15/05/2025
Contract information
Property Value
Framework Contract TAXUD/2021/CC/162
Specific Contract SC09
Document history
The document author is authorised to make the following types of changes to the document without
requiring that the document be re-approved:
• Editorial, formatting, and spelling.
• Clarification.
To request a change to this document, contact the document author or project owner.
Changes to this document are summarised in the table in reverse chronological order (latest version
first).
Version Date Description Action Section
7.10 15/05/2025 Re-Submitted for Acceptance (SfA) to Taxation and
Customs Union DG. (QC56417)
I/R As required
7.00 29/04/2025 Implementing RfE820.
Submitted for Acceptance (SfA) to Taxation and
Customs Union DG. (QC56417)
I/R As required
6.10 07/04/2025 Implementing RfE820.
Submitted for Review (SfR) to Taxation and Customs
Union DG.
I/R As required
6.00 30/01/2024 Implementing RfE428.
Submitted for Acceptance (SfA) to Taxation and
Customs Union DG.
I/R As required
5.10 16/01/2024 Implementing RfE428.
Submitted for Review (SfR) to Taxation and Customs
Union DG.
I/R As required
5.00 25/11/2022 Implementing QA4 review comments.
Submitted for Acceptance (SfA) to Taxation and
Customs Union DG.
I/R As required
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page iii / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
Version Date Description Action Section
4.10 09/11/2022 Submitted for Review (SfR) to Taxation and Customs
Union DG, after External Verification.
I/R As required
4.00 28/09/2022 Implementing QA4 review comments.
Submitted for Acceptance (SfA) to Taxation and
Customs Union DG.
I/R As required
3.40 20/09/2022 Implementing RfE074.
Submitted for Review (SfR) to Taxation and Customs
Union DG.
I/R As required
3.30 19/07/2021 Implementing QA4 review comments.
Submitted for Acceptance (SfA) to Taxation and
Customs Union DG.
I/R As required
3.20 06/07/2021 Implementing comments from External Verification.
Submitted for Review (SfR) to Taxation and Customs
Union DG.
I/R As required
3.10 12/04/2021 Implementing QA4 and DG TAXUD review comments.
Submitted for Acceptance (SfA) to Taxation and
Customs Union DG.
I/R As required
3.00
10/03/2021
Implementing QTM008.
Submitted for Review (SfR) to Taxation and Customs
Union DG.
I/R As required
Action: I=Insert R=Replace
*Previous Document History before v3.00 is not available.
Configuration management: document location
The latest accepted version of this controlled document is stored on: CIRCABC
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page iv / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
Table of contents
1. INTRODUCTION 4
2. AES – CORE BUSINESS PROCESSES 5
2.1 Export Process 5
2.2 Exit Summary Process 5
2.3 Re-Export Notification 5
2.4 Interfaces with other IT Systems 6
2.4.1 Risk Analysis System 6
2.4.2 EOS – ECONOMIC Operator Systems 6
2.4.3 UCC Customs Decisions 6
2.4.4 UCC NCTS 7
2.4.5 EMCS 7
2.5 L4-EXP-01-01-Customs Formalities at Office of Export-Acceptance and Controls 9
2.6 L4-EXP-01-02-Customs Formalities at Office of Export-Release 23
2.7 L4-EXP-01-04-Supplementary Declaration 27
2.8 L4-EXP-01-05-Amendment of the Export Declaration 32
2.9 L4-EXP-01-07-Customs Formalities at Office(s) of Exit-Process Exit 36
2.10 L4-EXP-01-08-Enquiry Procedure 41
2.11 L4-EXP-01-16-Operation Information Query 47
2.12 L4-EXP-01-17-Operation Status Check 51
2.13 L4-EXP-01-19-Handle Diversion 55
2.14 L4-EXP-01-21-Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods 62
2.15 L4-EXP-01-23-Customs Formalities at Office of Export-Handle Exit Results/Alternative
Evidence 66
2.16 L4-EXP-01-24-Customs Formalities at Office(s) of Exit-Process Arrival Notification 72
2.17 L4-EXP-01-25-Process Transit Release Notification 74
2.18 L4-EXP-01-26-Export Declaration Invalidation 81
2.19 L4-EXP-01-27-Handle Goods Movement Additional information 88
3. AES – EXIT SUMMARY DECLARATION 92
3.1 Introduction 92
3.2 L4-EXP-01-10-Exit Summary Declaration-Process Registration and Arrival 93
3.3 L4-EXP-01-11-Exit Summary Declaration-Process Exit 102
3.4 L4-EXP-01-12-Amendment of Exit Summary Declaration 106
3.5 L4-EXP-01-22-Exit Summary Declaration/Re-Export Notification Invalidation 109
4. AES – RE-EXPORT NOTIFICATION 112
4.1 Introduction 112
4.2 L4-EXP-01-13-Re-Export Notification-Process Registration 113
4.3 L4-EXP-01-14-Re-Export Notification-Process Exit 119
4.4 L4-EXP-01-15-Amendment of the Re-Export Notification 123
5. INDEX OF EBPS 127
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page v / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
Table of Figures
Figure 1: Overview of AES Master Process ............................................................................................................ 8
Figure 2: L4-EXP-01-01-Customs Formalities at Office of Export-Acceptance and Controls (Part A) .................. 9
Figure 3: L4-EXP-01-01-Customs Formalities at Office of Export-Acceptance and Controls (Part B) ................ 10
Figure 4: L4-EXP-01-02-Customs Formalities at Office of Export-Release (Part A) ........................................... 23
Figure 5: L4-EXP-01-02-Customs Formalities at Office of Export-Release (Part B) ........................................... 24
Figure 6: L4-EXP-01-04-Supplementary Declaration (Part A) ............................................................................. 27
Figure 7: L4-EXP-01-04-Supplementary Declaration (Part B) .............................................................................. 28
Figure 8: L4-EXP-01-05-Amendment of the Export Declaration (Part A) ............................................................ 32
Figure 9: L4-EXP-01-05-Amendment of the Export Declaration (Part B) ............................................................ 32
Figure 10: L4-EXP-01-05-Amendment of the Export Declaration (Part C) .......................................................... 33
Figure 11: L4-EXP-01-07-Customs Formalities at Office(s) of Exit-Process Exit ................................................ 36
Figure 12: L4-EXP-01-08-Enquiry Procedure (Part A) ......................................................................................... 41
Figure 13: L4-EXP-01-08-Enquiry Procedure (Part B) ......................................................................................... 42
Figure 14: L4-EXP-01-16-Operation Information Query ...................................................................................... 47
Figure 15: L4-EXP-01-17-Operation Status Check ............................................................................................... 51
Figure 16: L4-EXP-01-19-Handle Diversion (Part A) ........................................................................................... 55
Figure 17: L4-EXP-01-19-Handle Diversion (Part B) ........................................................................................... 56
Figure 18: L4-EXP-01-21-Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods (Part
A) .................................................................................................................................................................. 62
Figure 19: L4-EXP-01-21-Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods (Part
B) .................................................................................................................................................................. 62
Figure 20: L4-EXP-01-23-Customs Formalities at Office of Export-Handle Exit Results/Alternative Evidence
(Part A) ......................................................................................................................................................... 66
Figure 21: L4-EXP-01-23-Customs Formalities at Office of Export-Handle Exit Results/Alternative Evidence
(Part B) ......................................................................................................................................................... 67
Figure 22: L4-EXP-01-24-Customs Formalities at Office(s) of Exit-Process Arrival Notification ....................... 72
Figure 23: L4-EXP-01-25-Process Transit Release Notification (Part A) ............................................................. 74
Figure 24: L4-EXP-01-25-Process Transit Release Notification (Part B) ............................................................. 75
Figure 25: L4-EXP-01-25-Process Transit Release Notification (Part C) ............................................................. 76
Figure 26: L4-EXP-01-26-Export Declaration Invalidation (Part A) .................................................................... 81
Figure 27: L4-EXP-01-26-Export Declaration Invalidation (Part B) ..................................................................... 82
Figure 28: L4-EXP-01-26-Export Declaration Invalidation (Part C) ..................................................................... 83
Figure 29: L4-EXP-01-27-Handle Goods Movement Additional Information (Part A) ........................................ 88
Figure 30: L4-EXP-01-27-Handle Goods Movement Additional Information (Part B) ........................................ 88
Figure 31: L4-EXP-01-10-Exit Summary Declaration-Process Registration and Arrival (Part A) ....................... 93
Figure 32: L4-EXP-01-10-Exit Summary Declaration-Process Registration and Arrival (Part B) ........................ 94
Figure 34: L4-EXP-01-11-Exit Summary Declaration-Process Exit ................................................................... 102
Figure 35: L4-EXP-01-12-Amendment of Exit Summary Declaration ............................................................... 106
Figure 36: L4-EXP-01-22-Exit Summary Declaration/Re-Export Notification Invalidation .............................. 109
Figure 37: L4-EXP-01-13-Re-Export Notification-Process Registration (Part A) .............................................. 113
Figure 38: L4-EXP-01-13-Re-Export Notification-Process Registration (Part B) ............................................... 114
Figure 39: L4-EXP-01-14-Re-Export Notification-Process Exit ......................................................................... 119
Figure 40: L4-EXP-01-15-Amendment of the Re-Export Notification (Part A).................................................. 123
Figure 41: L4-EXP-01-15-Amendment of the Re-Export Notification (Part B) .................................................. 124
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 4 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
1. INTRODUCTION
What is this document used for?
The Functional System Specifications (FSS) are to be regarded as the basis for the development of the technical
specifications (e.g. DDNA – 'Design Document for National Application' and 'Scope' document).
What is included in this document?
Following the adoption of the Union Customs Code Delegated (No 2015/2446) and Implementing Acts (No
2015/2447), there was a clear need for the evolution of the Export Customs Application. This evolution requires
changes both on Business Processes and Infor mation Exchanges (IEs). The present Document is aligned to these
new UCC requirements (see publication in ARIS platform ‘ SC09_820_5_5_6_1_3_AES_L4 BPM SfR’). This
Document also covers the scope of the system for AES P1 as identified by the MASP (Multi Annu al Strategic
Plan).
The FSS main chapters are:
• The core business process threads for the processing of Export Customs declaration within the Automated
Export System (AES) (heading 2).
• The core business process threads for the Exit Summary Declaration within AES (heading 3).
• The core business process threads for the Re-Export Notification declaration within AES (heading 4).
This Document also provides the guidelines for the 'external domain' relating to communication between Traders
and National Customs Administrations and for the 'national domain' relating to processes on national systems.
What is not included in this document?
The FSS does not include SEAP -aspects (Single European Access Point). However, some of the functionalities
shall be provided already by the described system as concerns the lodgement of Export declarations and Exit
Summary Declaration in one Member State being forwarded to another Member State. In addition, the introduction
of amendments of the Exit Summary Declaration via a representative in a country other than the country of
Lodgement is described.
Supporting Material:
The following Annexes -as part of The EU Customs Functional Requirements BPM Report- can be used to support
the reading of this document.
• Annex 1: Model Graphics, providing all L4 BPM models.
• Annex 2: Glossary, providing a list of basic terms with their meanings applicable across all domains /
levels within the EU Customs Business Processes.
• Annex 3: Requirements, providing a list of all requirements for the system covered .
In addition, the Information Exchange objects referenced in the processes are those defined in the DDNXA
Appendix Q2 – Technical Message Structure.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 5 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
2. AES – CORE BUSINESS PROCESSES
This introduction provides a description of the core business which is rather intended to highlight the major process
threads of the core business and the links that exist between them.
The major process threads are:
• Process export.
• Process exit.
These process threads are inter-dependent: the processing of an export declaration or a re-export declaration at the
Office of Export if followed by the processing of the exit of a movement at the Office of Exit. The ‘link’ between
those two processes is t he transportation of the consignment from the Office of Export to the Office of Exit. A
consignment is the total number of items specified in the commercial contract between the supplier and the
customer and transported in a single or in multiple shipments.
2.1 EXPORT PROCESS
The export declaration message (IE515) is sent to the Customs Office of Export. The Declarant /Representative
receives the IE528 after acceptance of the export declaration and information regarding the means of transport
carrying the consignment covered by this message is transmitted to the Customs Office of Exit via IE501 after the
release of the goods at export.
Normally, the consignment arrives at the Office of Exit. The goods are presented to the Actual Office of Exit
which processes the exit of the goods. Once the exit processing is completed, the Office of Export finalises the
export operation.
Unless human intervention is specifically required by national policy, AES will allow fully automated processing
of:
• Process export (from declaration reception to release for export).
• Process exit (from presentation to exit of the goods).
• Finalise export operation.
Note: In Export Process models, in case the declaration concerns Centralised Clearance then the pool name/actor
"Customs Offices of Export" acts as the "Supervising Customs Office".
2.2 EXIT SUMMARY PROCESS
The exit summary declaration message (IE615) is sent to the Customs Office of Exit. The Person Lodging the Exit
Summary declaration receives the IE628 after acceptance of the exit summary declaration. If the declaration was
lodged at an office different than the office of exit, then information regarding the means of transport carrying the
consignment and the other declaration data is transmitted to the Customs Office of Exit via IE601 immediately
upon accepting the declaration.
In either case, the goods are presented to the Office of Exit, controlled if necessary and finally the goods are
released for exit.
2.3 RE-EXPORT NOTIFICATION
The Re-Export Notification message (IE570) is sent to the Customs Office of Exit. The Person lodging the Re -
Export Notification receives the Re -Export Notification Registration notification (IE571) after acceptance of the
IE570.
After the registration of the Re-Export notification the processing of the exit takes place. The goods are controlled
if necessary and the goods are finally released for exit.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 6 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.4 INTERFACES WITH OTHER IT SYSTEMS
2.4.1 RISK ANALYSIS SYSTEM
• National risk analysis is to be understood as other than common safety and security risk analysis (e.g.
fiscal or additional safety and security risk analysis based on national provisions). This is a national
matter.
• AES interfaces with the national risk analysis systems of the Member States and ensures that risks
analysis is initiated once the data is received and validated by the AES.
• The national risk analysis systems of the Member States carry out the required risk analysis and send the
risk analysis results together with control recommendation back to AES.
• Risk analysis result codes, control recommendation codes, control types and control result codes are
defined on an EU level and are managed in the national risk analysis systems . The way how the risk
analysis is conducted by MS, is not depicted in AES.
• AES forwards the risk analysis results, control recommendations and control results related to a specific
transaction to the relevant Customs Offices involved in the process.
2.4.2 EOS – ECONOMIC OPERATOR SYSTEMS
• Where the regulation requires Traders to be registered in the common EORI database, UCC IA Article 7
specifies that for the exchange and storage of information pertaining to EORI, an electronic system will
be used. AES will validate the EORI referenced numbers in the declarations, e.g. R0840 defines such a
case.
• Where facilitations are granted in the framework of a third country traders’ partnership programme which
is recognised by the Union, this information may take the form of a third country unique identification
number (TCUIN) which has been made available to the Union by the third country concerned. That
number may be used whenever available to the person lodging the Exit Summary Declaration.
• Where EORI registered Traders are to be declared in an AES message, the EORI number shall be
declared.
• When validating a received AES message, AES consults the EOS database in order to check the provided
EORI number.
• If the declared EORI number or TCUIN number is not valid or if it is not declared where it is required or
if the exporter and/or declarant is not established in the customs territory of the Union , AES rejects the
declaration and/or notification data set using the appropriate AES error/rejection message .
• Authorised Economic Operators and their AEO-authorisations are registered and managed in EOS.
• AES consults EOS to check whether the appropriate Traders are registered as AEO and whether they
have a valid AEO -authorisation of the relevant type. The query will be performed on the basis of the
declared EORI or TCUIN.
2.4.3 UCC CUSTOMS DECISIONS
• The Customs Decisions system allows the electronic processing and central storage of the applications
and authorisations and publication of the list of holders on the Internet. The IT system will facilitate the
necessary consultations between MS' customs a uthorities during the decision taking period and the
management of the authorisations process. Authorisations granted by MS using the central system for the
management of their Customs Decisions as well as authori sations are valid in more than one MS are
published to CRS (Customer Reference Services). All national applications (e.g. AES) will have to
communicate with CRS to check the status of authorisations that are mentioned in the declaration data .
• When validating a received data set for which authorisations are valid in more than one MS, AES consults
the CRS to check the existence and validity of the customs decisions. Validations of authorisations valid
in one Member State will be done by the national export system against the data available in their national
Customs Decision System or in CRS, in case they use the central system for the management of their
Customs Decisions.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 7 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.4.4 UCC NCTS
• In order to synchronise the transit and export procedures in a harmoni sed way and to avoid open
movements, AES needs to interface with NCTS when export is followed by transit. This is part of the so-
called national domain. All messages between AES and NCTS are of national matter, but the European
Commission recommends, transm itting at least the information included in the relevant messages (see
DDNXA Appendix Q2 – Technical Message Structure) between NCTS and AES.
• For both external and internal transit, NCTS will inform AES:
o In case the Goods are released for Transit.
o In case goods are not released for Transit. This is the case when the control revealed major
discrepancies.
• It is to be noted that in case of external Transit only, control results of Customs Office of Departure would
be available in AES.
• For internal transit, NCTS will inform AES:
o In case of Control Results , when Control Results are communicated to the Office of Departure
from the Office of Destination, NCTS will inform AES that there is positive/negative Control
Results.
o In case of negative Control Results, NCTS will inform AES about the discrepancies for the
movement identified.
o For the exception case of recovery, NCTS will inform AES at the start of the recovery .
o In case the Office of Destination is not appropriate.
2.4.5 EMCS
• In case of an Export declarat ion that contains Excise goods, AES (at the office of export) needs to
interface with EMCS (Excise Movement and Control System) , in order to synchroni se the Export and
EMCS Export procedures. This is part of the so -called national domain. All messages between AES (at
the office of export) and EMCS are of national matter, but the European Commission recommends,
transmitting at least the information included in the relevant messages (see DDNXA Appendix Q2 –
Technical Message Structure) between EMCS and AES.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 8 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 1: Overview of AES Master Process
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 9 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.5 L4-EXP-01-01-CUSTOMS FORMALITIES AT OFFICE OF EXPORT -ACCEPTANCE AND
CONTROLS
Figure 2: L4-EXP-01-01-Customs Formalities at Office of Export-Acceptance and Controls (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 10 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 3: L4-EXP-01-01-Customs Formalities at Office of Export-Acceptance and Controls (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 11 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Export Declaration Received
Organisation: Declarant/Representative
Location: Premises of the Declarant/Representative or Office of Export
AES at Customs Office of Export receives an Export Declaration.
E_Export Declaration Amended
Organisation: Declarant/Representative
Location: Premises of the Declarant/Representative or Office of Export
Export Declaration is amended at Customs Office of Export.
Processes
Customs Formalities at Office of Export-Acceptance and Controls Process: L4 -EXP-
01-01
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
AES at the Customs Office of Export receives an ‘Export Declaration’ (IE515) from the Trader in an electronic
format. Process ‘L4-EXP-01-01-01-Acceptance of Export Declaration’ is executed.
1. If AES does not accept the Export Declaration, then it is rejected. The process stops at this point.
2. If AES accepts the Export Declaration, then AES identifies if the Declaration concerns Centrali sed
Clearance and based on the outcome, two cases may occur:
2.1. Declaration doesn’t concern Centralised Clearance so the process continues with L4 -EXP-01-01-02-
Register and Record Control Decision call -activity and AES identifies if the decision was to control
the Goods or not and based on the outcome, two cases may occur:
2.1.1. Decision is not to control the Goods, and the process continues at point 3.
2.1.2. Decision is to control the Goods,
2.1.2.1. the process continues with L4-EXP-01-01-04-Register Control Results at Office of Export
call-activity,
2.1.2.2. then the process continues with L4-EXP-01-01-05-Handle Results of Control and Release
Request call-activity and the process continues at point 3.
2.2. Declaration concerns Centralised Clearance so the process continues with L4-EXP-01-01-03-Register
Control Decision and Results under Centralised Clearance call -activity and based on the outcome,
three cases may occur:
2.2.1. Goods Can be Released/Goods Cannot Be Released and the process continues at point 3.
2.2.2. Not Released for Export and the process stops at this point.
3. AES identifies if goods can be released for Export based on the outcome, two cases may occur:
3.1. Goods can be released for Export and the process ends with outcome ‘Goods Can Be Released’.
3.2. Goods can’t be release for Export, the process continues with L4 -EXP-01-01-07-Do Not Release the
Goods and the process ends with outcome ‘Not Released for Export’.
In case that an amendment/correction request with ‘Export Declaration Amendment’ (IE513) is submitted to
the Customs Office of Export while the movement state is ‘Accepted’ during the execution of L4-EXP-01-01-
01-Acceptance of Export Declaration , the process L4 -EXP-01-05 Amendment of the Export Declaration is
executed and provided that this request is accepted, the process L4-EXP-01-01-Customs Formalities at Office
of Export-Acceptance and Controls is initiated from point 2.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 12 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Final situation:
• Goods can be released for Export.
• Goods can’t be released for Export.
Acceptance of Export Declaration Process: L4 -EXP-
01-01-01
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
This process is initiated when the Export Declaration data is submitted to the Office of Export.
1. Validation of the Export Declaration is performed by AES.
1.1. If the Export Declaration is invalid, AES rejects the Export Declaration and notifies the
Declarant/Representative about the ‘Rejection from Office of Export’ (IE556), giving the reason for
the rejection. The movement state is set to ‘Rejected’. The process stops at this point.
1.2. If the Export Declaration is valid, AES automatically records the Export Declaration. AES checks the
Authorisations of the Declarant/Representative.
1.2.1. If Authorisations are invalid, then the process continues from point 1.1.
1.2.2. If Authorisations are valid, AES continues identifying if the customs declaration contains
ARC(s), in order to determine if the declared goods are under excise duty suspension
arrangement.
1.2.2.1. If Export Declaration contains ARC(s), then process L4 -EXP-01-01-01-01-Handle e-AD
Request is executed.
1.2.2.1.1. If all e-ADs are received and the Cross-Check Result between the e -AD and the
Customs Declaration is successful, then the main process ‘L4 -EXP-01-01-01-
Acceptance of Export Declaration’ continues from point 2.
1.2.2.1.2. If the ‘e-AD Request’ (IE532) is not accepted by the EMCS of the Member State
of Export (IE8xx) or the Cross -Check result was negative, AES records the
rejection. If the Cross-Check between the e -AD and the Customs Declaration was
negative, AES informs the Member State of Export on the ‘e -AD Negative Cross-
Check Result’ (IE537). The process continues from point 1.1.
1.2.2.2. If Export Declaration does not contain ARC(s), then the process continues from point 2.
2. AES identifies if the customs declaration has been lodged prior to the presentation of the goods.
2.1. If AES received the Export Declaration without the Goods being presented (Additional Declaration
Type=D, E, F) the state of the movement is set to ‘Registered and Waiting for Presentation of Goods’.
At this point, the MS may pre-allocate a MRN without communicating it to the
Declarant/Representative. AES starts the time limit to receive the Export Presentation Notification
and process L4-EXP-01-01-01-02-Request and Record Risk Analysis is executed. The Customs
Officer registers his/her control decision and AES record s the control decision. If it was decided to
perform control and the Declarant/Representative has an AEO certificate, then AES informs the
Declarant/Representative of the intention to control the goods with ‘Export Control Decision
Notification’ (IE560). In case the Declarant/Representative hasn’t got an AEO certificate then he/she
is not informed about the intention to control the goods.
2.1.1. One of the following cases is fulfilled:
2.1.1.1. The ‘Timer Awaiting for Export Presentation Notification’ expires. AES rejects the
Export Declaration and notifies the Exporter about the declaration rejection with
‘Rejection from Office of Export’ (IE556), giving the reason for the rejection. The
movement state is set to ‘Rejected’. The process stops at this point.
2.1.1.2. AES receives an ‘Export Presentation Notification’ (IE511), then process L4-EXP-01-01-
01-04 Evaluate Export Presentation Notification is executed.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 13 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.1.1.2.1. If the E xport Presentation Notification is valid the process continues from point
2.1.2.
2.1.1.2.2. If the Export Presentation Notification is invalid , the status of the movement
remains to ‘Registered and Waiting for presentation of goods’, then the process
continues from point 2.1.1.
2.1.1.3. AES receives an ‘Export Declaration Amendment’ as Correction (IE513) and then process
L4-EXP-01-05 Amendment of the Export Declaration is executed and the process
continues from point 2.1.1.
2.1.1.4. AES receives an ‘Export Invalidation Request’ (IE514) as Cancellation and then process
L4-EXP-01-01-01-05 Handle Cancellation Request is executed.
2.1.1.4.1. If the Cancellation Request is valid the movement state is set to ‘Cancelled’ and the
process stops at this point.
2.1.1.4.2. If the Cancellation Request is invalid the process continues from point 2.1.1.
2.1.2. AES validates the Export Declaration against the business rules and conditions, following the
‘Export Presentation Notification’ (IE511).
2.1.2.1. If the Export Declaration is invalid, AES rejects the Export Declaration and notifies the
Declarant/Representative about the declaration rejection with ‘Rejection from Office of
Export’ (IE556), giving the reason for the rejection. The movement state is set to
‘Rejected’. The process stops at this point.
2.1.2.2. If the Export Declaration is valid, AES checks the Authorisations of the
Declarant/Representative.
2.1.2.2.1. If the Authorisations are invalid , AES rejects the Export Declaration and notifies
the Declarant/Representative about the declaration rejection with ‘Rejection from
Office of Export’ (IE556), giving the reason for the rejection. The movement state
is set to ‘Rejected’. The process stops at this point.
2.1.2.2.2. If the Authorisations are valid , AES continues with identifying if the customs
declaration contains ARC(s), in order to determine if the declared goods are under
excise duty suspension arrangement.
2.1.2.2.2.1. If Export Declaration contains ARC(s), then process L4 -EXP-01-01-01-01-
Handle e-AD Request is executed.
2.1.2.2.2.1.1. If all e-ADs are received and the Cross-Check Result between the e -
AD and the Customs Declaration is successful, then depending on the
MS, AES shall check if MRN has been pre -allocated (or not) . The
process continues from point 3.
2.1.2.2.2.1.2. If the ‘e-AD Request’ (IE532) is not accepted by the EMCS of the
Member State of Export (IE8xx) or the Cross -Check result was
negative, AES records the rejection. In the event of a negative Cross-
Check between the e -AD and the Customs Declaration was negative,
AES informs the Member State of Export on the ‘e-AD Negative
Cross-Check Result’ (IE537). AES rejects the Export Declaration and
notifies the Declarant/Representative about the declaration rejection
with ‘Rejection from Office of the Export’ (IE556) and the MSA of
Export with ‘Export Declaration Rejection Notification to MSA of
Export’(IE519), providing the reason for the rejection. The movement
state is set to ‘Rejected’. The process stops at this point.
2.2. If AES received the Export Declaration and the Goods were presented , the process continues from
point 3.
3. AES accepts the Export Declaration, generates the MRN and assigns it to the movement . The movement
state is set to ‘Accepted’. The Trader is notified with ‘Export MRN Allocated’ (IE528) of the Export
Declaration acceptance. If the Export Declaration contains ARC(s), then AES informs the MSA of Export
of the ‘Export Declaration Acceptance Notification to MSA of Export’ (IE539).
4. The process L4-EXP-01-01-01-02 Request and Record Risk Analysis is executed. AES interfaces with the
national risk analysis systems of the Member States to request a Risk Analysis. When the Risk Analysis
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 14 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
results are received, AES records them and the process ‘L4 -EXP-01-01-01-Acceptance of Export
Declaration’ ends.
Final situation:
• If the declaration is not valid, it is rejected , and the trader is informed. The movement state is set to
‘Rejected’.
• If the declaration is valid, it is accepted. The Trader is notified of the acceptance of the declaration.
The result of the risk analysis is known. The movement state is set to ‘Accepted’ .
• If a Cancellation Request is received via ‘Export Invalidation Request’ (IE514) and is valid the
movement state is set to ‘Cancelled’ and the process stops at this point.
Handle e-AD Request and Cross-Checking Process: L4-EXP-
01-01-01-01
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
The process is initiated when AES identifies the following condition:
• Export Declaration contains ARC(s) and UBR(s) under Previous document (C651 or C658).
Following the above identification, the flow continues as per the below:
AES at the Customs Office of Export requests the e -AD in electronic format ‘e-AD Request’ (IE532) from
EMCS of the Member State of Export. Until the Export Declaration acceptance, AES uses LRN as a key in all
external and national domain information exchanges. Goods declared in one Export declaration can refer to
several e-ADs, therefore a separate message will need to be sent to the EMCS of the Member State of Export
for each e-AD. One of the following cases is fulfilled:
1. AES at the Customs Office of Export receives some (or all) of the requested e -AD(s) from EMCS at the
MSA of Export via ‘e-AD’ (IE801). In the case that in a single Export Declaration, the Goods refer to
several e-ADs, the Member State of Export will need to send to AES separate IE801 messages (in case of
availability of the e-ADs) for each e-AD. AES identifies whether it has received as many responses as the
number of the ‘e-AD Request’ (IE532) initially sent. At this point, the following may occur:
1.1. The number of the responses received from EMCS at the MSA of Export is equal to the requested e -
ADs initially sent. AES at the Customs Office of Export identifies whether all e -ADs that were
initially requested are received. The following may occur at this point:
1.1.1. All e-ADs that were initially requested are received. AES performs the cross-check of the e-ADs
and the Customs Declaration and records the results of the Cross check. The data elements that
must be cross-checked are the ARC, UBR, Combined Nomenclature Code and Net Mass. At this
point, the following may occur:
1.1.1.1. The cross -check was successful , and the flow stops here. The process that called this
process may now resume.
1.1.1.2. The cross-check result was unsuccessful (or for the case of 1.1.1.2. not all the e-ADs were
received, or for the case of 1.2.1. the e-AD is rejected). The MSA of Export is notified via
an ‘e-AD Negative Cross-Check Result’ (IE537) and the flow stops here. The process that
called this process may now resume.
1.1.2. The requested e-AD messages were not all received. The flow continues from point 1.1.1.1.2.
1.2. The number of the responses received from EMCS at the MSA of Export is not equal to the requested
e-ADs initially sent. The flow continues from point 1, after the request of the e -AD(s).
2. AES at the Customs Office of Export receives some (or all) negative responses from the MSA of Export
via IE8xx message. AES identifies whether it has received as many responses as the number of the ‘e-AD
Request’ (IE532) initially sent. At this point, the following may occur:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 15 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.1. The number of the responses received from EMCS at the MSA of Export is equal to the requested e -
ADs initially sent. Since AES has received at least one ‘e-AD Request Rejection’ (IE8xx), the flow
continues with the rejection of the e-AD. The flow continues from point 1.1.1.1.2. The initial process
that called this process may now resume.
2.2. The number of the responses received from EMCS at the MSA of Export is not equal to the requested
e-ADs initially sent. The flow continues from point 1, after the request of the e -AD(s).
Final Situation:
• Cross-Check Result was Successful thus the e-AD(s) is accepted.
• e-AD Rejected/ Cross-Check Result was negative; thus the e-AD is rejected.
Request and Record Risk Analysis Process: L4-EXP-
01-01-01-02
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
Automatic risk analysis is performed at this stage (fiscals and/or safety and security) . AES interfaces with the
national risk analysis systems of the Member States and ensures that risks analysis is initiated once the data is
received and validated by AES. The national risk analysis systems of the Member States carr y out the required
risk analysis and send back the risk analysis results and control recommendation to AES.
Random risk parameters shall be used additionally.
Risk analysis shall be performed for all the goods of the export declaration. The risk analysis shall be initiated
by AES and carried out by the national risk analysis application according to the rules set out by the risk
management framework. The risk analysis results shall be recorded in AES in the format used for
communication with other Offices/Member States, in order for them to be made available for usage in ‘AER’
(IE501).
Evaluate Export Presentation Notification Process: L4-EXP-
01-01-01-04
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
AES receives the Export Presentation Notification (IE511) , and validation is performed. The following cases
may occur:
1. The Export Presentation Notification is invalid , AES informs the Declarant/Representative about the
rejection via an IE556. The process which initiated this process can now continue.
2. The Export Presentation Notification is valid. AES records the Export Presentation Notification and stops
the time limit awaiting an IE511. The process which initiated this process can now continue.
Final situation:
• Export Presentation Notification is accepted.
• Export Presentation Notification is rejected.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 16 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Handle Cancellation Request Process: L4 -EXP-
01-01-01-05
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
In case of a pre -lodged declaration and before AES allocates a MRN to the movement, the
Declarant/Representative may lodge a C ancellation Request with Export Invalidation Request’ (IE514). The
term ‘Cancellation’ is employed so as to emphasise that MRN has not been allocated yet (else Invalidation
Request).
AES receives the Cancellation Request with ‘Export Invalidation Request’ (IE514) and validation is performed.
Then, one of the following might occur:
1. If the Cancellation Request is valid , AES records it. The Customs Officer registers his decision to accept
the cancellation request and then is recorded to AES. The process continues and the movement state is set
to ‘Cancelled ’. AES notifies the Declarant/Representative of the decision to cancel the movement with
‘Export Invalidation Decision’ (IE509) and stops the timer ‘Awaiting for the Presentation Notification’. If
the Export Declaration cont ains ARC(s) the MSA of Export is also notified with an ‘Export Declaration
Rejection Notification to MSA of Export’ (IE519). The process stops at this point.
2. If the Cancellation Request is invalid , AES notifies the Declarant/Representative of the Cancellation
Request rejection with ‘Rejection from Office of Export’ (IE556). The process which initiated this process
can now continue.
Final situation:
• Cancellation request is valid and the Export Declaration is cancelled, thus movement state turns to
‘Cancelled’.
• Cancellation request is rejected.
Register and Record Control Decision Process: L4 -EXP-
01-01-02
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
The process starts when AES accepts the Export Declaration in Process L4 -EXP-01-01. The Customs Officer
compiles all the information he needs (the export declaration information retrieved by AES via the allocated
MRN) and checks the risk analysis results (performed either in the end of L4 -EXP-01-01-01-Acceptance of
Export Declaration or in the end of L4 -EXP-01-05-Amendment of the Export Declaration) in order to register
control decision. Even if the risk analysis and the cross -checks mentioned above are automatic processes, the
final decision to control may be overruled by the Customs Officer.
The Customs Officer registers the control decision:
1. The control decision is recorded in the AES of the Customs Office of Export.
2. Then, one of the following might occur depending on the control decision:
2.1. No control is to be performed on goods and/or documents. The movement state changes to ‘Goods
Released for Export’ and process ends with ‘Control Decision Recorded’. Process which initiated this
process can now continue.
2.2. If controls are to be performed, then the Declarant/Representative must be notified with an ‘Export
Control Decision Notification’ (IE560) of the decision to control. This would allow him to be present during
the control (declaration amendments are no longer accepted by the Office of Export). The movement state
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 17 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
changes to 'Under Control' and process ends with 'Control Decision Recorded'. Process which initiated this
process can now continue.
Final situation:
• Process ends with 'Control Decision Recorded'.
Register Control Decision and Results under Centralised Clearance Process: L4 -EXP-
01-01-03
Organisation: National Customs Administration
Location: Supervising Customs Office
Constraint: N/A
Description:
When the Risk Analysis has been performed and the results have been recorded, the process starts concerning
Centralised Clearance, the Customs Officer registers the Control Decision, and the Control Decision is recorded
in AES.
AES in the Supervising Customs Office (SCO) identifies the Control Decision of the previously executed
process.
Upon the Control Decision, one of the following might occur:
1. The Customs Officer has decided that no Documentary Controls must be performed.
1.1. AES at the Supervising Customs Office (SCO) decid es to recommend pre -release. The decision for
pre-release recommendation to Presentation Customs Office (PCO) is recorded and the Process L4-EXP-
01-01-03-03- Notify PCO for Pre-release/Control Recommendation or Release Rejection is executed.
2. The Customs Officer has decided that Documentary Controls must be performed.
2.1. SCO executes the documentary controls. Process L4 -EXP-01-01-03-01-Register Documentary
Controls at Supervising Customs Office is executed.
2.1.1. In case there is the need to request Documents during Documentary Controls, the process L4-
EXP-01-01-03-04-Notify Declarant/Representative for Controls and/or Requested Documents is
executed.
2.1.2. In case there is no need to request Documents during Documentary Controls, the flow
continues as is.
2.2. Based on the Documentary Control Results, one of the following might occur:
2.2.1. In case of Satisfactory Control Results , the AES at the Supervising Customs Office (SCO)
decides to recommend pre -release. The decision for pre-release recommendation to Presentation
Customs Office (PCO) is recorded and the Process L4 -EXP-01-01-03-03-Notify PCO for Pre -
release/Control Recommendation or Release Rejection is executed.
2.2.2. Otherwise, even in case of Satisfactory Control Results, the AES at the Supervising Customs
Office (SCO) decides to recommend controls. The decision for controls recommendation to
Presentation Customs Office (PCO) is recorded and the Process L4-EXP-01-01-03-03-Notify PCO for
Pre-release/Control Recommendation or Release Rejection is executed.
3. Upon L4-EXP-01-01-03-03- Notify PCO for Pre -release/Control Recommendation or Release Rejection
process completion and based on the decision taken, one of the following cases might occur:
3.1.1. If it was decided by the SCO-Supervising Customs Office that the goods can be released
(based on the documentary control results at the SCO, the PCO control decision, the PCO control
results, the respect of the time limit for receiving the PCO control decision, as well as other information
or indication received at SCO in the meantime (Risk notification, RIF messages, etc.), the state alters
to ‘Goods Can Be Released’ and the process ends at this point.
3.1.2. If it was decided by the SCO-Supervising Customs Office that the goods cannot be released
after unsatisfactory Documentary Controls Results at the Supervising Customs Office (SCO, the state
of the movement is set to ‘Not Released for Export’ and the process ends at this point.
3.1.3. If it was decided by the SCO -Supervising Customs Office that the goods can not be released
(based on the documentary control results at the SCO, the PCO control decision, the PCO control
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 18 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
results, the respect of the time limit for receiving the PCO control decision, as well as other information
or indication received at SCO in the meantime (Risk notification, RIF messages, etc.), then the state
alters to ‘Goods Cannot Be Released’ and the process ends at this point.
Final situation:
• If Documentary Controls are Not Satisfactory at the SCO-Supervising Customs Office, the state of the
movement is set to ‘Not Released for Export’.
• If it or was decided by the Supervising Customs Office (SCO) that goods can be released the state
alters to ‘Goods Can Be Released’.
• If it was decided by the Supervising Customs Office (SCO) that goods cannot be released the state
alters to ‘Goods Cannot Be Released’.
Register Documentary Controls at Supervising Customs Office Process: L4 -EXP-
01-01-03-01
Organisation: National Customs Administration
Location: Supervising Customs Office
Constraint: N/A
Description:
Process L4-EXP-01-01-03-01 is initiated in case Documentary Controls are to be performed from the SCO -
Supervising Customs Office. T he Customs Officer in the Supervising Customs Office registers the results of
the documentary controls that were performed. AES in the Supervising Customs Office records the control
results, and the process ends with ‘Documentary Control Results recorded’.
Notify PCO for Pre-release/Control Recommendation or Release Rejection Process: L4 -EXP-
01-01-03-03
Organisation: National Customs Administration
Location: Supervising Customs Office
Constraint: N/A
Description:
The process L4-EXP-01-01-03-03-Notify PCO for Pre-release/Control Recommendation or Release Rejection
is initiated under Centralised Clearance in order to consolidate the decision of SCO-Supervising Customs Office
upon a movement and the relevant actions performed by the PCO-Presentation Customs Office, where needed.
This process has the following start events:
• SCO's decision refers to Release Rejection due to Unsatisfactory Documentary Controls at SCO .
• SCO's decision refers to Recommendation of pre-release to PCO.
• SCO's decision refers to Recommendation of controls to PCO.
When AES at the SCO identifies one of the above, one of the following three cases might occur:
1. The SCO's decision refers to Release Rejection. Consequently, SCO -Supervising Customs Office informs
Declarant/Representative of Non Release of Goods for Export with ‘Export No Release ’ (IE551). In
parallel, SCO -Supervising Customs Office informs the PCO -Presentation Customs Office with ‘Pre-
release/Control Notification’ (IE540) regarding the Release Rejection.
1.1. The PCO-Presentation Customs Office receives the pre -release/control notification and records the
release rejection in AES. Next, PCO -Presentation Customs Office informs the SCO -Supervising
Customs Office with a ‘Pre-release/Control Acknowledgment’ (IE545).
1.2. The SCO-Supervising Customs Office received the pre -release/control acknowledgment and as the
SCO decision in AES indicated release rejection, the state is set to ‘Not Released for Export’. At the
same time, after the dispatch of the ‘Pre-release/Control Acknowledgment’ (IE545), the AES at the
PCO-Presentation Customs Office sets the state at PCO is set to ‘Not Released for Export’. The flow
ends at this point.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 19 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2. The SCO's decision refers to Recommendation of pre-release to PCO. Consequently, the SCO-Supervising
Customs Office informs the PCO -Presentation Customs Office with ‘Pre-release/Control Notification ’
(IE540) indicating Pre-release recommendation.
2.1. The PCO-Presentation Customs Office receives the pre -release/control notification and records the
pre-release recommendation in AES. Next, PCO -Presentation Customs Office informs the SCO -
Supervising Customs Office with a ‘Pre-release/Control Acknowledgment’ (IE545).
2.2. The SCO-Supervising Customs Office received the pre -release/control acknowledgment and as the
SCO decision in AES indicated pre -release recommendation, the Timer to receive Control
Notification from PCO is initiated. At the same time, after the dispatch of the ‘Pre-release/Control
Acknowledgment’ (IE545), the AES at the PCO-Presentation Customs Office performs risk analysis
and the Customs Officer registers the control decision in AES.
2.3. AES in the PCO records the Control Decision and one of the following might occur:
2.3.1. AES in the PCO -Presentation Customs Office might inform the SCO -Supervising Customs
Office with a ‘Control Decision from Presentation Customs Office ’ (IE563). AES in the SCO -
Supervising Customs Office might receive the Control Decision , stop the Timer to receive
Control Notification from PCO and records the Control Notification from PCO . The flow
continues from point 2.4.
2.3.2. AES in the PCO-Presentation Customs Office might not communicate to the SCO -Supervising
Customs Office the Control Decision, for a configurable amount of time before the Timer to
receive Control Notification expires, thus, the SCO -Supervising Customs Offic e might send a
‘Reminder for Control Decision ’ (IE564). Upon its receipt, the PCO -Presentation Customs
Office, shall proceed, based on the PCO Control Decision to one of the two following:
2.3.2.1. Either with informing the SCO -Supervising Customs Office with the ‘Control Decision
from Presentation Customs Office’ (IE563) and the flow shall continue from point 2.3 (As
the configurable amount of time has passed, the flow shall continue either with 2.3.1 or
2.3.3).
2.3.2.2. Or, by not informing the SCO upon PCO Control Decision, hence, the process at the PCO
ends at this point with ‘No PCO Control Decision is sent’.
2.3.3. The Timer to Receive Con trol Notification from PCO might expire and no ‘Control Decision
from Presentation Customs Office ’ (IE563) is received, consequently, AES at the SCO -
Supervising Customs Office shall record the expiration and take decision upon the release of the
goods for Export and the flow ends at this point.
2.4. The SCO -Supervising Customs Office identifies the PCO Control Decision and based on the
Decision (whether Controls might be performed at the PCO-Presentation Customs Office), one of the
following two cases might occur:
2.4.1. If PCO indicates no Controls to be performed, the Customs Officer at the SCO-Supervising
Customs Office shall take the Decision to Release or not to Release the Goods for Export, thus,
the process outcome turns to either ‘Goods Can Be Released’ or ‘Goods Can Not Be Released’,
respectively. In parallel, the process at PCO-Presentation Customs Office ends with ‘No Control
of the Goods at PCO was performed’.
2.4.2. If PCO indicates Controls to be performed, the process L3 -EXP-01-01-03-02-Notify
Declarant/Representative for Controls and/or Request Documents is initiated by the AES at the
SCO-Supervising Customs Office. At the same time, the Customs Officer at the PCO -
Presentation Customs Office registers the Control Result an d when the Control Results are
recorded in the AES, the PCO informs the SCO -Supervising Customs Office with ‘Control
Results from Presentation Customs Office ’ (IE541) and the process ends with ‘Control of the
Goods at PCO was performed ’. Upon control results receipt, the AES at the SCO-Supervising
Customs Office records the PCO Control Results and then the AES at the SCO -Supervising
Customs Office identifies whether the PCO Control Results are Satisfactory or Considered
Satisfactory or Satisfactory with Min or Discrepancies or not. Then, one of the following might
occur:
2.4.2.1. If the PCO Control Results are Satisfactory or Considered Satisfactory or Satisfactory
with Minor Discrepancies, the Customs Officer at the SCO -Supervising Customs Office
shall take the Decision to Release or not to Release the Goods for Export, thus, the process
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 20 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
outcome turns to either ‘Goods Can Be Released’ or ‘Goods Can Not Be Released’,
respectively.
2.4.2.2. If the PCO Control Results are Not Satisfactory, the process outcome turns to ‘Goods Can
Not Be Released’.
3. The SCO's decision refers to Recommendation of controls to PCO. Consequently, the SCO -Supervising
Customs Office informs the PCO -Presentation Customs Office with ‘Pre -release/Control Notification’
(IE540) indicating Controls recommendation.
3.1. The PCO-Presentation Customs Office receives the pre -release/control notification and records the
pre-release recommendation in AES. Next, PCO -Presentation Customs Office informs the SCO -
Supervising Customs Office with a ‘Pre-release/Control Acknowledgment’ (IE545).
3.2. The SCO-Supervising Customs Office received the pre -release/control acknowledgment and as the
SCO decision in AES indicated controls recommendation, the Timer to receive Control Notification
from PCO is initiated. At the same time, after the dispatch of the ‘Pre -release/Control
Acknowledgment’ (IE545), the AES at the PCO -Presentation Customs Office performs risk analysis
and the Customs Officer registers the control decision in AES. Process continues from point 2.3.
Final Situation:
• If the goods can be released for export (as the SCO -Supervising Customs Office has taken this
decision) the process at SCO-Supervising Customs Office ends with ‘Goods Can Be Released’. If the
goods cannot be released for export (as the SCO-Supervising Customs Office has taken this decision)
the process at SCO-Supervising Customs Office ends with ‘Goods Can Not Be Released’. At the PCO-
Presentation Customs Office, if no response upon controls at PCO is sent, the process ends with ‘No
PCO Control Decision is sent’, whereas if no controls were needed to be performed the process ends
with ‘No Control of the Goods at PCO was performed’ . If the controls have been performed at PCO,
the process ends at PCO -Presentation Customs Office with ‘Control of the Goods at PCO was
performed’.
• If the Documentary Controls at SCO -Supervising Customs Office indicated release rejection , the
movement state is set to ‘Not Released for Export’.
Notify Declarant/Representative for Controls and/or Request Documents Process: L4 -EXP-
01-01-03-04
Organisation: National Customs Administration
Location: Supervising Customs Office
Constraint: N/A
Description:
Under Centralised Clearance, when one of the two following cases occur, the process L4-EXP-01-01-03-04 is
initiated, which depicts the notification of Declarant/Representative upon upcoming controls and/or request of
documents.
This process has the following start events:
• SCO-Supervising Customs Office decides that documentary controls are required (by the Supervising
Customs Office) with the need to request documents.
• PCO-Presentation Customs Office decides to Perform physical controls or other type of controls which
may need the physical presence of the Declarant/Representative, and request documents, if necessary.
When AES at the SCO identifies one of the above, it informs the Declarant/Representative with an ‘Export
Control Decision Notification’ (IE560) and the process ends with ‘SCO notified Declarant/Representative upon
Control Decision’.
Final Situation:
SCO informs Declarant/Representative about the upcoming controls that might be performed and/or request of
documents and the process ends with 'SCO notified Declarant/Representative upon Control Decision'.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 21 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Register Control Results at Office of Export Process: L4-EXP-
01-01-04
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
This process is initiated after the goods have been controlled by the Customs Officer.
The Customs Officer at the Office of Export registers the controls results, AES records the control results , and
the process ends with outcome ‘Control Results Recorded’.
The process which initiated this process can now continue.
Final situation:
• Control Results recorded in AES.
Handle Results of Control and Release Request Process: L4 -EXP-
01-01-05
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
When the 'Register Control Results at Office of Export' process ends with 'Control Results Recorded' as an end
event, this L4 process will start.
1. This process is triggered if
Control Results Recorded and the process continues at point 2.
2. AES identifies if the control results are satisfactory or unsatisfactory and based on the outcome, two cases
may occur:
2.1. Control Results are satisfactory, AES records the Declaration Data Control Results , and the process
ends with outcome ‘Goods Can Be Released’.
2.2. Control Results are unsatisfactory as major discrepancies identified, AES doesn’t release the goods
for exit and the process ends with outcome ‘Goods Not to Be Released’.
The process which initiated this process can now continue.
Final Situation:
• Control Results are satisfactory, and the process ends with outcome ‘Goods Can Be Released’.
• Control Results are unsatisfactory, and the process ends with outcome ‘Goods Not to Be Released’.
Do Not Release Goods at Office of Export Process: L4-EXP-
01-01-07
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
Customs Office of Export
1. This process starts when the decision not to release the goods has been reached.
2. At this point, a parallel course of events takes place, and the following three cases are followed in parallel:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 22 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.1. AES notifies the Declarant/Representative of Non-Release of Goods for Export via an ‘Export No
Release’ (IE551) message and the process continues at point 3.
2.2. AES identifies if the Declaration contains Excise Goods and based on the outcome, two cases may
occur:
2.2.1. Declaration contains Excise Goods, AES notifies MSA of Export of Non-Release of Goods via
an ‘Non-Release for Export Notification to MSA of Export’ (IE534) message and the process
continues at point 3.
2.2.2. Declaration doesn’t contain Excise Goods, and the process continues at point 3.
2.3. AES identifies if the Declaration concerns Centralised Clearance and based on the outcome, two cases
may occur:
2.3.1. Declaration concerns Centralised Clearance, AES notifies the PCO of the Release Rejection of
the Goods via an ‘Release Rejection Notification’ (IE542) message and the process continues at
point 3.
2.3.2. Declaration doesn’t concern Centralised Clearance, and the process continues at point 3.
3. Process ends with outcome ‘Not Released for Export’.
PCO – Presentation Customs Office
This process starts at the Presentation Customs Office when the ‘Release Rejection Notification’ (IE542) is
received from Customs Office of Export (acting as Supervising Customs Office) at point 2.3.1, AES records the
Release Rejection Notification, and the movement state changes to ‘Not Released for Export’.
The process which initiated this process can now continue.
Final Situation:
• All the involved parties (Declarant/Representative, MSA of Export, PCO) are notified of the release
rejection and the movement state remains unchanged to ‘Not Released for Export’.
Major Results
R_Goods Can Be Released
Organisation: National Customs Administration
Location: Customs Office of Export
The decision to release the goods has been reached.
E_Not Released for Export
Organisation: National Customs Administration
Location: Customs Office of Export
The decision not to release the goods has been reached.
Minor Results
R_ Export Declaration Rejected
Organisation: National Customs Administration
Location: Customs Office of Export
AES rejects the Export Declaration.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 23 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.6 L4-EXP-01-02-CUSTOMS FORMALITIES AT OFFICE OF
EXPORT-RELEASE
Figure 4: L4-EXP-01-02-Customs Formalities at Office of Export-Release (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 24 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 5: L4-EXP-01-02-Customs Formalities at Office of Export-Release (Part B)
Major Events
E_Goods Can Be Released
Organisation: National Customs Administration
Location: Customs Office of Export
The decision to release the goods has been reached. AES proceeds to the handling of the goods release.
Minor Events
E_Anticipated Export Record
Organisation: National Customs Administration
Location: Customs Office of Exit
The ‘AER’ data has been received. AES at the Customs Office of Exit is initiated to handle the ‘AER’ data.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 25 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
E_Release Notification to Presentation Customs Office Received
Organisation: National Customs Administration
Location: Presentation Customs Office
AES at the PCO receives and records the release notification information.
Processes
Customs Formalities at Office of Export-Release Process: L4-EXP-
01-02
Organisation: National Customs Administration
Location: Customs Office of Export, Customs Office of Exit, Presentation Customs Office
Constraint: N/A
Description:
This process starts when the decision to release the goods has been reached. AES releases the goods for export.
At this point, AES starts a timer (90 days) to receive the exit results from the Customs Office of Exit. At the
same time, AES starts a timer (150 days) to certify the exit of the goods to the Trader. At the same time, AES
identifies the declaration type. One of the following may occur:
1. At this point, AES starts a timer (90 days) to receive the exit results from the Customs Office of Exit. At
the same time, AES starts a timer (150 days) to certify the exit of the goods to the Trader. At the same time,
AES identifies the declaration type. One of the following might occur:
1.1. If it’s not a Simplified Declaration the process continues from point 2.
1.2. If it is a Simplified Declaration, AES identifies if waiver for supplementary declaration applies. The
following cases might apply, and the flow continues from point 2:
1.2.1. If a waiver for supplementary declaration applies, then the process continues.
1.2.2. If a waiver for supplementary declaration doesn’t apply, then the 'Timer for Lodgement of
Supplementary Declaration' is started. This time limit is set according to the Authorisation for
Simplified and Supplementary Declaration.
2. Following this, at the same time the following events take place in parallel:
2.1. The release is communicated with ‘Release for Export’ (IE529) to the Declarant/Representative.
The ‘Release for Export’ (IE529) corresponds always to the current (latest) version of the Export
operation data. This means that it contains the amended declaration data (if any) and/or the revised
declaration data after a control (if any), completed with the control results of the Office of Export.
2.2. AES checks whether the customs declaration is lodged under the centralised clearance procedure. The
following may occur:
2.2.1. If the customs declaration is lodged under the centralised clearance procedure, AES at the
Customs Office of Export (acting as Supervising Customs Office) informs the Presentation
Customs Office with ‘Release Notification to Presentation Customs Office’ (IE543). The
customs declaration data together with the control results and other relevant information from
the Customs Office of Export is sent to the Pres entation Customs Office. The Presentation
Customs Office records the ‘Release Notification to Presentation Customs Office’ (IE543) and
the flow at PCO ends here with ‘Goods Released for Export’.
2.2.2. If not, the process continues from point 3.
2.3. AES identifies whether the Customs Office of Exit is in the same or another Member State. The
following may occur:
2.3.1. If the Customs Office of Exit is located in another Member State, AES sends an anticipated
export record ‘AER’ (IE501) to that Customs Office of Exit. Risk analysis result may also be
communicated to the Office of Exit for information purposes. At that poi nt, the Customs
Office of Exit records the AER and the process ’L4-EXP-01-01-01-02-Request and Record
Risk Analysis for AES’ is initiated. Following the completion of this process, the flow at the
Customs Office of Exit stops here with the registration of ‘AER’ (IE501).
2.3.2. If not, the process continues from point 3.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 26 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.4. AES checks whether the customs declaration contains ARC(s) in order to determine if the declared
goods are under excise duty suspension arrangement. The following may occur:
2.4.1. The declaration contains ARC(s). AES sends a copy of the anticipated export record with
‘Release for Export Notification to MSA of Export’ (IE535) to the EMCS of the Member State
of Export.
2.4.2. If not, the process continues from point 3.
3. The flow stops and the movement state turns to ‘Goods Released for Export’.
Final Situation:
• The movement state turns to ‘Goods Released for Export’ at the Customs Office of Export.
• The movement state turns to ‘Goods Released for Export’ at the Presentation Customs Office.
• The process at the Customs Office of Exit ends with “Anticipated Export Record Registered”.
Major Results
R_Goods Released for Export
Organisation: National Customs Administration
Location: Customs Office of Export
AES at Customs Office of Export has determined that the goods can be released for export.
R_Goods Released for Export
Organisation: National Customs Administration
Location: Presentation Customs Office
AES at Presentation Customs Office has determined that the goods are released for export.
Minor Results
R_ Anticipated_Export_Record_Registered
Organisation: National Customs Administration
Location: Customs Office of Exit
The ‘AER’ data are registered at the AES at the Customs Office of Exit
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 27 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.7 L4-EXP-01-04-SUPPLEMENTARY DECLARATION
Figure 6: L4-EXP-01-04-Supplementary Declaration (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 28 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 7: L4-EXP-01-04-Supplementary Declaration (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 29 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Customs Initiates Simplified Declaration Reconciliation
Organisation: National Customs Administration
Location: Customs Office of Export
If the customs declaration(s) lodged is/are simplified declaration(s) and no waiver for supplementary declaration
was raised, then AES initiates the process to reconcile its data with data of the supplementary declaration.
Processes
Supplementary Declaration Process: L4 -EXP-
01-04
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: This process is only used when at least one simplified declaration is received.
Description:
1. The ‘Export Declaration ’ (IE515) was lodged as a simplified declaration and no waiver for the
supplementary declaration has been received. AES has started a timer for lodgement of the supplementary
declaration. One of the following cases is fulfilled:
1.1. The Customs Officer extends the timer prior to its expiration in case of duly justified circumstances
and the process L4-EXP-01-04-01 is executed.
1.2. The Customs Officer does not extend the timer prior to its expiration.
No matter if the timer for lodgement of supplementary declaration has been extended or not, the process flow
continues as follows from point 2.
2. One of the following cases is fulfilled:
2.1. AES receives the supplementary declaration from the Declarant/Representative with ‘Export
Declaration’ (IE515) within the pre-set time limit. AES validates the received supplementary customs
declaration against the business rules and conditions. If the validation against the business rules and
conditions fails, the customs declaration is rejected.
2.1.1. If the supplementary customs declaration is not valid, AES rejects the declaration and informs the
Declarant/Representative, indicating the reasons for rejection with ‘Rejection from Office of Export’
(IE556) The process continues from point 1.
2.1.2. If the supplementary customs declaration is valid, AES records it in the database and stops the timer
for lodgement of the supplementary declaration. Next, AES reconciles the data of the simplified and
supplementary declaration and then identifies i f the supplementary declaration has been lodged under the
Centralised Clearance procedure.
2.1.2.1. If yes, then the matched and reconciled declaration data are forwarded to the Presentation Customs
Office from the Customs Office of Export (acting as Supervising Customs Office) with ‘Matched Data
Declaration’ (IE533). The Presentation Customs Of fice AES makes available all the information that
should be provided to other authorities for statistical purposes and the process ends.
2.1.2.2. If the supplementary customs declaration has not been lodged under the Centralised Clearance
procedure, then the data of the simplified customs declaration and the supplementary declaration have been
reconciled and the process ends.
2.2. The time limit for the Trader to lodge the supplementary declaration expires. AES informs the
Declarant/Representative that the time limit to lodge the supplementary declaration has expired with
‘Expiry of Timer for Supplementary Declaration Notification’ (IE531).
2.2.1. If AES receives the supplementary declaration from the Declarant/Representative with ‘Export
Declaration’ (IE515) after the expiration of the timer, then the flow continues from point 2.1.
2.2.2. If AES does not receive the supplementary declaration from the Declarant/Representative ‘Export
Declaration’ (IE515) after the expiration of the timer , then AES checks if the timer for lodgement of
supplementary declaration can be extended.
2.2.2.1. If AES has determined that the timer for lodgement of supplementary declaration can be extended,
then the Customs Officer will have to register his/her decision to extend or not the time limit for lodging a
supplementary declaration.
2.2.2.1.1. If the Customs Officer decides to extend the timer, the process L4-EXP-01-04-01 is executed and
the flow continues from point 2.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 30 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.2.2.1.2. If the Customs Officer decides not to extend the timer for a lodgement of supplementary
declaration, then a customs office intervention is required, after the timer is expired.
2.2.2.2. If AES has determined that the timer for lodgement of supplementary declaration cannot be
extended, then a customs office intervention is required, after the timer is expired.
2.3. AES receives the recapitulative supplementary declaration from the Declarant/Representative with
‘Recapitulative Supplementary Declaration’ (IE512) within the pre -set time limit. AES validates the
received recapitulative supplementary customs declaration against the business rules and conditions. If the
validation against the business rules and conditions fails, the customs declaration is rejected. The flow then
continues from 2.1.1 or 2.1.2 depending on if the declaration is found valid or not.
Note: the reception of a supplementary declaration, by itself, as well as the forwarding/ receipt of the ‘Matched
Data Declaration’ C_MAT_DAT (IE533) message does not trigger a state change for the movement at the SCO
or PCO (i.e. the supplementary declaration is not involved in any movement state change).
Final situation:
• The data of the simplified customs declaration(s) and the supplementary declaration are reconciled.
The timer for lodging the supplementary declaration is stopped.
• The data of the simplified and supplementary declarations have been reconciled, and a customs office
intervention is required.
Extend Timer for Lodgement of Supplementary Declaration Process: L4 -EXP-
01-04-01
Organisation: National Customs Administration
Location: Customs Office of Export
Description:
This process starts when the Customs Officer decides to extend the time for lodgement of supplementary
declaration.
The Customs Officer must also define the start date and the time limit for the Trader to lodge the supplementary
declaration.
AES records the extension of the time for lodgement of supplementary declaration and then informs the Trader
that the time limit to lodge the supplementary declaration has been extended with ‘Expiry of Timer for
Supplementary Declaration Notification’ (IE531).
Final situation:
• The timer for lodgement of supplementary declaration extended and the Declarant/Representative was
informed accordingly.
Major Results
R_Export Declaration Supplemented
Organisation: National Customs Administration
Location: Customs Office of Export
The data of the simplified customs declaration and the supplementary declaration have been reconciled.
R_Export Declaration not Supplemented
Organisation: National Customs Administration
Location: Customs Office of Export
The data of the simplified customs declaration and the supplementary declaration have not been reconciled.
R_Matched Declaration Data Recorded at PCO
Organisation: National Customs Administration
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 31 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Location: Presentation Customs Office
The matched declaration data have been recorded at PCO.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 32 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.8 L4-EXP-01-05-AMENDMENT OF THE EXPORT
DECLARATION
Figure 8: L4-EXP-01-05-Amendment of the Export Declaration (Part A)
Figure 9: L4-EXP-01-05-Amendment of the Export Declaration (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 33 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 10: L4-EXP-01-05-Amendment of the Export Declaration (Part C)
Major Events
E_Exporter submits an amendment request
Organisation: Declarant/Representative
Location: Premises of the Declarant/Representative or Customs Office of Export
AES at the Customs Office of Export receives a customs declaration amendment request from the
Declarant/Representative.
E_Exporter submits a correction request
Organisation: Declarant/Representative
Location: Premises of the Declarant/Representative or Customs Office of Export
AES at the Customs Office of Export receives a customs declaration correction request from the -
Declarant/Representative.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 34 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Processes
Amendment of the Export Declaration Process: L4-EXP-
01-05
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint:
This process is only used if an amendment request (IE513) is received.
Amendment concerns to a still accepted declaration, meanwhile correction can be carried out for pre -lodged
declaration only. In both cases the relevant message is the same - IE513.
The amendment request must be sent to the Office of Export or - if national provisions provide for - to another
Office which is located in the same Member State as the previously declared Office of Export.
The amendment request can only be sent by the Declarant/Representative having sent the initial declaration.
An amendment request may concern the creation, modification or deletion of data within a declaration. A
cancellation of an entire declaration is not to be regarded as an amendment.
Only one declaration amendment request can be processed at a time.
While a declaration amendment request is processed, there can be no other declaration amendment request.
There is no limit of amendment requests on a specific declaration while it is under ‘Accepted’ state.
Description:
This process starts when an amendment/correction request with ‘Export Declaration Amendment’ (IE513) is
submitted to the Customs Office of Export. For this purpose, there are two starting conditions for this process,
as follows:
• Receive Export Declaration Amendment Request.
• Receive Export Declaration Correction Request.
When one of the above conditions is met in AES, the flow continues as per the following:
AES validates the ‘Export Declaration Amendment’ (IE513) message. The IE513 message contains all values
of the original declaration altered with the requested amendments. At this point one of the following cases
may occur:
1. If the Export Declaration Amendment Request is valid, AES at the Customs Office of Export records the
request and identifies if the Declaration contains ARC(s). At this point, one of the following may occur:
1.1. If the Export Declaration contains ARC(s), the process ’L4-EXP-01-01-01-01-Handle e-AD
Request and Cross-Checking’ is initiated. Following the completion of this process, one of the
following may occur:
1.1.1. If all e-ADs were received and the Cross-Check result is successful, AES proceeds
with the amendment of the data of the Export Declaration and notifies the
Declarant/ Representative on the acceptance of the Amendment of the Export
Declaration via an ‘Export Declaration Amendment Acceptance’ (IE504). At this
point, the system checks if the state of the movement is ‘Accepted’. One of the
following may occur:
1.1.1.1. If the movement state is ‘Accepted’, AES at the Customs Office of
Export notifies the EMCS in the MSA of Export on the Export
Declaration Amendment Acceptance via an (IE539) ‘Export Declaration
Acceptance Notification to MSA of Export’. The flow continues with the
initiation of the process ‘L4-EXP-01-01-01-02-Request and Record Risk
Analysis’. After the completion of this process, the flow stops there.
1.1.1.2. If the movement state is not ‘Accepted’, the flow continues with the
initiation of the process ‘L4-EXP-01-01-01-02-Request and Record Risk
Analysis’. After the completion of this process, the flow stops there.
1.1.2. If the Cross-Check result was negative or the e-AD was rejected, the flow
continues from point 2.
1.2. If the Declaration does not contain ARC(s), the system continues with the amendment of the
Export Declaration data and notifies the Declarant/ Representative on the acceptance of the
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 35 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Amendment of the Export Declaration via an ‘Export Declaration Amendment Acceptance’
(IE504). The flow continues with the initiation of the process ‘L4-EXP-01-01-01-02-Request
and Record Risk Analysis’. After the completion of this process, the flow stops here.
2. If the Export Declaration Amendment Request is not valid or the handling of e -AD failed, AES records
the Declaration Amendment Request Rejection and notifies the Declarant/ Representative via a ‘Rejection
from Office of Export’ (IE556) message. The flow stops here.
Final Situation:
• The Export Declaration Correction/Amendment Request can be Rejected by AES at the Customs
Office of Export.
• The Export Declaration Correction/Amendment Request can be Accepted by AES at the Customs
Office of Export.
Major Results
R_Amendment/Correction accepted by Office of Export
Organisation: National Customs Administration
Location: Premises of the Declarant/Representative or Customs Office of Export
The amendment/correction request has been accepted and the export declaration has been amended/corrected.
R_Amendment/Correction rejected by Office of Export
Organisation: National Customs Administration
Location: Premises of the Declarant/Representative or Customs Office of Export
Customs declaration amendment/correction request is rejected by the Customs Office of Export.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 36 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.9 L4-EXP-01-07-CUSTOMS FORMALITIES AT OFFICE(S) OF EXIT-PROCESS EXIT
Figure 11: L4-EXP-01-07-Customs Formalities at Office(s) of Exit-Process Exit
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 37 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Goods Released for Export
Organisation: National Customs Administration
Location: Customs Office of Exit
AES has determined that the goods can be released for exit.
Processes
Customs Formalities at Office(s) of Exit-Process Exit Process: L4-EXP-
01-07
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
When the ‘Exit Release Notification’ (IE525) has been communicated to the Trader at Exit and the end result
of L4-EXP-01-21-Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods has ended
with ‘Goods Released for Exit’, the process L4 -EXP-01-07-Customs Formalities at Office(s) of Exit -Process
Exit will be initiated.
1. AES at the Customs Office of Exit identifies whether the Goods were released for immediate leave or were
stored. One of the following cases might occur:
1.1. If the goods were released for immediate leave, i.e. the movement state is ‘Goods Released for
Immediate Leave’, the process will continue directly to L4 -EXP-01-07-02-Handle Exit Notification.
Process continues from point 3.
1.2. If the goods were held for storing, i.e. the movement state is ‘Goods Held for Storing’, the L4 -EXP-
01-07-01-Process Manifest Presentation will be initiated. Process continues from point 2.
2. In the L4 -EXP-01-07-01-Process Manifest Presentation , a successful validation of the received Manifest
Presentation (IE547) by AES shall follow. If the received ‘Manifest Presentation’ (IE547) is invalid, AES
loops back waiting for a new ‘Manifest Presentation ’ (IE547) and informs the Trader at Exit about the
negative results of the validation with ‘Manifest Validation’ (IE548). At any case, in the end the manifest
presentation shall be accepted.
3. The Exit Information is provided successfully at the Customs Office of Exit in the L4 -EXP-01-07-02-
Handle Exit Notification. If the ‘Exit Notification’ (IE590) is invalid, then AES loops back and waits for a
new ‘Exit Notification’ (IE590). In all other cases, AES Records the Exit Notification. One of the following
two might occur:
3.1. The process L4-EXP-01-07-02-Handle Exit Notification ends with ‘Exit Results Available’ in case of
Total Exit information available and continues with L4-EXP-01-07-03-Send Exit Results (point 4).
3.2. The process L4-EXP-01-07-02-Handle Exit Notification ends with the movement state at the Customs
Office of Exit changing to ‘Partially exited’ in case partial exit is concerned . The process goes back
to point 2 with an arrival of a new ‘Manifest Presentation’ (IE547).
4. The process continues with the initiation of L4-EXP-01-07-03-Send Exit Results, where the Exit Results
are sent to the Customs Office of Export, and it reaches the final movement state ‘Exited’. The process ends
with ‘Exit Formalities are Completed’.
Final Situation:
• The Exit Formalities are Completed.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 38 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Process Manifest Presentation Process: L4 -EXP-
01-07-01
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint:
National variants are possible depending on the local organisations.
It must be possible to receive and process amendments of the presented manifest (i.e. mainly reduction of the
cargo, and/or its increase).
Description:
AES determined that the goods can be released for Exit in process L4 -EXP-01-21-Customs Formalities at
Office(s) of Exit-Handle Controls and Release of Goods . The following start events may initiate the L4-EXP-
01-07-01 Process Manifest Presentation model:
• ‘Goods Held for Storing’ start event shall be used the first time a 'Manifest Presentation' (IE547) is
about to be received. AES identified that ‘Goods Held for Storing’ based on the information provided
on arrival at exit. This state was reached after communication of 'Export Release Notification' (IE525)
to the Trader at Exit.
• ‘Receive Manifest Presentation in ‘Partially Exited’ state’ start event shall be used all the following
times a 'Manifest Presentation' (IE547) is about to be received , while the moveme nt is under state
‘Partially Exited’. This state change has occurred after the first 'Exit Notification' (IE590) is sent to the
Trader at Exit at L4-EXP-01-07-02 Handle Exit Notification.
Thus, either a ‘Manifest Presentation’ (IE547) will be received while movement state is ‘ Goods Held for
Storing’ or while movement state is ‘Partially Exited’.
1. The manifest covering the goods of the export declaration is submitted via electronic means to the actual
Customs Office of Exit and is registered there after validation. The validation process can be a completely
automatic process. AES validates the submitted manifest against the business rules and conditions.
1.1. If the manifest presentation is invalid, AES rejects the submitted ‘Manifest Presentation’ (IE547) and
notifies with ‘Manifest Validation’ (IE548) the Trader at Exit that the presentation is invalid with the
reasons of the rejection. The movement state at the actual Customs Office of Exit remains is. AES
continues to wait for a valid manifest presentation and the flow continues from point 1.
1.2. If the manifest presentation is valid, AES records the total or partial intended leave with the given
means of transport and the goods covered by the export declaration. Then, one of the following occur:
1.2.1. If the manifest presentation covers only a part of the export declaration, the movement state shall
change to ‘Goods Released for Immediate Leave (Partial)’. At the next time(s) that the L4-EXP-
01-07-01 Process Manifest Presentation model will be initia ted (loop modelled in the L4 -EXP-
01-07-Customs Formalities at Office(s) of Exit-Process Exit) for the following Manifest(s), the
state upon a valid receipt of a ‘Manifest Presentation’ (IE547) shall change to ‘Partially Exited’.
1.2.2. If the manifest presentation received covers the whole export declaration and this manifest is
considered a valid one, then the goods are ready to immediately leave the Union , and the
movement state turns to ‘Goods Released for Immediate Leave’.
2. The Trader at Exit is notified consequently (IE548) , and the process ends with ‘Manifest Presentation
Accepted’ at this point. The process which initiated this process might continue.
Final situation:
• The ‘Manifest Presentation is Accepted’ and the movement state has been changed to either ‘Goods
released for Immediate Leave’ in case of manifest presentation covering the whole export declaration
or to ‘Partially Exited’ in case of manifest presentation covers a part of the whole export declaration.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 39 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Handle Exit Notification Process: L4 -EXP-
01-07-02
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
This process is initiated in one of the following cases:
• When AES determined that the goods can be released for Exit in process L4 -EXP-01-21-Customs
Formalities at Office(s) of Exit-Handle Controls and Release of Goods and the state is ‘Goods Released
for Immediate Leave’ and the following L4 -EXP-01-07-Customs Formalities at Office(s) of Exit -
Process Arrival is initiated.
• When a manifest presentation is accepted in L4-EXP-01-07-01-Process Manifest Presentation.
1. At both cases, one of the following cases is fulfilled:
1.1. The actual Office of Exit is notified with an ‘Exit Notification’ (IE590) by the Trader at Exit that the
goods have left, either on the basis of the export document (MRN) or on the basis of the manifest
linked to a given means of transport.
1.1.1. The process continues with the validation of the received ‘Exit Notification’ (IE590) by AES.
1.1.1.1. If the received ‘Exit Notification’ (IE590) is invalid, AES notifies Trader at Exit of Exit
Notification rejection and flow loops back waiting for a new ‘Exit Notification’ (IE590).
Process continues from Point 1.
1.1.1.2. If the received Exit Notification is valid, based on the export document MRN or on the
MRNs/item numbers referred to in the manifest, AES records the actual exit of the goods
from the Union. Total exit leads to movement state change to ‘Exited’ or, where the case
occurs, the partial exit is recorded and movement state change or remains (in case of
multiple manifests) to ‘Partially Exited’.
1.2. AES receives the Exit Information that is available through the Commercial or Port or Transport
System linked to the export document (MRN). Based on the received information MRN or on the
MRNs/item numbers referred to in the manifest, AES records the actua l exit of the goods from the
Union. Total exit leads to movement state change to ‘Exited’ or, where the case occurs, the partial
exit is recorded and movement state change or remains (in case of multiple manifests) to ‘Partially
Exited’.
2. AES identifies whether the Exit Information available at this point covers the whole movemen t, which
leads to ‘Exit Results Available’ process end. If not, the process is finalised with ‘Partially Exited’ process
end. At any case, the process which initiated this process might continue.
For each Export operation for which the movement state is set to ‘Exited’, the Customs Office of Exit sends an
‘Exit Results’ message (IE518) to the Customs Office of Export (see process L4 -EXP-01-07-03-Send Exit
Results). Otherwise, in case of ‘Partially Exited’ state, the Customs Office of Exit expects a new ‘Manifest
Presentation’ (IE547) from the Trader at Exit (see process L4-EXP-01-07-01-Process Manifest Presentation).
Final situation:
• The goods covered by an export operation have left the Union totally, the movement state has turned
to ‘Exited’ and the ‘Exit Results are Available’ to be sent.
• The goods covered by an export operation have left the Union partially, the movement state is set to
'Partially exited'. Partial exit is the procedure, where the whole consignment is in one location and is
partially exited via manifest presentations.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 40 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Send Exit Results Process: L4 -EXP-
01-07-03
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
This process starts when ‘Exit Results Available’ in L4-EXP-01-07-02-Handle Exit Notification. This can occur
either when all the goods have exited from the Customs Office of Exit under the supervision of a competent
Customs Officer or when the whole Exit information is made available about all the goods that have exited the
customs territory for a specific movement (‘Exit Notification’ (IE590) received from the Trader at Exit or Exit
Information available through Commercial or Port or Transport System).
If the Customs Office of Export is not the same as the Customs Office of Exit, AES in the Customs Office of
Exit informs the Customs Office of Export of the ‘Exit Results’ (IE518), the exit formalities are completed, and
the process ends at this point. The process which initiated this process might continue.
Final situation:
• The Customs Office of Exit informs the Customs Office of Export of the ‘Exit Results’ (IE518) and
the Exit Formalities are completed.
Major Results
R_Exit Formalities Completed
Organisation: National Customs Administration
Location: Customs Office of Exit
Since the Customs office of Exit is appropriate, the exit results are sent to the Customs Office of Export.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 41 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.10 L4-EXP-01-08-ENQUIRY PROCEDURE
Figure 12: L4-EXP-01-08-Enquiry Procedure (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 42 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 13: L4-EXP-01-08-Enquiry Procedure (Part B)
Major Events
E_Expiry of Time Limit to Receive Exit Results
Organisation: National Customs Administration
Location: Customs Office of Export
The time allotted for the receipt of the exit confirmation has expired. This time -out indicates that Enquiry
Procedure may be initiated. The value of this ‘timer’ may be manually adjusted by a Customs Officer, where
necessary. When the exit confirmation is received from the Office of Exit, or when the export operation is
cancelled, the timer is stopped.
E_Information on Non-Exited Export Received (at earlier 10 days after the release of the movement)
Organisation: National Customs Administration
Location: Customs Office of Export
The Trader sends on his own initiative an ‘Information on Non-Exited Export’ (IE583) message to AES at the
Customs Office of Export for communicating the exit of the goods. The Trader can send this message at earlier
10 days after the release of the movement.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 43 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Processes
Enquiry Procedure Process: L4-EXP-
01-08
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
The process of Enquiry procedure may be initiated in two possible ways with two start events:
• Time Limit Expiry to Receive Exit Results.
• Information on Non-Exited Export Received (at earlier 10 days after the release of the movement).
When AES at the Customs Office of Export identifies one of the above, the following cases might occur:
1. The time limit to receive Exit Results expires after 90 days following the release of the goods and AES
at the Customs Office of Export records this time limit expiration. Following this, the Customs Officer
acknowledges the time limit expiration and registers the decision to initiate the Enquiry Procedure. At
this point, the flow of the 1 st case merges with the case of 2.1 and both flows continue similarly.
Subsequently, AES records the initiation of the Enquiry Procedure. Following this, the ‘L4 -EXP-01-
17-Operation Status Check’ process is exe cuted. After the execution of the operation status check
mechanism, at this point, AES checks whether the Exit Results were sent to the Customs Office of
Export. The two following cases may occur:
1.1. The Exit Results have been received by the Customs Office of Export. The process ends here. The
process that has called the Enquiry Procedure process can now continue.
1.2. The Exit Results have not been received by the Customs Office of Export. At this point, AES at
the Customs Office of Export identifies whether the Trader provided on his own initiative
Additional Information regarding the movement. The following cases may occur:
1.2.1. If the Trader did not provide on his own initiative Additional Information regarding the
movement of the goods via an ‘Information on Non -Exited Export’ (IE583), meaning
that the Enquiry Procedure was initiated by the Customs Officer due to the expiry of t he
time limit to Receive Exit Results, the process L4-EXP-01-27-Handle Goods Movement
Additional Information is initiated. Upon the execution of this process, the flow stops
here and one of the following might have occurred:
1.2.1.1. The ‘Exit Results’ (IE518) have been received at the Customs Office of Export.
1.2.1.2. Sufficient Alternative Evidence is available at the Customs Office of Export and thus
can certify the exit of the goods.
1.2.1.3. Enquiry Information Code submitted in the ‘Information on Non -Exited Export’
(IE583) by the Trader was ‘Will not Exit’.
1.2.1.4. The time limit to Receive Alternative Evidence has expired.
1.2.2. If the Trader provided additional information on the movement of the goods on his own
initiative via an ‘Information on Non -Exited Export’ (IE583), the process ‘L4 -EXP-01-
08-04-Handle Alternative Evidence’ is initiated. Upon the execution of this process, the
flow stops here and one of the following might occur:
1.2.2.1. Sufficient Alternative Evidence is available at the Customs Office of Export and
thus can certify the exit of the goods.
1.2.2.2. The provided Alternative Evidence was found insufficient or no alternative evidence
was provided.
2. The Trader sends on his own initiative ‘Information on Non -Exited Export’ (IE583) to AES at the
Customs Office of Export. AES validates the received ‘Information on Non -Exited Export’ (IE583)
message. The two following cases may occur:
2.1. The validation of the received ‘Information on Non-Exited Export’ (IE583) is successful and AES
records the IE583, and the flow continues from point 1, from the point when the AES records the
initiation of the Enquiry Procedure.
2.2. The validation of the received ‘Information on Non-Exited Export’ (IE583) is not successful. AES
at the Customs Office of Export notifies the Declarant/ Representative with a ‘Rejection from
Office of Export’ (IE556). The flow stops at this point.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 44 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Final Situation:
• The Trader has sent on his own initiative an ‘Information on Non -Exited Export’ (IE583)
message which was validated and found invalid by AES at the Customs Office of Export. The
‘Information on Non-Exited Export’ (IE583) message is rejected.
• Following the Operation Status Check mechanism execution, the exit results are available at
the Customs Office of Export.
• Sufficient Alternative Evidence is available at the Customs Office of Export ; thus the exit of
the goods can be certified.
• The Enquiry Information Code mentioned in the ‘Information on Non-Exited Export’ (IE583)
message sent by the Trader is ‘Will not Exit’.
• The time limit to receive Alternative Evidence has expired.
• The Trader has provided on his own initiative sufficient alternative evidence which is
available at the Customs Office of Export so as to be able to certify the exit of the goods .
• The Trader on his own initiative has either provided alternative evidence which was found
insufficient by the Customs Officer or did not provide alternative evidence while indicating
that the goods had already exited.
Handle Alternative Evidence Provided by the Trader on his own Initiative Process: L4 -EXP-
01-08-04
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
The process starts with the following start event:
• Enquiry Procedure was initiated by Trader and Exit Results have not been received (The movement is
in state other than ‘Exited’, ‘Goods not Allowed to Exit’).
When AES at the Customs Office of Export identifies the above, the following occurs:
AES identifies the Enquiry Information Code declared in ‘Information on Non -Exited Export’ (IE583). Based
on the identified Enquiry Information Code, the following may occur:
1. The Enquiry Information Code is ‘Exited -Alternative Evidence’. The Customs Officer registers the
decision on Alternative Evidence. AES records the decision on Alternative Evidence. At this point, the
following may occur:
1.1 The provided Alternative Evidence is considered sufficient. The flow stops at this point. The initial
process that called this process can now resume.
1.2 The provided Alternative Evidence is considered insufficient (or for the case of point 2 no
alternative evidence was provided). AES at the Customs Office of Export notifies the Declarant/
Representative via an ‘Rejection from Office of Export’ (IE556) mess age. The flow stops at this
point. The parent process that initiated this process can now resume.
2. The Enquiry Information Code is ‘Exited- No Alternative Evidence’. The flow continues from point 1.2.
Final situation:
• The Alternative Evidence provided by the Trader is considered sufficient .
• The Alternative Evidence provided by the Trader is considered insufficient or no alternative evidence
at all was provided.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 45 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Extend Time Limit to Receive Alternative Evidence Process: L4 -EXP-
01-08-05
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process starts as follows:
• Decision to Extend the Time Limit to receive Alternative Evidence.
When AES identifies the above, the following occurs:
The Customs Officer has decided to extend the time limit to Receive Alternative Evidence. The Customs Officer
registers the decision to extend the time limit to Receive Alternative Evidence, AES records this decision , and
the flow stops at this point. The time limit to Receive Alternative Evidence is extended and the initial process
that called this process may now resume.
Final Situation:
• Time Limit to Receive Alternative Evidence is extended.
Major Results
R_Exit Results Received
Organisation: National Customs Administration
Location: Customs Office of Export
AES at the Customs Office of Export has received the Exit Results from the Customs Office of Exit. This result
is applicable for both the case of reception of exit results after the operation status check mechanism and also
the reception of the exit results while the handling of additional information provided by the Trader is ongoing.
R_Sufficient Alternative Evidence is Available
Organisation: National Customs Administration
Location: Customs Office of Export
The provided alternative evidence is considered sufficient in order to confirm the exit of the goods. This result
is applicable for both the case of initiation of the process of Enquiry Procedure due to the expiry of the time
limit to receive exit results but also the case in which the Trader has provided information on the movement on
his own initiative.
R_Enquiry Information Code is ‘Will not Exit’
Organisation: National Customs Administration
Location: Customs Office of Export
The Declarant/Representative informed the Customs Office of Export that the goods will not exit the Customs
Territory of the Union.
R_Rejected after Insufficient or no Alternative Evidence
Organisation: National Customs Administration
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 46 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Location: Customs Office of Exit
The Declarant/Representative informed the Customs Office of Export that the goods will not exit the Customs
Territory of the Union.
R_Information on Non-Exited Export Rejected
Organisation: National Customs Administration
Location: Customs Office of Export
AES at the Customs Office of Export rejects the Information on Non-Exited Export received by the Trader.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 47 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.11 L4-EXP-01-16-OPERATION INFORMATION QUERY
Figure 14: L4-EXP-01-16-Operation Information Query
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 48 / 129
Document version 7.00 EN dated 29/04/2025
Confidentiality: Commission use (CU)
Major Events
E_Customs Officer requests export operation information
Organisation: National Customs Administration
Location: Any Customs Office connected to AES
A Customs Officer with an appropriate level of authorisation and access to AES at any Customs Office, requests
the export operation information for an export with a given MRN.
Minor Events
E_Receive Operation Information Request
Organisation: National Customs Administration
Location: Customs Office of Export
This event indicates that the operation information request is received.
Processes
Operation Information Query Process: L4-EXP-
01-16
Organisation: National Customs Administration
Location: Requesting Customs Office
Constraint: N/A
Description:
The operation information query process is initiated by a Customs Officer at the requesting office.
The process L4-EXP-01-16-01 is executed where the Customs Officer registers his/her operation information
query by submitting an MRN in AES. One of the following cases is fulfilled:
1. The requested information is available in AES. In this case the Requesting Customs Office retrieves the
information, and the process ends at this point.
2. The requested information is not available. AES at the requesting customs office sends an operation
information request with ‘Export Query’ (IE527). The requested customs office ( Customs Office of Export)
receives the ‘Export Query ’ (IE527) and attempts to retrieve the information to respond to the query. The
process L4-EXP-01-16-02 Handle Request for Export Operation Information is executed. The Customs Office
of Export sends either a positive ‘Response To Export Query ’ (IE538) with the requested data or a negative
export query response if the requested data for the specific MRN is not known. AES at the requesting customs
office records this response and the process L4-EXP-01-16-03 Display Requested Export Operation Information
is executed. The received data is displayed to the Customs Officer and the process ends when the operation
information query result (either positive or negative) is available at the requesting customs office.
Final situation:
• The Operation Information Query Result sent by the Customs Office of Export.
• The Operation Information Query Result received by the Requesting Customs Office.
Submit Request for Export Operation Information Process: L4 -EXP-
01-16-01
Organisation: National Customs Administration
Location: Requesting Customs Office
Constraint: N/A
Description:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 49 / 129
Document version 7.00 EN dated 29/04/2025
Confidentiality: Commission use (CU)
The process starts with the Customs Officer from any customs office to register a request for export operation
information based on a given MRN to AES.
AES records the operation information query and then identifies if the requesting information is available. One
of the following cases is fulfilled:
1. The export operation information is available at the office where the request is submitted. AES displays the
information to the Customs Officer immediately and the process ends at this point.
2. The export operation information is not available at the Office where the request is submitted. AES notifies
the Customs Officer that the information is not available and automatically sends a ‘Export Query’ (IE527) to
the Country of Export and the process ends at this point.
Final situation:
• The export operation information is available and is displayed to the Customs Officer.
• A request for export operation information is submitted to the Country of Export.
Handle Request for Export Operation Information Process: L4 -EXP-
01-16-02
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
The process starts when the Customs Office of Export receives an ‘Export Query’ (IE527) from a Customs
Office. AES records the request and identifies if the export operation information for the requested MRN is
available.
1. If the operation information is available the AES retrieves this information and sends a positive ‘Response to
Export Query’ (IE538) to the requesting Customs Office and the process ends at this point.
2. If the operation information is not available, the AES sends a negative ‘Response to Export Query’ (IE538)
to the requesting customs office that contains the reason for not providing the movement details (e.g. unknown
MRN).
Final situation:
• A positive/negative ‘Response to Export Query’ (IE538) is sent by the Customs Office of Export to
the Requesting Customs Office.
Display Requested Export Operation Information Process: L4 -EXP-
01-16-03
Organisation: National Customs Administration
Location: Requesting Customs Office
Constraint: N/A
Description:
The process starts when the Requesting Customs Office receives either a positive or a negative ‘Response to
Export Query’(IE538). AES records the response and displays either the received information that was available
or the reasons for not providing the requested information and the process ends at this point.
Final situation:
• The response to export query (positive/negative) is provided to the Requesting Customs Office.
Major Results
R_ Response to Export Query Available
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 50 / 129
Document version 7.00 EN dated 29/04/2025
Confidentiality: Commission use (CU)
Organisation: National Customs Administration
Location: Any Customs Office connected to AES (the requesting Office)
This event indicates that the operation information query result is available.
R_ Operation Information Query Result Available
Organisation: National Customs Administration
Location: Any Customs Office connected to AES (the requesting Office)
This event indicates that the operation information query result is available.
Minor Results
R_Operation Information Query Result Sent
Organisation: National Customs Administration
Location: Any Customs Office connected to AES (the requesting Office)
This event indicates that the operation information query result is sent.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 51 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.12 L4-EXP-01-17-OPERATION STATUS CHECK
Figure 15: L4-EXP-01-17-Operation Status Check
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 52 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Customs Initiated Operation Status Check
Organisation: National Customs Administration
Location: Requesting Customs Office
A Competent Customs Officer at the Requesting Customs Office initiates the operation status check.
E_Operation Status to Be Verified
Organisation: National Customs Administration
Location: Requesting Customs Office
The operation status check is initiated either by the enquiry procedure, or the invalidation of export declaration
processes.
Minor Events
E_Operation Status Request Initiated
Organisation: National Customs Administration
Location: Customs Office of Exit
The Customs Office of Exit receives a status request ( IE594) for an export operation identified by a specific
MRN.
Processes
Operation Status Check Process: L4-EXP-
01-17
Organisation: National Customs Administration
Location: Requesting Customs Office
Constraint: N/A
Description:
The Operation Status Check process is initiated either by the Customs Officer or by the Enquiry Procedure or
by the Invalidation processes. The Requesting Customs Office requests the status from the Customs Office of
Exit by means of a ‘Status Request’ (IE594). The Customs Office of Exit handles the Operation Status Check.
The Requesting Customs Office receives the ‘Status Response’ (IE595) and if there are available ‘Exit Results’
(IE518), this information should be also resent from the Customs Office of Exit. The movement state is up to
date. The Exit Results, if received, are recorded and the process ends at this point.
Final situation:
• The movement state is up to date.
Initiate Operation Status Request Process: L4 -EXP-
01-17-01
Organisation: National Customs Administration
Location: Requesting Customs Office
Constraint: N/A
Description:
The process is initiated either by the Customs Officer or by the Enquiry Procedure or by the Invalidation.
The Customs Officer must register his/her Operation Status Request.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 53 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
The Requesting Customs Office requests the status from the Customs Office of Exit by means of a ‘Status
Request’ (IE594). The process ends at this point and the process which initiated this process can now continue.
Final situation:
• AES sends the operations ‘Status Request’ (IE594) to the Customs Office of Exit.
Handle Operation Status Request Process: L4 -EXP-
01-17-02
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
1. AES receives an Operation ‘Status Request’ from the requesting customs office for an export operation
identified by a specific MRN (IE594) and records it in its systems.
2. AES retrieves the operation status of the export operation, identified by the MRN given in the status request.
3. AES informs the requesting customs office by sending a ‘Status Response’ (IE595) that contains the MRN
and the movement state.
4. AES identifies whether the movement state indicates if the goods have already exited or not and one of the
following occurs:
4.1. If the movement state shows that the goods have exited (the movement state is set to ‘Exited’, 'Goods
not Allowed to Exit'), then AES informs the requesting customs office that the goods have exited by
sending the ‘Exit Results (IE518)’. The process ends at this point.
4.2. If the movement state shows that the goods have not exited, then the process ends at this point.
Final situation:
One of the following decisions is taken:
• If the movement state shows that the goods have exited, then AES sends a ‘Status Response’ (IE595)
and the ‘Exit Results’ (IE518) to the requesting customs office.
• If the movement state shows that the goods have not exited, then AES sends a ‘Status Response ’
(IE595) to the requesting customs office.
Handle Operation Status Response Process: L4 -EXP-
01-17-03
Organisation: National Customs Administration
Location: Requesting Customs Office
Constraint: N/A
Description:
AES receives a ‘Status Response’ (IE595) on the Operation ‘Status Request’ (IE594) that has been sent before.
AES compares the newly recorded export movement state with the current movement state for the export
operation that is identified by a specific MRN.
One of the following cases is fulfilled:
1. If both states match, then the current movement state is verified, and the process ends at this point.
2. If the states don't match, then the Customs Officer at the Customs Office of Export, considering the reported
status in IE595, decides if further actions are required or not. At this point, the following may occur:
2.1. The Requesting Customs Office receives the ‘Exit Results’ (IE518) from the Customs Office of Exit.
Once AES receives the Exit Results, it records them, and the process ends at this point.
2.2. The Requesting Customs Office does not receive the ‘Exit Results’ (IE518) and then the process ends
at this point.
Final situation:
One of the following decisions is taken:
• If the movement state received with the Status Response matches with the movement state of the export
operation at stake, then there is no following decision.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 54 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
• If the movement state received with the Status Response does not match with the movement state of
the export operation at stake , then the Customs Officer decides whether the Enquiry procedure or the
Invalidation process will take place.
Major Results
R_Operation Status Check Completed
Organisation: National Customs Administration
Location: Requesting Customs Office
The Operation Status Check has been completed and the movement state is up to date.
Minor Results
R_Operation Status Sent
Organisation: National Customs Administration
Location: Office of Exit
The goods of the export operation wherefore an operation status check has been performed have not exited and
the operation status update has been sent to the requesting customs office.
R_Exit Results Sent
Organisation: National Customs Administration
Location: Office of Exit
The goods of the export operation wherefore an operation status check has been performed have exited and the
exit results have been sent to the requesting customs office.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 55 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.13 L4-EXP-01-19-HANDLE DIVERSION
Figure 16: L4-EXP-01-19-Handle Diversion (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 56 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 17: L4-EXP-01-19-Handle Diversion (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 57 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_AER Not Available
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at the Customs Office of Exit (Actual in case of Diversion/Declared in case of AER missing) has not
available the declaration data (AER).
E_Receive Declaration Request
Organisation: National Customs Administration
Location: Customs Office of Export
AES receives a declaration request from the Customs Office of Exit.
E_Receive Forwarded Arrival Advice
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at the Customs Office of Exit (Declared) receives a Forwarded Arrival Advice (IE524) from the Customs
Office of Export in case there has been a diversion.
Processes
Handle Diversion Process: L4 -EXP-
01-19
Organisation: National Customs Administration
Location: Customs Office of Export, Customs Office of Exit
Constraint:
The AES of the Customs Office of Exit having sent out a ‘Declaration Request Export’ (IE502) must be able to
receive and process following possible responses:
• ‘AER Response’ (IE503), including the requested export declaration data (case 1), or
• ‘AER Response’ (IE503), not including the requested export declaration data (case 2).
It should be noted that the Multiple Diversion process is not supported in this AES model on its own, since it
requires multiple pools of Requesting Offices of Exit.
Description:
The process L4 -EXP-01-19 is initiated when the Customs Office of Exit has not any information on the
declaration data (AER Not Available). This may occur either because the AER is not available at the Customs
Office of Exit (Declared) due to technical issues (AER missing case) or because the Customs Office of Exit that
the goods presented is not the declared one (i.e. Customs Office of Exit (Actual) in Diversion case). This process
is initiated either from the L4 -EXP-01-00-AES Master Process (considering AE R missing case or Diversion
case) or from the L4 -EXP-01-25-01-Cross-Check of the Export MRN(s) (considering arrival of 'Transit
Presentation Notification' (IE190), thus Export Followed by Transit case and the AES system shall check the
Export MRN(s) unknow n, in order to reply back to NCTS Customs Office of Departure with a positive or
negative 'Transit Presentation Notification Response' (IE191)).
1. The AES system in Customs Office of Exit (Actual) requests AER by sending an ‘Export Declaration
Request’ (IE502) to the Customs Office of Export and the movement state changes to ‘AER Requested’.
2. AES at the Office of Export checks for the requested data (export customs declaration) referenced by the
MRN in order to identify if they are available in the system and if a negative or positive ‘AER Response’
(IE503) must be sent. One of the following occurs:
2.1. If the customs declaration with the given MRN exists, AES forwards the subset of the customs
declaration data to the Customs Office of Exit (Actual). A positive response ‘AER Response’ (IE503)
shall be sent if the MRN is related to the export declaration. The response may contain the safety and
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 58 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
security risk analysis results. This customs declaration data shall be forwarded to Office of Exit (the
initially declared one), in case of AER missing, too - this means that, Office of Exit may have not
received the ‘AER’ (IE501) while goods arrive in that office. Next, it is investigated whether diversion
has occurred, in order the Customs Office of Export to inform the Customs Office of Exit (Declared)
on this change of the movement.
2.1.1. If diversion occurred, AES at the Customs Office of Export also sends a ‘Forwarded Arrival
Advice’ (IE524) to the Customs Office of Exit (Declared). In the case of international diversion
a ‘Forwarded Arrival Advice’ (IE524) is sent in the Office of Exit (Declared) (which has already
received an ‘ AER’ (IE501), in order to close the movement that has been presented in another
Customs Office of Exit (Actual)). The process ends at this point in the Customs Office of Export
with ‘AER Request Accepted’ and continues with the Customs Office of Exit (Declared) in point
3 and Customs Office of Exit (Actual) in point 4.
2.1.2. In the exceptional case of missing ‘AER’ (IE501) in the Customs Office of Exit (Declared), then
no diversion has occurred and therefore, no ‘Forwarded Arrival Advice’ (IE524) is sent. The
process ends at this point in the Customs Office of Export with ‘AER Request Accepted’ and
continues with Customs Office of Exit (which in this case is the Declared one) directly from
point 4.
2.2. If the customs declaration with the given MRN is not known to the Customs Office of Export or the
diversion cannot be accepted because of the state of the movement (e.g. goods have already exited),
then a negative ‘AER Response’ (IE503) is sent to the Cust oms Office of Exit (Actual). A negative
response, shall be sent in one of following cases:
2.2.1. If the requested Country does not know the MRN, in the context of an export customs
declaration, the process at Customs Office of Export ends with ‘AER Request Rejected’.
2.2.2. If the movement is not in movement state ‘Goods Released for Export’, the process at Customs
Office of Export ends with ‘AER Request Rejected’.
2.2.3. If a diversion occurred, but AES at the Customs Office of Export rejects it. The process at
Customs Office of Export ends with ‘AER Request Rejected’.
3. The Customs Office of Exit (Declared) receives the ‘Forwarded Arrival Advice’ (IE524) and records it in
its AES system.
3.1. The diversion is recorded, and the movement state alters to ‘Arrived Elsewhere’ at this point.
3.2. The Timer to Receive Arrival at Exit is initiated and then, one of the following two cases might occur:
3.2.1. Despite of this diversion, the Goods are finally presented in the Customs Office of Exit
(Declared) at a later point. Thus, it shall be re-considered whether declaration data are available
or need to be requested from the Customs Office of Export with 'Dec laration Request Export'
(IE502). The process at the Customs Office of Exit (Declared) ends with ‘Arrival at Exit’. The
process for the Customs Office of Exit (Declared) ends at this point and shall continue from L4-
EXP-01-24-Customs Formalities at Office(s) of Exit-Process Arrival Notification.
3.2.2. The Timer to receive Arrival at Exit expires and no goods are presented at this Customs Office
of Exit (Declared), thus, the process ends at this point at the at the Customs Office of Exit
(Declared) and the movement state is changed to ‘Handled Elsewhere', which is a final state.
4. The Customs Office of Exit (Actual) (in case of AER missing, this Customs Office of Exit is the Declared
one) receives the AER response (sent by the Office of Export), records it and the following cases might
occur:
4.1. If the AER data were available (positive 'AER Response' (IE503)) in the Customs Office of Export,
AES system in the Customs Office of Exit (Actual) checks whether the AER request concerned an
unknown Export MRN for an Export Movement Followed by Transit an d one of the following cases
might occur:
4.1.1. If the AER Request was not for an Export Movement Followed by Transit, the process at the
Customs Office of Exit (Actual) ends at this point with the movement state changing to 'Goods
presented at exit'. The process which initiated this process can now continue.
4.1.2. If the AER Request was for an Export Movement Followed by Transit, the process at the
Customs Office of Exit (Actual) ends at this point with ‘Positive AER Response received for an
Export Movement Followed by Transit’. The process which initiated this proc ess can now
continue.
4.2. If the AER data were not available (negative 'AER Response' (IE503)) in the Customs Office of
Export, AES system in the Customs Office of Exit (Actual) checks whether the AER request
concerned an unknown Export MRN for an Export Movement Followed by Transi t and one of the
following cases might occur:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 59 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
4.2.1. If the AER Request was not for an Export Movement Followed by Transit:
4.2.1.1. A new Timer to receive Arrival at Exit information is initiated.
4.2.1.2. The Trader at Exit is notified of Diversion rejection with a ‘Diversion Rejection
Notification’ (IE521).
4.2.1.3. Following, one of the following two cases is fulfilled:
4.2.1.3.1. The Goods arrive at Exit in this Customs Office of Exit at a later point. Thus, it shall
be re-considered whether declaration data are available or need to be requested from
another Customs Office of Export. The process at the Customs Office of Exit
(Actual) ends with ‘Arrival at Exit’. The process for the Customs Office of Exit
(Actual) ends at this point and shall continue from L4 -EXP-01-24-Customs
Formalities at Office(s) of Exit-Process Arrival Notification.
4.2.1.3.2. The Timer to receive Arrival at Exit expires and no goods are presented at this
Customs Office of Exit or Arrival at Exit information is made available, thus, the
process ends at this point at the at the Customs Office of Exit (Actual) and the
movement state is changed to ‘Handled Elsewhere', which is a final state.
4.2.2. If the AER Request was for an Export Movement Followed by Transit, the process at the
Customs Office of Exit (Actual) ends at this point with ‘Negative AER Response received for
an Export Movement Followed by Transit’. The process which initiated this proc ess can now
continue.
Note: In case the Customs Office of Exit (Declared) receives an IE524 , and the movement state is not ‘AER
Created’ or ‘Goods Presented at Exit’, this indicates an unforeseen circumstance. Therefore, an IE524 received
by the Customs Office of Exit (Declared) for the specific MRN in this case, is not expected and shall be rejected
as an out -of-sequence IE. Following this, the Custom Office of Export is expected to further investigate this
unforeseen situation and possibly block the state of the MRN. This investigation shall be carried out-of-system.
Final situation:
● AES at the Customs Office of Export accepts the AER Request and sends the declaration data available
to the Customs Office of Exit requesting this information. The process ends with ‘AER Request Accepted’.
● AES at the Customs Office of Export rejects the AER Request and sends a negative notification to AER
Request to the Customs Office of Exit requesting this information. The process ends with ‘AER Request
Rejected’.
● AES at the Customs Office of Exit (Declared) receives a ‘Forwarded Arrival Advice’ (IE524) from the
Customs Office of Export, records the diversion, but later on goods arrive at this Customs Office of Exit or
Arrival at Exit is submitted by Trader at Exit for this MRN. The process ends with 'Arrival at Exit'.
● AES at the Customs Office of Exit (Declared) receives a ‘Forwarded Arrival Advice’ (IE524) from the
Customs Office of Export, records the diversion and no goods arrive at this Customs Office of Exit or Arrival
at Exit is submitted by Trader at Exi t for this MRN. The movement state is set to ‘Handled Elsewhere', which
is a final state.
● AES at the Customs Office of Exit (Actual) receives the declaration data with ‘AER Response’ (IE503)
from the Customs Office of Export, records the AER Response, the movement does not concern Export
Followed by Transit, thus, the movement state is set to ‘Goods Presented at Exit'.
● AES at the Customs Office of Exit (Actual) receives the declaration data with ‘AER Response’ (IE503)
from the Customs Office of Export, records the AER Response, the movement concerns Export Followed by
Transit, thus, the process ends with ‘Positi ve AER Response received for an Export Movement Followed by
Transit’.
● AES at the Customs Office of Exit (Actual) receives ‘negative’ response to declaration request with ‘AER
Response’ (IE503) from the Customs Office of Export, the movement concerns Export Followed by Transit,
thus, the process ends with ‘Negative AER Response received for an Export Movement Followed by Transit’.
● AES at the Customs Office of Exit (Actual) receives ‘negative’ response to declaration request (IE503)
from the Customs Office of Export, but later on goods arrive at this Customs Office of Exit or Arrival at Exit is
submitted by Trader at Exit for this MRN. The process ends with 'Arrival at Exit'.
● AES at the Customs Office of Exit (Actual) receives ‘negative’ response to declaration request with ‘AER
Response’ (IE503) from the Customs Office of Export, and no goods arrive at this Customs Office of Exit or
Arrival at Exit is submitted by Trader at Exit for this MRN. The movement state is set to ‘Handled Elsewhere’,
which is a final state.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 60 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Results
R_AER Request Accepted at Customs Office of Export
Organisation: National Customs Administration
Location: Customs Office of Export
AER Request has been accepted (diversion occurs) and declaration data and arrival advice have been sent to the
Customs Offices of Exit (Declared and Actual). In case of missing AER, AER Request has been accepted ( no
diversion occurs) and AER data resent to the Customs Office of Exit.
R_AER Request Rejected at Customs Office of Export
Organisation: National Customs Administration
Location: Customs Office of Export
AER Request has been rejected from the Customs Office of Export.
R_Goods Presented at Customs Office of Exit (Actual)
Organisation: National Customs Administration
Location: Customs Office of Exit
Customs Office of Exit received the declaration data from the Customs Office of Export and the movement
does not concern Export followed by Transit.
R_Positive AER Response received for an Export Movement Followed by Transit at Customs Office of
Exit (Actual)
Organisation: National Customs Administration
Location: Customs Office of Exit
Customs Office of Exit received the declaration data from the Customs Office of Export and the movement
concerns Export followed by Transit.
R_Negative AER Response received for an Export Movement Followed by Transit at Customs Office of
Exit (Actual)
Organisation: National Customs Administration
Location: Customs Office of Exit
Customs Office of Exit received a negative response to request for the declaration data from the Customs Office
of Export and the movement concerns Export followed by Transit.
R_Arrival at Exit at Customs Office of Exit (Actual)
Organisation: National Customs Administration
Location: Customs Office of Exit
For the movement which does not concern Export Followed by Transit, this final state is reached when after
this diversion rejection (while timer to receive arrival at exit is still running) goods have arrived at Exit and the
Customs Office of Exit (Actual).
R_Handled Elsewhere at the Customs Office of Exit (Actual)
Organisation: National Customs Administration
Location: Customs Office of Exit
For the movement which does not concern Export followed by Transit, this final state is reached when after this
diversion rejection, timer to receive arrival at exit expires.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 61 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
R_Arrival at Exit at Customs Office of Exit (Declared)
Organisation: National Customs Administration
Location: Customs Office of Exit
This final state is reached when after this diversion rejection and while timer to receive arrival at exit is still
running goods have arrived at Exit and the Customs Office of Exit (Declared), which now serves as the Customs
Office of Exit (Actual).
R_Handled Elsewhere at the Customs Office of Exit (Declared)
Organisation: National Customs Administration
Location: Customs Office of Exit
This final state is reached when after this diversion rejection, timer to receive arrival at exit expires.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 62 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.14 L4-EXP-01-21-CUSTOMS FORMALITIES AT OFFICE(S)
OF EXIT-HANDLE CONTROLS AND RELEASE OF GOODS
Figure 18: L4-EXP-01-21-Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods
(Part A)
Figure 19: L4-EXP-01-21-Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods
(Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 63 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Goods Presented at Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
Goods are presented at Exit either after normal export procedure, or after diversion.
Processes
Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods Process: L4 -EXP-
01-21
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
Process is initiated while ‘Goods are Presented at Exit’ either after L4-EXP-01-24-Customs Formalities at
Office(s) of Exit-Process Arrival Notification completion or after L4-EXP-01-19-Handle Diversion completion
with AER Response being positive.
1. Following the presentation of goods at the Customs Office of Exit, the AES at the Customs Office of Exit
might perform Risk Analysis, thus, the Process L4-EXP-01-01-01-02-Request and Record Risk Analysis
is executed.
2. Based on the above, the AES at the Customs Office of Exit decides whether controls are about to be
performed, and this decision is registered in its system in Process L4 -EXP-01-21-01-
Register and Record Control Decision at Office of Exit, which is initiated.
3. Next, one of the below two cases might occur:
3.1. The decision shall indicate that goods shall be controlled.
3.1.1. After goods have been controlled, the p rocess L4 -EXP-01-21-02-Register Control Results at
Office of Exit is executed, in order the control results to be registered. Based on the Control
Results, one of the above might occur:
3.1.1.1. Either the control results will be not satisfactory, hence, the movement state changes to
‘Goods Not Allowed to Exit’ and process ends here, as this is a final state.
3.1.1.2. Or, the control results will be satisfactory/minor discrepancies, hence, the goods are ready
to be released. Process continues from point 4.
3.2. The decision shall indicate that goods are not controlled, and they are ready to be released. Process
continues from point 4.
4. Process L4 -EXP-01-21-03-Release Goods for Exit is executed, where the goods are released for exit.
Movement state changes to ‘Goods Released for Exit’ and this is a final state, thus, process ends at this
point.
Process shall continue with L4-EXP-01-07-Customs Formalities at Office(s) of Exit-Process Exit.
Final Situation:
• The ‘Goods Released for Exit’ either after no controls performance or after satisfactory/minor
discrepancies control results at the Customs Office of Exit.
• The ‘Goods Not Allowed to Exit’ after unsatisfactory controls results at the Customs Office of Exit.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 64 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Register and Record Control Decision at Office of Exit Process: L4 -EXP-
01-21-01
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process L4-EXP-01-21-01-Register and Record Control Decision at Office of Exit is executed in case ‘Risk
Analysis Results Recorded’ in the process L4-EXP-01-21-Customs Formalities at Office(s) of Exit -Handle
Controls and Release of Goods. The Customs Officer at the Customs Office of Exit compiles all the information
(the export movement information and the risk analysis result) in order to register control decision. Even if the
risk analysis is an automatic process, the final decision to control must be taken by the Customs Officer.
The Customs Officer registers the control decision for AES and this decision is recorded in the AES system of
the Customs Office of Exit. Following, one of the two cases might occur:
1. The Control Decision indicates that goods need to be controlled and the type of controls to be performed
(e.g. documentary, physical check).
1.1. The AES at the Customs Office of Exit notifies the Trader at Exit about the decision to control with
an ‘Exit Control Decision Notification’ (IE561). The movement state is set to 'Under Control'. The
process which initiated this process might continue.
2. The Control Decision indicates that goods do not need to be controlled, thus, the movement state change to
‘Goods Ready to Be Released’ for exit. The process which initiated this process might continue.
Final Situation:
One of the following decisions is registered:
• No control at all, movement state is set to ‘Goods Ready to Be Released’.
• Controls will be performed.
• The movement state is set to ‘Under Control’.
Register Control Results at Office of Exit Process: L4 -EXP-
01-21-02
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process L4-EXP-01-21-02-Register Control Results at Office of Exit is executed in case goods are ‘Under
Control’ in the process L4 -EXP-01-21-Customs Formalities at Office(s) of Exit -Handle Controls and Release
of Goods. The process starts when controls have taken place (manual process).
The Customs Officer at the Customs Office of Exit registers the results of the control in AES. Control results
recorded may be one of the following two:
1. The Control Results are satisfactory or with minor discrepancies, thus, the movement state changes to
‘Goods Ready to Be Released’ and process ends. In case of minor discrepancies, t he minor discrepancies
will be reported to the Office of Export in due time, with the Control ‘Exit Results’ (IE518). The process
which initiated this process might continue.
2. The Control Results are not satisfactory, thus, the following two shall occur in parallel:
2.1. The Office of Export is notified about the ‘Exit Results’ (IE518 reporting the detected discrepancies)
2.2. The Trader at Exit is notified with ‘Exit Release Rejection’ (IE522) due to the detected discrepancies
identified in Exit Controls.
In both two above cases, the goods are not allowed to exit, hence the export operation is stopped here without
prejudice of any subsequent measure to be taken. The movement state changes to ‘Goods Not Allowed to Exit’,
this process ends at this point and the process which initiated this process might continue.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 65 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Final situation:
Control results are stored in AES:
• Either the goods are ready to be released, and the movement state is set to ‘Goods Ready to Be Released’.
• Or, goods are not allowed to exit (in case of 'not satisfactory' control results considered) and the movement
state is set to ‘Goods Not Allowed to Exit’.
Release Goods for Exit Process: L4 -EXP-
01-21-03
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process L4-EXP-01-21-03-Release Goods for Exit is executed in case ‘Goods Ready To Be Released’ in
the process L4 -EXP-01-21-Customs Formalities at Office(s) of Exit -Handle Controls and Release of Goods.
The goods are released for exit and AES at the Customs Office of Exit notifies the Trader at Exit with ‘Exit
Release Notification’ (IE525). The movement state is set to 'Goods Released for Immediate Leave'. If the goods
are to be stored prior the exit, the movement status is set to 'Goods held for storing'. In both cases, this process
ends with ‘Goods Released for Exit’ and the process which initiated this process might continue.
Final Situation:
AES releases the goods for exit. The movement state is set to 'Goods released for Immediate Leave'. If the goods
are to be stored prior the exit, the movement state is set to 'Goods Held for Storing'. In both cases, this process
ends with ‘Goods Released for Exit’.
Major Results
R_Goods Not Allowed for Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at Customs Office of Exit has determined that the goods are not allowed to exit.
R_Goods Released for Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at Customs Office of Exit has determined that the goods are released for exit.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 66 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.15 L4-EXP-01-23-CUSTOMS FORMALITIES AT OFFICE OF
EXPORT-HANDLE EXIT RESULTS/ALTERNATIVE
EVIDENCE
Figure 20: L4-EXP-01-23-Customs Formalities at Office of Export-Handle Exit Results/Alternative
Evidence (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 67 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 21: L4-EXP-01-23-Customs Formalities at Office of Export-Handle Exit Results/Alternative
Evidence (Part B)
Major Events
E_Exit Results Available for Export Movement Followed by Transit
Organisation: National Customs Administration
Location: Customs Office of Export
AES receives Exit Results for a movement that is followed by Transit.
E_Sufficient Alternative Evidence Available for an Export Movement Followed by Transit
Organisation: National Customs Administration
Location: Customs Office of Export
AES receives sufficient alternative evidence for an export movement followed by Transit.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 68 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
E_Customs Office of Export is the same office as the Customs Office of Exit and Exit Notification is
Available
Organisation: National Customs Administration
Location: Customs Office of Export
AES receives an Arrival at Exit Notification when the Customs Office of Export is the same as Customs Office
of Exit.
E_Exit Results Available
Organisation: National Customs Administration
Location: Customs Office of Export
AES receives the Exit Results.
E_Sufficient Alternative Evidence Available
Organisation: National Customs Administration
Location: Customs Office of Export
AES receives Sufficient Alternative Evidence.
Minor Events
E_Receive Certification of Exit on Alternative Evidence Notification
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at the Customs Office of Exit receives ‘Certification of Exit on Alternative Evidence Notification’ (IE588)
and records it in its systems.
E_Exit Results to PCO Received
Organisation: National Customs Administration
Location: Presentation Customs Office
AES at the PCO receives ‘Exit Results to PCO’ (IE592) and records it in its systems.
Processes
Customs Formalities at Office of Export -Handle Exit Results/Alternative
Evidence
Process: L4 -EXP-
01-23
Organisation: National Customs Administration
Location: Customs Office of Export, Customs Office of Exit, Presentation Customs Office
Constraint: N/A
Description:
The process L4-EXP-01-23-Customs Formalities at Office of Export-Handle Exit Results/Alternative Evidence
is triggered after one of the following events occur:
• Exit Results Available for Export Movement Followed by Transit after L4-EXP-01-25-Process
Transit Release Notification completion.
• Sufficient Alternative Evidence Available for an Export Movement Followed by Transit after L4-
EXP-01-25-Process Transit Release Notification completion.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 69 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
• The Customs Office of Export is the same office as the C ustoms Office of Exit and Exit
Notification is available after L4-EXP-01-07-Customs Formalities at Office(s) of Exit -Process
Exit completion.
• Exit Results Available after L4-EXP-01-25-Process Transit Release Notification completion or
L4-EXP-01-08-Enquiry Procedure completion or L4-EXP-01-07-Customs Formalities at
Office(s) of Exit-Process Exit completion.
• Sufficient Alternative Evidence Available after L4-EXP-01-08-Enquiry Procedure completion.
1. The process starts with one the following:
1.1. If Exit Results for an export movement followed by Transit are available, the process continues at
point 2.
1.2. If Sufficient Alternative Evidence for an export movement followed by Transit is available, the
process continues at point 2.
1.3. If the Customs Office of Export is the same office as the Customs Office of Exit and Exit Notification
is Available, the process continues at point 2.
1.4. If Exit Results Received, AES records the Exit Results, and the process continues at point 2.
1.5. If Sufficient Alternative Evidence is available, AES notifies the Customs Office of Exit of
Certification of Exit via a ‘Certification of Exit on Alternative Evidence Notification’ (IE588) and the
process continues at point 2.
2. AES handles the Timers at this point and the process continues with L4-EXP-01-23-01-Handle Timers call-
activity. It means that after exit results or exit notification were received or alternative evidence were
registered, the relevant timer(s) stop.
3. At this point, a parallel course of events takes place, and the following three cases are followed in parallel:
3.1. AES notifies the Declarant/Representative of the Export Notification , and the process continues at
point 4.
3.2. AES checks whether the movement concerns Centralised Clearance and if yes, the Customs Office of
Export (acting as Supervising Customs Office) notifies the Presentation Customs Office of the Exit
Results via an ‘Exit Results to PCO’ (IE592) message and the process continues at point 4.
3.3. AES checks whether the movement concerns Excise Goods and if yes, AES notifies MSA of Export
of the Exit Results via an ‘Exit Results to MSA of Export’ (IE598) message and the process continues
at point 4.
4. The process ends at this point and the outcome is ‘Export Formalities Completed’.
Final Situation:
• AES notifies the Declarant/Representative, Presentation Customs Office or MSA of Export whoever
is concerned and then the process ends, and the outcome is ‘Export Formalities Completed’.
Customs Office of Exit
1. The process is triggered when the Customs Office of Exit receives a Certification of Exit based on
alternative evidence via a ‘Certification of Exit on Alternative Evidence Notification’ (IE588) message.
2. AES records the Certification of Exit based on Alternative Evidence.
3. AES records the Exit based on Alternative Evidence and the process ends at this point and the outcome is
‘Exit Based on Alternative Evidence Recorded’.
Note: In case the Enquiry information code in message CC583C is equal to “Exited-No Alternative Evidence”,
the information regarding the Alternative Evidence may not be provided by the Declarant/Representative.
Nevertheless, the Customs Officer at the Customs Office of Export may manually provide this information.
This means that this information is transmitted to the Customs Office of Exit via the message ‘Certification of
Exit on Alternative Evidence Notification’ (IE588).
Final Situation:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 70 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
• AES records the Exit based on Alternative Evidence and the process ends at this point and the outcome
is ‘Exit Based on Alternative Evidence Recorded’.
Presentation Customs Office
1. The process is triggered when the Presentation Customs Office receives the ‘Exit Results to PCO’ (IE592).
2. AES records the Exit Results at the AES of the Presentation Customs Office. Then, based on the Exit
results, one of the following may occur:
2.1. In case of positive Exit Results where the Customs Office of Export (acting as Supervising Customs
Office) certifies the Exit, the movement state at the Presentation Customs Office changes to
‘Exported’.
2.2. In case of negative Exit Results where the Customs Office of Export (acting as Supervising Customs
Office) does not certify Exit, the movement state at the Presentation Customs Office changes to
‘Export Stopped, Discrepancies at Exit’.
Final Situation:
• AES records the Exit certification at the Presentation Customs Office and the movement state changes
to ‘Exported’.
• AES at the Presentation Customs Office records the decision that Exit is not certified , and the
movement state changes to ‘Export Stopped, Discrepancies at Exit’.
Handle Timers Process: L4 -EXP-
01-23-01
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
1. The process is triggered when the timers needs to be handled.
2. At this point, a parallel course of events takes place, and the following three cases are followed in parallel:
2.1. AES identifies if Timer to Certify Exit is still running and based on the outcome, two cases may occur:
2.1.1. If timer to Certify Exit is running, AES stops it, and the process continues at point 3.
2.1.2. If timer to Certify Exit is not running, the process continues at point 3.
2.2. AES identifies if Timer to Receive Exit Results is still running and based on the outcome, two cases
may occur:
2.2.1. If timer to Receive Exit Results is running, AES stops it, and the process continues at point 3.
2.2.2. If timer to Receive Exit Results is not running, the process continues at point 3.
2.3. AES identifies if Timer to Receive Alternative Evidence is still running and based on the outcome,
two cases may occur:
2.3.1. If timer to Receive Alternative Evidence is running, AES stops it , and the process continues at
point 3.
2.3.2. If timer to Receive Alternative Evidence is not running, the process continues at point 3.
3. The process ends at this point and the outcome is ‘Timer Handled’.
Final situation:
After all the running timers have been stopped, the p rocess ends at this point and the outcome is ‘Timers
Handled’.
Major Results
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 71 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
R_Export Formalities Completed
Organisation: National Customs Administration
Location: Customs Office of Export
Export Formalities Completed.
R_Exit Based on Alternative Evidence Recorded
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at Customs Office of Exit records the Exit Results and the process ends at this point.
R_Exported
Organisation: National Customs Administration
Location: Presentation Customs Office
AES at Presentation Customs Office records the Exit Results that certify Exit, and the process ends at this point
with movement state changing to ‘Exported’.
R_Export Stopped, Discrepancies at Exit
Organisation: National Customs Administration
Location: Presentation Customs Office
AES at Presentation Customs Office records the Exit Results that do not certify Exit , and the process ends at
this point with movement state changing to ‘Export Stopped, Discrepancies at Exit’.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 72 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.16 L4-EXP-01-24-CUSTOMS FORMALITIES AT OFFICE (S)
OF EXIT-PROCESS ARRIVAL NOTIFICATION
Figure 22: L4-EXP-01-24-Customs Formalities at Office(s) of Exit-Process Arrival Notification
Major Events
E_Customs Officer registers the arrival of the goods at exit
Organisation: National Customs Administration
Location: Customs Office of Exit
Customs Officer at Customs Office of Exit registers the arrival of the goods .
E_Trader registers the arrival of the goods at exit
Organisation: Trader at Exit
Location: Premises of the Trader or Customs Office of Exit
Trader registers the arrival of the goods.
Processes
Process Arrival Notification Process: L4 -EXP-
01-24
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process has the following start events at the Customs Office of Exit:
• Arrival at Exit Registered by a Customs Officer.
• Receive Arrival at Exit Notification.
In case the process starts by receiving an ‘Arrival at Exit’ (IE507):
1. AES validates the received IE against the business rules and conditions and one of the following cases is
fulfilled:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 73 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
1.1. The ‘Arrival at Exit’ notification is invalid, and AES rejects the notification and informs the Trader
at Exit, indicating the reasons for the rejection with a ‘Rejection from Office of Exit’ (IE557). The
process ends at this point and the movement state at the Customs Office of Exit remains as -is.
1.2 The ‘Arrival at Exit’ notification is valid. Next, AES identifies if the Timer to Receive Arrival at
Exit is still running.
1.2.1. If the Timer to Receive Arrival at Exit is still running, then AES stops the timer , and
the process flow continues from point 2.
1.2.2. If the Timer to Receive Arrival at Exit has already stopped , then the process continues
from point 2.
2. Then AES checks if the AER for the MRN is already available in the system or not.
2.1. If the AER is available AES records the arrival at exit notification received from the trader in an
electronic format or registered by the Customs Officer at the Customs Office of Exit. The movement
state is changed to 'Goods Presented at Exit' and the process ends.
2.2. If the AER is not available, then the process ends at this point.
In case the goods physically arrive at the Customs Office of Exit they will be registered by the competent
Customs Officer. The process flow continues from point 1.2.
Final situation:
• The goods have been successfully presented at the Customs Office of Exit. The movement state is
changed to 'Goods Presented at Exit'.
• The 'Arrival at Exit Notification' (IE507) was rejected. The process ends with 'Arrival at Exit
Notification Rejected' and the movement state remains as is.
• The goods have been successfully presented but the process ends with 'AER not available' at Office of
Exit. Process continues under L4-EXP-01-19-Handle Diversion.
Major Results
R_Goods presented at Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
The goods have successfully presented at the Customs Office of Exit
R_Arrival at Exit Notification Rejected
Organisation: National Customs Administration
Location: Customs Office of Exit
AES rejects an invalid exit notification that received by the Customs Office of Exit .
Minor Results
R_AER not available
Organisation: National Customs Administration
Location: Customs Office of Exit
AER is not available at the Customs Office of Exit.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 74 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.17 L4-EXP-01-25-PROCESS TRANSIT RELEASE
NOTIFICATION
Figure 23: L4-EXP-01-25-Process Transit Release Notification (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 75 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 24: L4-EXP-01-25-Process Transit Release Notification (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 76 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 25: L4-EXP-01-25-Process Transit Release Notification (Part C)
Major Events
E_Receive Transit Presentation Notification at Customs Office of Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
AES receives the ‘Transit Presentation Notification’ (IE190).
Minor Events
E_Exit Results Received at Customs Office of Export
Organisation: National Customs Administration
Location: Customs Office of Export
AES receives the ‘Exit Results’ (IE518).
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 77 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Processes
Process Transit Release Notification Process: L4 -EXP-
01-25
Organisation: National Customs Administration
Location: Customs Office of Exit, Customs Office of Export
Constraint: N/A
Description:
When the ‘Transit Presentation Notification’ (IE190) (‘Receive Transit Presentation Notification ’) is
communicated from the Customs Office of Departure to the Customs Office of Exit, the L4-EXP-01-25-Process
Transit Release Notification will be initiated.
4. AES at the Customs Office of Exit receives the ‘Transit Presentation Notification’ (IE190) from the
Customs Office of Departure and records it in its system.
5. Next, upon its reception, the Customs Office of Exit shall verify (cross -check) that the referenced Export
MRN(s) exist and are in the appropriate movement state ( i.e. ‘AER Created’, ‘Goods Presented at Exit ’,
‘Goods Ready to be Released’). For this reason, the process L4-EXP-01-25-01-Cross-Check of the Export
MRN(s) is initiated. The cross -check result may be positive (i.e. the ‘Cross -check is successful for all the
Export MRN(s)’) or negative (i.e. the ‘Cross-check was not successful for all the Export MRN(s)’ or ‘AER
Responses received were not all positive’ for unknown Export MRN(s)).
6. Depending on the verification (cross-check) performed, one of the following cases might occur:
6.1. The Customs Office of Exit replies positively with a positive ‘Transit Presentation Notification
Response’ (IE191). The process continues from point 4.
6.2. The Customs Office of Exit replies negatively with a negative ‘Transit Presentation Notification
Response’ (IE191). The process ends with ‘Transit Presentation Notification Response was Negative’
and this is the final step. Customs Office of Exit waits for another ‘ Transit Presentation Notification’
(IE190) or ‘Arrival at Exit’ (IE507), so as the L4-EXP-01-25-Process Transit Release Notification or
L4-EXP-01-24-Customs Formalities at Office(s) of Exit -Process Arrival Notification to be initiated,
respectively.
7. The Customs Office of Exit receives a new ‘Transit Presentation Notification’ (IE190) from the Customs
Office of Departure as allocation request of the transit MRN to the Export MRN(s) since the transit
declaration has now been accepted and records it in its system. The movement state is set to ‘Goods
Presented at Transit’ at the Customs Office of Exit.
8. AES at the Office of Exit allocates the Transit MRN for the specific Export MRN(s).
9. The Customs Office of Exit replies positively to the Customs Office of Departure by sending a positive
‘Transit Presentation Notification Response’ (IE191).
10. Then, one of the following cases might be fulfilled:
10.1. The Customs Office of Exit receives Destination Control Results for each referenced export MRN(s)
in the transit declaration via the ‘Destination Control Results to AES’ (IE042) from the Customs
Office of Departure, records it in its system and identifies whether the Destination Controls Results
code indicating release for transit or not.
10.1.1. At any case, the AES at the Customs Office of Exit will generate and send to the AES at the
Customs Office of Export, an instance of the ‘Exit Results’ (IE518) for each referenced Export
MRN in the ‘Destination Control Results to AES’ (IE042) and the process at the Customs Office
of Exit ends with ‘Exit Results Received’, which is final for the Customs Office of Exit. Process
continues with point 7.1.2.
10.1.2. The ‘Exit Results’ (IE518) are received from the Customs Office of Exit, which is considered
as the start event for the Customs Office of Export. AES at the Customs Office of Export records
the Exit Results in its system and identifies whether the Exit Control Result code concerns
unsatisfactory Control Results or satisfactory Control Results. Then, one of the following might
occur:
10.1.2.1. If the Exit Control Result code concerns unsatisfactory Control Results ( ‘B2’ or
‘B3’), the movement state at the Customs Office of Export turns to ‘Under Exit
Confirmation Request ’, the Timer to Receive Exit Results is stopped , and the Customs
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 78 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Office of Export will initiate the request for Alternative Evidence in the L4-EXP-01-27-
Handle Goods Movement Additional Information. The process ends with either ‘Enquiry
Information code was 'Will not Exit' ‘ or ‘Time Limit To Receive Alternative Evidence
expired’, which lead to initiation of L4-EXP-01-26-Export Declaration Invalidatio n, or
‘Sufficient Alternative Evidence Available for an Export Movement Followed by Transit’
which leads to initiation of L4-EXP-01-23-Customs Formalities at Office of Export -
Handle Exit Results/Alternative Evidence.
10.1.2.2. If the Exit Control Result code does not concern 'B2' or 'B3' Control Results (could
be either 'A1', 'A4' or 'B1'), then the process ends with ‘Exit Results Available for an
Export Movement Followed by Transit ’. Process L4-EXP-01-23-Customs Formalities at
Office of Export-Handle Exit Results/Alternative Evidence shall follow.
10.2. The Customs Office of Exit receives ‘Recovery Communication to AES’ (IE048) from the Customs
Office of Departure and records it in its system. Then, sends the Exit Results to the Customs Office
of Export with Exit Control Result Code 'B1' and the process continues from point 7.1.2.
10.3. The Customs Office of Exit receives the ‘Transit Presentation Notification’ (IE190) from the Customs
Office of Departure (Transit Indicator Flag is set to ‘Amendment of Export MRNs referenced in
Transit Declaration’) containing Export MRNs that exist into the Previous Documents of the amended
transit declaration. AES at the Customs Office of Exit records it in its system.
10.3.1. Upon its reception, the Customs Office of Exit shall verify (cross -check) that the referenced
Export MRN(s) exist, thus, the process L4-EXP-01-25-01-Cross-Check of the Export MRN(s)
is initiated. Depending on the verification (cross -check) performed, one of the following cases
might occur:
10.3.1.1. The Customs Office of Exit replies positively with a positive ‘Transit Presentation
Notification Response’ (IE191).
10.3.1.1.1. AES at the Customs Office of Exit performs the appropriate de-
association for the amended Export MRN(s) and any new association of Export
MRN(s), if required. Process loops back to point 7, normally expecting for the
‘Destination Control Results’ (IE042).
10.3.1.2. The Customs Office of Exit replies negatively with a negative ‘Transit Presentation
Notification Response’ (IE191). The process loops back to point 7, expecting for the next
valid ‘Transit Presentation Notification’ (IE190) for amendment.
10.4. The Customs Office of Exit receives a ‘Transit Invalidation Notification’ (IE040) and AES at the
Customs Office of Exit records it in its system.
10.4.1. AES at the Customs Office of Exit performs the appropriate de-association for the invalidated
Export MRN(s), and the process ends with ‘Transit Declaration was Invalidated’ and this is the
final step. For the invalidated export MRNs, the transition to their previous state before the
transition to ‘Goods Presented at Transit ’ is performed. That way, the Export MRNs become
available for another procedure. Customs Office of Exit waits for another ‘ Transit Presentation
Notification’ (IE190) or ‘Arrival at Exit’ (IE507), so as the L4-EXP-01-25-Process Transit
Release Notification or L4-EXP-01-24-Customs Formalities at Office(s) of Exit-Process Arrival
Notification to be initiated, respectively.
Note: Regardless of the value of the Control Result Code in IE042, message IE518 will contain the Control
Result Code and the specific Export MRN, along with the Transit MRN. In case the Control Result Code in
IE042 is 'A4', 'B2' or 'B3' (i.e. minor discre pancies at Destination, non -appropriate Office of Destination or
unsatisfactory control results) and the Customs Office of Exit has access to/is aware of the related Export MRN
discrepancies provided to the Customs Office of Departure by the Customs Office of Destination, then the
Customs Office of Exit may report those discrepancies in IE518.
Final Situation:
• At the Customs Office of Exit, d ue to negative cross -check (before acceptance of the transit
declaration), the process ends with ‘Transit Presentation Notification Response was Negative’.
• At the Customs Office of Exit, due to invalidation of the transit declaration (after the acceptance of the
transit declaration), the process ends with ‘Transit Declaration was Invalidated’.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 79 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
• At the Customs Office of Exit, in case of Destination Control results received from the Customs Office
of Departure, the ‘Exit results sent’ to the Customs Office of Export and the process ends .
• At the Customs Office of Export, upon reception of the Exit Results with code ‘A1’, ‘A4’ or ‘B1’ from
the Customs Office of Exit , the process ends with ‘Exit Results available for an Export Movement
Followed by Transit’.
• At the Customs Office of Export, upon reception of the unsatisfactory Exit Results (‘B2’ or ‘B3’) from
the Customs Office of Exit and request for Alternative Evidence from the Declarant/Representative,
the process ends with ‘Enquiry Information code was 'Will not Exit'‘.
• At the Customs Office of Export, upon reception of the unsatisfactory Exit Results (‘B2’ or ‘B3’) from
the Customs Office of Exit and request for Alternative Evidence from the Declarant/Representative,
the process ends with ‘Sufficient Alternative Evidence Available for an Export Movement Followed
by Transit’.
• At the Customs Office of Export, upon reception of the unsatisfactory Exit Results (‘B2’ or ‘B3’) from
the Customs Office of Exit and request for Alternative Evidence from the Declarant/Representative,
the process ends with ‘Time Limit To Receive Alternative Evidence expired’.
Cross-Check of the Export MRN(s) Process: L4 -EXP-
01-25-01
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process can be initiated when at least one Export MRN is referenced into the previous documents (document
type code N830) data group of the transit declaration and then the following condition is identified by AES at
the Customs Office of Exit:
• Transit Presentation Notification Recorded.
When the above condition is met, the flow continues as per the below:
AES at the Customs Office of Exit identifies whether all Export MRN(s) mentioned in the Transit Presentation
Notification are known and the declaration data are available. At this point, the following may occur:
1. Some of the Export MRN(s) are unknown to the Customs Office of Exit and thus the process ‘L4-EXP-01-
19-Handle Diversion’ is initiated. At this point, the following may occur:
1.1. The AER Responses received were not all positive. The process ends at this point. The initial process
that called this one can now resume.
1.2. The AER Responses received were all positive. AES at the Customs Office of Exit performs the
Cross-Check of the Export MRN(s). At this point, the following may occur:
1.2.1. The Cross-Check of all the Export MRN(s) was successful. The flow ends here. The process that
call this one may now resume.
1.2.2. The Cross -Check for at least one Export MRN was unsuccessful. The flow ends here. The
process that call this one may now resume.
2. All the Export MRN(s) are known to the Customs Office of Exit and the Declaration data are available.
The flow continues from point 1.1.2. at the point of performing the Cross-Check of the Export MRN(s).
Final situation:
• AER Responses received were not all positive.
• Cross-Check was not successful for all Export MRN(s).
• Cross-Check was successful for all Export MRN(s).
Major Results
R_ Exit results sent
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 80 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Organisation: National Customs Administration
Location: Customs Office of Exit
In case of Destination Control results received from the Customs Office of Departure, the ‘Exit results sent’ to
the Customs Office of Export and the process ends.
R_ Exit results Available for Export Movement Followed by Transit
Organisation: National Customs Administration
Location: Customs Office of Export
Upon reception of the Exit Results with Control Result Codes either ‘A1’, ‘A4’, ‘B1’ from the Customs Office
of Exit, the process ends with ‘Exit Results available’.
Minor Results
R_Transit Presentation Notification Response was Negative
Organisation: National Customs Administration
Location: Customs Office of Exit
Due to negative cross -check (before acceptance of the transit declaration), the process ends with ‘Transit
Presentation Notification Response was Negative’.
R_Transit Declaration was Invalidated
Organisation: National Customs Administration
Location: Customs Office of Exit
Due to invalidation of the transit declaration (after the acceptance of the transit declaration), t he process ends
with ‘Transit Declaration was Invalidated’.
R_Enquiry Information code was 'Will not Exit’
Organisation: National Customs Administration
Location: Customs Office of Export
Upon reception of the unsatisfactory Exit Results from the Customs Office of Exit and request for Alternative
Evidence from the Declarant/Representative, the process ends with ‘Enquiry Information code was 'Will not
Exit'‘.
R_Sufficient Alternative Evidence Available for an Export Movement Followed by Transit
Organisation: National Customs Administration
Location: Customs Office of Export
Upon reception of the unsatisfactory Exit Results from the Customs Office of Exit and request for Alternative
Evidence from the Declarant/Representative, the process ends with ‘Sufficient Alternative Evidence Available
for an Export Movement Followed by Transit’.
R_Time Limit To Receive Alternative Evidence expired
Organisation: National Customs Administration
Location: Customs Office of Export
Upon reception of the unsatisfactory Exit Results from the Customs Office of Exit and request for Alternative
Evidence from the Declarant/Representative, the process ends with ‘Time Limit To Receive Alternative
Evidence expired’.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 81 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.18 L4-EXP-01-26-EXPORT DECLARATION
INVALIDATION
Figure 26: L4-EXP-01-26-Export Declaration Invalidation (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 82 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 27: L4-EXP-01-26-Export Declaration Invalidation (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 83 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 28: L4-EXP-01-26-Export Declaration Invalidation (Part C)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 84 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Receive Invalidation Request
Organisation: National Customs Administration
Location: Customs Office of Export
AES at the Customs Office of Export receives an Export Declaration Invalidation request via an ‘Export
Invalidation Request’ (IE514) message.
E_Time Limit to Certify Exit Expired
Organisation: National Customs Administration
Location: Customs Office of Export
Time Limit to Certify Exit expires at the Customs Office of Export.
E_Time Limit to Receive Alternative Evidence Expired
Organisation: National Customs Administration
Location: Customs Office of Export
Time Limit to Receive Alternative Evidence expires at the Customs Office of Export.
E_Customs Officer Initiates the Invalidation of Export Declaration
Organisation: National Customs Administration
Location: Customs Office of Export
Customs Officer decides to initiate the Invalidation process.
E_Receive Export Invalidation Notification
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at the Customs Office of Exit receives an Export Invalidation Notification via an ‘Export Invalidation
Notification’ (IE510) message.
E_Export Invalidation Notification Received
Organisation: National Customs Administration
Location: Presentation Customs Office - PCO
An Export Invalidation Notification has been received at PCO.
Processes
Export Declaration Invalidation Process: L4 -EXP-
01-26
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
Customs Office of Export
The process starts with one of the following events:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 85 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
• Customs Office of Export receives an Invalidation request from the Declarant/Representative .
• Customs Officer decides to Initiate the Invalidation process for a movement.
• Time limit to Certify Exit expires OR Time limit to Receive Alternative Evidence expires .
1. The Customs Office of Export receives an Invalidation Request via an ‘Export Invalidation Request’
(IE514) from the Declarant/Representative. Then, AES validates the Export Invalidation Request and based
on the outcome of the validation, two cases may occur:
1.1. Export Declaration Invalidation Request is valid , AES records the Invalidation Request , and the
process continues at point 4.
1.2. Export Declaration Invalidation Request is invalid, AES notifies the Declarant/Representative of the
invalid Invalidation Request via a ‘Rejection from Office of Export’ (IE556) and the process ends at
this point with outcome ‘Export Declaration Invalidation Request Rejected’.
2. The Customs Officer decides to initiate the Invalidation process and registers his/her decision. The process
continues at point 4.
3. Time limit to Certify Exit or Time limit to Receive Alternative Evidence expires and then AES records the
expiry of the timer. The Customs Officer acknowledges the expiry of the timer and registers the decision
to initiate the Invalidation process, and the process continues at point 4.
4. AES identifies if the Goods are Release for Export and based on the outcome, two cases may occur:
4.1. Goods Released for Export. The Customs Officer determines if the Operation Status Check needs to
be performed and based on the outcome, two cases may occur:
4.1.1. Customs Officer decides to perform Operation Status Check, and the process continues with L4-
EXP-01-17-Operation Status Check call -activity. AES identifies the outcome of Operation
Status Check call -activity, and t he Customs Officer determines whether to proce ed with the
Export Declaration Invalidation or not and based on the decision, two cases may occur:
4.1.1.1. Decision to proceed with Export Declaration Invalidation. The Customs Officer registers
the decision to proceed with Export Declaration invalidation and AES records it. T he
process continues at point 4.2.
4.1.1.2. Decision not to proceed with Export Declaration Invalidation and the process continues at
point 4.1.2.3.1.
4.1.2. Customs Officer decides not to perform Operation Status Check , and the process continues at
point 4.2.
4.1.3. AES identifies if the Customs Office of Export is also the Customs Office of Exit and based on
the outcome, two cases may occur:
4.1.3.1. Customs Office of Export is also the Customs Office of Exit, and the process continues at
point 4.1.2.3.1.
4.1.3.2. Customs Office of Export is not also the Customs Office of Exit . Then AES notifies
Customs Office of Exit of the Invalidation Request via an ‘Export Invalidation
Notification’ (IE510) message. AES receive s the Invalidation Acknowledgement
Response from the Customs Office of Exit via ‘Invalidation Acknowledgement’ (IE591)
message and then identifies whether the Invalidation Acknowledgement Response is
Positive or Negative. Based on the outcome, two cases may occur:
4.1.3.2.1. Invalidation Acknowledgement Response is Positive. AES Invalidates the Export
Declaration and the timers are handled at this point which means that after the Export
Declaration Invalidation, the relevant timer(s) stop , the process continues with L4 -
EXP-01-23-01 Handle Timer call -activity. It means that after exit results or exit
notification were received or alternative evidence were registered, the relevant
timer(s) stop. AES identifies if the Export Declaration concerns Centralised
Clearance and based on the outcome, two cases may occur:
4.1.3.2.1.1. Export Declaration concerns Centralised Clearance . AES notifies the
Presentation Customs Office of Invalidation via an ‘Export Invalidation
Notification’ (IE510) message sent from the Customs Office of Export
(acting as Supervising Customs Office) and the process continues at point 6.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 86 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
4.1.3.2.1.2. Export Declaration doesn’t concern Centralised Clearance , and the process
continues at point 6.
4.1.3.2.2. Invalidation Acknowledgement Response is negative. AES identifies if Invalidation
Request has been lodged by the Trader and based on the outcome, two cases may
occur:
4.1.3.2.2.1. Invalidation requested by the Trader . AES notifies the
Declarant/Representative via an ‘Rejection from Office of Export’ (IE556)
message and the process ends at this point and the outcome is ‘Export
Declaration Invalidation Request Rejected’.
4.1.3.2.2.2. Invalidation was not requested by the Trader and the process ends at this point
and the outcome is ‘Export Declaration Invalidation Request Rejected’.
5. Goods are not released for Export . AES invalidates the Export Declaration , and the process continues at
point 6.
6. AES Identifies in the Export Declaration concerns Excise Goods and based on the outcome, two cases may
occur:
6.1. Export Declaration concerns Excise Goods and AES notifies the MSA of Export . The process
continues at point 7.
6.2. Export Declaration does not concern Excise Goods, and the process continues at point 7.
7. AES notifies the Declarant/Representative of the Invalidation of the Export Declaration via an ‘Export
Invalidation Decision’ (IE509) message. The movement state is changed to ‘Invalidated’ and the process
ends at this point.
Final Situation:
• AES notifies the Declarant/Representative of the Export Declaration Invalidation , and the movement
state is changed to ‘Invalidated’.
Customs Office of Exit
1. The process is triggered when the Customs Office of Exit receives an Export Invalidation Notification via
an ‘Export Invalidation Notification’ (IE510) message.
2. AES identifies is invalidation can be performed.
3. AES send back to the Customs Office of Export a Positive or a Negative Invalidation Acknowledgment
Response via an ‘Invalidation Acknowledgement ’ ( IE591) message. In case of positive Invalidation
Acknowledgement, the movement state changes to “Invalidated”.
4. The process ends at this point with outcome ‘Invalidation Acknowledgement has been communicated’.
Presentation Customs Office – PCO
1. The process is triggered when the Presentation Customs Office (PCO) receives an ‘Export Invalidation
Notification’ message (IE510).
2. AES at the PCO records the Export Invalidation Notification and the movement state is set to ‘Invalidated’,
which is a final state. The process ends at this point.
Final Situation:
• After sending the ‘Invalidation Acknowledgement ’ (IE591) to the Customs Office of Export, the
process ends at this point with outcome ‘Invalidation Acknowledgement has been communicated’.
• After AES records the Export Invalidation Notification at the PCO, the process ends, and the movement
state is set to ‘Invalidated’ at the PCO.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 87 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Results
R_Export Declaration Invalidated
Organisation: National Customs Administration
Location: Customs Office of Export
The Export Declaration is invalidated. This is a final state.
Minor Results
R_Export Declaration Invalidation Request Rejected
Organisation: National Customs Administration
Location: Customs Office of Export
The Export Declaration Invalidation Request was invalid and thus was rejected.
R_Export Declaration Invalidation Request Rejected
Organisation: National Customs Administration
Location: Customs Office of Export
The Invalidation Acknowledgement Response from Customs Office of Exit was negative and this the Export
Declaration Invalidation Request was rejected.
R_Invalidation Acknowledgement has been communicated
Organisation: National Customs Administration
Location: Customs Office of Exit
The Invalidation Acknowledgement Response has been sent from Customs Office of Exit to the requesting
Customs Office of Export.
R_Invalidated
Organisation: National Customs Administration
Location: Presentation Customs Office - PCO
The movement state at PCO is set to 'Invalidated', which is a final state.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 88 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.19 L4-EXP-01-27-HANDLE GOODS MOVEMENT
ADDITIONAL INFORMATION
Figure 29: L4-EXP-01-27-Handle Goods Movement Additional Information (Part A)
Figure 30: L4-EXP-01-27-Handle Goods Movement Additional Information (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 89 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Enquiry Procedure was initiated by the Customs Officer and Exit Results have not been received (The
movement is in state other than ’Exited'', ‘Goods Not Allowed to Exit’)
Organisation: National Customs Administration
Location: Customs Office of Export
Enquiry Procedure was initiated by the Customs Officer after the expiration of the time limit to Receive Exit
results and the movement is in state other than 'Exited', 'Goods not Allowed to Exit'.
E_Control Result Code in the Exit Results of an Export Movement followed by Transit is either 'B2' or
'B3'
Organisation: National Customs Administration
Location: Customs Office of Export
The control result code in the exit results is 'B2' or 'B3' in the case of an export movement that will be followed
by transit.
Handle Goods Movement Additional Information Process: L4 -EXP-
01-27
Organisation: National Customs Administration
Location: Customs Office of Export
Constraint: N/A
Description:
The process of Handling Goods Movement Additional Information can be initiated with two possible start
events as listed below:
• Enquiry Procedure was initiated by the Customs Officer and Exit Results have not been received (The
movement is in state other than ‘Exited’, ‘Goods not Allowed to Exit’).
• Control Result Code in the Exit Results is either ‘B2’ or ‘B3’.
When AES at the Customs Office of Export identifies one of the above, the following occurs:
AES at the Customs Office of Export notifies the Declarant/ Representative requesting information about the
movement of the goods via a ‘Request on Non -Exited Export’ (IE582) message. At this point, the Time Limit
to Receive Alternative Evidence (60 days - extendable) is initiated. Following this, the Customs Officer registers
the decision to extend the Time Limit to Receive Alternative Evidence. The two following cases may occur:
1. The Customs Officer decides to Extend the Time Limit to Receive Alternative Evidence and the process
‘L4-EXP-01-08-05-Extend Time Limit To Receive Alternative Evidence’ is initiated. Upon the execution
of this process, the flow continues and merges with th e flow of point 2, after the decision of the Customs
Officer to not extend the Time Limit to Receive Alternative Evidence.
2. The Customs Officer does not extend the Time Limit to Receive Alternative Evidence. The following cases
may occur at this point:
2.1. AES at the Customs Office of Export receives an ‘Information on Non -Exited Export’ (IE583)
message from the Declarant/Representative. AES validates the received message and then records
it. At this point, the following may occur:
2.1.1. The validation of ‘Information on Non-Exited Export’ (IE583) was successful. AES
records the ‘Information on Non-Exited Export’ (IE583) message and subsequently
identifies the Enquiry Information Code declared by the Trader. Based on the
Enquiry Information Code declared in ‘Information on Non-Exited Export’ (IE583),
the following cases may occur:
2.1.1.1. The Enquiry Information Code in ‘Information on Non -Exited Export’
(IE583) message is ‘Will not Exit’. The flow stops here. The initial process
that called this process may resume.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 90 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
2.1.1.2. The Enquiry Information Code in ‘Information on Non -Exited Export’
(IE583) message is ‘Expected to Exit’. The flow continues from point
2.1.2.1.
2.1.1.3. The Enquiry Information Code is ‘Exited -Alternative Evidence’. The
Customs Officer registers the decision on Alternative Evidence. AES at the
Customs Office of Export records the decision on Alternative Evidence. At
this point the following cases may occur:
2.1.1.3.1. The provided Alternative Evidence is considered sufficient in
order to certify the exit of the goods. AES at the Customs
Office of Export stops the time limit to Receive Alternative
Evidence and the flow stops here. The initial process that
called this process may resume.
2.1.1.3.2. The provided Alternative Evidence is considered insufficient
in order to certify the exit of the goods. The flow continues
from point 2.1.2.
2.1.2. The validation of ‘Information on Non -Exited Export’ (IE583) was not successful.
AES notifies the Trader via a ‘Rejection from Office of Export’ (IE556) message.
2.1.2.1. At this point, AES checks whether the Exit Results are available at the
Customs Office of Export (this check is not applicable for the case of an
Export movement followed by Transit) in which the Control Results Code
in the Exit Results is either ‘B2’ or ‘B3’ and the Time Limit to Receive Exit
Results was stopped). The following may occur:
2.1.2.1.1. The Exit Results are available to the Customs Office of
Export. The process ends here. The initial process that called
this process may now resume.
2.1.2.1.2. The Exit Results are not available to the Customs Office of
Export. The flow continues from the beginning of the process.
Specifically, from the point after the Time Limit to Receive
Alternative Evidence is initiated.
2.2. The time Limit to Receive Alternative Evidence Expires. AES at the Customs Office of Export
records this time limit expiry and the process stops here. The initial process that called this process
can now resume from that point.
Final situation:
The possible final situations for this process are the following:
• Time Limit to Receive Alternative Evidence expired.
• Exit Results Received.
• Enquiry Information Code ‘Will not Exit’.
• Sufficient Alternative Evidence Available.
Major Results
R_Enquiry Information code was 'Will not Exit'
Organisation: National Customs Administration
Location: Customs Office of Export
The Declarant/Representative informed the Customs Office of Export that the goods will not exit the Customs
Territory of the Union.
R_Exit Results Received
Organisation: National Customs Administration
Location: Customs Office of Export
AES at the Customs Office of Export has received the Exit Results from the Customs Office of Exit.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 91 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
R_Sufficient Alternative Evidence Available
Organisation: National Customs Administration
Location: Customs Office of Export
The provided alternative evidence is considered sufficient in order to confirm the exit of the goods.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 92 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
3. AES – EXIT SUMMARY DECLARATION
3.1 INTRODUCTION
This section presents the various business process threads related to the Exit Summary Declaration which is used
when goods are to be taken out of the customs territory of the Union and a customs declaration , or a re -export
declaration is not lodged as pre -departure declaration. ( In case goods leaving the customs territory of the Union
are not assigned to a customs approved treatment or use for which a cu stoms declaration is required (t he latter
being dealt with in section 2).)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 93 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
3.2 L4-EXP-01-10-EXIT SUMMARY DECLARATION -
PROCESS REGISTRATION AND ARRIVAL
Figure 31: L4-EXP-01-10-Exit Summary Declaration-Process Registration and Arrival (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 94 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 32: L4-EXP-01-10-Exit Summary Declaration-Process Registration and Arrival (Part B)
Major Events
E_Exit Summary Declaration Received
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at Customs Office of Exit receives the Exit Summary Declaration from the Person lodging the EXS in an
electronic format.
E_Exit Summary Declaration Received
Organisation: National Customs Administration
Location: Office of Lodgement
AES at Customs Office of Lodgement receives the Exit Summary Declaration from the Person lodging the EXS
in an electronic format.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 95 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
E_EXS Received
Organisation: National Customs Administration
Location: Customs Office of Exit
AES receives the Exit Summary Declaration from Customs Office of Lodgement.
Processes
Exit Summary Declaration-Process Registration and Arrival Process: L4-EXP-
01-10
Organisation: National Customs Administration
Location: Customs Office of Exit, Customs Office of Lodgement
Constraint: N/A
Description:
This BPM depicts the process that occurs when goods that will leave the territory are not bound by the export
formalities of L4-EXP-01-01.
1. At the Customs Office of Lodgement the process concerning an exit summary declaration has one start event:
• Receive ‘Exit Summary Declaration’ (IE615)
1.1. AES registers the ‘Exit Summary Declaration’ (IE615), and the process continues with L4 -EXP-01-
10-07-Register Exit Summary Declaration.
1.1.1. If the Exit Summary Declaration is invalid, AES notifies the Declarant/Representative via
‘Rejection from Office of Exit’ (IE557) and the process stops at this point.
1.1.2. If the Exit Summary Declaration is valid then the state is changed to ‘Registered’ and AES
communicates the ‘EXS’ (IE601) to the Customs Office of Exit. The process continues and AES
starts the time limit for Assumed Exited. At this point one of the following cases is fulfilled:
1.1.2.1. The time limit for Assumed Exited expires. AES records the time limit expiration, and the
movement state is set to ‘Assumed Exited’.
1.1.2.2. The Customs Office of Lodgement receives the ‘Declaration Request Export ’ (IE502)
from the Customs Office of Exit requesting the Export Declaration Data in case of
diversion. AES records the request for Exit Summary Declaration Data and identifies if it
is available at the Customs Office of Lodgement. AES responds to the Customs Office of
Exit with the ‘Exit Summary Declaration Response’ (IE603) which can be either positive
or negative. At this point one of the following cases may occur:
1.1.2.2.1. If the ‘Exit Summary Declaration Response ’ (IE603) is negative, the Timer for
Assumed Exited at the Customs Office of Lodgement continues.
1.1.2.2.2. If the ‘Exit Summary Declaration Response ’ (IE603) is positive, the Timer for
Assumed Exited stops and the state is changed to ‘Arrived Elsewhere ’ at the
Customs Office of Lodgement.
At this point the process at the Customs Office of Lodgement ends.
2. At the Customs Office of Exit, the process concerning an exit summary declaration has two start events:
• Receive ‘Exit Summary Declaration’ (IE615)
• Receive ‘EXS’ (IE601)
Two cases may occur:
2.1. If the ‘Exit Summary Declaration’ (IE615) is received, AES registers the ‘Exit Summary Declaration’
(IE615) and the process L4-EXP-01-10-07-Register Exit Summary Declaration is executed. The state
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 96 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
is changed to ‘Registered’ and the process continues from point 2.3 .
In case the Exit Summary Declaration is invalid, the process stops at this point.
2.2. If the ‘EXS’ (IE601) is received, AES records the EXS, and the process continues from point 2.3.
2.3. The Timer to Receive Exit Notification starts at this point. The process continues and two cases may
occur based on whether the Exit Summary Declaration was lodged at another Customs Office:
2.3.1. If it wasn’t lodged at another Customs Office, the process continues from point 2.4.
2.3.2. If it was lodged at another Customs Office, one of the following cases is fulfilled:
2.3.2.1. If the ‘Arrival at Exit’ (IE507) notification was received from the Trader at Exit or if the
‘Arrival at Exit’ (IE507) notification was registered by a Customs Officer, AES processes
the Arrival at Exit Notification. The process is the same for both cases and continues with
L4-EXP-01-10-03-Process Arrival Notification -Exit Summary Declaration. The process
may result in one of the following three outcomes:
2.3.2.1.1. If Goods Presented at Exit, the process continues from point 2.4.
2.3.2.1.2. If Arrival at Exit Notification Rejected, then the Timer to Receive Arrival at Exit
Notification will remain active, and the process will continue from point 2.3.2 until
a valid Arrival at Exit Notification is received or until the Timer expires.
2.3.2.1.3. If EXS is not available, then AES will request the Exit Summary Declaration Data
via a ‘Declaration Request Export’ (IE502) from the Customs Office of Lodgement
and after receiving the ‘Exit Summary Declaration Data Response ’ (IE603) , it
handles the response, and the process will continue with L4-EXP-01-10-04-Handle
Declaration Request Response – Exit Summary Declaration. The process continues
and may result in one of the following outcomes:
2.3.2.1.3.1. If the outcome is a Positive response, then the Goods are presented at Exit
and the process continues from point 2.4.
2.3.2.1.3.2. If the outcome is a Negative response, the state is change to ‘Diversion
Rejected’ and the process stops at this point.
2.3.2.2. If the 150-day time limit to Receive Arrival at Exit Notification expires, AES Records the
Expiry of the time limit to Receive Arrival at Exit Notification.
The invalidation process is initiated and the process L4 -EXP-01-03-05-Invalidate Export
Declaration is executed.
2.4. The process L4 -EXP-01-01-01-02-Request and Record Risk Analysis is executed. The process
continues with L4-EXP-01-10-02-Register and Record Control Decision-Exit Summary Declaration.
AES then identifies whether the goods should be controlled or not. Two cases may occur:
2.4.1. Decision not to control the goods so the state is changed to ‘Goods Ready to be Released’, AES
notifies that Trader at Exit regarding the release of the goods via an ‘Exit Release Notification’
(IE525). The outcome of the process is ‘Goods Released for Exit’ and the process ends here (the
state at the Customs Office of Exit is changed either to ‘Goods Released for Immediate Leave’
in case of no storing, or to ‘Goods Held for Storing’ in case of storing of goods.).
2.4.2. Decision to control the goods, the state is changed to ‘Under Control’ and the process continues
with L4-EXP-01-10-05-Register Control Results-Exit Summary Declaration.
AES then checks if the control results were satisfactory, and two cases may occur:
2.4.2.1. Control Results were satisfactory , and the goods are released for Exit, AES notifies that
Trader at Exit regarding the release of the goods via an ‘Exit Release Notification’
(IE525). The outcome of the process is ‘Goods Released for Exit’ and the process ends
here (the state at the Customs Office of Exit is changed either to ‘Goods Released for
Immediate Leave’ in case of no storing, or to ‘Goods Held for Storing’ in case of storing
of goods.).
2.4.2.2. Control Results were not satisfactory, and the goods are not released for Exit. The state is
changed to ‘Goods Not Allowed to Exit’ which is a final state , and the process stops at
this point.
Note: IF the timer expires and no IE507 has been received at OoExt, then the state of the Exit Summary
Declaration changes to “Assumed Exited”.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 97 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
OR
IF IE525 is sent from OoExt and the timer expires and no IE590 has been received at OoExt, then OoExt
invalidates the Exit Summary Declaration. The Invalidation of an EXS can only take place if the EXS is in
specific states.
Final Situation:
• Decision not to control the goods or control results were satisfactory, goods are released for Exit, AES
notifies the Trader at Exit via an ‘Exit Release Notification’ (IE525) and the outcome of the process is
‘Goods Released for Exit’ (the state at the Customs Office of Exit is changed either to ‘Goods Released
for Immediate Leave’ in case of no storing, or to ‘Goods Held for Storing’ in case of storing of goods.).
• Control results were not satisfactory, so goods were not released for Exit and the state is change d to
‘Goods Not Allowed to Exit’.
Register Exit Summary Declaration Process: L4 -EXP-
01-10-07
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
1. The process L4 -EXP-01-10-07-Register Exit Summary Declaration is initiated with the reception of the
Exit Summary Declaration.
2. AES validates the Exit Summary Declaration, and then two cases may occur:
2.1. Exit Summary Declaration is valid , AES generates MRN for this Exit Summary Declaration , AES
notifies the Trader at Exit of the registration of the Exit Summary Declaration via an ‘Exit Summary
Declaration Acknowledgement’ (IE628) message the state is changed to ‘Registered’, and the process
ends.
2.2. Exit Summary Declaration is invalid , AES notifies the Trader at Exit of the Rejection of the Exit
Summary Declaration via message ‘Rejection from Office of Exit ’ (IE557) and the process stops at
this point until a new Exit Summary Declaration is received.
The process which initiated this process can now continue.
Final situation:
• State of the movement is set to ‘Registered’
Register and Record Control Decision-Exit Summary Declaration Process: L4 -EXP-
01-10-02
Organisation: National Customs Administration
Location: Office of Exit
Constraint: N/A
Description:
The process L4 -EXP-01-10-02- Register and Record Control Decision -Exit Summary Declaration is initiated
with the registered decision of the Customs Officer on whether to control the goods.
Two cases may occur:
1.The Customs Officer registers the decision to control the goods:
The Customs Officer registers the decision to control in AES and the type of controls to be performed. The
movement state is set to 'Under Control'. The trader at exit is notified with an ‘Exit Control Decision
Notification’ (IE561) of the decision to control as he is the person lodging the exit summary declaration, in
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 98 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
order to allow him to be present during the control. The process which initiated this process can now
continue.
2.The Customs Officer registers decision not to control the goods:
The Customs Officer records in AES the decision not to control the consignment. The goods are ready to
be released for exit. The movement state is set to 'Goods ready to be released'. The process which initiated
this process can now continue.
Final situation:
One of the following decisions is registered:
• No control at all, the movement state is set to ‘Goods Ready to be Released’.
• Controls will be performed, and the movement state is set to ‘Under Control’.
Process Arrival Notification-Exit Summary Declaration Process: L4 -EXP-
01-10-03
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint:
The Customs Office of Exit may not know whether the provided MRN in the arrival notification (IE507) relates
to an Exit Summary declaration. If AES cannot find the data related to the provided MRN, a ‘Declaration
Request Export ’ (IE502) is sent in any case. This process is therefore used for exit summary declarations
processing.
Description:
1. Goods are presented to the Office of Exit and two cases may occur:
1.1. Trader at Exit lodges the ‘Arrival at Exit’ (IE507) notification and AES validates the Arrival at Exit
Notification.
Two cases may occur:
1.1.1. ‘Arrival at Exit’ (IE507) notification is valid, and the process continues from point 2.
1.1.2. ‘Arrival at Exit’ (IE507) notification is invalid, AES notifies the Trader at Exit with ‘Rejection
from Office of Exit ’ (IE557) and the outcome of this process is ‘Arrival at Exit Notification
Rejected’. The process which initiated this process can now continue.
1.2. Customs Officer at Customs Office of Exit registers the Arrival at Exit Notification, AES records the
Arrival at Exit Notification, and the process continues from point 2.
2. AES identifies if EXS data is available.
Two cases may occur:
2.1. EXS data is available, so AES records the Arrival at Exit Notification, and the outcome of this process
is ‘Goods Presented at Exit’. The process which initiated this process can now continue.
2.2. EXS data is not available , so the outcome of this process is ‘EXS not available’. The process which
initiated this process can now continue.
Final situation:
• If the exit summary declaration data is available at the Customs Office of Exit, the movement state is
set to ‘Goods Presented at Exit’.
• If the exit summary declaration data is not available at the Customs Office of Exit, the outcome of the
process is ‘EXS not available’.
• If the Arrival at Exit Notification is invalid , AES notifies the Trader at Exit , and the outcome of the
process is ‘Arrival at Exit Notification Rejected’.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 99 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Handle Declaration Request Response-Exit Summary Declaration Process: L4 -EXP-
01-10-04
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint:
The AES of the Customs Office of Exit having previously sent out a ‘Declaration Request Export’ (IE502) must
be able to receive and process following possible responses:
• ‘Exit Summary Declaration Response ’ (IE603), including the requested Exit Summary Declaration
data or
• ‘Exit Summary Declaration Response’ (IE603), not including the requested Exit Summary Declaration
data.
Description:
1. The Customs Office of Exit receives the response from the Customs Office of Lodgement regarding a
requested Exit Summary Declaration.
2. AES records the Exit Summary Declaration Data Response. Based on whether the response was positive or
negative, two cases may occur:
2.1. If the Exit Summary Declaration Data is available, the movement state is changed to ‘Goods presented
at Exit’.
2.2. If the Exit Summary Declaration Data is not available, AES notifies the Trader about the rejection
with a ‘Diversion Rejection Notification ’ (IE521) and the movement state is changed to ‘Diversion
Rejected’.
The process which initiated this process can now continue.
Final situation:
• If the Exit Summary Declaration Data Response is positive the movement state is changed to ‘Goods
presented at Exit’.
• If the Exit Summary Declaration Data Response is negative, the Trader at Exit is informed accordingly,
and the movement state is changed to ‘Diversion Rejected’.
Register Control Results-Exit Summary Declaration Process: L4 -EXP-
01-10-05
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process L4 -EXP-01-10-05-Register Control Results -Exit Summary Declaration is initiated when the
Customs Officer at the Office of Exit registers the results of a control in AES .
AES records the control results. Based on the control results, two cases may occur:
1. If control results are satisfactory, the movement state is changed to ‘Goods Ready to Released’.
2. If control results are not satisfactory , AES notifies the Trader at Exit with an ‘Exit Release Rejection’
(IE522) and the movement state is changed to ‘Goods Not Allowed to Exit’.
The process which initiated this process can now continue.
Final situation:
• If control results are satisfactory, the movement state is changed to ‘Goods Ready to be Released’.
• If control results are not satisfactory, AES notifies the Trader at Exit with an ‘Exit Release Rejection’
(IE522) and the movement state is changed to ‘Goods Not Allowed to Exit’.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 100 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Results
R_Goods Not Allowed to Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
Due to major discrepancies detected, the goods are not released for exit. This is a final state.
R_Goods Released for Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
The goods have been released for Exit and the state at the Customs Office of Exit is changed either to ‘Goods
Released for Immediate Leave’ in case of no storing, or to ‘Goods Held for Storing’ in case of storing of goods.
Minor Results
R_Exit Summary Declaration Rejected
Organisation: National Customs Administration
Location: Customs Office of Exit, Customs Office of Lodgement
Exit Summary Declaration is rejected. This is a final state.
R_Invalidation Initiated
Organisation: National Customs Administration
Location: Customs Office of Exit
AES initiates the invalidation of the re -export notification or exit summary declaration for which no exit
notification has been received within the time limit.
R_Arrival at Exit Notification Rejected
Organisation: National Customs Administration
Location: Customs Office of Exit
The Arrival at Exit Notification is rejected by AES.
R_EXS Rejected by Office of Lodgement
Organisation: National Customs Administration
Location: Customs Office of Exit
The Exit Summary Declaration data is not available in the Customs Office of Lodgement.
R_Assumed Exited
Organisation: National Customs Administration
Location: Customs Office of Lodgement
Time limit for Assumed Exit expires.
R_Arrived Elsewhere
Organisation: National Customs Administration
Location: Customs Office of Lodgement
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 101 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
The goods were presented at another Customs Office of Exit than the declared one and the Exit Summary
Declaration Data was available at the Customs Office of Lodgement.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 102 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
3.3 L4-EXP-01-11-EXIT SUMMARY DECLARATION-PROCESS EXIT
Figure 33: L4-EXP-01-11-Exit Summary Declaration-Process Exit
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 103 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_ Goods Released for Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at Customs Office of Exit has determined that the goods can be released for exit.
Processes
Exit Summary Declaration-Process Exit Process: L4 -EXP-
01-11
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
This process is triggered by an end event included in one of the following processes:
L4-EXP-01-10-Exit Summary Declaration -Process Registration and Arrival or L4 -EXP-01-13-04-Release
Goods for Exit-Re-Export Notification.
1. The process starts with the Goods Released for Exit.
2. AES identifies if the goods shall be stored based on the 'Exit Summary Declaration' (IE615) or 'Exit
Summary Declaration Amendment' (IE613) or the ‘Arrival at Exit’ (IE507) (in case of EXS lodged at
another Customs Office of Exit). The following cases may occur:
2.1. Goods are released for immediate leave and the process continues from point 3.
2.2. Goods are held for storing and the process continues with L4-EXP-01-11-01-Process Manifest
Presentation-Exit Summary Declaration. Manifest Presentation is accepted, and the process
continues from point 3.
3. The process L4 -EXP-01-11-02-Handle Exit Notification -Exit Summary Declaration is executed. The
following cases may occur:
3.1. Exit Results are Available and
3.1.1. AES stops the time limit to Receive Exit Notification.
3.1.2. State is changed to ‘Exited’ and the process ends at this point.
3.2. Goods are “Partially Exited”, and the process continues from point 2.2 until a Manifest Presentation,
with “final shipment” designation is received.
Final Situation:
• The Exit Results are available, the state is changed to ‘Exited’ and the process ends at this point.
Process Manifest Presentation-Exit Summary Declaration Process: L4 -EXP-
01-11-01
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint:
National variants are possible depending on the local organisations.
It must be possible to receive and process amendments of the presented manifest (i.e. mainly reduction of the
cargo, and/or its increase), not described here.
Description:
AES receives a ‘Manifest Presentation’ (IE547) from the Trader at Exit and validates the Manifest presentation.
Based on the outcome of the validation, two cases may occur:
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 104 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
1. Manifest presentation is valid, AES records the Manifest presentation , notifies the Trader at Exit of the
Manifest Presentation Acceptance via a positive ‘Manifest Validation’ (IE548) and the movement state is
changed to either “ Goods Released for Immediate Leave ” or “Goods Released for Immediate Leave
(Partial)”. The outcome of the call-activity is ‘Manifest Presentation Accepted’, and the process ends at this
point.
2. Manifest presentation is invalid, AES notifies the Trader at Exit of the Manifest Presentation Rejection via
a negative ‘Manifest Validation’ (IE548) and the process returns to the start of the model, waiting for a
valid ‘Manifest Presentation’ (IE547).
Final Situation:
Manifest Presentation is accepted.
Handle Exit Notification-Exit Summary Declaration Process: L4 -EXP-
01-11-02
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
This process is initiated when a Manifest Presentation is Accepted , or the Goods are Released for Immediate
Leave.
1. One of the following two cases is fulfilled:
1.1. Exit Information is available through Commercial or Port or Transport system and AES records the
Exit Information, and the process continues from point 2.
1.2. An ‘Exit Notification’ (IE590) is received , and AES performs validation . Based on the outcome of
the Exit Notification validation, two cases may occur:
1.2.1. Exit Notification is valid, AES records the Exit Notification , and the process continues from
point 2.
1.2.2. Exit Notification is invalid, and AES notifies the Trader at Exit of the invalid Exit Notification
via a ‘Rejection from Office of Exit’ (IE557). Τhe process continues from point 1.
2. AES identifies if Exit Information/‘Exit Notification’ (IE590) refers to Partial Exit. Based on the outcome
of the previous check, two cases may occur:
2.1. Exit Information/‘Exit Notification’ (IE590) refers to Partial Exit, the movement state is changed to
‘Partially Exited’ and the process ends at this point.
2.2. Exit Information/‘Exit Notification’ (IE590) doesn’t refer to Partial Exit and the process ends at this
point with the outcome ‘Exit Results Available’, having the movement state ‘Exited’.
Final Situation:
• If the Exit Information/‘Exit Notification’ (IE590) refers to Partial Exit , then the state is changed to
‘Partially Exited’ and the process ends at this point.
• If the Exit Information/‘Exit Notification’ (IE590) doesn’t refer to Partial Exit , then the process ends
at this point with outcome ‘Exit Results Available’ and movement state turns to ‘Exited’.
Major Results
R_Goods Exited
Organisation: National Customs Administration
Location: Customs Office of Exit
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 105 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
The goods have exited the customs territory.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 106 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
3.4 L4-EXP-01-12-AMENDMENT OF EXIT SUMMARY DECLARATION
Figure 34: L4-EXP-01-12-Amendment of Exit Summary Declaration
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 107 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Declarant/Representative submits an amendment
Organisation: Person Lodging the Exit Summary Declaration or Representative at Exit
Location: Premises of the Person Lodging the Exit Summary Declaration or of the Representative at Exit
The Declarant/Representative submits an amendment to his/her declaration.
Processes
Amendment of Exit Summary Declaration Process: L4-EXP-
01-12
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint:
This process is only used if an amendment request with ‘Exit Summary Declaration Amendment ’ (IE613) is
received.
The amendment request must be sent to an Office which is located in the same Member State as the previously
declared Office of Exit (i.e. the initial Exit Summary Declaration must be available in the national system).
The amendment request cannot be sent to the Customs Office of Lodgement.
The amendment request can be accepted only if it is sent by the Person lodging the Exit Summary Declaration
(if he has access to the Customs AES at Exit) or by his /her Representative at Exit declared in the initial ‘Exit
Summary Declaration’ (IE615).
An amendment request may concern the creation, modification or deletion of data within an Exit Summary
Declaration (e.g. adding, modifying or deleting goods items in an Exit Summary Declaration).
Description:
The process starts when an amendment request is submitted by the Declarant/Representative using electronic
means via an ‘Exit Summary Declaration Amendment ’ (IE613) message. It contains all values of the original
declaration altered with the requested amendments.
AES validates the Exit Summary Declaration Amendment request and then two cases may occur:
1. If the Exit Summary Declaration Amendment request is valid . AES records the Exit Summary
Declaration Amendment request , and the d eclaration data are amended . The process continues and
AES notifies the Declarant/Representative of ‘Exit Summary Declaration Amendment Acceptance’
(IE604). The process ends at this point with ‘Exit Summary Declaration Amended’.
2. If the Exit Summary Declaration Amendment request is invalid, AES notifies the
Declarant/Representative of the Exit Summary Declaration Amendment request rejection with
‘Rejection from the Office of Exit’ (ΙΕ557) and the process ends at this point with ‘Exit Summary
Declaration Amendment Rejected’.
Final situation:
• If the amendment is rejected , the outcome of the process is ‘Exit Summary Declaration Amendment
Rejected’.
• If the amendment is accepted, the outcome of the process is ‘Exit Summary Declaration Amendment
Amended’.
Major Results
R_Amendment accepted by Office of Exit
Organisation: National Customs Administration
Location: Premises of the Declarant/Representative.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 108 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
The amendment is accepted. The acceptance is communicated.
R_Amendment rejected by Office of Exit
Organisation: National Customs Administration
Location: Premises of the Declarant/Representative.
The amendment is rejected. The rejection is communicated.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 109 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
3.5 L4-EXP-01-22-EXIT SUMMARY DECLARATION/RE -EXPORT NOTIFICATION
INVALIDATION
Figure 35: L4-EXP-01-22-Exit Summary Declaration/Re-Export Notification Invalidation
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 110 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_ Receive EXS/REN Invalidation Request
Organisation: National Customs Administration
Location: Customs Office of Exit
AES receives an EXS or REN Invalidation Request from the Trader at Exit.
E_ Time Limit to Receive Arrival at Exit Notification Expires
Organisation: National Customs Administration
Location: Customs Office of Exit
Timer to Receive Arrival at Exit Notification expires at this point.
Processes
Exit Summary Declaration/Re-Export Notification Invalidation Process: L4 -EXP-
01-22
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
1. The process is triggered when one of the following two cases occur:
• Receive EXS/REN Invalidation Notification
• Time Limit to Receive Arrival at Exit expires
1.1. AES receives an EXS/REN Invalidation Notification via an ‘EXS/REN Invalidation Request’ (IE614)
and then,
1.1.1. AES records the ‘EXS/REN Invalidation Request’ (IE614),
1.1.2. AES validates the ‘EXS/REN Invalidation Request’ (IE614) and based on the outcome of the
validation; two cases may occur:
1.1.2.1. EXS/REN Invalidation Notification is valid, and the process continues at point 2.
1.1.2.2. EXS/REN Invalidation Notification is invalid, AES notifies the Trader at Exit of the
rejection of the invalidation request via an ‘Rejection from Office of Exit ’ (IE557)
message and the process ends at this point with outcome ‘EXS/REN Invalidation Request
Rejected’.
1.2. Timer to Receive Arrival at Exit expires and then the process continues at point 2.
2. AES invalidates the EXS/REN.
3. AES notifies the Trader at Exit of EXS/REN Invalidation Decision via an ‘EXS/REN Invalidation
Decision’ (IE609).
4. AES stops the timer to Receive Exit Notification.
5. The movement state is changed to ‘Invalidated’, and the process ends at this point.
Final Situation:
• AES invalidates EXS/REN and movement state is changed to ‘Invalidated’.
• EXS/REN Invalidation Request is invalid, and the process ends with outcome ‘EXS/REN Invalidation
Notification Request Rejected’.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 111 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Results
R_EXS/REN Invalidated
Organisation: National Customs Administration
Location: Customs Office of Exit
EXS/REN is invalidated.
R_EXS/REN Invalidation Request Rejected
Organisation: National Customs Administration
Location: Customs Office of Exit
EXS/REN is rejected as invalid.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 112 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
4. AES – RE-EXPORT NOTIFICATION
4.1 INTRODUCTION
This section presents the various business process threads related to the Re -Export Notification which is used in
case goods leaving the customs territory of the Union are not assigned to a customs approved treatment or use for
which a customs declaration or re-export declaration or EXS is required (The latter being dealt with in section 2).
Whenever possible, the Elementary Business Processes (EBP's) of the AES -Export process have been used.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 113 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
4.2 L4-EXP-01-13-RE-EXPORT NOTIFICATION-PROCESS REGISTRATION
Figure 36: L4-EXP-01-13-Re-Export Notification-Process Registration (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 114 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 37: L4-EXP-01-13-Re-Export Notification-Process Registration (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 115 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Re-Export Notification Received
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at Customs Office of Exit receives a re-export notification.
Processes
Re-Export Notification-Process Registration Process: L4-EXP-
01-13
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process starts when the Custom Office of Exit receives a ‘Re-Export Notification’ from the trader (IE570).
1. The process L4 -EXP-01-13-01 Acceptance of Re -Export Notification is executed. The re -export
notification is validated by AES and one of the following cases is fulfilled:
1.1. The re-export notification is invalid, and it is rejected. The process flow stops at this point.
1.2. The re-export notification is valid and accepted and AES interfaces with the national risk analysis
systems of the Member States to request a Risk Analysis. Based on the risk analysis one of the
following cases is fulfilled:
1.2.1. The Customs Officer decides not to control the goods , and the state of the movement is set to
‘Goods Ready to be Released ’. The process L4 -EXP-01-13-04-Release Goods for Exit (Re -
Export Notification) is executed, and the process flow continues from point 2.
1.2.2. The Customs Officer decides to control the goods, hence the state of the movement is set to
‘Under Control ’. The process L4-EXP-01-13-03-Register Controls Results -Re-Export
Notification is executed and one of the following cases is fulfilled:
1.2.2.1. The control results are ‘satisfactory’ and AES records that the goods are ready to be
released for exit. The state of the movement is set to ‘Goods Ready to be Released ’ and
the process flow continues from point 2.
1.2.2.2. The control results are ‘not satisfactory’ and AES records that the goods cannot be
released for exit. The movement is stopped here, and the state of the movement is set to
‘Goods Not Allowed to Exit’.
2. Next, the process L4-EXP-01-13-04-Release Goods for Exit (Re-Export Notification) is executed, and the
movement state is set either to ‘Goods Released for Immediate Leave’ or to ‘Goods Held for Storing’.
Acceptance of Re-Export Notification Process: L4 -EXP-
01-13-01
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process is initiated when a ‘Re-Export Notification’ (IE570) is submitted to the Customs Office of Exit.
The person lodging the Re -Export Notification must provide a local reference number (LRN) that - until the
issuing of an MRN - allows the person lodging the Re-Export Notification and the Office of Exit to refer to the
data in AES. AES checks that the provided LRN is unique.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 116 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
The Person lodging the Re -Export Notification can specify a Representative (at Exit) being allowed to amend
the Re-Export Notification on his/her behalf.
Validation of the Re-Export Notification must be performed. One of the following cases is fulfilled:
1. If the Re-Export notification is invalid, AES rejects it and notifies with a ‘Rejection from Office of Exit ’
(IE557) the person lodged the re-export notification that the declaration is invalid, giving the reason of the
rejection and the process stops at this point.
2. If the Re-export notification is valid, the Customs Office of Exit registers the notification and AES starts
the timer to receive the exit notification. If the goods do not exit within the time limit, the Re -Export
Notification is deemed not to be lodged and can be invalidated.
Next, a MRN is automatically generated, and the notification submission date and time are stored in AES. The
allocated MRN is immediately communicated with a ‘Re-Export Notification Registration ’ (IE571) to the
person lodged the re-export notification.
The automatic risk analysis will be performed at this stage, process L4 -EXP-01-01-01-02-Request and Record
Risk Analysis is executed. Random risk parameters should be used additionally. AES registers the results of the
risk analysis.
Final situation:
• If the notification is not valid it is rejected and the person lodging the Re -Export Notification is
informed with a ‘Rejection from Office of Exit’ (IE557).
• If the notification is valid, it is registered and an MRN is generated and allocated. The trader at exit is
notified with ‘Re-Export Notification Registration ’ (IE571) for the registration of the Re -Export
Notification by the immediate issuance of an MRN. The result of the risk analysis performed is
recorded. The movement state at the Office of Exit is set to ‘Registered'.
Decide to Control-Re-Export Notification Process: L4 -EXP-
01-13-02
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process L4 -EXP-01-13-02-Decide to Control -Re-Export Notification is initiated with the receipt of the
results of the risk analysis he/she had requested.
The Customs Officer compiles all the information he needs (the risk analysis results -retrieved by AES via the
MRN), in order to decide whether a control is required. Even if the risk analysis is an automatic process, the
final decision to control may be overruled by the Customs Officer .
Based on the risk analysis one of the following cases is fulfilled:
1. The Customs Officer registers his/her decision to perform controls and specifies the types of controls that
will be performed. The movement state is set to 'Under Control'. The Trader at Exit is notified with ‘Export
Control Decision Notification ’ (IE561) of the decision to control in order to allow him/her to be present
during the controls.
2. The Customs Officer records in AES the decision not to control the consignment. The goods are ready to
be released for exit (i.e. to be allowed to be stored prior to exit or to be allowed to immediate leave the
Union). The movement state is set to ‘Goods Ready to be Released’.
Final situation:
One of the following decisions is registered:
• The movement state is set to ‘Goods Ready to be Released’ or,
• The movement state is set to ‘Under Control’.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 117 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Register Control Results-Re-Export Notification Process: L4 -EXP-
01-13-03
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
This process is initiated after the goods have been controlled by the Customs Officer. The Customs Officer at
the Office of Exit registers the results of the control in AES.
Based on the control results one of the following cases is fulfilled:
1. The control results are ‘satisfactory’ and AES records that the goods are ready to be released for exit. Minor
discrepancies can be regarded as 'satisfactory'. The goods may also be ready to be released for exit.
2. The control results are ''not satisfactory' and AES records that the goods are not allowed to exit. The
movement is stopped here without prejudice of any subsequent measure to be taken. The movement state
is set to ‘Goods Not Allowed to Exit’. AES will notify with an ‘Exit Release Rejection’ (IE522) the Trader
at Exit about the rejection reason of the Exit Release, which is the final state, and the process ends.
Final situation:
Control results are stored in AES:
• The goods are ready to be released (if ‘satisfactory' is considered), the movement state is set to ‘Goods
Ready to be Released’.
• The goods are to be stopped (if 'not satisfactory' is considered), the movement state is set to ‘Goods
not Allowed to Exit’.
Release Goods for Exit-Re-Export Notification Process: L4-EXP-
01-13-04
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
This process is initiated when either the Customs Officer registered decision not to control the goods at Exit or
when the decision was taken to control the goods , and the control results were satisfactory. In both cases, the
state of the movement is ‘Goods Ready to be Released’.
‘Goods Ready to be Released’ are released either for immediately leaving the Union or for being stored in a
warehouse prior to their exit (see L4 -EXP-01-14-01-Process Manifest Presentation -Re-Export Notification).
The Trader at Exit is notified with ‘Exit Release Notification’ (IE525) consequently.
Final situation:
• The goods are released to exit, and the movement state is set to ‘Goods Released for Immediate Leave’.
• The goods are to be stored prior the exit and the movement state is set to 'Goods Held for Storing'.
Major Results
R_Goods Released for Immediate Leave
Organisation: National Customs Administration
Location: Customs Office of Exit
The goods have been released for immediate leave.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 118 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
R_Goods Held for Storing
Organisation: National Customs Administration
Location: Customs Office of Exit
The goods held for storing.
Minor Results
R_Re-Export Notification Rejected
Organisation: National Customs Administration
Location: Customs Office of Exit
AES at the Customs Office of Exit rejects the invalid re-export notification.
R_Goods Not Allowed to Exit
Organisation: National Customs Administration
Location: Customs Office of Exit
Due to major discrepancies detected, the goods are not allowed to exit. This is a final state.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 119 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
4.3 L4-EXP-01-14-RE-EXPORT NOTIFICATION-PROCESS EXIT
Figure 38: L4-EXP-01-14-Re-Export Notification-Process Exit
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 120 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Goods Released for Immediate Leave
Organisation: National Customs Administration
Location: Customs Office of Exit
The goods have exited the customs territory.
E_Goods Held for Storing
Organisation: National Customs Administration
Location: Customs Office of Exit
The goods have stored prior to their exit from the customs territory.
Processes
Re-Export Notification-Process Exit Process: L4-EXP-
01-14
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
This process is triggered by the end events included in L4 -EXP-01-13-04-Release Goods for Exit -Re-Export
Notification.
1. The AES at the Customs Office of Exit identifies whether goods shall be stored based on Exit Release
Notification information. One of the following cases is fulfilled:
1.1. The goods are held for storing, hence L4-EXP-01-14-01 is executed. The manifest presentation is
accepted in L4-EXP-01-14-01 and then process continues from point 2.
1.2. If the goods are released for immediate leave, then the process continues from point 2.
2. L4-EXP-01-14-02 is executed and there are two possible cases:
2.1. Partial exit is recorded, and the movement state is set to ‘Partially Exited’. The process flow
continues from point 1.1. but while the state is in ‘Partially Exited’.
2.2. Final exit is recorded, and the movement state is set to ‘Exited’. The process ends at this point.
The manifest can happen for the whole Re-Export Notification and not only for Partial Exit Consignment. The
manifest presentation (or load list) shall include all goods to be loaded onto the ship, irrespective of their status
and, where applicable, the MRN linking the manifest to the re-export notification for the shipments concerned.
Final situation:
• The goods are exited.
Process Manifest Presentation-Re-Export Notification Process: L4 -EXP-
01-14-01
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
The process starts with two start events:
• Goods Held for Storing.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 121 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
• Receive Manifest Presentation in ‘Partially Exited’ state.
Next, the manifest for the goods covered by the re-export notification is submitted with a ‘Manifest Presentation’
(IE547) via electronic means to the actual Office of Exit and is registered and validated. The validation process
can be a completely automatic process.
The manifest contains, apart from the data required in the international Convention and/or in the national
provisions, one or more 'MRN' and – in case a partial Exit shall be processed linking the manifest to the arrival
notification and to the re -export notification and to the item(s) concerned. The manifest presentation (or load
list) shall include all goods to be loaded onto the ship, irrespective of their status and, where applicable, the
MRN linking the manifest to the re-export notification for the shipments concerned.
For each shipment AES also checks the marks and numbers, number of packages, gross weight, and the
description of the goods (where coded on the manifest).
The validation performed by AES will result one of the following cases:
1. If the presentation is invalid, AES rejects the submitted ‘Manifest Presentation’ (IE547) and notifies with
‘Manifest Validation’ (IE548) the Trader at Exit that the presentation is invalid with the reasons of the
rejection. The movement state at the actual Office of Exit remains 'Goods held for storing'. AES continues
to wait for a valid Manifest Presentation or until the Customs Officer registers exit results.
2. If the presentation is valid, AES records the total or partial intended leave with the given means of transport
and the goods are ready to immediately leave the Union. The Trader at Exit is notified consequently with
‘Manifest Validation’ (IE548). The movement state at the actual Office of Exit is set to 'Goods released for
Immediate Leave' in case of whole Re -Export Notification and to ‘Goods released for Immediate Leave
(Partial)’ in case of partial exit.
Final situation:
If the presentation of manifest is valid, the manifest is accepted, and the movement state is set to ‘Goods released
for Immediate Leave’ in case of final exit in one 'step' or ‘Goods released for Immediate Leave (Partial)’ in case
of partial exit.
Handle Exit Notification-Re-Export Notification Process: L4 -EXP-
01-14-02
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint: N/A
Description:
1. The process starts with two start events:
• Manifest Presentations Accepted.
• Goods Released for Immediate Leave.
Next, one of the following cases is fulfilled:
1.1. The actual Office of Exit is notified with an ‘Exit Notification’ (IE590) by the Trader at Exit that the
goods have left the EU territory, either on the basis of the re -export notification (EXPORT
OPERATION FOR IE590.MRN) or on the basis of the manifest linked to a given means of transport
(EXPORT OPERATION FOR IE590.Ma nifest Number). The manifest can refer either to the whole
shipment (final) or to a part of it (partial).
The process continues with the validation of the received ‘Exit Notification’ (IE590) by AES. One of
the following cases is fulfilled:
1.1.1. If the received ‘Exit Notification’ (IE590) is invalid, AES informs the trader at exit about the
exit notification rejection with ‘Rejection from Office of Exit ’ (IE557) and loops back waiting
for a new ‘Exit Notification’ (IE590).
1.1.2. If the received Exit Notification is valid, based on the re -export notification MRN or on the
MRNs/item numbers referred to the manifest, AES records the actual exit of the goods from the
Union.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 122 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
1.2. AES receives the Exit Information that is available through the Commercial or Port or Transport
System linked to the re -export notification (MRN) or on the basis of the manifest document and the
process flow continues from point 2.
2. Next, AES identifies if the Exit Information refers to partial or final exit of goods.
2.1. In case a partial exit is recorded the movement state changes to ‘Partially Exited’ and the process ends
at this point.
2.2. In case a final shipment is recorded, then the timer to receive the exit notification stops, the state
changes to ‘Exited’ and the process ends at this point.
Final Situation:
• If partial exit is recorded, the movement state is set to ‘Partially Exited’.
• If total exit is recorded, the movement state is set to 'Exited'.
Major Results
R_Goods Exited
Organisation: National Customs Administration
Location: Customs Office of Exit
The goods have exited the customs territory.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 123 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
4.4 L4-EXP-01-15-AMENDMENT OF THE RE-EXPORT NOTIFICATION
Figure 39: L4-EXP-01-15-Amendment of the Re-Export Notification (Part A)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE BUSINESS Page 124 / 129
Document version 7.10EN dated 15/05/2025
Confidentiality: Commission use (CU)
Figure 40: L4-EXP-01-15-Amendment of the Re-Export Notification (Part B)
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 125 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Events
E_Trader submits an amendment request
Organisation: Trader at Exit
Location: Premises of the Trader or Customs Office of Exit
The Trader submits an amendment to his/her declaration.
Processes
Amendment of the Re-Export Notification Process: L4-EXP-
01-15
Organisation: National Customs Administration
Location: Customs Office of Exit
Constraint:
This process is only used if a ‘Re-Export Notification Amendment Request’ (IE573) is received.
The amendment request must be sent to an Office which is located in the same Member State as the previously
declared Office of Exit (i.e. the initial Re-Export Notification must be available in the national system).
The amendment request can be accepted only if it is sent by the Person lodging the Re -Export Notification (if
he has access to the Customs AES at Exit) or by his/her Representative at Exit declared in the initial ‘Re-Export
Notification’ (IE570).
An amendment request may concern the creation, modification or deletion of data within a Re -Export
Notification (e.g. adding, modifying or deleting goods items in a Re-Export Notification).
The Re-Export Notification amendment request cannot be accepted if:
• The Trader was informed about the customs decision to control the goods .
• The Re-Export Notification Particulars are incorrect.
• The Goods are released for exit.
Description:
This process starts when an ‘Re-Export Notification Amendment Request ’ (IE573) is received. AES validates
the received Re-Export Notification Amendment Request against the business rules and conditions. One of the
following cases is fulfilled:
1. If the validation against the business rules and conditions fails, the request is rejected. AES records the
rejection reasons and informs with ‘Rejection from Office of Exit’ (IE557) the trader at exit accordingly.
The process ends at this point and the state of the movement at Exit remains as -is (either ‘Registered’ or
‘Goods Ready to be Released’).
2. If the validation of the re -export notification amendment request is successful, then AES records the re -
export notification request and amends the customs declaration data accordingly while the movement state
remains as-is (either ‘Registered’ or ‘Goods Ready to be Released ’). Next, AES informs the trader at exit
with ‘Re-Export Notification Amendment Acceptance’ (IE574) and the process ends at this point.
Final situation:
• The Re-export Amendment request rejected.
• The Re-export Amendment request accepted.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 126 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
Major Results
R_Amendment accepted by Office of Export
Organisation: National Customs Administration
Location: Premises of the Trader or Customs Office of Exit
The amendment is accepted. The acceptance is communicated to the Trader.
R_Amendment rejected by Office of Export
Organisation: National Customs Administration
Location: Premises of the Declarant/Representative or Customs Office of Export
The amendment is rejected. The rejection is communicated to the Trader.
FUNCTIONAL SYSTEM SPECIFICATIONS – AES DOCUMENT - SECTION I A: BUSINESS PROCESS THREADS FOR CORE
BUSINESS Page 127 / 129
Document version 7.10 EN dated 15/05/2025
Confidentiality: Commission use (CU)
5. INDEX OF EBPS
L4-EXP-01-01-Customs Formalities at Office of Export-Acceptance and Controls
L4-EXP-01-02-Customs Formalities at Office of Export-Release
L4-EXP-01-04-Supplementary Declaration
L4-EXP-01-05-Amendment of the Export Declaration
L4-EXP-01-07-Customs Formalities at Office(s) of Exit-Process Exit
L4-EXP-01-08-Enquiry Procedure
L4-EXP-01-16-Operation Information Query
L4-EXP-01-17-Operation Status Check
L4-EXP-01-19-Handle Diversion
L4-EXP-01-21-Customs Formalities at Office(s) of Exit-Handle Controls and Release of Goods
L4-EXP-01-23-Customs Formalities at Office of Export-Handle Exit Results/Alternative Evidence
L4-EXP-01-24-Customs Formalities at Office(s) of Exit-Process Arrival Notification
L4-EXP-01-25-Process Transit Release Notification
L4-EXP-01-26-Export Declaration Invalidation
L4-EXP-01-27-Handle Goods Movement Additional information
L4-EXP-01-10-Exit Summary Declaration-Process Registration and Arrival
L4-EXP-01-11-Exit Summary Declaration-Process Exit
L4-EXP-01-12-Amendment of Exit Summary Declaration
L4-EXP-01-22-Exit Summary Declaration/Re-Export Notification Invalidation
L4-EXP-01-13-Re-Export Notification-Process Registration
L4-EXP-01-14-Re-Export Notification-Process Exit
L4-EXP-01-15-Amendment of the Re-Export Notification
Electronically signed on 13/08/2025 14:43 (UTC+02) in accordance with Article 11 of Commission Decision (EU) 2021/2121