New Temporary Storage Declaration (ATO)

The final implementation date of the new Temporary Storage Declaration (ATO) / TSD is 16 November 2026. From this point at the latest, you must submit the ATO in two ways:

  • TSD message with master and house data;
  • TSD message with master data only.

View here the Dutch Customs communication about this legal change.

Recording of information session

The main changes were explained by Dutch 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.

Planning 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:

  • Successfully complete tests in the Portbase test environment;
  • Move all changes to production

If this is not completed before 1 November, we cannot guarantee a timely go-live.

Planning 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 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 we can process it in the TSD.

A change in the IFTMCS message specifications or a switch to API* is required.

HS code (with 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 we can process it in the TSD.

A change in the IFTMCS message specifications or a switch to API* is required.

RTO number (ferry & containers)

No action required.

The RTO number of ferry and container terminals is known to Portbase. We process this in the TSD.

No action required.

The RTO number of ferry and container terminals is known to Portbase. We process this in the TSD.

Customs warehouse licence number (bulk)

Action required.

This number is not known to Portbase. We also do not receive it from Dutch Customs.
Enter this in the web screen; Portbase will create a new field.

Action required.

This number is not known to Portbase. We also do not receive it from Dutch Customs.
Enter this in the web screen; Portbase will create a new field.

Notify party may be stated, including phone 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 include an email address or telephone number for 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 include 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 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 previously mentioned TSR message (Temporary Storage Reuse) will not be introduced by Dutch Customs.

New working method

Dutch Customs preferably receives 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 no ENS precedes it? Dutch Customs preferably receives the master and house data. We would like to receive this data so 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 reported back at Bill of Lading level.

Related articles

Part of

Was this article helpful?

7 out of 8 found this helpful
Link copied to clipboard