02016R0323 — EN — 13.02.2020 — 002.001

This text is meant purely as a documentation tool and has no legal effect. The Union's institutions do not assume any liability for its contents. The authentic versions of the relevant acts, including their preambles, are those published in the Official Journal of the European Union and available in EUR-Lex. Those official texts are directly accessible through the links embedded in this document

Amended by:









▼B

COMMISSION IMPLEMENTING REGULATION (EU) 2016/323

of 24 February 2016

laying down detailed rules on cooperation and exchange of information between Member States regarding goods under excise duty suspension pursuant to Council Regulation (EU) No 389/2012







CHAPTER I

GENERAL PROVISIONS

Article 1

Subject matter

For the purposes of cooperation and exchange of information between Member States regarding goods under excise duty suspension, this Regulation lays down detailed rules concerning the following:

(a) the structure and content of the mutual administrative assistance documents exchanged through the computerised system referred to in Article 2 (8) of Regulation (EU) No 389/2012 for the purposes of Articles 8, 15 and 16 of that Regulation;

(b) the structure and content of communications of feedback on follow-up action taken as a result of cooperation on request or of optional communication of information;

(c) the rules and procedures to be used by competent authorities exchanging mutual administrative assistance documents;

(d) the structure and content of fall-back mutual administrative assistance documents and the rules and procedures relating to their use.

▼M1

Article 2

Definition

For the purposes of this Regulation, ‘movement’ means a movement between two or more Member States of goods under excise duty suspension within the meaning of Chapter IV of Directive 2008/118/EC.

▼B

Article 3

Structure and content of mutual administrative assistance documents

1. Mutual administrative assistance documents shall be drawn up in accordance with Annex I.

2. Where codes are required for the completion of certain data fields in the mutual administrative assistance documents in accordance with Annex I to this Regulation, the codes listed in Annex II to this Regulation, Annex II to Commission Implementing Regulation (EU) No 612/2013 ( 1 ) and Annex II to Commission Regulation (EC) No 684/2009 ( 2 ) shall be used as set out in the tables of Annex I to this Regulation.







CHAPTER II

COOPERATION ON REQUEST







SECTION I

Requests for download of information contained in the computerised system

Article 4

Request for download of information where the administrative reference code of a movement is known to the requesting authority

1. Where the administrative reference code of the electronic administrative document under cover of which a movement takes place, assigned in accordance with the third subparagraph of Article 21(3) of Directive 2008/118/EC, is known to the requesting authority, it may make a request for any document referred to in Annex I to Regulation (EC) No 684/2009 and any other document relating to the movement.

For that purpose the requesting authority shall send a ‘Movement download request’ document, as set out in Table 1 of Annex I, to the requested authority in the Member State of dispatch. The request shall state the administrative reference code of the electronic administrative document under cover of which the movement takes place.

2. Where the administrative reference code is known to the requested authority, it shall respond to requests made in accordance with paragraph 1 using a ‘Movement download answer’ document, as set out in Table 2 of Annex I, indicating the status of the movement.

The requested authority shall also send a ‘History of a movement’ document, as set out in Table 3 of Annex I, containing a copy of the electronic administrative document under cover of which the movement takes place and of any other documents relating to that movement.

3. Where the administrative reference code is not known to the requested authority, it shall respond to requests made in accordance with paragraph 1 using a ‘Movement download answer’ document with the ‘Status’ data element set to ‘None.’

Article 5

Request for download of information where the administrative reference code is unknown to the requesting authority

1. Where the administrative reference code or codes of one or more electronic administrative documents for which the requesting authority is searching are not known and the requesting authority believes another Member State to be the Member State of dispatch, the requesting authority may request a search to be carried out by the competent authority of another Member State for a list of electronic administrative documents under cover of which relevant movements take place.

For that purpose, the requesting authority shall send a ‘Common request’ document, as set out in Table 4 of Annex I, to the requested authority. The request shall state the relevant search criteria and include any information which supports the selection of those criteria.

2. The requested authority shall respond to requests made in accordance with paragraph 1 by returning a list of electronic administrative documents matching the search criteria selected in accordance with the second subparagraph of paragraph 1, identified by their administrative reference codes using the ‘List of e-AD as a result of a general query’ document, as set out in Table 5 of Annex I.

3. Where no document meets the search criteria selected in accordance with the second subparagraph of paragraph 1, or the number of administrative reference codes meeting the selected search criteria is greater than 99, the requested authority shall send the requesting authority a ‘Refusal of common request’ document, as set out in Table 6 of Annex I.







SECTION II

Requests for information not contained in the computerised system

Article 6

Requests for information and administrative enquiries

1. Requests for information regarding goods under excise duty suspension that is not contained in the computerised system shall be made by sending an ‘Administrative cooperation common request’ document, as set out in Table 7 of Annex I. The request type shall be set to ‘Administrative cooperation’.

2. Each request made in accordance with paragraph 1 may concern one or more economic operators registered in the Member State of the requesting authority in accordance with Article 19(1)(a) of Regulation (EU) No 389/2012. It shall concern no more than one economic operator registered in the Member State of the requested authority.

3. Having completed any necessary enquiries, the requested authority shall send the results of those enquiries to the requesting authority by means of an ‘Administrative cooperation results’ document, as set out in Table 10 of Annex I.

▼M2







SECTION IIA

Requests for manual closure

Article 6a

Request for manual closure

For the purpose of Article 8(1) of Regulation (EU) No 389/2012, when the movement of excise goods under duty suspension arrangement cannot be closed under Article 24 or 25 of Directive 2008/118/EC, the requesting authority may request the competent authority in the Member State of dispatch to close a movement of excise goods under excise duty suspension manually. Such a request shall be made by sending a ‘Manual Closure Request’ document set out in Table 15 of Annex I.

▼B







SECTION III

Time limits and refusals

Article 7

Time limits

1. A requesting authority may remind a requested authority that it has not yet responded to a previous request for cooperation by sending a ‘Reminder message for administrative cooperation’ document, as set out in Table 9 of Annex I.

2. Where the requested authority does not respond to a request within the time limits provided for in Article 11(1) of Regulation (EU) No 389/2012 it shall send information on the reasons for the failure using an ‘Answer message’ document, as set out in Table 8 of Annex I to this Regulation.

Article 8

Refusal to cooperate

▼M1

Where the requested authority refuses to handle a request for information, to carry out an administrative enquiry relating to the requested information, or to provide the information requested, it shall notify the requesting authority by means of an ‘Answer message’ document, as set out in Table 8 of Annex I to this Regulation.

▼B

It shall send such notification as soon as it has taken its decision and in any event within three months of receipt of the request.







CHAPTER III

EXCHANGE OF INFORMATION WITHOUT PRIOR REQUEST

Article 9

Optional exchange of information

1. In cases other than those referred to in paragraph 2, optional exchange of information provided for in Article 16 of Regulation (EU) No 389/2012 shall be carried out using an ‘Administrative cooperation results’ document, as set out in Table 10 of Annex I to this Regulation.

2. Where the optional exchange of information concerns the results of a documentary or physical control of goods during a movement, the results shall be sent using a ‘Control report’ document, as set out in Table 11 of Annex I.

Article 10

Mandatory exchange of information — goods under excise duty suspension covered by the provisions of Chapter III of Directive 2008/118/EC or goods received by a registered consignee

Where one of the cases referred to in points (a) to (e) of Article 15(1) of Regulation (EU) No 389/2012 is detected as a result of a documentary or physical control of goods at the premises of a registered consignee within the meaning of Article 4(9) of Directive 2008/118/EC (hereinafter referred to as ‘registered consignee’) or of an authorised warehouse keeper within the meaning of Article 4(1) of that Directive (hereinafter referred to as ‘authorised warehouse keeper’), the mandatory transmission of the necessary information shall be carried out using an ‘Administrative cooperation results’ document, as set out in Table 10 of Annex I to this Regulation.

The ‘Administrative cooperation results’ document shall be sent to the competent authorities in the Member State concerned within seven days of the control.

Article 11

Mandatory exchange of information — control report

Where one of the cases referred to in points (a) to (e) of Article 15(1) of Regulation (EU) No 389/2012 is detected as a result of a documentary or physical control of goods during a movement, the mandatory transmission of the control report shall be carried out using a ‘Control report’ document, as set out in Table 11 of Annex I to this Regulation.

The ‘Control report’ document shall be sent to the competent authorities in the Member States concerned within seven days of the control.

Article 12

Mandatory exchange of information — definitive interruption of a movement

Where a competent authority becomes aware of the definitive interruption of a movement due to one of the cases referred to in points (a) to (e) of Article 15(1) of Regulation (EU) No 389/2012, the mandatory transmission of that information shall be carried out using an ‘Interruption of movement’ document, as set out in Table 13 of Annex I to this Regulation.

The ‘Interruption of movement’ document shall be sent to the competent authorities in the Member States concerned within one day of the moment when the competent authority referred to in the first paragraph becomes aware of the definitive interruption.

Article 13

Mandatory exchange of information — alert or rejection notification

Where a competent authority becomes aware that goods under excise duty suspension dispatched to a registered consignee or an authorised warehouse keeper had not been requested, or that the content of the electronic administrative document concerning goods under excise duty suspension dispatched to a registered consignee or an authorised warehouse keeper is incorrect, and the competent authority suspects that this is due to one of cases referred to in points (a) to (c) or (e) of Article 15(1) of Regulation (EU) No 389/2012, it shall send an ‘Alert or rejection of an e-AD’ document, as set out in Table 14 of Annex I to this Regulation, to the competent authority of the Member State of dispatch.

