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.
View the communication from Customs about this statutory change here.
Recording of the information session
The most important changes were explained by 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. View the answers to the frequently asked questions during and after this session here.
Planning for customers with system interface
Before go-live, successful testing in the test environment must have been completed, 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 no later than 1 November:
- Complete successful tests in the Portbase test environment;
- Move all adjustments to production
If this has not been completed before 1 November, we cannot guarantee a timely go-live.
Planning for customers using web screens
We will align the exact date for switching to the new web screens of Cargo Declaration Import by mutual agreement.
From 16 November 2026 at 12.00, you must complete 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. A change in the IFTMCS message specifications or a switch to API* is necessary. |
| HS code (with six digits instead of the current four digits) |
No action required. 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. A change in the IFTMCS message specifications or a switch to API* is necessary. |
| 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. |
| Warehouse authorisation number (bulk) |
Action required. This number is not known to Portbase. We also do not receive it from Customs. |
Action required. This number is not known to Portbase. We also do not receive it from 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 for 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 for the notify party.
|
*Would you like to send a TSD message with master and house data?
Portbase facilitates this with an API connection. Contact sales for more information.
Would you like to send a TSD message with master data only? Then make a change to the new IFTMCS message specifications or choose for a connection via API.
Customs will not introduce the previously mentioned TSR message (Temporary Storage Reuse).
New working method
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 will send a TSD message with master and house data to Customs.
• When we receive master data only for the ENS, we will send a TSD message with master data.
• Reporting a TSD only and no ENS precedes it? 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 Customs.
• The TSD message is sent per Bill of Lading (and no longer grouped per manifest/loading port). Customs wants to receive this message in this way; therefore, the status is also returned at Bill of Lading level.