The final implementation date of the new Temporary Storage Declaration (ATO) / TSD is 16 November 2026. No later than this moment, you must submit the ATO in two ways:
- TSD message with master and house data;
- TSD message with master data only.
See here the communication from Dutch Customs about this legal change.
Recording of the information session
The most important changes were explained by Dutch Customs and Portbase in an information session. You can find it here:
Please note: this session refers to the old deadline; the correct deadline is 16 November 2026. See here the answers to the frequently asked questions during and after this session.
Planning for customers with system interface
Before go-live, successful testing must have taken place in the test environment, followed by a successful pilot in production. Only then can there be a go-live. There is no time to wait; action is necessary!
It is crucial that you no later than 1 November:
- Complete successful tests in the Portbase test environment;
- Have moved all adjustments to production
If this is not completed before 1 November, we cannot guarantee a timely go-live.
Planning for customers with web screens
We will agree the exact date for switching to the new web screens of Cargo Declaration Import in mutual consultation.
From 16 November 2026 at 12.00, you must enter all mandatory data.
Mandatory data for the TSD message
The following data must be reported:
| Mandatory to include in the TSD message | ENS via Portbase? | No ENS via Portbase? |
|---|---|---|
| Type consignment (704/705), (must be the same as reported in the ENS) |
No action required. Portbase includes the reported document type in the TSD. |
Action required. You must send this data to Portbase so we can process it in the TSD. A change to the IFTMCS message specifications or a switch to API* is required. |
| HS code (with six digits instead of the current four digits) |
No action required. Do send the six-digit code. Send the six-digit HS code with the ENS. We will take this over in the TSD. |
Action required. You must send this six-digit code to Portbase so we can process it in the TSD. A change to the IFTMCS message specifications or a switch to API* is required. |
| RTO number (ferry & containers) |
No action required. Portbase is aware of the RTO number of ferry and container terminals. We process this in the TSD. |
No action required. Portbase is aware of the RTO number of ferry and container terminals. We process this in the TSD. |
| Customs warehouse authorisation number (bulk) |
Action required. This number is not known to Portbase. We also do not receive it from Dutch Customs. |
Action required. This number is not known to Portbase. We also do not receive it from Dutch Customs. |
| Notify party may be stated, including telephone or email |
Is the consignee known? Then you are not obliged to report the notify party.
Do you decide to do so anyway? Then you are obliged to also state an email address or telephone number of the notify party.
|
Is the consignee known? Then you are not obliged to report the notify party.
Do you decide to do so anyway? Then you are obliged to also state an email address or telephone number of the notify party.
|
*Do you want to send a TSD message with master and house data ?
Portbase facilitates this with an API connection. Please contact sales for more information.
Do you want to send a TSD message with master data only? Switch to the new IFTMCS message specifications or choose a connection via API.
The aforementioned TSR message (Temporary Storage Reuse) is not being introduced by Dutch Customs.
New way of working
Dutch Customs preferably receives the master and house data. Therefore, the following applies:
• When we receive the master and house data for the ENS (and the cargo is discharged in the Netherlands), we send a TSD message with master and house data to Dutch Customs.
• When we receive only the master data for the ENS, we send a TSD message with master data.
• Only reporting a TSD and no ENS precedes it? Dutch Customs preferably receives the master and house data. We would like to receive this data so that we can send a TSD message with master and house data to Dutch Customs.
• The TSD message is sent per Bill of Lading (and no longer grouped per manifest/loading port). Dutch Customs wants to receive this message in this way; therefore, the status is also returned at Bill of Lading level.
Related articles
Part of