Search Legislation

Commission Implementing Regulation (EU) 2019/2223Show full title

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

 Help about what version

What Version

 Help about advanced features

Advanced Features

 Help about UK-EU Regulation

Legislation originating from the EU

When the UK left the EU, legislation.gov.uk published EU legislation that had been published by the EU up to IP completion day (31 December 2020 11.00 p.m.). On legislation.gov.uk, these items of legislation are kept up-to-date with any amendments made by the UK since then.

Close

This item of legislation originated from the EU

Legislation.gov.uk publishes the UK version. EUR-Lex publishes the EU version. The EU Exit Web Archive holds a snapshot of EUR-Lex’s version from IP completion day (31 December 2020 11.00 p.m.).

Changes over time for: Commission Implementing Regulation (EU) 2019/2223

 Help about opening options

Changes to legislation:

This version of this Regulation was derived from EUR-Lex on IP completion day (31 December 2020 11:00 p.m.). It has not been amended by the UK since then. Find out more about legislation originating from the EU as published on legislation.gov.uk. Help about Changes to Legislation

Close

Changes to Legislation

Revised legislation carried on this site may not be fully up to date. At the current time any known changes or effects made by subsequent legislation have been applied to the text of the legislation you are viewing by the editorial team. Please see ‘Frequently Asked Questions’ for details regarding the timescales for which new effects are identified and recorded on this site.

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/2004(1), and in particular Article 9(2), Article 15(5) and Article 16(3) thereof,

Whereas:

(1) Commission Implementing Regulation (EU) 2016/323(2) 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 Council(3) 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:

Article 1U.K.

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

(1)

the following Section IIA is inserted:

SECTION IIAU.K. Requests for manual closure

Article 6aRequest 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.;

(2)

the following Article 14a is inserted:

Article 14aMandatory 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.;

(3)

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

(4)

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

Article 2U.K.

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.

Done at Brussels, 13 December 2019.

For the Commission

The President

Ursula von der Leyen

ANNEX IU.K.

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 ATTRIBUTESR
aRequest 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
bRequest 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
cRequesting OfficeR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
dRequest 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
eStart 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
fEnd DateCdate
gSingle DateC
  • ‘R’ if <Request Type> is ‘2’ or ‘5’

  • Does not apply otherwise

(see Request Type in box 1a)

date
2 E-AD LIST REQUESTC
  • ‘R’ if <Request Type> is ‘6’

  • Does not apply otherwise

(see Request Type in box 1a)

aMember State CodeR (see Code list 3 in Annex II to Regulation (EC) No 684/2009)a2
2.1 RA_PRIMARY CRITERIONR99x
aPrimary 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 VALUEO99x
aValueRIf <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_REQUESTC
  • ‘R’ if <Request Type> is ‘7’

  • Does not apply otherwise

(see Request Type in box 1a)

aStatistic 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 CodeR99x
aMember State CodeR (see Code list 3 in Annex II to Regulation (EC) No 684/2009)a2
4 STA_PERIODC
  • ‘R’ if <Request Type> is ‘7’

  • Does not apply otherwise

(see Request Type in box 1a)

aYearRThe value of the data element must be greater than zero.n4
bSemesterC

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
cQuarterC

The possible values are:

1

=

First quarter

2

=

Second quarter

3

=

Third quarter

4

=

Fourth quarter

n1
dMonthC

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_REQUESTC
  • ‘R’ if <Request Type> is ‘2’

  • Does not apply otherwise

(see Request Type in box 1a)

aCommon Risk Assessment Criteria flagO

The possible values are:

0

=

No or False

1

=

Yes or True

n1
5.1 LIST OF CODES CodeO99x
aRequested 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 ATTRIBUTESR
aRequesting OfficeR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
bRequest Correlation IdentifierRThe value of <Request Correlation Identifier> is unique per Member State.an..44
2 E-AD LIST ITEMO99x
aDispatch DateRdate
2.1 EXCISE MOVEMENTR
aARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bDate and Time of Validation of e-ADRdateTime
cSequence NumberRThe value of the data element must be greater than zero.n..2
2.2 TRADER ConsignorR
aTrader 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
bTrader NameRan..182
2.3 TRADER Place of DispatchC

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’

