Search Legislation

Commission Implementing Regulation (EU) 2018/505Show full title

Commission Implementing Regulation (EU) 2018/505 of 7 March 2018 amending Implementing Regulation (EU) 2016/323 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

 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) 2018/505

 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) 2018/505

of 7 March 2018

amending Implementing Regulation (EU) 2016/323 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

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) In accordance with Commission Implementing Regulation (EU) 2016/323(2), under certain conditions the competent authorities of a Member State may refuse to provide information regarding goods under excise duty suspension which has been requested by another competent authority on the grounds of legally justified reasons.

(2) A competent authority which has forwarded information necessary to ensure the correct application of the legislation on excise duties to another authority, may request that the other competent authority provide feedback on the follow-up action it has taken on the basis of the information.

(3) Currently those refusals are to be forwarded and feedback is to be requested and provided using the CCN secure mail system.

(4) In order to accelerate and to improve the exchange of information between the Member States, all information should be stored in a central place. Accordingly, the competent authorities should use the computerised system to forward refusals and to request and provide feedback instead of using the CCN secure mail system.

(5) For the purposes of requests for assistance competent authorities should be able to link multiple messages that relate to the same movement of goods or the same trader, where the messages are exchanged in separate requests. For this purpose a new data item ‘National Case Reference Identifier’ should be introduced in the documents for requests for assistance and movement verification requests messages.

(6) In order to improve the integrity of the information contained in numeric data items, some data elements should be prevented from being filled in by stakeholders with a zero value. For this purpose the Tables 2, 3, 7, 10, 11 and 12 in Annex I to Implementing Regulation (EU) 2016/323 should be amended.

(7) The values in several code lists in Annex II to Implementing Regulation (EU) 2016/323 should be updated in order to link excise and customs procedures and to improve the quality of information provided by economic operators.

(8) In order to enable economic operators to provide extensive and accurate information while leaving enough space for the translation of the information, the size of the free text fields in administrative cooperation messages should be increased. For this purpose the Tables 7, 9, 10, 11 and 12 in Annex I to Implementing Regulation (EU) 2016/323 should be amended.

