The final implementation date for the new Temporary Storage Declaration (ATO) / TSD is 16 November 2026. 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 the Dutch Customs communication about this legal change.
Recording of the information session
The key changes were explained by Dutch Customs and Portbase during 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.
Schedule for customers with system interface
Before going live, successful testing in the test environment is required, followed by a successful pilot in production. Only then can you go live. There is no time to wait—action is necessary!
It is crucial that you no later than 1 November:
- Have successfully completed tests in the Portbase test environment;
- Have moved all adjustments to production
If this has not been completed before 1 November, we cannot guarantee a timely go-live.
Schedule for customers using 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 required data.
Required 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 that we can process it in the TSD. An adjustment in the IFTMCS message specifications or a switch to API* is required. |
| HS code (six digits instead of the current four digits) |
No action required. However, do include 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. An adjustment in the IFTMCS message specifications or a switch to API* is required. |
| RTO number (ferry & containers) |
No action required. Portbase already has the RTO number of ferry and container terminals. We process this in the TSD. |
No action required. Portbase already has the RTO number of ferry and container terminals. We process this in the TSD. |
| Bonded warehouse permit 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 interface. Please contact sales for more information.
Do you want to send a TSD message with master data only? Then change to the new IFTMCS message specifications or choose an interface via API.
Dutch Customs will not introduce the aforementioned 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.
• Reporting only a TSD and there is no ENS beforehand? 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 this message in this way; therefore the status is also returned at Bill of Lading level.
Related articles
- Frequently asked questions about the new Temporary Storage Declaration (ATO) / TSD
- ATO / TSD scenarios – Dutch Customs
- New IFTMCS specifications (5.8.9) for customers who do not submit the ENS via Portbase
- New IFTMCS specifications (6.0.5) for customers who submit the ENS via Portbase
- Cargo Declaration Import web screens, after the transition to TSD
Part of