FAQ

1. LSP

• How to set up a Handshake as an LSP?
• Which email address of the shipping agent should I use to request a handshake?
• How do Logistics Service Providers use the Inbound Release Platform?

2. TSD

• How to apply for an EORI number from Customs?
• Can Union status still be granted via an amendment after activation of the TSD?
• How to work with cassettes and MAFI trailers in a TSD?
• How do multiple outbound BLs appear in the IE570 (Re-Export Notification) message?
• How should packaging codes be used in a TSD and in a subsequent declaration?

3. WRITE OFF TSD

• Is it advisable to write off a container at the Master Consignment Item level?
• Is it also possible to write off at Master Consignment Item level for a TSD that contains multiple items?
• Can I state the full number of packages and the full weight at goods shipment level in order to trigger the release of the container?
• Do the HS codes provided during the write-off process need to be the same as the HS codes recorded in the TSD?
• How should I include the B/L number or consignment number (for ferry or short sea container) in my declaration to correctly discharge the TSD?
• Which previous document must I specify in the declaration to be able to discharge a TSD?
• Which location codes should be used to trigger an FASFC declaration?

As an LSP, you send an email to your shipping agent requesting that they establish the handshake with you. Don't forget to include your NxtEntityID. The shipping agent must use your NxtEntityID to initiate the handshake in the IRP Portal.

We have requested an email address from the various shipping agents. You can find the provided addresses in the table below.

Watch this short demo to see how a Logistics Service Provider navigates and uses the Inbound Release Platform.

Go to the following Customs website: General information EORI | SPF Finances. 

You will then be taken to the following page:

There you can download the NL PDF or EN PDF and send the completed form back to the address listed on the document.

Goods are automatically considered non-Union goods upon submission of a TSD.
In accordance with the Union Customs Code (UCC), goods placed under temporary storage are deemed to be non-Union goods as long as their Union status has not been proved.
If no Proof of Union Status (PoUS) is submitted with the TSD, the goods are categorized by AAD&A as non-Union goods and are treated accordingly, regardless of their actual customs status.

It is not possible to change the customs status at system level.
After activation of the TSD, it cannot be cancelled, nor can an amendment be submitted to assign Union status at a later stage.

The cargo can still be released in such cases.
To do so, the supervising customs office responsible for the place of unloading must be contacted.
Following a positive assessment of the submitted documents and evidence, the Competent Customs Officer (CCO) may manually regularize the TSD and release the goods.

Cassettes and MAFI trailers are mainly used for loading and unloading goods from ro-ro vessels.

Cassettes are primarily used in the paper sector on short-sea routes, where they are picked up and set down by a tug or terminal tractor.

For containers, BR-PN-TS-028 applies. This means the container identification number must comply with ISO 6346 (format: ZZZZ9999999, e.g. CSQU3054383).

SECU units may therefore be specified in the containerIdentificationNumber element under TransportEquipment.

All other unit types must be submitted as SupportingDocuments (CL213).

Please refer to the attached list of SupportingDocuments codes to select the correct code:

• Cassette (empty): 8001
• Cassette (full): 8002
• Trailer (empty): 8003
• Trailer (full): 8004

Cassettes and MAFI trailers used in the breakbulk trade are not considered “TransportEquipment” and therefore do not fall within the scope of the IRP process. Breakbulk cargo loaded on these units must be processed in accordance with Chapter 8.5.1 (individually identifiable cargo) and Chapter 8.5.2 (non-identifiable cargo) of the IRP Business Implementation Guide (IRP BIG).

The Re-Export Notification (IE570) message is always generated for the entire TSD.

Furthermore, in the Re-Export Notification (IE570) message, it is possible to include between 1 and 99 TransportDocument. You can find an overview in the table attached below.

To enable this, it is also possible to include between 1 and 99 outbound BL values in the RENEnvelope.

For each outboundBL value included in the RENEnvelope, a transportDocument section will be added with type N705 and a reference number matching the outboundBL value in the IE570 message.

There are several codelists containing packaging codes, which are determinative for the discharge process.

When lodging and discharging a TSD (Temporary Storage Declaration), packaging codes must be used correctly. This is essential for correct processing in Goods Accounting (GA) and IRP/CPu.

These packaging codes are included in CodeList 017 (part of the PN/TS Message Implementation Guide). This list contains all possible package types.

In the TSD and in the subsequent declaration discharging the TSD (Section 12 – Previous Document), the packaging code does not have to be identical, but it must originate from the same codelist.

In addition to the main list, CodeList 017 contains two important sub-lists:

• CL017 (excluding the codes in CL181 and CL182) – countable goods
• CL181 – non-countable goods
• CL182 – countable goods “not packed”

Both sub-lists are also included in the PN/TS MIG.

Important: The codes from CL181 and CL182 also occur in CL017, but are subject to different validation rules.

• Use a packaging code from CL017, excluding CL181 and CL182.
• The number of items (pieces) must be declared.
• Discharge is performed on the basis of quantity and gross mass (with a tolerance of 10% in plus or minus).
  See also the GA Basics document.