aTax 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
bTrader NameOan..182
2.4 OFFICE of Dispatch — ImportC

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’

aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
2.5 TRADER ConsigneeC‘R’, except for message type ‘2 — Submission for export with local clearance’ or for Destination Type Code 8
aTrader 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)

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)
bEORI 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
cTrader NameRan..182
2.6 TRADER Place of DeliveryC

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.

aTrader 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)

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)
bTrader 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 — CustomsCThe 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
aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
2.8 EXCISE PRODUCTS CATEGORY CodeR9x
aExcise Product Category CodeR (see Code list 3 in Annex II to Regulation (EU) No 612/2013)a1
2.9 TRADER Transport ArrangerC

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’

aVAT NumberOan..14
bTrader NameRan..182
2.10 TRADER First TransporterO
aVAT NumberOan..14
bTrader NameRan..182

Table 7

(as referred to in Article 6(1))

Administrative Cooperation Common Request

ABCDEFG
1 ATTRIBUTESR
aRequest TypeR

The possible values are:

1

=

Administrative cooperation

2

=

Request for history

n1
bDeadline for ResultsRdate
2 FOLLOW UPR
aFollow-Up Correlation IDR (see Code list 1 in Annex II)an28
bDate of IssuanceRdate
cSender 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
dSender Office Reference NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
eSender OfficerOan..35
fAddressee 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
gAddressee Office Reference NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
hAddressee OfficerOan..35
iNational Case Reference IdentifierOan..99
3 ACO_REQUESTC
  • ‘R’ if <Request Type> is ‘1’

  • Does not apply otherwise

(see Request Type in box 1a)

aAdministrative Cooperation Request InformationRan..999
bAdministrative 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
cFlagO

The possible values are:

0

=

No or False

1

=

Yes or True

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

  • ‘O’ otherwise

an..999
cACO_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 REFERENCEO99x
aOther Risk ProfileOan..999
bOther 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 ListO99x
aARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bSequence NumberOThe value of the Data Item must be greater than zero.n..2
3.3 TRADER PersonO99x
aTrader 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
bVAT NumberCan..14
cTrader NameCan..182
dMember 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
eStreet NameOan..65
fStreet NumberOan..11
gPostcodeOan..10
hCityOan..50
iNAD_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
jPhone NumberOan..35
kFax NumberOan..35
lEmail AddressOan..70
3.4 SUPPORTING DOCUMENTSO9x
aShort 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
bShort 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
cReference 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
dReference 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
eImage 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)

fSupporting 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 RequestedO99x
aAdministrative Cooperation Action CodeR (see Code list 9 in Annex II)n..2
bACO Action ComplementC
  • ‘R’ if <Administrative Cooperation Action Code> is ‘Other’

  • ‘O’ otherwise

(see Administrative Cooperation Action Code in box 3.5a)

an..999
cACO 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 REQUESTC
  • ‘R’ if <Request Type> is ‘2’

  • Does not apply otherwise

(see Request Type in box 1a)

aARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bHistory 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
cScope DateC
  • Does not apply if <History Request Scope Type> is ‘3’

  • ‘R’ otherwise

(see History Request Scope Type in box 4b)

