Passer au contenu
Français
Portail client
Contact
  • Il n'y a aucune suggestion car le champ de recherche est vide.

Description du process

Emplacement : Documentation PN-TS

Source : PN-TS DEV Message implementation guide v0.2.0

1. Process model description

The PN-TS system covers the exchange of information between Economic Operators and Belgian Customs upon entry and unloading in Belgium of goods arriving from a third country, following the legal provisions laid down in the Union Customs Code (UCC), its Delegated Act and Implementing Regulation.[1]

According to the UCC, all goods must be presented to customs upon their arrival in the EU customs territory and availability for customs controls by means of an electronic Presentation Notification (PN). For maritime and air transport the presentation of goods may be done in one instance upon unloading from the vessel or the aircraft. For other modes of transport, the presentation of goods takes place upon arrival in the EU customs territory. Non-Union goods are stored under customs supervision until they are placed under a customs procedure or re-exported. For this, a Temporary Storage Declaration (TSD) is required, to be lodged at the latest upon unloading.

The PN system allows Economic Operators to notify customs of goods being presented and customs officers to follow-up on the accomplishment of customs formalities upon entry. The TSD system allows Economic Operators to lodge, amend and invalidate TSD's and customs officers to ensure compliance with the rules and formalities applicable to the temporary storage procedure.

This message implementation guide describes the web-service-enabled message exchange between Economic Operators and both systems.[2] The process model description explains the context and scenario’s applicable to this message exchange.

· 3.1 describes the message exchange in the context of placing non-Union goods under temporary storage by lodging a TSD (and additionally a PN in certain scenario’s) and in the context of the TSD lifecycle management (excluding ending the temporary storage procedure by lodging a customs declaration or re-export notification).

· 3.2 describes the message exchange in the context of presenting Union goods (or non-Union goods in certain scenario’s) outside the temporary storage procedure and in the context of the PN lifecycle management.

· 3.3 gives an overview of the potential sequences of messages for each of the above scenarios.

· 3.4 and 3.5 gives an overview of the TSD and PN lifecycle and the potential state transitions.

1.1. Placement under temporary storage of non-Union goods

Non-Union goods can be placed under temporary storage by lodging a TSD, which can be done in two different ways:

  • the submission of a pre-lodged TSD before presentation and a PN upon presentation;
  • or the submission of a combined TSD upon presentation.

After submission of the declaration details, messages are foreseen for invalidating and amending the TSD, notifying a transfer of declared consignments (movement to another temporary storage facility within Belgium) or deconsolidating a TSD originally lodged with master consignment data only (add related house consignment data).

  • 3.1.1 describes the submission of a pre-lodged TSD (3.1.1.1) prior to presentation of the goods and the submission of a Presentation Notification (3.1.1.2) upon presentation of the goods. The CRN and consignment details of both messages need to match in order to activate the pre-lodged TSD (3.1.1.3).     
    Until the goods are presented, it is allowed that the Economic Operator invalidates the pre-lodged TSD via the submission of a TSD invalidation request (3.1.1.5). Via such invalidation request Customs will be informed that the originally to-be presented non-Union goods will no longer be declared / presented. Note that it is required that the goods declared via a pre-lodged TSD are presented via a Presentation Notification within 30 days of submission of the pre-lodged TSD. At the end of this period (upon expiration), the pre-lodged TSD will be automatically invalidated (3.1.1.4) by Customs.
  • 3.1.2 describes the submission of a combined TSD upon presentation of the goods. Both the Temporary Storage Declaration details and the Presentation Notification details are submitted in one message. The system will create both a TSD and linked PN based upon this validated message.
  • Both during the pre-lodged and the presented (activated pre-lodged TSD or combined TSD) phase of the TSD, the Economic Operator is allowed to amend the previously submitted declaration details via the submission of a TSD amendment request (3.1.3). Depending on the phase, it is only allowed to amend certain data elements, as well as explicit Customs Officer approval might be required.
  • 3.1.4 describes the message exchange in the context transferring or deconsolidating TSD consignments. A Temporary Storage Facility Holder (Economic Operator) can submit a TSD transfer notification (3.1.4.1) in order to notify the transfer of one or more consignments of a presented (activated pre-lodged or combined) TSD. The notification can only be used for authorized transfers from 1 temporary storage facility to another temporary storage facility within Belgium. By submitting a TSD deconsolidation notification (3.1.4.2), a TSD containing only Master Consignment data can be supplemented with the House Consignments after placement under temporary storage (activated pre-lodged TSD or combined TSD). A TSD Master Consignment can only be deconsolidated once during the temporary storage monitoring. A TSD containing both master and house consignment details is considered to be deconsolidated upon submission. After processing a successful TSD transfer and/or deconsolidation notification, it is no longer possible to amend the TSD via a TSD amendment request.

Regardless of the flow, the Economic Operator (message sender) is always informed of the business processing result of the submitted message. Relevant feedback messages will asynchronously be sent in return. The following sections explain in more details the main flows.

1.1.1. Pre-Lodged TSD

1.1.1.1. Submit pre-lodged TSD

Prior to the presentation of the goods (maximum 30 days), it is possible to submit a pre-lodged TSD message (IETS015). The pre-lodged TSD message contains all required data elements for placing goods in temporary storage and a unique LRN (Local Reference Number) as unique reference by the Economic Operator.

A technical validation will be executed synchronously upon submission of the message. When the message is technically compliant and successfully received by customs, a positive acknowledgment (IETS928) response is returned which contains a unique correlation id as functional reference. In case a technical error is encountered (xsd and format validations), a negative acknowledgement (IETS906) response is returned which contains the list of technical errors.

