OpenLegislation

Commission Implementing Regulation (EU) 2019/2223 of 13 December 2019 amending Implementing Regulation (EU) 2016/323 as regards the data required for mutual administrative assistance documents used for the purpose of the exchange of information regarding excise goods under suspension of excise duty

EU Regulation 2019/2223 · Adopted 13 December 2019 · Extends to United Kingdom

Original text. legislation.gov.uk does not revise this item, so later amendments are not shown here. Changes made to it are listed under each provision when known.

Commission Implementing Regulation (EU) 2019/2223

of 13 December 2019

amending Implementing Regulation (EU) 2016/323 as regards the data required for mutual administrative assistance documents used for the purpose of the exchange of information regarding excise goods under suspension of excise duty

THE EUROPEAN COMMISSION,

Having regard to the Treaty on the Functioning of the European Union,

Having regard to Council Regulation (EU) No 389/2012 of 2 May 2012 on administrative cooperation in the field of excise duties and repealing Regulation (EC) No 2073/2004f1, and in particular Article 9(2), Article 15(5) and Article 16(3) thereof,

Whereas:

(1)

Commission Implementing Regulation (EU) 2016/323f2 lays down the structure and content of mutual administrative assistance documents used for the exchange of information regarding excise goods under suspension of excise duty, as well as the codes required for the completion of certain data items in those documents.

(2)

Taking into account changes in the data requirements of a new version of the computerised system established by Decision No 1152/2003/EC of the European Parliament and of the Councilf3 and in order to ensure consistency, certain changes have to be made in the structure of messages and lists of codes used in mutual assistance documents.

(3)

The explanation in column F in Table 4 of Annex I to Implementing Regulation (EU) 2016/323 should be updated to provide a clear identification of the ‘Value’ data element when the ‘Primary Criterion’ type code is set to the value ‘46 = Type of Transport’.

(4)

The optionality of data group ‘Trader — Consignee’ in Table 5 and 14 of Annex I to Implementing Regulation (EU) 2016/323 should be updated so that relevant messages can be sent as a response to the query for an electronic administrative document with unknown destination or submission for export with local clearance.

(5)

In order to ensure the correct application of legislation on excise duties, the computerised system should provide a standard structure for mutual administrative assistance documents to support exchange of information where there is a need to manually close a movement of excise goods under suspension. In particular, the computerised system should provide a standard structure for a request for the manual closure of a movement of excise goods under suspension arrangement sent to the Member State of dispatch.

(6)

In order to prevent fraud or loss of excise duty the Member State of dispatch should always notify the competent authority of the Member State of destination or the Member State of export of the manual closure. The computerised system should provide a standard structure for such replies.

(7)

The values of several data items in Tables 4, 5, 7, 10, 11, 12 and 14 of Annex I to Implementing Regulation (EU) 2016/323 should be updated in order to improve the quality of information provided by economic operators. These further technical corrections should bring clarity and precision of applicable provisions.

(8)

For the purpose of manual closure, in order to ensure that the required information communicated to the involved competent authorities of the Member States is accurate and appropriate, the necessary code lists of manual closure request reasons and manual closure rejection reasons are created in Annex II to Implementing Regulation (EU) 2016/323.

(9)

Implementing Regulation (EU) 2016/323 should therefore be amended accordingly.

(10)

In order to align the application date of this Regulation with the application date for a new version of the computerised system established by Decision No 1152/2003/EC, this Regulation should apply from 13 February 2020.

(11)

The measures provided for in this Regulation are in accordance with the opinion of the Committee on Excise Duty,

HAS ADOPTED THIS REGULATION:

Annotations to the whole text

Footnotes

f1

OJ L 121, 8.5.2012, p. 1.

f2

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 (OJ L 66, 11.3.2016, p. 1).

f3

Decision No 1152/2003/EC of the European Parliament and of the Council of 16 June 2003 on computerising the movement and surveillance of excisable products (OJ L 162, 1.7.2003, p. 5).

Contents

  1. 1Article 1
  2. 2Article 2
  3. Signature
  4. Annex IAnnex I
  5. Annex IIAnnex II

1

