NCTSP5
Current Situation
NCTS5 ACC is currently open for testing for all software providers.
They can align with the Economic Operators (EO) who have completed the registration process and were able to register their callback address when to start the testing phase.
There are still some technical incidents, mostly situated in these domains:
* Write off/link with other applications (AES, IDMS, ...)
* Data transfer between customs offices (departure, destination, ...)
Apart from those there are still several general cross-application and legal topics to be covered.
Concerning the emergency procedure a proposition was done and is currently at BE Customs side for the approval and publication.
More detailed information can be found in the FAQ below
Frequently asked questions
If your softwareprovider is doing the registration for you, you can contact them for further follow up. they will be the ones who can provide you the details concerning the callback as well. If you have to take care of the registration process yourself you can mail it to :
CRSNP is in continuous contact with BE Customs. New dates are published here: https://www.naforna.be/nl/nieuws/19112024-masp-ncts-p5
Mind that for NCTSP5 09/12/2024 for now is a BIG bang - the date till 21/01/2025 simply means that you can keep sending in messages into NCTSP4 to close the old messages that started in NCTSP4.
update 26/11/2024
The MIG is published on https://financien.belgium.be/sites/default/files/Customs/Ondernemingen/Applicaties/technische-documentatie/NCTS/NCTS%20DEV%20Message%20implementation%20guide%20v0.1.9.docx
This document contains a description of all the messages that will be send to and from the customs authorities.
In this document several other documents are embedded e.g.:
- Data mapping NCTS4 vs. NCTS5
- XSD files
- Excel files with rules and conditions
- Link to code lists
- Instructions for the follow letter
The code lists can be downloaded from the website of the EU: https://ec.europa.eu/taxation_customs/dds2/rd/rd_download_home.jsp?Lang=en
Choose "NCTS5" as domain in the dropdownbox and download the XML file
There are also some national code lists: the are published on https://financien.belgium.be/nl/douane_accijnzen/ondernemingen/applicaties-da/technische-documentatie-0/ncts/ncts-p5 -> the lists are at the very bottom of the page
The first step is onboarding Access Managers This can be done by informing the helpdesk on who is responsible for your company, by providing them the following information:
Name
Company
BCE # CBE (Crossroads Bank for Enterprises) / CBE (Crossroads Bank for Enterprises) / BCE (Banque Carrefour des Entreprises) / KBO number of the company
National Register #
With this information the helpdesk can add those users so called (Access Manager) to be registered in the IAM system and are will then be able to activate their first registration with their ID.
once this is done - or if your company already has an access manager - you can move on with the next steps:
Next step Role assignment :
The access manager is now able to assign the role "FPS FIN Customs & Excise Internal Company Designation" property "Customs formalities" to the end-user(s): TEST: https://iamapps.int.belgium.be/rma
PROD: https://iamapps.belgium.be/rma
The onboarding process can proceed. For Belgian users, it's important to note that they all potentially exist, as all Belgians have access to CSAM through their EID, regardless of the environment. FEDIAM takes the info from CSAM/BOSA.
The access manager is required to follow below procedure when assigning roles to end-users.
NL: https://www.loginhulp.be/44.php
FR: https://www.aideacces.be/44.php
IMPORTANT: for the first connection to the TEST (INT / ACC) environment, it is mandatory that users (access manager and end-user) use their electronic identity card (EID) to connect otherwise it risks creating a corrupt profile. In such cases, please submit a ServiceNow ticket to the helpdesk or send an email to servicedesk.dto@bosa.fgov.be to ask them to reset their TEST profile.
Please be aware that all actions related to the individuals mentioned concerns to the TEST environment. Consequently, when accessing PROD, certain steps will need to be repeated. However, most companies typically already have Access Manager Role set up in PROD, so this aspect will not require duplication. Nevertheless, the role assignment by the access manager to the end-user(s) will need to be performed again, but this time in the PROD environment.
Finally Access to NCTSP5 web: if everything is set up, the EO can connect to the AES web application shown below.
ACC: https://nctsp5.acc.minfin.be/
PROD: not yet available
The transition period starts from the moment that NCTS5 is going live in production in BE and runs until the last EU member state has made the switch to NCTSP5.
Currently this date is technically set to 02/01/2025 (however this can be shifted depending on the readiness of other member states).
Reason is that till that time we have to stick to certain rules that apply to the country with the lowest settings.
for example your description of goods will be shortened to a specific number of digits, until the transistion period is finished because one of the member states can only receive this limited number.
Once everyone is transferred the number of digits will be extended to what is agreed EU wide.
Same applies to certain documents that have to be mentioned on item level during transition phase and on shipment level after transition period.
For NCTS5 only location type C (approved location) in combination with identification type U (= UN Locode) can be used. In data element unlocode you have to mention the location code.
Attention: the data element unlocode needs to contain the full location code known by the customs authorities. This is not a "real" 5-digit unlocode. You have to use the sames location codes as used in NCTS 4 e.g. location code for approved location, rto, ...
You have send out an NCTS Declaration but did not receive a reply.
Step 1 : Did you receive a correlation ID?
if yes this means your message was received by customs. > go to the next step
if no, this means your message did not reach BE customs, please check your credentials and your communication.
Step 2: You did not receive any functional message:
if you did not receive any of those you can try receiving the last message via the pulling mechanisme.
if this works it means there might be something wrong with your callback registration /set-up to receive answers automatically. (you can check this via the self-service portal, check the registration and on-boarding topic)
Step 3: Did you receive any functional message via callback or pulling mechanism.
in case you received a technical or functional error: solve the error and resend your export declaration.
if you do not manage to identify where it went wrong gather the following information:
- correlation ID
- MRN / LRN
- date and time of the sending
as a CRNSP member you can forward this to Peggy Cole (pc@organi.be)
non-CRSNP members forward this to NCTS helpdesk (ncts.helpdesk@minfin.fed.be)
Your Contactperson
Peggy Cole