Upon successful technical validation, the pre-lodged TSD message will be processed further (asynchronous business processing). When all business validations are passed, a validation approved message (IETS028) is returned as feedback message and the pre-lodged TSD is registered in the system with status ‘Pre-lodged’. The validation approved message contains the CRN (Customs Reference Number) as unique customs reference for the registered pre-lodged TSD and an expiration timestamp. The pre-lodged TSD is only valid for 30 days. During this period, the pre-lodged TSD needs to be activated via a separate Presentation Notification (IETS007), otherwise the pre-lodged TSD will be automatically invalidated.

In case one or more business validation errors are triggered during the business processing of the pre-lodged TSD, a validation refused message (IETS016) is returned as feedback message. The validation refused message contains the list of functional errors encountered, including the error reason (specific for the rule/condition/code list), error code, and pointer to the element in the message causing the error. For the full overview of functional error reasons, please refer to code list section CLPNTSErrorReason.

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS015 : EO ; IETS928 : / ; IETS906 : / ; IETS028 : TSD@BE ; IETS016 : TSD@BE
  • Recipient — IETS015 : TSD@BE ; IETS928 : / ; IETS906 : / ; IETS028 : EO ; IETS016 : EO
  • Message id — IETS015 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id ; IETS016 : Msg id
  • Ref to message id — IETS015 : / ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id (IETS015) ; IETS016 : Msg id (IETS015)
  • Correlation id — IETS015 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS028 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928)
  • Business validation type — IETS015 : / ; IETS928 : / ; IETS906 : / ; IETS028 : 015 ; IETS016 : 015
  • LRN — IETS015 : LRN (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : LRN (IETS015) ; IETS016 : LRN (IETS015)
  • FRN — IETS015 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • CRN — IETS015 : / ; IETS928 : / ; IETS906 : / ; IETS028 : CRN ; IETS016 : /
  • MRN — IETS015 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /

1.1.1.2. Submit PN

Upon presentation of the non-union goods, a Presentation Notification (IETS007) message needs to be submitted. If lodged within the temporary storage procedure, the Presentation Notification shall contain a reference to the pre-lodged Temporary Storage Declaration (IETS015) within CRN attribute. This value will be used to activate the pre-lodged TSD which was already submitted successfully prior to presentation of the goods. The Presentation Notification shall also contain the required presentation information, actors, location of goods and consignment details, and LRN (Local Reference Number) as unique reference by the Economic Operator.

The same principle of synchronous technical validation is applicable with acknowledgement (IETS928) or negative acknowledgement (IETS906) response.

Upon asynchronous business validation, a validation approved (IETS028) or validation refused (IETS016) feedback message is returned.

When all business validations are passed, a validation approved message (IETS028) is returned as feedback message and the Presentation Notification is registered in the system with status ‘Accepted’. The validation approved message contains the FRN (Functional Reference Number) as unique customs reference for the Presentation Notification.

The validation refused message contains the list of functional errors encountered during the business validation.

In case no pre-lodged TSD was submitted prior to the presentation of the goods, the Presentation Notification can be lodged outside the temporary storage procedure.[3] In this case, the CRN attribute will refer to a customs declaration (if available upon presentation) or be left empty. For more details about this flow, please refer to section 3.2 (Presentation of goods outside the temporary storage procedure).

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS007 : EO ; IETS928 : / ; IETS906 : / ; IETS028 : PN@BE ; IETS016 : PN@BE
  • Recipient — IETS007 : PN@BE ; IETS928 : / ; IETS906 : / ; IETS028 : EO ; IETS016 : EO
  • Message id — IETS007 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id ; IETS016 : Msg id
  • Ref to message id — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id (IETS007) ; IETS016 : Msg id (IETS007)
  • Correlation id — IETS007 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS028 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928)
  • Business validation type — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : 007 ; IETS016 : 007
  • LRN — IETS007 : LRN (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : LRN (IETS007) ; IETS016 : LRN (IETS007)
  • FRN — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : FRN ; IETS016 : /
  • CRN — IETS007 : CRN pre-lodged TSD (IETS028 response to IETS015) ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • MRN — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /

1.1.1.3. Activation of the pre-lodged TSD

Upon registration of the Presentation Notification, an attempt is made to activate the existing (referenced) pre-lodged TSD based on the provided CRN value.

Besides the match on CRN value to identify the pre-lodged TSD, it is verified that all consignment details are provided in the Presentation Notification match with the consignment details as declared in the pre-lodged TSD. For the full list of business validations and related error reasons, please refer to section 4.4.5.

When the pre-lodged TSD is activated, the MRN (Master Reference Number) is generated, and the presentation details are joined together with the pre-lodged temporary storage details. Both the sender of the Presentation Notification and pre-lodged TSD are asynchronously informed of this activation.

The message sender of the Presentation Notification is asynchronously informed of the pre-lodged TSD activation result via the PN Linking Notification (IETS030) message. This message contains:

  • Activation of the pre-lodged TSD: The updated PN status (Linked), CRN and MRN of the activated pre-lodged TSD

  • No activation of the pre-lodged TSD: The updated PN status (Not linked), CRN of the pre-lodged TSD which was mentioned in the Presentation Notification, and list of activation errors encountered during the pre-lodged TSD activation attempt.

The message sender of the Temporary Storage Declaration is also informed that a pre-lodged TSD activation attempt was made based on a received Presentation Notification. When the Presentation Notification refers to an existing pre-lodged TSD, the pre-lodged TSD message sender will be informed via the TSD Activation Notification (IETS029) message. This message contains:

  • Activation of the pre-lodged TSD:

o   The updated TSD status (Accepted), MRN of the activated pre-lodged TSD, and key Presentation Notification details of the activating PN.   
OR

o   The updated TSD status (Irregularity under investigation), MRN of the activated pre-lodged TSD, and key Presentation Notification details of the activating PN.
In case the presented location of goods has a type of location ‘D – Other’, despite the successful activation of the Temporary Storage Declaration based on the Presentation Notification, a Customs Officer will need to confirm if the goods can be maintained in temporary storage or not. Therefore, another status is assigned to the activated pre-lodged TSD, which is now uniquely identified by the MRN. The customs officer first need to take a decision before the TSD can be processed further (status to Accepted in case the goods can be maintained in temporary storage).

  • No activation of the pre-lodged TSD: The TSD status (Pre-lodged), CRN of the pre-lodged TSD, and list of activation errors encountered during the pre-lodged TSD activation attempt.

The following table summarizes the exchange of the different messages and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS029 : TSD@BE ; IETS030 : PN@BE
  • Recipient — IETS029 : EO (IETS015) ; IETS030 : EO (IETS007)
  • Message id — IETS029 : Msg id ; IETS030 : Msg id
  • Ref to message id — IETS029 : Msg id (IETS015) ; IETS030 : Msg id (IETS007)
  • Correlation id — IETS029 : Correlation id (IETS928 of IETS015)) ; IETS030 : Correlation id (IETS928 of IETS007)
  • LRN — IETS029 : / ; IETS030 : /
  • FRN — IETS029 : FRN of the PN which wants to activate the pre-lodged TSD ; IETS030 : FRN
  • CRN — IETS029 : CRN ; IETS030 : CRN of the referenced pre-lodged TSD
  • MRN — IETS029 : MRN, in case the pre-lodged TSD is activated ; IETS030 : MRN of the activated TSD (in case the pre-lodged TSD was activated)