date
dHistory Request ReasonRan..999
eHistory 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 CONTACTO
aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
bSubmitting Excise OfficerOan..35
cTel. NumberOan..35
dFax NumberOan..35
eEmail 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 UPR
aFollow Up Correlation IDR (see Code list 1 in Annex II)an28
bDate of IssuanceRdate
cSender 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
dSender Office Reference NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
eSender OfficerOan..35
fAddressee 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
gAddressee Office Reference NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
hAddressee OfficerOan..35
iNational 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 CONTACTO
aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
bSubmitting Excise OfficerOan..35
cTel. NumberOan..35
dFax NumberOan..35
eEmail AddressOan..70
3 ACO_ACTION RESULTO99x
aARCO (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bSequence 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
cAdministrative Cooperation Action CodeR (see Code list 9 in Annex II)n..2
dACO Action ComplementC
  • ‘R’ if <Administrative Cooperation Action Code> is ‘Other’

  • ‘O’ otherwise

(see Administrative Cooperation Action Code in box 3c)

an..999
eACO 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
fACO Action Not Possible Reason CodeO (see Code list 11 in Annex II)n..2
gACO 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
hACO 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
iFinding 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
jOther Finding TypeC
  • ‘R’ if <Finding at Destination> is ‘Other finding’

  • Does not apply otherwise

(see Finding at Destination in box 3i)

an..999
kOther 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
lComplementary ExplanationsOan..999
mComplementary 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
nControl 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 REQUESTO
aFeedback Requested or ProvidedR

The possible values are:

0

=

No feedback requested

1

=

Feedback requested

2

=

Feedback provided

n1
bFollow Up ActionsC

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

  • <Follow Up Actions>

  • <Relevance of Information>

an..999
cFollow 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
dRelevance of Information ProvidedC

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

  • < Follow Up Actions>

  • <Relevance of Information>

an..999
eRelevance 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 DOCUMENTSO9x
aShort Description of Supporting DocumentC
  • ‘R’ if <Supporting Document Type> is ‘Other’

  • Doesn’t apply otherwise

(See Supporting Document Type in box 5f)

an..999
bShort 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
cReference 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
dReference 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
eImage 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)

fSupporting 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 ATTRIBUTESR
aMessage TypeR

The possible values are:

1

=

Validated document

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

  • Does not apply otherwise

dateTime
2 CONTROL REPORT HEADERR
aControl Report ReferenceR (see Code list 2 in Annex II)an16
2.1 CONTROL OFFICER
aControl Office Reference NumberO (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
bMember 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
cControl Office NameCan..35
dStreet NameCan..65
eStreet NumberCan..11
fPostcodeCan..10
gCityCan..50
hPhone 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
iFax NumberCan..35
jEmail AddressCan..70
kNAD_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-ADCOne of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present
aARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bSequence NumberRThe value of the Data Item must be greater than zero.n..2
4 OTHER ACCOMPANYING DOCUMENTCOne of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present
aOther Accompanying Document TypeR

The possible values are:

0

=

Other

2

=

SAAD

n1
bShort Description of Other Accompanying DocumentC

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

It doesn’t apply otherwise

an…350
cShort 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
dOther Accompanying Document NumberRan…350
eOther Accompanying Document DateRdate
fImage of Other Accompanying DocumentO
gMember 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
hMember 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 MovementO9x
aTrader 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
bTrader 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
cTrader NameC

At least one of the following attributes must be present:

  • <Trader Excise Number>

  • <Trader Identification>

  • <Trader Name>

an..182
dTrader 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
eMember 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
fStreet NameOan..65
gStreet NumberOan..11
hPostcodeOan..10
iCityOan..50
jNAD_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
kPhone NumberOan..35
mEmail AddressOan..70
4.2 GOODS ITEMO999x
aDescription of the GoodsOan..55
bCN 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
cCommercial Description of the GoodsOan..999
dAdditional codeOan..35
eQuantityC
  • ‘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
fUnit 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
gGross 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
hNet 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 TRANSPORTC
  • ‘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)

aTrader NameRan..182
bStreet NameRan..65
cStreet NumberOan..11
dTransporter 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
ePostcodeRan..10
fCityRan..50
gTransport 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
hACO_Complementary InformationC
  • ‘R’ if <MEANS OF TRANSPORT. Transport Mode Code> is ‘Other’

  • Does not apply otherwise

(see box 4.3 g)

an..999
iACO_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
jRegistrationRan..35
kCountry 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 REPORTR
aDate of ControlRdate
bPlace of ControlRan..350
cPlace 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
dControl TypeR

The possible values are:

1

=

Physical control

2

=

Documentary control

n1
eReason 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
fComplementary Origin ReferenceOan..350
gComplementary 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
hControl Officer IdentityRan..350
iControl 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
jGlobal 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
kControl at Arrival RequiredR

The possible values are:

0

=

No or False

1