The ‘Alert or Rejection of an e-AD’ document shall be sent to the competent authority of the Member State of dispatch within one day of the moment when the competent authority becomes aware of the facts referred to in the first paragraph.

Article 14

Mandatory exchange of information — event reports

Where a competent authority becomes aware of facts concerning a movement other than those set out in Articles 10, 11, 12 or 13 and the competent authority suspects that they relate to one of the cases in points (a) to (e) of Article 15(1) of Regulation (EU) No 389/2012, the mandatory transmission of the necessary information shall be carried out using an ‘Event report’ document, as set out in Table 12 of Annex I to this Regulation.

The ‘Event report’ document shall be sent within seven days of the moment when the competent authority becomes aware of the facts referred to in the first paragraph.

▼M2

Article 14a

Mandatory exchange of information — manual closure

For the purpose of Article 15(1)(c) of Regulation (EU) No 389/2012, where a competent authority of the Member State of dispatch has received evidence of the completion of a movement of excise goods under duty suspension arrangement and the movement cannot be closed under Article 24 or Article 25 of Directive 2008/118/EC, it shall decide whether to close the movement of excise goods manually.

The competent authority of the Member State of dispatch shall notify the competent authorities of the Member State of destination or of the Member State of export of its decision.

The notification of a decision to manually close a movement shall be made by means of a ‘Manual Closure Response’ document, set out in Table 16 of Annex I to this Regulation.

▼B







CHAPTER IV

COMMON PROVISIONS ON THE EXCHANGE OF INFORMATION

Article 15

Unavailability of the computerised system and the use of the fall-back mutual administrative assistance document

1. For the purposes of Article 15(4) of Regulation (EU) No 389/2012, Member States may consider the computerised system to be unavailable in the following circumstances:

(a) the computerised system is unavailable due to hardware or telecommunication failures;

(b) network problems occur which are not under the direct control of the Commission or the Member State concerned;

(c) force majeure;

(d) scheduled maintenance notified at least 48 hours before the planned start of the maintenance period.

2. For the purposes of the second subparagraph of Article 9(1) and Article 15(4) of Regulation (EU) No 389/2012 the fall-back mutual administrative assistance document shall identify the type of mutual administrative assistance document that it is replacing. The requisite information shall be drawn up as set out in the tables of Annex I to this Regulation in the form of data elements, expressed in the same manner as in the mutual administrative assistance document. All data elements and data groups and subgroups to which those data elements belong shall be identified by numbers and letters referred to in columns A and B of the corresponding tables of Annex I.

The fall-back mutual administrative assistance document shall be exchanged by any means agreed between the competent authorities concerned.

3. As soon as the availability of the computerised system is restored, the information exchanged in accordance with paragraph 2 shall be sent using the computerised system in the form of the appropriate mutual administrative assistance documents.

▼M1

Article 16

Feedback on follow-up action taken as a result of exchange of information

A request for feedback and feedback on follow-up action in accordance with Article 8(5), Article 15(2) or Article 16(2) of Regulation (EU) No 389/2012 shall be made by means of an ‘Administrative cooperation results’ document, as set out in Table 10 of Annex I to this Regulation. The feedback shall be provided by sending a further ‘Administrative cooperation results’ document, as set out in Table 10.

▼B







CHAPTER V

FINAL PROVISIONS

Article 17

Entry into force

This Regulation shall enter into force on the twentieth day following that of its publication in the Official Journal of the European Union.

This Regulation shall be binding in its entirety and directly applicable in all Member States.









ANNEX I

STRUCTURE OF COMMON MESSAGES

Electronic messages used for the purpose of information exchange concerning excise goods under duty suspension

EXPLANATORY NOTES

(1) The data elements of the electronic messages used for the purpose of information exchange concerning excise goods under duty suspension using the computerised system referred to in Article 21(2) of Directive 2008/118/EC and in Article 2(17) of Regulation (EU) No 389/2012 are structured in data groups and, where applicable, data subgroups. Details regarding the data and their use are presented in the tables of this Annex, in which:

(a) column A sets out the numeric code (number) attributed to each data group and data subgroup; each subgroup follows the sequence number of the data (sub)group of which it forms part (for example: where the data group number is 1, one data subgroup of that group is 1.1 and one data subgroup of that subgroup is 1.1.1);

(b) column B sets out the alphabetic code (letter) attributed to each data element in a data (sub)group;

(c) column C identifies the data (sub)group or data element;

(d) column D indicates for each data (sub)group or data element a value indicating whether the insertion of the corresponding data is: — ‘R’ (required), meaning that the data must be provided; when a data (sub)group is ‘O’ (optional) or ‘C’ (conditional), data elements within that group can still be ‘R’ (required) when the competent authorities of the Member State have decided that the data in that (sub)group must be completed or when the condition for the enclosing data (sub)group is fulfilled, — ‘O’ (optional), meaning that the insertion of the data is optional for the person submitting the message (the consignor or consignee) except where a Member State has stipulated that the data are required in accordance with the option provided for in column E for some of the optional data (sub)groups or data elements, — ‘C’ (conditional), meaning that the use of the data (sub)group or data element depends on other data (sub)groups or data elements in the same message;

(e) column E sets out the condition(s) on which the insertion of data is conditional, specifies the use of the optional data where applicable and indicates which data must be provided by the competent authorities;

(f) column F provides explanations, where necessary, concerning the completion of the message;

(g) column G indicates: — for some data (sub)groups a number followed by the character ‘x’ indicating how many times the data (sub)group can be repeated in the message (default = 1), — for each data element, except for data elements indicating the time or date, the characteristics identifying the data type and the data length; the codes for the data types are as follows: a alphabetic, n numeric, an alphanumeric. The number following the code indicates the admissible data length for the data element concerned. The two dots before the length indicator mean that the data have no fixed length, but can have up to a number of digits, as specified by the length indicator. A comma in the data length means that the data can hold decimals, the number before the comma indicating the total length of the attribute, and the number after the comma indicating the maximum number of digits after the decimal point. For data elements indicating the time or date, the mention ‘date’, ‘time’ or ‘dateTime’ means that the date, the time or the date and time must be given using the ISO 8601 standard for representation of dates and time.

(2) The following abbreviations are used in the tables of this Annex:

— e-AD: electronic administrative document,

— ARC: administrative reference code,

— SEED: system for exchange of excise data (the electronic database referred to in Article 19(1) of Regulation (EU) No 389/2012),

— CN Code: Combined Nomenclature code,

— MRN: movement reference Number,

— LRN: local reference number,

— LNG: language,

— VAT: value added tax,

— ACO: administrative cooperation.

▼M1







Table 1 (as referred to in Article 4(1)) Movement Download Request A B C D E F G 1 ATTRIBUTES R a Request Correlation Identifier R The value of <Request Correlation Identifier> is unique per Member State. an..44 2 EXCISE MOVEMENT e-AD R a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2 c National Movement Information Requested flag R The format of Boolean is digital: ‘0’ or ‘1’ (‘0’ = No or False; ‘1’ = Yes or True) n1 d Status R The possible values are: X01 = Accepted X02 = Cancelled X03 = Delivered X04 = Diverted X05 = Rejected X06 = Replaced X07 = e-AD Manually closed X08 = Refused X09 = None X10 = Partially Refused X11 = Exporting X12 = Accepted for Export X13 = Stopped an3 e Last Received Message Type R The possible values are: IE801 = E-AD IE803 = NOTIFICATION OF DIVERTED E-AD IE807 = INTERRUPTION OF MOVEMENT IE810 = CANCELLATION OF AN E-AD IE813 = CHANGE OF DESTINATION IE818 = ACCEPTED OR (PARTIALLY) REFUSED REPORT OF RECEIPT/EXPORT IE819 = ALERT OR REJECTION OF AN E-AD IE829 = NOTIFICATION OF ACCEPTED EXPORT IE839 = REJECTION OF E-AD FOR EXPORT IE905 = STATUS RESPONSE None = NONE Note: The IE905 should be included only when the e-AD is manually closed. an..5 f Status Request Message Type O The possible values are: 1 = Status Synchronisation Request 2 = Movement History Request n1







Table 2 (as referred to in the first subparagraph of Article 4(2)) Movement Download Answer A B C D E F G 1 ATTRIBUTES R a Request Correlation Identifier R The value of <Request Correlation Identifier> is unique per Member State. an..44 2 EXCISE MOVEMENT e-AD R a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2 c Status R The possible values of <Status> are: X01 = Accepted X02 = Cancelled X03 = Delivered X04 = Diverted X05 = Rejected X06 = Replaced X07 = e-AD Manually closed X08 = Refused X09 = None X10 = Partially Refused X11 = Exporting X12 = Accepted for Export X13 = Stopped an3 d Last Received Message Type R The possible values are: IE801 = E-AD IE803 = NOTIFICATION OF DIVERTED E-AD IE807 = INTERRUPTION OF MOVEMENT IE810 = CANCELLATION OF AN E-AD IE813 = CHANGE OF DESTINATION IE818 = ACCEPTED OR (PARTIALLY) REFUSED REPORT OF RECEIPT/EXPORT IE819 = ALERT OR REJECTION OF AN E-AD IE829 = NOTIFICATION OF ACCEPTED EXPORT IE839 = REJECTION OF E-AD FOR EXPORT IE905 = STATUS RESPONSE None = NONE Note: The IE905 should be included only when the e-AD is manually closed. an..5







