Search Legislation

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

Commission Implementing Regulation (EU) 2018/504 of 7 March 2018 amending Implementing Regulation (EU) No 612/2013 on the operation of the register of economic operators and tax warehouses, related statistics and reporting pursuant to Council Regulation (EU) No 389/2012 on administrative cooperation in the field of excise duties

 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/504

 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/504

of 7 March 2018

amending Implementing Regulation (EU) No 612/2013 on the operation of the register of economic operators and tax warehouses, related statistics and reporting pursuant to Council Regulation (EU) No 389/2012 on administrative cooperation in the field of excise duties

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 22 thereof,

Whereas:

(1) Annex I to Commission Implementing Regulation (EU) No 612/2013(2) lays down the structure and content of messages relating to the registration of economic operators and tax warehouses in the national registers and the Central Register. In order to improve the quality of data used in those messages Tables 1, 2 and 4 of Annex I to Implementing Regulation (EU) No 612/2013 should be amended.

(2) In accordance with Article 22 of Council Directive 2008/118/EC(3) in the case of movement of energy products under a duty suspension arrangement by sea or inland waterways, the competent authorities of the Member State of dispatch may authorise the consignor to omit the details of the consignee at the time of dispatch in the draft electronic administrative document referred to in Article 21(2) of that Directive. In accordance with Regulation (EU) No 612/2013 only an authorised warehouse keeper is allowed to omit the details of the consignee. Therefore it is also necessary to enable a registered consignor to leave empty the destination fields in the draft electronic administrative document when moving energy products under duty suspension arrangement by sea or inland waterways in order to align with Article 22 of Directive 2008/118/EC.

(3) The explanation in column F of Table 1 of Annex I to Implementing Regulation (EU) No 612/2013 should provide a clearer identification of the ‘Requesting Office’ data element in order to align with the definition in Annex II to Regulation (EC) No 684/2009.

(4) Implementing Regulation (EU) No 612/2013 should therefore be amended accordingly.

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

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

Annex I of Implementing Regulation (EU) No 612/2013 is amended as set out in the Annex 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

ANNEXU.K.

Annex I to Implementing Regulation (EU) No 612/2013 is amended as follows:

(1)

Tables 1 and 2 are replaced by the following:

Table 1

Common request

(referred to in Article 4(5), Article 7(2) and Article 8(2))

ABCDEFG
1 ATTRIBUTESR
aRequest TypeR

The possible values are:

2

=

Request for extraction of reference data

3

=

Request for retrieval of reference data

4

=

Request for extraction of economic operators

5

=

Request for retrieval of economic operators

6

=

Request for EOL

7

=

Request for retrieval of a list of e-ADs

8

=

Request for SEED statistics

n1
bRequest Message NameC
  • ‘R’ if <Request Type> is ‘2’ or ‘3’

  • 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’, ‘3’, ‘4’, ‘5’, ‘7’, or ‘8’

  • 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 ‘3’ or ‘5’

  • Does not apply otherwise

(see Request Type in box 1a)

date
fEnd DateCdate
gSingle DateC
  • ‘R’ if <Request Type> is ‘2’ or ‘4’

  • Does not apply otherwise

(see Request Type in box 1a)

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

  • 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 ‘8’

  • 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 ‘8’

  • Does not apply otherwise

(see Request Type in box 1a)

aYearRn4
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’ or ‘3’

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

Operations on the register of economic operators

(referred to in Article 3(3), Article 4(2) and (3) and Article 6(3))

ABCDEFG
1 ATTRIBUTESR
aMessage TypeR

The possible values are:

1

=

Update of economic operators (Notification of changes to CD/RD)

2

=

Dissemination of updates of economic operators

3

=

Retrieval of economic operators

4

=

Extraction of economic operators

n1
bRequest Correlation IdentifierC
  • ‘R’ if <Message Type> is ‘3’ or ‘4’

  • Does not apply otherwise

(see Message Type in box 1a)