Implementing Regulation (EU) 2016/323 is amended as follows:

  1. (1)

    the following Section IIA is inserted:

    ‘SECTION IIA

    Requests for manual closure

    Request for manual closure

    Article 6a

    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.’;

  2. (2)

    the following Article 14a is inserted:

    ‘Mandatory exchange of information — manual closure

    Article 14a

    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.’;

  3. (3)

    Annex I is amended in accordance with Annex I to this Regulation;

  4. (4)

    Annex II is amended in accordance with Annex II to this Regulation.

2

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

It shall apply from 13 February 2020.

Signature

Done at Brussels, 13 December 2019.

For the Commission

The President

Ursula von der Leyen

Annex I

In Annex I to Regulation (EC) 2016/323, Tables 4, 5, 7, 10, 11, 12 and 14 are replaced by the following and new Tables 15 and 16 are inserted:

‘

Table 4

(as referred to in Article 5(1))

Common Request

ABCDEFG
1 ATTRIBUTES R
a Request TypeR

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 NameC
    • ‘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 OfficeR (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    d Request Correlation IdentifierC
    • ‘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 DateC

    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 DateCdate
    g Single DateC
    • ‘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 CodeR (see Code list 3 in Annex II to Regulation (EC) No 684/2009) a2
    2.1 RA_PRIMARY CRITERION R99x
    a Primary Criterion Type CodeR

    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 O99x
    a ValueRIf <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 TypeR

    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 R99x
    a Member State CodeR (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 YearRThe value of the data element must be greater than zero.n4
    b SemesterC

    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 QuarterC

    The possible values are:

    1
  • First quarter

  • 2
  • Second quarter

  • 3
  • Third quarter

  • 4
  • Fourth quarter

  • n1
    d MonthC

    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 flagO

    The possible values are:

    0
  • No or False

  • 1
  • Yes or True

  • n1
    5.1 LIST OF CODES Code O99x
    a Requested List of CodeO

    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

    ABCDEFG
    1 ATTRIBUTES R
    a Requesting OfficeR (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    b Request Correlation IdentifierRThe value of <Request Correlation Identifier> is unique per Member State.an..44
    2 E-AD LIST ITEM O99x
    a Dispatch DateRdate
    2.1 EXCISE MOVEMENT R
    a ARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21
    b Date and Time of Validation of e-ADRdateTime
    c Sequence NumberRThe value of the data element must be greater than zero.n..2
    2.2 TRADER Consignor R
    a Trader Excise NumberR

    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 NameRan..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 ReferenceR

    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 NameOan..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 NumberR (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 IdentificationC

    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 CodeTRADER CONSIGNEE. Trader IdentificationTRADER 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. (1)

      The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>.

    2. (2)

      An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>.

    3. (3)

      The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>.

    4. (4)

      For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional.

    5. (5)

      An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>.

    6. (6)

      For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional.

    7. (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. (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 NumberC
    • ‘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 NameRan..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 IdentificationC

    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 CodeTRADER CONSIGNEE. Trader IdentificationTRADER 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. (1)

      The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>.

    2. (2)

      An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>.

    3. (3)

      The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>.

    4. (4)

      For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional.

    5. (5)

      An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>.

    6. (6)

      For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional.

    7. (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. (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 NameC

    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 CThe 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 applyDoes not apply
    a Office Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    2.8 EXCISE PRODUCTS CATEGORY Code R9x
    a Excise Product Category CodeR (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 NumberOan..14
    b Trader NameRan..182
    2.10 TRADER First Transporter O
    a VAT NumberOan..14
    b Trader NameRan..182

    Table 7

    (as referred to in Article 6(1))

    Administrative Cooperation Common Request

    ABCDEFG
    1 ATTRIBUTES R
    a Request TypeR

    The possible values are:

    1
  • Administrative cooperation

  • 2
  • Request for history

  • n1
    b Deadline for ResultsRdate
    2 FOLLOW UP R
    a Follow-Up Correlation IDR (see Code list 1 in Annex II) an28
    b Date of IssuanceRdate
    c Sender Member State CodeR 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 NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    e Sender OfficerOan..35
    f Addressee Member State CodeR 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 NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    h Addressee OfficerOan..35
    i National Case Reference IdentifierOan..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 InformationRan..999
    b Administrative Cooperation Request Information_LNGR 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 FlagO

    The possible values are:

    0
  • No or False

  • 1
  • Yes or True

  • n1
    3.1 REQUEST REASON Code R99x
    a Administrative Cooperation Request Reason CodeR (see Code list 8 in Annex II) n..2
    b ACO_Complementary InformationC
    • ‘R’ if <Administrative Cooperation Request Reason Code> is ‘Other’

    • ‘O’ otherwise

    —an..999
    c ACO_Complementary Information_LNGC
    • ‘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 O99x
    a Other Risk ProfileOan..999
    b Other Risk Profile_LNGC
    • ‘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 O99x
    a ARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21
    b Sequence NumberOThe value of the Data Item must be greater than zero.n..2
    3.3 TRADER Person O99x
    a Trader Excise NumberC

    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 NumberCan..14
    c Trader NameCan..182
    d Member State CodeC
    • ‘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 NameOan..65
    f Street NumberOan..11
    g PostcodeOan..10
    h CityOan..50
    i NAD_LNGC
    • ‘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 NumberOan..35
    k Fax NumberOan..35
    l Email AddressOan..70
    3.4 SUPPORTING DOCUMENTS O9x
    a Short Description of Supporting DocumentC
    • ‘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_LNGC
    • ‘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 DocumentC

    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_LNGC
    • ‘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 DocumentC

    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 TypeC

    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 O99x
    a Administrative Cooperation Action CodeR (see Code list 9 in Annex II) n..2
    b ACO Action ComplementC
    • ‘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_LNGC
    • ‘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 ARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21
    b History Request Scope TypeR

    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 DateC
    • Does not apply if <History Request Scope Type> is ‘3’

    • ‘R’ otherwise

    (see History Request Scope Type in box 4b)

    date
    d History Request ReasonRan..999
    e History Request Reason_LNGR 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 NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    b Submitting Excise OfficerOan..35
    c Tel. NumberOan..35
    d Fax NumberOan..35
    e Email AddressOan..70

    Table 10

    (as referred to in Article 6(3), Article 9(1) and Articles 10 and 16)

    Administrative Cooperation Results

    ABCDEFG
    1 FOLLOW UP R
    a Follow Up Correlation IDR (see Code list 1 in Annex II) an28
    b Date of IssuanceRdate
    c Sender Member State CodeR 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 NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    e Sender OfficerOan..35
    f Addressee Member State CodeR 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 NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    h Addressee OfficerOan..35
    i National Case Reference IdentifierC
    • ‘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 NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    b Submitting Excise OfficerOan..35
    c Tel. NumberOan..35
    d Fax NumberOan..35
    e Email AddressOan..70
    3 ACO_ACTION RESULT O99x
    a ARCO (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21
    b Sequence NumberC
    • ‘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 CodeR (see Code list 9 in Annex II) n..2
    d ACO Action ComplementC
    • ‘R’ if <Administrative Cooperation Action Code> is ‘Other’

    • ‘O’ otherwise

    (see Administrative Cooperation Action Code in box 3c)

    an..999
    e ACO Action Complement_LNGC
    • ‘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 CodeO (see Code list 11 in Annex II) n..2
    g ACO Action Not Possible Reason ComplementC
    • ‘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_LNGC
    • ‘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 DestinationO

    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 TypeC
    • ‘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_LNGC
    • ‘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 ExplanationsOan..999
    m Complementary Explanations_LNGC
    • ‘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 ReferenceO

    (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 ProvidedR

    The possible values are:

    0
  • No feedback requested

  • 1
  • Feedback requested

  • 2
  • Feedback provided

  • n1
    b Follow Up ActionsC

    At least one among these two fields if box 4a is given:

    • <Follow Up Actions>

    • <Relevance of Information>

    —an..999
    c Follow Up Actions_LNGC
    • ‘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 ProvidedC

    At least one among these two fields if box 4a is given:

    • < Follow Up Actions>

    • <Relevance of Information>

    —an..999
    e Relevance of Information_LNGC
    • ‘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 O9x
    a Short Description of Supporting DocumentC
    • ‘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_LNGC
    • ‘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 DocumentC

    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_LNGC
    • ‘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 DocumentC

    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 TypeC

    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

    ABCDEFG
    1 ATTRIBUTES R
    a Message TypeR

    The possible values are:

    1
  • Validated document

  • n1
    b Date and Time of Validation of Control ReportC
    • ‘R’ after successful validation

    • Does not apply otherwise

    dateTime
    2 CONTROL REPORT HEADER R
    a Control Report ReferenceR (see Code list 2 in Annex II) an16
    2.1 CONTROL OFFICE R
    a Control Office Reference NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    b Member State CodeC

    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 NameCan..35
    d Street NameCan..65
    e Street NumberCan..11
    f PostcodeCan..10
    g CityCan..50
    h Phone NumberC

    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 NumberCan..35
    j Email AddressCan..70
    k NAD_LNGC‘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 COne of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present
    a ARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21
    b Sequence NumberRThe value of the Data Item must be greater than zero.n..2
    4 OTHER ACCOMPANYING DOCUMENT COne of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present
    a Other Accompanying Document TypeR

    The possible values are:

    0
  • Other

  • 2
  • SAAD

  • n1
    b Short Description of Other Accompanying DocumentC

    ‘R’ if <Other Accompanying Document Type> is ‘Other’

    It doesn’t apply otherwise

    an…350
    c Short Description of Other Accompanying Document_LNGC
    • ‘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 NumberRan…350
    e Other Accompanying Document DateRdate
    f Image of Other Accompanying DocumentO
    g Member State of DispatchR 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 DestinationR 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 O9x
    a Trader Excise NumberC

    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 IdentificationC

    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 NameC

    At least one of the following attributes must be present:

    • <Trader Excise Number>

    • <Trader Identification>

    • <Trader Name>

    —an..182
    d Trader Person TypeO

    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 CodeC

    ‘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 NameOan..65
    g Street NumberOan..11
    h PostcodeOan..10
    i CityOan..50
    j NAD_LNGC
    • ‘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 NumberOan..35
    m Email AddressOan..70
    4.2 GOODS ITEM O999x
    a Description of the GoodsOan..55
    b CN CodeC
    • ‘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 GoodsOan..999
    d Additional codeOan..35
    e QuantityC
    • ‘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 CodeC
    • ‘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 WeightO

    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 WeightO

    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 NameRan..182
    b Street NameRan..65
    c Street NumberOan..11
    d Transporter CountryR 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 PostcodeRan..10
    f CityRan..50
    g Transport Mode CodeR 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 InformationC
    • ‘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_LNGC
    • ‘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 RegistrationRan..35
    k Country of RegistrationR 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 ControlRdate
    b Place of ControlRan..350
    c Place of Control_LNGR 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 TypeR

    The possible values are:

    1
  • Physical control

  • 2
  • Documentary control

  • n1
    e Reason for ControlR

    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 ReferenceOan..350
    g Complementary Origin Reference_LNGC
    • ‘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 IdentityRan..350
    i Control Officer Identity_LNGR 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 ConclusionR

    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 RequiredR

    The possible values are:

    0
  • No or False

  • 1
  • Yes or True

  • n1
    l FlagR

    The possible values are:

    0
  • No or False

  • 1
  • Yes or True

  • n1
    m CommentsOan..350
    n Comments_LNGC
    • ‘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 R99x
    a Performed Control ActionR

    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 ActionC
    • ‘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_LNGC
    • ‘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 AuthorityOan..35
    b Issuing Authority_LNGC
    • ‘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 CodeR (see Code list 6 in Annex II) n..2
    d Evidence Type ComplementC
    • ‘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_LNGC
    • ‘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 EvidenceOan..350
    g Reference of Evidence_LNGC
    • ‘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 EvidenceO
    5.3 UNSATISFACTORY REASON O9x
    a Unsatisfactory Reason CodeR (see Code list 12 in Annex II) n..2
    b Complementary InformationC
    • ‘R’ if <Unsatisfactory Reason Code> is ‘Other’

    • Does not apply otherwise

    (see Unsatisfactory Reason Code in box 5.3a)

    an..350
    c Complementary Information_LNGC
    • ‘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 O99x
    a Transport Unit CodeR (see Code list 7 in Annex II to Regulation (EC) No 684/2009) n..2
    b Identity of Transport UnitsC
    • ‘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 SealOan..35
    d Seal InformationOan..350
    e Seal Information_LNGC
    • ‘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 InformationOan..350
    g Complementary Information_LNGC
    • ‘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 O99x
    a Body Record Unique ReferenceC
    • ‘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 GoodsC
    • ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present

    • Does not apply otherwise

    —an..55
    c CN CodeC
    • ‘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 codeC
    • ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present

    • Does not apply otherwise

    —an..35
    e Indicator of Shortage or ExcessO

    The possible values are:

    S
  • Shortage

  • E
  • Excess

  • a1
    f Observed Shortage or ExcessC
    • ‘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 CommentsOan..350
    h Comments_LNGC
    • ‘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 O9x
    a Unsatisfactory Reason CodeR (see Code list 12 in Annex II) n..2
    b Complementary InformationC
    • ‘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_LNGC
    • ‘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

    ABCDEFG
    1 ATTRIBUTES R
    a Message TypeR

    The possible values are:

    1
  • Initial submission

  • 3
  • Validated document

  • n1
    b Date and Time of Validation of Event ReportC
    • ‘R’ after successful validation,

    • Does not apply otherwise

    —dateTime
    2 EVENT REPORT HEADER R
    a Event Report NumberC
    • ‘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 ReferenceC
    • ‘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 ARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009) an21
    d Sequence NumberRThe value of the data element must be greater than zero.n..2
    3 OTHER ACCOMPANYING DOCUMENT COne of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present
    a Other Accompanying Document TypeR

    The possible values are:

    0
  • Other

  • 2
  • SAAD

  • n1
    b Short Description of Other Accompanying DocumentC
    • ‘R’ if <Other Accompanying Document Type> is ‘Other’

    • It doesn’t apply otherwise

    an..350
    c Short Description of Other Accompanying Document_LNGC
    • ‘R’ if the corresponding text field(s) is (are) used

    • Does not apply otherwise

    a2
    d Other Accompanying Document NumberRan..350
    e Other Accompanying Document DateRdate
    f Image of Other Accompanying DocumentO
    g Member State of DispatchR 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 DestinationR 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 O9x
    a Trader Excise NumberC
    • 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 IdentificationC
    • 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 NameC
    • At least one of the following attributes must be present:

    • <Trader Excise Number>

    • <Trader Identification>

    • <Trader Name>

    —an..182
    d Trader Person TypeO

    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 CodeC
    • ‘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 NameOan..65
    g Street NumberOan..11
    h PostcodeOan..10
    j NAD_LNGC
    • ‘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 NumberOan..35
    l Fax NumberOan..35
    m Email AddressOan..70
    3.2 GOODS ITEM O999x
    a Description of the GoodsOan..55
    b CN CodeC
    • ‘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 GoodsOan..999
    d Additional codeOan..35
    e QuantityC
    • ‘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 CodeC
    • ‘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 WeightO

    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 WeightO

    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 NameRan..182
    b Street NameRan..65
    c Street NumberOan..11
    d Transporter CountryR 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 PostcodeRan..10
    f CityRan..50
    g Transport Mode CodeRProvide 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 InformationC
    • ‘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_LNGC
    • ‘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 RegistrationRan..35
    k Country of RegistrationR 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 EventRdate
    b Place of EventRan..350
    c Place of Event_LNGC
    • ‘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 IdentificationOan..35
    e Submitting PersonRan..35
    f Submitting Person CodeR (see Code list 10 in Annex II) n..2
    g Submitting Person ComplementC
    • ‘R’ if <Submitting Person Code> is ‘Other’

    • ‘O’ otherwise

    (see Submitting Person Code in box 4f)

    an..350
    h Submitting Person Complement_LNGC
    • ‘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 ArrangementO

    The possible values are:

    1
  • Consignor

  • 2
  • Consignee

  • 3
  • Owner of goods

  • 4
  • Other

  • n1
    j CommentsOan..350
    k Comments_LNGC
    • ‘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 O9x
    a Issuing AuthorityOan..35
    b Issuing Authority_LNGC
    • ‘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 CodeR (see Code list 6 in Annex II) n..2
    d Evidence Type ComplementC
    • ‘R’ <Evidence Type Code> is ‘Other’

    • Does not apply otherwise

    (see Evidence Type Code in box 5c)

    an..350
    e Evidence Type Complement_LNGC
    • ‘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 EvidenceRan..350
    g Reference of Evidence_LNGR 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 EvidenceO
    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 NumberOan..14
    b Trader NameRan..182
    c Street NameRan..65
    d Street NumberOan..11
    e PostcodeRan..10
    f CityRan..50
    g NAD_LNGR 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 TRADER New Transporter O
    a VAT NumberOan..14
    b Trader NameRan..182
    c Street NameRan..65
    d Street NumberOan..11
    e PostcodeRan..10
    f CityRan..50
    g NAD_LNGR 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 TRANSPORT DETAILS O99x
    a Transport Unit CodeR (see Code list 7 in Annex II to Regulation (EC) No 684/2009) n..2
    b Identity of Transport UnitsC
    • Does not apply if <Transport Unit Code> is ‘Fixed transport installations’.

    • ‘R’ otherwise

    (see Transport Unit Code in box 8a)

    an..35
    c Identity of Commercial SealOan..35
    d Seal InformationOan..350
    e Seal Information_LNGC
    • ‘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 InformationOan..350
    g Complementary Information_LNGC
    • ‘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
    9 EVENT REPORT Body C
    • ‘O’ if <TRADER New Transport Arranger> is used, or <TRADER New Transporter> is used, or <TRANSPORT DETAILS> is used

    • ‘R’ otherwise

    (see TRADER New Transport Arranger in 6, TRADER New Transport in 7, and TRANSPORT DETAILS in 8)

    99x
    a Event Type CodeR (see Code list 14 in Annex II) n..2
    b Associated InformationC
    • ‘R’ if <Event Type Code> is ‘0’

    • ‘O’ otherwise

    (see Event Type Code in box 9a)

    an..350
    c Associated Information_LNGC
    • ‘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 Body Record Unique ReferenceC
    • ‘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
    e Description of the GoodsC
    • ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present

    • Does not apply otherwise

    an..55
    f CN CodeC
    • ‘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
    g Additional codeC
    • ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present

    • Does not apply otherwise

    an..35
    h Indicator of Shortage or ExcessC

    For 9h and 9i:

    • ‘R’ if <Body Record Unique Reference> or <Description of the Goods> or <CN Code> or <Additional Code> is given

    • Does not apply otherwise

    (see Body Record Unique Reference in box 9d, Description of the Goods in box 9e, CN Code in box 9f and Additional Code in box 9g)

    The possible values are:

    S
  • Shortage

  • E
  • Excess

  • a1
    iObserved Shortage or ExcessCThe value of the Data Item must be greater than zero.n..15,3

    Table 14

    (as referred to in Article 13)

    Alert or Rejection of an e-AD

    ABCDEFG
    1 ATTRIBUTES R
    a Date and Time of Validation of Alert or RejectionC
    • R if corresponding field is validated

    • Does not apply otherwise

    dateTime
    2 EXCISE MOVEMENT e-AD R
    a ARCR

    Provide the ARC of the e-AD.

    (see Code list 2 in Annex II to Regulation (EC) No 684/2009)

    an21
    b Sequence NumberRThe value of the data element must be greater than zero.n..2
    3 TRADER Consignee C‘R’, except for message type ‘2 — Submission for export with local clearance’ or for Destination Type Code 8
    a Trader IdentificationC
    • ‘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:an..16
    Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER 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. (1)

      The operator type of the consignee is ‘Authorised warehouse keeper’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>.

    2. (2)

      An existing identifier <Tax Warehouse Reference> in the set of <TAX WAREHOUSE>.

    3. (3)

      The operator type of the consignee is ‘Registered consignee’. An existing identifier <Trader Excise Number> in the set of <TRADER AUTHORISATION>.

    4. (4)

      For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional.

    5. (5)

      An existing <Temporary Authorisation Reference> in the set of <TEMPORARY AUTHORISATION>.

    6. (6)

      For the place of delivery, ‘Any identification’ means: a VAT number or any other identifier; it is optional.

    7. (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. (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 NumberC
    • ‘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 NameRan..182
    d Street NameRan..65
    e Street NumberOan..11
    f PostcodeRan..10
    g CityRan..50
    h NAD_LNGR 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 OFFICE OF DESTINATION R
    a Office Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009) an8
    5 ALERT R
    a Date of AlertRdate
    b e-AD Rejected flagRThe format of Boolean is digital: ‘0’ or ‘1’ (‘0’ = No or False; ‘1’ = Yes or True).n1
    6 ALERT OR REJECTION OF E-AD REASON Code C
    • ‘R’ if <e-AD Rejected flag> is True

    • ‘O’ if otherwise

    9x
    a Alert or Rejection of E-AD Reason CodeR (see Code list 5 in Annex II) n..2
    b Complementary InformationC
    • ‘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 6a)

    an..350
    c Complementary Information_LNGC
    • ‘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 15

    (as referred to in Article 6a)

    Manual Closure Request

    ABCDEFG
    1 ATTRIBUTE R
    a ARCR

    Provide the ARC of the e-AD.

    (see Code list 2 in Annex II to Regulation (EC) No 684/2009)

    an21
    b Sequence NumberR Provide the sequence number of the e-AD. n..2
    c Manual Closure Request Reason CodeR (see code list 16 in Annex II) n1
    d Manual Closure Reason ComplementC
    • ‘R’ if <Manual Closure Request Reason Code> is ‘Other’

    • ‘O’ otherwise

    an..999
    e Manual Closure Reason Complement_LNGC
    • ‘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
    2 SUPPORTING DOCUMENTS O 9x
    a Short Description of Supporting DocumentC
    • ‘R’ if <Supporting Document Type> is ‘Other’

    • Does not apply otherwise

    an..999
    b Short Description of Supporting Document_LNGC
    • ‘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 DocumentC

    At least one, among these three fields, must be present:

    • <Supporting Document Type>

    • <Reference of Supporting Document>

    • <Image of Document>

    (see Image of Document in box 2e and Supporting Document Type in box 2f)

    an..999
    d Reference of Supporting Document_LNGC
    • ‘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 DocumentC

    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 2c and Supporting Document Type in box 2f)

    f Supporting Document TypeC

    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 2c and Image of Document in box 2e)

    (see code list 15 in Annex II) n..4
    3 MANUAL CLOSURE Body O 999X
    a Body Record Unique ReferenceR

    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 this data element must be greater than zero.

    n..3
    b Indicator of Shortage or ExcessO

    The possible values are:

    S
  • Shortage

  • E
  • Excess

  • a1
    c Observed Shortage or ExcessC
    • ‘R’ if <Indicator of Shortage or Excess> is given

    • Does not apply otherwise

    (see Indicator of Shortage or Excess in box 3b)

    The value of the Data Item must be greater than zero.n..15,3
    d Excise Product CodeO (see Code list 11 in Annex II to Regulation (EC) No 684/2009) an4
    e Refused QuantityOThe value of this data element must be greater than zero.n..15,3
    f Complementary InformationOan..350
    g Complementary Information_LNGC
    • ‘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

    Table 16

    (as referred to in Article 14a)

    Manual Closure Response

    ABCDEFG
    1 ATTRIBUTE R
    a ARCR

    Provide the ARC of the e-AD.

    (see Code list 2 in Annex II to Regulation (EC) No 684/2009)

    an21
    b Sequence NumberR Provide the sequence number of the e-AD. n..2
    c Date of Arrival of Excise ProductsOThe date at which the movement ends in accordance with Article 20(2) of Directive 2008/118/EC.date
    d Global Conclusion of ReceiptO

    The possible values are:

    1
  • Receipt accepted and satisfactory,

  • 2
  • Receipt accepted although unsatisfactory,

  • 3
  • Receipt refused,

  • 4
  • Receipt partially refused,

  • 21
  • Exit accepted and satisfactory,

  • 22
  • Exit accepted although unsatisfactory,

  • 23
  • Exit refused.

  • n..2
    e Complementary InformationOan..350
    f Complementary Information_LNGC
    • ‘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
    g Manual Closure Request Reason CodeR (see code list 16 in Annex II) n1
    h Manual Closure Reason ComplementC
    • ‘R’ if <Manual Closure Request Reason Code> is ‘Other’

    • ‘O’ otherwise

    an..999
    i Manual Closure Reason Complement_LNGC
    • ‘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
    j Manual Closure Request AcceptedRThe format of Boolean is digital: ‘0’ or ‘1’ (‘0’ = No or False; ‘1’ = Yes or True).n1
    k Manual Closure Rejection Reason CodeC
    • ‘R’ if <Manual Closure Request Accepted> is ‘0’

    • Does not apply otherwise

    (see code list 17 in Annex II) n1
    l Manual Closure Rejection ComplementC
    • ‘R’ if <Manual Closure Rejection Reason Code> is ‘Other’

    • ‘O’ otherwise

    an..999
    m Manual Closure Rejection Complement_LNGC
    • ‘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
    2 SUPPORTING DOCUMENTS O 9x
    a Short Description of Supporting DocumentC
    • ‘R’ if <Supporting Document Type> is ‘Other’

    • Does not apply otherwise

    an..999
    b Short Description of Supporting Document_LNGC
    • ‘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
    c Reference of Supporting DocumentC

    At least one, among these three fields, must be present:

    • <Supporting Document Type>

    • <Reference of Supporting Document>

    • <Image of Document>

    (see Image of Document in box 2e and Supporting Document Type in box 2f)

    an..999
    d Reference of Supporting Document_LNGC
    • ‘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 DocumentC

    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 2c and Supporting Document Type in box 2f)

    f Supporting Document TypeC

    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 2c and Image of Document in box 2e)

    (see code list 15 in Annex II) n..4
    3 MANUAL CLOSURE Body O 999X
    a Body Record Unique ReferenceR

    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 this data element must be greater than zero.

    n..3
    b Indicator of Shortage or ExcessO

    The possible values are:

    S
  • Shortage

  • E
  • Excess

  • a1
    c Observed Shortage or ExcessC
    • ‘R’ if <Indicator of Shortage or Excess> is given

    • Does not apply otherwise

    (see Indicator of Shortage or Excess in box 3b)

    The value of the Data Item must be greater than zero.n..15,3
    d Excise Product CodeO (see Code list 11 in Annex II to Regulation (EC) No 684/2009) an4
    e Refused QuantityOThe value of this data element must be greater than zero.n..15,3
    f Complementary InformationOan..350
    g Complementary Information_LNGC
    • ‘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

    ’

    Annex II

    In Annex II to Regulation (EC) 2016/323 is amended as follows:

    1. (1)

      In code list 4 (Refusal Reasons), in the row 8, the entry for ‘Description’ is replaced by the following:

      ‘The requested Member State is unable, for legal reasons, to provide similar information’.

    2. (2)

      In code list 15 (Type of Document), after the row 18, a new row is inserted as follows:

      ‘

      <TARIC CODE>Any TARIC code used in ‘box 44’ of the SAD

      ’

    3. (3)

      A new code list 16 (Manual Closure Request Reasons) is inserted as follows:

      ‘

      Code list 16: Manual Closure Request Reasons
      CodeDescription
      0Other
      1Export closed but no IE518 available
      2Consignee no longer connected to EMCS
      3Exempted consignee
      4Exit confirmed but no IE829 submitted (IE818 out of sequence)
      5No movement but cancellation no longer possible
      6Multiple issuances of e-ADs for a single movement
      7e-AD does not cover actual movement
      8Erroneous report of receipt
      9Erroneous rejection of an e-AD

      ’

    4. (4)

      A new code list 17 (Manual Closure Rejection Reasons) is inserted as follows:

      ‘

      Code list 17: Manual Closure Rejection Reasons
      CodeDescription
      0Other
      1Evidence provided does not justify manual closure
      2Request Reason provided does not justify manual closure

      ’