The final implementation date of the new Temporary Storage Declaration (ATO) / TSD is 1 October 2026. No later than from this moment, you must 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 of information session 21 May 2026
The key changes were explained by Customs and Portbase in an information session. You can find it here:
View here the answers to the frequently asked questions during and after this session.
Expected planning
We will start pilots from 1 June. After successful pilots, we will migrate all customers to the new TSD. Make sure all mandatory data (see table below) is known by then. This data can already be entered now. Due to the holiday period, completion by mid-July is preferred.
The full transition must be completed no later than 30 September.
Please note: if a vessel arrives after 1 October, a new TSD must have been submitted. An old ATO will not be supplemented.
Mandatory data for the TSD message
The next data must be reported:
| Mandatory to include with 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 migration to API* is required. |
| HS code (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 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 migration to API* is required. |
| RTO number (ferry & containers) |
No action required. Portbase already knows the RTO number for ferry and container terminals. We process this in the TSD. |
No action required. Portbase already knows the RTO number for ferry and container terminals. We process this in the TSD. |
| Warehouse authorisation number (bulk) |
Action required. This number is not known to Portbase. We do not receive it from Customs either. |
Action required. This number is not known to Portbase. We do not receive it from Customs either. |
| Notify party may be reported, 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. Please 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 a connection via API.
The above-mentioned TSR message (Temporary Storage Reuse) will not be introduced by Customs.
New way of working
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.
• Only reporting 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/port of loading). Customs wants to receive this message in this way, therefore the status is also reported back at Bill of Lading level.