1.1.1.4. Automatic Invalidation of the expired pre-lodged TSD

Upon successful submission of a pre-lodged TSD which is registered after business validation, the pre-lodged TSD remains available for activation by a Presentation Notification for 30 days. When the pre-lodged TSD is not activated before this expiration timestamp, the pre-lodged TSD will be automatically invalidated by customs. As feedback of this automatic invalidation a TSD invalidation notification (IETS410) message is sent to the pre-lodged TSD message sender. The status of the Temporary Storage Declaration is updated to ‘Invalidated’ and cannot be processed further.

The following table summarizes the message exchange and gives an overview of the key data elements present in this message. For the full content details of this message, please refer to section Information model.

  • Sender — IETS410 : TSD@BE
  • Recipient — IETS410 : EO (IETS015)
  • Message id — IETS410 : Msg id
  • Ref to message id — IETS410 : Msg id (IETS015)
  • Correlation id — IETS410 : Correlation id (IETS928 of IETS015))
  • Invalidation initiated by customs — IETS410 : 1
  • LRN — IETS410 : /
  • FRN — IETS410 : /
  • CRN — IETS410 : CRN of the expired pre-lodged TSD
  • MRN — IETS410 : /

1.1.1.5. Invalidation of the pre-lodged TSD upon request

Besides the automatic invalidation of a pre-lodged TSD upon expiration, the Economic Operator can also request the invalidation of a successfully submitted (registered after business validation) pre-lodged TSD. It is therefore required to submit a TSD invalidation request (IETS414) message. The invalidation request contains a reference to the registered pre-lodged TSD (reference made based on the unique CRN) and reason for invalidation.

Note that it is only allowed to invalidate a pre-lodged TSD which has current ‘Pre-lodged’ status when handling the invalidation request. An invalidation request for a pre-lodged TSD that has been activated by a PN or already automatically invalidated upon expiration will be refused.           
It is not required that the invalidation request message is sent by the same message sender as the pre-lodged TSD. However, the same declarant needs to be present (see BR-PN-TS-106 in section 4.4) in the invalidation message as in the pre-lodged TSD.

The same principle of synchronous technical validation is applicable with acknowledgement (IETS928) or negative acknowledgement (IETS906) response.

Upon asynchronous business validation of the invalidation request, an invalidation notification (IETS410) or validation refused (IETS016) feedback is returned. The invalidation notification message confirms the successful invalidation and contains the CRN of the invalidated TSD. The status of the Temporary Storage Declaration is updated to ‘Invalided’ and cannot be processed further.

The validation refused message contains the list of functional errors encountered during the business processing of the invalidation request. The pre-lodged TSD is not invalidated and remains available for activation, amendment, or invalidation (status Pre-lodged).

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS414 : EO ; IETS928 : / ; IETS906 : / ; IETS410 : TSD@BE ; IETS016 : TSD@BE
  • Recipient — IETS414 : TSD@BE ; IETS928 : / ; IETS906 : / ; IETS410 : EO ; IETS016 : EO
  • Message id — IETS414 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS410 : Msg id ; IETS016 : Msg id
  • Ref to message id — IETS414 : / ; IETS928 : / ; IETS906 : / ; IETS410 : Msg id (IETS015) ; IETS016 : Msg id (IETS015)
  • Correlation id — IETS414 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS410 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928)
  • Invalidation initiated by customs — IETS414 : / ; IETS928 : / ; IETS906 : / ; IETS410 : 0 ; IETS016 : /
  • Business validation type — IETS414 : / ; IETS928 : / ; IETS906 : / ; IETS016 : 414
  • LRN — IETS414 : / ; IETS928 : / ; IETS906 : / ; IETS410 : / ; IETS016 : /
  • FRN — IETS414 : / ; IETS928 : / ; IETS906 : / ; IETS410 : / ; IETS016 : /
  • CRN — IETS414 : CRN of the pre-lodged TSD ; IETS928 : / ; IETS906 : / ; IETS410 : CRN ; IETS016 : /CRN
  • MRN — IETS414 : / ; IETS928 : / ; IETS906 : / ; IETS410 : / ; IETS016 : /