Table 3 (as referred to in the second subparagraph of Article 4(2)) History of a movement A B C D E F G 1 ATTRIBUTES R a Request Correlation Identifier R The value of <Request Correlation Identifier> is unique per Member State. an..44 2 All validated e-ADs R The set of all draft electronic administrative documents and electronic administrative documents relating to the movement, the structure of which is set out in Table 1 of Annex I to Regulation (EC) No 684/2009 99x 3 All Reports of Receipt/Export O The set of all Report of receipt/Report of export messages relating to the movement, the structure of which is set out in Table 6 of Annex I to Regulation (EC) No 684/2009 99x 4 Last Notification of Diverted e-AD O The content of the last Notification of change of destination/Notification of splitting message relating to the movement, the structure of which is set out in Table 4 of Annex I to Regulation (EC) No 684/2009 1x 5 All Control Reports O The set of all Control Report messages relating to the movement, the structure of which is set out in Table 11 99x 6 All Event Reports O The set of all Event Report messages relating to the movement, the structure of which is set out in Table 12 99x 7 All explanations of delay for delivery O The set of all Explanation on delay for delivery messages relating to the movement 99x 7.1 ATTRIBUTES R a Message Role R The possible values are: 1 = Explanation on delay for sending the report of receipt/export 2 = Explanation on delay for giving destination n1 b Date and Time of Validation of Explanation on Delay C — ‘R’ after successful validation — Does not apply otherwise dateTime c Submitter Type R The possible values are: 1 = Consignor 2 = Consignee n1 d Submitter Identification R an13 Rule072 R The <Submitter Identification> is a valid trader excise number. (see Code list 1 in Annex II to Regulation (EU) No 612/2013) an13 e Explanation Code R (see Code list 7 in Annex II) n..2 f Complementary Information C — ‘R’ if <Explanation Code> is ‘Other’ — ‘O’ Otherwise (see Explanation Code in box 7.1e) an..350 g Complementary Information_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 7.2 EXCISE MOVEMENT e-AD R a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2 8 All Notifications of Export O The set of all Notification of accepted export messages relating to the movement 99x 8.1 ATTRIBUTES R a Date and Time of Issuance R dateTime 8.2 EXCISE MOVEMENT e-AD R 99x a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2 8.3 TRADER Consignee C Does not apply if <Message Type> of all concerned e-ADs is ‘Submission for export (local clearance)’ — ‘R’ otherwise a Trader Identification C — ‘R’ if <Destination Type Code> is: — — ‘Destination - Tax warehouse’ — ‘Destination - Registered consignee’ — ‘Destination - Temporary registered consignee’ — ‘Destination - Direct delivery’ — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise The possible values of <Trader Identification> are described in the following table:



Destination Type Code TRADER CONSIGNEE. Trader Identification TRADER Place of Delivery.Trader Identification 1 - Destination- Tax warehouse Excise number (1) Tax Warehouse Reference (Excise Number) (5) 2 - Destination- Registered consignee Excise number (2) Any identification (*1) 3 - Destination- Temporary registered consignee Temporary authorisation reference (4) Any identification (*1) 4 - Destination- Direct delivery Excise number (3) (Does not apply) 5 - Destination- Exempted consignee (Does not apply) Any identification (*1) 6 - Destination– Export VAT number (optional) (The data group <TRADER Place of Delivery> does not exist) (1) The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (2) The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (3) The operator type of the consignee is either ‘Authorised warehouse keeper’ or ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (4) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>; (5) An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>; (*1) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable) an..16 b EORI Number C — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise Provide the EORI number of the person responsible for lodging the export declaration as set out in Article 21(5) of Directive 2008/118/EC. an..17 c Trader Name R an..182 d Street Name R an..65 e Street Number O an..11 f Postcode R an..10 g City R an..50 h NAD_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 8.4 OFFICE Place of Export O a Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 8.5 EXPORT ACCEPTANCE R a Sender Customs Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 b Sender Customs Officer Identification O an..35 c Date of Acceptance R date d MRN Export R A valid MRN or SAD Number confirmed against Customs data, according to the Customs case. MRN = Movement Reference Number SAD = Single Administrative Document an..21 9 All Notifications of refusal by Customs O The set of all Customs rejection of e-AD messages relating to the movement 99x 9.1 ATTRIBUTES R a Date and Time of Issuance R dateTime 9.2 The concerned draft e-AD C In the case of rejection at import one concerned draft e-AD must be given or in the case of rejection at export one or several concerned validated e-ADs must be given. (see All concerned validated e-ADs in box 9.3) a Local Reference Number R an..22 9.3 All concerned validated e-ADs C In the case of rejection at import one concerned draft e-AD must be given or in the case of rejection at export one or several concerned validated e-ADs must be given. (see The concerned draft e-AD in box 9.2) 99x a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R n..2 9.4 REJECTION R a Rejection Date and Time R dateTime b Rejection Reason Code R The possible values are: 1 = Import data not found 2 = The contents of the e-AD does not match with import data 3 = Export data not found 4 = The content of the e-AD does not match with export data 5 = Goods are rejected at export procedure n1 9.5 EXPORT CROSS CHECKING DIAGNOSES C ‘R’ if <Rejection Reason Code> is ‘The content of the e-AD does not match with export data’ — Does not apply otherwise (see Rejection Reason Code in box 9.4b) a LRN Export C At least one of the following attributes must be present: — <MRN Export> — <LRN Export> (see MRN Export in box 9.5b) an..22 b MRN Export C At least one of the following attributes must be present: — <MRN Export> — <LRN Export> (see LRN Export in box 9.5a) A valid MRN or SAD Number confirmed against Customs data, according to the Customs case. MRN = Movement Reference Number SAD = Single Administrative Document an..21 9.6 DIAGNOSIS R 999x a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Body Record Unique Reference R The value of the Data Item must be greater than zero. n..3 c Diagnosis Code R The possible values are: 1 = Unknown ARC 2 = Body Record Unique Reference does not exist in the e-AD 3 = No corresponding GOODS ITEM in the export declaration 4 = Weight/mass do not match 5 = The destination type code of the e-AD is not export 6 = CN codes do not match n1 9.7 TRADER Consignee C — ‘R’ if <Message Type> of all concerned e-ADs is not ‘Submission for export (local clearance)’ — Does not apply otherwise The possible Message Types are: 1 = Standard submission (to be used in all cases except where submission concerns export with local clearance) 2 = Submission for export with local clearance (Application of Article 283 of Commission Regulation (EEC) No 2454/93 (1)) The message type must not occur in the e-AD to which an ARC has been assigned, nor in the paper document referred to in Article 8(1) of Regulation (EC) No 684/2009 a Trader Identification C — ‘R’ if <Destination Type Code> is in: — — ‘Destination - Tax warehouse’ — ‘Destination - Registered consignee’ — ‘Destination - Temporary registered consignee’ — ‘Destination - Direct delivery’ — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise The possible values of <Trader Identification> are described in the following table:



Destination Type Code TRADER CONSIGNEE. Trader Identification TRADER Place of Delivery.Trader Identification 1 - Destination- Tax warehouse Excise number (1) Tax Warehouse Reference (Excise Number) (5) 2 - Destination- Registered consignee Excise number (2) Any identification (*1) 3 - Destination- Temporary registered consignee Temporary authorisation reference (4) Any identification (*1) 4 - Destination- Direct delivery Excise number (3) (Does not apply) 5 - Destination- Exempted consignee (Does not apply) Any identification (*1) 6 - Destination– Export VAT number (optional) (The data group <TRADER Place of Delivery> does not exist) (1) The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (2) The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (3) The operator type of the consignee is either ‘Authorised warehouse keeper’ or ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (4) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>; (5) An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>; (*1) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable) an..16 b EORI Number C — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise Provide the EORI number of the person responsible for lodging the export declaration as set out in Article 21(5) of Directive 2008/118/EC. an..17 c Trader Name R an..182 d Street Name R an..65 e Street Number O an..11 f Postcode R an..10 g City R an..50 h NAD_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 9.8 OFFICE Place of Export O a Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 10 The Possible Interruption of Movement O The content of a possible Interruption of movement message relating to the movement, the structure of which is set out in Table 13 1x 11 The Possible Cancellation of e-AD O The content of a possible Cancellation message relating to the movement, the structure of which is set out in Table 2 of Annex I to Regulation (EC) No 684/2009 1x 12 All Changes of Destination O The set of all Change of destination messages relating to the movement, the structure of which is set out in Table 3 of Annex I to Regulation (EC) No 684/2009 99x 13 All Alerts or Rejections of an e-AD O The set of all Alert or Rejection of an e-AD messages relating to the movement, the structure of which is set out in Table 14 99x 13.1 ATTRIBUTES R a Date and Time of Validation of Alert or Rejection C — ‘R’ after successful validation — Does not apply otherwise dateTime 13.2 EXCISE MOVEMENT e-AD R a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2 13.3 TRADER Consignee R a Trader Identification C — ‘R’ if <Destination Type Code> is in: — — ‘Destination - Tax warehouse’ — ‘Destination - Registered consignee’ — ‘Destination - Temporary registered consignee’ — ‘Destination - Direct delivery’ — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise The possible values of <Trader Identification> are described in the following table:



Destination Type Code TRADER CONSIGNEE. Trader Identification TRADER Place of Delivery.Trader Identification 1 - Destination- Tax warehouse Excise number (1) Tax Warehouse Reference (Excise Number) (5) 2 - Destination- Registered consignee Excise number (2) Any identification (*1) 3 - Destination- Temporary registered consignee Temporary authorisation reference (4) Any identification (*1) 4 - Destination- Direct delivery Excise number (3) (Does not apply) 5 - Destination- Exempted consignee (Does not apply) Any identification (*1) 6 - Destination– Export VAT number (optional) (The data group <TRADER Place of Delivery> does not exist) (1) The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (2) The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (3) The operator type of the consignee is either ‘Authorised warehouse keeper’ or ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (4) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>; (5) An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>; (*1) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable) an..16 b EORI Number C — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise Provide the EORI number of the person responsible for lodging the export declaration as set out in Article 21(5) of Directive 2008/118/EC. an..17 c Trader Name R an..182 d Street Name R an..65 e Street Number O an..11 f Postcode R an..10 g City R an..50 h NAD_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 13.4 OFFICE of Destination R a Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 13.5 ALERT R a Date of Alert R date b E-AD Rejected flag R The format of Boolean is digital: ‘0’ or ‘1’ (‘0’ = No or False; ‘1’ = Yes or True) n1 13.6 ALERT OR REJECTION OF E-AD REASON Code C — ‘R’ if <E-AD Rejected flag> is True — ‘O’ if <E-AD Rejected flag> is False (see E-AD Rejected Flag in box 13.5b) 9x a Alert or Rejection of E-AD Reason Code R (see Code list 5 in Annex II) n..2 b Complementary Information C — ‘R’ if <Alert or Rejection of E-AD Reason Code> is ‘Other’ — ‘O’ otherwise (see Alert or Rejection of E-AD Reason Code in box 13.6a) an..350 c Complementary Information_LNG C — ‘R’ if the corresponding text field is used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 14 All Explanations on reason for shortage O 99x 14.1 ATTRIBUTES R a Submitter Type R The possible values are: 1 = Consignor 2 = Consignee n1 b Date and Time of Validation of Explanation on Shortage C — ‘R’ after successful validation — Does not apply otherwise dateTime 14.2 EXCISE MOVEMENT e-AD R a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2 14.3 TRADER Consignor C — ‘R’ if <Submitter Type> is ‘Consignor’ — Does not apply otherwise (see Submitter Type in box 14.1a) a Trader Excise Number R For TRADER Consignor An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION> The <Operator Type Code> of the referred <TRADER> must be: — ‘Authorised warehouse keeper’; OR — ‘Registered consignor’ For TRADER Place of dispatch An existing identifier <Tax Warehouse Reference> (Excise Number in SEED). (see Code list 1 in Annex II to Regulation (EU) No 612/2013) an13 b Trader Name R an..182 c Street Name R an..65 d Street Number O an..11 e Postcode R an..10 f City R an..50 g NAD_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 14.4 TRADER Consignee C — ‘R’ if <Submitter Type> is not ‘Consignor’ — Does not apply otherwise (see Submitter Type in box 14.1a) a Trader Identification C — ‘R’ if <Destination Type Code> is in: — — ‘Destination - Tax warehouse’ — ‘Destination - Registered consignee’ — ‘Destination — Temporary registered consignee’ — ‘Destination — Direct delivery’ — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise The possible values of <Trader Identification> are described in the following table:



Destination Type Code TRADER CONSIGNEE. Trader Identification TRADER Place of Delivery.Trader Identification 1 - Destination- Tax warehouse Excise number (1) Tax Warehouse Reference (Excise Number) (5) 2 - Destination- Registered consignee Excise number (2) Any identification (*1) 3 - Destination- Temporary registered consignee Temporary authorisation reference (4) Any identification (*1) 4 - Destination- Direct delivery Excise number (3) (Does not apply) 5 - Destination- Exempted consignee (Does not apply) Any identification (*1) 6 - Destination– Export VAT number (optional) (The data group <TRADER Place of Delivery> does not exist) 8 - Unknown destination (Does not apply) (Does not apply) (1) The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (2) The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (3) The operator type of the consignee is either ‘Authorised warehouse keeper’ or ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>; (4) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>; (5) An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>; (*1) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable) an..16 b EORI Number — ‘O’ if <Destination Type Code> is ‘Destination – Export’ — Does not apply otherwise Provide the EORI number of the person responsible for lodging the export declaration as set out in Article 21(5) of Directive 2008/118/EC an..17 c Trader Name R an..182 d Street Name R an..65 e Street Number O an..11 f Postcode R an..10 g City R an..50 h NAD_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 14.5 ANALYSIS C At least one of the <ANALYSIS> or <ANALYSIS Body> data groups must be present a Date of Analysis R date b Global Explanation R an..350 c Global Explanation_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 14.6 ANALYSIS Body C At least one of the <ANALYSIS> or <ANALYSIS Body> data groups must be present 999x a Body Record Unique Reference R The value of the Data Item must be greater than zero. The <Body Record Unique Reference> must be unique within the message and must refer to a <Body Record Unique Reference> of the e-AD Body of the associated e-AD for which shortages or excesses have been declared. n..3 b Excise Product Code R (see Code list 11 in Annex II to Regulation (EC) No 684/2009) an4 c Explanation O an..350 d Explanation_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 e Actual Quantity O The value of the Data Item must be greater than zero. n..15,3 15 All reminder messages for Excise movement O 99x 15.1 ATTRIBUTES R a Message Type R The possible values are: 1 = Reminder message at expiry of time to change destination (or split) 2 = Reminder message at expiry of time to send the report of receipt/export 3 = Reminder message at expiry of time to give destination information (Article 22 of Directive 2008/118/EC) n1 b Date and Time of Issuance of Reminder R dateTime c Limit date and Time R dateTime d Reminder Information O an..350 e Reminder Information_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2 15.2 EXCISE MOVEMENT e-AD R a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2

▼M2







Table 4 (as referred to in Article 5(1)) Common Request A B C D E F G 1 ATTRIBUTES R a Request Type R The possible values are: 1 = (reserved) 2 = Request for reference data 3 = (reserved) 4 = (reserved) 5 = Request for re-synchronisation of the register of economic operators 6 = Request for retrieval of a list of e-ADs 7 = Request for SEED statistics n1 b Request Message Name C — ‘R’ if <Request Type> is ‘2’ — Does not apply otherwise (see Request Type in box 1a) The possible values are: ‘C_COD_DAT’ = Common list of codes ‘C_PAR_DAT’ = Common system parameters ‘ALL’ = For complete structure a..9 c Requesting Office R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 d Request Correlation Identifier C — ‘R’ if <Request Type> is ‘2’, ‘5’, ‘6’, or ‘7’ — Does not apply otherwise (see Request Type in box 1a) The value of <Request Correlation Identifier> is unique per Member State. an..44 e Start Date C For 1 e and f: — ‘R’ if <Request Type> is ‘2’ or ‘5’ — Does not apply otherwise (see Request Type in box 1a) date f End Date C date g Single Date C — ‘R’ if <Request Type> is ‘2’ or ‘5’ — Does not apply otherwise (see Request Type in box 1a) date 2 E-AD LIST REQUEST C — ‘R’ if <Request Type> is ‘6’ — Does not apply otherwise (see Request Type in box 1a) a Member State Code R (see Code list 3 in Annex II to Regulation (EC) No 684/2009) a2 2.1 RA_PRIMARY CRITERION R 99x a Primary Criterion Type Code R The possible values are: 1 = ARC 2 = Brand name of product 3 = Categories of excise products of the movement 4 = (reserved) 5 = (reserved) 6 = (reserved) 7 = (reserved) 8 = City of consignee 9 = City of consignor 10 = City of guarantor 11 = (reserved) 12 = City of place of delivery 13 = City of tax warehouse of dispatch 14 = City of transporter 15 = CN code of product 16 = Date of invoice 17 = Excise number of consignee 18 = Excise number of consignor 19 = Excise number of guarantor 20 = (reserved) 21 = (reserved) 22 = Excise number of the tax warehouse of destination 23 = Excise number of the tax warehouse of dispatch 24 = (reserved) 25 = Excise product code 26 = Journey time 27 = Member State of destination 28 = Member State of dispatch 29 = Name of consignee 30 = Name of consignor 31 = Name of guarantor 32 = (reserved) 33 = Name of place of delivery 34 = Name of tax warehouse of dispatch 35 = Name of transporter 36 = Number of invoice 37 = Postal code of consignee 38 = Postal code of consignor 39 = Postal code of guarantor 40 = (reserved) 41 = Postal code of place of delivery 42 = Postal code of tax warehouse of dispatch 43 = Postal code of transporter 44 = Quantity of goods (in an e-AD body) 45 = Local Reference Number, being a serial number, assigned by the consignor 46 = Type of transport 47 = (reserved) 48 = (reserved) 49 = VAT number of the consignee 50 = (reserved) 51 = VAT number of the transporter 52 = Change of destination (sequence number ≥ 2) n..2 2.1.1 RA_PRIMARY VALUE O 99x a Value R If <Primary Criterion Type Code> is ‘46’ (Type of transport), then an existing <Transport Mode Code> in the list of <TRANSPORT MODES> shall be used. an..255 3 STA_REQUEST C — ‘R’ if <Request Type> is ‘7’ — Does not apply otherwise (see Request Type in box 1a) a Statistic Type R The possible values are: 1 = Active and inactive economic operators 2 = Pending expirations 3 = Economic operators by type and tax warehouses 4 = Excise activity 5 = Changes to excise authorisations n1 3.1 LIST OF MEMBER STATES Code R 99x a Member State Code R (see Code list 3 in Annex II to Regulation (EC) No 684/2009) a2 4 STA_PERIOD C — ‘R’ if <Request Type> is ‘7’ — Does not apply otherwise (see Request Type in box 1a) a Year R The value of the data element must be greater than zero. n4 b Semester C For 4 b, c, and d: The three following data fields are optional and exclusive: — <Semester> — <Quarter> — <Month> i.e. If one of these data fields is given then the two other data fields do not apply The possible values are: 1 = First semester 2 = Second semester n1 c Quarter C The possible values are: 1 = First quarter 2 = Second quarter 3 = Third quarter 4 = Fourth quarter n1 d Month C The possible values are: 1 = January 2 = February 3 = March 4 = April 5 = May 6 = June 7 = July 8 = August 9 = September 10 = October 11 = November 12 = December n..2 5 REF_REQUEST C — ‘R’ if <Request Type> is ‘2’ — Does not apply otherwise (see Request Type in box 1a) a Common Risk Assessment Criteria flag O The possible values are: 0 = No or False 1 = Yes or True n1 5.1 LIST OF CODES Code O 99x a Requested List of Code O The possible values are: 1 = Units of measure 2 = Events types 3 = Evidence types 4 = (reserved) 5 = (reserved) 6 = Language codes 7 = Member States 8 = Country codes 9 = Packaging codes 10 = Reasons for unsatisfactory receipt or control report 11 = Reasons for interruption 12 = (reserved) 13 = Transport modes 14 = Transport units 15 = Wine-growing zones 16 = Wine operation codes 17 = Excise product categories 18 = Excise products 19 = CN codes 20 = Correspondences CN code — Excise product 21 = Cancellation reasons 22 = Alert or rejection of e-AD reasons 23 = Delay explanations 24 = (reserved) 25 = Event submitting persons 26 = Refusal reasons 27 = Reasons for delayed result 28 = Request actions 29 = Request reasons 30 = (reserved) 31 = (reserved) 32 = (reserved) 33 = (reserved) 34 = Administrative cooperation action not possible reasons 35 = (reserved) 36 = Type of document 37 = (reserved) 38 = (reserved) 39 = Manual Closure Request Reasons 40 = Manual Closure Rejection Reasons n..2







