The final implementation date for the new Temporary Storage Declaration (ATO) / TSD is 16 November 2026. As of no later than this date, you must submit the TSD in two ways:
- TSD message with master and house data;
- TSD message with master data only.
See here Dutch Customs’ communication about this legal change.
Recording of the information session on 21 May 2026
The key changes were explained by Dutch Customs and Portbase during an information session. You can find it here:
Please note: in this session the old deadline is mentioned; the correct deadline is 16 November 2026. See here the answers to the frequently asked questions during and after this session.
Expected schedule
Before going live, successful testing must be completed in the test environment, followed by a successful pilot in production. Only then can go-live take place. There is no time to wait—action is necessary!
It is crucial that you have, no later than 1 November:
- Completed successful tests in the Portbase test environment;
- Moved all adjustments to production
If this is not completed before 1 November, we cannot guarantee a timely go-live.
Mandatory data for the TSD message
The following data must be reported:
| Must be included 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 that we can process it in the TSD. A change to the IFTMCS message specifications or a switch to the API* is required. |
| HS code (six digits instead of the current four digits) |
No action required. Do send the six-digit code. Include the six-digit HS code with the ENS. We will copy this into the TSD. |
Action required. You must send this six-digit code to Portbase so that we can process it in the TSD. A change to the IFTMCS message specifications or a switch to the API* is required. |
| RTO number (ferry & containers) |
No action required. Portbase already has the RTO number for ferry and container terminals. We process this in the TSD. |
No action required. Portbase already has the RTO number for ferry and container terminals. We process this in the TSD. |
| Bonded warehouse licence 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 required to report the notify party.
Do you decide to do so anyway? Then you are required to also state an email address or telephone number of the notify party.
|
Is the consignee known? Then you are not required to report the notify party.
Do you decide to do so anyway? Then you are required 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 via an API connection. Contact sales for more information.
Do you want to send a TSD message with master data only? Then switch to the new IFTMCS message specifications or choose a connection via API.
Dutch Customs is not introducing the previously mentioned TSR message (Temporary Storage Reuse).
New working method
Dutch Customs prefers to receive the master and house data. Therefore:
• 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.
• Are you reporting only a TSD and is there no ENS preceding it? Dutch Customs prefers to receive 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 the message in this way; therefore the status is also reported back at Bill of Lading level.