1.1.2. Combined TSD

As an alternative to the pre-lodged TSD (IETS015), it is possible to submit a combined TSD message (IETS115) upon presentation of the goods. This combined TSD message contains the same Temporary Storage Declaration data elements as for the pre-lodged TSD but now in combination with the Presentation Notification data elements.   

The same principle of synchronous technical validation is applicable with acknowledgement (IETS928) or negative acknowledgement (IETS906) response.

Upon asynchronous business validation, a validation approved (IETS028) or validation refused (IETS016) feedback is returned.           
When all business validations are passed, a validation approved message (IETS028) is returned as feedback message and the combined TSD is registered in the system with status ‘Accepted’. The validation approved message contains the MRN (Master Reference Number) as unique customs reference for the Temporary Storage Declaration.    
The validation refused message contains the list of functional errors encountered during the business validation.

The Presentation Notification data elements, which are part of the combined TSD message, will be registered automatically as a linked Presentation Notification to the Temporary Storage Declaration. It is hence not required to separately submit another Presentation Notification (IETS007).

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS115 : EO ; IETS928 : / ; IETS906 : / ; IETS028 : TSD@BE ; IETS016 : TSD@BE
  • Recipient — IETS115 : TSD@BE ; IETS928 : / ; IETS906 : / ; IETS028 : EO ; IETS016 : EO
  • Message id — IETS115 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id ; IETS016 : Msg id
  • Ref to message id — IETS115 : / ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id (IETS015) ; IETS016 : Msg id (IETS015)
  • Correlation id — IETS115 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS028 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928)
  • Business validation type — IETS115 : / ; IETS928 : / ; IETS906 : / ; IETS028 : 115 ; IETS016 : 115
  • LRN — IETS115 : LRN (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : LRN (IETS115) ; IETS016 : LRN (IETS115)
  • FRN — IETS115 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • CRN — IETS115 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • MRN — IETS115 : / ; IETS928 : / ; IETS906 : / ; IETS028 : MRN ; IETS016 : /

1.1.3. TSD amendment

It is possible for the Economic Operator to amend the TSD data elements for an already submitted (registered) Temporary Storage Declaration. To amend the Temporary Storage Declaration, it is required to submit a TSD amendment request (IETS413) message.

The same principle of synchronous technical validation is applicable with acknowledgement (IETS928) or negative acknowledgement (IETS906) response.

Upon asynchronous business validation, a validation approved (IETS028) or validation refused (IETS016) feedback is returned.

The validation approved message confirms that the amendment request passed all business validations, and the amended TSD data elements are registered as current values for the TSD. The same CRN (for pre-lodged TSD) and MRN (for activated pre-lodged TSD and combined TSD) is maintained as unique customs reference for the TSD.

Depending on the amended data elements:

  • TSD status remains ‘Pre-lodged’. For a pre-lodged TSD (current status ‘Pre-lodged’ when processing the amendment request), almost all data elements can be amended (see amendment business rules). Upon approval of the amendment request, the amended version becomes the new current TSD version which is still identified uniquely via the original CRN.

OR

  • TSD status remains ‘Accepted’ if no customs officer investigation is required. For an activated pre-lodged TSD or combined TSD (current status ‘Accepted’ when processing the amendment request), a limited set of data elements can be amended (see amendment business rules). If only amendable data elements are amended, it depends on the value of the amendable data elements if the amendment request can be processed automatically or if a customs officer investigation (manual) is required. Upon approval of the amendment request without manual customs officer investigation, the amended version becomes the new current TSD version which is still identified uniquely via the original MRN.

OR

  • TSD status is updated from ‘Accepted’ to ‘Irregularity under investigation’ if customs officer investigation is required. For an activated pre-lodged TSD or combined TSD (current status ‘Accepted’ when processing the amendment request), a limited set of data elements can be amended (see amendment business rules).        

If only amendable data elements are amended, it depends on the value of the amendable data elements if the amendment request can be processed automatically or if a customs officer investigation (manual) is required. Upon approval of the amendment request which requires manual customs officer investigation, the amended version becomes the new current TSD version with status Irregularity under investigation which is still identified uniquely via the original MRN. Note however that the TSD cannot be processed further until a customs officer decision is made.

For more details related to which data elements can be amended for the Temporary Storage Declaration and for which amendable data elements customs officer (manual) investigation is required, see section 4.5.3.

Please note that for an activated / combined TSD, amendments are only allowed before the declared goods are placed under a customs procedure or re-exported, even if only partially (BR-PN-TS-137). Also, amendments are not allowed in case of TSD irregularities, meaning that amendment requests for a TSD with a status other than ‘Pre-lodged’ or ‘Accepted’ will be rejected (BR-PN-TS-112). Finally, it is not allowed to amend a presented Temporary Storage Declaration after a Deconsolidation notification or Transfer notification has been registered (BR-PN-TS-155 and BR-PN-TS-156).

The validation refused message contains the list of functional errors encountered during the business validation of the amendment request. The TSD is not amended with the data elements present in the amendment request. Another amendment request, adhering to the business validations, can be submitted to amend the TSD.

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS413 : EO ; IETS928 : / ; IETS906 : / ; IETS028 : TSD@BE ; IETS016 : TSD@BE
  • Recipient — IETS413 : TSD@BE ; IETS928 : / ; IETS906 : / ; IETS028 : EO ; IETS016 : EO
  • Message id — IETS413 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id ; IETS016 : Msg id
  • Ref to message id — IETS413 : / ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id (IETS015) ; IETS016 : Msg id (IETS015)
  • Correlation id — IETS413 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS028 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928)
  • Business validation type — IETS413 : / ; IETS928 : / ; IETS906 : / ; IETS028 : 413 ; IETS016 : 413
  • LRN — IETS413 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • FRN — IETS413 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • CRN — IETS413 : CRN if TSD is pre-lodged ; IETS928 : / ; IETS906 : / ; IETS028 : CRN if TSD is pre-lodged ; IETS016 : CRN (IETS413)
  • MRN — IETS413 : MRN if TSD is accepted (combined TSD or activated pre-lodged TSD) ; IETS928 : / ; IETS906 : / ; IETS028 : MRN if TSD is accepted ; IETS016 : MRN (IETS413)