(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 of the European Parliament and of the Council(3) and to allow the Commission and the Member States adequate time to prepare for the changes resulting from this Regulation, it should apply from 15 February 2018.

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

Article 2 is replaced by the following:

Article 2Definition

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

(2)

in Article 8, the first paragraph is replaced by the following:

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

(3)

Article 16 is replaced by the following:

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

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

(4)

Annex I is amended as set out in Annex I to this Regulation;

(5)

Annex II is amended as set out in 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 15 February 2018.

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

Done at Brussels, 7 March 2018.

For the Commission

The President

Jean-Claude Juncker

ANNEX IU.K.

In Annex I to Regulation (EU) 2016/323, Tables 1 to 14 are replaced by the following:

Table 1

(as referred to in Article 4(1))

Movement Download Request

ABCDEFG
1 ATTRIBUTESR
aRequest Correlation IdentifierRThe value of <Request Correlation Identifier> is unique per Member State.an..44
2 EXCISE MOVEMENT e-ADR
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
cNational Movement Information Requested flagRThe format of Boolean is digital: ‘0’ or ‘1’ (‘0’ = No or False; ‘1’ = Yes or True)n1
dStatusR

The possible values are:

X01

=

Accepted

X02

=

Cancelled

X03

=

Delivered

X04

=

Diverted

X05

=

Rejected

X06

=

Replaced

X07

=

e-AD Manually closed

X08

=

Refused

X09

=

None

X10

=

Partially Refused

X11

=

Exporting

X12

=

Accepted for Export

X13

=

Stopped

an3
eLast Received Message TypeR

The possible values are:

IE801

=

E-AD

IE803

=

NOTIFICATION OF DIVERTED E-AD

IE807

=

INTERRUPTION OF MOVEMENT

IE810

=

CANCELLATION OF AN E-AD

IE813

=

CHANGE OF DESTINATION

IE818

=

ACCEPTED OR (PARTIALLY) REFUSED REPORT OF RECEIPT/EXPORT

IE819

=

ALERT OR REJECTION OF AN E-AD

IE829

=

NOTIFICATION OF ACCEPTED EXPORT

IE839

=

REJECTION OF E-AD FOR EXPORT

IE905

=

STATUS RESPONSE

None

=

NONE

Note: The IE905 should be included only when the e-AD is manually closed.

an..5
fStatus Request Message TypeO

The possible values are:

1

=

Status Synchronisation Request

2

=

Movement History Request

n1

Table 2

(as referred to in the first subparagraph of Article 4(2))

Movement Download Answer

ABCDEFG
1 ATTRIBUTESR
aRequest Correlation IdentifierRThe value of <Request Correlation Identifier> is unique per Member State.an..44
2 EXCISE MOVEMENT e-ADR
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
cStatusR

The possible values of <Status> are:

X01

=

Accepted

X02

=

Cancelled

X03

=

Delivered

X04

=

Diverted

X05

=

Rejected

X06

=

Replaced

X07

=

e-AD Manually closed

X08

=

Refused

X09

=

None

X10

=

Partially Refused

X11

=

Exporting

X12

=

Accepted for Export

X13

=

Stopped

an3
dLast Received Message TypeR

The possible values are:

IE801

=

E-AD

IE803

=

NOTIFICATION OF DIVERTED E-AD

IE807

=

INTERRUPTION OF MOVEMENT

IE810

=

CANCELLATION OF AN E-AD

IE813

=

CHANGE OF DESTINATION

IE818

=

ACCEPTED OR (PARTIALLY) REFUSED REPORT OF RECEIPT/EXPORT

IE819

=

ALERT OR REJECTION OF AN E-AD

IE829

=

NOTIFICATION OF ACCEPTED EXPORT

IE839

=

REJECTION OF E-AD FOR EXPORT

IE905

=

STATUS RESPONSE

None

=

NONE

Note: The IE905 should be included only when the e-AD is manually closed.

an..5

Table 3

(as referred to in the second subparagraph of Article 4(2))

History of a movement

ABCDEFG
1 ATTRIBUTESR
aRequest Correlation IdentifierRThe value of <Request Correlation Identifier> is unique per Member State.an..44
2 All validated e-ADsRThe set of all draft electronic administrative documents and electronic administrative documents relating to the movement, the structure of which is set out in Table 1 of Annex I to Regulation (EC) No 684/200999x
3 All Reports of Receipt/ExportOThe set of all Report of receipt/Report of export messages relating to the movement, the structure of which is set out in Table 6 of Annex I to Regulation (EC) No 684/200999x
4 Last Notification of Diverted e-ADOThe content of the last Notification of change of destination/Notification of splitting message relating to the movement, the structure of which is set out in Table 4 of Annex I to Regulation (EC) No 684/20091x
5 All Control ReportsOThe set of all Control Report messages relating to the movement, the structure of which is set out in Table 1199x
6 All Event ReportsOThe set of all Event Report messages relating to the movement, the structure of which is set out in Table 1299x
7 All explanations of delay for deliveryOThe set of all Explanation on delay for delivery messages relating to the movement99x
7.1 ATTRIBUTESR
aMessage RoleR

The possible values are:

1

=

Explanation on delay for sending the report of receipt/export

2

=

Explanation on delay for giving destination

n1
bDate and Time of Validation of Explanation on DelayC
  • ‘R’ after successful validation

  • Does not apply otherwise

dateTime
cSubmitter TypeR

The possible values are:

1

=

Consignor

2

=

Consignee

n1
dSubmitter Identification R an13 Rule072R

The <Submitter Identification> is a valid trader excise number.

(see Code list 1 in Annex II to Regulation (EU) No 612/2013)

an13
eExplanation CodeR (see Code list 7 in Annex II)n..2
fComplementary InformationC
  • ‘R’ if <Explanation Code> is ‘Other’

  • ‘O’ Otherwise

(see Explanation Code in box 7.1e)

an..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 groupa2
7.2 EXCISE MOVEMENT e-ADR
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
8 All Notifications of ExportOThe set of all Notification of accepted export messages relating to the movement99x
8.1 ATTRIBUTESR
aDate and Time of IssuanceRdateTime
8.2 EXCISE MOVEMENT e-ADR99x
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
8.3 TRADER ConsigneeC

Does not apply if <Message Type> of all concerned e-ADs is ‘Submission for export (local clearance)’

  • ‘R’ otherwise

aTrader IdentificationC
  • ‘R’ if <Destination Type Code> is:

    • “Destination - Tax warehouse”

    • “Destination - Registered consignee”

    • “Destination - Temporary registered consignee”

    • “Destination - Direct delivery”

  • ‘O’ if <Destination Type Code> is ‘Destination – Export’

  • Does not apply otherwise

The possible values of <Trader Identification> are described in the following table:

a

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

b

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

c

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

d

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

e

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

f

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

Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER Place of Delivery.Trader Identification
1 - Destination - Tax warehouse
Excise numberaTax Warehouse Reference (Excise Number)e
2 - Destination - Registered consignee
Excise numberbAny identificationf
3 - Destination - Temporary registered consignee
Temporary authorisation referencedAny identificationf
4 - Destination - Direct delivery
Excise numberc(Does not apply)
5 - Destination - Exempted consignee
(Does not apply)Any identificationf
6 - Destination – Export
VAT number (optional)(The data group <TRADER Place of Delivery> does not exist)

(see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable)

an..16
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_LNGRProvide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data groupa2
8.4 OFFICE Place of ExportO
aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
8.5 EXPORT ACCEPTANCER
aSender Customs Office Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
bSender Customs Officer IdentificationOan..35
cDate of AcceptanceRdate
dMRN ExportR

A valid MRN or SAD Number confirmed against Customs data, according to the Customs case.

MRN

=

Movement Reference Number

SAD

=

Single Administrative Document

an..21
9 All Notifications of refusal by CustomsOThe set of all Customs rejection of e-AD messages relating to the movement99x
9.1 ATTRIBUTESR
aDate and Time of IssuanceRdateTime
9.2 The concerned draft e-ADC

In the case of rejection at import one concerned draft e-AD must be given or in the case of rejection at export one or several concerned validated e-ADs must be given.

(see All concerned validated e-ADs in box 9.3)

aLocal Reference NumberRan..22
9.3 All concerned validated e-ADsC

In the case of rejection at import one concerned draft e-AD must be given or in the case of rejection at export one or several concerned validated e-ADs must be given.

(see The concerned draft e-AD in box 9.2)

99x
aARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bSequence NumberRn..2
9.4 REJECTIONR
aRejection Date and TimeRdateTime
bRejection Reason CodeR

The possible values are:

1

=

Import data not found

2

=

The contents of the e-AD does not match with import data

3

=

Export data not found

4

=

The content of the e-AD does not match with export data

5

=

Goods are rejected at export procedure

n1
9.5 EXPORT CROSS CHECKING DIAGNOSESC

‘R’ if <Rejection Reason Code> is “The content of the e-AD does not match with export data”

  • Does not apply otherwise

(see Rejection Reason Code in box 9.4b)

aLRN ExportC

At least one of the following attributes must be present:

  • <MRN Export>

  • <LRN Export>

(see MRN Export in box 9.5b)

an..22
bMRN ExportC

At least one of the following attributes must be present:

  • <MRN Export>

  • <LRN Export>

(see LRN Export in box 9.5a)

A valid MRN or SAD Number confirmed against Customs data, according to the Customs case.

MRN

=

Movement Reference Number

SAD

=

Single Administrative Document

an..21
9.6 DIAGNOSISR999x
aARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bBody Record Unique ReferenceRThe value of the Data Item must be greater than zero.n..3
cDiagnosis CodeR

The possible values are:

1

=

Unknown ARC

2

=

Body Record Unique Reference does not exist in the e-AD

3

=

No corresponding GOODS ITEM in the export declaration

4

=

Weight/mass do not match

5

=

The destination type code of the e-AD is not export

6

=

CN codes do not match

n1
9.7 TRADER ConsigneeC
  • ‘R’ if <Message Type> of all concerned e-ADs is not “Submission for export (local clearance)”

  • Does not apply otherwise

The possible Message Types are:

1

=

Standard submission (to be used in all cases except where submission concerns export with local clearance)

2

=

Submission for export with local clearance (Application of Article 283 of Commission Regulation (EEC) No 2454/93 (1))

The message type must not occur in the e-AD to which an ARC has been assigned, nor in the paper document referred to in Article 8(1) of Regulation (EC) No 684/2009

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:

a

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

b

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

c

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

d

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

e

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

f

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

Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER Place of Delivery.Trader Identification
1 - Destination - Tax warehouse
Excise numberaTax Warehouse Reference (Excise Number)e
2 - Destination - Registered consignee
Excise numberbAny identificationf
3 - Destination - Temporary registered consignee
Temporary authorisation referencedAny identificationf
4 - Destination - Direct delivery
Excise numberc(Does not apply)
5 - Destination - Exempted consignee
(Does not apply)Any identificationf
6 - Destination – Export
VAT number (optional)(The data group <TRADER Place of Delivery> does not exist)

(see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable)

an..16
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_LNGRProvide the language code presented in Annex II to Regulation (EC) No 684/2009, Code list 1 to define the language used in this data groupa2
9.8 OFFICE Place of ExportO
aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
10 The Possible Interruption of MovementOThe content of a possible Interruption of movement message relating to the movement, the structure of which is set out in Table 131x
11 The Possible Cancellation of e-ADOThe content of a possible Cancellation message relating to the movement, the structure of which is set out in Table 2 of Annex I to Regulation (EC) No 684/20091x
12 All Changes of DestinationOThe set of all Change of destination messages relating to the movement, the structure of which is set out in Table 3 of Annex I to Regulation (EC) No 684/200999x
13 All Alerts or Rejections of an e-ADOThe set of all Alert or Rejection of an e-AD messages relating to the movement, the structure of which is set out in Table 1499x
13.1 ATTRIBUTESR
aDate and Time of Validation of Alert or RejectionC
  • ‘R’ after successful validation

  • Does not apply otherwise

dateTime
13.2 EXCISE MOVEMENT e-ADR
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
13.3 TRADER ConsigneeR
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:

a

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

b

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

c

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

d

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

e

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

f

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

Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER Place of Delivery.Trader Identification
1 - Destination - Tax warehouse
Excise numberaTax Warehouse Reference (Excise Number)e
2 - Destination - Registered consignee
Excise numberbAny identificationf
3 - Destination - Temporary registered consignee
Temporary authorisation referencedAny identificationf
4 - Destination - Direct delivery
Excise numberc(Does not apply)
5 - Destination - Exempted consignee
(Does not apply)Any identificationf
6 - Destination – Export
VAT number (optional)(The data group <TRADER Place of Delivery> does not exist)

(see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable)

an..16
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 groupa2
13.4 OFFICE of DestinationR
aOffice Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
13.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
13.6 ALERT OR REJECTION OF E-AD REASON CodeC
  • ‘R’ if <E-AD Rejected flag> is True

  • ‘O’ if <E-AD Rejected flag> is False

(see E-AD Rejected Flag in box 13.5b)

9x
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 13.6a)