The value of <Request Correlation Identifier> is unique per Member Statean..44
2 TRADER AUTHORISATIONO999999x
aTrader Excise NumberR

(See Code list 1 in Annex II)

The <Trader Excise Number> must be unique in the list of <TRADER AUTHORISATION>.

an13
bVAT NumberOan..14
cAuthorisation Start DateRdate
dAuthorisation End DateOdate
eOperator Type CodeR

The possible values are:

1

=

Authorised warehouse keeper

2

=

Registered consignee

3

=

Registered consignor

The value of the <Operator Type Code> data item cannot be changed after the creation of the TRADER AUTHORISATION

n1
fExcise Office Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
2.1 ACTIONR
aOperationR

The possible values are:

C

=

Create

U

=

Update

I

=

Invalidate

a1
bActivation DateC
  • ‘R’ if <Operation> is ‘C’ or ‘U’

  • ‘O’ otherwise

(see Operation in box 2.1a)

If <Activation Date> is not entered the Activation Date of the Invalidate operation is considered to be the date that the Invalidate operation is incorporated into the central register.date
cResponsible Data ManagerOan..35
2.2 NAME AND ADDRESSR99x
aNameRan..182
bNAD_LNGR (see Code list 1 in Annex II to Regulation (EC) No 684/2009)a2
2.2.1 ADDRESSR
aStreet NameRan..65
bStreet NumberOan..11
cPostcodeRan..10
dCityRan..50
eMember State CodeR (see Code list 3 in Annex II to Regulation (EC) No 684/2009)a2
2.3 OPERATOR ROLE CodeO9x
aOperator Role CodeR

The possible values are:

1

=

Allowed to practise direct delivery

2

=

Allowed to leave empty the destination fields according to Article 22 of Directive 2008/118/EC.

The couplings <Operator Type / Operator Role Code> are as follows:

OP/OR TYPE / OP/OR ROLEAUTH. WH KEEPERREG. CON/EEREG. CON/OR
Allowed to practise direct deliveryXX
Allowed to leave empty the destination fields according to Article 22 of Directive 2008/118/ECXX
n1
2.4 EXCISE PRODUCTS CATEGORY CodeCAt least one of the <EXCISE PRODUCTS CATEGORY code> or <EXCISE PRODUCT code> data groups must be present999x
aExcise Products Category CodeR

(see Code list 3 in Annex II)

The <Excise Products Category Code> must be unique in the list of <EXCISE PRODUCTS CATEGORY Code> inside the same <TRADER AUTHORISATION> or <TAX WAREHOUSE>

a1
2.5 EXCISE PRODUCT CodeCAt least one of the <EXCISE PRODUCTS CATEGORY code> or <EXCISE PRODUCT code> data groups must be present999x
aExcise Product CodeR

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

The <Excise Products Category Code> of the <Excise Product Code> must not exist inside the same <TRADER AUTHORISATION> or <TAX WAREHOUSE>

The <Excise Product Code> must be unique in the list of <EXCISE PRODUCT Code> inside the same <TRADER AUTHORISATION>, <TAX WAREHOUSE>, or <TEMPORARY AUTHORISATION>

an..4
2.6 (USING) TAX WAREHOUSEC
  • ‘R’ if <Operator Type Code> is ‘Authorised warehouse keeper’

  • Does not apply otherwise

(see Operator Type Code in box 2e)

99x
aTax Warehouse ReferenceR

(see Code list 1in Annex II)

The “Tax Warehouse Reference” shall be one of the <TAX WAREHOUSE. Tax Warehouse Reference> such that there exists at least one Active version having its Validity Interval intersecting the Validity Interval of the <TRADER AUTHORISATION>, after the Activation Date of the latter, by at least one day

The <Tax Warehouse Reference> must be unique in the list of <TAX WAREHOUSE>.

an13
3 TAX WAREHOUSEO999999x
aTax Warehouse ReferenceR

