# L_2019325EN.01016801.xml

| 16.12.2019 | EN | Official Journal of the European Union | L 325/168 |
| --- | --- | --- | --- |

16.12.2019

EN

Official Journal of the European Union

L 325/168

---

COMMISSION IMPLEMENTING DECISION (EU) 2019/2151

of 13 December 2019

establishing the work programme relating to the development and deployment of the electronic systems provided for in the Union Customs Code

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Regulation (EU) No 952/2013 of the European Parliament and of the Council of 9 October 2013 laying down the Union Customs Code (1), and in particular to Article 281 thereof,

Whereas:

| (1) | Article 6 of Regulation (EU) No 952/2013 laying down the Union Customs Code provides that all exchanges of information between customs authorities and between economic operators and customs authorities and storage of such information are to be made using electronic data processing techniques. Article 280 of the Regulation provides that the Commission is to draw up a work programme relating to the development and deployment of the electronic systems (‘the work programme’). |
| --- | --- |

(1)

Article 6 of Regulation (EU) No 952/2013 laying down the Union Customs Code provides that all exchanges of information between customs authorities and between economic operators and customs authorities and storage of such information are to be made using electronic data processing techniques. Article 280 of the Regulation provides that the Commission is to draw up a work programme relating to the development and deployment of the electronic systems (‘the work programme’).

| (2) | The Commission adopted the first work programme by means of Commission Implementing Decision 2014/255/EU (2) and updated it for the first time in 2016 by means of Commission Implementing Decision (EU) 2016/578 (3). The 2016 work programme needs to be updated to take account of new resource- and priority-based planning for the electronic systems. It is also necessary to take account of the amendment to Article 278 of Regulation (EU) No 952/2013 made by Regulation (EU) 2019/632 of the European Parliament and of the Council (4) to prolong the transitional use of means other than the electronic data-processing techniques provided for in Regulation (EU) No 952/2013. To ensure stable and reliable planning for deployment of electronic systems provided for in Regulation (EU) No 952/2013, future updates of the work programme should take place only if there are new developments. The provision requiring an update of the work programme every year should therefore be deleted. |
| --- | --- |

(2)

The Commission adopted the first work programme by means of Commission Implementing Decision 2014/255/EU (2) and updated it for the first time in 2016 by means of Commission Implementing Decision (EU) 2016/578 (3). The 2016 work programme needs to be updated to take account of new resource- and priority-based planning for the electronic systems. It is also necessary to take account of the amendment to Article 278 of Regulation (EU) No 952/2013 made by Regulation (EU) 2019/632 of the European Parliament and of the Council (4) to prolong the transitional use of means other than the electronic data-processing techniques provided for in Regulation (EU) No 952/2013. To ensure stable and reliable planning for deployment of electronic systems provided for in Regulation (EU) No 952/2013, future updates of the work programme should take place only if there are new developments. The provision requiring an update of the work programme every year should therefore be deleted.

| (3) | It is also necessary to further specify certain elements of the reporting obligation, which was imposed on the Member States and on the Commission by the new Article 278a of Regulation (EU) No 952/2013 in order to monitor the progress in developing the electronic systems. In accordance with paragraph 4 of this Article, Member States are to provide the Commission, twice per year, with an updated table on their own progress in developing and deploying the electronic systems. The table should contain the dates for completion of certain milestones and, in the event of delays or risks of delays, the mitigating actions as referred to in Article 278a(3). It is also necessary to specify the dates by which the Member States should send the information. This will allow the Commission to draft and submit its report on progress in developing the electronic systems to the European Parliament and to the Council at the end of each year. The Member States should also inform the Commission immediately of substantial changes in their IT planning. However, given the reporting obligation provided in Article 278a(4), it is no longer necessary to require the Member States to send information 6 months before the deployment of a new electronic system. |
| --- | --- |

(3)

It is also necessary to further specify certain elements of the reporting obligation, which was imposed on the Member States and on the Commission by the new Article 278a of Regulation (EU) No 952/2013 in order to monitor the progress in developing the electronic systems. In accordance with paragraph 4 of this Article, Member States are to provide the Commission, twice per year, with an updated table on their own progress in developing and deploying the electronic systems. The table should contain the dates for completion of certain milestones and, in the event of delays or risks of delays, the mitigating actions as referred to in Article 278a(3). It is also necessary to specify the dates by which the Member States should send the information. This will allow the Commission to draft and submit its report on progress in developing the electronic systems to the European Parliament and to the Council at the end of each year. The Member States should also inform the Commission immediately of substantial changes in their IT planning. However, given the reporting obligation provided in Article 278a(4), it is no longer necessary to require the Member States to send information 6 months before the deployment of a new electronic system.

| (4) | The work programme should list the electronic systems provided for in Regulation (EU) No 952/2013, the relevant Articles providing for those systems and the dates on which they are expected to become operational. The work programme should distinguish between the electronic systems that the Member States are to develop themselves (‘national systems’) and those that they are to develop in cooperation with the Commission (‘trans-European systems’). All these electronic systems are needed for Regulation (EU) No 952/2013 to be fully effective. The list should be based on the existing planning document covering all IT-related customs projects (the multi-annual strategic plan for customs, ‘MASP-C’ (5)), which is being drawn up in accordance with Decision No 70/2008/EC of the European Parliament and of the Council (6), and in particular Article 4 and Article 8(2) thereof. The electronic systems referred to in the work programme should be managed, prepared and developed as established in the MASP-C. |
| --- | --- |

