Error messages


Search

Quickly to

Frequently Asked Questions

Error messages

Ich erhalte einen Fehlercode beim Bearbeiten/Löschen einer Dokumentnummer, was soll ich tun?

Use the table below to find out what is wrong and what solution is possible.

Error codeDescriptionSolution
-Diversion REJECTPlease contact the terminal. The terminal needs to send a new arrival notification to Portbase.
6210The structure of the MRN indicates that the MRN is incorrect.Your prenotification in Notification Export Documentation needs to be amended.
Check whether you have correctly copied the MRN number and type in the prenotification in Notification Export Documentation.
If the input is correct, please contact customs in the country where the export declaration was generated in order to find out the reason for the rejection.
6229The arrival notification was sent by the terminal more than 7 days ago.Please contact the terminal. The terminal needs to send a new arrival notification to Portbase.
6233The document has a status which means export is not possible. One possibility is that the document has already been used for export or has been cancelled.Your prenotification in Notification Export Documentation needs to be amended.
A different export document must be entered in the prenotification in Notification Export Documentation; the current status cannot be changed.
Please contact customs in the country where the export declaration was generated in order to find out the reason.
90MRN is unknown.Your prenotification in Notification Export Documentation needs to be amended.
Check whether you have correctly copied the number and type of the transit document in the prenotification in Notification Export Documentation.
If the input is correct, please contact customs in the country where the transit document was generated in order to find out the reason for the rejection.
91The MRN has already been released.Your prenotification in Notification Export Documentation needs to be amended.
Please contact customs in the country where the transit document was generated in order to find out the reason.
92Registration of arrival notification is impossible with current MRN status. One possibility is that the document has been cancelled or not activated.Please contact customs in the country where the transit document was generated in order to find out the cause and the solution.
One possibility is that the prenotification in Notification Export Documentation needs to be amended.
93MRN is invalid, does not comply with algorithm.Your prenotification in Notification Export Documentation needs to be amended.
Check whether you have correctly copied the number and type of the transit document in the prenotification in Notification Export Documentation.
If the input is correct, please contact customs in the country where the transit document was generated in order to find out the reason for the rejection.

Was this post helpful?

My prenotification is not known to the terminal, even though I have created it in MCA/Portbase

When creating a handling, you can choose to submit it as a status request or as a prenotification. If you select 'No' in the Prenotification field when creating the handling, a status request is first sent to the terminal.

If you select 'Yes' in the Prenotification field, a prenotification is sent straight away.

If the container has already been notified as a status request, you can convert it into a prenotification by using the ‘Submit as prenotification’ button.

Was this post helpful?

Why does the prenotification remain in ‘Expected’ when the container has already been loaded/discharged?

The ECTDELTA and EUROMAX terminals do not send a confirmation that a container has left from or arrived at the terminal. These are so-called Gate In/Out messages. As a result, these prenotifications remain in the Expected box.

Was this post helpful?

I can’t select a terminal, why is this?

Before you can send a NID message to a terminal, you need to sign a terminal contract for that terminal. In this terminal contract, you accept responsibility for the complete and correct prenotification of your document data to the terminal.

Please contact sales@portbase.com to sign the appropriate terminal contracts for the terminals you want. The applicable terminals and document types will then be activated for you in the service Notification Import Documentation. After activation, you can select the terminal in the service.

Was this post helpful?

Error message when entering, ‘The export shipment for document … has already been registered by the terminal’

In some (urgent) cases, a terminal can pre-notify the document number on your behalf. If you then try to pre-notify the same document, you will receive this error message:

‘The export shipment for document … has already been registered by the terminal.’

You are unable to find the document in Track & Trace. If necessary, contact the terminal to check whether the correct data has been pre-notified.

Was this post helpful?

Error message when entering, ‘Document … already exists’

If you receive the error message below, this means that the document number in question has already been entered in our system. This may have been done by your own company or by another party, such as the carrier, customs agent or terminal.

‘The export shipment for document... already exists.’

Check in Track & Trace whether the correct information has been pre-notified. Is the data incorrect? Read here how you can adjust the pre-notification.

Was this post helpful?

I have received an error message that the document number is incorrect

The moment you enter a number of a customs document, we automatically check whether its structure corresponds to that in the various customs systems.
In this way, we reduce the chance of error for you and problems are avoided when collecting the container at a terminal.
A straightforward example: an MRN number always comprises 18 characters. If you enter an MRN number with 17 characters, you will receive an error message. There are different criteria for each type of customs document that are automatically verified for you by the Port Community System.

Also see: # which document type should I use in which situation

Was this post helpful?

Why does Portbase say there is an embargo on the container when this is not visible at APM MVII?

If no document has been submitted, the container will always remain under a Customs embargo.
Once the document has been submitted and processed at APM MVII, the Customs embargo will be lifted.

Was this post helpful?

Why am I getting a notification that my documents are not in order from the ECT Delta/Euromax terminal when they are in Portbase?

You can check on the ECT website whether they have the document or you can contact the Portbase Service Desk.