(see Code list 1 in Annex II)

The <Tax Warehouse Reference> must be unique in the list of <TAX WAREHOUSE>.

The “Tax Warehouse Reference” shall be the same as one of the <(USING) TAX WAREHOUSE. Tax Warehouse Reference> within one or more <TRADER AUTHORISATION> data groups of “Authorised Warehouse Keeper” type satisfying also Rule204

an13
bValidity Begin DateRdate
cValidity End DateOdate
dExcise Office Reference NumberR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
3.1 ACTIONR
aOperationR

The possible values are:

C

=

Create

U

=

Update

I

=

Invalidate

a1
bActivation DateC
  • ‘R’ if <Operation> is ‘C’ or ‘U’

  • ‘O’ otherwise

(see Operation in box 3.1a)

If <Activation Date> is not entered the Activation Date of the Invalidate operation is considered to be the date that the Invalidate operation is incorporated into the central register.date
cResponsible Data ManagerOan..35
3.2 NAME AND ADDRESSR99x
aNameRan..182
bNAD_LNGR (see Code list 1 in Annex II to Regulation (EC) No 684/2009)a2
3.2.1 ADDRESSR
aStreet NameRan..65
bStreet NumberOan..11
cPostcodeRan..10
dCityRan..50
eMember State CodeR (see Code list 3 in Annex II to Regulation (EC) No 684/2009)a2
3.4 EXCISE PRODUCTS CATEGORY CodeCAt least one of the <EXCISE PRODUCTS CATEGORY code> or <EXCISE PRODUCT code> data groups must be present999x
aExcise Products Category CodeR

(see Code list 3 in Annex II)

The <Excise Products Category Code> must be unique in the list of <EXCISE PRODUCTS CATEGORY Code> inside the same <TRADER AUTHORISATION> or <TAX WAREHOUSE>

an1
3.5 EXCISE PRODUCT CodeCAt least one of the <EXCISE PRODUCTS CATEGORY code> or <EXCISE PRODUCT code> data groups must be present999x
aExcise Product CodeR

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

The <Excise Products Category Code> of the <Excise Product Code> must not exist inside the same <TRADER AUTHORISATION> or <TAX WAREHOUSE>

The <Excise Product Code> must be unique in the list of <EXCISE PRODUCT Code> inside the same <TRADER AUTHORISATION>, <TAX WAREHOUSE>, or <TEMPORARY AUTHORISATION>

an..4
4 TEMPORARY AUTHORISATIONO999999x
aTemporary Authorisation ReferenceR (see Code list 2 in Annex II)an13
bOffice Reference Number of IssuanceR (see Code list 5 in Annex II to Regulation (EC) No 684/2009)an8
cDate of ExpiryRdate
dRe-usable Temporary Authorisation flagR

The possible values are:

0

=

No or False

1

=

Yes or True

n1
eVAT NumberOan..14
fAuthorisation Start DateRdate
gSmall Wine Producer flagO

The possible values are:

0

=

No or False

1

=

Yes or True

n1
4.1 ACTIONR
aOperationR

The possible values are:

C

=

Create

U

=

Update

I

=

Invalidate

a1
bActivation DateC
  • ‘R’ if <Operation> is ‘C’ or ‘U’

  • ‘O’ otherwise

(see Operation in box 4.1a)

If <Activation Date> is not entered the Activation Date of the Invalidate operation is considered to be the date that the Invalidate operation is incorporated into the central register.date
cResponsible Data ManagerOan..35
4.2 TRADER ConsignorR
aTrader Excise NumberC
  • ‘R’ if <Temporary Authorisation – Small Wine Producer flag> is not present or is False

  • ‘O’ otherwise

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”

an13
bTrader NameRan..182
cStreet NameRan..65
dStreet NumberOan..11
ePostcodeRan..10
fCityRan..50
gNAD_LNGR (see Code list 1 in Annex II to Regulation (EC) No 684/2009)a2
4.3 TEMPORARY AUTHORISATION DETAILSR999x
aExcise Product CodeR

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