Table 5 (as referred to in Article 5(2)) List of e-AD as result of a general query A B C D E F G 1 ATTRIBUTES R a Requesting Office R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 b Request Correlation Identifier R The value of <Request Correlation Identifier> is unique per Member State. an..44 2 E-AD LIST ITEM O 99x a Dispatch Date R date 2.1 EXCISE MOVEMENT R a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Date and Time of Validation of e-AD R dateTime c Sequence Number R The value of the data element must be greater than zero. n..2 2.2 TRADER Consignor R a Trader Excise Number R For TRADER Consignor An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION> The <Operator Type Code> of the referred <TRADER> must be: — ‘Authorised warehouse keeper’; OR — ‘Registered consignor’ (see Code list 1 in Annex II to Regulation (EU) No 612/2013) an13 b Trader Name R an..182 2.3 TRADER Place of Dispatch C IF <E-AD.Origin Type Code> is ‘Origin — Tax warehouse’ THEN <TRADER Place of Dispatch> is ‘R’ <OFFICE of Dispatch — Import> does not apply ELSE <TRADER Place of Dispatch> does not apply <OFFICE of Dispatch — Import> is ‘R’ a Tax Warehouse Reference R For TRADER Place of dispatch An existing identifier <Tax Warehouse Reference> (Excise Number in SEED). (see Code list 1 in Annex II to Regulation (EU) No 612/2013) an13 b Trader Name O an..182 2.4 OFFICE of Dispatch — Import C IF <E-AD.Origin Type Code> is ‘Origin — Tax warehouse’ THEN <TRADER Place of Dispatch> is ‘R’ <OFFICE of Dispatch — Import> does not apply ELSE <TRADER Place of Dispatch> does not apply <OFFICE of Dispatch — Import> is ‘R’ a Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 2.5 TRADER Consignee C ‘R’, except for message type ‘2 — Submission for export with local clearance’ or for Destination Type Code 8 a Trader Identification C IF <Destination Type Code> is in: — ‘Destination — Tax warehouse’ — ‘Destination — Registered consignee’ — ‘Destination — Temporary registered consignee’ — ‘Destination — Direct delivery’ — THEN <TRADER Consignee.Trader Identification> is ‘R’ — ELSE — IF <Destination Type Code> is: — ‘Destination — Export’ — THEN <TRADER Consignee.Trader Identification> is ‘O’ — ELSE <TRADER Consignee.Trader Identification> does not apply The possible values of <Trader Identification> are described in the following table: an..16 Destination Type Code TRADER CONSIGNEE. Trader Identification TRADER Place of Delivery. Trader Identification 1 - Destination — Tax warehouse Excise number (1) Tax Warehouse Reference (Excise Number) (2) 2 - Destination — Registered consignee Excise number (3) Any identification (4) 3 - Destination — Temporary registered consignee Temporary authorisation reference (5) Any identification (6) 4 - Destination — Direct delivery Excise number (7) (Does not apply) 5 - Destination — Exempted consignee (Does not apply) Any identification (8) 6 - Destination — Export VAT number (optional) (The data group <TRADER Place of Delivery> does not exist) 8 - Unknown destination (Does not apply) (Does not apply) (1) The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>. (2) An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>. (3) The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>. (4) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (5) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>. (6) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (7) The operator type of the consignee is either ‘Authorised warehouse keeper’ or ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>. (8) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable) b EORI Number C — ‘O’ if <Destination Type Code> is ‘Destination — Export’ — Does not apply otherwise Provide the EORI number of the person responsible for lodging the export declaration as set out in Article 21(5) of Directive 2008/118/EC. an..17 c Trader Name R an..182 2.6 TRADER Place of Delivery C The optionality of data groups <TRADER Place of Delivery> and <OFFICE Place of Delivery — Customs> are described below, according to the <Destination Type Code>: — ‘R’ for Destination Type Code 1 and 4 — ‘O’ for Destination Type Code 2, 3 and 5 — does not apply otherwise. — — a Trader Identification C IF <Destination Type Code> is ‘Destination — Tax warehouse’ THEN <TRADER Place of Delivery. Trader Identification> is ‘R’ ELSE IF <Destination Type Code> is ‘Destination — Direct delivery’ THEN <TRADER Place of Delivery. Trader Identification> does not apply ELSE <TRADER Place of Delivery. Trader Identification> is ‘O’ The possible values of <Trader Identification> are described in the following table: an..16 Destination Type Code TRADER CONSIGNEE. Trader Identification TRADER Place of Delivery. Trader Identification 1 - Destination — Tax warehouse Excise number (1) Tax Warehouse Reference (Excise Number) (2) 2 - Destination — Registered consignee Excise number (3) Any identification (4) 3 - Destination — Temporary registered consignee Temporary authorisation reference (5) Any identification (6) 4 - Destination — Direct delivery Excise number (7) (Does not apply) 5 - Destination — Exempted consignee (Does not apply) Any identification (8) 6 - Destination — Export VAT number (optional) (The data group <TRADER Place of Delivery> does not exist) 8 - Unknown destination (Does not apply) (Does not apply) (1) The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>. (2) An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>. (3) The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>. (4) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (5) An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>. (6) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (7) The operator type of the consignee is either ‘Authorised warehouse keeper’ or ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>. (8) For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional. (see Code list 1 in Annex II to Regulation (EU) No 612/2013, if applicable) b Trader Name C IF <Destination Type Code> is ‘Destination — Direct delivery’ THEN <Trader Name> is ‘O’ ELSE <Trader Name> is ‘R’ an..182 2.7 OFFICE Place of Delivery — Customs C The optionality of the data groups <TRADER Place of Delivery> and <OFFICE Place of Delivery — Customs> are described in the table below, according to the <Destination Type Code>: Destination Type Code <TRADER Place of Delivery> <OFFICE Place of Delivery — Customs> 1 - Destination — Tax warehouse ‘R’ Does not apply 2 - Destination — Registered consignee ‘O’ Does not apply 3 - Destination — Temporary registered consignee ‘O’ Does not apply 4 - Destination — Direct delivery ‘R’ Does not apply 5 - Destination — Exempted consignee ‘O’ Does not apply 6 - Destination — Export Does not apply ‘R’ 8 - Unknown destination (consignee unknown) Does not apply Does not apply a Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 2.8 EXCISE PRODUCTS CATEGORY Code R 9x a Excise Product Category Code R (see Code list 3 in Annex II to Regulation (EU) No 612/2013) a1 2.9 TRADER Transport Arranger C IF <E-AD Header.Transport Arrangement>(IE801) (or <E-AD Header.Transport Arrangement>(IE815)) is ‘Consignor’ or ‘consignee’ THEN <TRADER Transport Arranger> does not apply ELSE <TRADER Transport Arranger> is ‘R’ a VAT Number O an..14 b Trader Name R an..182 2.10 TRADER First Transporter O a VAT Number O an..14 b Trader Name R an..182