(4)

The work programme should list the electronic systems provided for in Regulation (EU) No 952/2013, the relevant Articles providing for those systems and the dates on which they are expected to become operational. The work programme should distinguish between the electronic systems that the Member States are to develop themselves (‘national systems’) and those that they are to develop in cooperation with the Commission (‘trans-European systems’). All these electronic systems are needed for Regulation (EU) No 952/2013 to be fully effective. The list should be based on the existing planning document covering all IT-related customs projects (the multi-annual strategic plan for customs, ‘MASP-C’ (5)), which is being drawn up in accordance with Decision No 70/2008/EC of the European Parliament and of the Council (6), and in particular Article 4 and Article 8(2) thereof. The electronic systems referred to in the work programme should be managed, prepared and developed as established in the MASP-C.

| (5) | As the transitional period for the full application of Regulation (EU) No 952/2013 should be finished at the latest by the dates referred to in Article 278 provided for in this Regulation, the work programme defines in more detail the actual dates of deployment of each of the electronic systems and as such sets the end period of the application of the specific transitional measures as provided by Commission Delegated Regulation (EU) 2016/341 (7). |
| --- | --- |

(5)

As the transitional period for the full application of Regulation (EU) No 952/2013 should be finished at the latest by the dates referred to in Article 278 provided for in this Regulation, the work programme defines in more detail the actual dates of deployment of each of the electronic systems and as such sets the end period of the application of the specific transitional measures as provided by Commission Delegated Regulation (EU) 2016/341 (7).

| (6) | Where the work programme allows the Member States to choose to deploy a trans-European or national electronic system within a given period (i.e. deployment window), the Annex should make it clear that the ‘start date of deployment’ is the earliest date on which Member States may start operating the new electronic system and the ‘end date of deployment’ is the last date by which all Member States and all economic operators are to start using the new or upgraded electronic system. The end date of deployment should also be the end of the period of the transitional measures related to that electronic system. Those dates should therefore be set on the basis of the deadlines provided in paragraphs 1, 2 and 3 of Article 278 of Regulation (EU) No 952/2013. These deployment windows are necessary to implement the systems at Union level, taking into account the needs of each system. Different rules concerning deployment windows should apply to the customs project on pre-arrival security and safety (ICS2). In this case, all Member States should be ready to deploy each release of the project at the start date for the release, while economic operators should be given, with the agreement of the Member States, a possibility to connect within the deployment window. |
| --- | --- |

(6)

Where the work programme allows the Member States to choose to deploy a trans-European or national electronic system within a given period (i.e. deployment window), the Annex should make it clear that the ‘start date of deployment’ is the earliest date on which Member States may start operating the new electronic system and the ‘end date of deployment’ is the last date by which all Member States and all economic operators are to start using the new or upgraded electronic system. The end date of deployment should also be the end of the period of the transitional measures related to that electronic system. Those dates should therefore be set on the basis of the deadlines provided in paragraphs 1, 2 and 3 of Article 278 of Regulation (EU) No 952/2013. These deployment windows are necessary to implement the systems at Union level, taking into account the needs of each system. Different rules concerning deployment windows should apply to the customs project on pre-arrival security and safety (ICS2). In this case, all Member States should be ready to deploy each release of the project at the start date for the release, while economic operators should be given, with the agreement of the Member States, a possibility to connect within the deployment window.

| (7) | The deployment windows for the migration of national electronic systems should be adapted to the national project and migration plans of Member States and should take into account their specific national IT environments and circumstances. The end dates of deployment of national electronic systems should also bring to an end the periods of the transitional measures related to those electronic systems. Those dates should therefore be set on the basis of the deadlines provided in paragraphs 1, 2 and 3 of Article 278 of Regulation (EU) No 952/2013. |
| --- | --- |

(7)

The deployment windows for the migration of national electronic systems should be adapted to the national project and migration plans of Member States and should take into account their specific national IT environments and circumstances. The end dates of deployment of national electronic systems should also bring to an end the periods of the transitional measures related to those electronic systems. Those dates should therefore be set on the basis of the deadlines provided in paragraphs 1, 2 and 3 of Article 278 of Regulation (EU) No 952/2013.

| (8) | The Member States and the Commission should also ensure that the economic operators have received in a timely manner the technical information needed for them to update their own electronic systems and to connect to the new or upgraded electronic systems provided for in Regulation (EU) No 952/2013. Communication on the changes needed is to be provided between 12 and 24 months before deployment of a particular system, if necessary due to the scope and nature of that system. For minor changes, that period may be shorter. |
| --- | --- |

(8)

The Member States and the Commission should also ensure that the economic operators have received in a timely manner the technical information needed for them to update their own electronic systems and to connect to the new or upgraded electronic systems provided for in Regulation (EU) No 952/2013. Communication on the changes needed is to be provided between 12 and 24 months before deployment of a particular system, if necessary due to the scope and nature of that system. For minor changes, that period may be shorter.

| (9) | The dates of deployment of certain projects need to be modified to ensure synchronicity between the work programme and the MASP-C, and to take into account the new deadlines provided in Article 278 of Regulation (EU) No 952/2013. |
| --- | --- |

(9)

The dates of deployment of certain projects need to be modified to ensure synchronicity between the work programme and the MASP-C, and to take into account the new deadlines provided in Article 278 of Regulation (EU) No 952/2013.

| (10) | The measures provided for in this Decision are in accordance with the opinion of the Customs Code Committee, |
| --- | --- |

