The final implementation date for the new Temporary Storage Declaration (ATO) / TSD is 1 October 2026. No later than this moment, you must submit the ATO in two ways:
- TSD message with master and house details;
- TSD message with master details only.
View here Customs’ communication about this legal change.
Recording 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 that all mandatory data (see table below) is known before 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. For all vessels arriving after 1 October, a new TSD message must have been submitted.
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. An adjustment 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. An adjustment in the IFTMCS message specifications or a switch to API* is necessary. |
| RTO number (ferry & containers) |
No action required. The RTO number of ferry and container terminals is known to Portbase. We will process this in the TSD. |
No action required. The RTO number of ferry and container terminals is known to Portbase. We will 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 phone 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 phone 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 phone number for the notify party.
|
*Do you want to send a TSD message with master and house details ?
Portbase facilitates this with an API connection. Contact sales for more information.
Do you want to send a TSD message with master details only? Change then to the new IFTMCS message specifications or choose for a connection via API.
Customs will not introduce the aforementioned TSR message (Temporary Storage Reuse).
New way of working
Customs preferably receives the master and house details. Therefore, the following applies:
• When we receive the master and house details for the ENS (and the cargo is discharged in the Netherlands), we send a TSD message with master and house details to Customs.
• When we receive only the master details for the ENS, we send a TSD message with master details.
• Reporting only a TSD and no ENS precedes it? Customs preferably receives the master and house details. We would like to receive this data, so that we can send a TSD message with master and house details 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.