Commission Implementing Regulation (EU) 2015/2378 of 15 December 2015 laying down detailed rules for implementing certain provisions of Council Directive 2011/16/EU on administrative cooperation in the field of taxation and repealing Implementing Regulation (EU) No 1156/2012

Article 1

Standard forms for exchanges on request, spontaneous exchanges, notifications and feedback

Article 2

Computerised formats for the mandatory automatic exchange of information

Article 2a

Standard forms, including linguistic arrangements, for the mandatory automatic exchange of advance cross-border rulings and advance pricing arrangements

Article 2b

Linguistic arrangements for the mandatory automatic exchange of information on the country-by-country report

The key elements referred to in Article 20(6) of Directive 2011/16/EU are the information or explanation included in Table 3 of Section III of Annex III to that Directive and those key elements shall also be sent in English, except if another official language of the Union has been agreed to be used between the sending Member State and all the other Member States to which information is sent pursuant to Article 8aa(2) of Directive 2011/16/EU.

Article 2c

Form and conditions for the communication of the yearly assessment

Article 2d

List of statistical data

The list of statistical data required for the mandatory automatic exchange of information pursuant to Article 8(1) of Directive 2011/16/EU is set out in Annex X to this Regulation.

The list of statistical data required for the mandatory automatic exchange of information pursuant to Article 8(3a) of Directive 2011/16/EU is set out in Annex XI to this Regulation.

The list of statistical data required for the mandatory automatic exchange of information pursuant to Article 8aa of Directive 2011/16/EU is set out in Annex XII to this Regulation.

The list of statistical data required for the mandatory automatic exchange of information pursuant to Article 8ac of Directive 2011/16/EU is set out in Annex XV to this Regulation.

Article 2e

Standard forms, including linguistic arrangements, for the mandatory automatic exchange of information on reportable cross-border arrangements

Article 2f

Standard forms, for the communication of information on Excluded Platform Operators and Foreign Platform Operators to the central register, format of the individual identification number for Foreign Platform Operators and the retention period for information deleted from the central register

Article 2g

Standard forms, including linguistic arrangements, for the communication of information on Crypto-Asset Operators, and the retention period for information deleted from the Crypto-Asset Operator register

Article 3

Practical arrangements regarding the use of the CCN network

Article 4

Repeal

Implementing Regulation (EU) No 1156/2012 is repealed with effect from 1 January 2016.

References made to the repealed Implementing Regulation shall be construed as references to this Regulation.

Article 5

Entry into force and application

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

It shall apply from 1 January 2016.

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

ANNEX I

The form for requests for information and for administrative enquiries, pursuant to Article 5 and Article 5a of Directive 2011/16/EU, and their replies, acknowledgments, requests for additional background information, inability or refusal, pursuant to Article 7 of Directive 2011/16/EU, contains the following fields (³):

— Legal basis

— Reference number

— Date

— Identity of the requesting and requested authorities

— Identity of the person under examination or investigation

— General case description and, if appropriate, specific background information likely to allow assessing the foreseeable relevance of the information requested to the administration and enforcement of the domestic laws of Member States concerning the taxes referred to in Article 2 of Directive 2011/16/EU.

— Tax purpose for which the information is sought

— Period under investigation

— Name and address of any person believed to be in possession of the requested information

— Fulfilment of the legal requirement set out in Article 16(1) of Directive 2011/16/EU

— Fulfilment of the legal requirement set out in Article 17(1) of Directive 2011/16/EU

— Reasoned request for an administrative enquiry and reasons for refusal to undertake the requested administrative enquiry

— Acknowledgement of the request for information

— Request for additional background information

— Reasons for inability or refusal to provide information

— Reasons for a failure to respond by the relevant time limit and date by which the requested authority considers it might be able to respond

— A detailed description of the group.

ANNEX II

Form referred to in Article 1(3)

The form for spontaneous information and its acknowledgment pursuant to Articles 9 and 10 respectively of Directive 2011/16/EU contains the following fields (⁴):

— Legal basis

— Reference number

— Date

— Identity of the sending and receiving authorities

— Identity of the person subject to the spontaneous exchange of information

— Period covered by the spontaneous exchange of information

— Fulfilment of the legal requirement imposed by Article 16(1) of Directive 2011/16/EU

— Acknowledgement of the spontaneous information.

ANNEX III

Form referred to in Article 1(4)

The form for request for notification pursuant to Article 13(1) and 13(2) of Directive 2011/16/EU and their responses pursuant to Article 13(3) of that Directive contains the following fields (⁵):

— Legal basis

— Reference number

— Date

— Identity of the requesting and requested authorities

— Name and address of the addressee of the instrument or decision

— Other information which may facilitate the identification of the addressee

— Subject of the instrument or decision

— Response of the requested authority, in accordance with Article 13(3) of Directive 2011/16/EU, including the date of notification of the instrument or decision to the addressee.