=

Yes or True

n1
lFlagR

The possible values are:

0

=

No or False

1

=

Yes or True

n1
mCommentsOan..350
nComments_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 ACTIONR99x
aPerformed 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
bOther Control ActionC
  • ‘R’ if <Performed Control Action> is ‘0’

  • Does not apply otherwise

(see Performed Control Action in box 5.1a)

an..350
cOther 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 EVIDENCEC
  • ‘R’ if <Reason for Control> is ‘2’

  • ‘O’ otherwise

(see Reason for Control in box 5e)

9x
aIssuing AuthorityOan..35
bIssuing 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
cEvidence Type CodeR (see Code list 6 in Annex II)n..2
dEvidence Type ComplementC
  • ‘R’ if <Evidence Type Code> is ‘Other’

  • Does not apply otherwise

(see Evidence Type Code in box 5.2c)

an..350
eEvidence 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
fReference of EvidenceOan..350
gReference 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
hImage of EvidenceO
5.3 UNSATISFACTORY REASONO9x
aUnsatisfactory Reason CodeR (see Code list 12 in Annex II)n..2
bComplementary InformationC
  • ‘R’ if <Unsatisfactory Reason Code> is ‘Other’

  • Does not apply otherwise

(see Unsatisfactory Reason Code in box 5.3a)

an..350
cComplementary 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 DETAILSO99x
aTransport Unit CodeR (see Code list 7 in Annex II to Regulation (EC) No 684/2009)n..2
bIdentity 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
cIdentity of Commercial SealOan..35
dSeal InformationOan..350
eSeal 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
fComplementary InformationOan..350
gComplementary 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 BodyO99x
aBody 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
bDescription of the GoodsC
  • ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present

  • Does not apply otherwise

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

  • Does not apply otherwise

an..35
eIndicator of Shortage or ExcessO

The possible values are:

S

=

Shortage

E

=

Excess

a1
fObserved 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
gCommentsOan..350
hComments_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 REASONO9x
aUnsatisfactory Reason CodeR (see Code list 12 in Annex II)n..2
bComplementary InformationC
  • ‘R’ if <Unsatisfactory Reason Code> is ‘Other’

  • ‘O’ otherwise

(see Indicator of Unsatisfactory Reason Code in box 5.5.1a)

an..350
cComplementary 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 ATTRIBUTESR
aMessage TypeR

The possible values are:

1

=

Initial submission

3

=

Validated document

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

  • Does not apply otherwise

dateTime
2 EVENT REPORT HEADERR
aEvent 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
bMS 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
cARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
dSequence NumberRThe value of the data element must be greater than zero.n..2
3 OTHER ACCOMPANYING DOCUMENTCOne of the <EXCISE MOVEMENT e-AD> or <OTHER ACCOMPANYING DOCUMENT> data groups must be present
aOther Accompanying Document TypeR

The possible values are:

0

=

Other

2

=

SAAD

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

  • It doesn’t apply otherwise

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

  • Does not apply otherwise

a2
dOther Accompanying Document NumberRan..350
eOther Accompanying Document DateRdate
fImage of Other Accompanying DocumentO
gMember 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
hMember 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 MovementO9x
aTrader 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
bTrader 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
cTrader NameC
  • At least one of the following attributes must be present:

  • <Trader Excise Number>

  • <Trader Identification>

  • <Trader Name>

an..182
dTrader 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
eMember 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
fStreet NameOan..65
gStreet NumberOan..11
hPostcodeOan..10
jNAD_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
kPhone NumberOan..35
lFax NumberOan..35
mEmail AddressOan..70
3.2 GOODS ITEMO999x
aDescription of the GoodsOan..55
bCN 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
cCommercial Description of the GoodsOan..999
dAdditional codeOan..35
eQuantityC
  • ‘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
fUnit 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
gGross 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
hNet 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 TRANSPORTC
  • ‘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)