an..350
cComplementary 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 groupa2
14 All Explanations on reason for shortageO99x
14.1 ATTRIBUTESR
aSubmitter TypeR

The possible values are:

1

=

Consignor

2

=

Consignee

n1
bDate and Time of Validation of Explanation on ShortageC
  • ‘R’ after successful validation

  • Does not apply otherwise

dateTime
14.2 EXCISE MOVEMENT e-ADR
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
14.3 TRADER ConsignorC
  • ‘R’ if <Submitter Type> is “Consignor”

  • Does not apply otherwise

(see Submitter Type in box 14.1a)

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”

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 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 groupa2
14.4 TRADER ConsigneeC
  • ‘R’ if <Submitter Type> is not “Consignor”

  • Does not apply otherwise

(see Submitter Type in box 14.1a)

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:

a

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

b

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

c

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

d

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

e

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

f

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

Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER Place of Delivery.Trader Identification
1 - Destination - Tax warehouse
Excise numberaTax Warehouse Reference (Excise Number)e
2 - Destination - Registered consignee
Excise numberbAny identificationf
3 - Destination - Temporary registered consignee
Temporary authorisation referencedAny identificationf
4 - Destination - Direct delivery
Excise numberc(Does not apply)
5 - Destination - Exempted consignee
(Does not apply)Any identificationf
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)