• Use a packaging code from CL181.
• Number of items cannot be declared.
• Discharge is performed solely on the basis of weight (see GA Basics document).

Example: Container with scrap metal → packaging code VS (Bulk, scrap metal) + weight of the goods.

Result: discharge based on gross mass.

Note: Bulk goods transported by bulk vessels are, for the time being, still declared in PLDA (CUSCAR).

Important: When using codes from CL181, the “Marks & Numbers” field must be left empty.

When using a code from CL182, countable goods are discharged only on the basis of weight (with a tolerance of 10% in plus or in minus). As a result, the proper functioning of Goods Accounting (customs), and consequently IRP and CPu, cannot be guaranteed. Customs release may occur before the TSD has been fully discharged. It is even unclear what exactly is considered as being “discharged” in such cases.

The use of packaging codes from CL182 is therefore strongly discouraged. Ship agents preferably do not include these codes in their TSDs. CodeList 017 provides sufficient alternative packaging codes. This prevents declarants of subsequent declarations from also using packaging codes from CL182 and avoids discussions regarding the discharge of the cargo manifest and possible premature customs release at terminal level.

In that case, write-off due to MCI is possible, but not necessary because it is physically impossible to remove part of the container from the terminal anyway. A partial release of a container's contents therefore offers no added value.

If, in the subsequent declaration, you refer to the TSD without specifying a particular MCI, reduce the Goods Account package count and weight according to what is being written off.

Yes. You can even write off the TSD using more than one declaration in this way. The number of packages written off in each of these declarations is deducted from the total number of packages in the TSD. Once the number of packages to be written off for the TSD reaches zero, it is released for collection at the terminal.

No. Each declarant is responsible for the accuracy and completeness of their own declaration. If the TSD contains incorrect data according to the declarant, the declaration must still be correct. An adjustment of the data in the TSD is not required, except in cases where there is an incorrect number of packages that would prevent you from writing it off.

The B/L or consignment number must be indicated as a transport document in the declaration. This requires specifying a transport document type and a transport document reference.

The reference must contain the correct B/L number. This number can be taken from the TSD when preparing the declaration, either via the IRP User Interface or the Import Consignment API.

For the type, you must choose one of the codes published by customs in codelist 754 (Type of Transport Document). For the maritime sector, these codes are relevant:

• N704 “Master Bill of Lading”
• N705 “Bill of Lading”

It is important to use the same transport document type in the declaration as in the TSD. A different type will result in a discharge error. This type can also be retrieved from the TSD via the IRP User Interface or the Import Consignment API.

For detailed information on discharging, see: PN-TS | FOD Financiën.

You must provide the CRN or MRN number of the TSD as the previous document. However, the application depends on the circumstances and on how the shipping agent drafted the TSD.

The release at the terminal can take place at the Master Consignment (MC) level (i.e., the entire TSD) or at the Master Consignment Item (MCI) level within the TSD.

• If you want to make all goods in the entire TSD available at once at the terminal (e.g., a whole container), you can discharge at the MC level.
  • For MC-level discharging, you specify the CRN or MRN_number of the TSD as the previous document (“reference”). The document type is N337 in NCTS or IDMS, and 337 in a PLDA declaration.
• If you want to release only part of the goods in the TSD without discharging the entire TSD (e.g., an NCTS declaration for a number of cars listed in a TSD), you must discharge specific MCIs in the TSD.
  • For MCI-level discharging, you use the same data but add a specific MCI number. This is the sequential number of the MCI within the TSD.

The CRN or MRN number can be retrieved from the TSD via the IRP User Interface or the Import Consignment API. The TSD contents can also be retrieved—provided a “handshake” with the shipping agent—from the IRP, giving access to all MCI numbers that can be used in the previous document.

Unlike in PLDA, the cargo list (TSD) in PN/TS is only activated after the goods have been unloaded at the terminal. To safeguard the existing fast logistics process, prelodged discharging will often be necessary.

Prelodged discharging can be performed using the CRN number of the TSD, supplemented with an MCI number if needed.

A prelodged declaration must be activated after unloading (= activation of the TSD) by sending an additional PN message to the declaration system (IDMS or NCTS). This can be done via your declaration software. Only after that will the cargo list be effectively discharged and your declaration released.

For discharging after unloading, you refer in the declaration to the MRN number of the TSD, supplemented with an MCI number if needed.

For detailed information on discharging, see: PN-TS | FOD Financiën

Only if these location codes of FASFC inspection centres are used in the IDMS or NCTS declaration will a customs check be triggered, resulting in an orange CSR in IRP and an orange customs light in CPu, allowing you to take the container to the inspection point.

Location codes of type A (= 3rd character in new unLoCode): available in the attachment below.

The following guideline was provided by AADA along with these new codes.

• "These new codes work in all customs applications (NCTS, PLDA, etc.) and replace the old FASFC location codes listed in notes D/14/014 (PLDA application in the Antwerp region) and 2020/101/0020 (NCTS application in the Antwerp region).

   

• The above new location codes are type A location codes. It is important that the correct location type (A) is specified in the new declaration components (NCTS, IDMS, etc.). As a characteristic/qualifier, you must enter U (UN/LOCODE)."