New Temporarily Storage Declaration (ATO) from 1 October 2026

The final implementation date for the new Temporary Storage Declaration (ATO) / TSD is 1 October 2026. From that moment at the latest, you must submit the TSD in two ways:

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

View the communication from Customs about this legal change here.

Recording of the information session on 21 May 2026

The key changes were explained by Customs and Portbase in an information session. You can find it here:

View the answers to the frequently asked questions during and after this session here.

Expected schedule

We will start pilots from 1 June. After successful pilots, we will migrate all customers to the new TSD. Make sure that all mandatory details (see table below) are known by then. These details 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 details for the TSD message

The next details 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 these details to Portbase so that we can process them in the TSD.

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

HS code (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 required.

RTO number (ferry & containers)

No action required.

Portbase already has the RTO number for ferry and container terminals. We process this in the TSD.

No action required.

Portbase already has the RTO number for ferry and container terminals. We process this in the TSD.

Bonded warehouse licence number (bulk)

Action required.

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

Action required.

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

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 details?
Portbase facilitates this via an API integration. Please contact sales for more information.

Do you want to send a TSD message with master details only? Then switch to the new IFTMCS message specifications or choose an integration via API.

Customs will not introduce the aforementioned TSR message (Temporary Storage Reuse).

New working method

Customs prefers to receive the master and house details. Therefore:

• When we receive 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 master details for the ENS, we send a TSD message with master details.
• Are you reporting a TSD only and is there no ENS beforehand? Customs prefers to receive the master and house details. We would like to receive these details 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 the message in this way; therefore, the status is also returned at Bill of Lading level.

Related articles

Related to

Was this article helpful?

6 out of 7 found this helpful