The ultimate effective date of the new Temporary Storage Declaration (ATO) / TSD is 16 November 2026. From no later than this moment, you submit the ATO in two ways:
- TSD message with master and house data;
- TSD message with master data only.
View here Customs’ communication about this legal change.
Recording information session
The key 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 here the answers to the frequently asked questions during and after this session.
Schedule for customers with system interface
Before go-live, successful testing in the test environment must have taken place, followed by a successful pilot in production. Only then can go-live take place. There is no time to wait; action is required!
It is crucial that you no later than 1 November:
- Successfully complete tests in the Portbase test environment;
- Have moved all changes to production
If this is not completed before 1 November, we cannot guarantee timely go-live.
Schedule 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 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 that we can process it in the TSD. A change in the IFTMCS message specifications or switching to API* is required. |
| HS code (with six digits instead of the current four digits) |
No action required. Do make sure you include the six-digit code. Include the six-digit HS code with the ENS. We will take this over 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 switching to API* is required. |
| RTO number (ferry & containers) |
No action required. Portbase already has the RTO number for ferry and container terminals. We will process this in the TSD. |
No action required. Portbase already has the RTO number for ferry and container terminals. We will 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 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.
|
*Do you want to send a TSD message with master and house data?
Portbase facilitates this with an API connection. Contact sales at 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 an interface via API.
Customs will not introduce the aforementioned TSR message (Temporary Storage Reuse).
New working method
Customs prefers to receive 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 Customs.
• When we receive only the master data for the ENS, we send a TSD message with master data.
• Reporting only a TSD and no ENS precedes it? 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 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 fed back at Bill of Lading level.
Related articles
Part of