aTrader NameRan..182
bStreet NameRan..65
cStreet NumberOan..11
dTransporter 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
ePostcodeRan..10
fCityRan..50
gTransport Mode CodeRProvide the mode of transport using the codes in Code list 7 of Annex II to Regulation (EC) No 684/2009.n..2
hACO_Complementary InformationC
  • ‘R’ if <MEANS OF TRANSPORT.Transport Mode Code> is ‘Other’

  • Does not apply otherwise

(see box 3.3 g)

an..999
iACO_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
jRegistrationRan..35
kCountry 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 REPORTR
aDate of EventRdate
bPlace of EventRan..350
cPlace 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
dExcise Officer IdentificationOan..35
eSubmitting PersonRan..35
fSubmitting Person CodeR (see Code list 10 in Annex II)n..2
gSubmitting Person ComplementC
  • ‘R’ if <Submitting Person Code> is ‘Other’

  • ‘O’ otherwise

(see Submitting Person Code in box 4f)

an..350
hSubmitting 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
iChanged Transport ArrangementO

The possible values are:

1

=

Consignor

2

=

Consignee

3

=

Owner of goods

4

=

Other

n1
jCommentsOan..350
kComments_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 EVENTO9x
aIssuing AuthorityOan..35
bIssuing 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
cEvidence Type CodeR (see Code list 6 in Annex II)n..2
dEvidence Type ComplementC
  • ‘R’ <Evidence Type Code> is ‘Other’

  • Does not apply otherwise

(see Evidence Type Code in box 5c)

an..350
eEvidence 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
fReference of EvidenceRan..350
gReference 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
hImage of EvidenceO
6 TRADER New Transport ArrangerC
  • Does not apply if <Changed Transport Arrangement> is ‘1’, ‘2’, or is not used

  • ‘R’ otherwise

(see Changed Transport Arrangement in box 4i)

aVAT NumberOan..14
bTrader NameRan..182
cStreet NameRan..65
dStreet NumberOan..11
ePostcodeRan..10
fCityRan..50
gNAD_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 TransporterO
aVAT NumberOan..14
bTrader NameRan..182
cStreet NameRan..65
dStreet NumberOan..11
ePostcodeRan..10
fCityRan..50
gNAD_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 DETAILSO99x
aTransport Unit CodeR (see Code list 7 in Annex II to Regulation (EC) No 684/2009)n..2
bIdentity 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
cIdentity of Commercial SealOan..35
dSeal InformationOan..350
eSeal 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
fComplementary InformationOan..350
gComplementary 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 BodyC
  • ‘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
aEvent Type CodeR (see Code list 14 in Annex II)n..2
bAssociated InformationC
  • ‘R’ if <Event Type Code> is ‘0’

  • ‘O’ otherwise

(see Event Type Code in box 9a)

an..350
cAssociated 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
dBody 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
eDescription of the GoodsC
  • ‘O’ if the <OTHER ACCOMPANYING DOCUMENT> data group is present

  • Does not apply otherwise

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

  • Does not apply otherwise

an..35
hIndicator 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 ATTRIBUTESR
aDate and Time of Validation of Alert or RejectionC
  • R if corresponding field is validated

  • Does not apply otherwise

dateTime
2 EXCISE MOVEMENT e-ADR
aARCR

Provide the ARC of the e-AD.

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

an21
bSequence NumberRThe value of the data element must be greater than zero.n..2
3 TRADER ConsigneeC‘R’, except for message type ‘2 — Submission for export with local clearance’ or for Destination Type Code 8
aTrader 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)

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)
bEORI 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
cTrader NameRan..182
dStreet NameRan..65
eStreet NumberOan..11
fPostcodeRan..10
gCityRan..50
hNAD_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 DESTINATIONR
aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
5 ALERTR
aDate of AlertRdate
be-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 CodeC
  • ‘R’ if <e-AD Rejected flag> is True

  • ‘O’ if otherwise

9x
aAlert or Rejection of E-AD Reason CodeR (see Code list 5 in Annex II)n..2
bComplementary 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
cComplementary 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 ATTRIBUTER
aARCR

Provide the ARC of the e-AD.

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

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

  • ‘O’ otherwise

an..999
eManual 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 DOCUMENTSO 9x
aShort Description of Supporting DocumentC
  • ‘R’ if <Supporting Document Type> is ‘Other’

  • Does not apply otherwise