(see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable)

an..16
bEORI Number
  • ‘O’ if <Destination Type Code> is ‘Destination – Export’

  • Does not apply otherwise

Provide the EORI number of the person responsible for lodging the export declaration as set out in Article 21(5) of Directive 2008/118/ECan..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 groupa2
14.5 ANALYSISCAt least one of the <ANALYSIS> or <ANALYSIS Body> data groups must be present
aDate of AnalysisRdate
bGlobal ExplanationRan..350
cGlobal Explanation_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 groupa2
14.6 ANALYSIS BodyCAt least one of the <ANALYSIS> or <ANALYSIS Body> data groups must be present999x
aBody Record Unique ReferenceR

The value of the Data Item must be greater than zero.

The <Body Record Unique Reference> must be unique within the message and must refer to a <Body Record Unique Reference> of the e-AD Body of the associated e-AD for which shortages or excesses have been declared.

n..3
bExcise Product CodeR (see Code list 11 in Annex II to Regulation (EC) No 684/2009)an4
cExplanationOan..350
dExplanation_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 groupa2
eActual QuantityOThe value of the Data Item must be greater than zero.n..15,3
15 All reminder messages for Excise movementO99x
15.1 ATTRIBUTESR
aMessage TypeR

The possible values are:

1

=

Reminder message at expiry of time to change destination (or split)