It may be that the ECT/Euromax terminal has sent a double APERAK (return message) to Portbase. As a result, they will not be processed in the correct order.

The Service Desk will then again submit a return message, which will solve the problem.

Was this post helpful?

I have not received a TAR code, why is that?

If you have not received a TAR code for APM Maasvlakte II, APM Terminals Rotterdam or Rotterdam World Gateway (RWG), this may be because your pre-notification has been rejected, the system is experiencing a disruption or the terminal is closed.

Terminal APM Maasvlakte II

If there are no more available time slots available for the requested day, the pre-notification will be rejected. The error message shown is: THERE ARE NO APPOINTMENT OPENINGS AVAILABLE FOR THE ENTERED DATE. You can resubmit the pre-notification with a new desired time on a different day. In short, no time slot will be issued on a different day than the one requested.

Was this post helpful?

How long is a rejected notification listed in the overview screen?

A rejected local clearance notification always remains in the overview screen.

In case the rejected notification was an original notification, the notification has not been processed by Dutch Customs.

In case the rejected notification was an update on a previous notification, only the changes in the update have been rejected. The original notification remains valid with Dutch Customs.

Was this post helpful?

I have received an error message. What does this mean?

Pin doesn’t match or is expired, contact line operator.
The release does not match or has expired. Please contact the shipping line for assistance in this matter.

CDM - Customs document missing
If you receive the rejection ‘CDM blockade, DD.’ from the terminal, please consult your freight forwarder/importer to verify whether the terminal in question corresponds with the terminal selected by you. If this is the case, then please contact the Portbase Service Desk for a solution.

Rejection RUB25 - Booking is full
Please contact the shipping line to have the booking increased.

Rejection ORN - Booking is unknown
The acceptance order has not been submitted by the shipping line or you have submitted a wrong acceptance number.
If you receive this error message, your best option is to check the acceptance number.
If you are certain that this number is correct, then please contact the shipping line. They can check whether the acceptance order has been sent to the terminal. If all of the above proves correct, the container number may have been entered incorrectly.

BLA - Order (for line) not found, contact line operator.
Please contact the shipping line. You have probably selected a different shipping line than the one known at the terminal.

BLT- Blocked by terminal.
This is a general notification that states that the container cannot be collected or delivered. If the response message contains no additional data, you can contact the terminal for further information.

COR - Container not released
The shipping line has not yet commercially released the container.

BCO - Before cargo opening
This is the earliest possible moment on which an Export container may be delivered to the terminal (usually x days before the arrival of the ship).

ORN – the shipping company has not submitted the acceptance order, or you have entered an incorrect acceptance number
When this error message is displayed, the best thing to do is double-check the acceptance number. If you are absolutely certain this number is correct, you should contact the shipping company. They can verify for you whether or not the acceptance order has been submitted to the terminal.

If all of the aspects listed above are correct, it might be that the container number has been incorrectly entered in the Portbase system.

RUB20 – The booking number you submitted is registered in the terminal system as belonging to another shipping company
If you receive this error message, it is important to check which shipping company’s name is on the booking/release. If you do not know, the best thing for you to do is contact the client and/or the shipping company.

DUP - I have deleted the pre-notification and have resubmitted it, but now I am receiving a DUP error. What does this mean?

If your pre-notification is rejected for the reason: ‘DUP’ (duplicate), that means that a pre-notification with this container number and booking number already exists in the Hutchison Ports ECT Delta / Euromax terminal system. This other, existing pre-notification may have been created by you or by another party. It is also possible that the container has been pre-notified for a barge, train or seagoing vessel.

If you have created the pre-notification yourself, you will be able to look it up in the service Hinterland Container Notification. To find the pre-notification, enter the container number in question into the filter field and adjust the date.

If you are unable to locate the pre-notification,  contact the terminal and ask how (and from whom) they received the pre-notification.

If you find an earlier pre-notification that contains an error and is meant for an ECT terminal, you should cancel it. To do so, click the tick mark at the start of the line to select, then click ‘Delete’ at the bottom of the screen.

Please wait a few minutes for the terminal to process the cancellation.

You will then need to submit the new pre-notification (the one that was rejected with the DUP message) once more.

This time it should be processed as usual. If not, and it is once again rejected with a DUP message, the pre-notification has probably not been fully erased from the terminal’s system just yet. In that case, contact the terminal and work with them to solve the problem.

Hutchison Ports ECT Delta: +31 (0)18 127 83 29              / balie_databeheer@ect.nl

Hutchison Ports ECT Euromax: +31 (0)18 137 72 00 (02/03) / balie.euromax@ect.nl

Was this post helpful?

Loading list (Coprar) has been submitted but the export manifest cannot be found. How can I fix this?

Check the call reference number in the notification and verify whether the specified expected times of arrival and departure fall within the filter. There is also a notification in the notification settings that you can turn on. This concerns the notification ‘Loadlist message not processed by PCS’.

Was this post helpful?

IFTMCS has been sent but the B/L is not displayed in the web screens. Why is this?