ANNEX IV

Form referred to in Article 1(5)

The form for feedback pursuant to Article 14(1) of Directive 2011/16/EU contains the following fields (⁶):

— Reference number

— Date

— Identity of the competent authority issuing the feedback

— General feedback on the information provided

— Results directly related to the information provided.

ANNEX V

Computerised format referred to in Article 2(1)

The computerised formats for the mandatory automatic exchange of information pursuant to Article 8(1) of Directive 2011/16/EU comply with the following tree structure and contains the following classes of elements (⁷):

(a) As regards the overall message: Text of image - A "HEADER" containing: -- An "ORIGINATING COUNTRY", -- A "DESTINATION COUNTRIES", -- A unique "MESSAGE ID", -- A "CORRELATION ID", -- A "TIMESTAMP" and -- A "MESSAGE TYPE INDIC"; – And a "BODY" following the tree structure and classes of elements of any one of the bodies included in this annex under points (b) to (g) depending on the nature of the information to be exchanged automatically.

(b) As regards the body for communicating information on income from employment, director's fees or royalties: Text of image - An "APPLICATION ID" stating the nature of the information exchanged, - A "TAX YEAR" and - One or more building blocks containing: -- One or more "RECIPIENTS" providing information on each recipient and containing: --- One or more "PAYERS" providing information on each payer and containing: ---- One or more "RELATIONSHIPS" providing information on the nature of each relationship between the recipient and the payer and containing: ----- One or more "WORKPLACE" where the relationship is carried out and ----- One or more "INCOMES" providing information on each income or fee under the relationship and containing: ------ The "QUANTITY" of the days spent or worked by the recipient; -- And/or one or more "RECIPIENT INVALIDATIONS" in the case of a correction or cancellation of previously exchanged information.

(c) As regards the body for communicating information on pensions: Text of image - An "APPLICATION ID" stating the nature of the information exchanged, - A "TAX YEAR" and - One or more building blocks containing: -- One or more "RECIPIENTS" providing information on each recipient and containing: --- One or more "PAYERS" providing information on each payer and containing: ---- One or more "SCHEMES" providing information on each pension and containing: ----- One or more "SCHEME REFERENCE INFOS", ----- One or more "CAPITAL VALUES", ----- An "ADMINISTRATOR", ----- One or more "OWNERS", ----- One or more "EVENTS" providing general information on each event under the scheme and containing: ------ One or more "EVENT INFO" containing detailed information on the event and one or more "FINANCIAL INFO" and/or ------ One or more "TAX INFO" containing detailed information on the taxes and one or more "FINANCIAL INFO"; -- And/or one or more "RECIPIENT INVALIDATIONS" in the case of a correction or cancellation of previously exchanged information.

(d) As regards the body for communicating information on life insurance products: Text of image - An "APPLICATION ID" stating the nature of the information exchanged, - A "TAX YEAR" and - One or more building blocks containing: -- One or more "POLICIES" providing information on each product and containing: --- A "CONTRIBUTION DURATION", --- A "BENEFIT DURATION", --- A "POLICY OPTIONS", --- One or more "POLICY CAPITAL VALUES", --- An "INSURER/PAYING AGENT", --- One or more "BENEFICIARIES", --- One or more "LIFE INSURED", --- One or more "PAYERS OF PREMIUMS", --- One or more "POLICY OWNERS", --- One or more "EVENTS" providing general information on each event under the policy and containing: ---- One or more "EVENT INFO" containing detailed information on the event and one or more "FINANCIAL INFO" and/or ---- One or more "TAX INFO" containing detailed information on the taxes and one or more "FINANCIAL INFO"; -- And/or one or more "POLICY INVALIDATIONS" in the case of a correction or cancellation of previously exchanged information.

(e) As regards the body for communicating information on ownership of and income from immovable property: Text of image - An "APPLICATION ID" stating the nature of the information exchanged, - A "TAX YEAR" and - One or more building blocks containing: -- One or more "PARTIES" providing information on each recipient and containing: --- A "PARTNER" providing information on the spouse and --- Option 1 when the information relates to an income which cannot be linked (even indirectly) to one or more identified property: one or more "INCOMES" or --- Option 2 when the information relates either to another information than an income or to an income which can be linked (even indirectly) to one or more identified property: one or more "PROPERTIES" providing information on each property and containing: ---- One or more "OWNERSHIPS" and its associated "RIGHT" providing information on each ownership and associated right in the property and containing: ----- One or more "TRANSACTIONS" providing information on each transaction relating to the property, ----- One or more "INCOMES" providing information on each income relating to the; -- And/or one or more "PARTY INVALIDATIONS" in the case of a correction or of previously exchanged information.