2

=

Reminder message at expiry of time to send the report of receipt/export

3

=

Reminder message at expiry of time to give destination information (Article 22 of Directive 2008/118/EC)

n1
bDate and Time of Issuance of ReminderRdateTime
cLimit date and TimeRdateTime
dReminder InformationOan..350
eReminder 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 groupa2
15.2 EXCISE MOVEMENT e-ADR
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

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

=

Request for EOL

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 Statean..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 ‘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
aValueRan..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 zeron4
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

=

Administrative cooperation actions

29

=

Administrative cooperation request reasons

30

=

(reserved)

31

=

(reserved)

32

=

(reserved)

33

=

(reserved)

34

=

Administrative cooperation action not possible reasons

35

=

Common request rejection reasons

36

=

(reserved)

37

=

Movement verification request reasons

38

=

Movement verification actions

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 zeron..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 ConsigneeR
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:

a

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

b

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

c

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

d

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

e

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

f

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

Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER Place of Delivery.Trader Identification
1 - Destination - Tax warehouse
Excise numberaTax Warehouse Reference (Excise Number)e
2 - Destination - Registered consignee
Excise numberbAny identificationf
3 - Destination - Temporary registered consignee
Temporary authorisation referencedAny identificationf
4 - Destination - Direct delivery
Excise numberc(Does not apply)
5 - Destination - Exempted consignee
(Does not apply)Any identificationf
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)

(see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable)

an..16
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/ECan..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:

a

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

b

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

c

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

d

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

e

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

f

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

Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER Place of Delivery.Trader Identification
1 - Destination - Tax warehouse
Excise numberaTax Warehouse Reference (Excise Number)e
2 - Destination - Registered consignee
Excise numberbAny identificationf
3 - Destination - Temporary registered consignee
Temporary authorisation referencedAny identificationf
4 - Destination - Direct delivery
Excise numberc(Does not apply)
5 - Destination - Exempted consignee
(Does not apply)Any identificationf
6 - Destination – Export
VAT number (optional)(The data group <TRADER Place of Delivery> does not exist)

(see Code list 1 in Annex II to Regulation (EU) No 612/2013, if applicable)

an..16
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 - CustomsC

The optionality of the data groups <TRADER Place of Delivery> and <OFFICE Place of Delivery – Customs> are described in the table below, according to the <Destination Type Code>:

Destination Type Code<TRADER Place of Delivery><OFFICE Place of Delivery – Customs>
1 - Destination - Tax warehouse
‘R’Does not apply
2 - Destination - Registered consignee
‘O’Does not apply
3 - Destination - Temporary registered consignee
‘O’Does not apply
4 - Destination - Direct delivery
‘R’Does not apply
5 - Destination - Exempted consignee
‘O’Does not apply
6 - Destination – Export
Does not apply‘R’
8 - Unknown destination (consignee unknown)
Does not 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 6