▼M1







Table 6 (as referred to in Article 5(3)) Refusal of Common Request A B C D E F G 1 Common Request Message R The context of the Common Request message relating to the movement, the structure of which is set out in Table 4 2 Rejection R 99x a Rejection Date and Time R dateTime b Rejection Reason Code R The possible values are: 0 = Other 2 = No e-AD(s) retrieved matching selection criteria 3 = Reference data not available 4 = Excise Office List not available 5 = SEED data not available 7 = Unknown requested data 8 = Increment number out of range 26 = Duplicate detected 112 = Incorrect (code) value 115 = Not supported in this position n..3

▼M2







Table 7 (as referred to in Article 6(1)) Administrative Cooperation Common Request A B C D E F G 1 ATTRIBUTES R a Request Type R The possible values are: 1 = Administrative cooperation 2 = Request for history n1 b Deadline for Results R date 2 FOLLOW UP R a Follow-Up Correlation ID R (see Code list 1 in Annex II) an28 b Date of Issuance R date c Sender Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 d Sender Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 e Sender Officer O an..35 f Addressee Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 g Addressee Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 h Addressee Officer O an..35 i National Case Reference Identifier O an..99 3 ACO_REQUEST C — ‘R’ if <Request Type> is ‘1’ — Does not apply otherwise (see Request Type in box 1a) a Administrative Cooperation Request Information R an..999 b Administrative Cooperation Request Information_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 c Flag O The possible values are: 0 = No or False 1 = Yes or True n1 3.1 REQUEST REASON Code R 99x a Administrative Cooperation Request Reason Code R (see Code list 8 in Annex II) n..2 b ACO_Complementary Information C — ‘R’ if <Administrative Cooperation Request Reason Code> is ‘Other’ — ‘O’ otherwise — an..999 c ACO_Complementary Information_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 3.1.1 RISK ASSESSMENT REFERENCE O 99x a Other Risk Profile O an..999 b Other Risk Profile_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 3.2 ARC List O 99x a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number O The value of the Data Item must be greater than zero. n..2 3.3 TRADER Person O 99x a Trader Excise Number C For 3.3 a, b, and c: at least one of the following attributes must be present: — <Trader Excise Number> — <VAT Number> — <Trader Name> An existing identifier (Excise Number) <Trader Excise Number> in the set of <TRADER AUTHORISATION> or <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>. (see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013) an13 b VAT Number C an..14 c Trader Name C an..182 d Member State Code C — ‘R’ if <Trader Name> is given and <Trader Excise Number> is not given and <VAT Number> is not given — Does not apply otherwise (see Trader Excise Number in box 3.3a, VAT Number in box 3.3b, Trader Name in box 3.3c) A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 e Street Name O an..65 f Street Number O an..11 g Postcode O an..10 h City O an..50 i NAD_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 j Phone Number O an..35 k Fax Number O an..35 l Email Address O an..70 3.4 SUPPORTING DOCUMENTS O 9x a Short Description of Supporting Document C — ‘R’ if <Supporting Document Type> is ‘Other’ — Doesn’t apply otherwise (see Reference of Supporting Document in box 3.4c and Image of Document in box 3.4e) an..999 b Short Description of Supporting Document_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 c Reference of Supporting Document C At least one, among these three fields, must be present: — <Supporting Document Type> — <Reference of Supporting Document> — <Image of Document> (see Short Description of Supporting Document in box 3.4a and Image of Document in box 3.4e) an..999 d Reference of Supporting Document_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 e Image of Document C At least one, among these three fields, must be present: — <Supporting Document Type> — <Reference of Supporting Document> — <Image of Document> (see Short Description of Supporting Document in box 3.4a and Reference of Supporting Document in box 3.4c) f Supporting Document Type C At least one, among these three fields, must be present: — <Supporting Document Type> — <Reference of Supporting Document> — <Image of Document> See Reference of Supporting Document in box 3.4c and Image of Document in box 3.4e (see code list 15 in Annex II) n..4 3.5 ACTIONS Requested O 99x a Administrative Cooperation Action Code R (see Code list 9 in Annex II) n..2 b ACO Action Complement C — ‘R’ if <Administrative Cooperation Action Code> is ‘Other’ — ‘O’ otherwise (see Administrative Cooperation Action Code in box 3.5a) an..999 c ACO Action Complement_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 4 HISTORY REQUEST C — ‘R’ if <Request Type> is ‘2’ — Does not apply otherwise (see Request Type in box 1a) a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b History Request Scope Type R The possible values are: 1 = Applicable data at a given date set by the <Scope Date> 2 = History of data since a given date set by the <Scope Date> 3 = Complete history of data (see Scope Date in box 4c) n1 c Scope Date C — Does not apply if <History Request Scope Type> is ‘3’ — ‘R’ otherwise (see History Request Scope Type in box 4b) date d History Request Reason R an..999 e History Request Reason_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5 CONTACT O a Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 b Submitting Excise Officer O an..35 c Tel. Number O an..35 d Fax Number O an..35 e Email Address O an..70

▼M1







Table 8 (as referred to in Article 7(2) and Article 8) Answer message A B C D E F G 1 ATTRIBUTES R a Message Type R The possible values are: 1 = Administrative Cooperation answer message 2 = History answer message n1 2 FOLLOW UP R a Follow Up Correlation ID R (see Code list 1 in Annex II) an28 b Date of Issuance R date c Sender Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009 a2 d Sender Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 e Sender Officer O an..35 f Addressee Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009 a2 g Addressee Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 h Addressee Officer O an..35 i National Case Reference Identifier C — ‘O’ If <Follow Up Correlation ID> does not match with <Follow Up Correlation ID> in a request message — ‘R’ If <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message IF <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message THEN <National Case Reference Identifier> must be equal to the value of <National Case Reference Identifier> in the request message. an..99 3 ANSWER R a Deadline for Results C For 3 a and b: — ‘R’ if < Refusal Reason Code> is provided — Does not apply otherwise (see Refusal Reason Code in box 3c) dateTime b Delayed Result Reason Code C (see Code list 3 in Annex II) n..2 c Refusal Reason Code O (see Code list 4 in Annex II) n..2 d Refusal Reason Complement C — ‘R’ if < Refusal Reason Code> is ‘Other’ — Does not apply otherwise (see Refusal Reason Code in box 3c) an..999 e Refusal Reason Complement_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group a2







Table 9 (as referred to in Article 7(1)) Reminder Message for Administrative Cooperation A B C D E F G 1 ATTRIBUTES R a Message Type R The possible values are: 1 = Administrative cooperation results reminder message 2 = History results reminder message n1 2 FOLLOW UP R a Follow Up Correlation ID R (see Code list 1 in Annex II) an28 b Date of Issuance R date c Sender Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009 a2 d Sender Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 e Sender Officer O an..35 f Addressee Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009 a2 g Addressee Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 h Addressee Officer O an..35 i National Case Reference Identifier C — ‘O’ If <Follow Up Correlation ID> does not match with <Follow Up Correlation ID> in a request message — ‘R’ If <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message — Otherwise it does not apply. IF <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message THEN <National Case Reference Identifier> must be equal to the value of <National Case Reference Identifier> in the request message. an..99

▼M2







