CRS Manual

From E-fileWiki
Jump to navigation Jump to search

Transmission follow up.PNG

Introduction

The Luxembourg Tax Authority (Administration des contributions directes (ACD)) published on 6 February 2017 the ECHA - n° 4 Circular. This Circular describes the format and procedures of the Common Reporting Standard (CRS) that Luxembourg Reporting Financial Institutions (RFI) will have to follow according to the CRS Luxembourg law, 24 December 2015.


IMPORTANT: all pre-filled data have to be communicated to Fundsquare in order to be integrated in Fundsquare's database and to be available in the CRS form.
=> Consult our CRS Onboarding process for more information.

Report type

Choose the 'CRS Form' in the Report Generation module.


The CRS Report form opens and a small window pops up where you have to select the CRS report type.

In our example we will select CRS Report.

Select the CRS Report Type.png



The form

CRS-After-FrontPage.png

Note the vertical navigation bar on the left.

The different sections can be accessed via the buttons in the vertical navigation bar or clicking directly on the section's title.


AEOI reference

CRS-After AEOI.png

You can find the AEOI reference field in the first section of the CRS form under Information on depositor.

-This field has to be completed with a unique identifier.

-The ACD recommends to use a "timestamp", a digital counter or a "GUID" (Globally Unique Identifier).

-Specification examples: only capital characters (A-Z), number 0-9, must be unique, etc.

-The ACD asks not to include confidential data in the identifying elements.

Cf. ECHA - n° 4 of 6 February 2017 on page 21-22.

Information on depositor

CRS-After InformationDepositor.png

The Information on depositor has to be completed in the section 1 of the form.

Depositor name (pre-filled)
The Depositor is an entity (legal or natural person) that is in charge of filing the CRS reporting to the ACD (e.g. Service provider). The depositor and the declarer may be the same entity.
Cf. ECHA - n° 4 of 6 February 2017 on page 10.


Personal Identification Number (pre-filled)
The Depositor needs a Personal Identification Number (Luxembourgish Matricule Number also known as CCSS code) to be able to file the report.

If the Depositor does not have a Luxembourgish Matricule Number, he has to contact the Bureau de la retenue d'impôt sur les intérêts to obtain one.

-by phone: Contacts


Reporting Financial Institution

After-CRS-ReportingPerson.png

The Reporting Financial Institution (RFI) information has to be completed in section 2 of the form.


Name of the Reporting Financial Institution
Select the entity in the drop-down list for which the reporting has to be done.


Name
Name of the RFI (pre-filled once the RFI has been selected)


Entity Identification number
The Identification number is the Luxembourgish Matricule number of the RFI (pre-filled once the RFI has been selected)


Entity Identification number extension
The extension of the Luxembourgish Matricule number (pre-filled once the RFI has been selected). Example of an UCI that reports on UCI level: M00000000 (The Reporting FI Identifier will be 12345678912M00000000)

If a sub-entity wants to submit a CRS reporting to the ACD and does not have a personnel number, it puts the parent entity's number in the Entity Identification number field and an additional identifier in the Entity Identification number extension field. Example: a sub-fund that wants to report directly, can enter the umbrella number (= tax identification number available on the subscription-tax returns) in the Entity Identification number field and the sub-fund number (CSSF code of the sub-fund) in the Entity Identification number extension field. Exemple: F00000002 (The Reporting FI Identifier will be 12345678912F00000002)

IMPORTANT: instructions published on the ACD website should be followed in the event that the Luxembourg Financial Institution has no Luxembourgish matricule.


Reporting FI Identifier
It is the concatenation of the Identification Number and Identification Number Extension (pre-filled once the RFI has been selected).

Personnal information

CRS-After-InformationDeclarer.png

Still in section 2.

The ACD needs contact details of a person who would be able to answer business questions regarding the report.

Cf. ECHA - n° 4 of 6 February 2017 on page 10

Header tab

First part of the screenshot CRS report Header

CRS-After-Header.png

The Header information has to be completed in section 3 of the form.

The information in the header tab identifies the Competent Authority that is sending the message, as well as the Competent Authority receiving the message. It specifies when the message was created and the nature of the report.

Transmitting country
Must always be LU. This data element identifies the jurisdiction of the Competent Authority transmitting the message, which is the Competent Authority that has received the initial CRS message.
Cf. ECHA - n° 4 of 6 February 2017, page 28.