(as referred to in Article 5(3))

Refusal of Common Request

ABCDEFG
1 Common Request MessageRThe context of the Common Request message relating to the movement, the structure of which is set out in Table 4
2 RejectionR99x
aRejection Date and TimeRdateTime
bRejection Reason CodeR

The possible values are:

0

=

Other

2

=

No e-AD(s) retrieved matching selection criteria

3

=

Reference data not available

4

=

Excise Office List not available

5

=

SEED data not available

7

=

Unknown requested data

8

=

Increment number out of range

26

=

Duplicate detected

112

=

Incorrect (code) value

115

=

Not supported in this position

n..3

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/2009a2
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/2009a2
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 groupa2
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 groupa2
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 groupa2
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/2009a2
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 groupa2
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 groupa2
cReference of Supporting DocumentC

At least one, among these three fields:

  • <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 groupa2
eImage of DocumentC

At least one, among these three fields:

  • <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:

  • <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..2
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 groupa2
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 groupa2
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 8

(as referred to in Article 7(2) and Article 8)

Answer message

ABCDEFG
1 ATTRIBUTESR
aMessage TypeR

The possible values are:

1

=

Administrative Cooperation answer message

2

=

History answer message

n1
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/2009a2
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/2009a2
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

IF <Follow Up Correlation ID> matches with <Follow Up Correlation ID> in a request message AND <National Case Reference Identifier> is present in the request message

THEN

<National Case Reference Identifier> must be equal to the value of <National Case Reference Identifier> in the request message.

an..99
3 ANSWERR
aDeadline for ResultsC

For 3 a and b:

  • ‘R’ if < Refusal Reason Code> is provided

  • Does not apply otherwise

(see Refusal Reason Code in box 3c)

dateTime
bDelayed Result Reason CodeC (see Code list 3 in Annex II)n..2
cRefusal Reason CodeO (see Code list 4 in Annex II)n..2
dRefusal Reason ComplementC
  • ‘R’ if < Refusal Reason Code> is ‘Other’

  • Does not apply otherwise

(see Refusal Reason Code in box 3c)

an..999
eRefusal 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 groupa2

Table 9

(as referred to in Article 7(1))

Reminder Message for Administrative Cooperation

ABCDEFG
1 ATTRIBUTESR
aMessage TypeR

The possible values are:

1

=

Administrative cooperation results reminder message

2

=

History results reminder message

n1
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/2009a2
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/2009a2
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

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/2009a2
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/2009a2
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 groupa2
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 groupa2
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 groupa2
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 groupa2
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 groupa2
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 groupa2
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 groupa2
cReference of Supporting DocumentC

At least one, among these three fields:

  • <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 groupa2
eImage of DocumentC

At least one, among these three fields:

  • <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:

  • <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..2

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/2009a2
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 groupa2
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

1

=

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 groupn2
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/2009a2
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/2009a2
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 numberan16
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 groupa2
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 at least one instance of 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 at least one instance of 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 at least one instance of 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
5 MEANS OF TRANSPORTC
  • ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in at least one instance of 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 Code’‘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/2009n..2
hACO_Complementary InformationC
  • ‘R’ if <MEANS OF TRANSPORT. Transport Mode Code> is “Other”

  • Does not apply otherwise

(see box5g)

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 groupa2
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
6 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 groupa2
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 groupa2
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 groupa2
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 groupa2
6.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 6.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 groupa2
6.2 EVIDENCE OF EVENTC
  • ‘R’ if <Reason for Control> is ‘2’

  • Does not apply otherwise

(see Reason for Control in box 6e)

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 groupa2
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 3.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 groupa2
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 groupa2
hImage of EvidenceO
6.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 6.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 groupa2
6.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 6.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 groupa2
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 groupa2
6.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 6.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 groupa2
6.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 3.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 groupa2

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 One 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

1