1.1.4. Transfer and deconsolidation

1.1.4.1. Transfer

After presentation of a Temporary Storage Declaration (Submission of a combined TSD or activation of a pre-lodged TSD), the Temporary Storage Facility Holder (Economic Operator) can notify the transfer (IETS207) for one or more consignments of a TSD with current status ‘Accepted’. Consignments can be transferred multiple times during the temporary storage monitoring period.

The same principle of synchronous technical validation is applicable with acknowledgement (IETS928) or negative acknowledgement (IETS906) response.

Upon asynchronous business validation, a validation approved (IETS028) or validation refused (IETS016) feedback is returned.

When all business validations are passed, a validation approved message (IETS028) is returned as feedback message, the TSD transfer notification status is set to ‘Approved’ and the status of the TSD is set to ‘Accepted’. The new location is registered as ‘Current location’ for each of the consignments present in the TSD transfer notification message (IETS207).

Please note that transfers are only allowed before the declared goods are placed under a customs procedure or re-exported, even if only partially (BR-PN-TS-145). Also, transfers are not allowed in case of TSD irregularities, meaning that transfer notifications for a TSD with a status other than ‘Accepted’ will be rejected (BR-PN-TS-144).

The validation refused message contains the list of functional errors encountered during the business validation.

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS207 : EO ; IETS928 : / ; IETS906 : / ; IETS028 : TSD@BE ; IETS016 : TSD@BE
  • Recipient — IETS207 : TSD@BE ; IETS928 : / ; IETS906 : / ; IETS028 : EO ; IETS016 : EO
  • Message id — IETS207 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id ; IETS016 : Msg id
  • Ref to message id — IETS207 : / ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id (IETS207) ; IETS016 : Msg id (IETS207)
  • Correlation id — IETS207 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS028 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928)
  • Business validation type — IETS207 : / ; IETS928 : / ; IETS906 : / ; IETS028 : 207 ; IETS016 : 207
  • LRN — IETS207 : LRN (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : LRN (IETS207) ; IETS016 : LRN (IETS207)
  • FRN — IETS207 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • CRN — IETS207 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • MRN — IETS207 : MRN of a valid TSD ; IETS928 : / ; IETS906 : / ; IETS028 : MRN ; IETS016 : MRN (IETS207)

1.1.4.2. Deconsolidation

After presentation of a Temporary Storage Declaration (Submission of a combined TSD or activation of a pre-lodged TSD), the Temporary Storage Facility Holder (Economic Operator) can notify the deconsolidation (IETS215) of the TSD Master Consignment into one or more House Consignments. It is only allowed to deconsolidate the TSD Master Consignment once during the temporary storage monitoring period if the Temporary Storage Declaration is not already deconsolidated upon submission.

The same principle of synchronous technical validation is applicable with acknowledgement (IETS928) or negative acknowledgement (IETS906) response.

Upon asynchronous business validation, a validation approved (IETS028) or validation refused (IETS016) feedback is returned.

When all business validations are passed, a validation approved message (IETS028) is returned as feedback message, the TSD deconsolidation notification status is set to ‘Approved’ and the status of the TSD is set to ‘Accepted’. The House Consignment details present in the TSD deconsolidation notification (IETS215) are registered by the system as part of the TSD dataset. Subsequent declarations writing off the TSD need to refer to the House Consignment details after registration, as deconsolidated Master Consignments are closed for write-off from this moment on.

Please note that a deconsolidation is only allowed before the declared goods are placed under a customs procedure or re-exported, even if only partially (BR-PN-TS-147). Also, deconsolidation is not allowed in case of TSD irregularities, meaning that a deconsolidation notification for a TSD with a status other than ‘Accepted’ will be rejected (BR-PN-TS-146).

The validation refused message contains the list of functional errors encountered during the business validation.

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS215 : EO ; IETS928 : / ; IETS906 : / ; IETS028 : TSD@BE ; IETS016 : TSD@BE
  • Recipient — IETS215 : TSD@BE ; IETS928 : / ; IETS906 : / ; IETS028 : EO ; IETS016 : EO
  • Message id — IETS215 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id ; IETS016 : Msg id
  • Ref to message id — IETS215 : / ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id (IETS215) ; IETS016 : Msg id (IETS215)
  • Correlation id — IETS215 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS028 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928)
  • Business validation type — IETS215 : / ; IETS928 : / ; IETS906 : / ; IETS028 : 215 ; IETS016 : 215
  • LRN — IETS215 : LRN (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : LRN (IETS215) ; IETS016 : LRN (IETS215)
  • FRN — IETS215 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • CRN — IETS215 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : /
  • MRN — IETS215 : MRN of a valid TSD ; IETS928 : / ; IETS906 : / ; IETS028 : MRN ; IETS016 : MRN (IETS215)

1.2. Presentation of goods outside the temporary storage procedure

As described in section 3.1.1.2 the Presentation Notification can be lodged outside the temporary storage procedure.

In most cases, a PN will be lodged outside the temporary storage procedure in order to present Union goods upon re-entry in the customs territory of the EU. In this case, the CRN attribute will be left empty, but a reference to Proof of Union Status is required within the previous document section of the presented consignments (see business rule BR-PN-TS-134 in section 4.4).

A PN can also be lodged outside the temporary storage procedure in order to present non-Union goods for which a customs declaration is available upon presentation (e.g. transit, customs warehousing, …). The CRN attribute shall contain a reference to the customs declaration in this case.[4]

Goods for which no customs declaration, no pre-lodged TSD nor a Proof of Union status is available upon presentation cannot be presented with a stand-alone Presentation Notification, as for non-Union goods legislation requires a Temporary Storage Declaration at the latest upon presentation. They shall be presented by lodging a Combined TSD (IETS115) instead.[5]

The following table summarizes the scenarios in which a PN is to be lodged outside the temporary storage procedure. The scenarios in which a PN is lodged within the temporary storage procedure (as a separate message or as part of a combined TSD) are greyed out.

  • ENS — Type of PN to be lodged upon presentation : Customs declaration
  • Yes — Type of PN to be lodged upon presentation : Yes
  • No — Type of PN to be lodged upon presentation : Yes
  • Yes — Type of PN to be lodged upon presentation : No
  • No — Type of PN to be lodged upon presentation : No

A stand-alone PN used to present Union goods shall refer to a Proof of Union Status in the Previous document section of each presented consignment.[6] Additional information about the correct reference of the Proof of union status can be found in section 4.5.4.2.2. When relevant, additionally a reference to an ENS declaration can be provided (MRN).

A stand-alone PN used to present non-Unions goods can only refer to an ENS in the Previous document section of the presented consignments. Additional information about the applicable business rules can be found in section 4.5.4.2.1.

Upon presentation of goods outside the temporary storage procedure, a Presentation Notification (IETS007) message needs to be submitted. The Presentation Notification contains the required presentation information, actors, location of goods and consignment details, and LRN (Local Reference Number) as unique reference by the Economic Operator. As opposed to a Presentation Notification (IETS007) message lodged within the temporary storage procedure, the CRN attribute (Customs Reference Number) does not refer to a pre-lodged Temporary Storage Declaration (IETS015).

The same principle of synchronous technical validation is applicable with acknowledgement (IETS928) or negative acknowledgement (IETS906) response.

Upon asynchronous business validation, a validation approved (IETS028) or validation refused (IETS016) feedback message is returned. The validation refused message contains the list of functional errors encountered during the business validation.

If all business validations are passed, a status is assigned based on the customs status of the goods (‘Accepted’ in case of non-Union goods, ‘Proof of Union Status presented’ in case of Union goods) and the Presentation Notification is registered in the system. The validation approved message (IETS028) contains the FRN (Functional Reference Number) as unique customs reference for the Presentation Notification and the status that has been assigned.

In case the Presentation Notification was lodged outside the temporary storage procedure in order to present non-Union goods (status ‘Accepted’), the presentation data will be sent to TSD, similarly to a Presentation Notification for non-Union goods lodged within the temporary storage procedure (see section 3.1.1.3). Obviously, no pre-lodged TSD will be activated since the CRN does not refer to a pre-lodged TSD, hence the status of the PN will be updated to ‘Not linked’. The message sender of the Presentation Notification is asynchronously informed of the updated PN status via the PN Linking Notification (IETS030) message.

In case the Presentation Notification was lodged outside the temporary storage procedure in order to present Union goods (status ‘Proof of Union Status presented’), no presentation data will be sent to TSD, the PN status will remain ‘Proof of Union Status presented’ and no PN Linking Notification (IETS030) message will be sent to the IETS007 message sender.

The following table summarizes the exchange of the different messages / responses and gives an overview of the key data elements present in this message. For the full content details of these messages, please refer to section Information model.

  • Sender — IETS007 : EO ; IETS928 : / ; IETS906 : / ; IETS028 : PN@BE ; IETS016 : PN@BE ; IETS030 : PN@BE
  • Recipient — IETS007 : PN@BE ; IETS928 : / ; IETS906 : / ; IETS028 : EO ; IETS016 : EO ; IETS030 : EO
  • Message id — IETS007 : Msg id (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id ; IETS016 : Msg id ; IETS030 : Msg id
  • Ref to message id — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : Msg id (IETS007) ; IETS016 : Msg id (IETS007) ; IETS030 : Msg id (IETS007)
  • Correlation id — IETS007 : / ; IETS928 : Correlation id ; IETS906 : / ; IETS028 : Correlation id (IETS928) ; IETS016 : Correlation id (IETS928) ; IETS030 : Correlation id (IETS928)
  • Business validation type — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : 007 ; IETS016 : 007 ; IETS030 : /
  • LRN — IETS007 : LRN (provided by EO) ; IETS928 : / ; IETS906 : / ; IETS028 : LRN (IETS007) ; IETS016 : LRN (IETS007) ; IETS030 : /
  • FRN — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : FRN ; IETS016 : / ; IETS030 : FRN
  • CRN — IETS007 : / (Union goods)   Customs declaration reference (non-Union goods) ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : / ; IETS030 : /
  • MRN — IETS007 : / ; IETS928 : / ; IETS906 : / ; IETS028 : / ; IETS016 : / ; IETS030 : /

1.3. Interaction overview

1.4. TSD Lifecycle

The following diagram summarizes the TSD lifecycle related to the above-described message exchanges.

1.4.1. Pre-lodged TSD lifecycle

The pre-lodged TSD lifecycle starts with the successful submission of a pre-lodged TSD (status ‘PRE-LODGED’), of which the TSD message sender is notified by means of IETS028 response message.

For a pre-lodged TSD, following status changes can occur:

  • PRE-LODGED — To : INVALIDATED ; Notified with : IETS410 ; Triggered by : ·        successful submission of a TSD invalidation request ·        automatic invalidation upon expiration of the 30 days time limit for presentation
  • PRE-LODGED — To : ACCEPTED ; Notified with : IETS029 ; Triggered by : ·        submission of a PN referring to the CRN of pre-lodged TSD, resulting in a successful attempt to activate the pre-lodged TSD (goods presented at an authorized or designated location or an approved place)
  • PRE-LODGED — To : IRREGULARITY UNDER INVESTIGATION ; Notified with : IETS029 ; Triggered by : ·        submission of a PN referring to the CRN of pre-lodged TSD, resulting in a successful attempt to activate the pre-lodged TSD (goods not presented at an authorized or designated location or an approved place)

When a control is recommended by customs for a pre-lodged TSD, the pre-lodged TSD / pre-lodged TSD amendment sender will be informed via an Intended control notification message (IETS460) only in case the declarant is holder of AEO status. The status of the pre-lodged TSD will remain ‘PRE-LODGED’ and will only be updated in case the control is confirmed upon activation (see 3.4.2).

The pre-lodged TSD lifecycle ends in case of invalidation. In case of activation, the temporary storage procedure starts, the TSD data is registered within custom’s goods accounting and the TSD lifecycle starts.

1.4.2. Combined/activated TSD lifecycle

The TSD lifecycle starts with:

  • the successful submission of a combined TSD (status ‘ACCEPTED’), of which the combined TSD message sender is notified by means of IETS028 response message, or;
  • the successful activation of a pre-lodged TSD (status ‘ACCEPTED’ or ‘IRREGULARITY UNDER INVESTIGATION’), of which the pre-lodged TSD message sender is notified by means of IETS029 message (see 3.4.1).

These response messages will contain the expiration date for temporary storage, before which all declared goods need to be placed under a customs procedure or re-exported. Before the expiration date for temporary storage, control and irregularity events can occur, which need to be resolved before release of the goods. Upon expiration date for temporary storage, the system will determine if all goods have been placed under a customs procedure or re-exported and end temporary storage if so. If not, or in case other irregularities would require so, corrective measures are to be taken in order to regularize the situation before temporary storage can be ended.

1.4.2.1. Status updates in case of control

Each TSD submission / activation, TSD amendment request, TSD deconsolidation notification and TSD transfer notification can induce a control, which will be notified to the relevant message sender(s) with an intended control notification message (IETS460).

When a control is recommended for a combined / activated TSD, the status of the declaration will be changed to ‘UNDER CONTROL’. The status change will be communicated to the relevant message sender(s)[7] with a Status update notification message (IETS095). Any further status updates as a result of the outcome of the control result will also be communicated with this message.

Please refer to section 4.3.8 and 4.3.6 for the full message details.

The table below summarizes the status updates that can occur in case of controls:

  • ACCEPTED — To : UNDER CONTROL ; Notified with : IETS095 ; Triggered by : ·        Intended control notification (IETS460) sent for: o   Activated pre-lodged TSD o   Combined TSD o   Activated / combined TSD amendment o   Transfer notification o   Deconsolidation notification
  • UNDER CONTROL — To : ACCEPTED ; Notified with : IETS095 ; Triggered by : ·        Control result(s) registered for the recommended controls listed above – no irregularities found
  • UNDER CONTROL — To : IRREGULARITY UNDER INVESTIGATION ; Notified with : IETS095 ; Triggered by : ·        Control result(s) registered for the recommended controls listed above – irregularities found

1.4.2.2. Status updates in case of irregularity

When an irregularity occurs during the lifecycle of a combined / activated TSD, the status will become ‘IRREGULARITY UNDER INVESTIGATION’. In this case, the TSD cannot be processed further until a customs officer decision is made. An irregularity can occur due to various reasons:

  • upon activation of a pre-lodged TSD, in case the goods are not presented at an authorised or designated location or an approved place (see 3.1.1.3);
  • upon approval of a TSD amendment request which requires manual customs officer investigation (see 3.1.3);
  • upon registration of a control result for a combined / activated TSD, in case irregularities have been found (see 3.4.2.1).

A customs officer will decide if the goods can be maintained in temporary storage (status ‘ACCEPTED’) or if measures are required (status ‘MEASURES REQUIRED’). In case the status is changed to ‘ACCEPTED’, the TSD can be processed further and goods can be placed under a customs procedure or re-exported again. In case the status is changed to ‘MEASURES REQUIRED’, the TSD cannot be processed further and corrective measures are required in order to regularize the situation (see 3.4.2.3).

This status update will be communicated to the relevant TSD message sender(s) via a Status update notification (IETS095). This message contains a summary of the TSD details including the updated status (and reason). For the full content details of this message, please refer to section 4.3.6).

The table below summarizes the status updates that can occur in case of irregularities:

  • IRREGULARITY UNDER INVESTIGATION — To : ACCEPTED ; Notified with : IETS095 ; Triggered by : ·        Customs officer approval of a TSD irregularity
  • IRREGULARITY UNDER INVESTIGATION — To : MEASURES REQUIRED ; Notified with : IETS095 ; Triggered by : ·        Customs officer refusal of a TSD irregularity

1.4.2.3. Status updates at the end of temporary storage

Upon expiration of the timer for temporary storage, the TSD status will be updated to ‘TEMPORARY STORAGE ENDED’ in case all goods have been placed under a customs procedure or re-exported, to be notified to the relevant message sender(s) with an End of temporary storage notification (IETS045).

In case not all goods have been placed under a customs procedure or re-exported, the TSD status well be updated to ‘MEASURES REQUIRED’, to be notified to the relevant message sender(s) with a Status update notification (IETS095). In this case, measures will be taken in order regularize the situation. Upon confirmation of a customs officer, the status will be updated from ‘MEASURES REQUIRED’ to ‘TEMPORARY STORAGE ENDED’. This will be notified to the relevant message sender(s) with an End of temporary storage notification (IETS045)

Via the End of temporary storage notification (IETS045), the recipient is informed that the temporary storage procedure has been ended for the declared goods of the Temporary Storage Declaration. This message contains a summary of the TSD temporary storage details including the list of linked subsequent customs declarations. For the full content details of this message, please refer to section 4.3.5.

The table below summarizes the status updates that can occur at the end the temporary storage procedure:

  • ACCEPTED / IRREGULARITY UNDER INVESTIGATION / UNDER CONTROL — To : MEASURES REQUIRED ; Notified with : IETS095 ; Triggered by : ·        Not all goods have been declared in a subsequent customs procedure at the end of the temporary storage period
  • ACCEPTED / IRREGULARITY UNDER INVESTIGATION / UNDER CONTROL — To : TEMPORARY STORAGE ENDED ; Notified with : IETS045 ; Triggered by : ·        All goods have been declared in a subsequent customs procedure at the end of the temporary storage period
  • MEASURES REQUIRED — To : TEMPORARY STORAGE ENDED ; Notified with : IETS045 ; Triggered by : ·        During the temporary storage period an event occurred due to which the temporary storage could not be continued; measures have been taken to regularise this situation ·        Not all goods have been declared in a subsequent customs procedure at the end of the temporary storage period; measures have been taken to regularise this situation

1.5. PN Lifecycle

The following diagram summarizes the PN lifecycle related to the above-described message submissions:

  • Status after successful submission of a Presentation Notification (IETS007)

o   Non-Union goods: status ‘ACCEPTED’

o   Union goods: status ‘PROOF OF UNION STATUS PRESENTED’

  • Status after successful submission of a combined TSD – The presentation notification details part of the combined TSD are registered as a Presentation Notification which is immediately linked to the TSD: status ‘LINKED’

  • PN Non-Union goods status transition after a TSD activation attempt (PN linking)

o   Successful – pre-lodged TSD activated: status ‘ACCEPTED’ to ‘LINKED’

o   Not successful – no pre-lodged TSD activated: status ‘ACCEPTED’ to ‘NOT LINKED’

[1] https://taxation-customs.ec.europa.eu/customs-4/union-customs-code/ucc-legislation_en

[2] Belgian customs also provides a user interface for economic operators in order to meet these legal obligations. This Message Implementation Guide however is limited to the web-service-enabled message exchange.

[3] The obligation to lodge a TSD may only be waived in case a customs declaration has been lodged before the goods are presented to customs or at the latest at the time of presentation of the goods to customs it has been determined that the goods have obtained the status of Union goods. A stand-alone PN should only be lodged in one of those cases. Goods for which no customs declaration, no pre-lodged TSD nor a Proof of Union status is available upon presentation, shall be presented by lodging a Combined TSD (IETS115) instead of a stand-alone Presentation Notification.

[4] If a customs declaration is available upon presentation, goods are presented within the customs procedure. In addition to this, IETS007 is required in case an ENS was lodged, in order to close the ENS lifecycle. If no ENS was lodged, IETS007 is not mandatory, but it can be requested by local customs.

[5] In this case, the ENS lifecycle will be closed with the presentation details included in IETS115 message. (see 3.1.2).

[6] All document types from CL014 applicable to PN Previous document type, except N355 (ENS), are considered to be a Proof of Union status. If the one of these previous document types is used by the declarant, the system will assign the status “Proof of Union status presented” to the PN. By assigning this status, customs acknowledges the presentation of the goods, not the validity of the proof as such. When referring to a Proof of Union status as a previous document of a stand-alone PN, the declarant needs to assure legal compliance of the referenced documents and keep them at disposal of customs in order to be able to check their validity.

[7] TSD current version message sender, and if applicable to all senders of an approved TSD Transfer notification and an approved TSD Deconsolidation notification

Source : https://mgi-team.atlassian.net/wiki/spaces/DOCI5/pages/3280601089