(f) As regards the body in case no information is to be communicated in relation to a specific category: Text of image - An "APPLICATION ID" stating the nature of the information exchanged, - A "DETAIL" stating the reason for the absence of data and - A "YEAR".

(g) As regards the body for an acknowledgement of receipt of the information for a specific category: Text of image - An "APPLICATION ID" stating the nature of the information exchanged, - A "STATUS" providing information on the acceptance or rejection of a message and - One or more "ERROR" providing information on the errors identified in a message received."

ANNEX VI

Computerised format referred to in Article 2(2)

The computerised format for the mandatory automatic exchange of information pursuant to Article 8(3a) of Directive 2011/16/EU complies with the following tree structure and contains the following elements and attributes (⁸):

(a) As regards the overall message: Text of image

Message type defines the type of reporting

Account Holder Type Passive Non-Financial Entity with one or more controlling person that is a Reportable Person CRS Reportable Person Text of image Passive NFE that is a CRS Reportable Person

The code describing the nature of the payments used in CRS Dividends Interest Gross Proceeds/Redemptions Other - CRS

The MessageTypeIndic defines the type of message sent The message contains new information The message contains corrections for previously sent information Text of image The message advises there is no data to report

Controlling Person Type CP of legal person - ownership CP of legal person - other means CP of legal person - senior managing official CP of legal arrangement - trust - settlor CP of legal arrangement - trust - trustee CP of legal arrangement - trust - protector CP of legal arrangement - trust - beneficiary CP of legal arrangement - trust - other Text of image CP of legal arrangement - other - settlor-equivalent CP of legal arrangement - other - trustee-equivalent CP of legal arrangement - other - protector-equivalent CP of legal arrangement - other - beneficiary-equivalent CP of legal arrangement - other - other-equivalent

Information in the message header identifies the Tax Administration that is sending the message. It specifies when the message was created, what period (normally a year) the report is for, and the nature of the report (original, corrected, supplemental, etc).

Free text expressing the restrictions for use of the information this message contains and the legal framework under which it is given All necessary contact information about persons responsible for and Text of image involved in the processing of the data transmitted in this message, both legally and technically. Free text as this is not intended for automatic processing. Sender's unique identifier for this message Sender's unique identifier that has to be corrected. Must point to 1 or more previous message The reporting year for which information is transmitted in documents of the current message.

Account number definition Text of image Account Number Type Undocumented Account Closed Account Dormant Account

The user must spread the data about the name of a party over up to six elements. The container element for this will be 'NameFix'. His Excellency,Estate of the Late ... Text of image Greeting title. Example: Mr, Dr, Ms, Herr, etc. Can have multiple titles. FirstName of the person Defines the name type of FirstName. Example: Given Name, Forename, Christian Name, Father's Name, etc. In some countries, FirstName could be a Family Name or a SurName. Use this attribute to define the type for this name. Middle name (essential part of the name for many nationalities). Example: Sakthi in "Nivetha Sakthi Shantha". Can have multiple middle names. Defines the name type of Middle Name. Example: First name, middle name, maiden name, father's name, given name, etc. de, van, van de, von, etc. Example: Derick de Clarke Text of image Defines the type of name associated with the NamePrefix. For example the type of name is LastName and this prefix is the prefix for this last name. Represents the position of the name in a name string. Can be Given Name, Forename, Christian Name, Surname, Family Name, etc. Use the attribute "NameType" to define what type this name is. In case of a company, this field can be used for the company name. Defines the name type of LastName. Example: Father's name, Family name, Sur Name, Mother's Name, etc. In some countries, LastName could be the given name or first name. Jnr, Thr Third, III Could be compressed initials - PhD, VC, QC Deceased, Retired ...

Text of image

This container brings together all data about a person as a party. Name and address are required components and each can be present more than once to enable as complete a description as possible. Whenever possible one or more identifiers (TIN etc) should be added as well as a residence country code. Additional data that describes and identifies the party can be given. The code for the legal type according to the OECD codelist must be added. The structures of all of the subelements are defined elsewhere in this schema.

This is the identification number/identification code for the Entity in question. As the identifier may be not strictly numeric, it is just defined as a string of characters. Attribute 'issuedBy' is required to designate the issuer of the identifier. Attribute 'INType' defines the type of identification number. Country code of issuing country, indicating country of Residence (to taxes and other) Text of image Identification Number Type

This container brings together all data about an organisation as a party. Name and address are required components and each can be present more than once to enable as complete a description as possible. Whenever possible one or more identifiers (TIN etc) should be added as well as a residence country code. Additional data that describes and identifies the party can be given . The code for the legal type according to the OECD codelist must be added. The structures of all of the subelements are defined elsewhere in this schema. Entity Identification Number

Type of payment (interest, dividend,...) Text of image The amount of payment

Reporting financial institution For CRS, only one ReportingGroup for each CrsBody is to be provided

CRS Version