(10)

The measures provided for in this Decision are in accordance with the opinion of the Customs Code Committee,

HAS ADOPTED THIS DECISION:

Article 1

The work programme

The work programme relating to the development and deployment of the electronic systems provided for in Regulation (EU) No 952/2013 laying down the Union Customs Code (‘the work programme’), as set out in the Annex, is hereby adopted.

Article 2

Implementation

1.   The Commission and the Member States shall cooperate in the implementation of the work programme.

2.   The Member States shall develop and deploy the relevant electronic systems within the dates of the relevant deployment windows laid down in the work programme.

3.   The projects specified in the work programme and the preparation and implementation of the related electronic systems shall be managed in a manner consistent with the work programme and the multi-annual strategic plan for customs.

4.   The Commission shall undertake to seek common understanding and agreement with the Member States on the project scope, design, requirements and architecture of the electronic systems when initiating the projects of the work programme. Where relevant, the Commission shall also consult with and take into account the views of economic operators.

Article 3

Updates

The work programme shall be updated regularly to ensure its alignment with and adjustment to developments in the implementation of Regulation (EU) No 952/2013, and to take account of actual progress in preparing and developing the electronic systems. This applies particularly to the availability of commonly agreed specifications and the practical operational launch of the electronic systems.

Article 4

Communication and reporting

1.   The Commission and the Member States shall share information on planning and on progress in implementing each of the systems.

2.   The Member States shall submit to the Commission national project and migration plans and the table on their progress in developing and deploying the electronic systems referred to in Article 278a(4) of Regulation (EU) No 952/2013 by 31 January and by 30 June each year. The plans and the table shall include the relevant information necessary for the annual report to be submitted by the Commission under Article 278a of Regulation (EU) No 952/2013.

3.   Member States shall inform the Commission immediately of any important updates in their national project and migration plans.

4.   Member States shall make the technical specifications related to the external communication of the national electronic system available to economic operators in a timely manner.

Article 5

Repeal

1.   Implementing Decision (EU) 2016/578 is repealed.

2.   References to the repealed Decision and to Implementing Decision 2014/255/EU shall be construed as references to this Decision.

Article 6

Entry into force

This Decision shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.

Official Journal of the European Union

Done at Brussels, 13 December 2019.

For the Commission

The President

Ursula VON DER LEYEN

---

(1)  
  OJ L 269, 10.10.2013, p. 1.

1

(2)  Commission Implementing Decision 2014/255/EU of 29 April 2014 establishing the Work Programme for the Union Customs Code (OJ L 134, 7.5.2014, p. 46).

2

(3)  Commission Implementing Decision (EU) 2016/578 of 11 April 2016 establishing the Work Programme relating to the development and deployment of the electronic systems provided for in the Union Customs Code (OJ L 99, 15.4.2016, p. 6).

3

(4)  Regulation (EU) 2019/632 of the European Parliament and of the Council of 17 April 2019 amending Regulation (EU) No 952/2013 to prolong the transitional use of means other than the electronic data-processing techniques provided for in the Union Customs Code (OJ L 11, 25.4.2019, p. 54).

4

(5)  https://ec.europa.eu/taxation_customs/general-information-customs/electronic-customs_en#heading_2

5

(6)  Decision No 70/2008/EC of the European Parliament and of the Council of 15 January 2008 on a paperless environment for customs and trade (OJ L 23, 26.1.2008, p. 21).

6

(7)  Commission Delegated Regulation (EU) 2016/341 of 17 December 2015 supplementing Regulation (EU) No 952/2013 of the European Parliament and of the Council as regards transitional rules for certain provisions of the Union Customs Code where the relevant electronic systems are not yet operational and amending Delegated Regulation (EU) 2015/2446, (OJ L 69, 15.3.2016, p. 1).

7

---

ANNEX

Work programme relating to the development and deployment of the electronic systems provided for in the Union Customs Code

I.   INTRODUCTION

| 1. | The work programme provides an instrument to support the application of those provisions of Regulation (EU) No 952/2013 that concern the development and deployment of its electronic systems. |
| --- | --- |

1.

| 2. | The work programme also specifies the periods during which the transitional measures shall apply until the deployment of the new or upgraded electronic systems as referred to in Commission Delegated Regulation (EU) 2015/2446 (1), Delegated Regulation (EU) 2016/341 and Commission Implementing Regulation (EU) 2015/2447 (2). |
| --- | --- |

2.

| 3. | The ‘key milestone’ of the technical specifications shall be understood to mean the date by which a stable version of the technical specifications is made available. For the national systems or components, this date will be communicated as part of the published national project planning. |
| --- | --- |

3.

| 4. | The work programme establishes the following ‘dates of deployment’ for the trans-European and national systems:






  (a) | the start date of the deployment window for the electronic systems, to be understood to mean the earliest date on which the electronic system becomes operational; |
| --- | --- | --- |

4.

(a)

the start date of the deployment window for the electronic systems, to be understood to mean the earliest date on which the electronic system becomes operational;

| (b) | the end date of the deployment window for the electronic systems, to be understood to mean:






  — | the last date by which the systems need to be operational in all Member States and used by all economic operators; and |
| --- | --- | --- |

(b)

the end date of the deployment window for the electronic systems, to be understood to mean:

—

the last date by which the systems need to be operational in all Member States and used by all economic operators; and

| — | the end date of the validity of the transitional measures. |
| --- | --- |

—

