NCTS still does what it has always done: it tracks goods moving under the transit procedure from the office of departure to the office of destination. Each declaration receives an MRN, enabling customs authorities to follow the movement in real time. What changes in NCTS6 are the system’s posture. Instead of acting mainly as a record of events, it becomes an active layer for control and risk analysis.
In day-to-day terms, transit stops are no longer treated as a purely “technical logistics procedure” and start functioning as part of supply-chain security oversight.
Security data moves out of NCTS: less flexibility, more specialisation.
One of the biggest shifts in NCTS6 is a clean-up of how security data is handled. Previously, the system allowed multiple ways to report it, which often led to inconsistent submissions and avoidable mistakes. The new version removes that freedom, effectively leaving only two routes: no security data at all, or a reference to an EXS declaration. Other options, including ENS data, have been removed from NCTS entirely.
This is not a “user-friendly simplification”. It reflects a deeper redesign of customs’ IT architecture. Import security data has been shifted into the dedicated ICS2 system, which is responsible for risk analysis before goods even arrive in the European Union customs territory.
As a result:
- NCTS no longer combines transit and security functions,
- each system now has a clearly defined purpose,
- consistent, on-time data exchange between systems becomes critical.
That shift has major operational consequences: data synchronisation errors will no longer be “harmless”. They can lead to goods being stopped before they are even dispatched.
Real-time incidents: the end of “after-the-fact” reporting
The second major pillar of NCTS6 is a fundamentally different approach to incidents during a transit movement.
Until now, the market often operated with a lot of leeway: incidents were frequently reported after the transport was completed, and their impact was largely limited to correcting paperwork.
NCTS6 flips that logic. An incident is no longer treated as a “historical note”. It becomes an event that triggers an immediate system response and requires action while the operation is still ongoing.
The update includes, among other things:
- the ability for the competent customs office to register an incident during the transit operation,
- the removal of incident markings in system messages,
- no option to report an incident after the procedure has been completed.
In practice, this means the driver or carrier must act immediately—report the situation to the nearest customs office and ensure it is formally recorded.
Importantly, the incident list is broad. It covers not only obvious events such as theft or an accident, but also operational situations like a route change, broken seals, or data discrepancies. In other words, an incident is no longer just a logistics headache—it can carry legal and financial consequences.
What this means for businesses: process redesign and risk ownership
NCTS6 forces companies involved in transit to rethink how they operate in real terms—not just update forms.
First, operational procedures need updating, especially instructions for drivers and carriers. Rapid-response routines become essential, and the habit of documenting incidents only once the job is done has to disappear.
Second, IT systems are affected. Businesses must support the new security codes, enable integration with ICS2, and validate data properly before a declaration is submitted.
Third, accountability increases. The party responsible for a transit procedure can no longer rely solely on documents. It must actively manage risk, control the flow of information, and ensure the movement meets system requirements.
In practical terms, that raises the bar for due diligence and brings a higher risk of penalties when errors or omissions occur. tachograph
Wrap-up: transit under continuous oversight
NCTS6 sets a new baseline for transit: full digital handling, immediate incident response, and tighter links to security systems. Security screening is pushed earlier in the process (via ICS2), incidents must be reported in real time, and the system leaves little room for formal mistakes.
For businesses, the perspective changes accordingly. Transit is no longer just a logistics operation—it becomes a process that demands continuous oversight, active risk management, and an informed understanding of legal responsibility. inspections
About the author
Dr Izabella Tymińska, customs law expert, specialising in customs and foreign trade. She provides advisory services on customs regulations, the import and export of goods and services, and the financial and economic analysis of international contracts. She focuses on complex, non-standard cases and previously worked for many years at a Customs Office. She also spent years in logistics and forwarding companies, including in a management board role. She lectures at the War Studies University in Warsaw, within the Institute of Logistics (Faculty of Management and Command). She has also taught at ALMAMER University in Warsaw, the Higher School of Customs and Logistics, and the Technical and Commercial University. She is a graduate in Economics, Logistics, International Relations, Management, and Defence Economics.