Table 10 (as referred to in Article 6(3), Article 9(1) and Articles 10 and 16) Administrative Cooperation Results A B C D E F G 1 FOLLOW UP R a Follow Up Correlation ID R (see Code list 1 in Annex II) an28 b Date of Issuance R date c Sender Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 d Sender Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 e Sender Officer O an..35 f Addressee Member State Code R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 g Addressee Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 h Addressee Officer O an..35 i National Case Reference Identifier C — ‘O’ If <Follow Up Correlation ID> does not match with <Follow Up Correlation ID> in a request message — ‘R’ If <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message — Otherwise it does not apply. IF <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message THEN <National Case Reference Identifier> must be equal to the value of <National Case Reference Identifier> in the request message. an..99 2 CONTACT O a Office Reference Number R (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 b Submitting Excise Officer O an..35 c Tel. Number O an..35 d Fax Number O an..35 e Email Address O an..70 3 ACO_ACTION RESULT O 99x a ARC O (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number C — ‘O’ if <ARC> is present — Does not apply otherwise (see ARC in box 3a) The value of the Data Item must be greater than zero. n..2 c Administrative Cooperation Action Code R (see Code list 9 in Annex II) n..2 d ACO Action Complement C — ‘R’ if <Administrative Cooperation Action Code> is ‘Other’ — ‘O’ otherwise (see Administrative Cooperation Action Code in box 3c) an..999 e ACO Action Complement_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 f ACO Action Not Possible Reason Code O (see Code list 11 in Annex II) n..2 g ACO Action Not Possible Reason Complement C — ‘R’ if <ACO Action Not Possible Reason Code> is ‘Other’ — ‘O’ otherwise (see ACO Action Not Possible Reason Code in box 3f) an..999 h ACO Action Not Possible Reason Complement_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 i Finding at Destination O The possible values are: 0 = Other finding 1 = (reserved) 2 = Consignment in order 3 = Consignment has not reached destination 4 = Consignment arrived late 5 = Shortage detected 6 = Excise products not in order 7 = Consignment not entered in stock records 8 = Trader could not be contacted 9 = Missing trader 10 = Excess detected 11 = Wrong EPC 12 = Wrong destination type code 13 = Differences confirmed 14 = Manual closing recommended 15 = Interruption recommended 16 = Irregularities Found n..2 j Other Finding Type C — ‘R’ if <Finding at Destination> is ‘Other finding’ — Does not apply otherwise (see Finding at Destination in box 3i) an..999 k Other Finding Type_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 l Complementary Explanations O an..999 m Complementary Explanations_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 n Control Report Reference O (see Code list 2 in Annex II) A ‘Control Report’ message exists in the system (including the case that it is encapsulated in a received ‘Movement History’/‘History results’ message) having the same <Control Report Reference> with that of the submitted message. In addition if the <ARC> is provided in the submitted message then it coincides with the <ARC> of the referenced ‘Control Report’ message. (see ARC in box 3a) an16 4 FEEDBACK REQUEST O a Feedback Requested or Provided R The possible values are: 0 = No feedback requested 1 = Feedback requested 2 = Feedback provided n1 b Follow Up Actions C At least one among these two fields if box 4a is given: — <Follow Up Actions> — <Relevance of Information> — an..999 c Follow Up Actions_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 d Relevance of Information Provided C At least one among these two fields if box 4a is given: — < Follow Up Actions> — <Relevance of Information> — an..999 e Relevance of Information_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5 SUPPORTING DOCUMENTS O 9x a Short Description of Supporting Document C — ‘R’ if <Supporting Document Type> is ‘Other’ — Doesn’t apply otherwise (See Supporting Document Type in box 5f) an..999 b Short Description of Supporting Document_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 c Reference of Supporting Document C At least one, among these three fields, must be present: — <Short Description of Supporting Document> — <Reference of Supporting Document> — <Image of Document> (see Short Description of Supporting Document in box.5a and Image of Document in box 5e) an..999 d Reference of Supporting Document_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 e Image of Document C At least one, among these three fields, must be present: — <Short Description of Supporting Document> — <Reference of Supporting Document> — <Image of Document> (see Short Description of Supporting Document in box 5a and Reference of Supporting Document in box 5c) f Supporting Document Type C At least one, among these three fields, must be present: — <Short Description of Supporting Document> — <Reference of Supporting Document> — <Image of Document> (see Short Description of Supporting Document in box 5a, Reference of Supporting Document in box 5c and Image of Document in box5e) (see code list 15 in Annex II) n..4







Table 11 (as referred to in Article 9(2) and Article 11) Control Report A B C D E F G 1 ATTRIBUTES R a Message Type R The possible values are: 1 = Validated document n1 b Date and Time of Validation of Control Report C — ‘R’ after successful validation — Does not apply otherwise dateTime 2 CONTROL REPORT HEADER R a Control Report Reference R (see Code list 2 in Annex II) an16 2.1 CONTROL OFFICE R a Control Office Reference Number O (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8 b Member State Code C For 2.1 b, c, d, e, f, and g: — ‘R’ except for <Street Number>, which is ‘O’, if <Control Office Reference Number> is not given — Does not apply otherwise (see Control Office Reference Number in box 2.1a) A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 c Control Office Name C an..35 d Street Name C an..65 e Street Number C an..11 f Postcode C an..10 g City C an..50 h Phone Number C For 2.1 h, i and j: If <Control Office Reference Number> is not given, at least one of the following three attributes must be present: — <Phone Number> — <Fax Number> — <Email Address> — otherwise, none of the three attributes are applicable (see Control Office Reference Number in box 2.1a) an..35 i Fax Number C an..35 j Email Address C an..70 k NAD_LNG C ‘R’ if the corresponding free text field(s) is (are) used Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 3 EXCISE MOVEMENT e-AD C One of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present a ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 b Sequence Number R The value of the Data Item must be greater than zero. n..2 4 OTHER ACCOMPANYING DOCUMENT C One of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present a Other Accompanying Document Type R The possible values are: 0 = Other 2 = SAAD n1 b Short Description of Other Accompanying Document C ‘R’ if <Other Accompanying Document Type> is ‘Other’ It doesn’t apply otherwise an…350 c Short Description of Other Accompanying Document_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. n2 d Other Accompanying Document Number R an…350 e Other Accompanying Document Date R date f Image of Other Accompanying Document O g Member State of Dispatch R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 h Member State of Destination R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 4.1 TRADER Person Involved in Movement O 9x a Trader Excise Number C At least one of the following attributes must be present: — <Trader Excise Number> — <Trader Identification> — <Trader Name> An existing identifier (Excise Number) <Trader Excise Number> in the set of <TRADER AUTHORISATION> or <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>. (see Code list 1 in Annex II to Regulation (EU) No 612/2013) an13 b Trader Identification C At least one of the following attributes must be present: — <Trader Excise Number> — <Trader Identification> — <Trader Name> A VAT number or any other National number. an16 c Trader Name C At least one of the following attributes must be present: — <Trader Excise Number> — <Trader Identification> — <Trader Name> — an..182 d Trader Person Type O The possible values are the following: 1 = Consignor 2 = Consignee 3 = Tax representative 4 = Vendor 5 = Liable person 6 = Customer private individual n..2 e Member State Code C ‘R’ if <Trader Name> is given AND <Trader Excise Number> and <Trader Identification> is not given. It doesn’t apply otherwise (see Code list 3 in Annex II to Regulation (EC) No 684/2009) a2 f Street Name O an..65 g Street Number O an..11 h Postcode O an..10 i City O an..50 j NAD_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 k Phone Number O an..35 m Email Address O an..70 4.2 GOODS ITEM O 999x a Description of the Goods O an..55 b CN Code C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box4 and 4f) The value of the Data Item must be greater than zero. n8 c Commercial Description of the Goods O an..999 d Additional code O an..35 e Quantity C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box4 and 4f) The value of the Data Item must be greater than zero. n..15,3 f Unit of Measure Code C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box4 and 4f) (See Annex II to Regulation (EC) No 684/2009, Code list 12) n..2 g Gross Weight O The Gross Weight must be equal to or higher than Net Weight. The value of the Data Item must be greater than zero. n..15,2 h Net Weight O The Gross Weight must be equal to or higher than Net Weight. The value of the Data Item must be greater than zero. n..15,2 4.3 MEANS OF TRANSPORT C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box4 and 4f) a Trader Name R an..182 b Street Name R an..65 c Street Number O an..11 d Transporter Country R Provide a ‘Country Code’ listed in Code list 4 of Annex II to Regulation (EC) No 684/2009, but not listed in Code list 3 of Annex II to Regulation (EC) No 684/2009 and except ‘Country Cod e ’‘GR’. a2 e Postcode R an..10 f City R an..50 g Transport Mode Code R Provide the mode of transport using the codes in Code list 7 of Annex II to Regulation (EC) No 684/2009. n..2 h ACO_Complementary Information C — ‘R’ if <MEANS OF TRANSPORT. Transport Mode Code> is ‘Other’ — Does not apply otherwise (see box 4.3 g) an..999 i ACO_Complementary Information_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 j Registration R an..35 k Country of Registration R Provide a ‘Country Code’ listed in Code list 4 of Annex II to Regulation (EC) No 684/2009, but not listed in Code list 3 of Annex II to Regulation (EC) No 684/2009 and except ‘Country Cod e’‘ GR’. a2 5 CONTROL REPORT R a Date of Control R date b Place of Control R an..350 c Place of Control_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 d Control Type R The possible values are: 1 = Physical control 2 = Documentary control n1 e Reason for Control R The possible values are: 0 = Other reason 1 = Control started at random 2 = Event signalled 3 = Request for assistance received 4 = Request from another office 5 = Alert received n1 f Complementary Origin Reference O an..350 g Complementary Origin Reference_LNG C — ‘R’ if the corresponding text field is used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 h Control Officer Identity R an..350 i Control Officer Identity_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 j Global Control Conclusion R The possible values are: 1 = Satisfactory 2 = Minor discrepancies found 3 = Interruption recommended 4 = Intention to make claim under Article 10 of Council Directive 2008/118/EC 5 = Allowable loss detected, in relation to Article 7(4) of Council Directive 2008/118/EC n1 k Control at Arrival Required R The possible values are: 0 = No or False 1 = Yes or True n1 l Flag R The possible values are: 0 = No or False 1 = Yes or True n1 m Comments O an..350 n Comments_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5.1 PERFORMED CONTROL ACTION R 99x a Performed Control Action R The possible values are: 0 = Other control action 1 = Verified counted packs 2 = Unloaded 3 = Opened packs 4 = Annotated paper copy of documents (e.g. SAAD) 5 = Counting 6 = Sampling 7 = Administrative control 8 = Goods weighted/measured 9 = Random check 10 = Control of records 11 = Compare documents presented with e-AD n..2 b Other Control Action C — ‘R’ if <Performed Control Action> is ‘0’ — Does not apply otherwise (see Performed Control Action in box 5.1a) an..350 c Other Control Action_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5.2 SUPPORTING EVIDENCE C — ‘R’ if <Reason for Control> is ‘2’ — ‘O’ otherwise (see Reason for Control in box 5e) 9x a Issuing Authority O an..35 b Issuing Authority_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 c Evidence Type Code R (see Code list 6 in Annex II) n..2 d Evidence Type Complement C — ‘R’ if <Evidence Type Code> is ‘Other’ — Does not apply otherwise (see Evidence Type Code in box 5.2c) an..350 e Evidence Type Complement_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 f Reference of Evidence O an..350 g Reference of Evidence_LNG C — ‘R’ if the corresponding text(s) field is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 h Image of Evidence O 5.3 UNSATISFACTORY REASON O 9x a Unsatisfactory Reason Code R (see Code list 12 in Annex II) n..2 b Complementary Information C — ‘R’ if <Unsatisfactory Reason Code> is ‘Other’ — Does not apply otherwise (see Unsatisfactory Reason Code in box 5.3a) an..350 c Complementary Information_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5.4 TRANSPORT DETAILS O 99x a Transport Unit Code R (see Code list 7 in Annex II to Regulation (EC) No 684/2009) n..2 b Identity of Transport Units C — ‘R’ if <Transport Unit Code> is not ‘Fixed transport installations’ — Does not apply otherwise (see Transport Unit Code in box 5.4a) an..35 c Identity of Commercial Seal O an..35 d Seal Information O an..350 e Seal Information_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 f Complementary Information O an..350 g Complementary Information_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5.5 CONTROL REPORT Body O 99x a Body Record Unique Reference C — ‘R’ if <EXCISE MOVEMENT e-AD> data group is present — Does not apply otherwise This value refers to the <Body Record Unique Reference> of the e-AD Body of the associated e-AD and must be unique within the message. The value of the Data Item must be greater than zero. n..3 b Description of the Goods C — ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present — Does not apply otherwise — an..55 c CN Code C — ‘R’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present — Does not apply otherwise The value of the Data Item must be greater than zero. n8 d Additional code C — ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present — Does not apply otherwise — an..35 e Indicator of Shortage or Excess O The possible values are: S = Shortage E = Excess a1 f Observed Shortage or Excess C — ‘R’ if <Indicator of Shortage or Excess> is given — Does not apply otherwise (see Indicator of Shortage or Excess in box 5.5e) The value of the Data Item must be greater than zero. n..15,3 g Comments O an..350 h Comments_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5.5.1 UNSATISFACTORY REASON O 9x a Unsatisfactory Reason Code R (see Code list 12 in Annex II) n..2 b Complementary Information C — ‘R’ if <Unsatisfactory Reason Code> is ‘Other’ — ‘O’ otherwise (see Indicator of Unsatisfactory Reason Code in box 5.5.1a) an..350 c Complementary Information_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2