an..999
bShort 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
cReference 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
dReference 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
eImage 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)

fSupporting 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 BodyO 999X
aBody 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
bIndicator of Shortage or ExcessO

The possible values are:

S

=

Shortage

E

=

Excess

a1
cObserved 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
dExcise Product CodeO (see Code list 11 in Annex II to Regulation (EC) No 684/2009)an4
eRefused QuantityOThe value of this data element must be greater than zero.n..15,3
fComplementary InformationOan..350
gComplementary 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 ATTRIBUTER
aARCR

Provide the ARC of the e-AD.

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

an21
bSequence NumberR Provide the sequence number of the e-AD.n..2
cDate of Arrival of Excise ProductsOThe date at which the movement ends in accordance with Article 20(2) of Directive 2008/118/EC.date
dGlobal 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
eComplementary InformationOan..350
fComplementary 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
gManual Closure Request Reason CodeR (see code list 16 in Annex II)n1
hManual Closure Reason ComplementC
  • ‘R’ if <Manual Closure Request Reason Code> is ‘Other’

  • ‘O’ otherwise

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

  • Does not apply otherwise

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

  • ‘O’ otherwise

an..999
mManual 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 DOCUMENTSO 9x
aShort Description of Supporting DocumentC
  • ‘R’ if <Supporting Document Type> is ‘Other’

  • Does not apply otherwise

an..999
bShort 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
cReference 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
dReference 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
eImage 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)

fSupporting 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 BodyO 999X
aBody 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
bIndicator of Shortage or ExcessO

The possible values are:

S

=

Shortage

E

=

Excess

a1
cObserved 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
dExcise Product CodeO (see Code list 11 in Annex II to Regulation (EC) No 684/2009)an4
eRefused QuantityOThe value of this data element must be greater than zero.n..15,3
fComplementary InformationOan..350
gComplementary 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 IIU.K.

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

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

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)

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)

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
(2)

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).

(3)

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).

Back to top

Options/Help

Print Options

Close

Legislation is available in different versions:

Latest Available (revised):The latest available updated version of the legislation incorporating changes made by subsequent legislation and applied by our editorial team. Changes we have not yet applied to the text, can be found in the ‘Changes to Legislation’ area.

Original (As adopted by EU): The original version of the legislation as it stood when it was first adopted in the EU. No changes have been applied to the text.

Close

See additional information alongside the content

Geographical Extent: Indicates the geographical area that this provision applies to. For further information see ‘Frequently Asked Questions’.

Show Timeline of Changes: See how this legislation has or could change over time. Turning this feature on will show extra navigation options to go to these specific points in time. Return to the latest available version by using the controls above in the What Version box.

Close

Opening Options

Different options to open legislation in order to view more content on screen at once

Close

More Resources

Access essential accompanying documents and information for this legislation item from this tab. Dependent on the legislation item being viewed this may include:

  • the original print PDF of the as adopted version that was used for the EU Official Journal
  • lists of changes made by and/or affecting this legislation item
  • all formats of all associated documents
  • correction slips
  • links to related legislation and further information resources
Close

Timeline of Changes

This timeline shows the different versions taken from EUR-Lex before exit day and during the implementation period as well as any subsequent versions created after the implementation period as a result of changes made by UK legislation.

The dates for the EU versions are taken from the document dates on EUR-Lex and may not always coincide with when the changes came into force for the document.

For any versions created after the implementation period as a result of changes made by UK legislation the date will coincide with the earliest date on which the change (e.g an insertion, a repeal or a substitution) that was applied came into force. For further information see our guide to revised legislation on Understanding Legislation.

Close

More Resources

Use this menu to access essential accompanying documents and information for this legislation item. Dependent on the legislation item being viewed this may include:

  • the original print PDF of the as adopted version that was used for the print copy
  • correction slips

Click 'View More' or select 'More Resources' tab for additional information including:

  • lists of changes made by and/or affecting this legislation item
  • confers power and blanket amendment details
  • all formats of all associated documents
  • links to related legislation and further information resources