General questions

This page features answers to the questions we are asked most frequently. These have been compiled by our service desk and other specialist colleagues. Do you have a question that is not included here? Feel free to contact us. We are always ready to help!

What should I do if I do not receive a Confirmation of Exit (CoE) after my export declaration?

When you file an export declaration, you eventually want to receive a Confirmation of Exit (CoE) from customs. If this CoE is not forthcoming, you have to provide proof of export by other means. This is a time-consuming and tedious process, and your time could be better spent. It is therefore important to make sure that your export declarations are confirmed. This also prevents the imposition of an additional sales tax (BTW) assessment.

 

In the Netherlands, the CoE is sent from the DMS to the party submitting the export declaration, provided that this party has filed an export declaration in the DMS in the Netherlands. If the export declaration has been filed in the system of another Member State, a CoE message will be sent from AES to that Member State’s system. This occurs when the shipment is processed through the intended office of exit, as stated in the export declaration.

However, in some cases, the shipment may exit through a different customs office (and in a different member state) from the one intended for exit. For example, a shipment may exit via Schiphol instead of the intended office of exit in Germany. In such cases, the AES procedure is as follows:

  • When it has been determined on the basis of the MFX (AES manifest at exit) that the shipment has been processed through another office of exit, the system generates a fallback message.
  • This message is sent from the actual office of exit (Schiphol) to the intended office of exit (in this example, Germany).
  • The intended office then sends a message back to the exit office approving or rejecting the fallback option.
  • If the fallback option is rejected by the intended office of exit, no CoE will be issued and the enquiry procedure will apply.
  • If the fallback option is approved, the office of exit sends an IE518 exit results message to the intended office of exit.
  • Finally, the intended office of exit (Germany in this example) sends a CoE to the declarant of the export declaration via its national system.

Read more here about how to obtain the CoE on declarations of air cargo shipments.

Read more here if you did not receive the CoE.

How can I confirm the exit of goods (Confirmation of Exit) retrospectively?

Read the proper Customs procedure for retrospectively confirming the exit of goods (Confirmation of Exit) here.

How do I avoid Not Ready for Carriage charges?

Read more here about how to check whether Cargonaut has received your FWB message and how to avoid charges.

What are the emergency procedures for the various Customs systems?

The emergency procedures of the various Customs systems as stated on the website of the Tax Authorities can be found at this link.

How can I check the status of the Confirmation of Exit (CoE) in eCargo Receipt and what do the status categories ‘?’, ‘Y’ and ‘N’ mean?

The ECS tab in eCargo Receipt contains more information about the CoE.
Open this document for an explanation of the status categories ‘?’, ‘Y’ or ‘N’ and the basis on which they are determined.

Why have the messages I submitted been rejected?

Unfortunately, Cargonaut still has to reject submitted messages on a regular basis because they fail to comply with the Cargo IMP Manual.

This non-compliance means that the rejected messages cannot be shared with the ground handlers and the airlines. Click here to read a number of common reasons for rejecting messages, along with the approved alternatives. The aim of these instructions is to help you share your messages successfully with ground handlers and airlines.

How can I reach the Tax Authorities’ helpdesk?

Click here for the contact details of the Tax Authorities’ helpdesk.

Which messages does Cargonaut support?

Cargonaut’s message platform is a new, modern Port Community System (PCS). This platform distributes messages such as the FWB, FHL and FFM. For this new platform, the set of message formats, types and versions supported has been revised. This means that not all formats, types and versions are currently supported by Cargonaut.

Cargonaut’s new Port Community System only supports the message formats/types/versions listed below. The term ‘support’ covers the following:

New customers will only be connected to the platform if the message formats/types/versions they use are compatible.

Existing customers will be assisted in transitioning to the supported message formats/types/versions. Cargonaut will contact customers in cases where messages are not yet supported. Please email the Cargonaut helpdesk at helpdesk@cargonaut.nl if you have any questions, or call +31 (0)20 653 0808.

Guidelines

The message formats/types/versions supported are selected on the basis of one or more of the criteria below:

  • The version is one of the two most recent versions of the message as described in the IATA manual (2024 version).
  • The version represents a substantial volume of the total received for that specific message type.
  • The version is used by a substantial number of Cargonaut’s customers.

Message types en versions

Based on these criteria, the following list of supported and unsupported messages has been compiled:

Type Supported versions Unsupported versions 
FWB 16, 17 1 t/m 15
FHL 2, 4, 5 1, 3
FFM 4*, 5, 8 1, 2, 3, 6, 7
FSU 6, 7, 12*, 14, 15 1 t/m 5, 8, 9, 10, 11, 13
CSN 3 1, 2
FMA 0
FNA 0, 1
CIT (750) 1
CIT_REJECT (751) 1
EIN (755) 1, 3
EIN_REJECT (756) 1, 2
EIN_ALERT (757) 1
EIN_ACK (758) 1
EIN_LIGHT (765) 1, 3
XFAI 1
* alleen voor inkomende berichten

The message types/groups below will no longer be supported (Cargonaut message IDs have been added for clarity):

  • CargoIMP FZB (203), FSR (801), FSA (802)
  • Comfort (820, 821, 822, 823, 830, 831, 832, 833)
  • NCTS (614, 615, 616, 625, 626, 628, 629, 634, 637, 643, 644, 645, 651, 652, 654, 655, 658, 606, 660, 662, 607, 608, 680, 609, 140, 141, 906, 907, 917, 928)
  • AGS (702, 701, 703)
  • Nomineren (400, 403, 406, 408)
  • Track N Trace (315)

Bericht formaten

Ondersteund

  • Cargonaut Envelope
  • Covast Envelope
  • EDIFACT – Only for PGTS/AES message (750, 751, 755, 756, 757, 758, 765)
  • SITA
  • BUSDOC (voor uitgaande berichten)
  • Wrapped CIMP

Niet ondersteund:

  • EDIFACT CIMP

 

Any remaining questions?

Can’t find your question here? Get in touch with us using the button below.

Latest news

More news