the end date of the validity of the transitional measures.

For the purposes of point (b), the date shall be the same as the start date if no actual window is envisaged for migration or deployment.

| 5. | For purely national systems or specific national components of a wider Union project, the Member States may determine the dates of deployment and the start and end dates of a deployment window in their national project planning, subject to the overall deadlines set out in Article 278 of Regulation (EU) No 952/2013.
  The following national systems or specific national components are covered by the first paragraph:






  (a) | UCC Automated Export System (AES) Component 2 (National Export Systems upgrade) (point 10 of Part II); |
| --- | --- | --- |

5.

The following national systems or specific national components are covered by the first paragraph:

(a)

UCC Automated Export System (AES) Component 2 (National Export Systems upgrade) (point 10 of Part II);

| (b) | UCC Special Procedures (SP IMP/SP EXP) (point 12 of Part II); |
| --- | --- |

(b)

UCC Special Procedures (SP IMP/SP EXP) (point 12 of Part II);

| (c) | UCC Arrival Notification, Presentation Notification, Temporary Storage (point 13 of Part II); |
| --- | --- |

(c)

UCC Arrival Notification, Presentation Notification, Temporary Storage (point 13 of Part II);

| (d) | UCC National Import Systems upgrade (point 14 of Part II); |
| --- | --- |

(d)

UCC National Import Systems upgrade (point 14 of Part II);

| (e) | UCC Guarantee Management (GUM) — Component 2 (point 16 of Part II). |
| --- | --- |

(e)

UCC Guarantee Management (GUM) — Component 2 (point 16 of Part II).

| 6. | For trans-European systems with a deployment window but without a single implementation date, the Member States may, where deemed appropriate, start the deployment at an appropriate date within this window and may allow a period of time within which economic operators can migrate. The start and end dates shall be communicated to the Commission. The common domain aspects will need to be carefully considered by the Commission and the Member States.
  The following trans-European systems are covered by the first paragraph:






  (a) | UCC NCTS upgrade (point 9 of Part II); |
| --- | --- | --- |

6.

The following trans-European systems are covered by the first paragraph:

(a)

UCC NCTS upgrade (point 9 of Part II);

| (b) | UCC AES (Component 1) (point 10 of Part II). |
| --- | --- |

(b)

UCC AES (Component 1) (point 10 of Part II).

| (c) | UCC CCI (point 15 of Part II) |
| --- | --- |

(c)

UCC CCI (point 15 of Part II)

The trans-European UCC ICS2 (point 17 of Part II) also requires gradual implementation and transition. The approach in this case is different, however, since all Member States are expected to be ready at the same time for each release at the start of each deployment window. Moreover, where deemed appropriate, Member States may allow the economic operators to gradually connect to the system until the end of the deployment window provided for each of the releases. Member States must publish, in coordination with the Commission, the deadlines and instructions for economic operators on their website.

| 7. | In implementing the work programme, the Commission and the Member States will need to carefully manage complexity in terms of dependencies, variables and assumptions. The principles set out in the MASP-C will be used to manage the planning.
  The projects will be rolled out in different phases, from preparation and development to construction, testing, migration and final operation. The role of the Commission and the Member States in these different phases will depend on the nature and architecture of the system and its components or services, as described in the detailed project fiches of the MASP-C. Where appropriate, common technical specifications will be defined by the Commission in close cooperation with, and subject to review by, the Member States, with a view to finalising them 24 months before the target date of deployment of the electronic system.
  The Member States and the Commission should also ensure that the economic operators have received in a timely manner the technical information needed for them to update their own electronic systems and to connect to the new or upgraded electronic systems provided for in Regulation (EU) No 952/2013. Any changes need to be communicated to the economic operators between 12 and 24 months before deployment of a particular system, if necessary due to the scope and nature of the change, to allow the economic operators to plan and adjust their systems and interfaces. For minor changes, that period may be shorter.
  The Member States and, where appropriate, the Commission will engage in the development and deployment of the systems in line with the defined systems’ architecture and specifications. The activities will be carried out in compliance with the milestones and dates stated in the work programme. The Commission and the Member States will also collaborate with economic operators and other stakeholders.
  The economic operators will have to take the steps necessary to enable them to make use of the systems once in place, and no later than the end dates defined in this work programme or, where applicable, defined by the Member States as part of their national plans. |
| --- | --- |

7.

The projects will be rolled out in different phases, from preparation and development to construction, testing, migration and final operation. The role of the Commission and the Member States in these different phases will depend on the nature and architecture of the system and its components or services, as described in the detailed project fiches of the MASP-C. Where appropriate, common technical specifications will be defined by the Commission in close cooperation with, and subject to review by, the Member States, with a view to finalising them 24 months before the target date of deployment of the electronic system.

The Member States and the Commission should also ensure that the economic operators have received in a timely manner the technical information needed for them to update their own electronic systems and to connect to the new or upgraded electronic systems provided for in Regulation (EU) No 952/2013. Any changes need to be communicated to the economic operators between 12 and 24 months before deployment of a particular system, if necessary due to the scope and nature of the change, to allow the economic operators to plan and adjust their systems and interfaces. For minor changes, that period may be shorter.

The Member States and, where appropriate, the Commission will engage in the development and deployment of the systems in line with the defined systems’ architecture and specifications. The activities will be carried out in compliance with the milestones and dates stated in the work programme. The Commission and the Member States will also collaborate with economic operators and other stakeholders.