Receiving country
Must always always be LU. This data element identifies the jurisdiction of the Competent Authority receiving the message, which is the Competent Authority that has sent the initial CRS message.
Cf. ECHA - n° 4 of 6 February 2017, page 28.

Warning
This optional data element is a free text field allowing input of specific cautionary instructions about use of the CRS Status Message.
Cf. ECHA - n° 4 of 6 February 2017, page 30.



Second part of the screenshot CRS report Header

Fatca-After-HeaderPartIInew.png

Contact
This optional data element is a free text field allowing input of specific contact information for the sender of the message (i.e. the Competent Authority sending the CRS Status Message).
Cf. ECHA - n° 4 of 6 February 2017, page 30.

Message reference ID
This field has to be completed with a unique identifier.
The ACD recommends to use a "timestamp", a digital counter or a "GUID" (Globally Unique Identifier).
Specification examples: only capital characters (A-Z), number 0-9, must be unique, etc.
The ACD asks not to include confidential data in the identifying elements.
Cf. ECHA - n° 4 of 6 February 2017, page 21-22 and page 28.

Declaration type

Select the Declaration type you need.
CRS701: The message contains new information
CRS702: The message contains corrections / cancellations for data previously reported
CRS703: The message informs that there are no data to declare by Luxembourg Reporting Financial Institution for the fiscal year indicated.

Reporting period

Select the icon that contains the tax year to which the message relates.

Groups

Manage countries

Click on the section 4 icon.
A window Manage countries pops-up.
Select the country and click the Validate button.

After-CRS-ManageCountries.png


CRS-After-Groups.png

In our case we selected Andorra and United Arab Emirates



Reporting FI

Click on the Reporting FI icon After-CRS-Reporting FI icon2.png. The drawer Reporting FI opens.

After-CRS-Reporting FI.png

Complete the fields. Mandatory fields are marked with a red asterisk.

Residence country
The country or countries of tax residence of the Luxembourg RFI. The "Residence country" element corresponds to the country or countries of tax residence of the Luxembourg RFI. There must be at least one element which has the value "LU". In addition, the value of the "Residence country" element must be equal to the value of the "TransmittingCountry" element, otherwise the file is rejected with error code 60013.
Cf. ECHA - n° 4 of 6 February 2017, page 34.

IN
The tax identification number(s) of the RFI. At least the Luxembourg Personal Identification Number (Matricule) of the Luxembourg RFI must be present.

Organisation name
The name of the Reporting Financial Institution (RFI). The RFI is the entity that is subject to the CRS Reporting.

Address
The address of the RFI

Cf. ECHA - n° 4 of 6 February 2017, page 31.

Document type
This element specifies the type of data to be transmitted
OECD0: Resend data
OECD1: New data
OECD2: Corrected data
OECD3: Deletion of data
Important:The file is rejected in case of Document type = OECD3 and if all account reports related to this Reporting FI have not previously been deleted.
Cf. ECHA - n° 4 of 6 February 2017, page 32.

Document reference ID

Cf. chapter 2.4.1.1 AEOI reference

Document reference ID to correct
This element is a reference to the unique identifier of the data that is to be corrected / deleted and its value must be known by the ACD because it had been previously transmitted via a new data message.
Cf. ECHA - n° 4 of 6 February 2017, page 33.

Account Report

After-CRS-AccountReport.png

AfterPoint1.pngClick on the Account report icon. The Account report drawer opens.

AfterPoint2.pngClick on Add an account report. The Add an account report drawer opens.

AfterPoint3.pngComplete the form and click on Save report button.


The Account Report can only be omitted if the Reporting FI is being corrected (OECD2) / deleted (OECD3) or, in the case of domestic reporting, if there is nil reporting (CRS703). If the Reporting FI indicates new data or resent data, then the Account Report must be provided.

Document type
OECD0: Resent data. This value is not authorized in the context of account reports
OECD1: New data
OECD2: Corrected data
OECD3: Deletion of data


Document Reference Id
Cf. chapter 2.4.1.1 AEOI reference
Cf. ECHA - n° 4 of 6 February 2017, page 39.


Document Reference ID to correct
This ID references the Document Reference ID of the element to be corrected (OECD2) or deleted (OECD3). It must always refer to the latest reference of this Account Report (Document Reference ID) that was sent.
Cf. ECHA - n° 4 of 6 February 2017, page 40.


