Union Customs Code: overview & planning of new declaration systems for the Belgian customs sector
The UCC (Union Customs Code), has been in force since 01/05/2016. The revision of the customs code is one of the actions within the framework of the modernization plan of the European Customs Union. It is a comprehensive framework for customs procedures and rules adapted to modern trade realities and modern communication tools.
To fulfill all customs formalities described in the UCC, the European Union and its member states musupgrade existing electronic systems and introduce new ones. For Belgium, this means, among other things:
The EU Customs Data Model (EUCDM) forms the basis for the Trans-European and national declaration systems in the European Union. The new systems IDMS, AES, NCTS F5, PN-TS, etc. will utilize the dataset defined in Annex B of the UCC. An overview of these datasets can also be found on the customs website.
19/06 start transition AES
26/06 start transition IDMS
26/07 end transition TS (air)
30/09 end transition AES
30/09 end transition PN + TS (maritime) break bulk, RoRo & ferry
30/11 end transition IDMS
30/11 end transition PN + TS (maritime) container
02/12 start transition NCTS F5
31/12 end transition PN + TS (maritime) bulk
21/01 end transition NCTS F5
On the customs website, you will find the complete schedule of all projects.
IDMS (Import Declaration Management System)Â replaces the current PLDA system for import declarations. In the future, declarations such as those to release goods into free circulation (H1) or to place them in customs warehousing (H2) will be submitted through this system.
In addition to the changes in the message structure, there are also substantive/operational changes. For example, only one customs procedure can be specified per import declaration. Incoterms are no longer expected at item level but at shipment level. There are new parties such as Importer and Representative, etc.
Yes, there is an IDMS test environment at Customs. We are quietly also preparing to roll out test environments within the client base.
Yes, we foresee 2 versions. A reviewed version with which we try to limit the changes compared to the current integration XML. In addition, a new standard will also be developed which, in the long term, will be the version with which orders must be delivered. Both versions will be available for use with Go-live IDMS. These new specifications are not yet available because we cannot yet fully validate our developments on the current IDMS test environment.
The IDMS declarations are based on the dataset defined in Annex B of the UCC legislation. Here you can check which data elements are expected for each type of declaration. An overview of these datasets can also be found on the customs website.
We are still waiting for feedback from customs here. There will be a transition period but exactly how it will work is not yet entirely clear.
AES (Automated Export System) replaces the current PLDA system for export declarations. Export declarations such as definitive export or re-export will soon have to be submitted through this system.
New messages will come into use, based on the EUCDM. However, these are not just technical changes. There will also be changes in content. Incoterms are no longer expected at item level but at shipment level. There are new parties such as the Exporter and the Representative. Etc.
Yes, there is an AES test environment at Customs. We are quietly also preparing to roll out test environments within the client base.
Yes, we foresee 2 versions. A reviewed version with which we try to limit the changes compared to the current integration XML. In addition, a new standard will also be developed which, in the long term, will be the version with which orders must be delivered. Both versions will be available for use at Go-live IDMS. The specifications can be requested by sending an e-mail to SWH@organi.be.
The AES declarations are based on the dataset defined in Annex B of the UCC legislation. Here you can check which data elements are expected for each type of declaration. An overview of these datasets can also be found on the customs website.
We are still waiting for feedback from customs here. There will be a transition period but exactly how it will work is not yet entirely clear.
PNTS replaces the current goods accountability system GCA, GCB…
The application consists of multiple components:
The goods accountability is also a component of the PNTS application. It is the application responsible for terminating the temporary storage regime when goods are placed under a customs procedure or re-exported. The application keeps track of goods in temporary storage and writes off the goods that are placed under a different regime by combining the data from TSD with that of other declaration components.
New messages will be introduced, based on the EUCDM. Besides the IT technical changes, there are also substantive adjustments as well as modifications in the operational flow. We are currently focusing on the transfer and deconsolidation message. These will initially be implemented in air freight.
Also, our partner Crossroad Communications is working on developing a solution related to PNTS. They will also be sending the PN and TSD messages in addition to the transfer and deconsolidation messages. So depending on what you as a customer need, you can always turn to us and/or our colleagues at Crossroad Communications.
For the maritime sector, Alfaport Voka and Nxtport are developing a platform called the Inbound Release Platform.
Yes, there is a test environment available for us. Once testing can proceed smoothly in the test environment and we have completed our developments, we will inform you accordingly.
A transition period is provided for. The transition will follow the Big Bang principle, but not all economic operators will switch at the same time.
NCTS Phase 5 replaces the current NCTS system. When the new system is implemented, we will say goodbye to the EDIFACT messages and switch to XML messages.
In addition to the technical changes (message type and message structure), there are also substantive changes. For example, a 6-digit HS code will be required in all NCTS declarations.
An NCTS-F5 test environment is available and basic testing is possible. Basic testing is possible, but testing is currently limited to testing fixed scenarios with predefined CN codes and EORI numbers. As soon as smooth testing is possible on the test environment and we are ready with our developments we will inform you.
Yes, we foresee 2 versions. A reviewed version with which we try to limit the changes compared to the current integration XML. In addition, a new standard will also be developed which, in the long term, will be the version with which orders must be delivered. Both versions will be available for use with Go-live IDMS. These new specifications are not yet available because we cannot yet fully validate our developments on the current IDMS test environment.
The NCTS declarations are based on the dataset defined in Annex B of the UCC legislation. Here you can check which data elements are expected for each type of declaration. An overview of these datasets can also be found on the customs website.
We are still waiting for feedback from customs here. There will be a transition period but exactly how it will work is not yet entirely clear.
Leave your details and we will contact you as soon as possible.
"*" indicates required fields
Organi is a part of the 4TheFuture Group.