The economic operators will have to take the steps necessary to enable them to make use of the systems once in place, and no later than the end dates defined in this work programme or, where applicable, defined by the Member States as part of their national plans.

II.   LIST OF PROJECTS RELATED TO THE DEVELOPMENT AND DEPLOYMENT OF ELECTRONIC SYSTEMS

A.   Full list

| ‘UCC projects and related electronic systems’
  List of projects related to the development and deployment of electronic systems required for the application of the Code | Legal base | Key milestone | Dates of deployment of the electronic systems |
| --- | --- | --- | --- |
| | | | Start date of the deployment window of the electronic system (3) | End date of the deployment window of the electronic system (4) = End date of the transitional period |
| 1.   UCC Registered Exporter System (REX)

  The project aims to make available up-to-date information on registered exporters established in Generalised Scheme of Preference (GSP) countries exporting goods to the Union. The system is trans-European and also includes data about EU economic operators, for the purpose of supporting exports to GSP countries. The required data was inserted into the system in a gradual manner until 31 December 2017. | Article 6(1), Articles 16 and 64 of Regulation (EU) No 952/2013 | Target date of technical specifications
  = Q1 2015 | 1.1.2017 | 1.1.2017 |
| 2.   UCC Binding Tariff Information (BTI)

  The project aims to provide an upgrade of the existing trans-European EBTI-3 system to ensure the following:






  (a) | alignment of the EBTI-3 system with UCC requirements; |

‘UCC projects and related electronic systems’

List of projects related to the development and deployment of electronic systems required for the application of the Code

Legal base

Key milestone

Dates of deployment of the electronic systems

Start date of the deployment window of the electronic system (3)

End date of the deployment window of the electronic system (4) = End date of the transitional period

1.   UCC Registered Exporter System (REX)

The project aims to make available up-to-date information on registered exporters established in Generalised Scheme of Preference (GSP) countries exporting goods to the Union. The system is trans-European and also includes data about EU economic operators, for the purpose of supporting exports to GSP countries. The required data was inserted into the system in a gradual manner until 31 December 2017.

Article 6(1), Articles 16 and 64 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q1 2015

1.1.2017

1.1.2017

2.   UCC Binding Tariff Information (BTI)

The project aims to provide an upgrade of the existing trans-European EBTI-3 system to ensure the following:

(a)

alignment of the EBTI-3 system with UCC requirements;

| (b) | extension of under-surveillance-required declaration data; |
| --- | --- |

(b)

extension of under-surveillance-required declaration data;

| (c) | monitoring of the compulsory BTI usage; |
| --- | --- |

(c)

monitoring of the compulsory BTI usage;

| (d) | monitoring and management of BTI extended usage. |
| --- | --- |

(d)

monitoring and management of BTI extended usage.

The project is implemented in two phases.

The first phase (step 1) provides functionality to gradually receive the UCC-required declaration dataset from 1 March 2017 until the implementation of the projects listed in points 10 (by 1 December 2023 at the latest) and 14 (by 31 December 2022 at the latest). Step 2 fulfils the BTI usage control obligation on the basis of the newly required declaration dataset and the alignment with the customs decisions process.

The second phase implements the electronic form of the BTI application and decision, and provides economic operators with a harmonised trader interface to submit the BTI application and receive the BTI decision electronically.

Article 6(1), Articles 16, 22, 23, 26, 27, 28, 33 and 34 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q2 2016

(phase 1)

1.3.2017

(phase 1 — step 1)

1.3.2017

(phase 1 — step 1)

2.10.2017

(phase 1 — step 2)

2.10.2017

(phase 1 — step 2)

Target date of technical specifications

= Q2 2018

(phase 2)

1.10.2019

(phase 2)

1.10.2019

(phase 2)

3.   UCC Customs Decisions

The project aims to harmonise the processes for applications for a customs decision, decision-making and decision management through standardisation and electronic management of application and decision/authorisation data across the Union. The project relates to national and multi-Member State decisions defined by the Code, and covers system components developed centrally at Union level and integration with national components where Member States opt for these. This trans-European system facilitates consultation during the decision-making process and the management of the authorisation process.

Article 6(1), Articles 16, 22, 23, 26, 27 and 28 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q4 2015

2.10.2017

2.10.2017

4.   Direct trader access to the European Information Systems (Uniform User Management & Digital Signature)

The goal of this project is to provide working solutions for direct and harmonised trader access as a service for user-to-system interfaces, to be integrated into the electronic customs systems as defined in the specific UCC projects. The Uniform User Management and Digital Signature will be integrated into the portals of the systems concerned, and includes support for identity, access and user management compliant with the necessary security policies.

The first deployment took place alongside the UCC Customs Decisions system.

This technical authentication and user management solution will subsequently be made available for use in other UCC projects such as the UCC Binding Tariff Information (BTI), UCC Authorised Economic Operators (AEO) upgrade, UCC Proof of Union Status (PoUS) and the UCC Information Sheets (INF) for Special Procedures. See the different projects for the dates of deployment.

Article 6(1) and Article 16 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q4 2015

2.10.2017

2.10.2017

5.   UCC Authorised Economic Operators (AEO) upgrade

The project aims to improve the business processes related to AEO applications and authorisations, taking into account changes to the legal provisions of the UCC.

In the first phase, the project aims to implement major improvements to the AEO system as part of the harmonisation of the customs decision-making procedure.