=

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/2009a2
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/2009a2
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 numberan16
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 groupa2
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 at least one instance of the <OTHER ACCOMPANYING DOCUMENT> data group

  • Does not apply otherwise (see box 4 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 at least one instance of 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 at least one instance of 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 WeightOThe 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 WeightOThe 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 MEANS OF TRANSPORTC
  • ‘R’ if <OTHER ACCOMPANYING DOCUMENT.Image of Other Accompanying Document> is not present in at least one instance of 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 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/2009n..2
hACO_Complementary InformationC
  • ‘R’ if <MEANS OF TRANSPORT.Transport Mode Code> is “Other”

  • Does not apply otherwise

(see box 4g)

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 groupa2
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
5 EVENT REPORTC
  • ‘R’ if <Message Type> is ‘1’ or ‘3’

  • ‘O’ otherwise

(see Message Type in box 1a)

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 groupa2
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 5f)

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 groupa2
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 groupa2
6 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 groupa2
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 6c)

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 group2
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 groupa2
hImage of EvidenceO
7 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 5i)

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 groupa2
8 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 groupa2
9 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 7a)

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 groupa2
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 groupa2
10 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 7, TRADER New Transport in 8, and TRANSPORT DETAILS in 9)

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 10a)

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 groupa2
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 10 e, f and g:

  • ‘R’ if <Body Record Unique Reference> is given

  • Does not apply otherwise

(see Body Record Unique Reference in box 8d)

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 13

(as referred to in Article 12)

Interruption of Movement

ABCDEFG
1 ATTRIBUTESR
aARCR (see Code list 2 in Annex II to Regulation (EC) No 684/2009)an21
bDate and Time of IssuanceRdateTime
cReason for Interruption CodeR (see Code list 13 in Annex II)n..2
dExcise Office Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
eExcise Officer IdentificationOan..35
fComplementary InformationC
  • ‘R’ if <Reason for Interruption Code> is ‘Other’

  • ‘O’ otherwise

(see Reason for Interruption Code in box 1c)

an..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 groupa2
2 CONTROL REPORT ReferenceO9x
aControl Report ReferenceR

(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’ message) having the same <Control Report Reference> and <ARC> with that of the submitted message.

(see ARC in box 1a)

an16
3 EVENT REPORT ReferenceO9x
aEvent Report NumberR

(see Code list 2 in Annex II)

An ‘Event Report’ message exists in the system (including the case that it is encapsulated in a received ‘Movement History’ message) having the same <Event Report Number> and <ARC> with that of the submitted message

(see ARC in box 1a)

an16

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 zeron..2
3 TRADER ConsigneeR
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:

a

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

b

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

c

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

d

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

e

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

f

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

Destination Type CodeTRADER CONSIGNEE. Trader IdentificationTRADER Place of Delivery. Trader Identification
1 - Destination - Tax warehouse
Excise numberaTax Warehouse Reference (Excise Number)e
2 - Destination - Registered consignee
Excise numberbAny identificationf
3 - Destination - Temporary registered consignee
Temporary authorisation referencedAny identificationf
4 - Destination - Direct delivery
Excise numberc(Does not apply)
5 - Destination - Exempted consignee
(Does not apply)Any identificationf
6 - Destination – Export
VAT number (optional)(The data group <TRADER Place of Delivery> does not exist)

(see Code list 1 and Code list 2 in Annex II to Regulation (EU) No 612/2013, if applicable)

an..16
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/ECan..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 groupa2
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 groupa2

ANNEX IIU.K.

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

(1)

code list 2 is replaced by the following:

Code list 2: Event Report Number/Control Report Reference

FieldContentField typeExamples
1Identifier of the MS where the report is validatedAlphabetic 2ES
2Nationally assigned, unique codeAlphanumeric 132005YTE17UIC2
3Check DigitNumeric 19

Field 1 is taken from the list of <MEMBER STATES> (see Code list 3 in Annex II to Regulation (EC) No 684/2009)

Field 2 must be filled with a unique identifier per report. The way this field is used is under MSAs' responsibility, but each report must have a unique number. It is possible, but not mandatory, that it contains the year when the report was initially submitted (as suggested in the example).

Field 3 gives the Check Digit for the whole identifier, which will help detect an error when keying this identifier.;

(2)

