Customers link the service Notification Import Documentation (NID) to the statuses they receive via the service Cargo Controller Import. For the Cargo Controller Import API we have elaborated in this article how you can automate this process.
The timely availability of a correct import document for the cargo is 1 of the 4 review points of a terminal. Without an import document, the cargo will not be released. Submitting an import document is described as a NID notification. The NID notification is reported back per container in Cargo Controller Import.
Status: Pre-notification import document
All statuses are tracked per equipment in the container status screen:
The main indicators show an overall status per phase, or the most critical status. These are what the colours mean:
: Status is confirmed, all indicators are green.
: At least 1 indicator is yellow; your attention may be required.
: At least 1 indicator is red; your attention is required.
: Process in progress. Not all indicators are green yet, but there are no warnings either. Waiting for an update.
: Status not yet known. There is no update available yet; there may be an expected status such as the ETA. Waiting for an update.
Common issues and how to deal with them
A number of examples of problem situations around the import document:
-
No document pre-notified
Solution: Check whether the import manifest has already been submitted. Check whether the cargo has already been discharged, or whether the vessel has arrived.
If the cargo has been discharged, then it is clear that the customs import declaration could be submitted. If no NID notification is known yet, this means that something has been delayed in that process. Contact the party and/or department that manages that process.
-
Document pre-notified to the wrong terminal
Solution: Withdraw the incorrectly submitted document. Submit it again to the correct terminal.
Has a vessel diverted from the terminal in the final phase of the voyage, or was an incorrect terminal selected? Then the first action is to withdraw the document.
Then pre-notify the document again to the correct terminal.
-
Document is accepted by the terminal, but does or does not show a confirmation.
Solution: If no response is received, check the terminal status of the pre-notification of the pickup.
Some terminal do not provide a status confirmation in response to submitting a NID notification. This is clearly shown in the status message of Cargo Controller Import.
Within the Secure Chain we also show the terminal status when the inland operator aligns its planning for picking up the cargo. If the NID document was not accepted, then this is shown for the first time at that moment:
Via all errors you then end up on an explanation page in Details:
Check the declaration and adjust it.
Advice: warn 6 hours after ATA Container
Provide a review mechanism within your own systems. Portbase offers an option via its web screens to send an email alert. If no NID notification has been submitted 6 hours after the discharge confirmation, we will send a warning by email.
You can set up this message manually as a user in the Cargo Controller Import web screen. For this, read the article Set up email notifications in Cargo Controller Import. You can also integrate this warning into your own systems if you use the Cargo Controller Import API.
Related to