In the second phase, the project implements the electronic form of the AEO application and decision, and provide economic operators with a harmonised interface to submit the AEO application and receive the AEO decision electronically. The upgraded system is deployed in two releases: part 1 for the submission of the AEO application and the decision-making process, and part 2 for the other subsequent processes.

Article 6(1), Articles 16, 22, 23, 26, 27, 28, 38 and 39 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q1 2016

5.3.2018

(phase 1)

5.3.2018

(phase 1)

Target date of technical specifications

= Q4 2018

1.10.2019

(phase 2 — part 1 initial processes)

16.12.2019

(phase 2 — part 2 other processes)

1.10.2019

(phase 2 — part 1)

16.12.2019

(phase 2 — part 2)

6.   UCC Economic Operator Registration and Identification System upgrade (EORI 2)

This project aims to provide a minor upgrade of the existing trans-European EORI system that enables the registration and identification of Union and third-country economic operators and persons other than economic operators that are active in customs matters in the Union.

Article 6(1) and Article 9 of Regulation (EU) No 952/2013 laying down the Union Customs Code

Target date of technical specifications

= Q2 2016

5.3.2018

5.3.2018

7.   UCC Surveillance 3

This project aims to provide an upgrade of the Surveillance 2+ system to ensure its alignment with UCC requirements such as the standard exchange of information via electronic data processing techniques and the establishment of the functionalities needed for processing and analysing the full surveillance dataset obtained from Member States.

It includes further data mining capabilities and reporting functionalities, therefore, which will be made available to the Commission and Member States.

Full implementation of this project is dependent on the projects listed in points 10 (by 1 December 2023 at the latest) and 14 (by 31 December 2022 at the latest). The date of deployment of this system has to be defined by the Member States as part of their national plans.

Article 6(1), Articles 16 and 56(5) of Regulation (EU) No 952/2013

Target date of technical specifications

= Q3 2016

1.10.2018

1.10.2018

8.   UCC Proof of Union Status (PoUS)

The project aims to create a new trans-European system to store, manage and retrieve the Proofs of Union Status T2L/F and the customs goods manifest (issued by a non-authorised issuer).

As implementation of the customs goods manifest is to be linked to the European Maritime Single Window, this part of the project will be covered under a separate phase.

Article 6(1), Articles 16 and 153 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q1 2022

1.3.2024

(phase 1)

2.6.2025

(phase 2)

1.3.2024

(phase 1)

2.6.2025

(phase 2)

9.   UCC New Computerised Transit System (NCTS) upgrade

The aim of this project is to align the existing trans-European NCTS system with the new UCC.

Component 1—‘NCTS Phase 5’: the aim of this phase is to align the NCTS system with the new UCC requirements except in safety and security data elements in transit customs declarations of goods brought into the customs territory of the Union.

It covers the registration of ‘en route’ events and the alignment of information exchanges with UCC data requirements, and the upgrade and development of interfaces with other systems.

Component 2—‘NCTS Phase 6’: the aim of this phase is to implement the specific new requirements for safety and security data elements in transit customs declarations of goods brought into the customs territory of the Union resulting from project 17 (UCC ICS2). The scope and implementation solution will be agreed during the project initiation phase.

Article 6(1), Articles 16 and 226-236 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q4 2019

Target date of technical specifications

= Q2 2022

1.3.2021

3.6.2024

1.12.2023

2.6.2025

10.   UCC Automated Export System (AES)

This project aims to implement the UCC requirements for export and exit.

Component 1 —‘Trans-European AES’. The aim of the project is to further develop the existing trans-European Export Control System in order to implement a full AES that will cover the business requirements for processes and data brought about by the UCC, including the coverage of simplified procedures and centralised clearance for export. It is also intended to cover the development of harmonised interfaces with the Excise Movement System (EMCS) and NCTS. As such, the AES will enable the full automation of export procedures and exit formalities. The AES covers parts to be developed centrally and nationally, including the national components in which the export declaration is lodged and processed and which enable the subsequent exchange of information with the customs office of exit via the common components of the AES.

Component 2 —‘National Export Systems upgrade’. In a process outside the scope of the AES but closely linked, separate national systems are to be upgraded for specific national elements related to export and/or exit formalities. Where these elements do not impact on the common domain for AES, they can be covered under this component.

Article 6(1), Articles 16, 179 and 263-276 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q4 2019

(component 1)

1.3.2021

(component 1)

1.12.2023

(component 1)

Target date of technical specifications

= to be defined by MS

(component 2)

1.3.2021

(component 2)

1.12.2023

(component 2)

11.   UCC Information Sheets (INF) for Special Procedures

The aim of this project is to develop a new trans-European system to support and streamline the INF data management processes and the electronic handling of INF data in the Special Procedures domain.

Article 6(1), Articles 16, 215, 255-262 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q2 2018

1.6.2020

1.6.2020

12.   UCC Special Procedures

This project aims to accelerate, facilitate and harmonise Special Procedures across the Union by providing common business process models. The national systems will implement all UCC changes required for customs warehousing, end-use, temporary admission, inward and outward processing.

This project will be implemented in two parts.

Component 1 —‘National SP EXP’. Provides the required national electronic solutions for export-related special procedures activities.

Component 2 —‘National SP IMP’. Provides the required national electronic solutions for import-related special procedures activities.

Implementation of these projects will take place through the projects listed in points 10 and 14.

Article 6(1), Articles 16, 215, 237-242 and 250-262 of Regulation (EU) No 952/2013

Target date of technical specifications

= to be defined by MS (for component 1 and 2)