This is commonly caused by the fact that certain data is missing in the submitted notification, such as the postal code of the consignee or another party. Check if all the data has been entered in your system. For many errors, negative aparaks and mail notifications are also sent. You can set these notifications under ‘My Profile’, notifications settings.

Was this post helpful?

What do the rejections R006 and R027 mean and how can I fix this?

R006 - Product code missing or incorrect (Goods classification * LVM / PRD)
R027 – Goods code (GN) missing or incorrect

First, check whether the Animo Code has been entered and is correct: https://webapplicaties.agro.nl/vgc2/animocode

Also check the fields ‘goods classification’, ‘purpose of use’ and ‘destination code’. These must for example be entered as follows:

Goods Classification: Foodstuff
Purpose of Use: Further processing (LNV)
Destination code: Input

It is possible that an animocode is only allowed for a certain combination of these data.

Was this post helpful?

The terminal notification is still showing as ‘not sent’. What do I do?

Check whether the terminal is connected to Notification Local Clearance. Via this document you can check which terminals allow document prenotifications under the local clearance procedure and whether they require prior approval. Please refer to the Local Clearance document types (local clearance bonded warehouse/import).

If the terminal is not connected, it is correct that no message will be sent to the terminal.You must pick up the goods from the terminal under a different procedure.

If the terminal is connected, you have probably not yet had approval from the terminal to apply the local clearance procedure at the terminal. You can read about  how to get this approval here.

Was this post helpful?

What do I do if I receive the error message: ‘Not allowed to declare security: Visit times are not in chronological order’?

This error is attributable to the fact that the data in the upload file does not match the data that is stated in the vessel call. The data in the vessel call will have to be adjusted to match the data stated in the upload file. This is related to the listed date/time not corresponding. If the data matches, the file can be uploaded again and it will be processed.

Was this post helpful?

User Management: I am getting the error: Authentication failed. Please try again.

Check in this case whether u filled in the correct organisation name, user name or password. If you cannot remember one of these data, you can ask this to your user administrator. If you do not know who the user administrator is, or you are the user administrator, please contact our servicedesk.

Was this post helpful?

User Management: I am getting to message error: You have committed too many login failures. Your user account is locked.

When you receive this message, your account has been locked. Please contact your user administrator. If you do not know who the user administrator is (or you are the user administrator), please contact our servicedesk.

Was this post helpful?

What does the following error message mean: ‘Transport equipment ‘x’ contains export shipments from another forwarder. Are you sure that you have…’?

This is a warning if:

  1. the combination of transport equipment and booking number has previously been submitted in the Port Community System;
  2. the document number has already been entered by another party;
  3. the transport equipment contains multiple documents.

If the transport equipment does indeed contain multiple documents, you can click on OK and the prenotification will be saved.

In the case of 1 or 3, this will be followed by the error message: 'The export shipment for document 'x' already exists'. This means that the combination of document number and transport equipment number already exists in the PCS. This may have been done by you or by another party in the chain. If the prenotification was sent by a forwarder or haulier, you can see this in Track & Trace Export. If the document was prenotified by a terminal, you can contact the Service Desk.

Was this post helpful?

I cannot send my MID, why is this?

Are you using Notification Domproc or Transit Declaration? Both services currently only support container cargo at deepsea terminals for forwarders. This will be resolved in the near future. Until then, you can use Notification Import Documentation 2.0.

Was this post helpful?

I have received my inspections based on my ENS declaration, but I don’t see them in Inspections Portal; how is this possible?

Customs restricts the inspections that are reported via the ENS declaration to a minimum. When designing Inspections Portal, it was therefore decided – in consultation with Customs – not to include a feature for their display. If Customs announces an inspection using the ENS declaration, Customs can then manually register the inspection via Inspections Portal at a later time. In that case, you will be informed in the usual manner.

Was this post helpful?

Functionalities

IFTMCS has been sent but the B/L is not displayed in the web screens. Why is this?

This is commonly caused by the fact that certain data is missing in the submitted notification, such as the postal code of the consignee or another party. Check if all the data has been entered in your system. For many errors, negative aparaks and mail notifications are also sent. You can set these notifications under ‘My Profile’, notifications settings.

Was this post helpful?

Process progress

The terminal notification is still showing as ‘not sent’. What do I do?

Check whether the terminal is connected to Notification Local Clearance. Via this document you can check which terminals allow document prenotifications under the local clearance procedure and whether they require prior approval. Please refer to the Local Clearance document types (local clearance bonded warehouse/import).

If the terminal is not connected, it is correct that no message will be sent to the terminal.You must pick up the goods from the terminal under a different procedure.

If the terminal is connected, you have probably not yet had approval from the terminal to apply the local clearance procedure at the terminal. You can read about  how to get this approval here.

Was this post helpful?

We use cookies

This website uses cookies to track and analyse user behaviour, to improve the user experience and to ensure that relevant information and advertisements can be displayed. Click on 'customize preferences' to view and set your permissions for this website.

Read our Privacy Statement here | Close