The <Excise Product Code> must be unique in the list of <EXCISE PRODUCT Code> inside the same <TRADER AUTHORISATION>, <TAX WAREHOUSE>, or <TEMPORARY AUTHORISATION>

If <Temporary Authorisation – Small Wine Producer> is present and is True THEN the

<Excise Product Code> must be either:

  • “W200”; OR

  • “W300”

an..4
bQuantityRn..15,3
4.4 NAME AND ADDRESSR99x
aNameRan..182
bNAD_LNGR (see Annex II, Code list 1 of Regulation (EC) No 684/2009)a2
4.4.1 ADDRESSR
aStreet NameRan..65
bStreet NumberOan..11
cPostcodeRan..10
dCityRan..50
eMember State CodeR (see Code list 3 in Annex II to Regulation (EC) No 684/2009)a2
(2)

Table 4 is replaced by the following:

Table 4

SEED statistics

(referred to in Article 7(2))

ABCDEFG
1 ATTRIBUTESR
aRequest Correlation IdentifierRThe value of <Request Correlation Identifier> is unique per Member State.an..44
2 STA_PERIODR
aYearRn4
bSemesterC

For 2 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
3 STA_PER_MSO99x
aMember State CodeR (see Code list 3 in Annex II to Regulation (EC) No 684/2009)a2
bNumber of Active Economic OperatorsOn..15
cNumber of Inactive Economic OperatorsOn..15
dNumber of Pending ExpirationsOn..15
eNumber of Tax WarehousesOn..15
fNumber of Excise Authorisation ChangesOn..15
3.1 OPERATOR_TYPEO9x
aOperator Type CodeR

The possible values are:

1

=

Authorised warehouse keeper

2

=

Registered consignee

3

=

Registered consignor

n1
bNumber of Economic OperatorsRn..15
3.2 EXCISE_PRODUCT_ CATEGORY_ACTIVITYO9x
aExcise Products Category CodeR (see Code list 3 in Annex II)a1
bNumber of Economic OperatorsRn..15
3.3 EXCISE_PRODUCT_ ACTIVITYO9999x
aExcise Product CodeR (see Code list 11 in Annex II to Regulation (EC) No 684/2009)an..4
bNumber of Economic OperatorsRn..15
4 STA_ALL_MSO
aTotal Number of Active Economic OperatorsOn..15
bTotal Number of Inactive Economic OperatorsOn..15
cTotal Number of Pending ExpirationsOn..15
dTotal Number of Tax WarehousesOn..15
eTotal Number of Excise Authorisation ChangesOn..15
4.1 OPERATOR_TYPE_ALL_MSO9x
aOperator Type CodeR

The possible values are:

1

=

Authorised warehouse keeper

2

=

Registered consignee

3

=

Registered consignor

n1
bTotal Number of Economic OperatorsRn..15
4.2 EXCISE_PRODUCT_ CATEGORY_ACTIVITY_ ALL_MSO9x
aExcise Products Category CodeR (see Code list 3 in Annex II)a1
bTotal Number of Economic OperatorsRn..15
4.3 EXCISE_PRODUCT_ ACTIVITY_ALL_MSO9999x
aExcise Product CodeR (see Code list 11 in Annex II to Regulation (EC) No 684/2009)an..4
bTotal Number of Economic OperatorsRn..15
(2)

Commission Implementing Regulation (EU) No 612/2013 of 25 June 2013 on the operation of the register of economic operators and tax warehouses, related statistics and reporting pursuant to Council Regulation (EU) No 389/2012 on administrative cooperation in the field of excise duties (OJ L 173, 26.6.2013, p. 9).

(3)

Council Directive 2008/118/EC of 16 December 2008 concerning the general arrangements for excise duty and repealing Directive 92/12/EEC (OJ L 9, 14.1.2009, p. 12).

(4)

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