1.3.2021

(component 1)

1.12.2023

(component 1)

To be defined by MS as part of the national plan

(component 2)

To be defined by MS as part of the national plan with a deployment window till 31.12.2022

(component 2)

13.   UCC Notification of Arrival, Presentation Notification and Temporary Storage

The goal of this project is to define the processes for Notification of Arrival of the means of transport, Presentation of the goods (Presentation Notification) and Declaration for Temporary Storage as described in the UCC and to support harmonisation in this respect across the Member States as regards the data exchange between trade and customs.

The project covers the automation of processes at national level.

Article 6(1), Articles 16 and 133-152 of Regulation (EU) No 952/2013

Target date of technical specifications

= to be defined by MS and for Notification of Arrival in line with ICS2 planning.

To be defined by MS as part of the national plan

To be defined by MS as part of the national plan with a deployment window till 31.12.2022

14.   UCC National Import Systems upgrade

The project aims to implement all process and data requirements deriving from the UCC which relate to the import domain (and which are not covered by one of the other projects defined in the work programme). It relates mainly to the changes in the ‘Release for free circulation’ procedure (standard procedure + simplifications), but also covers the impact arising from other system migrations. This project relates to the national import domain covering national customs declaration processing systems as well as other systems such as national accountancy and payment systems.

Article 6(1), Article 16(1) and Articles 53, 56, 77-80, 83-87, 101-105, 108-109, 158-187, 194-195 of Regulation (EU) No 952/2013

Target date of technical specifications

= to be defined by MS

To be defined by MS as part of the national plan

To be defined by MS as part of the national plan with a deployment window till 31.12.2022

15.   UCC Centralised Clearance for Import (CCI)

This project aims to allow goods to be placed under a customs procedure using centralised clearance, allowing economic operators to centralise their business from a customs viewpoint. The processing of the customs declaration and the physical release of the goods should be coordinated between the related customs offices. It concerns a trans-European system containing components developed centrally and nationally.

The project will be implemented in two phases.

Phase 1: this phase will cover the combination of centralised clearance with standard customs declarations and with simplified customs declarations and the respective supplementary declarations (regularising one simplified customs declaration). In addition it will cover the placing of goods under the following customs procedures: release for free circulation, customs warehousing, inward processing and end-use. Finally, for the type of goods this phase will cover all types of goods with the exception of excise goods and goods subject to common agricultural policy measures.

Phase 2: this phase will cover everything that is not covered by phase 1, namely the combination of centralised clearance with customs declarations through an entry in the declarant’s records and the respective supplementary declarations, supplementary declarations regularising more than one simplified customs declaration, the placing of goods under the temporary admission procedure, and excise goods and goods subject to common agricultural policy measures.

Article 6(1), Articles 16 and 179 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q3 2020

Target date of technical specifications

= Q2 2022

1.3.2022

2.10.2023

1.12.2023

2.6.2025

16.   UCC Guarantee Management (GUM)

This project aims to ensure the effective and efficient management of the different types of guarantees.

Component 1 —‘GUM’: The trans-European system will cover the management of the comprehensive guarantees that may be used in more than one Member State, and the monitoring of the reference amount for each customs declaration, supplementary declaration or appropriate information on the particulars needed for the entry in the accounts of existing customs debts for all customs procedures as provided for in the Union Customs Code, except Transit, which is handled as part of the NCTS project.

Component 2 —‘National Guarantee Management’: In addition, the electronic systems existing at national level to manage the guarantees valid in one Member State are to be upgraded.

Article 6(1), Articles 16 and 89-100 of Regulation (EU) No 952/2013

Target date of technical specifications

= Q3 2022

(component 1)

2.10.2023

(component 1)

2.6.2025

(component 1)

Target date of technical specifications

= to be defined by MS

(component 2)

To be defined by MS as part of the national plan

(component 2)

To be defined by MS as part of the national plan with a deployment window till 2.6.2025

(component 2)

17.   UCC Import Control System 2 (ICS2)

The aim of this programme is to strengthen pre-arrival safety and security of goods entering the Union by implementing the new UCC requirements regarding the lodging and treatment of entry summary declarations (ENS), namely the provision of ENS data in more than one submission and/or by different persons and the exchange of that data and the risk analysis results among the customs authorities. The ICS2 will lead to a complete new architecture and phased replacement of the existing trans-European ICS system.

The programme will be implemented in three releases.

Release 1: as a first phase, this release will cover the obligation on the relevant economic operators (postal operators and express carriers in air transport) to provide the minimum data, i.e. ENS pre-loading dataset.

Release 2: as a second phase, this release will cover the implementation of complete new ENS obligations, related business and risk management processes for all the goods in air traffic.

Release 3: as a third phase, this release will cover the implementation of complete new ENS obligations, related business and risk management processes for all goods in maritime and inland waterways and road and rail traffic (this includes goods in postal consignments transported in these means of transport).

Article 6(1), Articles 16, 46, 47, and 127-132 of Regulation (EU) No 952/2013

Target date of technical specifications for all three Releases

= Q2 2018

15.3.2021

(Release 1)

1.10.2021

(Release 1)

1.3.2023

(Release 2)

1.3.2024

(Release 3)

2.10.2023

(Release 2)

1.10.2024

(Release 3)

B.   Overview of the list

| UCC Projects related to electronic systems | Dates of deployment/
  Deployment windows | 2017 | 2018 | 2019 | 2020 | 2021 | 2022 | 2023 | 2024 | 2025 |
