TITLE I
Structure and content of the EDI transit declaration
Chapter I
Structure of the EDI transit declaration
>TABLE>
Chapter II
Particulars (data) of the EDI transit declaration
Particulars entered into the different boxes of the SAD document, as defined in Annexes VII and IX, will be used for the EDI transit declaration where the formalities are carried out using a data-processing technique in association with, or replaced by a code if appropriate.
Additional codes presented in Annex IX shall equally be applied.
In box 15 "Country of dispatch/export" and in box 17 "Country of destination" textual information shall be replaced by the proper code.
Additional data elements to be inserted are as follows:
LRN - local reference number nationally defined and allocated by the user in agreement with the customs authorities, to identify each single declaration,
authorised/agreed location of goods or customs subplace - precise indication of the place where the goods can be examined, if appropriate in coded form,
LNG - language code used to define the language in which the uncoded information in question is given,
sensitive quantity - quantity of declared sensitive goods according to Annex VIII, required to perform the guarantee check and registration,
sensitive goods code - enter the code associated, when the case occurs, to the relevant HS6 commodity code of the sensitive goods listed in Annex VIII of Appendix II,
a transit declaration made in accordance with Article 23f of Appendix I shall include the following information:
an indication "simplified procedure" using the appropriate code,
the identification measures applied, and
the period within which the goods must be presented at the office of destination.
TITLE II
Structure and content of the anticipated arrival message from the office of departure to the office of destination (AAR)
Chapter I
Structure of the AAR message
>TABLE>
Chapter II
The particulars (data) of the AAR message
The AAR message shall be based on data derived from the transit declaration presented in Chapter I (as amended by the trader and/or revised by the competent authorities) and completed using the additional data presented below:
diversion prohibited - the attribute has to be used as a flag, its value can be either "0" ("no") or "1" ("yes"),
declaration acceptance date - state the date when the transit declaration was accepted at the office of departure,
issuing date - state the date when the anticipated arrival record message (AAR) is issued at the office of departure,
movement reference number (MRN).
>TABLE>
Field 1 and 2 as explained above.
Field 3 has to be filled in with an identifier for the transit transaction. The way that field is used is the responsibility of national administrations but each transit transaction handled for one year within the given country must have a unique number. National administrations that want the office reference number of the customs authorities included in the MRN, could use up to the first six characters to insert the national number of the office.
Field 4 has to be filled in with a value that is a check digit for the whole MRN. This field allows error detection when capturing the whole MRN.
TITLE III
Structure and content of the arrival advice message from the office of destination to the office of departure
Chapter I
Structure of the arrival advice message
>TABLE>
Chapter II
The particulars (data) of the arrival advice message
MRN - movement reference number structured as presented in Annex VIIb, Title II,
arrival date - state the date when the movement arrived at the office of destination,
office reference number of the customs authorities structured as presented in Annex IXa.
TITLE IV
Structure and content of the control results message from the office of destination to the office of departure
Chapter I
Structure of the control results message
>TABLE>
Chapter II
The particulars (data) of the control results message
The control results message shall be based on the data derived from the anticipated arrival record message (AAR) presented in Title II, Chapter II.
Additional data elements to be inserted are as follows:
enquiry engaged at destination,
waiting for discrepancies resolution,
control results code as presented in Annex IXa,
control data (box I),
state of seals,
en route event: indicate the place and the country in which the event occurs,
incident flag,
incident information (box 56),
incident information LNG,
endorsement date (box G),
endorsement authority (box G),
endorsement authority LNG,
endorsement place (box G),
endorsement place LNG,
endorsement country (box G),
new transport means identity (box 55),
new transport means identity LNG,
new transport means nationality (box 55),
new seals number (box F),
new seals identity (box F),
new seals identity LNG,
endorsement date (box F),
endorsement authority (box F),
endorsement authority LNG,
endorsement place (box F),
endorsement place LNG,
endorsement country (box F),
new container number (box 55),
control indicator,
description,
description LNG,
corrected value.`