Announcement: change in NID withdraw process (for terminals)

Notification Import Documentation

In this article, we’re sharing an upcoming feature that will cause a process change for terminals processing withdrawal requests. This could be due, for example, to incorrectly submitted import documentation. The images below are a sample. The actual implementation may differ from the image shown. After the feature goes live, we’ll share the final screens in a new release note (and related articles on our support website).

Are you a NID user? Read the release note: Announcement: Uniform process to withdraw import documentation.

New procedure: process NID withdraw requests via the web screens

The community(NID users) have indicated on several occasions that the working methods for withdrawal requests at the various terminals vary so much that this creates a great deal of confusion. They are asking for a uniform process to know immediately what the status of the withdrawal request is. This new feature is mainly for terminals that cannot yet receive a withdrawal request via the current MID implementation.

Portbase will facilitate this process in the Notification Import Documentation (NID) service, regardless of the terminal’s implementation variant. This allows us as a community to work together on suitable solutions. The new process will likely go live in beginning of May 2026.

What changes for terminals

Portbase sends an email notification when an MID user submits a withdraw request. The email contains minimal information and a URL (link) to new MID screens for terminals in the Port Community System (PCS). Below you can see an example of the email.

In the screen, you can see per container for which a request to withdraw the import document is pending. When submitting this request, the submitter (MID user) is expressly informed of his/her own responsibility in this process.

Processing at the terminal is simple: you can choose to accept or reject each container. If you choose to reject, the terminal must provide a reason. The following two options are possible:

  • Rejected: the container is too far along in the process.
  • Rejected: the container has already departed.

By responding to these withdraw requests, the submitter (NID user) can take the necessary next steps. The submitter can set up an email notification for these notifications in NID.

Applicant’s perspective (NID user)

Read all about the feature for creating a withdraw request at a terminal here Announcement: Uniform process to withdraw import documentation.

Background information

The NID service is used by the community to submit import documentation paperless (and without counters) since early 2012. This essential functionality is also a service with a consistently high number of customer queries annually for the same reason.

In recent years, Portbase has unilaterally adjusted processes for those submitting import documentation where possible. From a community perspective, the working group also inquired and investigated whether terminals could be connected to this service in a uniform manner. The working group clearly reported that external factors are decisive in this matter and are not feasible in the short term.

Therefore, this solution is only possible in this web-based format, and the market wants to implement this uniformly.