| --- | --- | --- | --- | --- | --- | --- | --- | --- | --- | --- |
| 1. | UCC Registered Exporter System (REX) |

UCC Projects related to electronic systems

Dates of deployment/

Deployment windows

2017

2018

2019

2020

2021

2022

2023

2024

2025

1.

UCC Registered Exporter System (REX)

1.1.2017

X

| 2. | UCC Binding Tariff Information System (BTI) |
| --- | --- |

2.

UCC Binding Tariff Information System (BTI)

1.3.2017

(phase 1 — step 1)

2.10.2017

(phase 1 — step 2)

1.10.2019

(phase 2)

X

X

X

| 3. | UCC Customs Decisions |
| --- | --- |

3.

UCC Customs Decisions

2.10.2017

X

| 4. | Direct trader access to European Information Systems (Uniform user management & digital signature) |
| --- | --- |

4.

Direct trader access to European Information Systems (Uniform user management & digital signature)

2.10.2017

X

| 5. | UCC Authorised Economic Operators System (AEO) upgrade |
| --- | --- |

5.

UCC Authorised Economic Operators System (AEO) upgrade

1.3.2018

(phase 1)

1.10.2019

(phase 2 — part 1)

16.12.2019

(phase 2 — part 2)

X

X

X

| 6. | UCC Economic Operator Registration and Identification System upgrade |
| --- | --- |

6.

UCC Economic Operator Registration and Identification System upgrade

(EORI 2)

1.3.2018

X

| 7. | UCC Surveillance 3 |
| --- | --- |

7.

UCC Surveillance 3

1.10.2018

X

| 8. | UCC Proof of Union Status (PoUS) |
| --- | --- |

8.

UCC Proof of Union Status (PoUS)

1.3.2024

(phase 1)

2.06.2025

(phase 2)

X

X

| 9. | UCC New Computerised Transit System (NCTS) upgrade |
| --- | --- |

9.

UCC New Computerised Transit System (NCTS) upgrade

1.3.2021-1.12.2023 (phase 5)

3.6.2024-2.6.2025 (phase 6)

X

X

X

X

X

| 10. | UCC Automated Export System (AES) — |
| --- | --- |

10.

UCC Automated Export System (AES) —

Component 1: Trans-European AES

1.3.2021-1.12.2023

X

X

X

| 10. | UCC Automated Export System (AES) — |
| --- | --- |

10.

UCC Automated Export System (AES) —

Component 2: National Export Systems upgrade

1.3.2021-1.12.2023

X

X

X

| 11. | UCC Information Sheets (INF) for Special Procedures |
| --- | --- |

11.

UCC Information Sheets (INF) for Special Procedures

1.6.2020

X

| 12. | UCC Special Procedures — |
| --- | --- |

12.

UCC Special Procedures —

Component 1: National SP EXP

national planning

1.3.2021-1.12.2023— see also project 10

X

X

X

X

X

X

X

| 12. | UCC Special Procedures — |
| --- | --- |

12.

UCC Special Procedures —

Component 2: National SP IMP

national planning for SP IMP

(till 31.12.2022) — see also project 14

X

X

X

X

X

X

| 13. | UCC Notification of arrival, presentation notification and temporary storage |
| --- | --- |

13.

UCC Notification of arrival, presentation notification and temporary storage

national planning

(till 31.12.2022)

X

X

X

X

X

X

| 14. | UCC National Import Systems upgrade |
| --- | --- |

14.

UCC National Import Systems upgrade

national planning

(till 31.12.2022)

X

X

X

X

X

X

| 15. | UCC Centralised Clearance for Import (CCI) |
| --- | --- |

15.

UCC Centralised Clearance for Import (CCI)

1.3.2022-1.12.2023 (phase 1)

2.10.2023-2.6.2025 (phase 2)

X

X

X

X

X

| 16. | UCC Guarantee Management (GUM) — |
| --- | --- |

16.

UCC Guarantee Management (GUM) —

Component 1: Trans-European GUM

2.10.2023-2.6.2025

X

X

X

| 16. | UCC Guarantee Management System (GUM) — |
| --- | --- |

16.

UCC Guarantee Management System (GUM) —

Component 2: National Guarantee Management

national planning

(till 2.6.2025)

X

X

X

X

X

X

X

X

X

| 17. | UCC Import Control System |
| --- | --- |

17.

UCC Import Control System

(ICS 2)

15.3.2021-1.10.2021

(Release 1)

1.3.2023-2.10.2023

(Release 2)

1.3.2024-1.10.2024

(Release 3)

X

X

X

---

(1)  Commission Delegated Regulation (EU) 2015/2446 of 28 July 2015 supplementing Regulation (EU) No 952/2013 of the European Parliament and of the Council as regards detailed rules concerning certain provisions of the Union Customs Code (OJ L 343, 29.12.2015, p. 1).

(2)  Commission Implementing Regulation (EU) 2015/2447 of 24 November 2015 laying down detailed rules for implementing certain provisions of Regulation (EU) No 952/2013 of the European Parliament and of the Council laying down the Union Customs Code (OJ L 343, 29.12.2015, p. 558).

(3)  This date for starting the deployment window of the electronic systems is the earliest date for Member States to start operations.

(4)  This date for ending the deployment window of the electronic systems is the last date by which the system should be fully deployed and the last date by which all economic operators should be migrated; where applicable, the date will be established by the Member States and is the end date of the validity of the transitional period.

---