Organisation Account Number type

OECD601: IBAN - International Bank Account Number
OECD602: OBAN - Other Bank Account number
OECD603: ISIN - International Securities Identification Number
OECD604: OSIN _ Other Securities Identification Number
OECD605: Other


Account holder type
If the account holder is an organisation, select the account holder type:
CRS101 = Passive Non-Financial Entity with - one or more controlling person that is a Reportable Person
CRS102 = CRS Reportable Person
CRS103 = Passive Non-Financial Entiy that is a CRS Reportable Person

Type of message

New data message
A new data message is a message declaring data that is not yet known by the ACD. It is characterized by the value "CRS701" and by the value "OECD1"

New Data Message.PNG

Correction message
A correction message is a message that corrects or cancels data already known by the ACD. It is characterized by the value "CRS702" and the value "OECD2" or "OECD3".


Correction Message.PNG

Export - import files - save work in progress

CRS-After-SaveLocallyButton.png

Report type button

Press the REPORT TYPE button, if you want to change your FATCA Report Type. A small window pops up where you can select the report type you need:

- Contact update
- Zero report
- FATCA report


Select an existing report button

This button allows you to upload an existing XML report from your network or hard-drive into the report generator.


Save locally button

Work in progress on a report has to be saved with this button. Work in progress means that the report is not finalized, as important data are missing. The exported .xml file will be called DRAFT_filename.xml and cannot be uploaded for filing. It can be imported onto the tool for later use.

If you save locally a final report, meaning that all relevant data are available inside the report, it will carry the correct naming convention for submission to the Regulator.


Transmit button

If all buttons of the sidebar are green, the Transmission button will become available and the report can be transmitted to the regulator.

File transmission

The form is completed and all ticks are green.

Click the After-CRS-TransmitButtton.png button.


A drawer opens from the right, fill the form and click 'Transmit'.


CRS Transmit.png


Note: the file name is automatically generated and compliant to the ACD file naming convention.

Transmission follow up

Please consult our wiki page TRansmission Monitoring

Automatic filing through the Sending Service

CRS.xml files have to be dropped into the CRS subfolder:

CRS SD.jpg


  • Should you need further information on the Sending Service, please click the links below:

Sending Service Installation Procedure

Sending Service Update Procedure

Wiki-Sending Service



CRS file naming convention

The following naming convention has to be applied for the files:

XML file :
CRS<SEP>DateHeure<SEP>MessageTypeIndic<SEP>AnnéeFiscale<SEP>Canal<SEP>MatriculeDuDéposant<SEP>MatriculeDuRFI<SEP>Environnement.xml


Code Definition Structure Values
<SEP> Separator of the different variables of the file. The separator chosen is the underscore: _. Char(1) underscore: _.
DateHeure Creation date and time of the XML file Number(14) YYYYMMDDhhmmss
MessageTypeIndic CRS701: The message contains new information

CRS702: The message contains corrections for previously sent information

CRS703: The message advises there is no data to report


Char(3)Number(3) CRS701

CRS702

CRS703

AnnéeFiscale Fiscal year Number(4) YYYY
Canal Communication channel Char(1) B = Bourse
MatriculeDuDéposant Social Security Identification Number (Matricule, code CCSS) Number(11) 0-9
MatriculeDuRFI Concatenation of <ReportingPerson> / <IdentificationNumber> and <ReportingPerson> / <IdentificationNumberExtension> Number(11), char(1), number(8) 12345678901M00000000
Environnement Environment type Char(1) P = Production

T = Test


Example:

CRS_20170615114523_CRS701_2016_B_19751234567_01234567890M00000000_P.xml


VAL = Validated and imported by ACD

ERR = File rejected



Report transmission

File processing status generated by the Sending Service

During and at the end of the sending, the Sending Service generates various files in the subfolder that has been used for the sending. Three type of files are generated:

  • .trt file : indicates the start of the transmission

In order to be able to send the original file, the Sending Service transforms the latter into a .trt file and adds a timestamp. E.g. «OriginalName.xml» is transformed into OriginalName.xml.timestamp.trt:

.xml becomes

.trt

  • .acq file : the transmission has been successfully completed
  • .err file : indicates that an error has occurred during the sending

The error file contains technical messages indicating the root cause of the error, e.g. file name errors.



File transmission follow-up

Transmission status