Table 12 (as referred to in Article 14) Event Report A B C D E F G 1 ATTRIBUTES R a Message Type R The possible values are: 1 = Initial submission 3 = Validated document n1 b Date and Time of Validation of Event Report C — ‘R’ after successful validation, — Does not apply otherwise — dateTime 2 EVENT REPORT HEADER R a Event Report Number C — ‘R’ if <Message Type> is ‘3’ — Does not apply otherwise (see Message Type in box 1a) (see Code list 2 in Annex II) an16 b MS of Submission Event Report Reference C — ‘R’ if <Message Type> is ‘1’ or ‘3’ and the MS of submission is different from the MS of event — ‘O’ if <Message Type> is ‘1’ or ‘3’ and the MS of submission is the MS of event — Does not apply otherwise (see Message Type in box 1a) The format of <MS of Submission Event Report Reference> is: — 2 alphabetic characters: Identifier of the Member State of Submission of the event report — followed by a nationally assigned, unique code an..35 c ARC R (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21 d Sequence Number R The value of the data element must be greater than zero. n..2 3 OTHER ACCOMPANYING DOCUMENT C One of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present a Other Accompanying Document Type R The possible values are: 0 = Other 2 = SAAD n1 b Short Description of Other Accompanying Document C — ‘R’ if <Other Accompanying Document Type> is ‘Other’ — It doesn’t apply otherwise an..350 c Short Description of Other Accompanying Document_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise a2 d Other Accompanying Document Number R an..350 e Other Accompanying Document Date R date f Image of Other Accompanying Document O g Member State of Dispatch R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 h Member State of Destination R A Member State identified by a Member State Code in Code list 3 of Annex II to Regulation (EC) No 684/2009. a2 3.1 TRADER Person Involved in Movement O 9x a Trader Excise Number C — At least one of the following attributes must be present: — <Trader Excise Number> — <Trader Identification> — <Trader Name> An existing identifier (Excise Number) <Trader Excise Number> in the set of <TRADER AUTHORISATION> or <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>. (see Code list 1 in Annex II to Regulation (EU) No 612/2013) an13 b Trader Identification C — At least one of the following attributes must be present: — <Trader Excise Number> — <Trader Identification> — <Trader Name> A VAT number or any other National number. an16 c Trader Name C — At least one of the following attributes must be present: — <Trader Excise Number> — <Trader Identification> — <Trader Name> — an..182 d Trader Person Type O The possible values are the following: 1 = Consignor 2 = Consignee 3 = Tax representative 4 = Vendor 5 = Liable person 6 = Customer private individual n..2 e Member State Code C — ‘R’ if <Trader Name> is given AND <Trader Excise Number> and <Trader Identification> is not given. — It doesn’t apply otherwise (see Code list 3 in Annex II to Regulation (EC) No 684/2009) a2 f Street Name O an..65 g Street Number O an..11 h Postcode O an..10 j NAD_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 k Phone Number O an..35 l Fax Number O an..35 m Email Address O an..70 3.2 GOODS ITEM O 999x a Description of the Goods O an..55 b CN Code C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT. Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box 3 and 3f) The value of the Data Item must be greater than zero. n8 c Commercial Description of the Goods O an..999 d Additional code O an..35 e Quantity C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box3 and 3f) The value of the Data Item must be greater than zero. n..15,3 f Unit of Measure Code C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box3 and 3f) (See Annex II to Regulation (EC) No 684/2009, Code list 12) n..2 g Gross Weight O The Gross Weight must be equal to or higher than Net Weight. The value of the Data Item must be greater than zero. n..15,2 h Net Weight O The Gross Weight must be equal to or higher than Net Weight. The value of the Data Item must be greater than zero. n..15,2 3.3 MEANS OF TRANSPORT C — ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in the <OTHER ACCOMPANYING DOCUMENT> data group — Does not apply otherwise (see box3 and 3f) a Trader Name R an..182 b Street Name R an..65 c Street Number O an..11 d Transporter Country R Provide a ‘Country Code’ listed in Code list 4 of Annex II to Regulation (EC) No 684/2009, but not listed in Code list 3 of Annex II to Regulation (EC) No 684/2009 and except ‘Country Code’‘GR’. a2 e Postcode R an..10 f City R an..50 g Transport Mode Code R Provide the mode of transport using the codes in Code list 7 of Annex II to Regulation (EC) No 684/2009. n..2 h ACO_Complementary Information C — ‘R’ if <MEANS OF TRANSPORT.Transport Mode Code> is ‘Other’ — Does not apply otherwise (see box 3.3 g) an..999 i ACO_Complementary Information_LNG C — ‘R’ if the corresponding text field(s) is (are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 j Registration R an..35 k Country of Registration R Provide a ‘Country Code’ listed in Code list 4 of Annex II to Regulation (EC) No 684/2009, but not listed in Code list 3 of Annex II to Regulation (EC) No 684/2009 and except ‘Country Code’‘GR’. a2 4 EVENT REPORT R a Date of Event R date b Place of Event R an..350 c Place of Event_LNG C — ‘R’ if the corresponding text field is used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 d Excise Officer Identification O an..35 e Submitting Person R an..35 f Submitting Person Code R (see Code list 10 in Annex II) n..2 g Submitting Person Complement C — ‘R’ if <Submitting Person Code> is ‘Other’ — ‘O’ otherwise (see Submitting Person Code in box 4f) an..350 h Submitting Person Complement_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 i Changed Transport Arrangement O The possible values are: 1 = Consignor 2 = Consignee 3 = Owner of goods 4 = Other n1 j Comments O an..350 k Comments_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 5 EVIDENCE OF EVENT O 9x a Issuing Authority O an..35 b Issuing Authority_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 c Evidence Type Code R (see Code list 6 in Annex II) n..2 d Evidence Type Complement C — ‘R’ <Evidence Type Code> is ‘Other’ — Does not apply otherwise (see Evidence Type Code in box 5c) an..350 e Evidence Type Complement_LNG C — ‘R’ if the corresponding text field(s) is(are) used — Does not apply otherwise Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. 2 f Reference of Evidence R an..350 g Reference of Evidence_LNG R Provide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data group. a2 h Image of Evidence O 6 TRADER New Transport Arranger C — Does not apply if <Changed Transport Arrangement> is ‘1’, ‘2’, or is not used — ‘R’ otherwise (see Changed Transport Arrangement in box 4i) a VAT Number O an..14 b Trader Name R an..182 c Street Name R an..65 d Street Number O an..11 e Postcode R an..10 f City R an..50 g NAD_LNG R Provi