code list 4 is replaced by the following:

Code list 4: Refusal Reasons

CodeDescription
0Other
1The enquiry or information requested could not be authorised under the laws or administrative practices of the requested Member State for its own use (e.g. Confidential information)
2(reserved)
3Disclosure contrary to the public policy of the state — The provision of information would lead to the disclosure of a commercial, industrial or professional secret or of a commercial process, or where its disclosure would be contrary to public policy
4A judicial authority of the requested Member State has refused to allow the transfer of information under its control
5The request concerns information that is no longer available due to national rules of data retention (5 years or more minimum)
6The requesting authority has not exhausted the usual sources of information which it could have used in the circumstances
7The number and the nature of the requests for information made by the requesting authority within a specific period impose a disproportionate administrative burden on that requested authority
8The requesting Member State is unable, for legal reasons, to provide similar information
9The consignor has not exhausted all the means available to him to obtain proof that the movement of excise goods between Member States has ended
10No check performed
11Out of scope of 389/2012 (e.g. Naples II)
(3)

code list 6 is replaced by the following:

Code list 6: Evidence Types

CodeDescription
0Other
1Accident
2Goods destroyed
3Goods stolen
6Vehicle and goods stolen
7Transhipment of goods
(4)

code list 8 is replaced by the following:

Code list 8: Request Reasons

CodeDescription
0Other
1Report of Receipt/Export not returned to consignor
2Excesses or shortages stated at arrival of good
4Submission of an e-AD was rejected because the consignee record of SEED did not match — the request is to ask for more information
6Have goods/quantities specified on e-AD been entered in consignee's stock records?
7Check that goods have actually left EU (date on which export certified by customs)
8Placing of goods under a suspensive customs procedure (export warehouse, victualling warehouse, outward processing, etc.)
9Reimbursement of excise duty requested
10Spot checks
11Copy 3 not returned to Consignor
12Reverse of Copy 3 endorsed to show excesses or losses
13Certification of Receipt Incomplete
14Consignee's Excise Number not in SEED
15Particular Deleted/Overwritten without official Endorsement
16Request for Manual closure
17Export Status Unknown
18Request for Interruption of a movement
19Perform interview of authorised representative
20Fallback document
21Two e-ADs were created for the same consignment
22Clarification regarding type or quantity of goods
23Receipt of goods were rejected/refused
24Ongoing excise investigation
25Suspicions of irregularity
(5)

code list 9 is replaced by the following:

Code list 9: Request Actions

CodeDescription
0Other
2Administrative control
3Physical control
4Confirm entry in trader's records
5Confirm quantity received
6Confirm authorisation of trader
7Confirm the particulars in Box No(s)
11Confirm identity of the carrier and the number of the vehicle
12Confirm payment of duty
14Confirm quantity dispatched
15Confirm type of goods dispatched
16Confirm Authenticity of Excise official stamp
17Confirm Authenticity of Company's Stamp and Trader's signature
18Confirm Trader's Authorisation and SEED Data
19Manual closure
20Hearing of authorised representative (e.g. interview of company manager)
21Provide reason for shortage
22Confirm shortage/excess/differences
23Provide proof that the movement of excise goods has ended
24Confirm purpose of goods or next purchaser of goods
25Please see attached request
26Follow-up measure needs to be taken from the Consignor
27Correction required in Export declaration
28Confirm the content of the Export Declaration
29Inform if the movement has already been released by Customs
30Provide Export MRN
(6)

code list 11 is replaced by the following:

Code list 11: Administrative Cooperation Action Not Possible Reasons

CodeDescription
0Other
1Missing information
2Confidential information
3Missing time
4Deep investigation on economic operator ongoing, short-term answer not possible
5Trader could not be contacted
6Missing trader
(7)

a new code list 15 is added:

Code list 15: Type of Document

CodeDescription
0Other
1e-AD
2SAAD
3Invoice
4Delivery note
5CMR
6Bill of lading
7Way Bill
8Contract
9Trader's Application
10Official record
11Request
12Answer
13Fallback documents, Fallback Printout
14Photo
15Export Declaration
16Anticipated Export Record
17Exit Results
18SAD (Single Administrative Document)
(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