E-fileWiki - User contributions [en]

FundamentalDataForm

2026-05-28T11:51:27Z

Cso: /* How to complete the FDF */

Obsolete page

=Introduction=

<span style="color:white; background:DarkTurquoise"> '''Please be informed that we are working on a new e-file version of the '''Static Data Management''' ('''SDM''') application that will be delivered in the first quarter of 2020.''' </span>

This modernized e-file version will introduce a <u>new design</u> and <u>improve ergonomics</u> for a better user experience.

Please find below our '''Before - After User Guide''' where all changes will be explained.

=Select Test or Production environment=

Production environment : '''https://www.e-file.lu/e-file/'''

Homologation environment (Test) : '''https://homologation.e-file.lu/e-file/'''

=E-file login=

Enter your e-file login credentials (user name and password) and click the ACCESS button.

[[File:BeforAfterLogin.png|border|800 px]]

'''IMPORTANT:''' If you do not have an e-file user account, you might contact the '''e-file administrator''' of your company.

[[E-file Administration|=>for more detailed information please click the link '''e-file Administration''']]

=Launchpad=

Once logged in, the e-file launchpad opens.

Click on the '''Static Data Management''' icon to access the module.

[[File:3Launchpad.png|800 px]]

=Select template - Before=

The '''Export screen''' opens.

[[File:3BeforeServiceSelection.png|border|700 px]]

[[File:BeforePoint1.png|20 px]] Open the drop-down list to select the SERVICE

=Select template - After=

[[File:5After SelectTemplate.png|700 px]]

[[File:AfterPoint1.png|20 px]] Click on the arrow highlighted in yellow in the top left hand corner of the page to open the drop-down list to select the TEMPLATE [[File:AfterPoint2.png|20 px]]

=Filter functions - Before=

[[File:2Before FilterFunctions.png|1000 px]]

[[File:BeforePoint1.png|20 px]] Click on the FILTER button on the left side of the screen. A window opens where you can specify your search criteria.

[[File:BeforePoint2.png|20 px]] Narrow your search criteria by selecting the PROMOTER/LIBRARY OWNER, FUNDS, SUB-FUND, SHARE CLASS.

[[File:BeforePrint3.png|20 px]] Narrow your search criteria by selecting the STATUS of your instrument (e.g. active and public).

[[File:BeforePrint4.png|20 px]] RESET button to clear all fields and start a new search.

[[File:BeforePrint5.png|20 px]] SEARCH button to start the search.

[[File:BeforePrint6.png|20 px]] EXPAND/COLLAPSE button to display the whole fund tree (fund, sub-funds and share classes) (EXPAND) or to display only the fund level (COLLAPSE).

[[File:BeforePrint7.png|20 px]] Narrow your search criteria by entering the ISIN, CSSF CODE or INTERNAL CODE in the appropriate search field.

[[File:BeforePrint8.png|20 px]] REFRESH button to make available the most updated version of the page you are viewing.

[[File:BeforePrint9.png|20 px]] Specify your display options: SHOW SELECTED instruments, SELECT ALL instruments, UNCHECK ALL boxes.

[[File:BeforePrint10.png|20 px]] Specify your SELECTION option. STANDARD: each box of the fund tree has to be selected either manually or through the SELECT ALL button. [[File:BeforePrint11.png|20 px]] SPREAD: the checked box of the fund will be automatically spread to the whole fund tree.

[[File:BeforePrint12.png|20 px]] EXPORT button: all selected instruments (with checked boxes) will be exported in the file.

=Filter functions - After=
[[File:2AfterSDMExport.png|1000 px]]

[[File:AfterPoint1.png|20 px]] Click on the '''FILTER''' button [[File:AfterSDMFilter.png|30 px]] on the right side of the screen. A toolbar (highlighted in yellow) opens where you can narrow your search options by specifying the [[File:AfterPoint2.png|20 px]] STATUS of the instrument (e.g. active and public).

[[File:AfterPoint3.png|20 px]] Click inside the toolbar highlighted in yellow. A drop-down list '''DATA FILTERS''' pops up where you can narrow your search criteria by selecting e.g. ISIN, CSSF CODE. Enter your ISIN, CSSF CODE in the dedicated search field (3a, 3b) and

[[File:AfterPoint4.png|20 px]] Press the '''SEARCH''' button or press ENTER.

[[File:AfterPoint5.png|20 px]] Press the '''RESET''' button [[File:AfterSDMResetButton.png|20 px]] to clear all fields and reset filters.

[[File:AfterPoint6.png|20 px]] If the '''SELECT ALL''' box is checked, all instruments of all management companies that are linked in our database to the ACTOR are selected.

[[File:AfterPoint7.png|20 px]] Display options

:: If the '''SHOW ONLY SELECTED''' button is green, only the selected instruments are displayed on the screen.

:: If the '''EXPAND ALL''' button is green, the whole tree structure (fund, sub-fund, share class) of the instrument is displayed.

:: If the '''SPREAD SELECTION TO RELATED INSTRUMENTS''' button is green and you select an instrument at fund level, the whole tree structure of the fund will be automatically selected.

[[File:AfterPoint8.png|20 px]] If you press the '''EXPORT''' button, all selected instruments with checked boxes will be exported in the file.

=Export a file - Before=
[[File:2BeforeSDMExport.png|700 px]]

Press the '''EXPORT''' button.

[[File:BeforePoint1.png|20 px]] A message on the top of the screen informs you that '''Currently 1 report(s) is generated'''.

[[File:BeforePoint2.png|20 px]] Once the file is generated, a window pops up indicating '''The following report was generated'''. Press the OK button to open the file.

=Export a file - After=
[[File:2AfterSDMEportFDF.png|700 px]]

[[File:AfterPoint1.png|20 px]] Press the '''EXPORT''' button

[[File:AfterPoint2.png|20 px]] The red notification indicates that one file is being generated or has been generated.

[[File:AfterPoint3.png|20 px]] Once that file is generated, a window pops up indicating '''The following report has been generated'''.

[[File:AfterPoint4.png|20 px]] Open the file that is available at the bottom of the page.

=Import a file - Before=
[[File:3BeforeSDMImport.png|800 px]]

[[File:BeforePoint1.png|20 px]] Open the '''IMPORT''' tab on the top of the screen.

[[File:BeforePoint2.png|20 px]] Select the '''SERVICE'''.

[[File:BeforePrint3.png|20 px]] Press the button '''ADD a FILE''' and select the file you want to import.

[[File:BeforePrint4.png|20 px]] Press the '''IMPORT''' button.

[[File:BeforePrint5.png|20 px]] A window '''REQUEST FOR UPDATE WITHIN THE FUNDSQUARE STATIC DATA REFERENTIAL''' pops up. Complete the fields and press the '''VALIDATE''' button.

[[File:BeforePrint6.png|20 px]] A window opens indicating that '''Your document has been successfully uploaded. Within 72 hours you will receive a confirmation on its processing.'''

=Import a file - After=
[[File:3AfterSDMImport.png|800 px]]

[[File:AfterPoint1.png|20 px]] Press the '''FLOW-CHART''' button [[File:AfterSDMFlowChartButton.png|20 px]]. A small window pops up with two options: '''EXPORT''' and '''IMPORT'''. Select '''IMPORT.'''

[[File:AfterPoint2.png|20 px]] You have two options to upload your file:

:: - either you '''BROWSE''' your file system and select the file you want to upload

:: - or you '''DRAG & DROP your file directly onto the appropriate area [[File:AfterSDMDragDrop.png|20 px]]

:: <span style="color:white; background:DarkTurquoise"> '''NEW:''' </span> Please be informed that new <u>features</u> have been added to the new e-file version of the '''Static Data Management''' application. You have now the possibility to upload <u>several</u> files at the same time.

:: In our example we uploaded two files:

:: ABC_2019_12_17_FDF.xlsx (cf. '''2b''')

:: XYZ_2019_12_17_FDF.xlsx (cf. '''2a''')

[[File:AfterPoint3.png|20 px]] You have two options to add the mandatory parameters '''TEMPLATE''', '''ACTION''', '''COMMENT'''

::- either you select each parameter for each single file

::- or you set all parameters via the SET BULK PARAMETERS [[File:AfterPoint4.png|20 px]] funcionality cf. screen below

'''VERY IMPORTANT INFORMATION'''

Please ensure that you always follow the Fundsquare naming convention of the templates. The respective acronyms at the end of the file name are '''mandatory''' and they have to be preceded by an underscore. Please note that only '''.xlsx''' files are allowed to be imported.

FDF template: nnnnnnn_'''FDF'''.xlsx

MIFID template: nnnnnnn_'''MIFID'''.xlsx

PRIIPS template: nnnnnnn_'''PRIIPS'''.xlsx

==Set bulk parameters==
[[File:2AfterSDMBulkImport.png|600 px]]

[[File:AfterPoint1.png|20 px]] If you check the '''SELECT ALL''' box and complete all mandatory fields in this sections, all mandatory fields of the two files we imported, will be populated automatically with the same parameters.

[[File:AfterPoint2.png|20 px]] Press the '''VALIDATE IMPORT PARAMETERS''' button.

==Import confirmation==
[[File:NewSDM.png|600 px]]

[[File:AfterPoint1.png|20 px]] Press the IMPORT DATA button.

[[File:AfterPoint2.png|20 px]] A window pops up indicating '''Your documents were received'''

[[File:AfterPoint3.png|20 px]] At the top of the screen a toast notification shows up confirming that the import was successful.

[[File:AfterPoint4.png|20 px]] The red notification with number 2 inside, shows you that 2 files have been imported.

[[File:AfterPoint5.png|20 px]] If you click on the exclamation mark, a drop down list with all imported files opens.

Furthermore, please be informed, that you will receive a '''notification''' by email with detailed information on your files you imported.

[[File:ConfirmationMail.png|border|400 px]]

==How to use FSQ IDs in the Fundamental Data Form (FDF)==

In the following, we would like to explain you, how to use <u>Fundsquare's internal identification numbers</u> of instruments which are available in column 45, 46, 47 of the Fundamental Data Form (Id Fund, Id Sub-Fund, Id Share-Class).

(1) <u>Modification of an instrument</u>

If you modify an instrument '''<u>the three FSQ Id must not be changed under no circomstances</u>.'''

For example, if you want to change a sub-fund name, the new name must be reported in the appropriate cell. '''DO NOT CHANGE''' the FSQ IDs.

[[File:1 FSQ ID FDF.png|border|300 px]]

(2) <u>Closure of an instrument</u>

If you want to close an instrument, the appropriate cells in column 13, 24, 34 have to be completed with the closure date. '''DO NOT CHANGE''' the FSQ IDs.

[[File:1 FSQ ID FDF.png|border|300 px]]

Please note, that if you close a fund, the whole fund tree structure will be closed in our database.

If you close a single sub-fund, all share classes belonging to this sub-fund will be closed in our database.

(3) <u>Creation of a new fund</u>

To create a new fund, select a standard FDF extraction with the same fund structure (SICAV i.e..) and the same Law directive (P110 i.e..) as the new one you will have to create.

'''<u>IMPORTANT</u>''': you '''must <u>REMOVE</u> all ID instruments''' from the cells in columns 45, 46 and 47 as they refer to a <u>already existing instrument</u>', and the risk is you replace the existing instrument.

[[File:2 FSQ ID FDF.png|border|300 px]]

(4) <u>Creation of a new sub-fund</u>

For example, if you want to add 3 sub-funds to an existing fund, you have to add 3 lines below the fund in the extraction template and complete the appropriate cells.

'''<u>REMOVE</u> Id Sub-Fund and Id Share-Class''', but '''<u>DO NOT CHANGE</u> the Id Fund'''.

[[File:3 FSQ ID FDF.png|border|300 px]]

(5) <u>Creation of a new share-classes</u>

For example, if you want to add 5 share-classes to an existing sub-fund, you have to add 5 lines to the existing sub-fund structure in the extraction template. Complete all cells accordingly.

'''<u>REMOVE</u> Id Share-Class''', but '''<u>DO NOT CHANGE</u> the Id Fund and Id Sub-Fund'''.

[[File:4 FSQ ID FDF.png|border|300 px]]

(6) Exception in column 28

In the case of share class creations, we would like to ask you, for internal processing reasons only, to delete all "Capitalisation" and "Distribution" words that appear in column 28.

[[File:SDMException.png|400 px]]

== How to complete the FDF ==
In due course, we will provide further information on this section.<br>
<div style="text-align: center;">
{| border="1" cellspacing="5" cellpadding="10"
|-
|'''Main Category'''||'''Column Number'''||'''Field Label'''||'''Mandatory Field'''||'''Definition'''||'''Type of Data'''||'''Field Format'''||'''Format Constraints'''||'''Business Rule'''||
|-
|'''Third-Party Information'''||1||Promoter||No||Indicates the name of the Initiator/Sponsor of the fund including the country||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||2||Management Company||Yes||Indicates the name of the Management Company of the fund including the country||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||3||Investment Company||Conditional cf Definition||Indicates the name of the Investment Company of the fund including the country.<br>This field is mandatory if the fund is self-managed and no management company has been provided||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||4||Fund Administration||Yes||Indicates the name of the Administrator of the fund including the country.||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||5||Transfer Agent||Conditional cf Definition||Indicates the name of the Transfer Agent of the fund including the country.<br>This field is mandatory for the Order Routing Data||Company Name||String char (100)||N/A||N/A||
|-
|'''Fund Information'''||6||Fund Name||Yes||Indicates the legal name of the fund||Label||String char (100)||Is unique in Fundsquare's database (upper/lower case letters)||N/A||
|-
|'''Fund Information'''||7||Fund National Competent Authority Code||No||Indicates the codification used by the fund's domicile authority on fund level||Codification||String char (20)||Is unique in Fundsquare's database||N/A||
|-
|'''Fund Information'''||8||Fund Administration Code||No||Indicates the central administration's instrument code at the fund level (AC internal code)||Codification||String char (20)||Is unique at this level||N/A||
|-
|'''Fund Information'''||9||Fund GIIN Code||Conditional cf Definition||Indicates the Global Intermediary Identification Number of the instrument at the fund level<br>This field is mandatory for FATCA reporting||Codification||String char (20)||Alphanumerical: Char(6).Char(5).Char(2).Number(3).<br>Is unique in Fundsquare's database.||Has to be unique if not SP (Sponsor).<br>7th char = "."<br>13th char = "."<br>16th char = "."<br>&<br>Last 3 char = 442<br>or<br>14th&15th = SP
|-
|'''Fund Information'''||10||Fund RFI ID (CRS)||Conditional cf Definition||Indicates the Social Security Identification number at the fund level. Mandatory for CRS reporting||Codification||String char (20 or 22)||Number(11) - Number(13)||9th char is a letter followed by 8 "0"||
|-
|'''Fund Information'''||11||Type of EU Directive||Yes||Indicates whether the fund is an UCITS-fund or an AIF-fund according to european directives||Indicator||String char (6)||List of values:<br>UCITS<br>AIF<br>OTHER||N/A||
|-
|'''Fund Information'''||12||Umbrella Fund||No||Indicates whether the fund is an umbrella or not||Indicator||String char (3)||Boolean: YES/NO||N/A||
|-
|'''Fund Information'''||13||Fund Creation Date||Yes||Indicates the date on which the fund is created/activated||Date||Date char (10)||Date format: dd/MM/yyyy||If date > current date OR If no date = inactivated = anticipated creation (AC).<br>If date ≤ current date = activated = available for documents notification and dissemination (ACT).||
|-
|'''Fund Information'''||14||Fund End Date||No||Indicates the ending date of the fund's activity (closing/liquidation date)||Date||Date char (10)||Date format: dd/MM/yyyy||If Date ≤ current date = inactivated = not available for documents notification and dissemination.<br>available 1 year for reporting.||
|-
|'''Fund Information'''||15||Fund Jurisdiction Country||Yes||Indicates the country where the fund is domiciled||Legal||String char (2)||Code ISO2||The two first characters must be the same as the two first letters included in ISIN code.<br>For example: LU, GB, IE, etc.||
|-
|'''Fund Information'''||16||Fund Legal Form||Yes||Indicates the legal form of the fund||Legal||String char (4)||List of values:<br>"FCP" = FCP: Common fund<br>"SICV" = SICAV: Investment company with variable capital<br>"SICF" = SICAF: Investment company with fixed capital<br>"SICR" = SICAR: Investment company in risk capital<br>"OT" = OT: Securitisation entities<br>"SCA" = SCA: Partnership limited by shares<br>"SCS" = SCS: Limited partnership<br>"SCSp" = SCSp: Special partnership<br>"SA" = SA: public limited liability company<br>"OTH" = OTHER: Other fund||Linked/compatible with "Fund Legal Status"||
|-
|'''Fund Information'''||17||Fund Legal Status ||Yes||Indicates the legal status of the fund||Legal||String char (4)||List of values:<br>"SIF" = SIF<br>"NLUX" = Non-LU-domiciled<br>"PA04" = Law 14 june 2004<br>"PA05" = Law 22 march 2004<br>"PA06"=Law 10 august 1915<br> "PA07"=Law 23 july 2016<br> "PA08"=Law 12 July 2013<br> "PA09"=Law 15 December 2019<br> "PA10"=Law 16 july 2019<br>"P110" = Part I 2010 law<br>"P210" = Part II 2010 law<br>"RAIF" = RAIF||Linked/compatible with "Fund Legal Form"||
|-
|'''Sub-fund Information'''||18||Sub-Fund Name||Yes||Indicates the legal name of the sub-fund||Label||String char (100)||Is unique in Fundsquare's database at this level (upper/lower case letters)||N/A||
|-
|'''Sub-fund Information'''||19||Sub-Fund National Competent Authority Code||No||Indicates the codification used by the fund's domicile authority at the sub-fund level||Codification||String char (20)||Is unique in Fundsquare's database||N/A||
|-
|'''Sub-fund Information'''||20||Sub-Fund Administration Code||No||Indicates the central administration's instrument code at the sub-fund level (AC internal code)||Codification||String char (20)||Is unique at this level||N/A||
|-
|'''Sub-fund Information'''||21||Sub-Fund GIIN Code||Conditional cf Definition||Indicates the Global Intermediary Identification Number for the instrument at the fund level.<br>This field is mandatory for FATCA Reporting.||Codification||String char (20)||AlphaNumerical:Char(6).Char(5).Char(2).Number(3).<br>Is unique in Fundsquare Database.||Has to be unique<br>7th char = "".""<br>13th char = "".""<br>16th char = "".""<br>&<br>Last 3 char = 442<br>OR<br>14th&15th=SP||
|-
|'''Sub-fund Information'''||22||Sub-Fund RFI ID (CRS)||Conditional cf Definition||Indicates the Social Securities Identification number at the sub-fund level.<br>This field is mandatory for CRS reporting.||Codification||String char (20or22)||Number(11)-Number(13)||The 9th character is a letter followed by 8 numbers.<br>The CSSF code should be retrieved in the last part of the ID (Ex: MATRICULE+F00000145).<br>With a maximum of 8 characters after the letter.||
|-
|'''Sub-fund Information'''||23||Sub-Fund Creation Date||No||Indicates the date on which the sub-fund is created/activated||Date||Date char (10)||Date format: dd/MM/yyyy||If date > current date OR If no date = inactivated = anticipated creation (AC).<br>If date ≤ current date = activated = available for documents notification and dissemination (ACT).<br>Ensure that the date is not greater then creation date of the fund.||
|-
|'''Sub-fund Information'''||24||Sub-Fund End Date||No||Indicates the ending date of the sub-fund's activity (closing/liquidation date)||Date||Date char (10)||Date format: dd/MM/yyyy||If Date ≤ current date = inactivated = not available for documents notification and dissemination.<br>available 1 year for reporting.||
|-
|'''Sub-fund Information'''||25||Sub-Fund Base Currency||Yes||Indicates the ISO3-currency code for the base accounting currency of the sub-fund||Currency||String char (3)||Currency ISO-3||RMB should be CNH or CNY||
|-
|'''Sub-fund Information'''||26||NAV per Share Frequency||Yes||Notifies the frequency of the net asset per share calculation.<br>It must be the same for all the share classes that are included in one sub-fund.||Frequency||String char (4)||List of values:<br>YEAR = Annual<br>TWYR = Twice a year<br>TOWK = Twice a week<br>TOMN = Every two months<br>TWMN = Twice a month<br>WEEK = Weekly<br>DAIL = Daily<br>MNTH = Monthly<br>TRIE = Every four months<br>SEMI = Every six months<br>QURT = Every three months<br>MLTD = Multi-daily<br>NIMN = Every nine months<br>||N/A||
|-
|'''Sub-fund Information'''||27||Sub-Fund Sleeping Indicator||No||Indicates whether the sub-fund is sleeping or not||Indicator||String char (3)||Boolean:YES/NO||N/A||
|-
|'''Share-class Information'''||28||Share Class Name||Yes||Indicates the legal name of the share class||Label||String char (100)||Is unique at this level (upper/lower case letters)||N/A||
|-
|'''Share-class Information'''||29||Client Share Class Name||No||Indicates a client's name of the share class||Label||String char (100)||Is unique in Fundsquare's database (upper/lower case letters.<br>Combined with fund & sub-fund labels.||Name available on Fundsquare website and client whitelabelling||
|-
|'''Share-class Information'''||30||Share Class National Competent Authority Code||No||Indicates the codification used by the fund's domicile authority on share class level||Codification||String char (20)||Is unique in Fundsquare's database||The CSSF codes from 1 to 9 have to be written with two characters (01-02-03...)||
|-
|'''Share-class Information'''||31||Share Class Administration Code||No||Indicates the central administration's instrument code at the share class level (AC internal code).<br>Share class ID used in the client's proprietary system (for NAV).||Codification||String char (20)||Is unique at this level||N/A||
|-
|'''Share-class Information'''||32||Share Class ISIN Code||Conditional cf Definition||Indicates the ISIN code of the share class.<br>This field is mandatory for Ucits-funds if the share class is activated (creation date)||Codification||String char (12)||Is unique in Fundsquare's database||Ensure that the first two letters match to the fund juridiction country.<br>For Ucits Funds:If empty the share class status is inactivated (INA)||
|-
|'''Share-class Information'''||33||Share-Class Ticker Bloomberg Code||No||Indicates the Instrument’s Bloomberg Ticker (code)||Codification||String char (20)||Is unique in Fundsquare's database||N/A||
|-
|'''Share-class Information'''||34||Share Class Creation Date||No||Indicates the date on which the share class is created/activated||Date||Date char (10)||Date format: dd/MM/yyyy||If date > current date OR If no date = inactivated & anticipated creation (AC).<br>If date ≤ current date = activated = available for documents notification and dissemination (ACT).<br>If UCITS and NO ISIN CODE then no creation date should be available.<br>Ensure that the date is not greater than creation date of the sub-fund||
|-
|'''Share-class Information'''||35||Share Class End Date||No||Indicates the ending date of the share class activity (closing/liquidation date)||Date||Date char (10)||Date format: dd/MM/yyyy||If Date ≤ current date = inactivated = not available for documents notification and dissemination.<br>Available 1 year for reporting.||
|-
|'''Share-class Information'''||36||Share Class Reference Currency||Yes||Indicates the ISO3-currency code for the reference currency of the share class||Currency||String char (3)||Currency ISO-3||N/A||
|-
|'''Share-class Information'''||37||Share Class Dividend Payment Frequency||No||Indicates the frequency at which the dividends are paid||Frequency||String char (4)||List of values:<br>YEAR = Annual<br>TWYR = Twice a year<br>TOWK = Twice a week<br>TOMN = Every two months<br>TWMN = Twice a month<br>WEEK = Weekly<br>DAIL = Daily<br>MNTH = Monthly<br>TRIE = Every four months<br>SEMI = Every six months<br>QURT = Every three months<br>MLTD = Multi-daily<br>NIMN = Every nine months<br>||Yearly by default||
|-
|'''Share-class Information'''||38||Share Class Result Allocation||Yes||Indicates whether income payment is distributed or capitalized or other||Indicator||String char (3)||List of values:<br>ACC<br>INC<br>CAD=Acc&Inc<br>OTH||N/A||
|-
|'''Share-class Information'''||39||Share Class Sleeping Indicator||No||Indicates whether the share is sleeping or not||Indicator||String char (3)||Boolean:YES/NO||If blank, then N by default||
|-
|'''Share-class Information'''||40||Institutional Investor Type||No||Indicates whether the instrument is reserved for institutional investors or not||Indicator||String char (3)||Boolean:YES/NO||If blank, then N by default||
|-
|'''Share-class Information'''||41||Initial Launch Price||No||Indicates the initial launch price of the instrument||Number||Numeric char (20)||Separator: "." => "0.0000"||N/A||
|-
|'''Share-class Information'''||42||Initial Launch Price Currency||No||Indicates the ISO-3 currency code of the initial launch price of the instrument||Currency||String char (3)||Currency ISO-3||The initial launch price currency has to be the same as the share class reference currency||
|-
|'''Share-class Information'''||43||Initial Launch Price Date||No||Indicates the date of the initial launch price||Date||Date char (10)||Date format: dd/MM/yyyy||Should not be greater then the creation date of the share class||
|-
|}
</div>

[[Category: FAQ e-file]]

E-file Static Data Management

2026-05-28T08:25:59Z

Cso: /* How to complete the FDF */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

__TOC__

= FAQ =

<span class="mw-customtoggle-q0" style="font-weight:bold;line-height:2.5;">Your module is greyed out?</span>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-q0">
::To get access, please ask your e-file local administrator to [[E-file Administration#How_do_I_assign_groups_and_profiles_to_users|make you member]] of the '''''Fundamental Data Form''''' group.

::[[File:SDM GreyedOut.png|alt=Registration and distribution matrix is greyed out.|To have access : '''''Distribution matrix ''''' and '''''Registration matrix ''''' groups ]]
</div>

<span class="mw-customtoggle-q1" style="font-weight:bold;line-height:2.5;">Why is the CSSF code missing?</span>
<div class="mw-collapsible mw-collapsed" id="mw-customcollapsible-q1">
::Filing codes have to be provided to our static data team so that they can be mapped to the correct ISIN/Instrument. The provision of the CSSF codes lies with our customers or their service providers (e.g. the fund's central administration)
</div>

<div style="text-align: center; width:100%;border-style: double none none none;"> </div>

=Select template=

[[File:5After SelectTemplate.png|700 px]]

[[File:AfterPoint1.png|20 px]] Click on the arrow highlighted in yellow in the top left hand corner of the page to open the drop-down list to select the TEMPLATE [[File:AfterPoint2.png|20 px]]

=Filter functions=
[[File:2AfterSDMExport.png|1000 px]]

[[File:AfterPoint1.png|20 px]] Click on the '''FILTER''' button [[File:AfterSDMFilter.png|30 px]] on the right side of the screen. A toolbar (highlighted in yellow) opens where you can narrow your search options by specifying the [[File:AfterPoint2.png|20 px]] STATUS of the instrument (e.g. active and public).

[[File:AfterPoint3.png|20 px]] Click inside the toolbar highlighted in yellow. A drop-down list '''DATA FILTERS''' pops up where you can narrow your search criteria by selecting e.g. ISIN, CSSF CODE. Enter your ISIN, CSSF CODE in the dedicated search field (3a, 3b) and

[[File:AfterPoint4.png|20 px]] Press the '''SEARCH''' button or press ENTER.

[[File:AfterPoint5.png|20 px]] Press the '''RESET''' button [[File:AfterSDMResetButton.png|20 px]] to clear all fields and reset filters.

[[File:AfterPoint6.png|20 px]] If the '''SELECT ALL''' box is checked, all instruments of all management companies that are linked in our database to the ACTOR are selected.

[[File:AfterPoint7.png|20 px]] Display options

:: If the '''SHOW ONLY SELECTED''' button is green, only the selected instruments are displayed on the screen.

:: If the '''EXPAND ALL''' button is green, the whole tree structure (fund, sub-fund, share class) of the instrument is displayed.

:: If the '''SPREAD SELECTION TO RELATED INSTRUMENTS''' button is green and you select an instrument at fund level, the whole tree structure of the fund will be automatically selected.

[[File:AfterPoint8.png|20 px]] If you press the '''EXPORT''' button, all selected instruments with checked boxes will be exported in the file.

=Export a file=
[[File:2AfterSDMEportFDF.png|700 px]]

[[File:AfterPoint1.png|20 px]] Press the '''EXPORT''' button

[[File:AfterPoint2.png|20 px]] The red notification indicates that one file is being generated or has been generated.

[[File:AfterPoint3.png|20 px]] Once that file is generated, a window pops up indicating '''The following report has been generated'''.

[[File:AfterPoint4.png|20 px]] Open the file that is available at the bottom of the page.

=Import a file=
[[File:3AfterSDMImport.png|800 px]]

[[File:AfterPoint1.png|20 px]] Press the '''FLOW-CHART''' button [[File:AfterSDMFlowChartButton.png|20 px]]. A small window pops up with two options: '''EXPORT''' and '''IMPORT'''. Select '''IMPORT.'''

[[File:AfterPoint2.png|20 px]] You have two options to upload your file:

:: - either you '''BROWSE''' your file system and select the file you want to upload

:: - or you '''DRAG & DROP your file directly onto the appropriate area [[File:AfterSDMDragDrop.png|20 px]]

:: <span style="color:white; background:DarkTurquoise"> '''NEW:''' </span> Please be informed that new <u>features</u> have been added to the new e-file version of the '''Static Data Management''' application. You have now the possibility to upload <u>several</u> files at the same time.

:: In our example we uploaded two files:

:: ABC_2019_12_17_FDF.xlsx (cf. '''2b''')

:: XYZ_2019_12_17_FDF.xlsx (cf. '''2a''')

[[File:AfterPoint3.png|20 px]] You have two options to add the mandatory parameters '''TEMPLATE''', '''ACTION''', '''COMMENT'''

::- either you select each parameter for each single file

::- or you set all parameters via the SET BULK PARAMETERS [[File:AfterPoint4.png|20 px]] funcionality cf. screen below

'''VERY IMPORTANT INFORMATION'''

Please ensure that you always follow the Fundsquare naming convention of the templates. The respective acronyms at the end of the file name are '''mandatory''' and they have to be preceded by an underscore. Please note that only '''.xlsx''' files are allowed to be imported.

FDF template: nnnnnnn_'''FDF'''.xlsx

MIFID template: nnnnnnn_'''MIFID'''.xlsx

PRIIPS template: nnnnnnn_'''PRIIPS'''.xlsx

==Set bulk parameters==
[[File:2AfterSDMBulkImport.png|600 px]]

[[File:AfterPoint1.png|20 px]] If you check the '''SELECT ALL''' box and complete all mandatory fields in this sections, all mandatory fields of the two files we imported, will be populated automatically with the same parameters.

[[File:AfterPoint2.png|20 px]] Press the '''VALIDATE IMPORT PARAMETERS''' button.

==Import confirmation==
[[File:NewSDM.png|600 px]]

[[File:AfterPoint1.png|20 px]] Press the IMPORT DATA button.

[[File:AfterPoint2.png|20 px]] A window pops up indicating '''Your documents were received'''

[[File:AfterPoint3.png|20 px]] At the top of the screen a toast notification shows up confirming that the import was successful.

[[File:AfterPoint4.png|20 px]] The red notification with number 2 inside, shows you that 2 files have been imported.

[[File:AfterPoint5.png|20 px]] If you click on the exclamation mark, a drop down list with all imported files opens.

Furthermore, please be informed, that you will receive a '''notification''' by email with detailed information on your files you imported.

[[File:ConfirmationMail.png|border|400 px]]

==How to use FSQ IDs in the Fundamental Data Form (FDF)==

In the following, we would like to explain you, how to use <u>Fundsquare's internal identification numbers</u> of instruments which are available in column 45, 46, 47 of the Fundamental Data Form (Id Fund, Id Sub-Fund, Id Share-Class).

(1) <u>Modification of an instrument</u>

If you modify an instrument '''<u>the three FSQ Id must not be changed under no circomstances</u>.'''

For example, if you want to change a sub-fund name, the new name must be reported in the appropriate cell. '''DO NOT CHANGE''' the FSQ IDs.

[[File:1 FSQ ID FDF.png|border|300 px]]

(2) <u>Closure of an instrument</u>

If you want to close an instrument, the appropriate cells in column 13, 24, 34 have to be completed with the closure date. '''DO NOT CHANGE''' the FSQ IDs.

[[File:1 FSQ ID FDF.png|border|300 px]]

Please note, that if you close a fund, the whole fund tree structure will be closed in our database.

If you close a single sub-fund, all share classes belonging to this sub-fund will be closed in our database.

(3) <u>Creation of a new fund</u>

To create a new fund, select a standard FDF extraction with the same fund structure (SICAV i.e..) and the same Law directive (P110 i.e..) as the new one you will have to create.

'''<u>IMPORTANT</u>''': you '''must <u>REMOVE</u> all ID instruments''' from the cells in columns 45, 46 and 47 as they refer to a <u>already existing instrument</u>', and the risk is you replace the existing instrument.

[[File:2 FSQ ID FDF.png|border|300 px]]

(4) <u>Creation of a new sub-fund</u>

For example, if you want to add 3 sub-funds to an existing fund, you have to add 3 lines below the fund in the extraction template and complete the appropriate cells.

'''<u>REMOVE</u> Id Sub-Fund and Id Share-Class''', but '''<u>DO NOT CHANGE</u> the Id Fund'''.

[[File:3 FSQ ID FDF.png|border|300 px]]

(5) <u>Creation of a new share-classes</u>

For example, if you want to add 5 share-classes to an existing sub-fund, you have to add 5 lines to the existing sub-fund structure in the extraction template. Complete all cells accordingly.

'''<u>REMOVE</u> Id Share-Class''', but '''<u>DO NOT CHANGE</u> the Id Fund and Id Sub-Fund'''.

[[File:4 FSQ ID FDF.png|border|300 px]]

(6) Exception in column 28

In the case of share class creations, we would like to ask you, for internal processing reasons only, to delete all "Capitalisation" and "Distribution" words that appear in column 28.

[[File:SDMException.png|400 px]]

== How to complete the FDF ==
In due course, we will provide further information on this section.<br>
<div style="text-align: center;">
{| border="1" cellspacing="5" cellpadding="10"
|-
|'''Main Category'''||'''Column Number'''||'''Field Label'''||'''Mandatory Field'''||'''Definition'''||'''Type of Data'''||'''Field Format'''||'''Format Constraints'''||'''Business Rule'''||
|-
|'''Third-Party Information'''||1||Promoter||No||Indicates the name of the Initiator/Sponsor of the fund including the country||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||2||Management Company||Yes||Indicates the name of the Management Company of the fund including the country||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||3||Investment Company||Conditional cf Definition||Indicates the name of the Investment Company of the fund including the country.<br>This field is mandatory if the fund is self-managed and no management company has been provided||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||4||Fund Administration||Yes||Indicates the name of the Administrator of the fund including the country.||Company Name||String char (100)||N/A||N/A||
|-
|'''Third-Party Information'''||5||Transfer Agent||Conditional cf Definition||Indicates the name of the Transfer Agent of the fund including the country.<br>This field is mandatory for the Order Routing Data||Company Name||String char (100)||N/A||N/A||
|-
|'''Fund Information'''||6||Fund Name||Yes||Indicates the legal name of the fund||Label||String char (100)||Is unique in Fundsquare's database (upper/lower case letters)||N/A||
|-
|'''Fund Information'''||7||Fund National Competent Authority Code||No||Indicates the codification used by the fund's domicile authority on fund level||Codification||String char (20)||Is unique in Fundsquare's database||N/A||
|-
|'''Fund Information'''||8||Fund Administration Code||No||Indicates the central administration's instrument code at the fund level (AC internal code)||Codification||String char (20)||Is unique at this level||N/A||
|-
|'''Fund Information'''||9||Fund GIIN Code||Conditional cf Definition||Indicates the Global Intermediary Identification Number of the instrument at the fund level<br>This field is mandatory for FATCA reporting||Codification||String char (20)||Alphanumerical: Char(6).Char(5).Char(2).Number(3).<br>Is unique in Fundsquare's database.||Has to be unique if not SP (Sponsor).<br>7th char = "."<br>13th char = "."<br>16th char = "."<br>&<br>Last 3 char = 442<br>or<br>14th&15th = SP
|-
|'''Fund Information'''||10||Fund RFI ID (CRS)||Conditional cf Definition||Indicates the Social Security Identification number at the fund level. Mandatory for CRS reporting||Codification||String char (20 or 22)||Number(11) - Number(13)||9th char is a letter followed by 8 "0"||
|-
|'''Fund Information'''||11||Type of EU Directive||Yes||Indicates whether the fund is an UCITS-fund or an AIF-fund according to european directives||Indicator||String char (6)||List of values:<br>UCITS<br>AIF<br>OTHER||N/A||
|-
|'''Fund Information'''||12||Umbrella Fund||No||Indicates whether the fund is an umbrella or not||Indicator||String char (3)||Boolean: YES/NO||N/A||
|-
|'''Fund Information'''||13||Fund Creation Date||Yes||Indicates the date on which the fund is created/activated||Date||Date char (10)||Date format: dd/MM/yyyy||If date > current date OR If no date = inactivated = anticipated creation (AC).<br>If date ≤ current date = activated = available for documents notification and dissemination (ACT).||
|-
|'''Fund Information'''||14||Fund End Date||No||Indicates the ending date of the fund's activity (closing/liquidation date)||Date||Date char (10)||Date format: dd/MM/yyyy||If Date ≤ current date = inactivated = not available for documents notification and dissemination.<br>available 1 year for reporting.||
|-
|'''Fund Information'''||15||Fund Jurisdiction Country||Yes||Indicates the country where the fund is domiciled||Legal||String char (2)||Code ISO2||The two first characters must be the same as the two first letters included in ISIN code.<br>For example: LU, GB, IE, etc.||
|-
|'''Fund Information'''||16||Fund Legal Form||Yes||Indicates the legal form of the fund||Legal||String char (4)||List of values:<br>"FCP" = FCP: Common fund<br>"SICV" = SICAV: Investment company with variable capital<br>"SICF" = SICAF: Investment company with fixed capital<br>"SICR" = SICAR: Investment company in risk capital<br>"OT" = OT: Securitisation entities<br>"SCA" = SCA: Partnership limited by shares<br>"SCS" = SCS: Limited partnership<br>"SCSp" = SCSp: Special partnership<br>"SA" = SA: public limited liability company<br>"OTH" = OTHER: Other fund||Linked/compatible with "Fund Legal Status"||
|-
|'''Fund Information'''||17||Fund Legal Status ||Yes||Indicates the legal status of the fund||Legal||String char (4)||List of values:<br>"SIF" = SIF<br>"NLUX" = Non-LU-domiciled<br>"PA04" = Law 14 june 2004<br>"PA05" = Law 22 march 2004<br>"PA06"=Law 10 august 1915<br> "PA07"=Law 23 july 2016<br> "PA08"=Law 12 July 2013<br> "PA09"=Law 15 December 2019<br> "PA10"=Law 16 july 2019<br>"P110" = Part I 2010 law<br>"P210" = Part II 2010 law<br>"RAIF" = RAIF||Linked/compatible with "Fund Legal Form"||
|-
|'''Sub-fund Information'''||18||Sub-Fund Name||Yes||Indicates the legal name of the sub-fund||Label||String char (100)||Is unique in Fundsquare's database at this level (upper/lower case letters)||N/A||
|-
|'''Sub-fund Information'''||19||Sub-Fund National Competent Authority Code||No||Indicates the codification used by the fund's domicile authority at the sub-fund level||Codification||String char (20)||Is unique in Fundsquare's database||N/A||
|-
|'''Sub-fund Information'''||20||Sub-Fund Administration Code||No||Indicates the central administration's instrument code at the sub-fund level (AC internal code)||Codification||String char (20)||Is unique at this level||N/A||
|-
|'''Sub-fund Information'''||21||Sub-Fund GIIN Code||Conditional cf Definition||Indicates the Global Intermediary Identification Number for the instrument at the fund level.<br>This field is mandatory for FATCA Reporting.||Codification||String char (20)||AlphaNumerical:Char(6).Char(5).Char(2).Number(3).<br>Is unique in Fundsquare Database.||Has to be unique<br>7th char = "".""<br>13th char = "".""<br>16th char = "".""<br>&<br>Last 3 char = 442<br>OR<br>14th&15th=SP||
|-
|'''Sub-fund Information'''||22||Sub-Fund RFI ID (CRS)||Conditional cf Definition||Indicates the Social Securities Identification number at the sub-fund level.<br>This field is mandatory for CRS reporting.||Codification||String char (20or22)||Number(11)-Number(13)||The 9th character is a letter followed by 8 numbers.<br>The CSSF code should be retrieved in the last part of the ID (Ex: MATRICULE+F00000145).<br>With a maximum of 8 characters after the letter.||
|-
|'''Sub-fund Information'''||23||Sub-Fund Creation Date||No||Indicates the date on which the sub-fund is created/activated||Date||Date char (10)||Date format: dd/MM/yyyy||If date > current date OR If no date = inactivated = anticipated creation (AC).<br>If date ≤ current date = activated = available for documents notification and dissemination (ACT).<br>Ensure that the date is not greater then creation date of the fund.||
|-
|'''Sub-fund Information'''||24||Sub-Fund End Date||No||Indicates the ending date of the sub-fund's activity (closing/liquidation date)||Date||Date char (10)||Date format: dd/MM/yyyy||If Date ≤ current date = inactivated = not available for documents notification and dissemination.<br>available 1 year for reporting.||
|-
|'''Sub-fund Information'''||25||Sub-Fund Base Currency||Yes||Indicates the ISO3-currency code for the base accounting currency of the sub-fund||Currency||String char (3)||Currency ISO-3||RMB should be CNH or CNY||
|-
|'''Sub-fund Information'''||26||NAV per Share Frequency||Yes||Notifies the frequency of the net asset per share calculation.<br>It must be the same for all the share classes that are included in one sub-fund.||Frequency||String char (4)||List of values:<br>YEAR = Annual<br>TWYR = Twice a year<br>TOWK = Twice a week<br>TOMN = Every two months<br>TWMN = Twice a month<br>WEEK = Weekly<br>DAIL = Daily<br>MNTH = Monthly<br>TRIE = Every four months<br>SEMI = Every six months<br>QURT = Every three months<br>MLTD = Multi-daily<br>NIMN = Every nine months<br>||N/A||
|-
|'''Sub-fund Information'''||27||Sub-Fund Sleeping Indicator||No||Indicates whether the sub-fund is sleeping or not||Indicator||String char (3)||Boolean:YES/NO||N/A||
|-
|'''Share-class Information'''||28||Share Class Name||Yes||Indicates the legal name of the share class||Label||String char (100)||Is unique at this level (upper/lower case letters)||N/A||
|-
|'''Share-class Information'''||29||Client Share Class Name||No||Indicates a client's name of the share class||Label||String char (100)||Is unique in Fundsquare's database (upper/lower case letters.<br>Combined with fund & sub-fund labels.||Name available on Fundsquare website and client whitelabelling||
|-
|'''Share-class Information'''||30||Share Class National Competent Authority Code||No||Indicates the codification used by the fund's domicile authority on share class level||Codification||String char (20)||Is unique in Fundsquare's database||The CSSF codes from 1 to 9 have to be written with two characters (01-02-03...)||
|-
|'''Share-class Information'''||31||Share Class Administration Code||No||Indicates the central administration's instrument code at the share class level (AC internal code).<br>Share class ID used in the client's proprietary system (for NAV).||Codification||String char (20)||Is unique at this level||N/A||
|-
|'''Share-class Information'''||32||Share Class ISIN Code||Conditional cf Definition||Indicates the ISIN code of the share class.<br>This field is mandatory for Ucits-funds if the share class is activated (creation date)||Codification||String char (12)||Is unique in Fundsquare's database||Ensure that the first two letters match to the fund juridiction country.<br>For Ucits Funds:If empty the share class status is inactivated (INA)||
|-
|'''Share-class Information'''||33||Share-Class Ticker Bloomberg Code||No||Indicates the Instrument’s Bloomberg Ticker (code)||Codification||String char (20)||Is unique in Fundsquare's database||N/A||
|-
|'''Share-class Information'''||34||Share Class Creation Date||No||Indicates the date on which the share class is created/activated||Date||Date char (10)||Date format: dd/MM/yyyy||If date > current date OR If no date = inactivated & anticipated creation (AC).<br>If date ≤ current date = activated = available for documents notification and dissemination (ACT).<br>If UCITS and NO ISIN CODE then no creation date should be available.<br>Ensure that the date is not greater than creation date of the sub-fund||
|-
|'''Share-class Information'''||35||Share Class End Date||No||Indicates the ending date of the share class activity (closing/liquidation date)||Date||Date char (10)||Date format: dd/MM/yyyy||If Date ≤ current date = inactivated = not available for documents notification and dissemination.<br>Available 1 year for reporting.||
|-
|'''Share-class Information'''||36||Share Class Reference Currency||Yes||Indicates the ISO3-currency code for the reference currency of the share class||Currency||String char (3)||Currency ISO-3||N/A||
|-
|'''Share-class Information'''||37||Share Class Dividend Payment Frequency||No||Indicates the frequency at which the dividends are paid||Frequency||String char (4)||List of values:<br>YEAR = Annual<br>TWYR = Twice a year<br>TOWK = Twice a week<br>TOMN = Every two months<br>TWMN = Twice a month<br>WEEK = Weekly<br>DAIL = Daily<br>MNTH = Monthly<br>TRIE = Every four months<br>SEMI = Every six months<br>QURT = Every three months<br>MLTD = Multi-daily<br>NIMN = Every nine months<br>||Yearly by default||
|-
|'''Share-class Information'''||38||Share Class Result Allocation||Yes||Indicates whether income payment is distributed or capitalized or other||Indicator||String char (3)||List of values:<br>ACC<br>INC<br>CAD=Acc&Inc<br>OTH||N/A||
|-
|'''Share-class Information'''||39||Share Class Sleeping Indicator||No||Indicates whether the share is sleeping or not||Indicator||String char (3)||Boolean:YES/NO||If blank, then N by default||
|-
|'''Share-class Information'''||40||Institutional Investor Type||No||Indicates whether the instrument is reserved for institutional investors or not||Indicator||String char (3)||Boolean:YES/NO||If blank, then N by default||
|-
|'''Share-class Information'''||41||Initial Launch Price||No||Indicates the initial launch price of the instrument||Number||Numeric char (20)||Separator: "." => "0.0000"||N/A||
|-
|'''Share-class Information'''||42||Initial Launch Price Currency||No||Indicates the ISO-3 currency code of the initial launch price of the instrument||Currency||String char (3)||Currency ISO-3||The initial launch price currency has to be the same as the share class reference currency||
|-
|'''Share-class Information'''||43||Initial Launch Price Date||No||Indicates the date of the initial launch price||Date||Date char (10)||Date format: dd/MM/yyyy||Should not be greater then the creation date of the share class||
|-
|}
</div>

= FDF template =
<br>
In case you don't have yet the access to the module, to save your time, [[E-file Static Data Management#FAQ | Module is greyed out]] <br>
Please find [[Media:FDF.xlsx | here an empty FDF file]] you can complete and sent it back to us?

[[Category: FAQ e-file]]

E-file Administration

2026-05-21T09:58:55Z

Cso: /* Groups' management */

__NOTOC__
= e-file FAQ - Administrator's section =
<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

[[File:Administration module icon (Figure 2).png|300px]]

== Knowing the interface ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_am_I_allowed_to_do_as_an_administrator></span>
<div style="font-weight:bold;line-height:2.5;">What am I allowed to do as an administrator ?</div>
<div class="mw-collapsible-content">

The '''Administration module''' opens. Tabs are available in the '''e-file administrator''' module: (Figure 3).

[[File:Users, Groups and Certificates (Figure 3).png|900px]]

{|
|+
!'''Users tab'''
!'''Groups tab'''
!'''Certificates tab'''
!'''Sending service tab'''
!'''S3 keys tab'''
|-
|
*[[#How_can_I_create_a_new_e-file_user|Create a new user]]

*[[#Managing_permission_on_user's_account|Assign groups to a user]]

*[[#Explore_the_interface's_items|Force password change]]

*[[#Explore_the_interface's_items|Lock/ unlock user]]

*[[#Explore_the_interface's_items|Delete user]]
|
*[[#Groups'_management|User management at group level]]

* Add users to a group

* Assign a group to users

* Manage user profiles at group level
|
* [[#How_do_I_order_a_LUXTRUST_certificate|Order a new '''Luxtrust certificate''']]

* [[#How_do_I_order_a_LUXTRUST_certificate|Renew your Luxtrust certificate]]

* [[#How_do_I_activate_my_LUXTRUST_certificate_into_e-file|Activate Luxtrust certificate]]
|
:''Sending service user's management :''

* [[#What_about_the_Sending_Service_account|Assign groups to the '''Sending Service user''']]

* [[#What_about_the_Sending_Service_account|Subscribe the Sending Service user to '''alerts''']]
:''Sending service user's management - V2 :''
* [[Sending_Service_java-less_version|Sending service java-less version]]
|
* [[#S3_system|'''S3''' key management]]
|}
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Explore_the_interface's_items></span>
<div style="font-weight:bold;line-height:2.5;">Explore the interface's items</div>
<div class="mw-collapsible-content">

:<u>'''Explanations'''</u>

<imagemap>
File:AdminInterface.png|center|1200px|alt=clickable image : admin interface
rect 83 11 944 69 [[#hereExplainAction| This is the tabs' menu ]]
rect 1812 154 1686 93 [[#hereExplainAction| Click to create a new user's account ]]
rect 237 234 28 168 [[#hereExplainAction| The vertical menu can be reduce ]]
rect 238 281 31 239 [[#hereExplainAction| Here you can set who will receive some e-mail notifications in relation with the administration ]]
rect 256 186 1286 232 [[#hereExplainAction| You can filter the list on a group's members or a profile]]
rect 406 345 450 375 [[#hereExplainAction| The crown indicates an administrator]]
rect 793 285 878 300 [[#hereExplainAction| By hovering over their headers, text columns can be sorted]]
rect 1618 281 1748 332 [[#hereExplainAction| Each line allow its actions among : * Edit, * Force password, * Lock/Unlock, * Delete]]
rect 1618 337 1647 369 [[#hereExplainAction| Edit the user details or group permissions]]
rect 1652 337 1681 369 [[#hereExplainAction| Force password change : an email is sent to the user for him to reset]]
rect 1687 337 1711 369 [[#hereExplainAction| Lock or Unlock the account. The icon is greyed out for new users.]]
rect 1716 337 1743 369 [[#hereExplainAction| Delete the account. You can not delete administrators, ask us.]]
desc none
</imagemap>
</div>
</div>

== Accounts' management ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How many users can I create ?</div>
<div class="mw-collapsible-content">
:You can create as many as users' accounts you need. It is free of charge.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_create_a_new_e-file_user></span>
<div style="font-weight:bold;line-height:2.5;">How can I create a new e-file user ?</div>
<div class="mw-collapsible-content">

:Enter the administration module [[File:SDjl_8.png|150px]], you should be on the 'users' tab.
:Click the '''Create a user''' button [[File:Create_a_user_button_(Figure_5).png|150px]]

:The '''Create a user''' window pops up. Complete the form as shown in the figure below and click the '''Create''' button.

<imagemap>
File:4CreateUser.png|center|900px|alt=clickable image : create user form
rect 1081 737 41 282 [[#hereCreatUser|All fields are mandatory]]
rect 991 835 42 770 [[#hereCreatUser|You must choose a first group and a user's profile ]]
rect 475 856 637 914 [[#hereCreatUser|Click here to validate]]
rect 1363 993 1216 939 [[#hereCreatUser|Click here to cancel]]
circle 1355 58 34 [[#hereCreatUser|Click here to cancel]]
desc none
</imagemap>

:<span style="color: #C00000">'''Important note : You do not have to create a password for the user, an automatic mail will be sent to the new user to activate his account and create a password</span>'''

:The '''Create a user''' window closes and you return automatically to the '''Users List''' screen.

:At the same time a '''confirmation''' window pops up on the top of the screen indicating that the user creation was successful.

:[[File:User creation was successful (Figure 7).png|800px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_an_existing_account's_e-mail></span>
<div style="font-weight:bold;line-height:2.5;">How can I change an existing account's e-mail ?</div>
<div class="mw-collapsible-content">

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon.

[[File:SDjl_8.png|300px]]

<u>'''Step 2</u>:'''

The '''Users List''' screen opens. Click the Edit button on the line of the account to be changed.

[[File:AdminModuleChangeEmail.png|border]]

<u>'''Step 3</u>:'''
Click the detail tab, then Edit button

[[File:AdminModuleChangeEmail2.png|border|400px]]

<u>'''Step 4</u>:'''
Change the e-mail then click Validate button

[[File:AdminModuleChangeEmail3.png|border|400px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_about_the_Sending_Service_account></span>
<div style="font-weight:bold;line-height:2.5;">What about the Sending Service account ?</div>
<div class="mw-collapsible-content">

As an administrator, you can manage the permission for the sending service account too.
See more information upon the [[Sending_Service_home|sending service]]

<imagemap>
File:SDPermission.png|center|800px|alt=clickable image on SD permission
rect 385 1 615 68 [[#hereSDPerm| Click the sending service tab ]]
rect 7 172 192 211 [[#hereSDPerm| In the vertical menu, choose the proper version of your sending service ]]
rect 1370 310 1421 374 [[#hereSDPerm| On the matching line, click the edit icon ]]
rect 1378 442 1473 384 [[#hereSDPerm| A panel opens from the right, click the edit button ]]
rect 248 545 1231 778 [[#hereSDPerm| You can add or delete a group, the profile is always 'Service Déposant', subscribe to receive the authorities' feedbacks. ]]
desc none
</imagemap>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Managing_permission_on_user's_account></span>
<div style="font-weight:bold;line-height:2.5;">Managing permission on user's account </div>
<div class="mw-collapsible-content">

See: [[#How_do_I_assign_groups_and_profiles_to_users|How do I assign groups and profiles to users ?]]
</div>
</div>

== Groups' management ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_an_e-file_group></span>
<div style="font-weight:bold;line-height:2.5;">What is an e-file group ?</div>
<div class="mw-collapsible-content">

In e-file, a group allows you to manage permissions for similar reports in terms of type, circulars, costs or technical constraints.

Instead of managing groups for a user, the '''Groups''' tab allows you to manage users for a given group.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Which_group_do_I_need></span>
<div style="font-weight:bold;line-height:2.5;">Which group do I need ?</div>
<div class="mw-collapsible-content">

<div style="height:500px; width:auto; overflow-y:scroll">

{| class="wikitable filterable mw-collapsible sortable"
|+ <span style="white-space:nowrap">Which group for my report ?</span>
|- <div style="font-weight:bold; vertical-align:top; position:sticky;top:-1px;z-index:10">
! style= "background-color:#52BBBD; color:#FFF" | Concerned companies
! style= "background-color:#52BBBD; color:#FFF" | Report<br /> naming convention
! style= "background-color:#52BBBD; color:#FFF" | Details
! style= "background-color:#52BBBD; color:#FFF" | Authority
! style= "background-color:#FF7F27; color:#FFF" | e-file Group
! style= "background-color:#52BBBD; color:#FFF" | Sending way

</div>

|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| NOTREP
| Notification procedures to be followed by a UCITS governed by Luxembourg law wishing to market its units in another Member State of the European Union
| CSSF
| (-) Gestion documentaire<br /> (-) Dashboard<br /> (-) Matrice d'enregistrement et de distribution
| S3
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Monthly financial information for guaranteed funds
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| -
| Yearly financial information
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Interventions on the futures and options markets
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0103
| Monthly statistical balance sheet for money market funds (MMF)
| BCL
| Station Finesti
| KS
|-
|Investment Funds
|S0404
|Country of Marketing
|BCL
|Station Finesti
|KS
|-
|Investment Funds
|S0220
|Quarterly Financial Information
|BCL
|Station Finesti
|KS
|- style="vertical-align:bottom;"
| Investment Funds
| TPTOBS
| Monthly Security by security reporting for investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| SIF:<br /> (-) Prospectus (PC)<br /> (-) Offering document (DE)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| SIF Law 2007:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report SIF (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (PM)<br /> SICAR:<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Auditor report<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| Auditor report<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI:<br /> (-) Prospectus (PC)<br /> (-) Simplified prospectus (PS)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting (AIF Manager)
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| AnaCredit:<br /> Collection of granular credit and credit risk data
| BCL
| Reporting Anacredit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0218-L
| Quarterly statistical balance sheet of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S0219-L
| Information on valuation effects on the balance sheet of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0403-L
| Annual Premiums, claims and commissions of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| TPTASS
| Monthly Security by security reporting of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SHSGRP
| «SHS-Group» report:<br /> Statistics on holdings of securities by reporting banking groups
| BCL
| SHS reporting
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0001
| Daily deposit
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0101
| Monthly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0104
| Adjustments due to valuation effects|
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0105
| Information on interest rates in EUR
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0108
| Information on securititation<br /> transactions launched<br /> by credit institutions
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0109
| Information on CNY (renmibi) operations
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0205-L
| Quarterly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0205-N
| Quarterly statistical balance sheet<br /> of credit institutions -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0208
| Real estate loans for<br /> Lxuembourg buildings
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0209-L
| Staff report -<br /> Luxembourg entity
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0209-N
| Staff report -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0302
| Non balance sheet information
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit Report on AML/CTF
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Circ. 18/697 annexe1
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Annual Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Annual report consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| AC Member List
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Compliance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Governance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Internal Audit Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| ICAAP
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ICAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Branch or Specific Participation
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Long Form Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Reconciliation LuxGAAP FINREP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Management Letter Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit report on rules of conduct
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Management Letter
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Head quarter annual report
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Risk Control Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Report on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Recovery Plan
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Results Distribution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Single Customer View
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Table on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Financial Institutions - Common Reporting Standard (CRS)
| CRS
| Automatic exchange of<br /> financial account information<br /> on a global level
| ACD
| Reporting CRS
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Quarterly reporting on the<br /> financial health of the branches<br /> parent entities
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Residential credit deposits
| CSSF
| Enquêtes
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DCOR
| style="vertical-align:bottom;" | Reporting Entity<br /> B: Credit institution
| style="vertical-align:bottom;" | CSSF
| Enquetes
| style="vertical-align:bottom;" | S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DCOR
| Reporting Entity<br /> P: PFS
| CSSF
| Enquetes
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Residential real estate market
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Stress test in order to assess<br /> the interest rate risk<br /> arising from non-trading<br /> book activities
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0101
| Customer transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0110
| Stock taking of payment accounts in bank money
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01100
| Payment services provided by e-money institutions and payment institutions without the provision of payment accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0111
| OTC cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01110
| Payment initiation services (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01110-F
| Payment initiation services (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0112
| Transactions via telecommunication, digital or IT device
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0113
| Credits to the accounts by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0114
| Debits from the account by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0102
| Interbank transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0120
| Customer Credit transfers sent (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0120-F
| Customer Credit transfers sent (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01200
| Stock of issued payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01201
| Stock of distributed payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0121
| Customer credit transfers received
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01210
| Stock of terminals by terminal type
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01220
| Stock of accounts (except e-money accounts)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01221
| Stock of e-money accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01222
| Stock of accessed accounts - account information services (AIS)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01230
| Number of customers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0103
| Domiciliations
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130
| Direct debits - reporting as creditor's PSP (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01300-F
| Losses due to fraud per liability bearer
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130-F
| Direct debits - reporting as creditor's PSP (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0131
| Direct debits - reporting as debtor's PSP
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0104
| Inventory cards / terminals
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0140
| SEPA R-transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0141
| Interbank payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0142
| Intermediated payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0105
| Card transactiosn (Issuing part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0150
| Card transactions with cards issued by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0150-F
| Card transactions with cards issued by resident PSPs (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0151
| Electronic card transactions with cards issued by resident PSPs, split by Merchant Category Codes (MCC)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0152
| Card transactions acquired by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0152F
| Card transactions acquired by resident PSPs (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0153
| Fundings and withdrawals related to prepaid cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0106
| Card transactiosn (Acquiring part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0160
| Cheques and money remittances (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0160-F
| Cheques and money remittances (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0107
| Cheques and money orders
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0170
| Over-the-counter (OTC) cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0108
| Electronic money scheme
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0180
| Book entries
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0109
| Card based e-money schemes
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0190
| Fundings and withdrawals in e-money (except prepaid cards)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0191
| E-money transfers (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0191-F
| E-money transfers (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Fonds de garantie<br /> des dépôts Luxembourg<br /> (FGDL)
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Identification of third-party<br /> funds held and incorporated in the balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Capital adequacy of<br /> payment institutions
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Profit and loss accoount
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Identification of third-party<br /> funds held and incorporated<br /> in the balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Statement of<br /> authorised reinvestments
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Capital adequacy of<br /> electronic money institutions
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Profit and loss account
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Analysis of shareholdings
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Institutions - Foreign Account Tax Compliance Act (FATCA)
| FATCA
| Foreign Account Tax Compliance Act Reporting
| ACD
| Groupe FATCA
| KS
|-
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| (-) Letter of explanation (LE)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Annual report of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| FRCREP
| Information on participating interest<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| FRCREP
| Information on staff costs and taxes<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| LCRDAX
| CSSF
| Rapport FINREP
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Companies
| S0216
| Quarterly statistical balance of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| S0217
| Transactions of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Key Investor Information Document<br /> (-) O: OPC Law 2010 and Loi 2007<br /> (-) K: SICAR<br /> (-) V: non-reglem.
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Long Form reports (UCI Law 2010)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| SGOREP
| (-) SG 1A: Financial situation<br /> (-) SG 1B: Profit and loss account<br /> (-) SG 1C: Table relating to other activities<br /> (-) SG 2: Other activities<br /> (-) SG: Personnel Table relating to staff
| CSSF
| Rapport Société de Gestion
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007<br /> (-) K: SICAR
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| Articles of Incorporation of UCITS<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Management Regulations of UCITS<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom;"
| MiFID II / MiFIR
| TAFREP
| Article 26 of Regulation<br /> No 600/2014:<br /> Obligation to report transactions<br /> (Markets in financial instruments => MiFIR)
| CSSF
| Report TAF-MIFID
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Other reporting CSSF BCL
| OTHREP
| Other reporting
| CSSF
| Reporting OTHER (CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| BOP101
| Balance of payments reporting
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BOP102
| Cross-border payments<br /> executed for the account<br /> of the resident counterparts
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| PSFREP
| Reporting population:<br /> (-) Investment firms<br /> (-) Specialised PFS<br /> (-) Support PFS
| CSSF
| Rapport PSF
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| N01 (Comp); N02 (Comp); N03 (Comp);<br /> N04 (Comp); N05 (Réviseur); N06( Réviseur);<br /> N07 (Comp); N08 (Comp); N09 (Comp); N10 (Comp); N11 (Comp); N12 (Réviseur);<br /> N13<br /> (Comp);<br /> N14<br /> 'Comp)
| Rapports narratifs
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CSDREP
| Reporting CSDR:<br /> Introduction of quarterly internalised settlement reporting requirements<br /> pursuant to Article 9(1) of EU Regulation No 909/2014 (CSDR)
| CSSF
| Reporting CSDR-9
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BNNNN
| List of head offices, agencies,<br /> branches and representative offices
| CSSF
| Reporting EDIFACT
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Institutions for Occupational Retirement Provision
| SUFREP
| Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019
| CSSF
| Reporting IORP
| KS
|- style="vertical-align:bottom;"
| Money Market Funds (MMF)
| MMFREP
| • According to Article 37 of Regulation (EU) 2017/1131, the manager of a MMF must report information to the competent authority (CSSF) of the MMF, at least on a quarterly basis or - for MMF with assets under management of less than Eur 100 million - on at least an annual basis.<br /> • The first quarterly report should be sent to the competent authority of the MMF no later than 30 days after the end of Q1 2020.
| CSSF
| Money market fund reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0112-L
| Indirect withdrawal and remittance of banknotes denominated in EUR through an intermediary
| BCL
| Reporting S1.12
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| TPTIBS
| Monthly security by security reporting of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| U11
| Monthly financial information UCITS and UCI
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBBL
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBBN
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBHN
| Security by security report–<br /> Off-balance sheet data–<br /> Non-resident
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBHR
| Security by security report–<br /> Off-balance sheet data–<br /> Resident customers
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| S3
|- style="vertical-align:bottom;"
| Investment Funds
| SIC
| Financial information to be submitted by investment companies in risk capital (SICARs)
| CSSF
| Reporting SICAR
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI Law 2010:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (MP)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S01; S02; S03; S04; S05;<br /> S06 (Réviseur); S07; S08;<br /> S09; S10; S11; S12; S13;<br /> S14; S15; S16; S17; S18;<br /> S19; S20; S23
| XBRL reports Solvency II
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| S0214
| Quarterly statistical balance
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Securitisation Vehicles
| S0215
| Transactions and write-offs/write-downs on securitised loans
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| TPTTBS
| Security by security reporting
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| UCIAR
| Reporting Entity<br /> A: Alternative Investment fund manager (AIFM)
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| UCIAR
| Reporting Entity<br /> B: Credit institution
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| UCIAR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| UCIAR
| Reporting Entity<br /> S: Management company
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| UCIAR
| Reporting Entity<br /> (-) P: PFS<br /> (-) I: Support PFS
| CSSF
| (-) UCIAR reporting
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Other reporting CSSF BCL
| OTXREP
| Various correspondence
| BCL
| Reporting OTHER (BCL)
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SPJ
| Notification and execution of court orders
| SPJ
| Perquisitions électroniques
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI)(FR)<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CFEREP
| ALMXXX
| CSSF
| Rapport COREP
| S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Long Form Report
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Management Letter
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0106
| Monthly statistical balance sheet for non-money market funds (non-MMF)
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| S0213
| Quarterly statistical balance sheet for non-MMF investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| CED
| Etat de situation relatif aux contrats en déshérence
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| CPR
| Compte rendu
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ESP
| Enquête spécifique
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| ETR
| Etat trimestriel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| FIR
| Fiche de renseignement
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| PDA
| Rapport PDAL (Procédure de Dissolution Administrative sans Liquidation)
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RAC
| Rapport actuariel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RDC
| Rapport distinct complémentaire du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RDI
| Rapport distinct du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RGO
| Rapport de gouvernance
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RLB
| Rapport LBCFT
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RRE
| Rapports sur le traitement des réclamations
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RSE
| Rapport distinct Solvabilité 2 de l'entreprise
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RSO
| Rapport distinct Solvabilité 2 du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ICS
| Yearly Survey on Covered Investment claims (SIIL)
| CSSF
| Enquête
| S3
|- style="vertical-align:bottom;"
| Insurance Corporations
| ROI<br /> DIN
| DORA Register of Information<br /> DORA Incident Reporting
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DPAAIF
| self-assessment <br /> questionnaire PDAOFI
| CSSF
| PDAOFI reporting
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| (-) ALM corep_alm_con.xsd<br /> corep_alm_ind.xsd corep_alm.xsd<br /> (-) LCRDA corep_lcr_da_con.xsd<br /> corep_lcr_da_ind.xsd corep_lcr_da.xsd<br /> (-) IRRBB irrbb.xsd
| CSSF
| Rapport COREP
| S3
|}

</div>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How can I get a missing group ?</div>
<div class="mw-collapsible-content">
If you think that the group you need is not available in your list, please [[How_to_contact_us|ask us]] to check and/or add it.
</div>
</div>
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_manage_users_at_group_level></span>
<div style="font-weight:bold;line-height:2.5;">How can I manage users at group level ?</div>
<div class="mw-collapsible-content">

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon (Figure 21).

[[File:SDjl_8.png|400px]]

(Figure 21)

<u>'''Example'''</u>:

If you want to know the users to which the group '''Group FATCA''' has been assigned or if you want to add a new user to the group, please follow the instructions below.

<u>'''Step 1</u>:'''

Press the '''Groups''' button. The '''Groups list''' page opens. All groups assigned to your company are shown here (Figure 22).

[[File:3GroupList.png|800px]]

(Figure 22)

<u>'''Step 2</u>:'''

Click the '''Edit groups''' icon [[File:EditGroupSD.png|20px]] in order to view all the users assigned to '''Groupe FATCA''' group (Figure 23).

[[File:2EditGroup.png|800px]]

(Figure 23)

The '''Group detail''' page opens. Here you can find detailed information on the '''Group FATCA''' (e.g. Status date, number of inactive users, number of locked users) (Figure 24).

[[File:GroupDetailPage.png|500px]]

(Figure 24)

<u>'''Step 3</u>:'''

Press the '''Users''' button (Figure 25)

[[File:GroupDetailUsers.png|500px]]

(Figure 25)

The Group detail / Users page opens. All users assigned to the '''Group FATCA''' are listed here(Figure 26).

[[File:GroupUsrsList2.png|600px]]

(Figure 26)

<u>'''Step 4</u>:'''

Press the '''Edit Users''' button [[File:EditUserButton.png|100px]] (Figure 27)

[[File:EditUsersGroup.png|600px]]

(Figure 27)

The '''Users''' page opens in '''Edit mode''' (Figure 28)

[[File:UsersEditGroup.png|600px]]

(Figure 28)

The following actions can be done here:

1. '''ADD A USER'''. Select the user and his profile you want to add.

2. Change the '''Profile''' of the user

3. Delete the '''User'''

4. Once you have made your changes, press the VALDATE CHANGES button [[File:ValidateChanges.png|100px]]

The '''Users''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a confirmation window pops up on the top of the screen indicating that the assignment was successful (Figure 29).

[[File:AssignmentsSaved.png|800px]]

(Figure 29)
-------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_assign_groups_and_profiles_to_users></span>
<div style="font-weight:bold;line-height:2.5;">How do I assign groups and profiles to users ?</div>
<div class="mw-collapsible-content">

<u>Example</u>:

If a user has to send '''FATCA reportings''' to the authority, the e-file administrator must assign the <u>group</u> '''Rapport FATCA''' and the <u>profile</u> '''Manager''' to the user.

<u>'''Step 1</u>:'''

Open the '''User management''' screen in the '''Users''' tab and click the '''Edit''' [[File:EditGroupSD.png|20px]] icon of the user to whom you want assign [[E-file_Administration#Which_group_do_I_need|'''groups''']] and a specific [[E-file_Administration#User_profiles |'''profile''']] (Figure 11).

[[File:A specific profile (Figure 11).png|900px]]

(Figure 11)

<u>'''Step 2</u>:'''

The '''User details''' screen opens. Click the '''Groups''' button (Figure 12).

[[File:2AddGroup.png|500px]]

(Figure 12)

<u>'''Step 3</u>:'''
The '''User details / Groups''' screen opens. Click the '''Edit button''' (Figure 13).

[[File:2GroupDetails.png|500px]]

(Figure 13)

<u>'''Step 4</u>:'''

The '''User details / Groups''' screen opens in '''Edit''' mode (Figure 14).

Click the '''ADD A GROUP''' button [[File:AddGroup.png|100px]], select the [[E-file_Administration#Which_group_do_I_need|'''groups''']] and '''profile''' you want to assign and click the '''Validate''' button.

[[File:4Add group.png|800px]]

(Figure 14)

The '''User details / Groups''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a '''confirmation''' window pops up on the top of the screen indicating that the group assignment was successfully saved (Figure 15).

[[File:AssignmentsSaved.png|800px]]

(Figure 15)

Please be informed that you can find detailed information on all groups on our Wikipage [[E-file_Administration#Which_group_do_I_need|''''e-file Administrator FAQ'''']]; column <u>e-file user account: "groupe"</u>.

=== User profiles ===

====Administrator (EN)/ Administrateur (FR)====

The Administrator profile allows the e-file administrator to order and activate LuxTrust certificate(s), manage user accounts, groups, user profiles, lock and un lock user account.

==== Guest (EN) */ Visiteur (FR) * ====

* The Guest can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Guest cannot submit reports or documents via e-file.

====Manager (EN)/ Responsable (FR)====

* The Manager can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Manager can submit reports linked to his group(s) via e-file.

====Operator (EN) */ Opérateur (FR) * ====

* The Operator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* The Operator submit reports linked to his group(s) to validation by a Validator.

====Validator (EN) */ Valideur (FR) * ====

* The Validator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* He validates or rejects reports awaiting for validation linked to his group(s).

(*) Available depending the group
---------------
</div>
</div>

== Security's management ==

<span id=keystore_system></span>
=== * keystore system, Luxtrust certificate, SSL security ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_order_a_LUXTRUST_certificate></span>
<span id=LUXTRUST_certificate_purchase_order></span>
<div style="font-weight:bold;line-height:2.5;">How do I order a LUXTRUST certificate ?</div>
<div class="mw-collapsible-content">

You can find a video tutorial <b> <u>[[Media:E-fileLuxtrustCertificateProcess.mp4| here]]</u> which summarises the below process</b>

Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>
Prior your first filing you will have to order and activate a Luxtrust certificate.<br>
The only certificate authorised for the file encryption by the reporting entity are '''SSL certificates''' from the certification authority [https://www.easyssl.lu/?product=e-file LUXTRUST].

Please check the [[Transmission_Module#System_requirements|system requirements]] to run the e-file applications.

=== Key and Certificate Request generation ===

Please be informed that during the next steps <span style="background:yellow"> <u>two files</u> </span> will be generated:

<span style="background:yellow"> 1- </span> the keystore file '''keystore.ks''' containing your new keys

<span style="background:yellow"> 2- </span> the certificate request file '''Certificate Request.csr''' containing a copy of your new keys. <u>This file must be uploaded on LUXTRUST's website during your purchase order</u> .

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate purchase order and its activation have to be performed on the same computer workstation.</span>'''

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 30).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 30)

<u>'''Step 2</u>:'''

Click the '''Certificates ''' button (Figure 31)

[[File:AdminModule_2.png|border|500px]]

(Figure 31)

<u>'''Step 3</u>:'''

The '''Certificates Management''' screen opens. Click the '''CERTIFICATE REQUEST - ACTIVATION MENU''' link (Figure 32).

[[File:AdminModule_3.png|border|1000px]]

(Figure 32)

<u>Result</u>: A new screen opens displaying GENERATE CERTIFICATE KEYS - BEFORE LUXTRUST WEBSITE ORDER on the left side of the page

<u>'''Step 4</u>:'''

Configure your keystore (Figure 33).

[[File:Configure_your_keystore.png|border|1000px]]<br>

(Figure 33)

a. <u>Select the keystore import method</u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, select '''Create a new keystore file''' option and indicate a keystore name.

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, you '''<u>must</u> '''select your '''curent keystore file''' by using the ''browse file'' or ''drag & drop'' feature to import it.

<span style="color: #C00000">'''Important note : in both case, the new keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

- File name: choose your keystore name, for example '''keystore.ks'''

- File type : .ks

b. <u>Password </u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, you have to define a brand-new '''keystore password'''.
A confirmation is required

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, e.g. its validity date expired, you <u>must</u> use the '''keystore password''' that had been created when you ordered the certificate for the '''very first time'''.

<span style="color: #C00000">''' Important note : the keystore password has to be shared with all e-file users who have to transmit encrypted documents or decrypt feedback files received from the supervisory authorities. </span>.

<span style="color: #C00000">''' Important note : if you loose your keystore password, you will have to generate a new key and order a new certificate. </span>

c. <u>Certificate request name (.csr)</u>

You have to define a name for the technical certificate request file required by Luxtrust, for example '''CertificateRequest.csr'''

<span style="color: #C00000">'''Important note : the certificate request will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

- File name: '''CertificateRequest.csr'''

- File type : .csr

<u>'''Step 5</u>:'''

Verify the Company information. (Figure 34) :

[[File:Company_information.png|border|1300px]]

(Figure 34)

The related fields will be pre-filled in with information we currently have in our system. Feel free to make changes if necessary.

<u>'''Step 6</u>:'''

Click the '''Generate keys''' button.

A window will pop up inviting you to download the Keystore file and Certificate Signing Request (Figure 35).

[[File:Keystore CSR download window.PNG|border|500px]]

(Figure 35)

You must click on each of the Download buttons in order to activate the OK button.<br>
Then click OK to clear the message window.

<span style="color: #C00000">'''Both keystore and certificate request files will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name as follows: <br>The name of the previous keystore + a timestamp displayed as yyyymm + onhold. <br><br>Example: oldname : MyKeystore.ks / new name : MyKeystore_202212_onhold.ks''' </span>

<span style="color: #C00000">'''Important note : we advise you to back up the keystore.ks and CertificateRequest files.''' </span>

=== Finalize your LUXTRUST purchase order ===

<span style="color: #C00000">'''Before to start order in the Luxtrust website make sure that you have process the previous part (Key and Certificate Request generation). </span>

-Open the [https://www.easyssl.lu/?product=e-file LUXTRUST easy SSL e-file website].

-Browse to SSL Certificate section and click the E-FILE icon
[[File:Sans titre.png|50px]]

-Choose the period of validity of your certificate and click the ORDER E-FILE button.

-If you do not have a LUXTRUST easy SSL e-file account you have to get registered.

-Once registered, complete the whole order form, upload your '''CertificateRequest<span style="background:yellow">.csr </span>''' file, accept the TERMS AND CONDITIONS and click the PLACE ORDER button.

-Shortly afterwards, you will receive an e-mail from LUXTRUST confirming your purchase order.

-Please follow all instructions provided in the e-mail and its PDF attachment (Send signed PDF by post with all required documents to the address indicated inside, process the payment etc.)

----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_activate_my_LUXTRUST_certificate_into_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How do I activate (integrate) my LUXTRUST certificate into e-file ?</div>
<div class="mw-collapsible-content">

The certificate file will be sent to the e-mail address you provided in your purchase order.

The extension of this file will be .txt, in order to prevent your firewall from blocking the attached file.

<u>'''Step 1</u>:'''

<span style="color: #C00000">'''Important note: save the file .txt on your computer workstation and <u>replace</u> the .txt extension by <span style="background:yellow">.cer </span> </span>

Double-click the <span style="background:yellow"> .cer </span> file. You should be able to see your certificate as shown below (Figure 36):

[[File:Certificate visual example.png|alt=Certificate example|377x377px]]

(Figure 36)

<u>'''Step 2</u>:'''

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate ordering and its activation have to be performed on the same computer workstation.</span>'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 37).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 37)

<u>'''Step 3</u>:'''

Click the '''Certificates ''' button (Figure 38).

[[File:AdminModule2.png|border|500px]]

(Figure 38)

<u>'''Step 4</u>:'''

Click the '''CERTIFICATE ACTIVATION – AFTER RECEPTION OF LUXTRUST CERTIFICATE''' link (Figure 40).

[[File:Certificate_activation.png|border|1500px]]

(Figure 40)

<u>'''Step 5</u>:'''

Configure your keystore (Figure 41).

[[File:Certificate_activation_steps.png | 1000px]]

(Figure 41)

a. <u>Select the Group you need to use (by default Principal)</u>

b. <u>Import the keystore that was generated at the same time as the Certificate Signing Request</u>
(from previous step )

c. <u>Enter the keystore password</u>

d. <u>Import the certificate you received from Luxtrust </u>

<u>'''Step 6</u>:'''

Click the '''ACTIVATE CERTIFICATE''' button.

A window will pop up and inform you that the activation has been done successfully.

Your keystore.ks is now updated. It contains your activated LUXTRUST certificate and your encryption keys.

[[File:AdminModule_15.png | 300px]]

'''Note''': The display and the position of the pop up may differ regarding the Web browser you are using

<span style="color: #C00000">'''Important note : the updated keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name : the name of the previous keystore + a timestamp displayed as yyyymm + completed.<br>Example: previous name : MyKeystore.ks / new name : MyKeystore_202212_completed.ks''' </span>

<span style="color: #C00000">'''Important note : if you loose your keystore and/or its password,you will have to generate a new encryption key and order a new certificate. </span>.
-------------

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_must_I_do_with_the_keystore></span>
<div style="font-weight:bold;line-height:2.5;">What must I do with the keystore ?</div>
<div class="mw-collapsible-content">

===Manual file transmission===

The activated keystore, containing your LUXTRUST certificate and your encryption keys must now be provided to the workstations of each e-file user.

<u>'''Step 1</u>:'''

Open the Transmission module

[[File:Icon1.png | 300px]]

<u>'''Step 2</u>:'''

[[File:Keystore selection After(1).PNG| 600px]]

===Automatic file transmission===

In the case you are using the [[Sending_Service|Sending Service]] for automatic file transmission, the activated keystore.ks must be provided as well.
----------------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_register_my_LUXTRUST_certificate_with_the_CSSF></span>
<div style="font-weight:bold;line-height:2.5;">How can I register my LUXTRUST certificate with the CSSF ?</div>
<div class="mw-collapsible-content">

For some reportings, the LUXTRUST e-file SSL certificate used by the reporting entity must be registered with the CSSF, before sending any files, according to the registration procedure described in the '''[https://www.cssf.lu/wp-content/uploads/Naming-convention.pdf#page=8 CSSF 23/833, naming convention part.]'''

The LUXTRUST e-file SSL certificate must be registered with the CSSF for the below reportings:</br>
(list extracted from [https://www.cssf.lu/fr/transport-et-securisation/#specifications-techniques Transport et sécurisation via les canaux de transmission externes])

* COREP/FINREP reporting
* ESP – Special enquiries
* SIC – SICAR reporting
* PFS – Reporting PFS and support PFS
* EDP – Payment institutions reporting
* EME – Electronic money institution
* SGO – Management companies reporting
* OPC – Fund XML reporting (O1.2)
* DOC – Non-structured electronic documents (circ. 19/731)
* OTH – Other
* OCB – Other reportings for CSSF and BCL
* SUF – XBRL reportings for subfund-based structured products (IORP)
* O4.x – Edifact report

[[Media:How to declare your Luxtrust certificate to the CSSF.pdf|=> e-file User Guide: CSSF Certificate registration]]
----------------
</div>
</div>

=== * S3 system ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_is_the_S3_digital_key_management_in_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How is the S3 digital key management in e-file ?</div>
<div class="mw-collapsible-content">

The CSSF has updated its submission methods to allow AIFMs to file specific regulatory reports via the CSSF’s API from 2nd November.
Please note, this is not the deadline to make the change, it is the point at which the new method is available to use. <br>
FE Fundinfo are ready to support you through the transition.
Your current setup in e-file will remain in place and only minor one-off changes are required from you to ensure the continuation of your existing functionality on e-file and future proof the communication method for all reporting and filing with the CSSF going forward.
<br><br>

<u>'''Explanation in context of AIFMD reporting</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/7273286345756229380 November 21st webinar in English] and the [https://c2rv804.na1.hubspotlinks.com/Ctc/ZO+113/c2RV804/VWQ8Fx5Hw7JyVdSL7w2rxckBW20x2Jc566MpmN31NNCl5nXHsW7Y9pgv6lZ3kLW8mzYxT1ZSlmLW7yCpDW2jmg69W73tZTZ5yBySkW7jL_zN8my412W9hGQQt71RszSVkgkWT3FF-R2W1VryJ67bk_NmW1RKWr345DTFjV1PBRM2KwkQsW4P0bYq6h4FhzW2Y0TlL8jm7QlW6N2qBz9lFm9yW1bNKCy1qGVgGW7dJWkQ8TTtG5N3kH6ptzC816W33qG8b10K_BtW8gQSgN4g3h5TW9h3bp34KXCJHV_q02d6BgPGWW5xJSX81p0bg6W8jK_6G221K5qW3_hsX93mN9kwW2RyrBr7f39YJW8v09kD7Cw1nxW37qD826JSxdcW4Rc7yD85pl3PW109fZz4mxLcHW26Y0Y03k4GNWW8zPXjF1t6bspW78yjPn71W4ftW8-MxR372T_w5V13CVl6qstVRW21LWhW2dlqL_W2Xs3ZP6K5mZ2W1THZsw1FrpXLW54G4QN27qB0BW3yXpwm7rd3qwW23mB7r301kH7W19MCT85QW6wbW218pPC2z-WjCVQRHvT30nLTNW1qM-sk29_0TFd2XXgW04 related presentation]

[https://attendee.gotowebinar.com/recording/2231697877960308483 Webinaire en français]

<u>'''Explanation in context of UCITS Cross-Border notification</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/2670031382955110830 December 12th webinar in English] and the [https://445778.fs1.hubspotusercontent-na1.net/hubfs/445778/FE%20fundinfo%20presentations/FSQ%20channel%20change_Webinar%2012%20December.pdf related presentation]

This new system works via a bucket system.<br>
There is one bucket for each filing context (i.e. Cross-border notification, AIFMD)<br>
The CSSF imposes a technical size limit for filing per bucket on 30 rolling days.<br>
Should you encounter any issue, feel free to contact us directly [[How to contact us|'''Client Support & Operations Desk''']] we will liaise with the CSSF.<br>

<br>
The below is a step-by step guide to appoint FE Fundinfo as a delegate within the CSSF’s eDesk platform, the easiest path to allow us to maintain our services. <br>
Once the set-up is complete you can continue to use your familiar eFile interface and do not need to interact with eDesk as this will all be channelled within your existing workflows in eFile.
<br><br>
To perform the set-up in eFile you have two options:
<br>

* You as IT expert import the S3 keys on eFile

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide for eDesk IT Experts to connect CSSF’S eDesk to FE Fundinfo’s eFile system''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Your entity’s appointed IT Expert will need to log into the IT Management
area of eDesk ([https://edesk.apps.cssf.lu/edesk-itmgt/s3/accesses here]). This must be using the same LuxTrust Device and
account that the IT Expert role was assigned to. Please note, that these
steps can only be implemented from the appointed IT Expert account
|
|-
|
Step 2
|
Once logged in, go to the ‘S3 ACCESS DASHBOARD’ at the top of the page,
which will take you to a screen similar to the below
|
[[File:02-S3Dashboard.png|S3Dashboard|800px]]
|-
|
Step 3
|
Select ‘Create Access’
|
[[File:03-S3CreateAccess.png|S3CreateAccess|800px]]
|-
|
Step 4
|
This will provide you with an option to select a ‘scope’ which will be the
reporting type you have been appointed as IT Expert for and select create:
<br>
[[#Correspondance table|You can refer to our correspondance table]]
|
[[File:04-S3CreateScope.png|S3CreateScope|800px]]
|-
|
Step 5
|
This will create a line in the S3 access dashboard with the report type, the
status (this should show ‘Granted’) and the date of this creation.
<br>
Each report type generates 3 codes on eDesk, (the Bucket code, the Access
Key, and the Secret Key). To reveal these keys, click the magnifying glass
with a ‘+’ icon under the actions column (located on the far right of the
screen).
|
[[File:05-S3Granted.png|S3Granted|800px]]
|-
|
Step 6
|
This will reveal the information about the who the access has been granted to, when and what report it is for. It will also provide details of the unique codes specific to the entity, report type and individual.
|
[[File:06-S3Access.png|S3Access|800px]]
|-
|
Step 7
|
Once the Keys have been generated, keeping your connection to eDesk open, in another window, open your efile environment. Log in using the efile Admin account for your entity and open the ‘Keys Management’ tab.
|
[[File:07-efileMenu.png|efileMenu|800px]]
|-
|
Step 8
|
Select ‘Add Key’ on the far right of the screen
|
[[File:08-eFileAddKey.png|eFileAddKey|800px]]
|-
|
Step 9
|
A pop out will appear and provide you with several drop down lists to
complete. Under ‘Scope’ you should choose the report type that you are
providing the Keys for. In this instance AIFMD should be selected.
|
[[File:09-eFileScope.png|eFileScope|800px]]
|-
|
Step 10
|
Returning to eDesk, copy the Bucket code, the Access key and Secret key
and paste each of these into the applicable boxes on efile.
|[[File:10-BucketCopy.png|BucketCopy|800px]]
|-
|}

===Correspondance table===
'''Please find the correspondence table of e-file and e-Desk scopes'''<br>

{| class="sortable" border="1" cellspacing="2" cellpadding="1"
|- <div style="position:sticky;top:-1px;z-index:10">
! scope="col" | '''Label scope in e-file'''
! scope="col" | '''Label scope in e-Desk'''
! scope="col" | '''CSSF reference'''
! scope="col" | '''Deadline'''
</div>
|-
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/AIFM_Reporting_Technical_Guidance.pdf AIFM reporting -Technical guidance]
| style="vertical-align:middle; color:#202122;" | 30 June 2024
|-
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_guide_notifications_CBDF.pdf User guide notifications CBDF]
| style="vertical-align:middle; color:#202122;" | 2nd January 2024
|-
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/cssf22_811eng.pdf CSSF 22/811]
| style="vertical-align:middle; color:#202122;" | 30 June 2023
|-
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSSF_CPDI_2440eng.pdf CSSF-CPDI 24/40]
| style="vertical-align:middle; color:#202122;" | 15 May 2024
|-
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures - SFO
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Precontractual_Data_Collection_-_practical-guide.pdf SFDR precontractual data collection]
| style="vertical-align:middle; color:#202122;" | 31 October 2023
|-
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures - SFPER
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Data_Collection_-_practical-guide.pdf SFDR UCI Data Collection]
| style="vertical-align:middle; color:#202122;" | 31 January 2024
|-
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Bank_prudential_reporting.pdf Bank prudential reporting]
| style="vertical-align:middle; color:#202122;" | 1st September 2024

|-
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Regulatory-documents-and-reports.pdf User Guide for Regulatory Documents and Reports]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Key-Information-Document.pdf User Guide for Key Information Document]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_U1.1.pdf Guidelines on the U1.1 reporting]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_Yearly_Survey_on_Covered_Investment_Claims.pdf Guidelines for the Yearly Survey on Covered Investment claims (SIIL)]
| style="vertical-align:middle; color:#202122;" | 17th January 2025

|-
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_SAQ_DPAAIF.pdf Guidelines on the self-assessment questionnaire PDAOFI]
| style="vertical-align:middle; color:#202122;" | 31st March 2025

|-
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2025/03/upcoming-evolution-in-the-electronic-visa-stamp-procedure-for-the-prospectuses-of-ucits-part-ii-ucis-sicars-and-sifs/ Procedure change for visa "stamp" prospectuses]
| style="vertical-align:middle; color:#202122;" | 1st April 2025

|-
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSDR9_Handbook.pdf User Guide Internalised Settlement Reporting Under Article 9 OF CSDR]
| style="vertical-align:middle; color:#202122;" | 1st July 2025

|-
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/MMFR_Handbook.pdf MMF reporting Handbook]
| style="vertical-align:middle; color:#202122;" | 1st September 2025

|-
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2026/01/iorp-reporting-circular-cssf-19-726-new-edesk-procedure/ new IORP procedure]
| style="vertical-align:middle; color:#202122;" | 15th January 2026

|}
---------------
</div>
</div>
</br></br>

===Special cases===
'''For Key Information Document (KID PRIIPs/KID) and Regulatory Documents and Reports scopes'''<br>
Due to the way the CSSF has implemented the third-party delegation process we have adapted our S3 scope import system in order to enable
</br>
the possibility for a client who is a service provider to onboard multiple S3 keys for the same scope on different Asset Managers / Self-managed funds / Filing entity based on the FSQ referential
</br></br>
To do so after having selected Key Information Document (KID PRIIPs/KID) or Regulatory Documents and Reports scope.<br>
You have to use the dedicated radio button Asset Manager, Self-Managed funds or Filing Entity
<br>
The list is automatically refreshed to only display third-party without S3 key onboarded.<br>
In case of a Filing Entity, the name of the Third party linked to the eFile user will be pre-filed (and can't be changed)<br>
[[File:AssetManager-SelfManaged-FilingEntity.png|Asset Manager, Self-Manged fund or Filing Entity|400px]]

To help you identifying which key has already been imported on eFile a dedicated page has been added in the S3 Keys Management module <br>
This page lists the already imported key for scope(s) allowing delegation. <br>
The Bucket owner (entity that owns the S3 key) and the Provider (entity who uploaded the S3 key on eFile) are displayed.<br>
[[File:DelegationList.png|S3 Key list|800px]]

* Grant us with the IT expert role to perform such changes for you
To start the process please send us an email to '''[mailto:cso.desk@fundsquare.net cso.desk@fundsquare.net]''' with both '''name''' and '''CSSF identification number''' of the entity you want we become IT Expert

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide on how to assign FE Fundinfo as a CSSF IT Expert on eDesk''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Log into [https://edesk.apps.cssf.lu/ eDesk] with the Advanced User account using your LuxTrust Device and Password. Please note that these changes can only be implemented from the Advanced User account
|
|-
|
Step 2
|
Once logged in, go to the top right corner of the screen, click on your account user name, and select ‘Entity Management’
|
[[File:02-EntityManagement.png|EntityManagement|800px]]
|-
|
Step 3
|
Now select ‘Access Requests’ from the tabs at the top of the screen:
|
[[File:03-AccessRequest.png|AccessRequest|800px]]
|-
|
Step 4
|
As FEfundinfo will have made a request to connect from our Fundsquare account, you will see us on a list of users requests to connect with your entity. You will be able to identify our request as it will be with the LuxTrust SN: <span style="color: #C00000">100115278245548987357</span>
|
[[File:04-LuxtrustSN.png|LuxtrustSN|800px]]
|-
|
Step 5
|
Once you have identified the FE fundinfo request from our Fundsquare account, you can go to the far right of the screen and select ‘ACCEPT ACCESS’ or ‘REJECT ACCESS’. Remember to only
accept requests and provide access to users you are associated with. You will need to ‘ACCEPT ACCESS’ on our request:
|
[[File:05-AcceptAccess.png|AcceptAccess|800px]]
|-
|
Step 6
|
Once you have clicked accept, go to the ‘Specific roles within entity’ tab:
|
[[File:06-SpecificRole.png|SpecificRole|800px]]
|-
|
Step 7
|
Under the ‘Specific roles within entity’ tab, on the right of the screen, click the ‘Add’ button:
|
[[File:07-AddSpecificRole.png|AddSpecificRole|800px]]
|-
|
Step 8
|
You will now be able to click on the ‘User’ box and select a user within the list of approved users connected with your entity. One of these will be FE fundinfo’s Fundsquare account, select this option and the user details will populate automatically:
|
[[File:08-FSQUser.png|FSQUser|800px]]
|-
|
Step 9
|
Now you can select a role for that user, in this case you will need to select IT EXPERT for FE fundinfo in the drop down selection and click save on the top right to make the change
|
[[File:09-ITExpert.png|ITExpert|800px]]
|-
|
Step 10
|
You have now completed all you need to ensure continued use of efile and secure submission of your reports to the CSSF! FE fundinfo will do the rest and can now ensure that the changing transmission methods gradually introduced by the CSSF over the next 18 months are updated as needed without any impact on you
|
|-
|}
----------------
</div>
</div>

::== Onboarding workflow map ==
''You can click on the picture.''
<imagemap>
File:Wkf_S3_onboarding.png|center|1500px|alt=clickable image : form description| titre
rect 106 355 277 452 [[E-file_Administration#You_as_IT_Expert | You as IT Expert ]]
rect 776 541 947 630 [[E-file_Administration#FE_Fundinfo_as_IT_Expert |FE Fundinfo as IT Expert]]
rect 1024 376 1193 482 [https://edesk.apps.cssf.lu/edesk-dashboard/homepage?lng=en eDesk User Guide ]
rect 477 530 646 691 [https://www.cssf.lu/wp-content/uploads/Methods-of-transmitting-reports-via-S3-Application-Programming-Interface-Technical-guidance.pdf S3 transmitting method ]
desc none
</imagemap>
-----------
</div>
</div>

=== * general security questions ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_the_local_e-file_administrator></span>
<div style="font-weight:bold;line-height:2.5;">How can I change the local e-file administrator ?</div>
<div class="mw-collapsible-content">

Each e-file administrator account is linked to a single email at a time.

3 cases :
* You have access to the account
:then change the email of the administrator by using the <b>administration module</b> and update the administrator account's owner (name, firstname). The new administrator will just have to request a new password.
* You have access to the administrator's e-mail box
:you can use the "forgotten password" button on https://www.e-file.lu to change the password and get access.
* You do not have access to the administrator account nor to the email of this account
:then for security reason you will have to follow this specific procedure:

::Your request must be sent by email and paper mail.

::The paper can be replaced by a mail with a scan of the letterhead paper => Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com].

<u>'''The request must be submitted on letterhead of your company and signed by a legal representative with the following information'''</u>:
*Administrator's login adminXXX
*The current email address which is linked to the administrator
*The new email address to link to the administrator
*A brief explanation of the reason why you need to change it
*Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com]'''

Once Fundsquare has received and checked your request we will update your email and send you the procedure to update the password.

If you have further questions do not hesitate to contact our [[How to contact us|'''Client Support & Operations Desk''']].

-----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_the_e-file_password_policy></span>
<div style="font-weight:bold;line-height:2.5;">What is the e-file password policy ?</div>
<div class="mw-collapsible-content">

[[File:Password.png|300 px]]

(Figure 42)

The password you will have to provide must follow the rules below:

*At least one upper and one lower case letter
*At least one number
*At least one special character from this list: ! # $ % & ( ) * + , . /: ; < = > ? ^ _ @ { | } [ ] ~
*At least 8 characters and at most 20

<u> Please note that </u>:

The validity of your password is not limited in time.

Our system blocks the user after 3 incorrect attempts and it is the e-file administrator who has to unblock the account.

Passwords are encrypted in our database and we do not keep them. You may re-use them.
-----------
</div>
</div>

== Being informed ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_important_information></span>
<div style="font-weight:bold;line-height:2.5;">How can I get important information ?</div>
<div class="mw-collapsible-content">

As an administrator, you will received all significant information regarding e-file changes, maintenance or enhancement through the e-mail address set up onto your account.
You can also manage some alerts through e-file, see the notifications system.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_custom_notifications></span></span>
<div style="font-weight:bold;line-height:2.5;">How can I get custom notifications ?</div>
<div class="mw-collapsible-content">

Please be informed that you can receive alert by email triggered by specific events.

<u>Example</u> : Court orders sent by the Luxembourgish judicial police [http://www.cssf.lu/fileadmin/files/Lois_reglements/Circulaires/Hors_blanchiment_terrorisme/cssf13_566eng.pdf (=> CSSF - Circular 13/566)]

If you want to be notified by email each time the Luxembourgish judicial police sends you court orders, you have to follow the steps below.

<u>'''Step 1'''</u> : Connect to e-file with your user credentials : '''https://www.e-file.lu/e-file/'''

<u>'''Step 2'''</u> : Select Update my profile

[[File:Select Update my profile.png |200 px]]

<u>'''Step 3'''</u> : Verify that your email address registered in your e-file account is valid.

[[File:Your e-file account is valid.png |400 px]]

<u>IMPORTANT :</u> if your email address is not valid, please ask your [[Administration#e-file_administrator_functions_.28e-file_v1.29|'''e-file administrator''']] to replace it by a valid one.

<u>'''Step 4'''</u> : Select Customize your notifications.

[[File:Customize your notifications.png |200 px]]

<u>'''Step 5'''</u> : Select group.

[[File:Select group555.png |400 px]]

<u>'''Step 6'''</u> : Select the Alert type.

[[File:Notification.png |500 px]]

<u>IMPORTANT :</u>

A green window will pop-up stating that the update has been saved.

<u>'''Optional Step 7'''</u> : Receive only your alerts and not the group's ones.

Ticking also the group box, the sends from other users of the same reports group will be ignored.

[[File:Alerte Notification.png |500 px]]

[[Category: FAQ e-file]]

----------------------
</div>
</div>

ProductCoverage

2026-05-21T09:58:05Z

Cso:

__NOTOC__

<small>''Page's last update : {{REVISIONDAY2}}/{{REVISIONMONTH}}/{{REVISIONYEAR}}''</small>

You can find below the list of reports that can be managed through e-file.

<div style="height:500px; width:auto; overflow-y:scroll">

{| class="wikitable filterable mw-collapsible sortable"
|+ <span style="white-space:nowrap">Available reports</span>
|- <div style="font-weight:bold; vertical-align:top; position:sticky;top:-1px;z-index:10">
! style= "background-color:#52BBBD; color:#FFF" | Concerned companies
! style= "background-color:#52BBBD; color:#FFF" | Report<br /> naming convention
! style= "background-color:#52BBBD; color:#FFF" | Table
! style= "background-color:#52BBBD; color:#FFF" | Details
! style= "background-color:#52BBBD; color:#FFF" | Authority
! style= "background-color:#52BBBD; color:#FFF" | Sending way
! style= "background-color:#52BBBD; color:#FFF" | An e-file form exists
! style= "background-color:#52BBBD; color:#FFF" | Sending type in transmission module
! style= "background-color:#52BBBD; color:#FFF" | Example
</div>
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| NOTREP
| INI or<br /> UPD
| Notification procedures to be followed by a UCITS governed by Luxembourg law wishing to market its units in another Member State of the European Union
| CSSF
| S3
| yes
| -
|
|- style="vertical-align:bottom;"
| Investment Funds
| -
| O1.2
| Monthly financial information for guaranteed funds
| CSSF
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| -
| O4.1
| Yearly financial information
| CSSF
| KS
| yes
| -
|
|- style="vertical-align:bottom;"
| Investment Funds
| -
| O4.2
| Interventions on the futures and options markets
| CSSF
| KS
| yes
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0103
| S1.3
| Monthly statistical balance sheet for money market funds (MMF)
| BCL
| KS
| yes
| -
| S0103_L4_202302_B000000999_O009990099_20240619_001.xml
|- style="vertical-align:bottom;"
| Investment Funds
| TPTOBS
| TPTOBS
| Monthly Security by security reporting for investment funds
| BCL
| KS
| yes
| -
| TPTOBS_L3_202107_B000000009_O009990000_20240807_001.xml<br /> TPTOBS_L3_202107_P000000999_NAF99999999900000_20240603_001.xml<br />
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| (-) PC<br /> (-) DE<br /> (-) LE
| SIF:<br /> (-) Prospectus (PC)<br /> (-) Offering document (DE)<br /> (-) Letter of explanation (LE)
| CSSF
| KS
| no
| 08/371 FIS prospectus
| PROSP-O0000xxxx-2025-04-01-41c13c08-ef59-4183-870f-80d7a00c54e8.zip<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-DE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> PROSP-K0000xxxx-2025-04-01-41c13c08-ef59-4183-870f-80d7a00c54e8.zip<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-DE-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| (-) AR<br /> (-) SR<br /> (-) LE<br /> (-) RO<br /> (-) PM
| SIF Law 2007:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report SIF (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (PM)<br /> SICAR:<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| CSSF
| KS
| no
| 08/371 FIS report
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| RR<br /> HK
| Auditor report<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| KS
| no
| 08/371 report not in 08/371
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-HK-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (SICAR)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| RR<br /> HK
| Auditor report<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| KS
| no
| 08/371 report not in 08/371
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-HK-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (SICAR)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| (-) PC<br /> (-) PS<br /> (-) LE
| UCI:<br /> (-) Prospectus (PC)<br /> (-) Simplified prospectus (PS)<br /> (-) Letter of explanation (LE)
| CSSF
| KS
| no
| 08/371 UCI prospectus
| PROSP-O0000xxxx-2025-04-01-41c13c08-ef59-4183-870f-80d7a00c54e8.zip<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PS-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| AIF
| Alternative Investment Fund reporting
| CSSF
| S3
| yes
| AIF Reporting
| AIFREP-P12345678-A00000001-F00000000-00000000-MAN-20140129145000.zip<br /> AIFREP-P12345678-A00000111-V00002222-00003333-AIF-20140129145000.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| MAN
| Alternative Investment Fund reporting (AIF Manager)
| CSSF
| S3
| yes
| AIF Reporting
| AIFREP-P12345678-A00000001-F00000000-00000000-MAN-20140129145000.zip<br /> AIFREP-P12345678-A00000111-V00002222-00003333-AIF-20140129145000.zip
|- style="vertical-align:bottom;"
| Credit Institutions
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| AnaCredit:<br /> Collection of granular credit and credit risk data
| BCL
| KS
| no
| AnaCredit
| ANTREF_201801_LUB00999_20180205-001.xml<br /> ANTT1M_201801_LUB00999_LUB00999_20180205-001.xml<br /> ANTT2M_201801_LUB00999_LUB00999_20180205-001.xml<br /> ANTT2Q_201803_LUB00999_LUB00999_20180405-001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0218-L
| n/a
| Quarterly statistical balance sheet of insurance corporations – Luxembourg entity
| BCL
| KS
| yes
| BCL report for insurances
| S0218-L_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom;"
| Insurance Corporations
| S0219-L
| n/a
| Information on valuation effects on the balance sheet of insurance corporations
| BCL
| KS
| yes
| BCL report for insurances
| S0219-L_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0403-L
| n/a
| Annual Premiums, claims and commissions of insurance corporations – Luxembourg entity
| BCL
| KS
| yes
| BCL report for insurances
| S0403-L_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom;"
| Insurance Corporations
| TPTASS
| n/a
| Monthly Security by security reporting of insurance corporations
| BCL
| KS
| yes
| BCL report for insurances
| TPTASS_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SHSGRP
| SHSGRP
| «SHS-Group» report:<br /> Statistics on holdings of securities by reporting banking groups
| BCL
| KS
| no
| BCL SHS
| SHSGRP_201709_LUB00999_20171206_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0001
| S0.1
| Daily deposit
| BCL
| KS
| no
| BCL statistics
| S0001_L2_20130616_B000000999_B000000999_20130617_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0101
| S1.1
| Monthly statistical balance sheet
| BCL
| KS
| no
| BCL statistics
| S0101_L6_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0104
| S1.4
| Adjustments due to valuation effects|
| BCL
| KS
| yes
| BCL statistics
| S0104_L3_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0105
| S1.5
| Information on interest rates in EUR
| BCL
| KS
| yes
| BCL statistics
| S0105_L4_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0108
| S1.8
| Information on securititation<br /> transactions launched<br /> by credit institutions
| BCL
| KS
| yes
| BCL statistics
| S0108_L2_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0109
| S1.9
| Information on CNY (renmibi) operations
| BCL
| KS
| yes
| BCL statistics
| S0109_L0_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0205-L
| S2.5-L
| Quarterly statistical balance sheet
| BCL
| KS
| no
| BCL statistics
| S0205-L_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0205-N
| S2.5-N
| Quarterly statistical balance sheet<br /> of credit institutions -<br /> Luxembourg entity and its branches
| BCL
| KS
| no
| BCL statistics
| S0205-N_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0208
| S2.8
| Real estate loans for<br /> Lxuembourg buildings
| BCL
| KS
| no
| BCL statistics
| S0208_L0_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0209-L
| S2.9-L
| Staff report -<br /> Luxembourg entity
| BCL
| KS
| no
| BCL statistics
| S0209-L_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0209-N
| S2.9-N
| Staff report -<br /> Luxembourg entity and its branches
| BCL
| KS
| no
| BCL statistics
| S0209-N_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0302
| S3.2
| Non balance sheet information
| BCL
| KS
| no
| BCL statistics
| S0302_L0_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| COFREP
| SMRTLA<br /> CMRTLA<br /> MRTLAX<br /> CRESOL<br /> RESOLX<br /> SRESOL<br /> CFRXXX<br /> CIRXXX<br /> FMIRXX<br /> LDRXXX
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| KS
| no
| COREP report
| COFREP-B00000999-2014-03-CCOREP-00-L-N-S-CCOREP.xbrl<br /> COFREP-B00000999-2014-03-CCOREP-00-L-N-S.zip<br /> COFREP-B00000999-2019-12-SRESOL-00-L-N--.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| COFREP
| SMRTLA<br /> CMRTLA<br /> MRTLAX<br /> CRESOL<br /> RESOLX<br /> SRESOL<br /> CFRXXX<br /> CIRXXX<br /> FMIRXX<br /> LDRXXX
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| KS
| no
| COREP report
| COFREP-B00000999-2014-03-CCOREP-00-L-N-S-CCOREP.xbrl<br /> COFREP-B00000999-2014-03-CCOREP-00-L-N-S.zip<br /> COFREP-B00000999-2019-12-SRESOL-00-L-N--.zip
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AC
| Audit Report on AML/CTF
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-AC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AD
| Circ. 18/697 annexe1
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-AD-EN-0000.pdf
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| AR
| Annual Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-AR-EN-0000.pdf
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AS
| Annual report consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-AS-EN-0000.pdf
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | BD
| AC Member List
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-BD-EN-0000.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| CO
| Compliance Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-CO-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| GR
| Governance Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-GR-EN-0000.pdf<br />
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| IA
| Internal Audit Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-IA-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| IC
| ICAAP
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-IC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | ID
| ICAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-ID-EN-0000.pdf
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | IL
| ILAAP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-IL-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | IM
| ILAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-IM-EN-0000.pdf<br />
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LC
| Long Form Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-LC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LD
| Long Form Branch or Specific Participation
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-LD-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| LF
| Long Form Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-LF-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LG
| Reconciliation LuxGAAP FINREP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-LG-EN-0000.pdf<br />
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | MC
| Management Letter Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-MC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | MF
| Audit report on rules of conduct
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-MF-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| ML
| Management Letter
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-ML-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | MM
| Head quarter annual report
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-MM-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| RC
| Risk Control Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-RC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | RE
| Report on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-RE-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| RP
| Recovery Plan
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-RP-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | RR
| Results Distribution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-RR-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| SC
| Single Customer View
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-SC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | TR
| Table on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-TR-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Financial Institutions - Common Reporting Standard (CRS)
| CRS
| CRS
| Automatic exchange of<br /> financial account information<br /> on a global level
| ACD
| KS
| yes
| CRS report
| CRS_20170615114523_CRS701_2016_B_19751234567_01234567890M00000000_P.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| BRA
| Quarterly reporting on the<br /> financial health of the branches<br /> parent entities
| CSSF
| KS
| no
| CSSF enquiry
| ESPREP-B0999-2024-06-BRA.xlsx
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| DEP
| Residential credit deposits
| CSSF
| KS
| no
| CSSF enquiry
| ESPREP-B0999-2024-06-DEP.xlsx
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DCOR
| n/a
| Reporting Entity<br /> B: Credit institution
| CSSF
| S3
| no
| CSSF enquiry
| DCOR-ENNNNNNNN-YYYY-MM-DD_UUID.json
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DCOR
| n/a
| Reporting Entity<br /> P: PFS
| CSSF
| S3
| no
| CSSF enquiry
| DCOR-ENNNNNNNN-YYYY-MM-DD_UUID.json
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| RES
| Residential real estate market
| CSSF
| S3
| no
| CSSF enquiry
| ESPREP-B0999-2024-06-RES.xlsx
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| STT
| Stress test in order to assess<br /> the interest rate risk<br /> arising from non-trading<br /> book activities
| CSSF
| KS
| no
| CSSF enquiry
| ESPREP-B0999-2008-06-STT.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0101
| V1.1
| Customer transfers
| BCL
| KS
| no
| Data payment collection (CDP)
| V0101_L2_201601_W000000003_B000000999_20160201_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0110
| V1.10
| Stock taking of payment accounts in bank money
| BCL
| KS
| no
| Data payment collection (CDP)
| V0110_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01100
| V1.100
| Payment services provided by e-money institutions and payment institutions without the provision of payment accounts
| BCL
| KS
| no
| Data payment collection (CDP)
| V01100_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0111
| V1.11
| OTC cash transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0111_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01110
| V1.110
| Payment initiation services (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01110_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01110-F
| V1.110-F
| Payment initiation services (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01110-F_L0_202405_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0112
| V1.12
| Transactions via telecommunication, digital or IT device
| BCL
| KS
| no
| Data payment collection (CDP)
| V0112_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0113
| V1.13
| Credits to the accounts by simple book entry
| BCL
| KS
| no
| Data payment collection (CDP)
| V0113_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0114
| V1.14
| Debits from the account by simple book entry
| BCL
| KS
| no
| Data payment collection (CDP)
| V0114_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0102
| V1.2
| Interbank transfers
| BCL
| KS
| no
| Data payment collection (CDP)
| V0102_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0120
| V1.20
| Customer Credit transfers sent (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0120_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0120-F
| V120-F
| Customer Credit transfers sent (Fraud)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01200
| V1.200
| Stock of issued payment cards
| BCL
| KS
| no
| Data payment collection (CDP)
| V01200_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01201
| V1.201
| Stock of distributed payment cards
| BCL
| KS
| no
| Data payment collection (CDP)
| V01201_L0_202407_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0121
| V1.21
| Customer credit transfers received
| BCL
| KS
| no
| Data payment collection (CDP)
| V0121_L0_202201_B000000999_B000000999_20230421_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01210
| V1.210
| Stock of terminals by terminal type
| BCL
| KS
| no
| Data payment collection (CDP)
| V01210_L0_202407_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01220
| V1.220
| Stock of accounts (except e-money accounts)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01220_L0_202206_W000000099_W000000099_20240613_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01221
| V1.221
| Stock of e-money accounts
| BCL
| KS
| no
| Data payment collection (CDP)
| V01221_L0_202407_B000000999_B000000999_20240806_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01222
| V1.222
| Stock of accessed accounts - account information services (AIS)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01222_L0_202407_B000000999_B000000999_20240814_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01230
| V1.230
| Number of customers
| BCL
| KS
| no
| Data payment collection (CDP)
| V01230_L0_202407_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0103
| V1.3
| Domiciliations
| BCL
| KS
| no
| Data payment collection (CDP)
| V0130_L0_202407_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130
| V1.30
| Direct debits - reporting as creditor's PSP (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0103_L0_202407_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01300-F
| V1.300-F
| Losses due to fraud per liability bearer
| BCL
| KS
| no
| Data payment collection (CDP)
| V01300-F_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130-F
| V1.30-F
| Direct debits - reporting as creditor's PSP (fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0130-F_L0_202403_B000000999_B000000999_20240412_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0131
| V1.31
| Direct debits - reporting as debtor's PSP
| BCL
| KS
| no
| Data payment collection (CDP)
| V0131_L0_202407_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0104
| V1.4
| Inventory cards / terminals
| BCL
| KS
| no
| Data payment collection (CDP)
| V0104_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0140
| V1.40
| SEPA R-transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0140_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0141
| V1.41
| Interbank payment transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0141_L0_202407_B000000999_B000000999_20240731_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0142
| V1.42
| Intermediated payment transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0142_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0105
| V1.5
| Card transactiosn (Issuing part)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0105_L0_202405_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0150
| V1.50
| Card transactions with cards issued by resident PSPs (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0150_L0_202405_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0150-F
| V1.50-F
| Card transactions with cards issued by resident PSPs (fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0150-F_L0_202405_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0151
| V1.51
| Electronic card transactions with cards issued by resident PSPs, split by Merchant Category Codes (MCC)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0151_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0152
| V1.52
| Card transactions acquired by resident PSPs (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0152_L0_202405_B000000999_B000000999_20240802_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0152F
| V1.52F
| Card transactions acquired by resident PSPs (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0152-F_L0_202405_B000000999_B000000999_20240802_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0153
| V1.53
| Fundings and withdrawals related to prepaid cards
| BCL
| KS
| no
| Data payment collection (CDP)
| V0153_L0_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0106
| V1.6
| Card transactiosn (Acquiring part)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0106_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0160
| V1.60
| Cheques and money remittances (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0160_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0160-F
| V1.60-F
| Cheques and money remittances (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0160-F_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0107
| V1.7
| Cheques and money orders
| BCL
| KS
| no
| Data payment collection (CDP)
| V0107_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0170
| V1.70
| Over-the-counter (OTC) cash transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0170_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0108
| V1.8
| Electronic money scheme
| BCL
| KS
| no
| Data payment collection (CDP)
| V0108_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0180
| V1.80
| Book entries
| BCL
| KS
| no
| Data payment collection (CDP)
| V0180_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0109
| V1.9
| Card based e-money schemes
| BCL
| KS
| no
| Data payment collection (CDP)
| V0109_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0190
| V1.90
| Fundings and withdrawals in e-money (except prepaid cards)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0190_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0191
| V1.91
| E-money transfers (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0191_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0191-F
| V1.91-F
| E-money transfers (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0191-F_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| DCO
| Fonds de garantie<br /> des dépôts Luxembourg<br /> (FGDL)
| CSSF
| KS
| no
| DCOR reporting
| DCOR-ENNNNNNNN-YYYY-MM-DD_UUID.json<br /> DCOR-B00057255-2024-02-23_c15473ff-53c7-d38c-5219-3bdf950121f1.json
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Z1.1
| Balance sheet
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z11-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Z1.2
| Identification of third-party<br /> funds held and incorporated in the balance sheet
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z12-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Z1.4
| Capital adequacy of<br /> payment institutions
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z14-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Z2.1
| Profit and loss accoount
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z21-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| W1.1
| Balance sheet
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W11-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| W1.2
| Identification of third-party<br /> funds held and incorporated<br /> in the balance sheet
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W12-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| W1.3
| Statement of<br /> authorised reinvestments
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W13-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| W1.4
| Capital adequacy of<br /> electronic money institutions
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W14-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| W2.1
| Profit and loss account
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W21-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| W4.5
| Analysis of shareholdings
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W45-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Institutions - Foreign Account Tax Compliance Act (FATCA)
| FATCA
| FATCA
| Foreign Account Tax Compliance Act Reporting
| ACD
| KS
| yes
| FATCA sending
| FATCA_20150520080022_F0_2016_B_1970010112345_006M8M.00000.LE.442_P.xml
|-
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | (-) LE
| (-) Letter of explanation (LE)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Fin. Rep. of GFI
| style="vertical-align:bottom;" | DOCREP-S00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> no naming convention<br /> no naming convention<br /> no naming convention
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AR
| Annual report of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Fin. Rep. of GFI
| style="vertical-align:bottom;" | DOCREP-S00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> no naming convention<br /> no naming convention<br /> no naming convention
|- style="vertical-align:bottom;"
| Credit Institutions
| FRCREP
| B2.4
| Information on participating interest<br /> and subordinated loans
| CSSF
| S3
| no
| FINREP report
| PARTANDSUBLOANS-ENNNNNNNN-L-YYYY-MM-DD_UUID.zip (eg:PARTANDSUBLOANS-B00000499-L-2023-12-31_eb6809e1-bbf1-6cbc-5be1-35da4a526817.zip)<br />
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| FRCREP
| B2.5
| Information on staff costs and taxes<br /> and subordinated loans
| CSSF
| KS
| no
| FINREP report
| CFEREP-B00000999-2025-12-COREPY-L-N_133e79ec-d891-403c-983b-84af00c5b25b.zip<br /> B25.xml<br /> FRCREP-B9999-2007-12-B25-L0-L-N--.zip
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| LCRDA
| LCRDAX
| CSSF
| S3
| no
| FINREP report
| CFEREP-B00000999-2024-08-LCRDAX-N-N_a6fca981-2f2c-2a98-ddba-b241c2366a1a.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Companies
| S0216
| S2.16
| Quarterly statistical balance of Financial Companies
| BCL
| KS
| yes
| Issuing companies reporting
| S0216_L1_201406_DSE0003524_DSE0003524_20140720_001.xml<br />
|- style="vertical-align:bottom;"
| Financial Companies
| S0217
| S2.17
| Transactions of Financial Companies
| BCL
| KS
| yes
| Issuing companies reporting
| S0217_L1_201406_DSE0003524_DSE0003524_20140720_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| KI
| Key Investor Information Document<br /> (-) O: OPC Law 2010 and Loi 2007<br /> (-) K: SICAR<br /> (-) V: non-reglem.
| CSSF
| S3
| no
| PRIIPS Document
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf<br /> DOCREP-VNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LF
| Long Form reports (UCI Law 2010)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Long forms CSSF 09/423
| style="vertical-align:bottom;" | DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LF-LL-0000.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| SGOREP
| G21
| (-) SG 1A: Financial situation<br /> (-) SG 1B: Profit and loss account<br /> (-) SG 1C: Table relating to other activities<br /> (-) SG 2: Other activities<br /> (-) SG: Personnel Table relating to staff
| CSSF
| KS
| no
| Management company report
| SGOREP-S9999-2009-03-G21-L2-S-N--.xls
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | ML
| Management letters<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007<br /> (-) K: SICAR
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Management letters CSSF 09/423
| style="vertical-align:bottom;" | DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf (SICAR)
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | ML
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Management letters of GFI
| style="vertical-align:bottom;" | DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| AI
| Articles of Incorporation of UCITS<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| S3
| no
| Management regulation/status
| DOCOFF-ENNNNNNNN-UUID.zip<br /> containing DOCREP-ENNNNNNNN-YYYY-MM-DD-AI-LL.pdf <br /> - The expected format of an UUID is: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX<br /> - E in (O, K, V)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| MR
| Management Regulations of UCITS<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007
| CSSF
| S3
| no
| Management regulation/status
| DOCOFF-ENNNNNNNN-UUID.zip<br /> containing DOCREP-ENNNNNNNN-YYYY-MM-DD-MR-LL.pdf <br /> - The expected format of an UUID is: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX<br /> - E in (O, K, V)
|- style="vertical-align:bottom;"
| MiFID II / MiFIR
| TAFREP
| TAF
| Article 26 of Regulation<br /> No 600/2014:<br /> Obligation to report transactions<br /> (Markets in financial instruments => MiFIR)
| CSSF
| KS
| no
| Mifir reporting
| TAFREP-B00000001-2017-04-15-123456.xml
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| (-) GR<br /> (-) ID<br /> (-) FC<br /> (-) IA<br /> (-) TP<br /> (-) LP<br /> (-) PG<br /> (-) OG<br /> (-) TM<br /> (-) RD<br /> (-) AS<br /> (-) FP<br /> (-) PN
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Other closing documents of GFI
| style="vertical-align:bottom;" | DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (SIAG Partie I Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (GFI chapitre 15 Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (SIAG/FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (FIAAG)<br />
|- style="vertical-align:bottom;"
| Other reporting CSSF BCL
| OTHREP
| OTH
| Other reporting
| CSSF
| KS
| no
| OTHER reporting<br /> (=> CSSF)
| OTHREP-B9999-HELLO_WORLD.xlsx
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| BOP101
| BOP1.1
| Balance of payments reporting
| BCL
| KS
| no
| Payments balance
| BOP101_20130616_B000000999_B000000999_20130617_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| BOP102
| BOP1.2
| Cross-border payments<br /> executed for the account<br /> of the resident counterparts
| BCL
| KS
| no
| Payments balance
| BOP102_20240731_B000000999_B000000999_20240801_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| PSFREP
| (-) Basic reporting<br /> (-) Ad hoc reporting<br /> (-) Annual information
| Reporting population:<br /> (-) Investment firms<br /> (-) Specialised PFS<br /> (-) Support PFS
| CSSF
| KS
| no
| PSF report
| PSFREP-P9999-2008-03-P11-L1-L-N--.xlsx
|- style="vertical-align:bottom;"
| Insurance Corporations
| N01 (Comp); N02 (Comp); N03 (Comp);<br /> N04 (Comp); N05 (Réviseur); N06( Réviseur);<br /> N07 (Comp); N08 (Comp); N09 (Comp); N10 (Comp); N11 (Comp); N12 (Réviseur);<br /> N13<br /> (Comp);<br /> N14<br /> 'Comp)
| n/a
| Rapports narratifs
| CAA
| KS
| no
| Rapport narratif (CAA) (Companie) -<br /> Governance Re<br /> <br /> Rapport narratif (CAA) (Réviseur) -<br /> Governance Rep
| N01V-LU-01-20181231-CAA-LEIDéclarant-LEIDéposant.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CSDREP
| CSDR
| Reporting CSDR:<br /> Introduction of quarterly internalised settlement reporting requirements<br /> pursuant to Article 9(1) of EU Regulation No 909/2014 (CSDR)
| CSSF
| KS
| no
| Reporting CSDR
| CSDREP-B00000001-B00000001-2018-Q4-20190101-1.zip
|- style="vertical-align:bottom;"
| Credit Institutions
| BNNNN
| B4.4
| List of head offices, agencies,<br /> branches and representative offices
| CSSF
| KS
| no
| Reporting EDIFACT
| B0001809.T01
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Institutions for Occupational Retirement Provision
| FNDREP
| IORP
| Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019
| CSSF
| S3
| no
| Reporting IORP
| FNDREP-ENNNNNNNN-NNNNNNNN-YYYY-MM-DD-SUBTYPE-L-D_UUID.zip
|- style="vertical-align:bottom;"
| Money Market Funds (MMF)
| MMFREP
| MMF
| • According to Article 37 of Regulation (EU) 2017/1131, the manager of a MMF must report information to the competent authority (CSSF) of the MMF, at least on a quarterly basis or - for MMF with assets under management of less than Eur 100 million - on at least an annual basis.<br /> • The first quarterly report should be sent to the competent authority of the MMF no later than 30 days after the end of Q1 2020.
| CSSF
| S3
| no
| Reporting Money Market Fund
| MMFREP-P00000789-O00000654-00000123-2020-Q1-0001.zip<br /> MMFREP-P00000789-O00000654-00000123-2020-Y1-0001.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0112-L
| S1.12-L
| Indirect withdrawal and remittance of banknotes denominated in EUR through an intermediary
| BCL
| KS
| no
| Reporting S1.12-L
| S0112-L_L0_201905_B000000999_B000000999_20130605_001.xml
|- style="vertical-align:bottom;"
| Financial Companies
| TPTIBS
| TPTIBS
| Monthly security by security reporting of Financial Companies
| BCL
| KS
| yes
| Reporting securities by securities of issuing companies
| TPTIBS_L1_201406_DSE0003524_DSE0003524_20140720_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| U11
| U1.1
| Monthly financial information UCITS and UCI
| CSSF
| KS
| yes
| Reporting U
| U11REP-B00000012-O00008450-00000002-201512-RAP-1421893257541.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBBL
| TPTBBL
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| KS
| no
| Security by security Banks
| TPTBBL_L5_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBBN
| TPTBBN
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| KS
| no
| Security by security Banks
| TPTBBN_L5_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBHN
| TPTBHN
| Security by security report–<br /> Off-balance sheet data–<br /> Non-resident
| BCL
| KS
| no
| Security by security Banks
| TPTBHN_L2_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBHR
| TPTBHR
| Security by security report–<br /> Off-balance sheet data–<br /> Resident customers
| BCL
| KS
| no
| Security by security Banks
| TPTBHR_L2_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom;"
| Investment Funds
| SFDR
| Periodical disclosures
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| S3
| no
| SFDR Reporting
| SFDR-ENNNNNNNN-TTTTT-YYYY-MM-DD-UUID.zip<br /> SFDR-O00000406-PERIO-2023-03-31-41c13c08-ef59-4183-870f-80d7a00c54e8
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| SFDR
| Precontractual disclosures
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| S3
| no
| SFDR Reporting
| SFDR-ENNNNNNNN-PRECO-UUID.zip<br /> SFDR-O00000406-PRECO-41c13c08-ef59-4183-870f-80d7a00c54e8.zip
|- style="vertical-align:bottom;"
| Investment Funds
| SIC
| K3.1
| Financial information to be submitted by investment companies in risk capital (SICARs)
| CSSF
| KS
| no
| Sicar reporting
| SICREP-B999999-K999990000-2008-06-K31-L0-L-N.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| (-) AR<br /> (-) SR<br /> (-) LE<br /> (-) RO<br /> (-) PM
| UCI Law 2010:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (MP)
| CSSF
| KS
| no
| SIF or SICAR : 08/371 FIS report<br /> UCI : 08/371 report
| SIF:<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf<br /> SICAR:<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf<br /> UCI:<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-SR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf
|- style="vertical-align:bottom;"
| Insurance Corporations
| S01; S02; S03; S04; S05;<br /> S06 (Réviseur); S07; S08;<br /> S09; S10; S11; S12; S13;<br /> S14; S15; S16; S17; S18;<br /> S19; S20; S23
| n/a
| XBRL reports Solvency II
| CAA
| KS
| no
| Solvency II Reporting
| S01V-LU-01-20181231-CAA-LEIDéclarant-LEIDéposant.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| S0214
| S2.14
| Quarterly statistical balance
| BCL
| KS
| yes
| Titrisation vehicles
| S0214_L1_201412_T000000999_T000123001_20150120_001.xml<br />
|- style="vertical-align:bottom;"
| Securitisation Vehicles
| S0215
| S2.15
| Transactions and write-offs/write-downs on securitised loans
| BCL
| KS
| yes
| Titrisation vehicles
| S0215_L1_201412_T000000999_T000123001_20150120_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| TPTTBS
| TPTTBS
| Security by security reporting
| BCL
| KS
| no
| Titrisation vehicles
| TPTTBS_L1_201412_T000000999_T000123001_20150120_001.xml
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| UCIAR
| n/a
| Reporting Entity<br /> A: Alternative Investment fund manager (AIFM)
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| UCIAR
| n/a
| Reporting Entity<br /> B: Credit institution
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom;"
| Investment Funds
| UCIAR
| n/a
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| UCIAR
| n/a
| Reporting Entity<br /> S: Management company
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| UCIAR
| n/a
| Reporting Entity<br /> (-) P: PFS<br /> (-) I: Support PFS
| CSSF
| S3
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Other reporting CSSF BCL
| OTXREP
| OTX
| Various correspondence
| BCL
| KS
| no
| Various correspondence (OTH)<br /> (=> BCL -OTHER reporting)
| OTXREP-B0nnn-BOP_IDE_2015_B0nnn_20160615_001.xls
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| (-) GR<br /> (-) ID<br /> (-) FC<br /> (-) IA<br /> (-) TP<br /> (-) LP<br /> (-) PG<br /> (-) OG<br /> (-) TM<br /> (-) RD<br /> (-) AS<br /> (-) FP<br /> (-) PN
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Other closing documents of GFI
| style="vertical-align:bottom;" | DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (SIAG Partie I Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (GFI chapitre 15 Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (SIAG/FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (FIAAG)
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AR<br /> RO
| Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI)(FR)<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Fin. Rep. of GFI
| style="vertical-align:bottom;" | DOCREP-S00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| ALM
| ALMXXX
| CSSF
| S3
| no
| -
| CFEREP-B00000999-2024-08-ALMXXX-N-N_a6fca981-2f2c-2a98-ddba-b241c2366a1a.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| LF
| Long Form Report
| CSSF
| KS
| no
|
|
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| ML
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| CSSF
| KS
| no
|
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| ML
| Management Letter
| CSSF
| KS
| no
|
|
|- style="vertical-align:bottom;"
| Investment Funds
| S0106
| S1.6
| Monthly statistical balance sheet for non-money market funds (non-MMF)
| BCL
| KS
| yes
| -
| S0106_L2_202402_B000000999_NAF00000000000000_20240625_001.xml<br /> S0106_L2_202402_P000000999_O999990009_20240605_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0213
| S2.13
| Quarterly statistical balance sheet for non-MMF investment funds
| BCL
| KS
| yes
| -
| S0213_L2_202103_P000000999_O009990009_20240731_001.xml<br /> S0213_L2_202103_S000000999_O099990009_20240606_001.xml
|- style="vertical-align:bottom;"
| Investment Funds
| S0220
| S2.20
| Quarterly financial information
| BCL
| KS
| yes
| -
| S0220_L0_202512_B000000999_NAF66999999900000_20260127_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0404
| S4.4
| Marketing countries
| BCL
| KS
| yes
| -
| S0404_L0_202512_B000000999_NAF66999999900000_20260209_001.xml<br /> S0404_L0_202512_B000000999_O999990009_20260209_001.xml
|- style="vertical-align:bottom;"
| Insurance Corporations
| CED
| Source file reception from CAA
| Etat de situation relatif aux contrats en déshérence
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| CPR
| Source file reception from CAA
| Compte rendu
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| ESP
| Source file reception from CAA
| Enquête spécifique
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ETR
| Source file reception from CAA
| Etat trimestriel
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| FIR
| Source file reception from CAA
| Fiche de renseignement
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| PDA
| Source file reception from CAA
| Rapport PDAL (Procédure de Dissolution Administrative sans Liquidation)
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RAC
| Source file reception from CAA
| Rapport actuariel
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RDC
| Source file reception from CAA
| Rapport distinct complémentaire du réviseur
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RDI
| Source file reception from CAA
| Rapport distinct du réviseur
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RGO
| Source file reception from CAA
| Rapport de gouvernance
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RLB
| Source file reception from CAA
| Rapport LBCFT
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RRE
| Source file reception from CAA
| Rapports sur le traitement des réclamations
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RSE
| Source file reception from CAA
| Rapport distinct Solvabilité 2 de l'entreprise
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RSO
| Source file reception from CAA
| Rapport distinct Solvabilité 2 du réviseur
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Credit Institutions
| ICS
| ICS
| Yearly Survey on Covered Investment claims (SIIL)
| CSSF
| S3
| no
| ICS Reporting
| ICS-ENNNNNNNN-YYYY-MM-DD_UUID.json <br /> (eg:ICS-B00057255-2024-02-23_c15473ff-53c7-d38c-5219-3bdf950121f1.json)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ROI<br /> DIN
| n/a
| DORA Register of Information<br /> DORA Incident Reporting
| CAA
| KS
| no
| Rapport narratif (CAA) (Companie) -<br /> Governance Re<br /> <br /> Rapport narratif (CAA) (Réviseur) -<br /> Governance Rep
| ROIV-LU-01-20250303-CAA-LEIDéclarant-LEIDéposant.zip<br /> DINV-LU-01-20250303-CAA-LEIDéclarant-LEIDéposant.zip
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DPAAIF
| n/a
| self assessment <br /> questionnaire PDAOFI
| CSSF
| S3
| no
| PDAOFI Reporting
| DPAAIF-EIIIIIIII-YYYY-UUID.zip <br /> (e.g.: DPAAIF-P99999999-2024-41c13c08-ef59-4183-a456-870f80d7a00c54e8.zip)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CFEREP
| Monthly modules:<br /> - ALMXXX<br /> - LCRDAX<br /> Quarterly modules:<br /> - AEXXXX<br /> - COREPX<br /> - FINREP<br /> - FRTBXX<br /> - IRRBBX<br /> - LAREXX<br /> - LEVERX<br /> - NSFRXX
| (-) ALM corep_alm_con.xsd<br /> corep_alm_ind.xsd corep_alm.xsd<br /> (-) LCRDA corep_lcr_da_con.xsd<br /> corep_lcr_da_ind.xsd corep_lcr_da.xsd<br /> (-) IRRBB irrbb.xsd
| CSSF
| S3
| no
| COREP report
| CFEREP-B00000999-2024-08-ALMXXX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.xbrl<br /> inside <br /> CFEREP-B00000999-2024-08-ALMXXX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.zip<br /> <br /> <br /> CFEREP-B00000999-2024-08-LCRDAX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.xbrl<br /> inside<br /> CFEREP-B00000999-2024-08-LCRDAX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.zip
|}
</div>

Useful link :
<span class="plainlinks">[https://www.cssf.lu/wp-content/uploads/Naming-convention.pdf <span style="display: inline-block;
background-color: #009ACE;
color: white; text-align: center; font-family: sans-serif; font-size:0.8vw;
width: auto; height: auto;
border: none; border-style: outset; border-radius: 10px;
padding: 0.5%; margin: 1%;">CSSF Naming convention</span>]</span>

Sending Service

2026-05-21T09:55:13Z

Cso:

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

__TOC__

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

= Operating principle =

The '''Sending Service''' is our solution for the '''automatic transmission''' of reports and documents to authorities.

This solution is useful if you have a '''large number of reports''' to submit or if the manual sending does not suit your needs.

Please be aware that, in this case you will have to provide the files yourself according to the authorities' file specifications.

This tool is compatible with most of the current operating systems (Windows / Unix / Linux) and is usually <span style="color: #C00000">'''installed on a server'''</span> on your side.

With a suitable '''network mapping''', users can simply '''drop the file to be sent into the appropriate directory'''.

The file is then automatically ''' encrypted and sent'''.

= Prerequisites =

*Internet access
*<span style="color: #C00000">'''Java version 1.8 </span> <u>Note :</u> versions 8_351 and higher need a patch to be used with our system, see :[[Error_messages_list#JCE_cannot_authenticate_the_provider_BC]]'''
*If you use a proxy, authorize outgoing calls to [https://www.e-file.lu www.e-file.lu]. Port 443 (HTTPS) must be open.
*<span style="color: #C00000">'''Administrator rights''' </span> to install the Sending Service on the computer ''(Windows Start button > Control Panel > User Accounts > Manage User Accounts)''.
*OS: Windows or Linux
*Processor: Pentium 2 GHz or equivalent
*8 GB of RAM
*1 GB of free space on hard disk drive if the files are downloaded by ftp. If files are locally stored, provide a free space of above 100 MB or a regular purges.
*1 GB of free space on hard disk drive for logs. Regular purges are necessary as well.
*A <span style="color: #C00000">'''Sending Service user''' </span>, ''for example: aacSD'', and its password, ''for example: formation'', have to be available [[E-file_Administration#e-file_administrator_functions_.28e-file_v1.29|'''=> e-file administrator''']].
*The e-file account of the Sending Service user has to be linked to groups/modules, for example FATCA reporting + profile "Sending Service".
*A valid <span style="color: #C00000">'''keystore''' </span> (keystore.ks) and its <span style="color: #C00000">'''password''' </span> must be available
*The Sending Service user has to be properly configured in the e-file user administration tool in order to be able to receive <span style="color: #C00000">'''alerts''' </span> (receipt of acknowledgement and feedback files).

Note that you can find the prerequisites for the manual transmission there : [[Transmission_Module#System_requirements]]

= Installation / update with Sending Service Installer =

The Sending Service Installer is a tool that helps you install or configure quickly your Sending Service.

It can be downloaded from these links:

'''[https://www.e-file.lu/WSEfileFlex/messagebroker/assistantSD?cdLangIso=EN English version]'''

'''[https://www.e-file.lu/WSEfileFlex/messagebroker/assistantSD?cdLangIso=FR French version]'''

Once you have downloaded the application you will have to run it with Java by clicking the Run button.

[[File:Doc_SDInstaller_01.png|border|400 px]]

''If the message'' unable to run the application ''occurs, [[Transmission_Module#Delete_Java_cache|delete the java cache.]]''

'''The front page of the Sending Service Installer opens and shows you the different functionalities you can select: '''

* Install a new Sending Service
* Configure an existing Sending Service
* Update an existing Sending Service
* Send logs

[[File:Doc_SDInstaller_02.png|border|600 px]]

== Installation ==

'''Controls before installation:'''
* Check that the connected user is administrator of the computer
* Have an e-file Sending service user (login and password) (e.g. : aacSD)

To check whether a Sending service user exists, log on as an e-file administrator.
<u>'''Step 2</u>:'''

Click the '''Administration module'''

[[File:AdminAccess.png|700px]]

The user linked to the Sending Service usually follows the bellow naming rules : three
letters referring to the company (in lower case) following by "SD" in upper case. (e.g. :
aacSD)

[[File:User Sending service.png|900px]]
If the user doesn't exist, please contact us.

'''Start installation:'''
To install a <u> new </u> Sending Service, click on the button Install on the front page.

<u>'''Step 1'''</u>: Select the folder where you want to install your Sending Service.

[[File:Doc_SDInstaller_03.png]]

<u>'''Step 2'''</u>: The Sending Service is downloaded and saved in the selected folder.

<u>'''Step 3'''</u>: Select the keystore file, containing your LuxTrust certificate.

[[File:Doc_SDInstaller_04.png]]

<u>'''Step 4'''</u>: The Sending Service is ready to be configured. By clicking the '''Configuration''' button, you will be redirected to the '''Configuration menu''' of the '''.properties file'''.

[[File:Doc_SDInstaller_05.png]]

==Configuration==

To configure an <u>existing</u> Sending Service you have to select the folder where it is stored and click on the '''Configuration''' button.

[[File:10 SendServConf.png|border|600 px]]

The '''configuration''' of an existing Sending Service is similar to a new Sending Service.

<span style="background:yellow"> '''IMPORTANT:''' </span> each time you make changes to the properties (configuration) file, you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]] before, make your changes and then install the Sending Service again.

'''Configuration''' menu of the '''.properties file''' ([[Sending_Service#Configuration of the properties file | => Help: Configuration of the properties file]]):

[[File:Doc_SDInstaller_06.png|border|500 px]]

The '''Configuration''' menu allows you to setup your Sending Service.

The message ''Error: There are errors in your setup'' indicates that nothing has been set-up so far.

You have to configure each field marked in red.

If you have a '''proxy''', select ''True'' in the dropdown list and select ''More'' to type in the proxy settings.

''Note: The passwords will be asked during the finalization of the installation, all passwords are encrypted.''

''Note 2: You can edit each field by clicking the More button''

[[File:Doc_SDInstaller_07.png|border|600 px]]

The '''listeners''' can be activated in one shot by clicking on the button ''Listener state : Activate all''.

''Note: This functionality will force the Sending Service to scan all the folders, if you do not want all listeners to be activated, please activate manually the listeners you need.

Please consult our [[Sending_Service#Listener_list | Listener list]].

[[File:Doc_SDInstaller_08.png|border|600 px]]

If you have to submit Investment Funds reporting O4.1; O4.2 (EDIFACT format), you must complete this fields :

'''domain.descr''': Not relevant. You can provide abbreviated name of the Central Administration.

'''domain.env.ac.id.bcl''': this code is composed of a letter and six digits and has been provided to you by the CSSF (Example: P123, should be written as “P000123”).

'''domain.env.ac.id.cssf''': this code is composed of a letter and six digits and has been provided to you by the CSSF (Example P123, should be written as “P000123”).

The two others will be asked when installing (domain.en.ac.cd_auth and domain.env.ac.pwd)

[[File:Doc_SDInstaller_09.png|border|500 px]]

Once the configuration finished, you can click on '''Control''' to check if there is a configuration error.

The message ''No error in your setup'' means that the setup is correct.

[[File:Doc_SDInstaller_10.png|border|500 px]]

If there are no errors, you can click on '''Save''' to save your actual configuration.

[[File:Doc_SDInstaller_11.png|border|500 px]]

To install the Sending Service, you have to click on the '''Install''' button.

A pop-up window opens where you have to enter your passwords.

If you do not use a proxy, you can leave a blank for the proxy password<br/>
If you need to send O4.1 or O4.2 reports enter also those :<br/>
CA Password = '''domain.env.ac.pwd''': this '''authentication password''' has been provided to you by the CSSF (postal mail).<br/>
CA Code = '''domain.en.ac.cd_auth''': this '''authentication code''' has been provided to you by the CSSF (postal mail).<br/>

[[File:Doc_SDInstaller_12.png|border|500 px]]

Once finished a pop-up windows opens stating that the installation has been successful:

[[File:Doc_SDInstaller_13.png|border|500 px]]

To start your Sending Service open the folder where you installed it and run the file '''run.bat''' or '''InstallServiceNT.bat''' if you want to install the Service as a '''Windows Service'''.

[[Sending Service#Installation as a Windows Service|=> Installation as a Windows Service]]

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

==Update==

<span style="background:yellow"> '''IMPORTANT:''' </span> before updating your Sending Service you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]].

To update an <u> existing </u> Sending Service you have to click the ''Update'' button.

Then click on '''Check''' in order to verify if a new version is available.

[[File:Doc_SDInstaller_16.png|border|600 px]]

If your Sending Service is up-to-date you will get the following message:

[[File:Doc_SDInstaller_17.png|border|600 px]]

If there is a new version of the Sending Service available the following window will appear:

[[File:Doc_SDInstaller_18.png|border|600 px]]

To continue the update, click on Ok.

During the first steps, the new version will be downloaded.

Once you have reached step 3, the tool will ask you to select your old '''configuration''' file ('''.properties file''')

[[File:Doc_SDInstaller_19.png|border|600 px]]

The tool will automatically back-up of your old Sending Service. You have to wait until the process is finished.

[[File:Doc_SDInstaller_20.png|border|600 px]]

Step 5 will be the '''configuration''' of the updated Sending Service. You have to click on '''Configuration''' to access the '''Configuration''' menu.

[[File:Doc_SDInstaller_21.png|border|600 px]]

If there are changes in the configuration file of the Sending Service with the new version, the fields will be marked in red. You will have to select the proper setup and save the changes.

[[File:Doc_SDInstaller_22.png|border|600 px]]

Once the configuration finished, you can click on '''Control''' to check if there is a configuration error.

The message ''No error in your setup'' means that the setup is correct.

[[File:Doc_SDInstaller_10.png|border|500 px]]

If there are no errors, you can click on '''Save''' to save your actual configuration.

[[File:Doc_SDInstaller_11.png|border|500 px]]

To install the Sending Service, you have to click on the '''Install''' button.

A pop-up window opens where you have to enter your passwords.

''Note : If you do not use a proxy, you can leave a blank for the proxy password''

[[File:Doc_SDInstaller_12.png|border|500 px]]

==Send logs==

If you encounter issues with your Sending Service, you can use the Help function to send an email to the [[How to contact us|'''Client Support & Operations Desk''']].

The tool will create automatically a zip file containing the log files of your Sending Service you can attach to the email.<br><br>

[[File:Doc_SDInstaller_23.png]]

[[File:Doc_SDInstaller_24.png]]

= Manual installation with Command Prompt =

* Download the latest Sending Service version here: [https://www.e-file.lu/WSEfileFlex/SD/SD.zip '''Download latest Sending Service version''']
For UAT environment the latest version [https://homologation.e-file.lu/WSEfileFlex/SD/SD.zip '''is available here''']

* Extract and copy the entire content of the directory ServiceDeposant in the Sending Service directory. Ensure that the directory is <span style="color: #C00000">'''not read only''' </span>.
[[File:SD.png| 600 px]]

* Copy your <span style="color: #C00000">'''keystore'''</span> in the keystores folder of the Sending Service.

* Copy the <span style="color: #C00000">'''template_configInstall.properties'''</span> file and rename it [sender''Name''].properties.

* Complete the <span style="color: #C00000">'''properties file'''</span> as explained in [[Sending Service#Configuration of the properties file|'''Configuration of the properties file''']] chapter.

* Install the new Sending Service:
(-) Open Command Prompt
(-) Move to the root folder of your new Sending Service (for example: C:\Program Files\e-file\ServiceDeposant\)
(-) install.bat [sender''Name''].properties
(-) enter the root path of your JRE (for example: C:\Program Files\Java\jre1.8)
(-) Enter the password of the e-file Sending Service user
(-) Enter the password of your keystore
(-) Enter the password of your proxy if you use a proxy
(-) Enter the O4.x password for CSSF/BCL if needed
(-) Enter the O4.x authentication code for CSSF/BCL if needed
(-) Press the ENTER key

<span style="background:yellow"> '''IMPORTANT:''' </span>

SECURITY ENHANCEMENTS (june 2023)

The security settings of the Sending Service have been enhanced for O4.1 and O4.2 reports, the related passwords are now encrypted.

Please note that the installation procedure of the Sending Service slightly changed due to the implementation of this feature:

[[File:SD_CmdInstall.png | 800 px]]

At the end of the script you must get the following message: <span style="background:yellow"> '''BUILD SUCCESSFUL''' </span> indicating that the installation was successful.

[[File:SD_CmdInstall_success.png | 200 px]]

<span style="background:yellow"> '''IMPORTANT:''' </span> each time you make changes to the properties (configuration) file, you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]] before, make your changes and then install the Sending Service again.

== Configuration of the properties file ==

The <u>.properties</u> file (''template_configInstall.properties'') contains important information which are necessary to '''generate your configuration files''' during the physical installation.

The latter are used to start and use the Sending Service.

In other words :

* <span style="color: #C00000">'''The <u>.properties</u> file contains all the variables needed to run the Service Service.'''</span>

* <span style="color: #C00000">'''Any modification of the <u>.properties</u> file must be followed by an installation of the Sending Service to be really applied.'''</span>

<span style="color: #C00000">'''Please find below important information on how to configure your <u>.properties</u> file.''' </span>

<span style="color: #C00000">'''Please note, that at the end of setup, no '?' should remain in this file. </span>

'''E-file configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''efile.hostname=????'''''
|style="width:20em"| <span style="color: #C00000">'''www.e-file.lu'''</SPAN> for production environment,<br> or <br><span style="color: #C00000">'''homologation.e-file.lu'''</span> for test environment.
|-
|style="width:20em"| '''''efile.userId.Login=????'''''
|style="width:20em"| e-file login of the Sending Service user (Example: abcSD)
|-
|style="width:30em"| '''''keystore.path=@PROJECT_ROOT_PATH@/keystores/????.ks'''''
|style="width:20em"| path of the keystore (xxxx.ks)
|-
|style="width:20em"| '''''lang.code=FR??EN'''''
|style="width:100em"| language of the acknowledgement files
|}

'''Proxy configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''proxy.required=false??true'''''
|style="width:50em"| <span style="color: #C00000">'''true'''</span> if a proxy is used to access the internet through HTTP or HTTPS.
|-
|style="width:30em"| '''''proxy.host=???? <br> proxy.port=???? <br> proxy.user=???? <br> proxy.domainNTLM=????'''''
|style="width:100em"| Complete all other parameters according your network infrastructure.
|}

'''Configuration of connection for authority acknowledgement / feedback files'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''reportingXXXXXX.state=up??down'''''
|style="width:50em"| All subsequent blocks in the .properties file corespond to a particular type of reporting.

Please consult our [[Sending Service#Listener list|'''Listener list''']] to verify which reporting type is linked to which listener.

Example: if you only have to sent FATCA reportings, the state of the listener reportingFATCA.state has to be up: '''reportingFATCA.state='''<span style="color: #C00000">'''up'''</span>'''

The other listeners should be <span style="color: #C00000">'''down'''</span>.

|-
|style="width:30em"| '''''reportingXXXXXX.remoteDir'''''
|style="width:50em"| <span style="color: #C00000">'''Path to file location'''</span> for the relevant reporting.

|-
|style="width:30em"| '''''@PROJECT_ROOT_PATH@'''''
|style="width:50em"| <span style="color: #C00000">'''Dynamic parameter'''</span> indicating the Sending Service installation path.<br>
To change if you want to locate the user working directory elsewhere on the server or another machine.
In this case, indicate the full path to file (separator = '/').

|-
|style="width:30em"| '''''reportingXXXXXX.scheduleTime'''''''
|style="width:50em"| <span style="color: #C00000">'''Execution frequency'''</span> of Window Service to process files from this folder (30mn by default).
Feel free to '''reduce this value, but do not fall below 5mn= <i><span style="color: #C00000">300000</span></i>'''.

|-
|style="width:30em"| '''''reportingXXXXXX.deeplevel'''''''
|style="width:100em"| <span style="color: #C00000">Number of '''sub-levels'''</span> to scan.<br>
By default the value is <span style="color: #C00000">'''0'''</span>, which means that only files at the root of the folder will be taken in account.

|}

'''Business environment properties'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''domain.descr'''''
|style="width:20em"| Not relevant. You can provide '''abbreviated name''' of the Central Administration.
|-
|style="width:20em"| '''''domain.env.ac.id.cssf'''''
|style="width:20em"| Your <span style="color: #C00000"> '''CSSF identifier'''</span> of 7 characters, 1 letter and 6 numbers'''
|-
|style="width:30em"| '''''domain.env.ac.id.bcl'''''
|style="width:20em"| Your <span style="color: #C00000"> '''BCL identifier'''</span>
|-
|style="width:20em"| domain.env.ac.pwd
|style="width:50em"| Doesn't appear anymore in the .properties, it will be asked when installing. <span style="color: #C00000">'''Password'''</span> of the Central Administration provided by the CSSF
|-
|style="width:20em"| domain.env.ac.cd_auth
|style="width:100em"| Doesn't appear anymore in the .properties, it will be asked when installing. <span style="color: #C00000">'''Authentication code'''</span> of the Central Administration provided by the CSSF.

The CSSF has provided you in an official letter your <span style="color: #C00000">'''password'''</span> and <span style="color: #C00000">'''authentication code'''</span>. The above mentioned IDs, passwords and codes are necessary for the successful processing of the O4.1, O4.2; O1.2 and the former O1.1 reporting.
|}

'''Configuration of monitoring'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''mon.app.heartbeat=false'''''
|style="width:20em"| If parameter is "true", we will be able to send you an alert if an interruption of your service is detected on our side (within 72 hours).
'''Should you want to use this feature feel free to contact us'''

|-
|style="width:20em"| '''''mon.app.origin=????'''''
|style="width:20em"| <span style="color: #C00000">'''Unique name'''</span> , without space, to enable us to identify your Sending Service. Not mandatory.
|-
|style="width:30em"| '''''mon.task.dist.period=60000'''''
|style="width:100em"| Frequency of the heartbeat (here 60000 milliseconds, 1 min). The monitoring window is set to 9 minutes. At least one heartbeat must have been registered during this interval otherwise the Sending Service is considered as down.
|-
|}

== Listener list ==

{|border="1" cellspacing="2" cellpadding="10"
|-
! Listener
! Sending Service folder
! Reporting type
! Business group
|<span style="color: #868686"> <small>''Internal <br /> Technical <br /> Business ID''</small/> </span>
|-
|<span style="color: #868686"> <small>''Please be informed that the listener '''efile.listener.state''' is no longer available in the properties file''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|-
|<span style="color: #868686"> <small>''Please be informed that the listener '''efile.replies.listener.state''' is no longer available in the properties file''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|-
| reportingMMF=up
|(-) ReportingDiffusion/MMF''
| <small>CSSF - MMF
| Money Market Fund Reporting
| <span style="color: #868686"> <small>''83-Money Market Fund Reporting''</small/> </span>
|-
| reportingOPC.automatique.state=up
|(-) ReportingDiffusion/OPC/envoi_Automatique/fichiersCCLUX<br><span style="color: #868686"> <small>''(-) ReportingDiffusion/OPC/envoi_Automatique/fichiersCCLUX/Enrichment''</small/> </span><br><span style="color: #868686"> <small>''(-) ReportingDiffusion/OPC/envoi_Automatique/TPT_FINESTI''</small/> </span>
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL : S1.3, S1.6, S2.13, TPTOBS, S4.4, S2.20 </small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPCExportXLS.automatique.state=up
| ReportingDiffusion/OPC/envoi_Automatique/ExportXLS
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL : S1.3, S1.6, S2.13, TPTOBS</small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPC.envoi_Historique.state=up
| ReportingDiffusion/OPC/envoi_Historique/fichiersCCLUX
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL: S1.3, S1.6, S2.13, TPTOBS</small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPC.semiAuto.state=up
| n/a
| n/a
| n/a
| n/a
|-
|reportingVni.state=up
|ReportingDiffusion/VNI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingDividende.state=up
| ReportingDiffusion/Dividendes
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingTAF.state=up
| (-) ReportingDiffusion/TAF<br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/declaration_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Rapport''</small/> </span>
| <small>CSSF: transactions in financial instruments (TAF)</small/>
| Report TAF-MIFID
| <span style="color: #868686"> <small>''71-MiFIR reporting''</small/> </span>
|-
|-
| reportingTAF.state=up
| (-) ReportingDiffusion/TAF<br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/declaration_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Rapport''</small/> </span>
| <small>CSSF: transactions in financial instruments (TAF)</small/>
| Report TAF-MIFID
| <span style="color: #868686"> <small>''71-MiFIR reporting''</small/> </span>
|-
| reportingIORP.state=up
| ReportingDiffusion/IORP
| <small>CSSF - Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019 </small/>
| Report IORP
| <span style="color: #868686"> <small>''80''</small/> </span>
|-
| reportingCOREP.state=up
| ReportingDiffusion/COREP
| <small>CSSF:<br> SCOREP; SLAREX; SLCRXX; SNSFRX; SALMXX; CCOREP;<br>CLAREX; LCRXX; CNSFRX; CALMXX; CFINRP; SFINRP;<br>AEXXX; SAEXXX; CFPXXX; SFPXXX; CSBPXX;<br>SSBPXX; CSBPIM; SSBPIM; CLCRDA; SLCRDA; ALMXXX</small/>
| Rapport COREP
| <span style="color: #868686"> <small>''72-COREP reporting''</small/> </span>
|-
| reportingFINREP.state=up
| ReportingDiffusion/FINREP
| <small>CSSF: B2.4; B2.5; LCRDAX</small/>
| Rapport FINREP
| <span style="color: #868686"> <small>''73-FINREP reporting''</small/> </span>
|-
| reportingFINREP.EDIFACT.state=up
| ReportingDiffusion/FINREP/EDIFACT_CSSF
| <small>CSSF: B4.4</small/>
| Reporting EDIFACT
| <span style="color: #868686"> <small>''16-Edifact''</small/> </span>
|-
| reportingBOP.state=up
| ReportingDiffusion/BOP
| <small>BCL - Credit institutions: Balance of payments (BOP1.1; BOP1.2)</small/>
| Balance des Paiements
| <span style="color: #868686"> <small>''12-Edifact reporting''</small/> </span>
|-
| reportingBCLStat.state=up
| ReportingDiffusion/BCL_Statistics
| <small>BCL - Credit institutions: S0.1; S1.1; S1.4; S1.5; S1.8; S1.9;S1.12<br>S2.5-L; S2.5-N; S2.8; S2.9-L; S2.9-N; S3.2</small/>
| Statistiques BCL
| <span style="color: #868686"> <small>''13-BCL statistics''</small/> </span>

|-
| reportingAnacredit.state=up
| ReportingDiffusion/Anacredit
| <small>ANTREF; ANTT1M; ANTT2M; ANTT2Q</small/>
| Rapport Anacredit
| <span style="color: #868686"> <small>''74 ANACREDIT reporting''</small/> </span>

|-
| reportingSecurisation.state=up
| ReportingDiffusion/Securisation
| <small>BCL - Securitation vehicles: S2.14; S2.15; TPTTBS</small/>
| Véhicule titrisation
| <span style="color: #868686"> <small>''23-Véhicule titrisation''</small/> </span>
|-
|reportingSecurisationS2.14ExportXLS.state=up<br>reportingSecurisationS2.15ExportXLS.state=up<br>reportingSecurisationTPTTBSExportXLS.state=up
| ReportingDiffusion/Securisation/ExportXLS
| <small>BCL - Securitation vehicles:S2.14; S2.15; TPTTBS</small/>
| Véhicule titrisation
| <span style="color: #868686"> <small>''23-Securitisation vehicule''</small/> </span>
|-
| reportingTPTB.state=up
| ReportingDiffusion/TPT
| <small>BCL - Credit institutions: TPTBBL; TPTBBN; TPTBHR; TPTBHN</small/>
| Titre par Titre Bancaire
| <span style="color: #868686"> <small>''20-Security by security reporting''</small/> </span>
|-
| reportingTPTBExportXLS.state=up
| ReportingDiffusion/TPT/ExportXLS
| <small>BCL - Credit institutions: TPTBBL; TPTBBN; TPTBHR; TPTBHN</small/>
| Titre par Titre Bancaire
| <span style="color: #868686"> <small>''20-Security by security reporting''</small/> </span>
|-
| reportingESP.state=up
| ReportingDiffusion/ESP
| <small>CSSF: Special Enquiries (ESPREP)</small/>
| Rapport Enquête
| <span style="color: #868686"> <small>''15-CSSF polls''</small/> </span>
|-
| reportingPSF.state=up
| ReportingDiffusion/PSF
| <small>CSSF - Professional of the financial sector (PSFREP)</small/>
| Rapport PSF
| <span style="color: #868686"> <small>''18-PSF reporting''</small/> </span>
|-
| reportingSICAR.state=up
| ReportingDiffusion/SICAR
| <small>CSSF - SICAR</small/>
| Rapport SICAR
| <span style="color: #868686"> <small>''17-SICAR reporting''</small/> </span>
|-
| reportingOTH.state=up
| ReportingDiffusion/OTH
| <small>CSSF - Other reporting (OTHREP)</small/>
| Reporting OTHER (CSSF)
| <span style="color: #868686"> <small>''19-OTHER reporting (CSSF)''</small/> </span>
|-
| reportingRFOPC.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_OPC
| <small>CSSF UCI: <br /> (-) Annual Report (AR) <br /> (-) Semi-annual report (SR) <br /> (-) Letter of explanation (LE) <br /> (-) Other periodic report(RO) <br /> (-) Movements in the securities portfolios (MP)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>

|-
| reportingRAFIS.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_FIS
| <small> CSSF SIF: <br />
(-) Annual Report (AR) <br />
(-) Semi-annual report (SR) <br />
(-) Letter of explanation (LE) <br />
(-) Other periodic report (RO) <br />
(-) Movements in the securities portfolios (PM)</small/> <br />
<small> SICAR: <br />
(-) Annual Report (AR) <br />
(-) Annual Report (RO) </small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingPOPC.state=up
| ReportingDiffusion/DOC_FIS_OPC/PROSP_OPC
| <small>CSSF UCI: <br /> (-) Prospectus (PC) <br /> (-) Simplified prospectus (PS) <br /> (-) Letter of explanation (LE)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingPFIS.state=up
| ReportingDiffusion/DOC_FIS_OPC/PROSP_FIS
| <small>CSSF SIF: <br /> (-) Prospectus (PC) <br /> (-) Offering document (DE) <br /> (-) Letter of explanation (LE)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingKID.state=up
| ReportingDiffusion/DOC_FIS_OPC/KID_OPC
| <small> Key Investor Information Document (KID) <br />
(-) O: OPC Law 2010 and Law 2007 <br />
(-) K: SICAR <br />
(-) V: non-reglem. <br />
[[Sending Service#Automating process for KID packages|=> Automated process for KID packages]]</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingMR.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_REGUL
| <small>CSSF - Management Regulations of UCITS (MR)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingAI.state=up
| ReportingDiffusion/DOC_FIS_OPC/ART_INCORP
| <small>CSSF - Articles of Incorporation of UCITS (AI)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingML.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_LETTER
| <small>CSSF - Management Letters (ML) <br />
(-) O: OPC Law 2010 and Law 2007 <br />
(-) K: SICAR <br />
(-) V: non-reglem. <br />
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingLF.state=up
| ReportingDiffusion/DOC_FIS_OPC/LONG_FORM
| <small>CSSF - Long Form reports (LF)
(-) O: OPC Law 2010
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
|reportingMLGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_GFI
|<small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingRGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_GFI
|<small> CSSF <br />
Annual management company report <br />
Management company report, other frequency <br />
Explanation letter</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingDOC_OTH.state=up
| ReportingDiffusion/DOC_FIS_OPC/OTHER
|<small> CSSF <br />
Auditor's report (RR) <br />
Explanation letter (LE) (for funds or Sicar, CSSF codification S or A) <br />
Report Hong Kong Securities and Futures (HK)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingCSDR.state=up
| ReportingDiffusion/CSDR
|<small> CSSF <br />
Report CSDR</small/>
| Reporting CSDR-9
| <span style="color: #868686"> <small>''78-Reporting CSDR''</small/> </span>
|-
| reportingGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/DOC_GFI
| <small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)

(-) Risk management function(GR) <br />
(-) OPCVM instruments information (ID) <br />
(-) Compliance Function (FC)<br />
(-) Internal audit function report (IA)<br />
(-) Complaints handling (TP) <br />
(-) Authorized third party complaints (LP) <br />
(-) Risk Management Procedure (PG)<br />
(-) Organization chart (OG) <br />
(-) Mandates table (TM) <br />
(-) Delegates of RFI (RD) <br />
(-) Branch activity (AS), <br />
(-) Own funds ratio (FP) <br />
(-) Risk management procedure AIFM (PN) <br />

</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingAML-AIFM-REG.state=up
| ReportingDiffusion/DOC_FIS_OPC/AML_AIFM_REG
| <small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)

(-) Letter of explanation (LE) <br />

</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingCD.state=up
| ReportingDiffusion/Various_Correspondence
| <small>BCL - Other reporting (OTX)</small/>
| Reporting OTHER (BCL)
| <span style="color: #868686"> <small>''22-Various correspondence (OTH=> BCL)''</small/> </span>
|-
| reportingSGO.state=up
| ReportingDiffusion/SGO
| <small>CSSF - Management company reporting (SGOREP)</small/>
| Rapport Société de Gestion
| <span style="color: #868686"> <small>''26-Management company''</small/> </span>
|-
| reportingDOCBNK.state=up
| ReportingDiffusion/DOC_BNK
| <small> AR: Annual Report <br />
AS: Annual report consolidated <br />
CO: Compliance Report <br />
GR: Governance Report <br />
IA: Internal Audit Report <br />
IC: ICAAP <br />
ID: ICAAP Consolidated <br />
LF: Long Form Report <br />
LC: Long Form consolidated <br />
LD: Long form branch or specific participation <br />
ML: ManagementLetter <br />
MC: Management letter consolidated <br />
RC: Risk Control Report <br />
RP: Recovery Plan <br />
SC: Single Customer View <br />
LG: Reconciliation LuxGAAP FINREP <br />
RR: Results distribution <br />
BD: AC member list <br /> IL: ILAAP <br /> IM: ILAAP consolidated
<br />
AC: Audit report on AML/CTF <br />
MF: Audit report on rules of conduct <br />
MM: Head quarter annual report <br />
RE: Report on out-of-court complaint resolution <br />
TR: Table on out-of-court complaint resolution <br />
AD: Circ. 18/697 annexe1 <br />

| Reporting des établissements de crédit
| <span style="color: #868686"> <small>''27-Reporting of credit institutions''</small/> </span>
|-
| reportingEDP.state=up
| ReportingDiffusion/EDP
| <small>CSSF - Payment instituions (EDPREP): Z1.1; Z1.2; Z1.4; Z2.1 </small/>
| Reporting EDP
| <span style="color: #868686"> <small>''29-Periodic reporting scheme for payment instituions (EDP)''</small/> </span>
|-
| reportingEME.state=up
| ReportingDiffusion/EME
| <small>CSSF - Electronic money instituions (EMEREP): W1.1; W1.2; W1.3; W1.4; W2.1 </small/>
| Reporting EDP
| <span style="color: #868686"> <small>''34-Electronic money reporting (EME)''</small/> </span>
|-
| reportingPubDiffu.state=up
| ReportingDiffusion/DOC_FIS_OPC/PUB_FINESTI<br>ReportingDiffusion/DOC_OPC_NOT_LU/PUB_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''32-Envoi pour publication/diffusion''<br>''33-Envoi pour publication/diffusion OPC non LU'' </small/> </span>
|-
| reportingOPCNONLU.state=up
| ReportingDiffusion/DOC_OPC_NOT_LU/LOCAL_REGISTRATION<br>ReportingDiffusion/DOC_OPC_NOT_LU/LOCAL_NOTIFICATION
| <small>HOST_UPDATE: [[Sending Service#Automating process for KID packages|Automated process for KID packages]]</small/>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''30-Enregistrement pour OPC non LU''<br>''31-Notification pour OPC non LU'' </small/> </span>
|-
| reportingMAJDOCLU.state=up
| ReportingDiffusion/DOC_FIS_OPC/HOST_UPDATE
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''37-Enregistrement/Mise à jour de documents Fond LU vers pays HOST''</small/> </span>
|-
| reportingSE.state=up
| ReportingDiffusion/SE
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingSEExportXLS.state=up
| ReportingDiffusion/SE/ExportXLS
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingSETransfoXLS.state=up
| ReportingDiffusion/SE
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingASS.state=up
| ReportingDiffusion/ASS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-Reporting BCL pour les assurances''</small/> </span>
|-
| reportingASSExportXLS.state=up
| ReportingDiffusion/ASS/ExportXLS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-BCL report for insurances''</small/> </span>
|-
| reportingASSTransfoXLS.state=up
| ReportingDiffusion/ASS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-BCL report for insurances''</small/> </span>
|-
| reportingDP.state=up
| ReportingDiffusion/CDP
| <small> BCL - Data on payment operation: V 1.1 - V 1.14 </small/>
| Collecte des données de paiement (CDP)
| <span style="color: #868686"> <small>''36-Data on payment instruments and operations''</small/> </span>
|-
| reportingNotifUcitsIV.state=up
| ReportingDiffusion/DOC_FIS_OPC/NOTIFICATIONS_UCITSIV
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''28-UCITS IV notification''</small/> </span>
|-
| reportingFINESTI.state=up<br>reportingLIBFINLU.state=up
| ReportingDiffusion/DOC_FIS_OPC/LIBRARY_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingLIBFINNOTLU.state=up
| ReportingDiffusion/DOC_OPC_NOT_LU/LIBRARY_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| <span style="color: #868686"> <small>''OBSOLETE : reportingCRF.state=up''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
|-
| <span style="color: #868686"> <small>''OBSOLETE : reportingCRFEncrypted.state=up''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
|-
| reportingAIF.state=up
| ReportingDiffusion/AIF
| <small> CSSF - Alternative Investment Fund managers: AIF / AIFM </small/>
| (-) AIF <br /> (-) AMfine
| <span style="color: #868686"> <small>''54-AIFMD reporting''</small/> </span>
|-
| reportingFATCA.state=up
| ReportingDiffusion/FATCA
| <small> ACD - Financial Institutions - Foreign Account Tax Compliance Act (FATCA) </small/>
| Rapport FATCA
| <span style="color: #868686"> <small>''60-FATCA reporting''</small/> </span>
|-
| reportingCAA.state=up
| ReportingDiffusion/CAA
| <small> (-) CAA - Rapports narratifs (N01-N10 <br /> (-) CAA - XBRL reports Solvency II (S01-S23) </small/>
| Reporting CAA|
| <span style="color: #868686"> <small>''63-BCL report for insurances|''</small/> </span>
|-
| reportingCRS.state=up
| ReportingDiffusion/CRS
| <small> ACD - Financial Institutions - Common Reporting Standard (CRS) </small/>
| Reporting CRS
| <span style="color: #868686"> <small>''68-CRS reporting''</small/> </span>
|-
| reportingGRP_BNK.state=up
| ReportingDiffusion/GRP_BNK
| <small>«SHS-Group» report </small/>
| BCL SHS report
| <span style="color: #868686"> <small>''75-SHS Reporting''</small/> </span>
|-
| reportingUCIAR.state=up
| ReportingDiffusion/UCIAR
| <small>CSSF UCIAR </small/>
| UCIAR Reporting
| <span style="color: #868686"> <small>''86-UCIAR Reporting''</small/> </span>
|
|-
| reportingESP.state=up
| ReportingDiffusion/ESP
| <small>ICS reporting </small/>
| Rapport Enquête
| <span style="color: #868686"> <small>''15-CSSF polls''</small/> </span>
|
|-
| reportingCAADoraROI=up
| ReportingDiffusion/CAA
| <small>DORA Register of Information</small/>
| CAA reporting
| <span style="color: #868686"> <small>''62-CAA reporting''</small/> </span>
|
|-
| reportingCAADoraDIN.state=up
| ReportingDiffusion/CAA
| <small>DORA Incident Reporting</small/>
| CAA reporting
| <span style="color: #868686"> <small>''62-CAA reporting''</small/> </span>
|
|-
| reportingPDAOFI.state=up
| ReportingDiffusion/PDAOFI
| <small>PDAOFI Reporting</small/>
| self-assessment questionnaire PDAOFI
| <span style="color: #868686"> <small>''88-PDAOFI reporting''</small/> </span>
|
|-
| reportingSFDR.state=up
| ReportingDiffusion/SFDR
| <small>SFDR Reporting</small/>
| Sustainable Finance Disclosure Regulation
| <span style="color: #868686"> <small>''87-SFDR reporting''</small/> </span>
|}

= Installation as a Windows Service =

Once the installation the Sending Service is completed, the <span style="color: #C00000">'''InstallServiceNT.bat'''</span> file is available and you can complete your Sending Service installation by creating the Windows Service <span style="color: #C00000">'''ServiceDeposant'''</span>.

Execution frequency of Window Service ServiceDeposant to process files from this folder is 30mn by default [[Sending_Service#Configuration of the properties file | => Configuration of the properties file]].

Double click the <span style="color: #C00000">'''InstallServiceNT.bat'''</span> file.

[[File:InstallServiceNT.png|600 px]]

A Command Prompt window opens up and closes as quickly as it popped up. The new Windows Service <span style="color: #C00000">'''ServiceDeposant'''</span> is now available.

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

[[File:WindowsService.png]]

<u>IMPORTANT</u>: Please ensure the '''Sending Service user''' that is linked to this Windows Service has <span style="color: #C00000">'''Internet rights'''</span> (=> Right click on ''Service deposant'' > select ''Properties'' > select ''Log On'' tab).

If you want to uninstall the Windows Service, please double click the <span style="color: #C00000">'''UninstallServiceNT.bat'''</span> file.

= Installation on Unix/Linux =

*Move to the ServiceDeposant directory
<u> Example </u>: /opt/ServiceDeposant/

*Check that you have execution rights (x) on the Install.sh file
<u> Example </u>: ls -l

*If not, just add this right using the chmod command
<u> Example </u>: chmod 755 install.sh

*Launch Install.sh with the configuration file as parameter
<u> Example </u>: install.sh config.properties

*Press the Enter key and enter the Java path when requested

*Press the Enter key again and wait for the ‘BUILD SUCCESSFUL’ message.

* Once installed, launch the run.sh to run the sending service

= How to start the Sending Service =

* Double click the <span style="color: #C00000">'''run.bat'''</span> command available at the root folder of your Sending Service

In the case you created a '''Windows Service'''

* Double click the <span style="color: #C00000">'''StartService NT.bat'''</span> command available at the root folder of your Sending Service

or

* Browse to the <span style="color: #C00000">'''Windows Services'''</span> console (''Start > Control Panel > Administrative Tools > Services'') and right click the '''ServiceDeposant''' service and start the service.

[[File:WindowsService.png]]

The message *Fin Ok* means that the installation was successful.

= How to stop the Sending Service =

* If you launched the Sending Service using the <span style="color: #C00000">'''run.bat'''</span> command, you can stop it pressing the keys Ctrl+C+Y.

In the case you created a '''Windows Service'''

* Double click the <span style="color: #C00000">'''StopService NT.bat'''</span> command available at the root folder of your Sending Service

or

* Browse to the <span style="color: #C00000">'''Windows Services'''</span> console (''Start > Control Panel > Administrative Tools > Services'') and right click the '''ServiceDeposant''' service and stop the service.

[[File:WindowsService.png]]

= Automatic and semi-automatic sending of O4.1 and O4.2 reports =

<span style="color: red;>'''Changed on July 2023'''</span>

For [http://www.cssf.lu/en/supervision/ivm/ucits/legal-reporting/ '''O4.1 and O4.2 reports'''] the [http://www.cssf.lu/en/supervision/'''CSSF'''] is expecting '''EDIFACT''' file format (ISO 9735).

Please note that you have to generate yourself a '''flat text file''' for these reports, which, once dropped into the dedicated directory of the Sending Service, will be transformed into the expected EDIFACT format.

'''The structure of the flat file is detailed in the document [[Media:StructMess_EN.pdf|Structure of messages for interface files from fund manager host system]], pages 8 to 14.'''

The Sending Service provides two sending ways :

<u>Automatic sending</u>

In this case, the flat files must be dropped into the '''OPC\envoi_Automatique\fichiersCCLUX''' folder of your Sending Service.

If the flat file is well formed, the reports are '''changed to ''.T62'' for O4.1, respectively ''.T63'' for O4.2''' into the subfolder '''Edifact''' by default ([[#IdBothCasesEdifact |see how to change it]]).

On sending, the ''.T6x'' is transformed into ''.trt''.
If the sending is OK, a ''.acq'' is generated otherwise a ''.err''. All this in the Edifact subdirectory.<br/>
If nothing appears in the Edifact subdirectory, it means that things are not going well.<br/>
<blockquote>You must check the Edifact subfolder for .acq or .err</blockquote>

Note : The .err that may be temporary generated within the PDF file for O4.2 reports must be ignored.

<u>Semi-automatic sending</u>

If you want to use this kind of sending, you have to drop your flat file into the '''OPC\envoi_SemiAutomatique\fichiersCCLUX_aTraiter''' folder of your Sending Service, where it will be converted to a PDF file and stored in the '''OPC\envoi_SemiAutomatique\fichiersPDF_aValider''' folder.

The PDF file allows you to check the data of your flat file in a more user friendly way before you transmit it to the supervisory authority.

Once checked/validated, the PDF file must be dragged into '''OPC\envoi_SemiAutomatique\fichiersPDF_aEnvoyer''' folder.

After being checked for errors, the reports are '''changed to ''.T62'' for O4.1, respectively ''.T63'' for O4.2''' into the subfolder '''Edifact''', <span style="color: red;>BE CAREFUL : this folder is in OPC\envoi_Automatique\fichiersCCLUX\'''Edifact''' by default.</span>([[#IdBothCasesEdifact |see how to change it]])

On sending, the ''.T6x'' is transformed into ''.trt''.
If the sending is OK, a ''.acq'' is generated otherwise a ''.err''. All this in the Edifact subdirectory.<br/>
If nothing appears in the Edifact subdirectory, it means that things are not going well.<br/>
<blockquote>You must check the Edifact folder for .acq or .err</blockquote>

<div id="IdBothCasesEdifact"></div>
<u>In both cases</u>

* The reports sent are .T62, resp. .T63, you will find them into the transmission follow-up with such names. The CSSF answsers with EDOFBR....xml files as feedbacks.<br/>

* The .ack files are not sent anymore, even for the O4.1 Fundsquare file.

* The '''Edifact results subfolder''' is the same for the two ways of sending : automatic and semi-automatic. You can choose the one you want by changing the property '''''reportingOPC.automatique.edifact.remoteDir''''' into the .properties file. In the installation assistant (assistantSD), this property is under reportingOPC.automatic.state's button 'More'. <br>Then install again to enable it.

= Automating process for KID packages =

In the context of KID updates to be filed to the CSSF, it is possible to set up the automatic sending of KIDs packages (.zip files) from our server to your Sending Service. Once the Sending Service has received the KIDs, they are copied in one of the following directory:

'''Luxembourgish fund'''
\ReportingDiffusion\DOC_FIS_OPC\KID_OPC

'''Foreign fund'''
\ReportingDiffusion\DOC_OPC_NOT_LU\HOST_UPDATE

Then the files are sent to the CSSF in the usual way.

If you want to use this feature, please
* Install the Sending Service [[Sending Service#Installation with Sending Service Installer|'''=> Installation with Sending Service Installer''']] or [[Sending Service#Manual installation with Command Prompt|'''=> Manual installation with Command Prompt''']]
* Ensure that the listeners <span style="color: #C00000">'''reportingOPCNONLU.state'''</span> and <span style="color: #C00000">'''reportingKID.state''' </span> in your properties file are <span style="color: #C00000">'''=up'''</span>
* Contact our Regulatory Service department and request the installation of this specific feature.
* Generate the KID package (.zip file) in the UCITS IV Document Management application (https://www.e-file.lu). Please note that in some cases an automated process on our servers can be installed.

Do not hesitate to contact our [[How to contact us|'''Client Support & Operations Desk''']] if you need further assistance.

= Sending progress and follow up =

== Transmission following ==

Here are the default transmission followup files that are created depending on the state in the transmission workflow.

<div style="text-align: left;">
{| border="1" cellspacing="2" cellpadding="10"
|-
! scope="col" | '''File extension'''
! scope="col" | '''Description'''
|-
||<span style="color: #C00000">''' .trt'''</SPAN>
|| <u> Example </u>: file processing of '''FileName.ext'''
Once the file has been dropped into the appropriate folder, the Sending Service will start processing it and rename it as follows:

'''FileName.ext_YYYYMMDDhhmmssmmm.'''<span style="color:#C00000">'''trt'''</SPAN>
|-
|| <span style="color: #C00000">'''.acq'''</SPAN>
|| Once the processing finished an <span style="color:#C00000">'''.acq'''</SPAN> file will be generated in the same folder by the Sending Service in order to confirm the transmission:

'''FileName.ext_YYYYMMDDhhmmssmmm.'''<span style="color:#C00000">'''acq'''</SPAN>

|-
||<span style="color: #C00000">'''.err'''</SPAN>
||An <span style="color: #C00000">'''.err</SPAN> file is created in case or an error:

'''FileName.ext_YYYYMMDDhhmmssmmm'''<span style="color:#C00000">'''.err'''</SPAN>

Please open this file and analyse the error message.

|-

|}

</div>
<br/>

== Feedback files (Replies folder) ==

For some reporting, the administration will give you more detailed feedback. In this case, those feedback will replace the corresponding ones in the previous section.

By default, <u> feedback files</u> are dropped into <span style="color:#C00000">'''Replies'''</span> sub-folders. <span style="color:#C00000">'''Replies'''</SPAN> folders are created dynamically in the initial transmission folder of the files. They only appear when feedback files, sent by the supervisory authorities, have to be stored. If the folder is deleted, it will be automatically recreated upon receipt of new feedback files.

The name and location of the <span style="color:#C00000">'''Replies'''</SPAN> folder may be configured differently from the implementation of the solution with your company’s project coordinator [[Sending_Service#Configuration|=> Configuration .properties file.]]

<div style="text-align: left;">
{| border="1" cellspacing="2" cellpadding="10"
|-
! scope="col" | '''Autority'''
! scope="col" | '''Description'''

|-
||<span style="color: #C00000">'''CSSF'''</SPAN>
||Feedback files generated and sent by the CSSF.

Please click the picture below to access the '''Naming convention for CSSF reportings''' document:

[[File:FBR CSSF.png|500 px|link=http://www.cssf.lu/fileadmin/files/Reporting_legal/transport_securisation_reporting/Convention_de_nom.pdf]]

|-
||<span style="color: #C00000">'''BCL'''</SPAN>
||Feedback files generated and sent by the BCL.

The BCL sends feedback with the following naming convention :

FDBTECH_[OK/KO]_[YYYYMMDD]_[SENT FILE NAME]_[RANDOM CARACTERS].xml

With
* [OK/KO] : replaced either by OK (if the files has been transmitted and processed successfully) or KO (if there has been an error)
* [YYYYMMDD] : replaced by the date of the feedback
* [SENT FILE NAME] : replaced by the complete name of the original file (including it's extension)
* [RANDOM CARACTERS] : replaced by a random and unique caracters.

|-
||<span style="color: #C00000">'''ACD'''</SPAN>
||Feedback files generated and sent by the ACD.

ACD's feedback files are available in the sub-folder "Replies". For example, /ServiceDeposant/ReportingDiffusion/FATCA/Replies/

Each feedback has a specific status which is available in the file name: ACK, NAK, VAL, WAR, ERR (Cf. Status feedback ACD).

Example feedback from ACD :

FATCA_20150520080022_F0_2016_B_1970010112345_006M8M.00000.LE.442_P_ack.xml

FATCA_20150520080023_F1_2016_B_19700202123_ZZLRV4.99999.SL.442_T_ack.xml

The "Replies" folder is created upon feedback receipt. Please check the Sending Service's configuration if the "Replies" folder is not available. In the configuration file (properties file), the variable corresponding to "Configuration of connection for feedback" and the one corresponding to "Configuration of connection for authority acknowledgement" should be set to "up".
|}

* '''For other reporting''' (08/371 / VNI...), '''there is no additionnal acknowledgment'''. <br>
This means that only <span style="color: #C00000">'''acq'''</span> will be created. <br><br>

<u>'''Conclusion'''</u> : <span style="color: #C00000">'''Checking that both trt and acq files were generated is a good way to ensure the good working of the Sending Service'''</span>. Doing this way, you can be sure that your data was correctly sent and '''e-file will be in charge of forwarding them to authoritites'''.

= Sending Service versions and updates =

Please be informed that our system is able to check the version of the program you are running. This information is sent to our database when the service is launched.

Please note that the <b>''RELEASE_README.txt''</b> file, located at the root folder provides you information on the different Sending Service versions.
The example below indicates that the Sending Service version 4.5.6 is being used:
[[File:SD evol.png| 800 px]]

In case of major Sending Service changes, our [[How to contact us|'''Client Support & Operations Desk''']] will notify you by sending an INFO-email to your local e-file administrator.

= Functional testing and test environment =

In fact, it is not necessary to test the working of the Sending Service by performing a test sending.

Indeed, all '''technical checks''' are performed during the startup process.

In other words, if the startup process does not generate any error message, then the Sending Service is running properly.

* Launch the Sending Service through the dos <b>''run.bat''</b> file or through the Windows Service.
* '''Check the log files''' generated in the <b>''log''</b> folder of Service Deposant.
* The Sending Service is running properly if the '''error.log file''' is empty or if it does not contain any line in relation to the starting process.

<u>'''Remark'''</u> : If a problem occurs after this check, it would certainly be a functional problem or could also be linked to the e-file configuration.

In this case, we recommand to '''check the ''.err'' file''' automatically generated during the sending process.

If you want to install a '''test environment''' in order to validate the your source files or to anticipate a migration procedure, please follow the steps below:

* '''Duplicate the production Sending Service''' by copying the whole ''Service Deposant'' folder to another location.
* '''Adjust the properties file''' to redirect the service to our test environment : Homologation. <b>''e-file.hostname''</b> = <span style="color: #C00000">'''homologation.e-file.lu'''</span>

Please note that, if the user login may remain the same, the password will be changed in our test environment.
Feel free to set a new password

Do not forget to '''modify the path''' to your test files if these ones are stored in a specific location.

Finally, to identify cleary both Windows services, you must adjust the parameters used to identify the Windows Service name : <b>''wrapper.app.long.name''</b> and <b>''wrapper.app.name''</b>

* <span style="color: #C00000">'''Relaunch the Sending Service installation'''</span>

= Common Problems =

== The service does not start ==

Please refer to following procedure if a Sending Service, launched through <u>the Windows Services</u> does not start in order to analyze the origin of the problem.

<br><br>
<u>'''Attempt to start it with the DOS command line'''</u><br>
<br>
* Open a '''DOS''' window and make sure to have '''administrator rights''' on the computer (''Start>run : cmd'')
* Move to the folder where the sending service is installed
* '''Run the command : <span style="color: #C00000">''run.bat''</span>'''
<br>

'''If the sending service runs properly''' through this DOS command, without generating error logs, we recommand to follow [[Sending Service#IdSolve|this solving method]]'''.<br>
<span style="color: #C00000">'''Otherwise, a log analysis is necessary'''</span><br><br>

=== Log Analysis===

The <b>''error.log''</b> file located in the <b>''log''</b> folder at the root of Sending Service, contains the error trace causing this dysfunction.<br>

'''You will find below the most common known problems.'''<br>
<br>
In all cases, we are at your disposal to assist you in this analysis. Feel free to contact our <span style="color: #C00000">'''[[How to contact us|'''Client Support & Operations Desk''']].'''</span><br>

==== Network Problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Error when webservice's call 'obtenirVersionsDocument'.Unrecognized SSL message, plaintext connection.</span><br><br>

<u>'''Solving Method'''</u><br>
* Check the proxy parameters of your properties file
* '''Relaunch the sending service installation process''' so that the changes are taken into account.

<u>'''Error 2'''</u> : <span style="color: blue">java.net.ConnectException: Connection timed out: connect.</span><br>
<u>'''Error 3'''</u> : <span style="color: blue">Connection timed out: connect [TIP: The machine can be unauthorized by the proxy]</span><br><br>

<u>'''Solving Method'''</u><br>
* Check the configuration of your proxy with your network team : It must be correctly configured to allow outbound connections to our server [http://www.e-file.lu www.e-file.lu] HTTP and HTTPS.

==== Other time out problem====

<u>'''Error'''</u> : <span style="color: blue">Startup failed: Timed out waiting for signal from JVM.</span><br>

<u>'''Solving Method'''</u><br>
* '''Increase''' the value of <b>''wrapper.startup.timeout''</b> parameter from your properties file. As an example, increase from 300 to 600.
* '''Relaunch the sending service installation''' to take the changes in account.

This parameters indicates the duration allocated to the service startup. Is some cases, 5 mn may not be enough, particularly with slow proxy connections to e-file.

==== Administrator rights issue with Windows service ====
[[File:SDadmin.jpg]]

By default, a windows service runs through a '''non administrator system user'''.<br>
Depending on your architecture, it is possible that this user account has not enough rights to ensure a proper start of the Sending Service. (proxy issue for example)<br>

Then simply change this setting this way: <br>

<div id="IdSolve"></div>
<u>'''Solving Method'''</u><br>
* Open the '''Windows services''' window. (Start > Control Panel > Administrative tools > Services)
* Right click on the service named <b>''ServiceDéposant''</b>
* Select the <b>''Properties''</b> item
* Indicate an administrator user account and password in <b>''LogOn''</b> tag.
* Relaunch the service

== Errors are raised during sending ==

The generation of an <b>''.err''</b> file during the processing of your report indicates an issue during the sending.<br>

In this case,''' it is necessary to analyze the problem because the data could not be transmitted to the authorities.'''<br><br>

The <b>''.err''</b> file contains the explanation of the error that generates this dysfunction.<br><br>

'''You will find below the most common problems.'''<br>
In all cases, we are at your disposal to assist you in this analysis. Feel free to contact <span style="color: #C00000">'''[[How to contact us|'''Client Support & Operations Desk''']].'''</span><br>

==== Functional Problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Failed to validate XML</span><br>
<u>'''Error 2'''</u> : <span style="color: blue">All error indicating a data problem</span><br><br>

<u>'''Solving Method'''</u><br>
* '''Correct the source file''' according to the error messages indicated in the <b>''.err''</b> file.
* '''Resend the file'''.

==== User account problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Getting addressees information Une erreur est survenue lors de l'execution du Workflow</span><br>

<u>'''Solving Method'''</u><br>
* '''Link''' the sending service user account to the right '''User Group''' according to the kind of reporting your are trying to send. His profils should be <b>''SD with response''</b>

= Certificate Update =

Once your Luxtrust certificate is activate in E-file, you need to replace the new keystore in the sending service.

If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
In this case you can use a simplified process by '''<u>simply replacing the keystore:</u>'''
(-) Stop the Sending Service
(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
(-) Copy the newkeystore (to the sending service keystores folder.
(-) Rename this copy as the previous one.
(-) Restart the Sending Service

In case of a '''different kesytore password''', you '''<u>will have to reinstall the Sending Service</u>'''.<br>
Please find below what you need to do:
* Stop your sending service
* Copy your new keystore in the keystores folder of the Sending Service.
* Update the configuration: It is possible that your new Keystore has a different name than the previous Keystore therefore it is necessary to update the configuration.
'''E-file configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''keystore.path=@PROJECT_ROOT_PATH@/keystores/????.ks'''''
|style="width:20em"| path of the keystore (xxxx.ks)
|-
|}

* Install the sending service: To install the Sending Service, you have to click on the '''Install''' button. A pop-up window opens where you have to enter your passwords.

''Note : If you do not use a proxy, you can leave a blank for the proxy password''

[[File:Doc_SDInstaller_12.png|border|500 px]]

Once finished a pop-up windows opens stating that the installation has been successful:

[[File:Doc_SDInstaller_13.png|border|500 px]]

To start your Sending Service open the folder where you installed it and run the file '''run.bat''' or '''InstallServiceNT.bat''' if you want to install the Service as a '''Windows Service'''.

[[Sending Service#Installation as a Windows Service|=> Installation as a Windows Service]]

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

File:E-fileLuxtrustCertificateProcess.mp4

2026-05-06T15:08:53Z

Cso: Cso uploaded a new version of File:E-fileLuxtrustCertificateProcess.mp4

== Summary ==
Video tutorial

E-file Administration

2026-05-05T12:31:20Z

Cso: /* * keystore system, Luxtrust certificate, SSL security */

__NOTOC__
= e-file FAQ - Administrator's section =
<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

[[File:Administration module icon (Figure 2).png|300px]]

== Knowing the interface ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_am_I_allowed_to_do_as_an_administrator></span>
<div style="font-weight:bold;line-height:2.5;">What am I allowed to do as an administrator ?</div>
<div class="mw-collapsible-content">

The '''Administration module''' opens. Tabs are available in the '''e-file administrator''' module: (Figure 3).

[[File:Users, Groups and Certificates (Figure 3).png|900px]]

{|
|+
!'''Users tab'''
!'''Groups tab'''
!'''Certificates tab'''
!'''Sending service tab'''
!'''S3 keys tab'''
|-
|
*[[#How_can_I_create_a_new_e-file_user|Create a new user]]

*[[#Managing_permission_on_user's_account|Assign groups to a user]]

*[[#Explore_the_interface's_items|Force password change]]

*[[#Explore_the_interface's_items|Lock/ unlock user]]

*[[#Explore_the_interface's_items|Delete user]]
|
*[[#Groups'_management|User management at group level]]

* Add users to a group

* Assign a group to users

* Manage user profiles at group level
|
* [[#How_do_I_order_a_LUXTRUST_certificate|Order a new '''Luxtrust certificate''']]

* [[#How_do_I_order_a_LUXTRUST_certificate|Renew your Luxtrust certificate]]

* [[#How_do_I_activate_my_LUXTRUST_certificate_into_e-file|Activate Luxtrust certificate]]
|
:''Sending service user's management :''

* [[#What_about_the_Sending_Service_account|Assign groups to the '''Sending Service user''']]

* [[#What_about_the_Sending_Service_account|Subscribe the Sending Service user to '''alerts''']]
:''Sending service user's management - V2 :''
* [[Sending_Service_java-less_version|Sending service java-less version]]
|
* [[#S3_system|'''S3''' key management]]
|}
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Explore_the_interface's_items></span>
<div style="font-weight:bold;line-height:2.5;">Explore the interface's items</div>
<div class="mw-collapsible-content">

:<u>'''Explanations'''</u>

<imagemap>
File:AdminInterface.png|center|1200px|alt=clickable image : admin interface
rect 83 11 944 69 [[#hereExplainAction| This is the tabs' menu ]]
rect 1812 154 1686 93 [[#hereExplainAction| Click to create a new user's account ]]
rect 237 234 28 168 [[#hereExplainAction| The vertical menu can be reduce ]]
rect 238 281 31 239 [[#hereExplainAction| Here you can set who will receive some e-mail notifications in relation with the administration ]]
rect 256 186 1286 232 [[#hereExplainAction| You can filter the list on a group's members or a profile]]
rect 406 345 450 375 [[#hereExplainAction| The crown indicates an administrator]]
rect 793 285 878 300 [[#hereExplainAction| By hovering over their headers, text columns can be sorted]]
rect 1618 281 1748 332 [[#hereExplainAction| Each line allow its actions among : * Edit, * Force password, * Lock/Unlock, * Delete]]
rect 1618 337 1647 369 [[#hereExplainAction| Edit the user details or group permissions]]
rect 1652 337 1681 369 [[#hereExplainAction| Force password change : an email is sent to the user for him to reset]]
rect 1687 337 1711 369 [[#hereExplainAction| Lock or Unlock the account. The icon is greyed out for new users.]]
rect 1716 337 1743 369 [[#hereExplainAction| Delete the account. You can not delete administrators, ask us.]]
desc none
</imagemap>
</div>
</div>

== Accounts' management ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How many users can I create ?</div>
<div class="mw-collapsible-content">
:You can create as many as users' accounts you need. It is free of charge.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_create_a_new_e-file_user></span>
<div style="font-weight:bold;line-height:2.5;">How can I create a new e-file user ?</div>
<div class="mw-collapsible-content">

:Enter the administration module [[File:SDjl_8.png|150px]], you should be on the 'users' tab.
:Click the '''Create a user''' button [[File:Create_a_user_button_(Figure_5).png|150px]]

:The '''Create a user''' window pops up. Complete the form as shown in the figure below and click the '''Create''' button.

<imagemap>
File:4CreateUser.png|center|900px|alt=clickable image : create user form
rect 1081 737 41 282 [[#hereCreatUser|All fields are mandatory]]
rect 991 835 42 770 [[#hereCreatUser|You must choose a first group and a user's profile ]]
rect 475 856 637 914 [[#hereCreatUser|Click here to validate]]
rect 1363 993 1216 939 [[#hereCreatUser|Click here to cancel]]
circle 1355 58 34 [[#hereCreatUser|Click here to cancel]]
desc none
</imagemap>

:<span style="color: #C00000">'''Important note : You do not have to create a password for the user, an automatic mail will be sent to the new user to activate his account and create a password</span>'''

:The '''Create a user''' window closes and you return automatically to the '''Users List''' screen.

:At the same time a '''confirmation''' window pops up on the top of the screen indicating that the user creation was successful.

:[[File:User creation was successful (Figure 7).png|800px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_an_existing_account's_e-mail></span>
<div style="font-weight:bold;line-height:2.5;">How can I change an existing account's e-mail ?</div>
<div class="mw-collapsible-content">

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon.

[[File:SDjl_8.png|300px]]

<u>'''Step 2</u>:'''

The '''Users List''' screen opens. Click the Edit button on the line of the account to be changed.

[[File:AdminModuleChangeEmail.png|border]]

<u>'''Step 3</u>:'''
Click the detail tab, then Edit button

[[File:AdminModuleChangeEmail2.png|border|400px]]

<u>'''Step 4</u>:'''
Change the e-mail then click Validate button

[[File:AdminModuleChangeEmail3.png|border|400px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_about_the_Sending_Service_account></span>
<div style="font-weight:bold;line-height:2.5;">What about the Sending Service account ?</div>
<div class="mw-collapsible-content">

As an administrator, you can manage the permission for the sending service account too.
See more information upon the [[Sending_Service_home|sending service]]

<imagemap>
File:SDPermission.png|center|800px|alt=clickable image on SD permission
rect 385 1 615 68 [[#hereSDPerm| Click the sending service tab ]]
rect 7 172 192 211 [[#hereSDPerm| In the vertical menu, choose the proper version of your sending service ]]
rect 1370 310 1421 374 [[#hereSDPerm| On the matching line, click the edit icon ]]
rect 1378 442 1473 384 [[#hereSDPerm| A panel opens from the right, click the edit button ]]
rect 248 545 1231 778 [[#hereSDPerm| You can add or delete a group, the profile is always 'Service Déposant', subscribe to receive the authorities' feedbacks. ]]
desc none
</imagemap>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Managing_permission_on_user's_account></span>
<div style="font-weight:bold;line-height:2.5;">Managing permission on user's account </div>
<div class="mw-collapsible-content">

See: [[#How_do_I_assign_groups_and_profiles_to_users|How do I assign groups and profiles to users ?]]
</div>
</div>

== Groups' management ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_an_e-file_group></span>
<div style="font-weight:bold;line-height:2.5;">What is an e-file group ?</div>
<div class="mw-collapsible-content">

In e-file, a group allows you to manage permissions for similar reports in terms of type, circulars, costs or technical constraints.

Instead of managing groups for a user, the '''Groups''' tab allows you to manage users for a given group.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Which_group_do_I_need></span>
<div style="font-weight:bold;line-height:2.5;">Which group do I need ?</div>
<div class="mw-collapsible-content">

<div style="height:500px; width:auto; overflow-y:scroll">

{| class="wikitable filterable mw-collapsible sortable"
|+ <span style="white-space:nowrap">Which group for my report ?</span>
|- <div style="font-weight:bold; vertical-align:top; position:sticky;top:-1px;z-index:10">
! style= "background-color:#52BBBD; color:#FFF" | Concerned companies
! style= "background-color:#52BBBD; color:#FFF" | Report<br /> naming convention
! style= "background-color:#52BBBD; color:#FFF" | Details
! style= "background-color:#52BBBD; color:#FFF" | Authority
! style= "background-color:#FF7F27; color:#FFF" | e-file Group
! style= "background-color:#52BBBD; color:#FFF" | Sending way

</div>

|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| NOTREP
| Notification procedures to be followed by a UCITS governed by Luxembourg law wishing to market its units in another Member State of the European Union
| CSSF
| (-) Gestion documentaire<br /> (-) Dashboard<br /> (-) Matrice d'enregistrement et de distribution
| S3
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Monthly financial information for guaranteed funds
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| -
| Yearly financial information
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Interventions on the futures and options markets
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0103
| Monthly statistical balance sheet for money market funds (MMF)
| BCL
| Station Finesti
| KS
|-
|Investment Funds
|S0404
|Country of Marketing
|BCL
|Station Finesti
|KS
|-
|Investment Funds
|S0220
|Quarterly Financial Information
|BCL
|Station Finesti
|KS
|- style="vertical-align:bottom;"
| Investment Funds
| TPTOBS
| Monthly Security by security reporting for investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| SIF:<br /> (-) Prospectus (PC)<br /> (-) Offering document (DE)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| SIF Law 2007:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report SIF (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (PM)<br /> SICAR:<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Auditor report<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| Auditor report<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI:<br /> (-) Prospectus (PC)<br /> (-) Simplified prospectus (PS)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting (AIF Manager)
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| AnaCredit:<br /> Collection of granular credit and credit risk data
| BCL
| Reporting Anacredit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0218-L
| Quarterly statistical balance sheet of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S0219-L
| Information on valuation effects on the balance sheet of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0403-L
| Annual Premiums, claims and commissions of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| TPTASS
| Monthly Security by security reporting of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SHSGRP
| «SHS-Group» report:<br /> Statistics on holdings of securities by reporting banking groups
| BCL
| SHS reporting
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0001
| Daily deposit
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0101
| Monthly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0104
| Adjustments due to valuation effects|
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0105
| Information on interest rates in EUR
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0108
| Information on securititation<br /> transactions launched<br /> by credit institutions
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0109
| Information on CNY (renmibi) operations
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0205-L
| Quarterly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0205-N
| Quarterly statistical balance sheet<br /> of credit institutions -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0208
| Real estate loans for<br /> Lxuembourg buildings
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0209-L
| Staff report -<br /> Luxembourg entity
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0209-N
| Staff report -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0302
| Non balance sheet information
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit Report on AML/CTF
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Circ. 18/697 annexe1
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Annual Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Annual report consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| AC Member List
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Compliance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Governance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Internal Audit Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| ICAAP
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ICAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Branch or Specific Participation
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Long Form Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Reconciliation LuxGAAP FINREP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Management Letter Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit report on rules of conduct
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Management Letter
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Head quarter annual report
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Risk Control Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Report on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Recovery Plan
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Results Distribution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Single Customer View
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Table on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Financial Institutions - Common Reporting Standard (CRS)
| CRS
| Automatic exchange of<br /> financial account information<br /> on a global level
| ACD
| Reporting CRS
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Quarterly reporting on the<br /> financial health of the branches<br /> parent entities
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Residential credit deposits
| CSSF
| Enquêtes
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DCOR
| style="vertical-align:bottom;" | Reporting Entity<br /> B: Credit institution
| style="vertical-align:bottom;" | CSSF
| Enquetes
| style="vertical-align:bottom;" | S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DCOR
| Reporting Entity<br /> P: PFS
| CSSF
| Enquetes
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Residential real estate market
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Stress test in order to assess<br /> the interest rate risk<br /> arising from non-trading<br /> book activities
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0101
| Customer transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0110
| Stock taking of payment accounts in bank money
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01100
| Payment services provided by e-money institutions and payment institutions without the provision of payment accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0111
| OTC cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01110
| Payment initiation services (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01110-F
| Payment initiation services (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0112
| Transactions via telecommunication, digital or IT device
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0113
| Credits to the accounts by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0114
| Debits from the account by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0102
| Interbank transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0120
| Customer Credit transfers sent (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0120-F
| Customer Credit transfers sent (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01200
| Stock of issued payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01201
| Stock of distributed payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0121
| Customer credit transfers received
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01210
| Stock of terminals by terminal type
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01220
| Stock of accounts (except e-money accounts)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01221
| Stock of e-money accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01222
| Stock of accessed accounts - account information services (AIS)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01230
| Number of customers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0103
| Domiciliations
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130
| Direct debits - reporting as creditor's PSP (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01300-F
| Losses due to fraud per liability bearer
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130-F
| Direct debits - reporting as creditor's PSP (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0131
| Direct debits - reporting as debtor's PSP
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0104
| Inventory cards / terminals
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0140
| SEPA R-transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0141
| Interbank payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0142
| Intermediated payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0105
| Card transactiosn (Issuing part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0150
| Card transactions with cards issued by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0150-F
| Card transactions with cards issued by resident PSPs (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0151
| Electronic card transactions with cards issued by resident PSPs, split by Merchant Category Codes (MCC)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0152
| Card transactions acquired by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0152F
| Card transactions acquired by resident PSPs (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0153
| Fundings and withdrawals related to prepaid cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0106
| Card transactiosn (Acquiring part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0160
| Cheques and money remittances (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0160-F
| Cheques and money remittances (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0107
| Cheques and money orders
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0170
| Over-the-counter (OTC) cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0108
| Electronic money scheme
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0180
| Book entries
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0109
| Card based e-money schemes
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0190
| Fundings and withdrawals in e-money (except prepaid cards)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0191
| E-money transfers (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0191-F
| E-money transfers (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Fonds de garantie<br /> des dépôts Luxembourg<br /> (FGDL)
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Identification of third-party<br /> funds held and incorporated in the balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Capital adequacy of<br /> payment institutions
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Profit and loss accoount
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Identification of third-party<br /> funds held and incorporated<br /> in the balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Statement of<br /> authorised reinvestments
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Capital adequacy of<br /> electronic money institutions
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Profit and loss account
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Analysis of shareholdings
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Institutions - Foreign Account Tax Compliance Act (FATCA)
| FATCA
| Foreign Account Tax Compliance Act Reporting
| ACD
| Groupe FATCA
| KS
|-
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| (-) Letter of explanation (LE)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Annual report of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| FRCREP
| Information on participating interest<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| FRCREP
| Information on staff costs and taxes<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| LCRDAX
| CSSF
| Rapport FINREP
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Companies
| S0216
| Quarterly statistical balance of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| S0217
| Transactions of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Key Investor Information Document<br /> (-) O: OPC Law 2010 and Loi 2007<br /> (-) K: SICAR<br /> (-) V: non-reglem.
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Long Form reports (UCI Law 2010)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| SGOREP
| (-) SG 1A: Financial situation<br /> (-) SG 1B: Profit and loss account<br /> (-) SG 1C: Table relating to other activities<br /> (-) SG 2: Other activities<br /> (-) SG: Personnel Table relating to staff
| CSSF
| Rapport Société de Gestion
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007<br /> (-) K: SICAR
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| Articles of Incorporation of UCITS<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Management Regulations of UCITS<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom;"
| MiFID II / MiFIR
| TAFREP
| Article 26 of Regulation<br /> No 600/2014:<br /> Obligation to report transactions<br /> (Markets in financial instruments => MiFIR)
| CSSF
| Report TAF-MIFID
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Other reporting CSSF BCL
| OTHREP
| Other reporting
| CSSF
| Reporting OTHER (CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| BOP101
| Balance of payments reporting
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BOP102
| Cross-border payments<br /> executed for the account<br /> of the resident counterparts
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| PSFREP
| Reporting population:<br /> (-) Investment firms<br /> (-) Specialised PFS<br /> (-) Support PFS
| CSSF
| Rapport PSF
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| N01 (Comp); N02 (Comp); N03 (Comp);<br /> N04 (Comp); N05 (Réviseur); N06( Réviseur);<br /> N07 (Comp); N08 (Comp); N09 (Comp); N10 (Comp); N11 (Comp); N12 (Réviseur);<br /> N13<br /> (Comp);<br /> N14<br /> 'Comp)
| Rapports narratifs
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CSDREP
| Reporting CSDR:<br /> Introduction of quarterly internalised settlement reporting requirements<br /> pursuant to Article 9(1) of EU Regulation No 909/2014 (CSDR)
| CSSF
| Reporting CSDR-9
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BNNNN
| List of head offices, agencies,<br /> branches and representative offices
| CSSF
| Reporting EDIFACT
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Institutions for Occupational Retirement Provision
| SUFREP
| Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019
| CSSF
| Reporting IORP
| KS
|- style="vertical-align:bottom;"
| Money Market Funds (MMF)
| MMFREP
| • According to Article 37 of Regulation (EU) 2017/1131, the manager of a MMF must report information to the competent authority (CSSF) of the MMF, at least on a quarterly basis or - for MMF with assets under management of less than Eur 100 million - on at least an annual basis.<br /> • The first quarterly report should be sent to the competent authority of the MMF no later than 30 days after the end of Q1 2020.
| CSSF
| Money market fund reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0112-L
| Indirect withdrawal and remittance of banknotes denominated in EUR through an intermediary
| BCL
| Reporting S1.12
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| TPTIBS
| Monthly security by security reporting of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| U11
| Monthly financial information UCITS and UCI
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBBL
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBBN
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBHN
| Security by security report–<br /> Off-balance sheet data–<br /> Non-resident
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBHR
| Security by security report–<br /> Off-balance sheet data–<br /> Resident customers
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| SIC
| Financial information to be submitted by investment companies in risk capital (SICARs)
| CSSF
| Reporting SICAR
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI Law 2010:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (MP)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S01; S02; S03; S04; S05;<br /> S06 (Réviseur); S07; S08;<br /> S09; S10; S11; S12; S13;<br /> S14; S15; S16; S17; S18;<br /> S19; S20; S23
| XBRL reports Solvency II
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| S0214
| Quarterly statistical balance
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Securitisation Vehicles
| S0215
| Transactions and write-offs/write-downs on securitised loans
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| TPTTBS
| Security by security reporting
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| UCIAR
| Reporting Entity<br /> A: Alternative Investment fund manager (AIFM)
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| UCIAR
| Reporting Entity<br /> B: Credit institution
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| UCIAR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| UCIAR
| Reporting Entity<br /> S: Management company
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| UCIAR
| Reporting Entity<br /> (-) P: PFS<br /> (-) I: Support PFS
| CSSF
| (-) UCIAR reporting
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Other reporting CSSF BCL
| OTXREP
| Various correspondence
| BCL
| Reporting OTHER (BCL)
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SPJ
| Notification and execution of court orders
| SPJ
| Perquisitions électroniques
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI)(FR)<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CFEREP
| ALMXXX
| CSSF
| Rapport COREP
| S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Long Form Report
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Management Letter
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0106
| Monthly statistical balance sheet for non-money market funds (non-MMF)
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| S0213
| Quarterly statistical balance sheet for non-MMF investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| CED
| Etat de situation relatif aux contrats en déshérence
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| CPR
| Compte rendu
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ESP
| Enquête spécifique
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| ETR
| Etat trimestriel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| FIR
| Fiche de renseignement
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| PDA
| Rapport PDAL (Procédure de Dissolution Administrative sans Liquidation)
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RAC
| Rapport actuariel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RDC
| Rapport distinct complémentaire du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RDI
| Rapport distinct du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RGO
| Rapport de gouvernance
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RLB
| Rapport LBCFT
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RRE
| Rapports sur le traitement des réclamations
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RSE
| Rapport distinct Solvabilité 2 de l'entreprise
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RSO
| Rapport distinct Solvabilité 2 du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ICS
| Yearly Survey on Covered Investment claims (SIIL)
| CSSF
| Enquête
| S3
|- style="vertical-align:bottom;"
| Insurance Corporations
| ROI<br /> DIN
| DORA Register of Information<br /> DORA Incident Reporting
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DPAAIF
| self-assessment <br /> questionnaire PDAOFI
| CSSF
| PDAOFI reporting
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| (-) ALM corep_alm_con.xsd<br /> corep_alm_ind.xsd corep_alm.xsd<br /> (-) LCRDA corep_lcr_da_con.xsd<br /> corep_lcr_da_ind.xsd corep_lcr_da.xsd<br /> (-) IRRBB irrbb.xsd
| CSSF
| Rapport COREP
| S3
|}

</div>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How can I get a missing group ?</div>
<div class="mw-collapsible-content">
If you think that the group you need is not available in your list, please [[How_to_contact_us|ask us]] to check and/or add it.
</div>
</div>
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_manage_users_at_group_level></span>
<div style="font-weight:bold;line-height:2.5;">How can I manage users at group level ?</div>
<div class="mw-collapsible-content">

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon (Figure 21).

[[File:SDjl_8.png|400px]]

(Figure 21)

<u>'''Example'''</u>:

If you want to know the users to which the group '''Group FATCA''' has been assigned or if you want to add a new user to the group, please follow the instructions below.

<u>'''Step 1</u>:'''

Press the '''Groups''' button. The '''Groups list''' page opens. All groups assigned to your company are shown here (Figure 22).

[[File:3GroupList.png|800px]]

(Figure 22)

<u>'''Step 2</u>:'''

Click the '''Edit groups''' icon [[File:EditGroupSD.png|20px]] in order to view all the users assigned to '''Groupe FATCA''' group (Figure 23).

[[File:2EditGroup.png|800px]]

(Figure 23)

The '''Group detail''' page opens. Here you can find detailed information on the '''Group FATCA''' (e.g. Status date, number of inactive users, number of locked users) (Figure 24).

[[File:GroupDetailPage.png|500px]]

(Figure 24)

<u>'''Step 3</u>:'''

Press the '''Users''' button (Figure 25)

[[File:GroupDetailUsers.png|500px]]

(Figure 25)

The Group detail / Users page opens. All users assigned to the '''Group FATCA''' are listed here(Figure 26).

[[File:GroupUsrsList2.png|600px]]

(Figure 26)

<u>'''Step 4</u>:'''

Press the '''Edit Users''' button [[File:EditUserButton.png|100px]] (Figure 27)

[[File:EditUsersGroup.png|600px]]

(Figure 27)

The '''Users''' page opens in '''Edit mode''' (Figure 28)

[[File:UsersEditGroup.png|600px]]

(Figure 28)

The following actions can be done here:

1. '''ADD A USER'''. Select the user and his profile you want to add.

2. Change the '''Profile''' of the user

3. Delete the '''User'''

4. Once you have made your changes, press the VALDATE CHANGES button [[File:ValidateChanges.png|100px]]

The '''Users''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a confirmation window pops up on the top of the screen indicating that the assignment was successful (Figure 29).

[[File:AssignmentsSaved.png|800px]]

(Figure 29)
-------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_assign_groups_and_profiles_to_users></span>
<div style="font-weight:bold;line-height:2.5;">How do I assign groups and profiles to users ?</div>
<div class="mw-collapsible-content">

<u>Example</u>:

If a user has to send '''FATCA reportings''' to the authority, the e-file administrator must assign the <u>group</u> '''Rapport FATCA''' and the <u>profile</u> '''Manager''' to the user.

<u>'''Step 1</u>:'''

Open the '''User management''' screen in the '''Users''' tab and click the '''Edit''' [[File:EditGroupSD.png|20px]] icon of the user to whom you want assign [[E-file_Administration#Which_group_do_I_need|'''groups''']] and a specific [[E-file_Administration#User_profiles |'''profile''']] (Figure 11).

[[File:A specific profile (Figure 11).png|900px]]

(Figure 11)

<u>'''Step 2</u>:'''

The '''User details''' screen opens. Click the '''Groups''' button (Figure 12).

[[File:2AddGroup.png|500px]]

(Figure 12)

<u>'''Step 3</u>:'''
The '''User details / Groups''' screen opens. Click the '''Edit button''' (Figure 13).

[[File:2GroupDetails.png|500px]]

(Figure 13)

<u>'''Step 4</u>:'''

The '''User details / Groups''' screen opens in '''Edit''' mode (Figure 14).

Click the '''ADD A GROUP''' button [[File:AddGroup.png|100px]], select the [[E-file_Administration#Which_group_do_I_need|'''groups''']] and '''profile''' you want to assign and click the '''Validate''' button.

[[File:4Add group.png|800px]]

(Figure 14)

The '''User details / Groups''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a '''confirmation''' window pops up on the top of the screen indicating that the group assignment was successfully saved (Figure 15).

[[File:AssignmentsSaved.png|800px]]

(Figure 15)

Please be informed that you can find detailed information on all groups on our Wikipage [[E-file_Administration#Which_group_do_I_need|''''e-file Administrator FAQ'''']]; column <u>e-file user account: "groupe"</u>.

=== User profiles ===

====Administrator (EN)/ Administrateur (FR)====

The Administrator profile allows the e-file administrator to order and activate LuxTrust certificate(s), manage user accounts, groups, user profiles, lock and un lock user account.

==== Guest (EN) */ Visiteur (FR) * ====

* The Guest can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Guest cannot submit reports or documents via e-file.

====Manager (EN)/ Responsable (FR)====

* The Manager can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Manager can submit reports linked to his group(s) via e-file.

====Operator (EN) */ Opérateur (FR) * ====

* The Operator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* The Operator submit reports linked to his group(s) to validation by a Validator.

====Validator (EN) */ Valideur (FR) * ====

* The Validator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* He validates or rejects reports awaiting for validation linked to his group(s).

(*) Available depending the group
---------------
</div>
</div>

== Security's management ==

<span id=keystore_system></span>
=== * keystore system, Luxtrust certificate, SSL security ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_order_a_LUXTRUST_certificate></span>
<span id=LUXTRUST_certificate_purchase_order></span>
<div style="font-weight:bold;line-height:2.5;">How do I order a LUXTRUST certificate ?</div>
<div class="mw-collapsible-content">

You can find a video tutorial <b> <u>[[Media:E-fileLuxtrustCertificateProcess.mp4| here]]</u> which summarises the below process</b>

Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>
Prior your first filing you will have to order and activate a Luxtrust certificate.<br>
The only certificate authorised for the file encryption by the reporting entity are '''SSL certificates''' from the certification authority [https://www.easyssl.lu/?product=e-file LUXTRUST].

Please check the [[Transmission_Module#System_requirements|system requirements]] to run the e-file applications.

=== Key and Certificate Request generation ===

Please be informed that during the next steps <span style="background:yellow"> <u>two files</u> </span> will be generated:

<span style="background:yellow"> 1- </span> the keystore file '''keystore.ks''' containing your new keys

<span style="background:yellow"> 2- </span> the certificate request file '''Certificate Request.csr''' containing a copy of your new keys. <u>This file must be uploaded on LUXTRUST's website during your purchase order</u> .

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate purchase order and its activation have to be performed on the same computer workstation.</span>'''

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 30).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 30)

<u>'''Step 2</u>:'''

Click the '''Certificates ''' button (Figure 31)

[[File:AdminModule_2.png|border|500px]]

(Figure 31)

<u>'''Step 3</u>:'''

The '''Certificates Management''' screen opens. Click the '''CERTIFICATE REQUEST - ACTIVATION MENU''' link (Figure 32).

[[File:AdminModule_3.png|border|1000px]]

(Figure 32)

<u>Result</u>: A new screen opens displaying GENERATE CERTIFICATE KEYS - BEFORE LUXTRUST WEBSITE ORDER on the left side of the page

<u>'''Step 4</u>:'''

Configure your keystore (Figure 33).

[[File:Configure_your_keystore.png|border|1000px]]<br>

(Figure 33)

a. <u>Select the keystore import method</u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, select '''Create a new keystore file''' option and indicate a keystore name.

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, you '''<u>must</u> '''select your '''curent keystore file''' by using the ''browse file'' or ''drag & drop'' feature to import it.

<span style="color: #C00000">'''Important note : in both case, the new keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

- File name: choose your keystore name, for example '''keystore.ks'''

- File type : .ks

b. <u>Password </u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, you have to define a brand-new '''keystore password'''.
A confirmation is required

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, e.g. its validity date expired, you <u>must</u> use the '''keystore password''' that had been created when you ordered the certificate for the '''very first time'''.

<span style="color: #C00000">''' Important note : the keystore password has to be shared with all e-file users who have to transmit encrypted documents or decrypt feedback files received from the supervisory authorities. </span>.

<span style="color: #C00000">''' Important note : if you loose your keystore password, you will have to generate a new key and order a new certificate. </span>

c. <u>Certificate request name (.csr)</u>

You have to define a name for the technical certificate request file required by Luxtrust, for example '''CertificateRequest.csr'''

<span style="color: #C00000">'''Important note : the certificate request will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

- File name: '''CertificateRequest.csr'''

- File type : .csr

<u>'''Step 5</u>:'''

Verify the Company information. (Figure 34) :

[[File:Company_information.png|border|1300px]]

(Figure 34)

The related fields will be pre-filled in with information we currently have in our system. Feel free to make changes if necessary.

<u>'''Step 6</u>:'''

Click the '''Generate keys''' button.

A window will pop up inviting you to download the Keystore file and Certificate Signing Request (Figure 35).

[[File:Keystore CSR download window.PNG|border|500px]]

(Figure 35)

You must click on each of the Download buttons in order to activate the OK button.<br>
Then click OK to clear the message window.

<span style="color: #C00000">'''Both keystore and certificate request files will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name as follows: <br>The name of the previous keystore + a timestamp displayed as yyyymm + onhold. <br><br>Example: oldname : MyKeystore.ks / new name : MyKeystore_202212_onhold.ks''' </span>

<span style="color: #C00000">'''Important note : we advise you to back up the keystore.ks and CertificateRequest files.''' </span>

=== Finalize your LUXTRUST purchase order ===

<span style="color: #C00000">'''Before to start order in the Luxtrust website make sure that you have process the previous part (Key and Certificate Request generation). </span>

-Open the [https://www.easyssl.lu/?product=e-file LUXTRUST easy SSL e-file website].

-Browse to SSL Certificate section and click the E-FILE icon
[[File:Sans titre.png|50px]]

-Choose the period of validity of your certificate and click the ORDER E-FILE button.

-If you do not have a LUXTRUST easy SSL e-file account you have to get registered.

-Once registered, complete the whole order form, upload your '''CertificateRequest<span style="background:yellow">.csr </span>''' file, accept the TERMS AND CONDITIONS and click the PLACE ORDER button.

-Shortly afterwards, you will receive an e-mail from LUXTRUST confirming your purchase order.

-Please follow all instructions provided in the e-mail and its PDF attachment (Send signed PDF by post with all required documents to the address indicated inside, process the payment etc.)

----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_activate_my_LUXTRUST_certificate_into_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How do I activate (integrate) my LUXTRUST certificate into e-file ?</div>
<div class="mw-collapsible-content">

The certificate file will be sent to the e-mail address you provided in your purchase order.

The extension of this file will be .txt, in order to prevent your firewall from blocking the attached file.

<u>'''Step 1</u>:'''

<span style="color: #C00000">'''Important note: save the file .txt on your computer workstation and <u>replace</u> the .txt extension by <span style="background:yellow">.cer </span> </span>

Double-click the <span style="background:yellow"> .cer </span> file. You should be able to see your certificate as shown below (Figure 36):

[[File:Certificate visual example.png|alt=Certificate example|377x377px]]

(Figure 36)

<u>'''Step 2</u>:'''

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate ordering and its activation have to be performed on the same computer workstation.</span>'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 37).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 37)

<u>'''Step 3</u>:'''

Click the '''Certificates ''' button (Figure 38).

[[File:AdminModule2.png|border|500px]]

(Figure 38)

<u>'''Step 4</u>:'''

Click the '''CERTIFICATE ACTIVATION – AFTER RECEPTION OF LUXTRUST CERTIFICATE''' link (Figure 40).

[[File:Certificate_activation.png|border|1500px]]

(Figure 40)

<u>'''Step 5</u>:'''

Configure your keystore (Figure 41).

[[File:Certificate_activation_steps.png | 1000px]]

(Figure 41)

a. <u>Select the Group you need to use (by default Principal)</u>

b. <u>Import the keystore that was generated at the same time as the Certificate Signing Request</u>
(from previous step )

c. <u>Enter the keystore password</u>

d. <u>Import the certificate you received from Luxtrust </u>

<u>'''Step 6</u>:'''

Click the '''ACTIVATE CERTIFICATE''' button.

A window will pop up and inform you that the activation has been done successfully.

Your keystore.ks is now updated. It contains your activated LUXTRUST certificate and your encryption keys.

[[File:AdminModule_15.png | 300px]]

'''Note''': The display and the position of the pop up may differ regarding the Web browser you are using

<span style="color: #C00000">'''Important note : the updated keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name : the name of the previous keystore + a timestamp displayed as yyyymm + completed.<br>Example: previous name : MyKeystore.ks / new name : MyKeystore_202212_completed.ks''' </span>

<span style="color: #C00000">'''Important note : if you loose your keystore and/or its password,you will have to generate a new encryption key and order a new certificate. </span>.
-------------

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_must_I_do_with_the_keystore></span>
<div style="font-weight:bold;line-height:2.5;">What must I do with the keystore ?</div>
<div class="mw-collapsible-content">

===Manual file transmission===

The activated keystore, containing your LUXTRUST certificate and your encryption keys must now be provided to the workstations of each e-file user.

<u>'''Step 1</u>:'''

Open the Transmission module

[[File:Icon1.png | 300px]]

<u>'''Step 2</u>:'''

[[File:Keystore selection After(1).PNG| 600px]]

===Automatic file transmission===

In the case you are using the [[Sending_Service|Sending Service]] for automatic file transmission, the activated keystore.ks must be provided as well.
----------------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_register_my_LUXTRUST_certificate_with_the_CSSF></span>
<div style="font-weight:bold;line-height:2.5;">How can I register my LUXTRUST certificate with the CSSF ?</div>
<div class="mw-collapsible-content">

For some reportings, the LUXTRUST e-file SSL certificate used by the reporting entity must be registered with the CSSF, before sending any files, according to the registration procedure described in the '''[https://www.cssf.lu/wp-content/uploads/Naming-convention.pdf#page=8 CSSF 23/833, naming convention part.]'''

The LUXTRUST e-file SSL certificate must be registered with the CSSF for the below reportings:</br>
(list extracted from [https://www.cssf.lu/fr/transport-et-securisation/#specifications-techniques Transport et sécurisation via les canaux de transmission externes])

* COREP/FINREP reporting
* ESP – Special enquiries
* SIC – SICAR reporting
* PFS – Reporting PFS and support PFS
* EDP – Payment institutions reporting
* EME – Electronic money institution
* SGO – Management companies reporting
* OPC – Fund XML reporting (O1.2)
* DOC – Non-structured electronic documents (circ. 19/731)
* OTH – Other
* OCB – Other reportings for CSSF and BCL
* SUF – XBRL reportings for subfund-based structured products (IORP)
* O4.x – Edifact report

[[Media:How to declare your Luxtrust certificate to the CSSF.pdf|=> e-file User Guide: CSSF Certificate registration]]
----------------
</div>
</div>

=== * S3 system ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_is_the_S3_digital_key_management_in_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How is the S3 digital key management in e-file ?</div>
<div class="mw-collapsible-content">

The CSSF has updated its submission methods to allow AIFMs to file specific regulatory reports via the CSSF’s API from 2nd November.
Please note, this is not the deadline to make the change, it is the point at which the new method is available to use. <br>
FE Fundinfo are ready to support you through the transition.
Your current setup in e-file will remain in place and only minor one-off changes are required from you to ensure the continuation of your existing functionality on e-file and future proof the communication method for all reporting and filing with the CSSF going forward.
<br><br>

<u>'''Explanation in context of AIFMD reporting</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/7273286345756229380 November 21st webinar in English] and the [https://c2rv804.na1.hubspotlinks.com/Ctc/ZO+113/c2RV804/VWQ8Fx5Hw7JyVdSL7w2rxckBW20x2Jc566MpmN31NNCl5nXHsW7Y9pgv6lZ3kLW8mzYxT1ZSlmLW7yCpDW2jmg69W73tZTZ5yBySkW7jL_zN8my412W9hGQQt71RszSVkgkWT3FF-R2W1VryJ67bk_NmW1RKWr345DTFjV1PBRM2KwkQsW4P0bYq6h4FhzW2Y0TlL8jm7QlW6N2qBz9lFm9yW1bNKCy1qGVgGW7dJWkQ8TTtG5N3kH6ptzC816W33qG8b10K_BtW8gQSgN4g3h5TW9h3bp34KXCJHV_q02d6BgPGWW5xJSX81p0bg6W8jK_6G221K5qW3_hsX93mN9kwW2RyrBr7f39YJW8v09kD7Cw1nxW37qD826JSxdcW4Rc7yD85pl3PW109fZz4mxLcHW26Y0Y03k4GNWW8zPXjF1t6bspW78yjPn71W4ftW8-MxR372T_w5V13CVl6qstVRW21LWhW2dlqL_W2Xs3ZP6K5mZ2W1THZsw1FrpXLW54G4QN27qB0BW3yXpwm7rd3qwW23mB7r301kH7W19MCT85QW6wbW218pPC2z-WjCVQRHvT30nLTNW1qM-sk29_0TFd2XXgW04 related presentation]

[https://attendee.gotowebinar.com/recording/2231697877960308483 Webinaire en français]

<u>'''Explanation in context of UCITS Cross-Border notification</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/2670031382955110830 December 12th webinar in English] and the [https://445778.fs1.hubspotusercontent-na1.net/hubfs/445778/FE%20fundinfo%20presentations/FSQ%20channel%20change_Webinar%2012%20December.pdf related presentation]

This new system works via a bucket system.<br>
There is one bucket for each filing context (i.e. Cross-border notification, AIFMD)<br>
The CSSF imposes a technical size limit for filing per bucket on 30 rolling days.<br>
Should you encounter any issue, feel free to contact us directly [[How to contact us|'''Client Support & Operations Desk''']] we will liaise with the CSSF.<br>

<br>
The below is a step-by step guide to appoint FE Fundinfo as a delegate within the CSSF’s eDesk platform, the easiest path to allow us to maintain our services. <br>
Once the set-up is complete you can continue to use your familiar eFile interface and do not need to interact with eDesk as this will all be channelled within your existing workflows in eFile.
<br><br>
To perform the set-up in eFile you have two options:
<br>

* You as IT expert import the S3 keys on eFile

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide for eDesk IT Experts to connect CSSF’S eDesk to FE Fundinfo’s eFile system''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Your entity’s appointed IT Expert will need to log into the IT Management
area of eDesk ([https://edesk.apps.cssf.lu/edesk-itmgt/s3/accesses here]). This must be using the same LuxTrust Device and
account that the IT Expert role was assigned to. Please note, that these
steps can only be implemented from the appointed IT Expert account
|
|-
|
Step 2
|
Once logged in, go to the ‘S3 ACCESS DASHBOARD’ at the top of the page,
which will take you to a screen similar to the below
|
[[File:02-S3Dashboard.png|S3Dashboard|800px]]
|-
|
Step 3
|
Select ‘Create Access’
|
[[File:03-S3CreateAccess.png|S3CreateAccess|800px]]
|-
|
Step 4
|
This will provide you with an option to select a ‘scope’ which will be the
reporting type you have been appointed as IT Expert for and select create:
<br>
[[#Correspondance table|You can refer to our correspondance table]]
|
[[File:04-S3CreateScope.png|S3CreateScope|800px]]
|-
|
Step 5
|
This will create a line in the S3 access dashboard with the report type, the
status (this should show ‘Granted’) and the date of this creation.
<br>
Each report type generates 3 codes on eDesk, (the Bucket code, the Access
Key, and the Secret Key). To reveal these keys, click the magnifying glass
with a ‘+’ icon under the actions column (located on the far right of the
screen).
|
[[File:05-S3Granted.png|S3Granted|800px]]
|-
|
Step 6
|
This will reveal the information about the who the access has been granted to, when and what report it is for. It will also provide details of the unique codes specific to the entity, report type and individual.
|
[[File:06-S3Access.png|S3Access|800px]]
|-
|
Step 7
|
Once the Keys have been generated, keeping your connection to eDesk open, in another window, open your efile environment. Log in using the efile Admin account for your entity and open the ‘Keys Management’ tab.
|
[[File:07-efileMenu.png|efileMenu|800px]]
|-
|
Step 8
|
Select ‘Add Key’ on the far right of the screen
|
[[File:08-eFileAddKey.png|eFileAddKey|800px]]
|-
|
Step 9
|
A pop out will appear and provide you with several drop down lists to
complete. Under ‘Scope’ you should choose the report type that you are
providing the Keys for. In this instance AIFMD should be selected.
|
[[File:09-eFileScope.png|eFileScope|800px]]
|-
|
Step 10
|
Returning to eDesk, copy the Bucket code, the Access key and Secret key
and paste each of these into the applicable boxes on efile.
|[[File:10-BucketCopy.png|BucketCopy|800px]]
|-
|}

===Correspondance table===
'''Please find the correspondence table of e-file and e-Desk scopes'''<br>

{| class="sortable" border="1" cellspacing="2" cellpadding="1"
|- <div style="position:sticky;top:-1px;z-index:10">
! scope="col" | '''Label scope in e-file'''
! scope="col" | '''Label scope in e-Desk'''
! scope="col" | '''CSSF reference'''
! scope="col" | '''Deadline'''
</div>
|-
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/AIFM_Reporting_Technical_Guidance.pdf AIFM reporting -Technical guidance]
| style="vertical-align:middle; color:#202122;" | 30 June 2024
|-
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_guide_notifications_CBDF.pdf User guide notifications CBDF]
| style="vertical-align:middle; color:#202122;" | 2nd January 2024
|-
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/cssf22_811eng.pdf CSSF 22/811]
| style="vertical-align:middle; color:#202122;" | 30 June 2023
|-
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSSF_CPDI_2440eng.pdf CSSF-CPDI 24/40]
| style="vertical-align:middle; color:#202122;" | 15 May 2024
|-
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures - SFO
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Precontractual_Data_Collection_-_practical-guide.pdf SFDR precontractual data collection]
| style="vertical-align:middle; color:#202122;" | 31 October 2023
|-
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures - SFPER
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Data_Collection_-_practical-guide.pdf SFDR UCI Data Collection]
| style="vertical-align:middle; color:#202122;" | 31 January 2024
|-
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Bank_prudential_reporting.pdf Bank prudential reporting]
| style="vertical-align:middle; color:#202122;" | 1st September 2024

|-
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Regulatory-documents-and-reports.pdf User Guide for Regulatory Documents and Reports]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Key-Information-Document.pdf User Guide for Key Information Document]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_U1.1.pdf Guidelines on the U1.1 reporting]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_Yearly_Survey_on_Covered_Investment_Claims.pdf Guidelines for the Yearly Survey on Covered Investment claims (SIIL)]
| style="vertical-align:middle; color:#202122;" | 17th January 2025

|-
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_SAQ_DPAAIF.pdf Guidelines on the self-assessment questionnaire PDAOFI]
| style="vertical-align:middle; color:#202122;" | 31st March 2025

|-
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2025/03/upcoming-evolution-in-the-electronic-visa-stamp-procedure-for-the-prospectuses-of-ucits-part-ii-ucis-sicars-and-sifs/ Procedure change for visa "stamp" prospectuses]
| style="vertical-align:middle; color:#202122;" | 1st April 2025

|-
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSDR9_Handbook.pdf User Guide Internalised Settlement Reporting Under Article 9 OF CSDR]
| style="vertical-align:middle; color:#202122;" | 1st July 2025

|-
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/MMFR_Handbook.pdf MMF reporting Handbook]
| style="vertical-align:middle; color:#202122;" | 1st September 2025

|-
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2026/01/iorp-reporting-circular-cssf-19-726-new-edesk-procedure/ new IORP procedure]
| style="vertical-align:middle; color:#202122;" | 15th January 2026

|}
---------------
</div>
</div>
</br></br>

===Special cases===
'''For Key Information Document (KID PRIIPs/KID) and Regulatory Documents and Reports scopes'''<br>
Due to the way the CSSF has implemented the third-party delegation process we have adapted our S3 scope import system in order to enable
</br>
the possibility for a client who is a service provider to onboard multiple S3 keys for the same scope on different Asset Managers / Self-managed funds / Filing entity based on the FSQ referential
</br></br>
To do so after having selected Key Information Document (KID PRIIPs/KID) or Regulatory Documents and Reports scope.<br>
You have to use the dedicated radio button Asset Manager, Self-Managed funds or Filing Entity
<br>
The list is automatically refreshed to only display third-party without S3 key onboarded.<br>
In case of a Filing Entity, the name of the Third party linked to the eFile user will be pre-filed (and can't be changed)<br>
[[File:AssetManager-SelfManaged-FilingEntity.png|Asset Manager, Self-Manged fund or Filing Entity|400px]]

To help you identifying which key has already been imported on eFile a dedicated page has been added in the S3 Keys Management module <br>
This page lists the already imported key for scope(s) allowing delegation. <br>
The Bucket owner (entity that owns the S3 key) and the Provider (entity who uploaded the S3 key on eFile) are displayed.<br>
[[File:DelegationList.png|S3 Key list|800px]]

* Grant us with the IT expert role to perform such changes for you
To start the process please send us an email to '''[mailto:cso.desk@fundsquare.net cso.desk@fundsquare.net]''' with both '''name''' and '''CSSF identification number''' of the entity you want we become IT Expert

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide on how to assign FE Fundinfo as a CSSF IT Expert on eDesk''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Log into [https://edesk.apps.cssf.lu/ eDesk] with the Advanced User account using your LuxTrust Device and Password. Please note that these changes can only be implemented from the Advanced User account
|
|-
|
Step 2
|
Once logged in, go to the top right corner of the screen, click on your account user name, and select ‘Entity Management’
|
[[File:02-EntityManagement.png|EntityManagement|800px]]
|-
|
Step 3
|
Now select ‘Access Requests’ from the tabs at the top of the screen:
|
[[File:03-AccessRequest.png|AccessRequest|800px]]
|-
|
Step 4
|
As FEfundinfo will have made a request to connect from our Fundsquare account, you will see us on a list of users requests to connect with your entity. You will be able to identify our request as it will be with the LuxTrust SN: <span style="color: #C00000">100115278245548987357</span>
|
[[File:04-LuxtrustSN.png|LuxtrustSN|800px]]
|-
|
Step 5
|
Once you have identified the FE fundinfo request from our Fundsquare account, you can go to the far right of the screen and select ‘ACCEPT ACCESS’ or ‘REJECT ACCESS’. Remember to only
accept requests and provide access to users you are associated with. You will need to ‘ACCEPT ACCESS’ on our request:
|
[[File:05-AcceptAccess.png|AcceptAccess|800px]]
|-
|
Step 6
|
Once you have clicked accept, go to the ‘Specific roles within entity’ tab:
|
[[File:06-SpecificRole.png|SpecificRole|800px]]
|-
|
Step 7
|
Under the ‘Specific roles within entity’ tab, on the right of the screen, click the ‘Add’ button:
|
[[File:07-AddSpecificRole.png|AddSpecificRole|800px]]
|-
|
Step 8
|
You will now be able to click on the ‘User’ box and select a user within the list of approved users connected with your entity. One of these will be FE fundinfo’s Fundsquare account, select this option and the user details will populate automatically:
|
[[File:08-FSQUser.png|FSQUser|800px]]
|-
|
Step 9
|
Now you can select a role for that user, in this case you will need to select IT EXPERT for FE fundinfo in the drop down selection and click save on the top right to make the change
|
[[File:09-ITExpert.png|ITExpert|800px]]
|-
|
Step 10
|
You have now completed all you need to ensure continued use of efile and secure submission of your reports to the CSSF! FE fundinfo will do the rest and can now ensure that the changing transmission methods gradually introduced by the CSSF over the next 18 months are updated as needed without any impact on you
|
|-
|}
----------------
</div>
</div>

::== Onboarding workflow map ==
''You can click on the picture.''
<imagemap>
File:Wkf_S3_onboarding.png|center|1500px|alt=clickable image : form description| titre
rect 106 355 277 452 [[E-file_Administration#You_as_IT_Expert | You as IT Expert ]]
rect 776 541 947 630 [[E-file_Administration#FE_Fundinfo_as_IT_Expert |FE Fundinfo as IT Expert]]
rect 1024 376 1193 482 [https://edesk.apps.cssf.lu/edesk-dashboard/homepage?lng=en eDesk User Guide ]
rect 477 530 646 691 [https://www.cssf.lu/wp-content/uploads/Methods-of-transmitting-reports-via-S3-Application-Programming-Interface-Technical-guidance.pdf S3 transmitting method ]
desc none
</imagemap>
-----------
</div>
</div>

=== * general security questions ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_the_local_e-file_administrator></span>
<div style="font-weight:bold;line-height:2.5;">How can I change the local e-file administrator ?</div>
<div class="mw-collapsible-content">

Each e-file administrator account is linked to a single email at a time.

3 cases :
* You have access to the account
:then change the email of the administrator by using the <b>administration module</b> and update the administrator account's owner (name, firstname). The new administrator will just have to request a new password.
* You have access to the administrator's e-mail box
:you can use the "forgotten password" button on https://www.e-file.lu to change the password and get access.
* You do not have access to the administrator account nor to the email of this account
:then for security reason you will have to follow this specific procedure:

::Your request must be sent by email and paper mail.

::The paper can be replaced by a mail with a scan of the letterhead paper => Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com].

<u>'''The request must be submitted on letterhead of your company and signed by a legal representative with the following information'''</u>:
*Administrator's login adminXXX
*The current email address which is linked to the administrator
*The new email address to link to the administrator
*A brief explanation of the reason why you need to change it
*Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com]'''

Once Fundsquare has received and checked your request we will update your email and send you the procedure to update the password.

If you have further questions do not hesitate to contact our [[How to contact us|'''Client Support & Operations Desk''']].

-----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_the_e-file_password_policy></span>
<div style="font-weight:bold;line-height:2.5;">What is the e-file password policy ?</div>
<div class="mw-collapsible-content">

[[File:Password.png|300 px]]

(Figure 42)

The password you will have to provide must follow the rules below:

*At least one upper and one lower case letter
*At least one number
*At least one special character from this list: ! # $ % & ( ) * + , . /: ; < = > ? ^ _ @ { | } [ ] ~
*At least 8 characters and at most 20

<u> Please note that </u>:

The validity of your password is not limited in time.

Our system blocks the user after 3 incorrect attempts and it is the e-file administrator who has to unblock the account.

Passwords are encrypted in our database and we do not keep them. You may re-use them.
-----------
</div>
</div>

== Being informed ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_important_information></span>
<div style="font-weight:bold;line-height:2.5;">How can I get important information ?</div>
<div class="mw-collapsible-content">

As an administrator, you will received all significant information regarding e-file changes, maintenance or enhancement through the e-mail address set up onto your account.
You can also manage some alerts through e-file, see the notifications system.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_custom_notifications></span></span>
<div style="font-weight:bold;line-height:2.5;">How can I get custom notifications ?</div>
<div class="mw-collapsible-content">

Please be informed that you can receive alert by email triggered by specific events.

<u>Example</u> : Court orders sent by the Luxembourgish judicial police [http://www.cssf.lu/fileadmin/files/Lois_reglements/Circulaires/Hors_blanchiment_terrorisme/cssf13_566eng.pdf (=> CSSF - Circular 13/566)]

If you want to be notified by email each time the Luxembourgish judicial police sends you court orders, you have to follow the steps below.

<u>'''Step 1'''</u> : Connect to e-file with your user credentials : '''https://www.e-file.lu/e-file/'''

<u>'''Step 2'''</u> : Select Update my profile

[[File:Select Update my profile.png |200 px]]

<u>'''Step 3'''</u> : Verify that your email address registered in your e-file account is valid.

[[File:Your e-file account is valid.png |400 px]]

<u>IMPORTANT :</u> if your email address is not valid, please ask your [[Administration#e-file_administrator_functions_.28e-file_v1.29|'''e-file administrator''']] to replace it by a valid one.

<u>'''Step 4'''</u> : Select Customize your notifications.

[[File:Customize your notifications.png |200 px]]

<u>'''Step 5'''</u> : Select group.

[[File:Select group555.png |400 px]]

<u>'''Step 6'''</u> : Select the Alert type.

[[File:Notification.png |500 px]]

<u>IMPORTANT :</u>

A green window will pop-up stating that the update has been saved.

<u>'''Optional Step 7'''</u> : Receive only your alerts and not the group's ones.

Ticking also the group box, the sends from other users of the same reports group will be ignored.

[[File:Alerte Notification.png |500 px]]

[[Category: FAQ e-file]]

----------------------
</div>
</div>

File:E-fileLuxtrustCertificateProcess.mp4

2026-05-05T12:29:53Z

Cso: Video tutorial

== Summary ==
Video tutorial

E-file Administration

2026-05-05T12:27:32Z

Cso: /* Security's management */

__NOTOC__
= e-file FAQ - Administrator's section =
<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

[[File:Administration module icon (Figure 2).png|300px]]

== Knowing the interface ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_am_I_allowed_to_do_as_an_administrator></span>
<div style="font-weight:bold;line-height:2.5;">What am I allowed to do as an administrator ?</div>
<div class="mw-collapsible-content">

The '''Administration module''' opens. Tabs are available in the '''e-file administrator''' module: (Figure 3).

[[File:Users, Groups and Certificates (Figure 3).png|900px]]

{|
|+
!'''Users tab'''
!'''Groups tab'''
!'''Certificates tab'''
!'''Sending service tab'''
!'''S3 keys tab'''
|-
|
*[[#How_can_I_create_a_new_e-file_user|Create a new user]]

*[[#Managing_permission_on_user's_account|Assign groups to a user]]

*[[#Explore_the_interface's_items|Force password change]]

*[[#Explore_the_interface's_items|Lock/ unlock user]]

*[[#Explore_the_interface's_items|Delete user]]
|
*[[#Groups'_management|User management at group level]]

* Add users to a group

* Assign a group to users

* Manage user profiles at group level
|
* [[#How_do_I_order_a_LUXTRUST_certificate|Order a new '''Luxtrust certificate''']]

* [[#How_do_I_order_a_LUXTRUST_certificate|Renew your Luxtrust certificate]]

* [[#How_do_I_activate_my_LUXTRUST_certificate_into_e-file|Activate Luxtrust certificate]]
|
:''Sending service user's management :''

* [[#What_about_the_Sending_Service_account|Assign groups to the '''Sending Service user''']]

* [[#What_about_the_Sending_Service_account|Subscribe the Sending Service user to '''alerts''']]
:''Sending service user's management - V2 :''
* [[Sending_Service_java-less_version|Sending service java-less version]]
|
* [[#S3_system|'''S3''' key management]]
|}
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Explore_the_interface's_items></span>
<div style="font-weight:bold;line-height:2.5;">Explore the interface's items</div>
<div class="mw-collapsible-content">

:<u>'''Explanations'''</u>

<imagemap>
File:AdminInterface.png|center|1200px|alt=clickable image : admin interface
rect 83 11 944 69 [[#hereExplainAction| This is the tabs' menu ]]
rect 1812 154 1686 93 [[#hereExplainAction| Click to create a new user's account ]]
rect 237 234 28 168 [[#hereExplainAction| The vertical menu can be reduce ]]
rect 238 281 31 239 [[#hereExplainAction| Here you can set who will receive some e-mail notifications in relation with the administration ]]
rect 256 186 1286 232 [[#hereExplainAction| You can filter the list on a group's members or a profile]]
rect 406 345 450 375 [[#hereExplainAction| The crown indicates an administrator]]
rect 793 285 878 300 [[#hereExplainAction| By hovering over their headers, text columns can be sorted]]
rect 1618 281 1748 332 [[#hereExplainAction| Each line allow its actions among : * Edit, * Force password, * Lock/Unlock, * Delete]]
rect 1618 337 1647 369 [[#hereExplainAction| Edit the user details or group permissions]]
rect 1652 337 1681 369 [[#hereExplainAction| Force password change : an email is sent to the user for him to reset]]
rect 1687 337 1711 369 [[#hereExplainAction| Lock or Unlock the account. The icon is greyed out for new users.]]
rect 1716 337 1743 369 [[#hereExplainAction| Delete the account. You can not delete administrators, ask us.]]
desc none
</imagemap>
</div>
</div>

== Accounts' management ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How many users can I create ?</div>
<div class="mw-collapsible-content">
:You can create as many as users' accounts you need. It is free of charge.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_create_a_new_e-file_user></span>
<div style="font-weight:bold;line-height:2.5;">How can I create a new e-file user ?</div>
<div class="mw-collapsible-content">

:Enter the administration module [[File:SDjl_8.png|150px]], you should be on the 'users' tab.
:Click the '''Create a user''' button [[File:Create_a_user_button_(Figure_5).png|150px]]

:The '''Create a user''' window pops up. Complete the form as shown in the figure below and click the '''Create''' button.

<imagemap>
File:4CreateUser.png|center|900px|alt=clickable image : create user form
rect 1081 737 41 282 [[#hereCreatUser|All fields are mandatory]]
rect 991 835 42 770 [[#hereCreatUser|You must choose a first group and a user's profile ]]
rect 475 856 637 914 [[#hereCreatUser|Click here to validate]]
rect 1363 993 1216 939 [[#hereCreatUser|Click here to cancel]]
circle 1355 58 34 [[#hereCreatUser|Click here to cancel]]
desc none
</imagemap>

:<span style="color: #C00000">'''Important note : You do not have to create a password for the user, an automatic mail will be sent to the new user to activate his account and create a password</span>'''

:The '''Create a user''' window closes and you return automatically to the '''Users List''' screen.

:At the same time a '''confirmation''' window pops up on the top of the screen indicating that the user creation was successful.

:[[File:User creation was successful (Figure 7).png|800px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_an_existing_account's_e-mail></span>
<div style="font-weight:bold;line-height:2.5;">How can I change an existing account's e-mail ?</div>
<div class="mw-collapsible-content">

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon.

[[File:SDjl_8.png|300px]]

<u>'''Step 2</u>:'''

The '''Users List''' screen opens. Click the Edit button on the line of the account to be changed.

[[File:AdminModuleChangeEmail.png|border]]

<u>'''Step 3</u>:'''
Click the detail tab, then Edit button

[[File:AdminModuleChangeEmail2.png|border|400px]]

<u>'''Step 4</u>:'''
Change the e-mail then click Validate button

[[File:AdminModuleChangeEmail3.png|border|400px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_about_the_Sending_Service_account></span>
<div style="font-weight:bold;line-height:2.5;">What about the Sending Service account ?</div>
<div class="mw-collapsible-content">

As an administrator, you can manage the permission for the sending service account too.
See more information upon the [[Sending_Service_home|sending service]]

<imagemap>
File:SDPermission.png|center|800px|alt=clickable image on SD permission
rect 385 1 615 68 [[#hereSDPerm| Click the sending service tab ]]
rect 7 172 192 211 [[#hereSDPerm| In the vertical menu, choose the proper version of your sending service ]]
rect 1370 310 1421 374 [[#hereSDPerm| On the matching line, click the edit icon ]]
rect 1378 442 1473 384 [[#hereSDPerm| A panel opens from the right, click the edit button ]]
rect 248 545 1231 778 [[#hereSDPerm| You can add or delete a group, the profile is always 'Service Déposant', subscribe to receive the authorities' feedbacks. ]]
desc none
</imagemap>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Managing_permission_on_user's_account></span>
<div style="font-weight:bold;line-height:2.5;">Managing permission on user's account </div>
<div class="mw-collapsible-content">

See: [[#How_do_I_assign_groups_and_profiles_to_users|How do I assign groups and profiles to users ?]]
</div>
</div>

== Groups' management ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_an_e-file_group></span>
<div style="font-weight:bold;line-height:2.5;">What is an e-file group ?</div>
<div class="mw-collapsible-content">

In e-file, a group allows you to manage permissions for similar reports in terms of type, circulars, costs or technical constraints.

Instead of managing groups for a user, the '''Groups''' tab allows you to manage users for a given group.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Which_group_do_I_need></span>
<div style="font-weight:bold;line-height:2.5;">Which group do I need ?</div>
<div class="mw-collapsible-content">

<div style="height:500px; width:auto; overflow-y:scroll">

{| class="wikitable filterable mw-collapsible sortable"
|+ <span style="white-space:nowrap">Which group for my report ?</span>
|- <div style="font-weight:bold; vertical-align:top; position:sticky;top:-1px;z-index:10">
! style= "background-color:#52BBBD; color:#FFF" | Concerned companies
! style= "background-color:#52BBBD; color:#FFF" | Report<br /> naming convention
! style= "background-color:#52BBBD; color:#FFF" | Details
! style= "background-color:#52BBBD; color:#FFF" | Authority
! style= "background-color:#FF7F27; color:#FFF" | e-file Group
! style= "background-color:#52BBBD; color:#FFF" | Sending way

</div>

|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| NOTREP
| Notification procedures to be followed by a UCITS governed by Luxembourg law wishing to market its units in another Member State of the European Union
| CSSF
| (-) Gestion documentaire<br /> (-) Dashboard<br /> (-) Matrice d'enregistrement et de distribution
| S3
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Monthly financial information for guaranteed funds
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| -
| Yearly financial information
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Interventions on the futures and options markets
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0103
| Monthly statistical balance sheet for money market funds (MMF)
| BCL
| Station Finesti
| KS
|-
|Investment Funds
|S0404
|Country of Marketing
|BCL
|Station Finesti
|KS
|-
|Investment Funds
|S0220
|Quarterly Financial Information
|BCL
|Station Finesti
|KS
|- style="vertical-align:bottom;"
| Investment Funds
| TPTOBS
| Monthly Security by security reporting for investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| SIF:<br /> (-) Prospectus (PC)<br /> (-) Offering document (DE)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| SIF Law 2007:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report SIF (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (PM)<br /> SICAR:<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Auditor report<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| Auditor report<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI:<br /> (-) Prospectus (PC)<br /> (-) Simplified prospectus (PS)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting (AIF Manager)
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| AnaCredit:<br /> Collection of granular credit and credit risk data
| BCL
| Reporting Anacredit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0218-L
| Quarterly statistical balance sheet of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S0219-L
| Information on valuation effects on the balance sheet of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0403-L
| Annual Premiums, claims and commissions of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| TPTASS
| Monthly Security by security reporting of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SHSGRP
| «SHS-Group» report:<br /> Statistics on holdings of securities by reporting banking groups
| BCL
| SHS reporting
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0001
| Daily deposit
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0101
| Monthly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0104
| Adjustments due to valuation effects|
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0105
| Information on interest rates in EUR
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0108
| Information on securititation<br /> transactions launched<br /> by credit institutions
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0109
| Information on CNY (renmibi) operations
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0205-L
| Quarterly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0205-N
| Quarterly statistical balance sheet<br /> of credit institutions -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0208
| Real estate loans for<br /> Lxuembourg buildings
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0209-L
| Staff report -<br /> Luxembourg entity
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0209-N
| Staff report -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0302
| Non balance sheet information
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit Report on AML/CTF
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Circ. 18/697 annexe1
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Annual Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Annual report consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| AC Member List
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Compliance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Governance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Internal Audit Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| ICAAP
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ICAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Branch or Specific Participation
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Long Form Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Reconciliation LuxGAAP FINREP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Management Letter Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit report on rules of conduct
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Management Letter
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Head quarter annual report
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Risk Control Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Report on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Recovery Plan
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Results Distribution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Single Customer View
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Table on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Financial Institutions - Common Reporting Standard (CRS)
| CRS
| Automatic exchange of<br /> financial account information<br /> on a global level
| ACD
| Reporting CRS
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Quarterly reporting on the<br /> financial health of the branches<br /> parent entities
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Residential credit deposits
| CSSF
| Enquêtes
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DCOR
| style="vertical-align:bottom;" | Reporting Entity<br /> B: Credit institution
| style="vertical-align:bottom;" | CSSF
| Enquetes
| style="vertical-align:bottom;" | S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DCOR
| Reporting Entity<br /> P: PFS
| CSSF
| Enquetes
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Residential real estate market
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Stress test in order to assess<br /> the interest rate risk<br /> arising from non-trading<br /> book activities
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0101
| Customer transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0110
| Stock taking of payment accounts in bank money
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01100
| Payment services provided by e-money institutions and payment institutions without the provision of payment accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0111
| OTC cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01110
| Payment initiation services (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01110-F
| Payment initiation services (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0112
| Transactions via telecommunication, digital or IT device
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0113
| Credits to the accounts by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0114
| Debits from the account by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0102
| Interbank transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0120
| Customer Credit transfers sent (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0120-F
| Customer Credit transfers sent (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01200
| Stock of issued payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01201
| Stock of distributed payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0121
| Customer credit transfers received
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01210
| Stock of terminals by terminal type
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01220
| Stock of accounts (except e-money accounts)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01221
| Stock of e-money accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01222
| Stock of accessed accounts - account information services (AIS)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01230
| Number of customers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0103
| Domiciliations
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130
| Direct debits - reporting as creditor's PSP (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01300-F
| Losses due to fraud per liability bearer
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130-F
| Direct debits - reporting as creditor's PSP (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0131
| Direct debits - reporting as debtor's PSP
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0104
| Inventory cards / terminals
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0140
| SEPA R-transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0141
| Interbank payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0142
| Intermediated payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0105
| Card transactiosn (Issuing part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0150
| Card transactions with cards issued by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0150-F
| Card transactions with cards issued by resident PSPs (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0151
| Electronic card transactions with cards issued by resident PSPs, split by Merchant Category Codes (MCC)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0152
| Card transactions acquired by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0152F
| Card transactions acquired by resident PSPs (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0153
| Fundings and withdrawals related to prepaid cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0106
| Card transactiosn (Acquiring part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0160
| Cheques and money remittances (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0160-F
| Cheques and money remittances (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0107
| Cheques and money orders
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0170
| Over-the-counter (OTC) cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0108
| Electronic money scheme
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0180
| Book entries
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0109
| Card based e-money schemes
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0190
| Fundings and withdrawals in e-money (except prepaid cards)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0191
| E-money transfers (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0191-F
| E-money transfers (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Fonds de garantie<br /> des dépôts Luxembourg<br /> (FGDL)
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Identification of third-party<br /> funds held and incorporated in the balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Capital adequacy of<br /> payment institutions
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Profit and loss accoount
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Identification of third-party<br /> funds held and incorporated<br /> in the balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Statement of<br /> authorised reinvestments
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Capital adequacy of<br /> electronic money institutions
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Profit and loss account
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Analysis of shareholdings
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Institutions - Foreign Account Tax Compliance Act (FATCA)
| FATCA
| Foreign Account Tax Compliance Act Reporting
| ACD
| Groupe FATCA
| KS
|-
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| (-) Letter of explanation (LE)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Annual report of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| FRCREP
| Information on participating interest<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| FRCREP
| Information on staff costs and taxes<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| LCRDAX
| CSSF
| Rapport FINREP
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Companies
| S0216
| Quarterly statistical balance of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| S0217
| Transactions of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Key Investor Information Document<br /> (-) O: OPC Law 2010 and Loi 2007<br /> (-) K: SICAR<br /> (-) V: non-reglem.
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Long Form reports (UCI Law 2010)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| SGOREP
| (-) SG 1A: Financial situation<br /> (-) SG 1B: Profit and loss account<br /> (-) SG 1C: Table relating to other activities<br /> (-) SG 2: Other activities<br /> (-) SG: Personnel Table relating to staff
| CSSF
| Rapport Société de Gestion
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007<br /> (-) K: SICAR
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| Articles of Incorporation of UCITS<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Management Regulations of UCITS<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom;"
| MiFID II / MiFIR
| TAFREP
| Article 26 of Regulation<br /> No 600/2014:<br /> Obligation to report transactions<br /> (Markets in financial instruments => MiFIR)
| CSSF
| Report TAF-MIFID
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Other reporting CSSF BCL
| OTHREP
| Other reporting
| CSSF
| Reporting OTHER (CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| BOP101
| Balance of payments reporting
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BOP102
| Cross-border payments<br /> executed for the account<br /> of the resident counterparts
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| PSFREP
| Reporting population:<br /> (-) Investment firms<br /> (-) Specialised PFS<br /> (-) Support PFS
| CSSF
| Rapport PSF
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| N01 (Comp); N02 (Comp); N03 (Comp);<br /> N04 (Comp); N05 (Réviseur); N06( Réviseur);<br /> N07 (Comp); N08 (Comp); N09 (Comp); N10 (Comp); N11 (Comp); N12 (Réviseur);<br /> N13<br /> (Comp);<br /> N14<br /> 'Comp)
| Rapports narratifs
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CSDREP
| Reporting CSDR:<br /> Introduction of quarterly internalised settlement reporting requirements<br /> pursuant to Article 9(1) of EU Regulation No 909/2014 (CSDR)
| CSSF
| Reporting CSDR-9
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BNNNN
| List of head offices, agencies,<br /> branches and representative offices
| CSSF
| Reporting EDIFACT
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Institutions for Occupational Retirement Provision
| SUFREP
| Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019
| CSSF
| Reporting IORP
| KS
|- style="vertical-align:bottom;"
| Money Market Funds (MMF)
| MMFREP
| • According to Article 37 of Regulation (EU) 2017/1131, the manager of a MMF must report information to the competent authority (CSSF) of the MMF, at least on a quarterly basis or - for MMF with assets under management of less than Eur 100 million - on at least an annual basis.<br /> • The first quarterly report should be sent to the competent authority of the MMF no later than 30 days after the end of Q1 2020.
| CSSF
| Money market fund reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0112-L
| Indirect withdrawal and remittance of banknotes denominated in EUR through an intermediary
| BCL
| Reporting S1.12
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| TPTIBS
| Monthly security by security reporting of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| U11
| Monthly financial information UCITS and UCI
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBBL
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBBN
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBHN
| Security by security report–<br /> Off-balance sheet data–<br /> Non-resident
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBHR
| Security by security report–<br /> Off-balance sheet data–<br /> Resident customers
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| SIC
| Financial information to be submitted by investment companies in risk capital (SICARs)
| CSSF
| Reporting SICAR
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI Law 2010:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (MP)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S01; S02; S03; S04; S05;<br /> S06 (Réviseur); S07; S08;<br /> S09; S10; S11; S12; S13;<br /> S14; S15; S16; S17; S18;<br /> S19; S20; S23
| XBRL reports Solvency II
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| S0214
| Quarterly statistical balance
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Securitisation Vehicles
| S0215
| Transactions and write-offs/write-downs on securitised loans
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| TPTTBS
| Security by security reporting
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| UCIAR
| Reporting Entity<br /> A: Alternative Investment fund manager (AIFM)
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| UCIAR
| Reporting Entity<br /> B: Credit institution
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| UCIAR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| UCIAR
| Reporting Entity<br /> S: Management company
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| UCIAR
| Reporting Entity<br /> (-) P: PFS<br /> (-) I: Support PFS
| CSSF
| (-) UCIAR reporting
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Other reporting CSSF BCL
| OTXREP
| Various correspondence
| BCL
| Reporting OTHER (BCL)
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SPJ
| Notification and execution of court orders
| SPJ
| Perquisitions électroniques
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI)(FR)<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CFEREP
| ALMXXX
| CSSF
| Rapport COREP
| S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Long Form Report
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Management Letter
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0106
| Monthly statistical balance sheet for non-money market funds (non-MMF)
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| S0213
| Quarterly statistical balance sheet for non-MMF investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| CED
| Etat de situation relatif aux contrats en déshérence
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| CPR
| Compte rendu
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ESP
| Enquête spécifique
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| ETR
| Etat trimestriel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| FIR
| Fiche de renseignement
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| PDA
| Rapport PDAL (Procédure de Dissolution Administrative sans Liquidation)
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RAC
| Rapport actuariel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RDC
| Rapport distinct complémentaire du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RDI
| Rapport distinct du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RGO
| Rapport de gouvernance
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RLB
| Rapport LBCFT
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RRE
| Rapports sur le traitement des réclamations
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RSE
| Rapport distinct Solvabilité 2 de l'entreprise
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RSO
| Rapport distinct Solvabilité 2 du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ICS
| Yearly Survey on Covered Investment claims (SIIL)
| CSSF
| Enquête
| S3
|- style="vertical-align:bottom;"
| Insurance Corporations
| ROI<br /> DIN
| DORA Register of Information<br /> DORA Incident Reporting
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DPAAIF
| self-assessment <br /> questionnaire PDAOFI
| CSSF
| PDAOFI reporting
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| (-) ALM corep_alm_con.xsd<br /> corep_alm_ind.xsd corep_alm.xsd<br /> (-) LCRDA corep_lcr_da_con.xsd<br /> corep_lcr_da_ind.xsd corep_lcr_da.xsd<br /> (-) IRRBB irrbb.xsd
| CSSF
| Rapport COREP
| S3
|}

</div>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How can I get a missing group ?</div>
<div class="mw-collapsible-content">
If you think that the group you need is not available in your list, please [[How_to_contact_us|ask us]] to check and/or add it.
</div>
</div>
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_manage_users_at_group_level></span>
<div style="font-weight:bold;line-height:2.5;">How can I manage users at group level ?</div>
<div class="mw-collapsible-content">

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon (Figure 21).

[[File:SDjl_8.png|400px]]

(Figure 21)

<u>'''Example'''</u>:

If you want to know the users to which the group '''Group FATCA''' has been assigned or if you want to add a new user to the group, please follow the instructions below.

<u>'''Step 1</u>:'''

Press the '''Groups''' button. The '''Groups list''' page opens. All groups assigned to your company are shown here (Figure 22).

[[File:3GroupList.png|800px]]

(Figure 22)

<u>'''Step 2</u>:'''

Click the '''Edit groups''' icon [[File:EditGroupSD.png|20px]] in order to view all the users assigned to '''Groupe FATCA''' group (Figure 23).

[[File:2EditGroup.png|800px]]

(Figure 23)

The '''Group detail''' page opens. Here you can find detailed information on the '''Group FATCA''' (e.g. Status date, number of inactive users, number of locked users) (Figure 24).

[[File:GroupDetailPage.png|500px]]

(Figure 24)

<u>'''Step 3</u>:'''

Press the '''Users''' button (Figure 25)

[[File:GroupDetailUsers.png|500px]]

(Figure 25)

The Group detail / Users page opens. All users assigned to the '''Group FATCA''' are listed here(Figure 26).

[[File:GroupUsrsList2.png|600px]]

(Figure 26)

<u>'''Step 4</u>:'''

Press the '''Edit Users''' button [[File:EditUserButton.png|100px]] (Figure 27)

[[File:EditUsersGroup.png|600px]]

(Figure 27)

The '''Users''' page opens in '''Edit mode''' (Figure 28)

[[File:UsersEditGroup.png|600px]]

(Figure 28)

The following actions can be done here:

1. '''ADD A USER'''. Select the user and his profile you want to add.

2. Change the '''Profile''' of the user

3. Delete the '''User'''

4. Once you have made your changes, press the VALDATE CHANGES button [[File:ValidateChanges.png|100px]]

The '''Users''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a confirmation window pops up on the top of the screen indicating that the assignment was successful (Figure 29).

[[File:AssignmentsSaved.png|800px]]

(Figure 29)
-------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_assign_groups_and_profiles_to_users></span>
<div style="font-weight:bold;line-height:2.5;">How do I assign groups and profiles to users ?</div>
<div class="mw-collapsible-content">

<u>Example</u>:

If a user has to send '''FATCA reportings''' to the authority, the e-file administrator must assign the <u>group</u> '''Rapport FATCA''' and the <u>profile</u> '''Manager''' to the user.

<u>'''Step 1</u>:'''

Open the '''User management''' screen in the '''Users''' tab and click the '''Edit''' [[File:EditGroupSD.png|20px]] icon of the user to whom you want assign [[E-file_Administration#Which_group_do_I_need|'''groups''']] and a specific [[E-file_Administration#User_profiles |'''profile''']] (Figure 11).

[[File:A specific profile (Figure 11).png|900px]]

(Figure 11)

<u>'''Step 2</u>:'''

The '''User details''' screen opens. Click the '''Groups''' button (Figure 12).

[[File:2AddGroup.png|500px]]

(Figure 12)

<u>'''Step 3</u>:'''
The '''User details / Groups''' screen opens. Click the '''Edit button''' (Figure 13).

[[File:2GroupDetails.png|500px]]

(Figure 13)

<u>'''Step 4</u>:'''

The '''User details / Groups''' screen opens in '''Edit''' mode (Figure 14).

Click the '''ADD A GROUP''' button [[File:AddGroup.png|100px]], select the [[E-file_Administration#Which_group_do_I_need|'''groups''']] and '''profile''' you want to assign and click the '''Validate''' button.

[[File:4Add group.png|800px]]

(Figure 14)

The '''User details / Groups''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a '''confirmation''' window pops up on the top of the screen indicating that the group assignment was successfully saved (Figure 15).

[[File:AssignmentsSaved.png|800px]]

(Figure 15)

Please be informed that you can find detailed information on all groups on our Wikipage [[E-file_Administration#Which_group_do_I_need|''''e-file Administrator FAQ'''']]; column <u>e-file user account: "groupe"</u>.

=== User profiles ===

====Administrator (EN)/ Administrateur (FR)====

The Administrator profile allows the e-file administrator to order and activate LuxTrust certificate(s), manage user accounts, groups, user profiles, lock and un lock user account.

==== Guest (EN) */ Visiteur (FR) * ====

* The Guest can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Guest cannot submit reports or documents via e-file.

====Manager (EN)/ Responsable (FR)====

* The Manager can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Manager can submit reports linked to his group(s) via e-file.

====Operator (EN) */ Opérateur (FR) * ====

* The Operator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* The Operator submit reports linked to his group(s) to validation by a Validator.

====Validator (EN) */ Valideur (FR) * ====

* The Validator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* He validates or rejects reports awaiting for validation linked to his group(s).

(*) Available depending the group
---------------
</div>
</div>

== Security's management ==

<span id=keystore_system></span>
=== * keystore system, Luxtrust certificate, SSL security ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_order_a_LUXTRUST_certificate></span>
<span id=LUXTRUST_certificate_purchase_order></span>
<div style="font-weight:bold;line-height:2.5;">How do I order a LUXTRUST certificate ?</div>
<div class="mw-collapsible-content">

You can find a video tutorial <b> <u>[[Media:e-fileLuxtrustCertificateProcess.mp4| here]]</u> which summarises the below process</b>

Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>
Prior your first filing you will have to order and activate a Luxtrust certificate.<br>
The only certificate authorised for the file encryption by the reporting entity are '''SSL certificates''' from the certification authority [https://www.easyssl.lu/?product=e-file LUXTRUST].

Please check the [[Transmission_Module#System_requirements|system requirements]] to run the e-file applications.

=== Key and Certificate Request generation ===

Please be informed that during the next steps <span style="background:yellow"> <u>two files</u> </span> will be generated:

<span style="background:yellow"> 1- </span> the keystore file '''keystore.ks''' containing your new keys

<span style="background:yellow"> 2- </span> the certificate request file '''Certificate Request.csr''' containing a copy of your new keys. <u>This file must be uploaded on LUXTRUST's website during your purchase order</u> .

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate purchase order and its activation have to be performed on the same computer workstation.</span>'''

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 30).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 30)

<u>'''Step 2</u>:'''

Click the '''Certificates ''' button (Figure 31)

[[File:AdminModule_2.png|border|500px]]

(Figure 31)

<u>'''Step 3</u>:'''

The '''Certificates Management''' screen opens. Click the '''CERTIFICATE REQUEST - ACTIVATION MENU''' link (Figure 32).

[[File:AdminModule_3.png|border|1000px]]

(Figure 32)

<u>Result</u>: A new screen opens displaying GENERATE CERTIFICATE KEYS - BEFORE LUXTRUST WEBSITE ORDER on the left side of the page

<u>'''Step 4</u>:'''

Configure your keystore (Figure 33).

[[File:Configure_your_keystore.png|border|1000px]]<br>

(Figure 33)

a. <u>Select the keystore import method</u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, select '''Create a new keystore file''' option and indicate a keystore name.

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, you '''<u>must</u> '''select your '''curent keystore file''' by using the ''browse file'' or ''drag & drop'' feature to import it.

<span style="color: #C00000">'''Important note : in both case, the new keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

- File name: choose your keystore name, for example '''keystore.ks'''

- File type : .ks

b. <u>Password </u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, you have to define a brand-new '''keystore password'''.
A confirmation is required

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, e.g. its validity date expired, you <u>must</u> use the '''keystore password''' that had been created when you ordered the certificate for the '''very first time'''.

<span style="color: #C00000">''' Important note : the keystore password has to be shared with all e-file users who have to transmit encrypted documents or decrypt feedback files received from the supervisory authorities. </span>.

<span style="color: #C00000">''' Important note : if you loose your keystore password, you will have to generate a new key and order a new certificate. </span>

c. <u>Certificate request name (.csr)</u>

You have to define a name for the technical certificate request file required by Luxtrust, for example '''CertificateRequest.csr'''

<span style="color: #C00000">'''Important note : the certificate request will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

- File name: '''CertificateRequest.csr'''

- File type : .csr

<u>'''Step 5</u>:'''

Verify the Company information. (Figure 34) :

[[File:Company_information.png|border|1300px]]

(Figure 34)

The related fields will be pre-filled in with information we currently have in our system. Feel free to make changes if necessary.

<u>'''Step 6</u>:'''

Click the '''Generate keys''' button.

A window will pop up inviting you to download the Keystore file and Certificate Signing Request (Figure 35).

[[File:Keystore CSR download window.PNG|border|500px]]

(Figure 35)

You must click on each of the Download buttons in order to activate the OK button.<br>
Then click OK to clear the message window.

<span style="color: #C00000">'''Both keystore and certificate request files will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name as follows: <br>The name of the previous keystore + a timestamp displayed as yyyymm + onhold. <br><br>Example: oldname : MyKeystore.ks / new name : MyKeystore_202212_onhold.ks''' </span>

<span style="color: #C00000">'''Important note : we advise you to back up the keystore.ks and CertificateRequest files.''' </span>

=== Finalize your LUXTRUST purchase order ===

<span style="color: #C00000">'''Before to start order in the Luxtrust website make sure that you have process the previous part (Key and Certificate Request generation). </span>

-Open the [https://www.easyssl.lu/?product=e-file LUXTRUST easy SSL e-file website].

-Browse to SSL Certificate section and click the E-FILE icon
[[File:Sans titre.png|50px]]

-Choose the period of validity of your certificate and click the ORDER E-FILE button.

-If you do not have a LUXTRUST easy SSL e-file account you have to get registered.

-Once registered, complete the whole order form, upload your '''CertificateRequest<span style="background:yellow">.csr </span>''' file, accept the TERMS AND CONDITIONS and click the PLACE ORDER button.

-Shortly afterwards, you will receive an e-mail from LUXTRUST confirming your purchase order.

-Please follow all instructions provided in the e-mail and its PDF attachment (Send signed PDF by post with all required documents to the address indicated inside, process the payment etc.)

----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_activate_my_LUXTRUST_certificate_into_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How do I activate (integrate) my LUXTRUST certificate into e-file ?</div>
<div class="mw-collapsible-content">

The certificate file will be sent to the e-mail address you provided in your purchase order.

The extension of this file will be .txt, in order to prevent your firewall from blocking the attached file.

<u>'''Step 1</u>:'''

<span style="color: #C00000">'''Important note: save the file .txt on your computer workstation and <u>replace</u> the .txt extension by <span style="background:yellow">.cer </span> </span>

Double-click the <span style="background:yellow"> .cer </span> file. You should be able to see your certificate as shown below (Figure 36):

[[File:Certificate visual example.png|alt=Certificate example|377x377px]]

(Figure 36)

<u>'''Step 2</u>:'''

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate ordering and its activation have to be performed on the same computer workstation.</span>'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 37).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 37)

<u>'''Step 3</u>:'''

Click the '''Certificates ''' button (Figure 38).

[[File:AdminModule2.png|border|500px]]

(Figure 38)

<u>'''Step 4</u>:'''

Click the '''CERTIFICATE ACTIVATION – AFTER RECEPTION OF LUXTRUST CERTIFICATE''' link (Figure 40).

[[File:Certificate_activation.png|border|1500px]]

(Figure 40)

<u>'''Step 5</u>:'''

Configure your keystore (Figure 41).

[[File:Certificate_activation_steps.png | 1000px]]

(Figure 41)

a. <u>Select the Group you need to use (by default Principal)</u>

b. <u>Import the keystore that was generated at the same time as the Certificate Signing Request</u>
(from previous step )

c. <u>Enter the keystore password</u>

d. <u>Import the certificate you received from Luxtrust </u>

<u>'''Step 6</u>:'''

Click the '''ACTIVATE CERTIFICATE''' button.

A window will pop up and inform you that the activation has been done successfully.

Your keystore.ks is now updated. It contains your activated LUXTRUST certificate and your encryption keys.

[[File:AdminModule_15.png | 300px]]

'''Note''': The display and the position of the pop up may differ regarding the Web browser you are using

<span style="color: #C00000">'''Important note : the updated keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name : the name of the previous keystore + a timestamp displayed as yyyymm + completed.<br>Example: previous name : MyKeystore.ks / new name : MyKeystore_202212_completed.ks''' </span>

<span style="color: #C00000">'''Important note : if you loose your keystore and/or its password,you will have to generate a new encryption key and order a new certificate. </span>.
-------------

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_must_I_do_with_the_keystore></span>
<div style="font-weight:bold;line-height:2.5;">What must I do with the keystore ?</div>
<div class="mw-collapsible-content">

===Manual file transmission===

The activated keystore, containing your LUXTRUST certificate and your encryption keys must now be provided to the workstations of each e-file user.

<u>'''Step 1</u>:'''

Open the Transmission module

[[File:Icon1.png | 300px]]

<u>'''Step 2</u>:'''

[[File:Keystore selection After(1).PNG| 600px]]

===Automatic file transmission===

In the case you are using the [[Sending_Service|Sending Service]] for automatic file transmission, the activated keystore.ks must be provided as well.
----------------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_register_my_LUXTRUST_certificate_with_the_CSSF></span>
<div style="font-weight:bold;line-height:2.5;">How can I register my LUXTRUST certificate with the CSSF ?</div>
<div class="mw-collapsible-content">

For some reportings, the LUXTRUST e-file SSL certificate used by the reporting entity must be registered with the CSSF, before sending any files, according to the registration procedure described in the '''[https://www.cssf.lu/wp-content/uploads/Naming-convention.pdf#page=8 CSSF 23/833, naming convention part.]'''

The LUXTRUST e-file SSL certificate must be registered with the CSSF for the below reportings:</br>
(list extracted from [https://www.cssf.lu/fr/transport-et-securisation/#specifications-techniques Transport et sécurisation via les canaux de transmission externes])

* COREP/FINREP reporting
* ESP – Special enquiries
* SIC – SICAR reporting
* PFS – Reporting PFS and support PFS
* EDP – Payment institutions reporting
* EME – Electronic money institution
* SGO – Management companies reporting
* OPC – Fund XML reporting (O1.2)
* DOC – Non-structured electronic documents (circ. 19/731)
* OTH – Other
* OCB – Other reportings for CSSF and BCL
* SUF – XBRL reportings for subfund-based structured products (IORP)
* O4.x – Edifact report

[[Media:How to declare your Luxtrust certificate to the CSSF.pdf|=> e-file User Guide: CSSF Certificate registration]]
----------------
</div>
</div>

=== * S3 system ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_is_the_S3_digital_key_management_in_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How is the S3 digital key management in e-file ?</div>
<div class="mw-collapsible-content">

The CSSF has updated its submission methods to allow AIFMs to file specific regulatory reports via the CSSF’s API from 2nd November.
Please note, this is not the deadline to make the change, it is the point at which the new method is available to use. <br>
FE Fundinfo are ready to support you through the transition.
Your current setup in e-file will remain in place and only minor one-off changes are required from you to ensure the continuation of your existing functionality on e-file and future proof the communication method for all reporting and filing with the CSSF going forward.
<br><br>

<u>'''Explanation in context of AIFMD reporting</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/7273286345756229380 November 21st webinar in English] and the [https://c2rv804.na1.hubspotlinks.com/Ctc/ZO+113/c2RV804/VWQ8Fx5Hw7JyVdSL7w2rxckBW20x2Jc566MpmN31NNCl5nXHsW7Y9pgv6lZ3kLW8mzYxT1ZSlmLW7yCpDW2jmg69W73tZTZ5yBySkW7jL_zN8my412W9hGQQt71RszSVkgkWT3FF-R2W1VryJ67bk_NmW1RKWr345DTFjV1PBRM2KwkQsW4P0bYq6h4FhzW2Y0TlL8jm7QlW6N2qBz9lFm9yW1bNKCy1qGVgGW7dJWkQ8TTtG5N3kH6ptzC816W33qG8b10K_BtW8gQSgN4g3h5TW9h3bp34KXCJHV_q02d6BgPGWW5xJSX81p0bg6W8jK_6G221K5qW3_hsX93mN9kwW2RyrBr7f39YJW8v09kD7Cw1nxW37qD826JSxdcW4Rc7yD85pl3PW109fZz4mxLcHW26Y0Y03k4GNWW8zPXjF1t6bspW78yjPn71W4ftW8-MxR372T_w5V13CVl6qstVRW21LWhW2dlqL_W2Xs3ZP6K5mZ2W1THZsw1FrpXLW54G4QN27qB0BW3yXpwm7rd3qwW23mB7r301kH7W19MCT85QW6wbW218pPC2z-WjCVQRHvT30nLTNW1qM-sk29_0TFd2XXgW04 related presentation]

[https://attendee.gotowebinar.com/recording/2231697877960308483 Webinaire en français]

<u>'''Explanation in context of UCITS Cross-Border notification</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/2670031382955110830 December 12th webinar in English] and the [https://445778.fs1.hubspotusercontent-na1.net/hubfs/445778/FE%20fundinfo%20presentations/FSQ%20channel%20change_Webinar%2012%20December.pdf related presentation]

This new system works via a bucket system.<br>
There is one bucket for each filing context (i.e. Cross-border notification, AIFMD)<br>
The CSSF imposes a technical size limit for filing per bucket on 30 rolling days.<br>
Should you encounter any issue, feel free to contact us directly [[How to contact us|'''Client Support & Operations Desk''']] we will liaise with the CSSF.<br>

<br>
The below is a step-by step guide to appoint FE Fundinfo as a delegate within the CSSF’s eDesk platform, the easiest path to allow us to maintain our services. <br>
Once the set-up is complete you can continue to use your familiar eFile interface and do not need to interact with eDesk as this will all be channelled within your existing workflows in eFile.
<br><br>
To perform the set-up in eFile you have two options:
<br>

* You as IT expert import the S3 keys on eFile

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide for eDesk IT Experts to connect CSSF’S eDesk to FE Fundinfo’s eFile system''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Your entity’s appointed IT Expert will need to log into the IT Management
area of eDesk ([https://edesk.apps.cssf.lu/edesk-itmgt/s3/accesses here]). This must be using the same LuxTrust Device and
account that the IT Expert role was assigned to. Please note, that these
steps can only be implemented from the appointed IT Expert account
|
|-
|
Step 2
|
Once logged in, go to the ‘S3 ACCESS DASHBOARD’ at the top of the page,
which will take you to a screen similar to the below
|
[[File:02-S3Dashboard.png|S3Dashboard|800px]]
|-
|
Step 3
|
Select ‘Create Access’
|
[[File:03-S3CreateAccess.png|S3CreateAccess|800px]]
|-
|
Step 4
|
This will provide you with an option to select a ‘scope’ which will be the
reporting type you have been appointed as IT Expert for and select create:
<br>
[[#Correspondance table|You can refer to our correspondance table]]
|
[[File:04-S3CreateScope.png|S3CreateScope|800px]]
|-
|
Step 5
|
This will create a line in the S3 access dashboard with the report type, the
status (this should show ‘Granted’) and the date of this creation.
<br>
Each report type generates 3 codes on eDesk, (the Bucket code, the Access
Key, and the Secret Key). To reveal these keys, click the magnifying glass
with a ‘+’ icon under the actions column (located on the far right of the
screen).
|
[[File:05-S3Granted.png|S3Granted|800px]]
|-
|
Step 6
|
This will reveal the information about the who the access has been granted to, when and what report it is for. It will also provide details of the unique codes specific to the entity, report type and individual.
|
[[File:06-S3Access.png|S3Access|800px]]
|-
|
Step 7
|
Once the Keys have been generated, keeping your connection to eDesk open, in another window, open your efile environment. Log in using the efile Admin account for your entity and open the ‘Keys Management’ tab.
|
[[File:07-efileMenu.png|efileMenu|800px]]
|-
|
Step 8
|
Select ‘Add Key’ on the far right of the screen
|
[[File:08-eFileAddKey.png|eFileAddKey|800px]]
|-
|
Step 9
|
A pop out will appear and provide you with several drop down lists to
complete. Under ‘Scope’ you should choose the report type that you are
providing the Keys for. In this instance AIFMD should be selected.
|
[[File:09-eFileScope.png|eFileScope|800px]]
|-
|
Step 10
|
Returning to eDesk, copy the Bucket code, the Access key and Secret key
and paste each of these into the applicable boxes on efile.
|[[File:10-BucketCopy.png|BucketCopy|800px]]
|-
|}

===Correspondance table===
'''Please find the correspondence table of e-file and e-Desk scopes'''<br>

{| class="sortable" border="1" cellspacing="2" cellpadding="1"
|- <div style="position:sticky;top:-1px;z-index:10">
! scope="col" | '''Label scope in e-file'''
! scope="col" | '''Label scope in e-Desk'''
! scope="col" | '''CSSF reference'''
! scope="col" | '''Deadline'''
</div>
|-
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/AIFM_Reporting_Technical_Guidance.pdf AIFM reporting -Technical guidance]
| style="vertical-align:middle; color:#202122;" | 30 June 2024
|-
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_guide_notifications_CBDF.pdf User guide notifications CBDF]
| style="vertical-align:middle; color:#202122;" | 2nd January 2024
|-
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/cssf22_811eng.pdf CSSF 22/811]
| style="vertical-align:middle; color:#202122;" | 30 June 2023
|-
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSSF_CPDI_2440eng.pdf CSSF-CPDI 24/40]
| style="vertical-align:middle; color:#202122;" | 15 May 2024
|-
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures - SFO
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Precontractual_Data_Collection_-_practical-guide.pdf SFDR precontractual data collection]
| style="vertical-align:middle; color:#202122;" | 31 October 2023
|-
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures - SFPER
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Data_Collection_-_practical-guide.pdf SFDR UCI Data Collection]
| style="vertical-align:middle; color:#202122;" | 31 January 2024
|-
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Bank_prudential_reporting.pdf Bank prudential reporting]
| style="vertical-align:middle; color:#202122;" | 1st September 2024

|-
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Regulatory-documents-and-reports.pdf User Guide for Regulatory Documents and Reports]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Key-Information-Document.pdf User Guide for Key Information Document]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_U1.1.pdf Guidelines on the U1.1 reporting]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_Yearly_Survey_on_Covered_Investment_Claims.pdf Guidelines for the Yearly Survey on Covered Investment claims (SIIL)]
| style="vertical-align:middle; color:#202122;" | 17th January 2025

|-
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_SAQ_DPAAIF.pdf Guidelines on the self-assessment questionnaire PDAOFI]
| style="vertical-align:middle; color:#202122;" | 31st March 2025

|-
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2025/03/upcoming-evolution-in-the-electronic-visa-stamp-procedure-for-the-prospectuses-of-ucits-part-ii-ucis-sicars-and-sifs/ Procedure change for visa "stamp" prospectuses]
| style="vertical-align:middle; color:#202122;" | 1st April 2025

|-
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSDR9_Handbook.pdf User Guide Internalised Settlement Reporting Under Article 9 OF CSDR]
| style="vertical-align:middle; color:#202122;" | 1st July 2025

|-
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/MMFR_Handbook.pdf MMF reporting Handbook]
| style="vertical-align:middle; color:#202122;" | 1st September 2025

|-
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2026/01/iorp-reporting-circular-cssf-19-726-new-edesk-procedure/ new IORP procedure]
| style="vertical-align:middle; color:#202122;" | 15th January 2026

|}
---------------
</div>
</div>
</br></br>

===Special cases===
'''For Key Information Document (KID PRIIPs/KID) and Regulatory Documents and Reports scopes'''<br>
Due to the way the CSSF has implemented the third-party delegation process we have adapted our S3 scope import system in order to enable
</br>
the possibility for a client who is a service provider to onboard multiple S3 keys for the same scope on different Asset Managers / Self-managed funds / Filing entity based on the FSQ referential
</br></br>
To do so after having selected Key Information Document (KID PRIIPs/KID) or Regulatory Documents and Reports scope.<br>
You have to use the dedicated radio button Asset Manager, Self-Managed funds or Filing Entity
<br>
The list is automatically refreshed to only display third-party without S3 key onboarded.<br>
In case of a Filing Entity, the name of the Third party linked to the eFile user will be pre-filed (and can't be changed)<br>
[[File:AssetManager-SelfManaged-FilingEntity.png|Asset Manager, Self-Manged fund or Filing Entity|400px]]

To help you identifying which key has already been imported on eFile a dedicated page has been added in the S3 Keys Management module <br>
This page lists the already imported key for scope(s) allowing delegation. <br>
The Bucket owner (entity that owns the S3 key) and the Provider (entity who uploaded the S3 key on eFile) are displayed.<br>
[[File:DelegationList.png|S3 Key list|800px]]

* Grant us with the IT expert role to perform such changes for you
To start the process please send us an email to '''[mailto:cso.desk@fundsquare.net cso.desk@fundsquare.net]''' with both '''name''' and '''CSSF identification number''' of the entity you want we become IT Expert

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide on how to assign FE Fundinfo as a CSSF IT Expert on eDesk''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Log into [https://edesk.apps.cssf.lu/ eDesk] with the Advanced User account using your LuxTrust Device and Password. Please note that these changes can only be implemented from the Advanced User account
|
|-
|
Step 2
|
Once logged in, go to the top right corner of the screen, click on your account user name, and select ‘Entity Management’
|
[[File:02-EntityManagement.png|EntityManagement|800px]]
|-
|
Step 3
|
Now select ‘Access Requests’ from the tabs at the top of the screen:
|
[[File:03-AccessRequest.png|AccessRequest|800px]]
|-
|
Step 4
|
As FEfundinfo will have made a request to connect from our Fundsquare account, you will see us on a list of users requests to connect with your entity. You will be able to identify our request as it will be with the LuxTrust SN: <span style="color: #C00000">100115278245548987357</span>
|
[[File:04-LuxtrustSN.png|LuxtrustSN|800px]]
|-
|
Step 5
|
Once you have identified the FE fundinfo request from our Fundsquare account, you can go to the far right of the screen and select ‘ACCEPT ACCESS’ or ‘REJECT ACCESS’. Remember to only
accept requests and provide access to users you are associated with. You will need to ‘ACCEPT ACCESS’ on our request:
|
[[File:05-AcceptAccess.png|AcceptAccess|800px]]
|-
|
Step 6
|
Once you have clicked accept, go to the ‘Specific roles within entity’ tab:
|
[[File:06-SpecificRole.png|SpecificRole|800px]]
|-
|
Step 7
|
Under the ‘Specific roles within entity’ tab, on the right of the screen, click the ‘Add’ button:
|
[[File:07-AddSpecificRole.png|AddSpecificRole|800px]]
|-
|
Step 8
|
You will now be able to click on the ‘User’ box and select a user within the list of approved users connected with your entity. One of these will be FE fundinfo’s Fundsquare account, select this option and the user details will populate automatically:
|
[[File:08-FSQUser.png|FSQUser|800px]]
|-
|
Step 9
|
Now you can select a role for that user, in this case you will need to select IT EXPERT for FE fundinfo in the drop down selection and click save on the top right to make the change
|
[[File:09-ITExpert.png|ITExpert|800px]]
|-
|
Step 10
|
You have now completed all you need to ensure continued use of efile and secure submission of your reports to the CSSF! FE fundinfo will do the rest and can now ensure that the changing transmission methods gradually introduced by the CSSF over the next 18 months are updated as needed without any impact on you
|
|-
|}
----------------
</div>
</div>

::== Onboarding workflow map ==
''You can click on the picture.''
<imagemap>
File:Wkf_S3_onboarding.png|center|1500px|alt=clickable image : form description| titre
rect 106 355 277 452 [[E-file_Administration#You_as_IT_Expert | You as IT Expert ]]
rect 776 541 947 630 [[E-file_Administration#FE_Fundinfo_as_IT_Expert |FE Fundinfo as IT Expert]]
rect 1024 376 1193 482 [https://edesk.apps.cssf.lu/edesk-dashboard/homepage?lng=en eDesk User Guide ]
rect 477 530 646 691 [https://www.cssf.lu/wp-content/uploads/Methods-of-transmitting-reports-via-S3-Application-Programming-Interface-Technical-guidance.pdf S3 transmitting method ]
desc none
</imagemap>
-----------
</div>
</div>

=== * general security questions ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_the_local_e-file_administrator></span>
<div style="font-weight:bold;line-height:2.5;">How can I change the local e-file administrator ?</div>
<div class="mw-collapsible-content">

Each e-file administrator account is linked to a single email at a time.

3 cases :
* You have access to the account
:then change the email of the administrator by using the <b>administration module</b> and update the administrator account's owner (name, firstname). The new administrator will just have to request a new password.
* You have access to the administrator's e-mail box
:you can use the "forgotten password" button on https://www.e-file.lu to change the password and get access.
* You do not have access to the administrator account nor to the email of this account
:then for security reason you will have to follow this specific procedure:

::Your request must be sent by email and paper mail.

::The paper can be replaced by a mail with a scan of the letterhead paper => Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com].

<u>'''The request must be submitted on letterhead of your company and signed by a legal representative with the following information'''</u>:
*Administrator's login adminXXX
*The current email address which is linked to the administrator
*The new email address to link to the administrator
*A brief explanation of the reason why you need to change it
*Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com]'''

Once Fundsquare has received and checked your request we will update your email and send you the procedure to update the password.

If you have further questions do not hesitate to contact our [[How to contact us|'''Client Support & Operations Desk''']].

-----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_the_e-file_password_policy></span>
<div style="font-weight:bold;line-height:2.5;">What is the e-file password policy ?</div>
<div class="mw-collapsible-content">

[[File:Password.png|300 px]]

(Figure 42)

The password you will have to provide must follow the rules below:

*At least one upper and one lower case letter
*At least one number
*At least one special character from this list: ! # $ % & ( ) * + , . /: ; < = > ? ^ _ @ { | } [ ] ~
*At least 8 characters and at most 20

<u> Please note that </u>:

The validity of your password is not limited in time.

Our system blocks the user after 3 incorrect attempts and it is the e-file administrator who has to unblock the account.

Passwords are encrypted in our database and we do not keep them. You may re-use them.
-----------
</div>
</div>

== Being informed ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_important_information></span>
<div style="font-weight:bold;line-height:2.5;">How can I get important information ?</div>
<div class="mw-collapsible-content">

As an administrator, you will received all significant information regarding e-file changes, maintenance or enhancement through the e-mail address set up onto your account.
You can also manage some alerts through e-file, see the notifications system.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_custom_notifications></span></span>
<div style="font-weight:bold;line-height:2.5;">How can I get custom notifications ?</div>
<div class="mw-collapsible-content">

Please be informed that you can receive alert by email triggered by specific events.

<u>Example</u> : Court orders sent by the Luxembourgish judicial police [http://www.cssf.lu/fileadmin/files/Lois_reglements/Circulaires/Hors_blanchiment_terrorisme/cssf13_566eng.pdf (=> CSSF - Circular 13/566)]

If you want to be notified by email each time the Luxembourgish judicial police sends you court orders, you have to follow the steps below.

<u>'''Step 1'''</u> : Connect to e-file with your user credentials : '''https://www.e-file.lu/e-file/'''

<u>'''Step 2'''</u> : Select Update my profile

[[File:Select Update my profile.png |200 px]]

<u>'''Step 3'''</u> : Verify that your email address registered in your e-file account is valid.

[[File:Your e-file account is valid.png |400 px]]

<u>IMPORTANT :</u> if your email address is not valid, please ask your [[Administration#e-file_administrator_functions_.28e-file_v1.29|'''e-file administrator''']] to replace it by a valid one.

<u>'''Step 4'''</u> : Select Customize your notifications.

[[File:Customize your notifications.png |200 px]]

<u>'''Step 5'''</u> : Select group.

[[File:Select group555.png |400 px]]

<u>'''Step 6'''</u> : Select the Alert type.

[[File:Notification.png |500 px]]

<u>IMPORTANT :</u>

A green window will pop-up stating that the update has been saved.

<u>'''Optional Step 7'''</u> : Receive only your alerts and not the group's ones.

Ticking also the group box, the sends from other users of the same reports group will be ignored.

[[File:Alerte Notification.png |500 px]]

[[Category: FAQ e-file]]

----------------------
</div>
</div>

Sending Service java-less version

2026-05-04T09:19:09Z

Cso: /* Certificate Update */

''<small>Page's last update : 30 May 2024</small>''
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

''You can click on the picture.''
<imagemap>
File:SDjl_general.png|center|900px|alt=clickable image : form description| titre
rect 23 39 332 149 [[Sending_Service_java-less_version#Prerequisites | Prerequisites ]]
rect 425 91 678 182 [[Sending_Service_java-less_version#Purpose |Purpose]]
rect 703 3 911 96 [[Sending_Service_java-less_version#Manual_installation_using_command_prompt | Installation ]]
rect 782 110 1057 208 [[Sending_Service_java-less_version#Update_the_sending_service | Upgrade or change the configuration ]]
rect 47 264 413 350 [[Sending_Service_java-less_version#Administration_Interface | Using the administration interface ]]
rect 491 266 694 357 [[Sending_Service_java-less_version#Process_overview | Process ]]
rect 767 266 1056 349 [[Sending_Service_java-less_version#Sending_Folders | Folders ]]
rect 46 459 212 582 [[Sending_Service_java-less_version#Administration_Interface | through the administration interface]]
rect 246 566 470 669 [[Sending_Service_java-less_version#Logs| Is my sending service running ?]]
rect 387 457 514 531 [[Sending_Service_java-less_version#Stop_the_application | Stop ]]
rect 534 496 722 592 [[Sending_Service_java-less_version#Start_the_application | Start ]]
rect 803 455 969 546 [[Sending_Service_java-less_version#Submit_a_report | How can I submit a report ?]]
rect 987 508 1181 590 [[Sending_Service_java-less_version#Check_for_acknowledgment_and_feedbacks | Check my sends ]]
rect 730 600 950 700 [[Sending_Service_java-less_version#Solving known problems | Solutions ]]
desc none
</imagemap>

= Purpose =

The '''Sending Service''' is our solution for the '''automatic transmission''' of reports and documents to authorities.

It is an application consisting of a set of '''processes''' (called listeners) that periodically exchange files with authorities through a set of designated '''folders'''. Everything is configured via an '''administration interface'''.

This solution is useful if you have a '''large number of reports''' to submit or if the manual sending does not suit your needs.

Please be aware that, in this case you will have to provide the files yourself according to the authorities' file specifications.

This tool is usually <span style="color: #C00000">'''installed on a server'''</span> on your side.

With a suitable '''network mapping''', users can simply '''drop the file to be sent into the appropriate directory'''. It is then automatically '''encrypted and sent'''.

= Prerequisites =

*Internet access
*If you use a proxy, authorise outgoing calls to [https://www.e-file.lu www.e-file.lu]. Port 443 (HTTPS) must be open.
*<span style="color: #C00000">'''Windows Administrator rights''' </span> to install the Sending Service <span style="color: #C00000">on the computer</span> ''(Windows Start button > Control Panel > User Accounts > Manage User Accounts)''.
*'''OS''': Windows - ''Linux will be developed''
*Processor: Pentium 2 GHz or equivalent
*8 GB of RAM
*300 MB of free space on hard disk drive. Think of providing regular purges.
*500 MB of free space on hard disk drive for logs. Regular purges are necessary as well.
*A <span style="color: #C00000">'''Sending Service user''' </span>, ''for example: aacSD'', and its password, ''for example: formation'', have to be available [[E-file_Administration#e-file_administrator_functions_.28e-file_v1.29|'''=> e-file administration''']].
*The e-file account of the Sending Service user has to be linked to groups/modules, ''for example FATCA reporting + profile "Sending Service".''
*A valid <span style="color: #C00000">'''keystore''' </span>(keystore.ks) and its <span style="color: #C00000">'''password''' </span>must be available as soon your file must be encrypted. (You do not need a keystore anymore if all your reports are going through S3 API).
*The Sending Service user has to be properly configured in the e-file user administration tool in order to be able to receive <span style="color: #C00000">'''alerts''' </span> (receipt of acknowledgement and feedback files).

Note that you can find the prerequisites for the manual transmission there : [[Transmission_Module#System_requirements]]

= Sending service version 1 vs version 2 =
{| class="wikitable"
|+Differences between v1 and v2
!
!<span style="color: #21C8DB">v1</span>
!<span style="color: #21C8DB">v2</span>
|-
|needs Java
|x
|
|-
|support S3 protocol
|x
|x
|-
|allow pre-encrypted files send
|x
|
|-
|U11 enrichment
|x
|
|-
|export to XLS
|x
|
|-
|XLS to XML (TPTIBS)
|x
|
|-
|O4.x semi-automatic (txt to PDF)
|x
|not yet
|-
|allow O4.x PDF direct send
|x
|x
|-
|user interface for configuration
|
|x
|-
|deep level (deposit in sub-directories)
|x
|x
|-
|automatic upgrade
|
|x
|-
|self-managable heartbeat monitoring
|
|x
|-
|Linux-compatible
|x
|not yet
|-
|unit of time used in set up
|milliseconds
|minutes
|}

= Process overview =
The sending service can be run in the <u>console mode</u> through '''launcher.exe'''. It then runs in a line-command window which must stay open.

On the first launch see [[#Manual_installation_using_command_prompt|installation]] paragraph to locate it, otherwise [[#Start_the_application|start]].

The sending service can also be installed as a <u>Windows' service</u> through '''''run-as-service.bat'''''. Once done, it is visible into the Windows' services list. Then it is launched on the workstation boot.

See chapter [[#Start_the_application|Start the application]].

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">''<small>Click to see more technical details</small>''</div>
<div class="mw-collapsible-content">
</br></br>
''launcher.exe'' is the launcher application. It launches and updates the main application described below. It contains proxy and environment configuration files.

''<nowiki>get</nowiki>-service-status.bat'' displays the status of the sending service when it is installed as a Windows service

''remove-service.bat'' uninstalls the Windows service

''run-as-service.bat'' installs then runs the sending service as a Windows service

''sending-service.exe'' is located in the .\system\bin folder. This is the main application, used to send documents and containing all the business rules and configuration files linked to the operation of the application, such as dictionary-xsd and dictionary-workflow.

<span id="folder-hierarchy"></span>
== Folder hierarchy ==

Once installation is complete, three sub-folders will be present:

'''system''': this is the folder containing the technical elements of the application, and contains also three sub-folders:

::'''bin''': contains the main application executable

::'''config''': contains all client configuration files

::'''log''': contains all logs generated during application execution

'''sendingservice''': this is the folder containing all the sub-folders in which we will place our files for sending.<br />
For example, in the default configuration, if you want to send a KID file, you'll need to save the file in the following folder: ''sendingservice\fundregistration\luxembourg\opc''

'''tmp''': This is the folder containing all temporary files related to the application's operation.

</div>
</div>

<span id="logsy"></span>
== Logs ==
Each process creates its own log.</br>
sending-service.exe creates '''service-deposant-''timestamp''.log''' into .\system\log : it mainly contains information on the processing of your reports </br>
launcher.exe creates '''launcher-''timestamp''.log into .\log''' : it contains in particular information about the installation process</br>

[[File:SDjl_logs.png|400px|where are the log files ?]]

In case you think something goes wrong, you can open these files into a text editor and check if you see error messages. Also send them to us if you need us to check for you.

For a continuous monitoring, see also [[#Details_on_heartbeat_system]]

Running as a Windows' service, you can check the sending service's status launching '''''<nowiki>get</nowiki>-service-status.bat'''''

<span id="start-the-application"></span>

== Start the application ==

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the console mode... click</div>
<div class="mw-collapsible-content">
</br></br>
Once the application is installed:

Double-click [[File:SDjl_2.png|169x25px]] (''if you get this message:[[File:SDjl_3.png|264x89px|A windows's error message]], [[#protect_error|solve it]]'')

</div>
</div>

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the windows service mode... click</div>
<div class="mw-collapsible-content">
</br></br>
Once the sending service is installed as a Windows' service, use the windows' services app to start it :

[[File:SDjl_StartStopService.png|StartStopService|800px]]

</div>
</div>

<span id="stop-the-process"></span>

== Stop the application ==
<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the console mode... click</div>
<div class="mw-collapsible-content">
</br></br>

hit the keys '''Ctrl+C'''

</div>
</div>

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the windows service mode... click</div>
<div class="mw-collapsible-content">
</br></br>

If the sending service is running as a Windows' service, use the windows' services app to stop it :

[[File:SDjl_StartStopService.png|StartStopService|800px]]

</div>
</div>

<span id="administration-interface"></span>

= Administration Interface =

''New : The former .properties file is no longer a file onto your disk but the data are stored in our database and you can access them through the administration interface.''

In the administration interface, you can retrieve all the parameters you can set up. Note that some of them have default values and some are set up when the installation is done. You can make all the changes needed.

Sign in with the sending service account (or as an administrator) and click [[File:SDjl_8.png|194x55px|the administration module access button]]

then [[File:SDjl_9.png|158x37px]], you get :

[[File:SDjl_10.png|800px|the sending services control panel]]

Click the name of the sending service to change, click [[File:SDjl_11.png|47x39px]] to go back to the list.

[[File:SDjl_12.png|800px|the details' control panel]]

To change a value, click [[File:SDjl_13.png|60x39px|the edit button]], make your changes then save or discard.

[[File:SDjl_14.png|349x46px|group of three buttons]]

The ‘edit all workflows’ button, allow you to make massive changes in one shot.

Once the changes saves, you will get: [[File:SDjl_15.png|309x59px|a positive answer]]

The buttons [[File:SDjl_16.png|193x39px]], respectively exporting/importing the properties to/from .json format : to backup, to move from UAT to production or to import manual changes onto properties.

Note

* the automatic update set up:<br />
[[File:SDjl_17.png|246x46px]]<br />
This is related to the sending service’s version delivered by our IT team. Click the icon to change the automatic update’s status.
* the categories of parameters: [[File:SDjl_18.png|377x84px|the parameters categories menu]]
* the [[File:SDjl_19.png|137x50px|the expand button]] button

<span id="details-on-workflows-part"></span>
== Details on workflows part ==

Regarding the workflows, each one takes care of specific reports. You must enable those you want the sending service to send.

''For example, to send'' U11 reports'', you must enable the'' reporting_u ''workflow, the active box must be ticked, and a folder must be entered, you can keep the default one or change it. The'' intervalTimeInMinute ''is the frequency with which the directory will be scanned.''

[[File:SDjl_21.png|601x203px|example reporting U details]]

You can find the reports and their matching sending service workflow in our [[ProductCoverage|product coverage page]].

<span id="details-on-heartbeat-system"></span>

== Details on heartbeat system ==

The heartbeat is a monitoring system to check whether the sending service is still up or not. It pings the sending service at the chosen frequency and send an alert e-mail if the sending service doesn’t answer.

In the ‘properties’ category, you can set it up or down by ticking the box or not, and choose the frequency or the monitoring.

[[File:SDjl_22.png|601x338px|Heartbeat activation]]

In the ‘Heartbeat’ section, you can find statistics on heartbeat running and you can choose who will receive an alert e-mail when needed.

[[File:SDjl_23.png|800px|Heartbeat monitoring]]

<span id="section"></span>

= Manual installation using command prompt =
<span id="step-1-Stop_former"></span>
== <u>Step 1</u>: Stop the former instance ==

Be sure that no former instance of the sending service is running on the same environment. If so, [[Sending_Service_java-less_version#Stop_the_application | stop ]] it.

''If you install to replace the version with java, plan to use a new directory.''

<span id="step-2-download-the-launcher."></span>

== <u>Step 2</u>: Download the launcher. ==

The official version is always on the production site. You will be asked for homologation or production environment during the installation process. </br>To monitor and manage the properties, use the administration module on the relative website.

Connect to www.e-file.lu as the sending service (or as an administrator).

In the administration module, Sending service management:

[[File:V2_access.png|332x231px]]

Click:

[[File:SDjl_25.png|604x172px]]

The launcher will be downloaded into your default folder:

[[File:SDjl_26.png|262x101px]]

<blockquote>An alternative is to use this direct link, after logging into e-file :https://www.e-file.lu/fsq-graph/file/download/launcher-version/download?distribution=WINDOWS</blockquote><span id="step-3-install-the-new-sending-service-with-the-launcher"></span>

== <u>Step 3</u>: Install the new Sending Service with the launcher ==

<span id="copy-launcher.exe"></span>
=== copy ''launcher.exe'' ===
into the folder where you want to install the sending service

<span id="open-launcher.exe"></span>
=== Open launcher.exe ===
Double-click it [[File:SDjl_2.png|169x25px]] (''if you get this message:[[File:SDjl_3.png|264x89px|A windows's error message]], [[#protect_error|solve it]]'')

You will be asked:

<span id="enter-y-yes-or-n-no-for-the-question-are-you-using-a-proxy"></span>

=== Enter Y (yes) or N (no) for the question: Are you using a proxy? ===
[[File:SDjl_27.png|222x29px|question about the proxy]]

<span id="enter-the-environment-production-or-homologation"></span>
=== Enter the environment: PRODUCTION or HOMOLOGATION ===
The name must be entirely typed</br>
[[File:SDjl_28.png|604x22px]]

The sending service will be downloaded, wait a little.

[[File:SDjl_29.png|604x147px|See the progression bars]]

<span id="enter-username"></span>
=== Enter username ===
Enter the sending service’s account user name (the one usually ended by ...SD)

<span id="enter-the-username-password"></span>

=== Enter the username password ===
<span id="either-if-a-properties-config-file-is-found-on-the-server-and-you-want-to-use-it"></span>

=== Either: it is not the first installation : a properties file is found on the server ===

When you have already done an installation in the past, even if you have deleted it on your workstation, your previous setup is saved on our servers. So you will be asked if you want to overwrite it :

Enter N (no) for the question: ''overwrite the existing properties config file'', if you want to keep the previous setup.

Enter the password of your keystore.

<span id="or-if-no-properties-config-file-is-found-on-the-server-or-you-want-to-overwrite-the-existing-one"></span>

=== Or: If no properties file is found on the server OR you want to overwrite the existing one ===

Enter Y (yes) for the question: ''overwrite the existing properties config file''.

[[File:SDjl_30.png|604x15px]]

Then you will be asked :

<span id="enter-the-root-folder"></span>
: <span style="color:#21b8b5">'''Enter the root folder '''</span>
::It is the folder where you want the sending service to be installed: it must already exist.
::Entering none will take the current one.
::It is in this folder that the tree structure of sending folders will be generated. After that, for each upload there will be a concatenation between the root folder and the subfolder for each workflow. For example Let's take the rootFolder: "C:\NewSendingService" and the folder for the Key Investor Document "sendingservice/fundregistration/luxembourg/opc". The service will then fetch the documents with the path "C:\NewSendingService\sendingservice\fundregistration\luxembourg\opc". Be careful not to put an \ at the end of the specified path

<span id="enter-the-configuration-name"></span>
: <span style="color:#21b8b5">'''Enter the configuration name '''</span>
::Choose a name for your setup.

<span id="enter-your-keystore-file-path-optional."></span>
: <span style="color:#21b8b5">'''Enter your keystore file path (optional).'''</span>
::Please note that you must enter your keystore to transmit to Luxembourg authorities.

<span id="enter-authentication-cssf-optional"></span>
: <span style="color:#21b8b5">'''Enter Authentication CSSF (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-authentication-bcl-optional"></span>
: <span style="color:#21b8b5">'''Enter Authentication BCL (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-the-password-optional"></span>
: <span style="color:#21b8b5">'''Enter the password (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-authentication-code-optional"></span>
: <span style="color:#21b8b5">'''Enter authentication code (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-y-yes-or-n-no-for-the-question-do-you-want-to-close-the-app-after-installation"></span>
: <span style="color:#21b8b5">'''Enter Y (yes) or N (no) for the question: Do you want to close the app after installation ?'''</span>
::Yes means that only the installation will be done.
::No means that the sending service itself will be run after the installation and starts to file reports.

The process will continue, installing all the xsd files …

You can close the window, click the right-corner red cross.

<span id="update-the-sending-service"></span>

= Update the sending service =

== Change your setup ==

To change the sending service's setup: '''workflows; heartbeat, ... and also groups and permissions'''
* use the administration interface
* then [[#Stop_the_application|stop the application]] and [[#Start_the_application|start]] it again.

To change only the '''proxy''' setup
* In the folder .\system\config, delete the ''proxy-conf.json''
* then [[#Stop_the_application|stop the application]]
* On the root folder, launch ''launcher'' again, keep the existing properties config file.
* If you want to use the Windows' service, exit launcher (Ctrl+C) and [[#Start_the_application|restart]].

To change only one or several '''passwords'''

Note that the passwords are encrypted and asked just one time at the first installation. If you have to change them, you must install the whole application again :
* In the folder .\system\config, delete all the .json files (you can keep the ''proxy-conf.json'' and the ''environment.json'' files if they won't change)
* then [[#Stop_the_application|stop the application]]
* On the root folder, launch ''launcher'' again, keep the existing properties config file.
* If you want to use the Windows' service, exit launcher (Ctrl+C) and [[#Start_the_application|restart]].

<span id="upgrade-the-application"></span>

== Upgrade the application ==
=== Automatic upgrade===

This feature concerns the application updates affecting the sending service (SD) itself and that are applicable to all clients / users.

''Short description:''

Whenever the sending service starts, restarts, and every 30 minutes when it is up and running, it will check for updates. If an update is detected, and automatic update is selected (you can modify the value in the admin module page), the SD will stop the current process, reinstall the new version and rerun the process automatically. After a successful (or unsuccessful) update a notification will be sent per email.

If the client did not subscribe for automatic application updates and a new version of SD is available, an email will be sent to the client requesting them to update the SD. The client will then have to rerun the application and install the new version.

If the client does not update its SD in a specific timeframe, the sending service will stop running until it has been updated.

===Manual upgrade===

When a new version is available from our IT team you <span style="color: #C00000"> '''simply need to'''</span>: [[#Stop_the_application|stop the application]] then [[#Start_the_application|start]] it again through the launcher.exe.</br>
A prompt will as you to download the update: ''A new version is available do you want to download it now (Y/n) ?''</br>
You need to press ''Y'' and hit the ''Enter'' key.</br>
Once completed, the Sending Service will be updated.</br>
If the tool is installed as a Service, we advise you: '''to close this windows and restart the Service'''.</br>

'''<u>Important note :</u> unless a request from the FEFI team, there is no need to (re)download the ''Launcher.exe'' '''

<span id="submit-a-report"></span>

=Submit a report=

To send a report just copy it in the relevant folder depending on its type.

See the default sending folders tree:

[[File:SDjl_32.png|195x333px]]

You can relocate this folders tree to adapt it to your needs, using the administration interface to change the setup.

Then either enter ''root folder + relative tree folder path'' or ''empty root folder'' and enter an ''absolute path'' for the listener :

[[File:SDjl_ExplicPathFolder.png]]

<span id="sending-folders"></span>
==Default Sending Folders==

Scroll this list to find the sending type you need and where you must copy your reports for them to be processed:

<div style="height:300px; width:auto; overflow-y:scroll">

{| class="wikitable table-filterable sortable"
|+<span style="white-space:nowrap"></span>
|- <div style="position:sticky;top:-1px;z-index:10">
! width="44%" style="background-color:#21b8b5" |Sending type / type d'envoi
! width="55%" style="background-color:#21b8b5" | To be copied into / à déposer dans

|-
|08/371 FIS Prospectus
|sendingservice/fundregistration/luxembourg/fis
|-
| 08/371 FIS Reports
|sendingservice/fundregistration/luxembourg/fis
|-
|Non-LU UCI Registration
|sendingservice/fundregistration/luxembourg/fundsnotlu
|-
|Other closing docs of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Management letters of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Fin rep of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Key Investor Document
|sendingservice/fundregistration/luxembourg/opc
|-
|Management letters for CSSF 09/423
|sendingservice/fundregistration/luxembourg/opc
|-
|CSSF Attestation
|sendingservice/fundregistration/luxembourg/opc
|-
|Management regulation status
|sendingservice/fundregistration/luxembourg/opc
|-
|Notification Full
|sendingservice/fundregistration/luxembourg/opc
|-
|Long forms for CSSF 09/423
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 UCI Prospectus
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 Report
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 report not in 08/371
|sendingservice/fundregistration/luxembourg/other
|-
|BCL report for insurances
|sendingservice/regulatoryreporting/luxembourg
|-
|BCL SHS
| sendingservice/regulatoryreporting/luxembourg
|-
|AIF Reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting_s112-l
|sendingservice/regulatoryreporting/luxembourg
|-
|MIFIR reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting U
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting EDIFACT
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting IORP
| sendingservice/regulatoryreporting/luxembourg
|-
|Reporting CSDR
|sendingservice/regulatoryreporting/luxembourg
|-
|FATCA Report
|sendingservice/regulatoryreporting/luxembourg
|-
|CRS Report
| sendingservice/regulatoryreporting/luxembourg
|-
|FINREP
|sendingservice/regulatoryreporting/luxembourg
|-
|SICAR Reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|PSF Report
|sendingservice/regulatoryreporting/luxembourg
|-
|COREP Report
|sendingservice/regulatoryreporting/luxembourg
|-
|EME Report
|sendingservice/regulatoryreporting/luxembourg
|-
|EDP Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Credit institution reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Management company report
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting Money Market Fund
|sendingservice/regulatoryreporting/luxembourg
|-
|CSSF enquiry
|sendingservice/regulatoryreporting/luxembourg
|-
| TAF MIFID Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport distinct solvabilité 2 du réviseur
| sendingservice/regulatoryreporting/luxembourg
|-
|Distinct solvency company Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport Narratif (Réviseur)
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport Narratif (compagnie)
|sendingservice/regulatoryreporting/luxembourg
|-
|Solvency II reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Titrisation Vehicles
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting TPT
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting securities by securities of issuing companies
|sendingservice/regulatoryreporting/luxembourg
|-
|Issuing companies reporting
|sendingservice/regulatoryreporting/luxembourg
|-
| Payment’s balance
|sendingservice/regulatoryreporting/luxembourg
|-
| AnaCredit
|sendingservice/regulatoryreporting/luxembourg
|-
|Security by Security banks
|sendingservice/regulatoryreporting/luxembourg
|-
|BCL statistics
|sendingservice/regulatoryreporting/luxembourg
|-
|Data payment collection
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting S
|sendingservice/regulatoryreporting/luxembourg
|-
|Various correspondence (OTH)
|sendingservice/regulatoryreporting/luxembourg/otherbcl
|-
|Other reporting for CSSF
|sendingservice/regulatoryreporting/luxembourg/othercssf
|-
|Reporting O
|sendingservice/regulatoryreporting/luxembourg/reporting_o
|-
|Reporting ICS
|sendingservice/regulatoryreporting/luxembourg/
|-
|DORA Incident Reporting
|sendingservice/regulatoryreporting/luxembourg/
|-
|DORA Register of Information
|sendingservice/regulatoryreporting/luxembourg/
|-
|Self-assessment questionnaire PDAOFI
|sendingservice/regulatoryreporting/luxembourg/
|}
</div>

<span id="check-for-acknowledgment-and-feedbacks"></span>

=Check for acknowledgment and feedbacks=

Once a report is sent, it is renamed as .trt and move into an auto-generated subfolder called ''reporttransmitted, ''
a file with extension .acq is also created as an acknowledgement.

[[File:SDjl_33.png|276x70px|the reporttransmitted folder]]

If an error occurs, you get a file with extension ''.err''. Open it and read the messages.

The feedbacks from the authority will come into ''feedbacks.'' Remember to read them.

<span id="transmission-following"></span>
==Transmission following==

Here are the default transmission follow up files that are created depending on the state in the transmission workflow.

{|
! width="13%" |'''File extension'''
! width="86%" | '''Description'''
|-
| '''.trt'''
|
<u>Example </u>: file processing of '''FileName.ext'''

Once the file has been dropped into the appropriate folder, the Sending Service will start processing it and rename it as follows:

'''FileName.ext_YYYYMMDDhhmmssmmm.trt'''
|-
|'''.acq'''
|
Once the processing finished an '''.acq''' file will be generated in the same folder by the Sending Service in order to confirm the transmission:

'''FileName.ext_YYYYMMDDhhmmssmmm.acq'''
|-
|'''.err'''
|
An '''.err file is created in case or an error:'''

'''FileName.ext_YYYYMMDDhhmmssmmm.err'''

Please open this file and analyse the error message.
|}

<span id="feedback-files-replies-folder"></span>
==Feedback files (Replies folder)==

For some reporting, the administration will give you a more detailed feedback. The feedbacks from the authority will come into ''feedbacks.''

<s>By default, <u>feedback files</u> are dropped into '''Replies''' sub-folders. '''Replies''' folders are created dynamically in the initial transmission folder of the files. They only appear when feedback files, sent by the supervisory authorities, have to be stored. If the folder is deleted, it will be automatically recreated upon receipt of new feedback files.

The name and location of the '''Replies''' folder may be configured differently from the implementation of the solution with your company’s project coordinator </s>

{|
! width="10%" |'''Autority'''
! width="89%" |'''Description'''
|-
|'''CSSF'''
|
Feedback files generated and sent by the CSSF.

Please click the picture below to access the '''Naming convention for CSSF reportings''' document:

[[File:SDjl_34.png|500x135px|A close-up of a screen Description automatically generated]]
|-
|'''BCL'''
|
Feedback files generated and sent by the BCL.

The BCL sends feedback with the following naming convention :

FDBTECH_[OK/KO]_[YYYYMMDD]_[SENT FILE NAME]_[RANDOM CARACTERS].xml

With

<ul>
<li> <blockquote><p>[OK/KO] : replaced either by OK (if the files has been transmitted and processed successfully) or KO (if there has been an error)</p></blockquote></li>
<li><blockquote><p>[YYYYMMDD] : replaced by the date of the feedback</p></blockquote></li>
<li><blockquote><p>[SENT FILE NAME] : replaced by the complete name of the original file (including it's extension)</p></blockquote> </li>
<li><blockquote><p>[RANDOM CARACTERS] : replaced by a random and unique caracters.</p></blockquote></li></ul>
|}

<ul>
<li><blockquote><p>'''For other reporting''' (08/371 / VNI...), '''there is no additional acknowledgment'''.</p></blockquote></li></ul>

This means that only '''acq''' will be created.

'''<u>Conclusion</u>''' : '''Checking that both trt and acq files were generated is a good way to ensure the good working of the Sending Service'''. Doing this way, you can be sure that your data was properly sent and '''e-file will be in charge of forwarding them to authorities'''.

=Solving known problems=

<span id="protect_error"></span>
*If you get this when double-clicking the launch.exe :

[[File:SDjl_3.png|552x140px|Protection Error Windows]]

Right-click the launch.exe file, then tick unblock : [[File:Sdjl_LauncherProperties.png|Protection Error Windows Solution]]

Or

click the address bar in the file explorer: [[File:SDjl_4.png|409x40px]] [[File:SDjl_5.png|335x33px|the adress bar]]

type ''cmd,'' [[File:SDjl_6.png|137x71px|where to type cmd]] then type ''launcher'' [[File:SDjl_7.png|379x83px|the command line windows]]

<span id="process_blocked"></span>
*Sometimes in console mode, the process seems to be blocked :

[[File:SDjl_BlockedProcessExamples.png|552x140px|Blocked processes]]

First try to hit ''Enter'' or ''space''. <br> If it is still blocked, you must stop it (CTRL+C) and [[#Start_the_application| restart it]].

*Error message when installing :

[[File:SDjl_InstallErr1.png|800px|Installation error message 1]]

Hit ''Enter'' twice, the program will ask for the username again, and go on.

*Error message after stop and start (401):

[[File:SDjl_InstallErr2_401.png|800px|Installation error message 2]]

The sending service password may have changed. You must install it again.

*Setup changes not applied despite being saved

After each change through the administration module, please [[#Stop_the_application|stop]] and [[#Start_the_application|start]] the sending service again.

= Certificate Update =

Once your Luxtrust certificate is activate in E-file, you need to replace the new keystore in the sending service.

If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
In this case you can use a simplified process by '''<u>simply replacing the keystore:</u>'''
(-) Stop the Sending Service
(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
(-) Copy the new keystore (to the sending service keystores folder.
(-) Rename this copy as the previous one.
(-) Restart the Sending Service

In case of a '''different kesytore password''', you '''<u>will have to reinstall the Sending Service</u>'''.<br>
You need import the new keystore and then [[#Change_your_setup|change the step-up ]] of your Sending Service

Sending Service

2026-05-04T09:18:40Z

Cso: /* Certificate Update */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

__TOC__

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

= Operating principle =

The '''Sending Service''' is our solution for the '''automatic transmission''' of reports and documents to authorities.

This solution is useful if you have a '''large number of reports''' to submit or if the manual sending does not suit your needs.

Please be aware that, in this case you will have to provide the files yourself according to the authorities' file specifications.

This tool is compatible with most of the current operating systems (Windows / Unix / Linux) and is usually <span style="color: #C00000">'''installed on a server'''</span> on your side.

With a suitable '''network mapping''', users can simply '''drop the file to be sent into the appropriate directory'''.

The file is then automatically ''' encrypted and sent'''.

= Prerequisites =

*Internet access
*<span style="color: #C00000">'''Java version 1.8 </span> <u>Note :</u> versions 8_351 and higher need a patch to be used with our system, see :[[Error_messages_list#JCE_cannot_authenticate_the_provider_BC]]'''
*If you use a proxy, authorize outgoing calls to [https://www.e-file.lu www.e-file.lu]. Port 443 (HTTPS) must be open.
*<span style="color: #C00000">'''Administrator rights''' </span> to install the Sending Service on the computer ''(Windows Start button > Control Panel > User Accounts > Manage User Accounts)''.
*OS: Windows or Linux
*Processor: Pentium 2 GHz or equivalent
*8 GB of RAM
*1 GB of free space on hard disk drive if the files are downloaded by ftp. If files are locally stored, provide a free space of above 100 MB or a regular purges.
*1 GB of free space on hard disk drive for logs. Regular purges are necessary as well.
*A <span style="color: #C00000">'''Sending Service user''' </span>, ''for example: aacSD'', and its password, ''for example: formation'', have to be available [[E-file_Administration#e-file_administrator_functions_.28e-file_v1.29|'''=> e-file administrator''']].
*The e-file account of the Sending Service user has to be linked to groups/modules, for example FATCA reporting + profile "Sending Service".
*A valid <span style="color: #C00000">'''keystore''' </span> (keystore.ks) and its <span style="color: #C00000">'''password''' </span> must be available
*The Sending Service user has to be properly configured in the e-file user administration tool in order to be able to receive <span style="color: #C00000">'''alerts''' </span> (receipt of acknowledgement and feedback files).

Note that you can find the prerequisites for the manual transmission there : [[Transmission_Module#System_requirements]]

= Installation / update with Sending Service Installer =

The Sending Service Installer is a tool that helps you install or configure quickly your Sending Service.

It can be downloaded from these links:

'''[https://www.e-file.lu/WSEfileFlex/messagebroker/assistantSD?cdLangIso=EN English version]'''

'''[https://www.e-file.lu/WSEfileFlex/messagebroker/assistantSD?cdLangIso=FR French version]'''

Once you have downloaded the application you will have to run it with Java by clicking the Run button.

[[File:Doc_SDInstaller_01.png|border|400 px]]

''If the message'' unable to run the application ''occurs, [[Transmission_Module#Delete_Java_cache|delete the java cache.]]''

'''The front page of the Sending Service Installer opens and shows you the different functionalities you can select: '''

* Install a new Sending Service
* Configure an existing Sending Service
* Update an existing Sending Service
* Send logs

[[File:Doc_SDInstaller_02.png|border|600 px]]

== Installation ==

'''Controls before installation:'''
* Check that the connected user is administrator of the computer
* Have an e-file Sending service user (login and password) (e.g. : aacSD)

To check whether a Sending service user exists, log on as an e-file administrator.
<u>'''Step 2</u>:'''

Click the '''Administration module'''

[[File:AdminAccess.png|700px]]

The user linked to the Sending Service usually follows the bellow naming rules : three
letters referring to the company (in lower case) following by "SD" in upper case. (e.g. :
aacSD)

[[File:User Sending service.png|900px]]
If the user doesn't exist, please contact us.

'''Start installation:'''
To install a <u> new </u> Sending Service, click on the button Install on the front page.

<u>'''Step 1'''</u>: Select the folder where you want to install your Sending Service.

[[File:Doc_SDInstaller_03.png]]

<u>'''Step 2'''</u>: The Sending Service is downloaded and saved in the selected folder.

<u>'''Step 3'''</u>: Select the keystore file, containing your LuxTrust certificate.

[[File:Doc_SDInstaller_04.png]]

<u>'''Step 4'''</u>: The Sending Service is ready to be configured. By clicking the '''Configuration''' button, you will be redirected to the '''Configuration menu''' of the '''.properties file'''.

[[File:Doc_SDInstaller_05.png]]

==Configuration==

To configure an <u>existing</u> Sending Service you have to select the folder where it is stored and click on the '''Configuration''' button.

[[File:10 SendServConf.png|border|600 px]]

The '''configuration''' of an existing Sending Service is similar to a new Sending Service.

<span style="background:yellow"> '''IMPORTANT:''' </span> each time you make changes to the properties (configuration) file, you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]] before, make your changes and then install the Sending Service again.

'''Configuration''' menu of the '''.properties file''' ([[Sending_Service#Configuration of the properties file | => Help: Configuration of the properties file]]):

[[File:Doc_SDInstaller_06.png|border|500 px]]

The '''Configuration''' menu allows you to setup your Sending Service.

The message ''Error: There are errors in your setup'' indicates that nothing has been set-up so far.

You have to configure each field marked in red.

If you have a '''proxy''', select ''True'' in the dropdown list and select ''More'' to type in the proxy settings.

''Note: The passwords will be asked during the finalization of the installation, all passwords are encrypted.''

''Note 2: You can edit each field by clicking the More button''

[[File:Doc_SDInstaller_07.png|border|600 px]]

The '''listeners''' can be activated in one shot by clicking on the button ''Listener state : Activate all''.

''Note: This functionality will force the Sending Service to scan all the folders, if you do not want all listeners to be activated, please activate manually the listeners you need.

Please consult our [[Sending_Service#Listener_list | Listener list]].

[[File:Doc_SDInstaller_08.png|border|600 px]]

If you have to submit Investment Funds reporting O4.1; O4.2 (EDIFACT format), you must complete this fields :

'''domain.descr''': Not relevant. You can provide abbreviated name of the Central Administration.

'''domain.env.ac.id.bcl''': this code is composed of a letter and six digits and has been provided to you by the CSSF (Example: P123, should be written as “P000123”).

'''domain.env.ac.id.cssf''': this code is composed of a letter and six digits and has been provided to you by the CSSF (Example P123, should be written as “P000123”).

The two others will be asked when installing (domain.en.ac.cd_auth and domain.env.ac.pwd)

[[File:Doc_SDInstaller_09.png|border|500 px]]

Once the configuration finished, you can click on '''Control''' to check if there is a configuration error.

The message ''No error in your setup'' means that the setup is correct.

[[File:Doc_SDInstaller_10.png|border|500 px]]

If there are no errors, you can click on '''Save''' to save your actual configuration.

[[File:Doc_SDInstaller_11.png|border|500 px]]

To install the Sending Service, you have to click on the '''Install''' button.

A pop-up window opens where you have to enter your passwords.

If you do not use a proxy, you can leave a blank for the proxy password<br/>
If you need to send O4.1 or O4.2 reports enter also those :<br/>
CA Password = '''domain.env.ac.pwd''': this '''authentication password''' has been provided to you by the CSSF (postal mail).<br/>
CA Code = '''domain.en.ac.cd_auth''': this '''authentication code''' has been provided to you by the CSSF (postal mail).<br/>

[[File:Doc_SDInstaller_12.png|border|500 px]]

Once finished a pop-up windows opens stating that the installation has been successful:

[[File:Doc_SDInstaller_13.png|border|500 px]]

To start your Sending Service open the folder where you installed it and run the file '''run.bat''' or '''InstallServiceNT.bat''' if you want to install the Service as a '''Windows Service'''.

[[Sending Service#Installation as a Windows Service|=> Installation as a Windows Service]]

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

==Update==

<span style="background:yellow"> '''IMPORTANT:''' </span> before updating your Sending Service you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]].

To update an <u> existing </u> Sending Service you have to click the ''Update'' button.

Then click on '''Check''' in order to verify if a new version is available.

[[File:Doc_SDInstaller_16.png|border|600 px]]

If your Sending Service is up-to-date you will get the following message:

[[File:Doc_SDInstaller_17.png|border|600 px]]

If there is a new version of the Sending Service available the following window will appear:

[[File:Doc_SDInstaller_18.png|border|600 px]]

To continue the update, click on Ok.

During the first steps, the new version will be downloaded.

Once you have reached step 3, the tool will ask you to select your old '''configuration''' file ('''.properties file''')

[[File:Doc_SDInstaller_19.png|border|600 px]]

The tool will automatically back-up of your old Sending Service. You have to wait until the process is finished.

[[File:Doc_SDInstaller_20.png|border|600 px]]

Step 5 will be the '''configuration''' of the updated Sending Service. You have to click on '''Configuration''' to access the '''Configuration''' menu.

[[File:Doc_SDInstaller_21.png|border|600 px]]

If there are changes in the configuration file of the Sending Service with the new version, the fields will be marked in red. You will have to select the proper setup and save the changes.

[[File:Doc_SDInstaller_22.png|border|600 px]]

Once the configuration finished, you can click on '''Control''' to check if there is a configuration error.

The message ''No error in your setup'' means that the setup is correct.

[[File:Doc_SDInstaller_10.png|border|500 px]]

If there are no errors, you can click on '''Save''' to save your actual configuration.

[[File:Doc_SDInstaller_11.png|border|500 px]]

To install the Sending Service, you have to click on the '''Install''' button.

A pop-up window opens where you have to enter your passwords.

''Note : If you do not use a proxy, you can leave a blank for the proxy password''

[[File:Doc_SDInstaller_12.png|border|500 px]]

==Send logs==

If you encounter issues with your Sending Service, you can use the Help function to send an email to the [[How to contact us|'''Client Support & Operations Desk''']].

The tool will create automatically a zip file containing the log files of your Sending Service you can attach to the email.<br><br>

[[File:Doc_SDInstaller_23.png]]

[[File:Doc_SDInstaller_24.png]]

= Manual installation with Command Prompt =

* Download the latest Sending Service version here: [https://www.e-file.lu/WSEfileFlex/SD/SD.zip '''Download latest Sending Service version''']
For UAT environment the latest version [https://homologation.e-file.lu/WSEfileFlex/SD/SD.zip '''is available here''']

* Extract and copy the entire content of the directory ServiceDeposant in the Sending Service directory. Ensure that the directory is <span style="color: #C00000">'''not read only''' </span>.
[[File:SD.png| 600 px]]

* Copy your <span style="color: #C00000">'''keystore'''</span> in the keystores folder of the Sending Service.

* Copy the <span style="color: #C00000">'''template_configInstall.properties'''</span> file and rename it [sender''Name''].properties.

* Complete the <span style="color: #C00000">'''properties file'''</span> as explained in [[Sending Service#Configuration of the properties file|'''Configuration of the properties file''']] chapter.

* Install the new Sending Service:
(-) Open Command Prompt
(-) Move to the root folder of your new Sending Service (for example: C:\Program Files\e-file\ServiceDeposant\)
(-) install.bat [sender''Name''].properties
(-) enter the root path of your JRE (for example: C:\Program Files\Java\jre1.8)
(-) Enter the password of the e-file Sending Service user
(-) Enter the password of your keystore
(-) Enter the password of your proxy if you use a proxy
(-) Enter the O4.x password for CSSF/BCL if needed
(-) Enter the O4.x authentication code for CSSF/BCL if needed
(-) Press the ENTER key

<span style="background:yellow"> '''IMPORTANT:''' </span>

SECURITY ENHANCEMENTS (june 2023)

The security settings of the Sending Service have been enhanced for O4.1 and O4.2 reports, the related passwords are now encrypted.

Please note that the installation procedure of the Sending Service slightly changed due to the implementation of this feature:

[[File:SD_CmdInstall.png | 800 px]]

At the end of the script you must get the following message: <span style="background:yellow"> '''BUILD SUCCESSFUL''' </span> indicating that the installation was successful.

[[File:SD_CmdInstall_success.png | 200 px]]

<span style="background:yellow"> '''IMPORTANT:''' </span> each time you make changes to the properties (configuration) file, you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]] before, make your changes and then install the Sending Service again.

== Configuration of the properties file ==

The <u>.properties</u> file (''template_configInstall.properties'') contains important information which are necessary to '''generate your configuration files''' during the physical installation.

The latter are used to start and use the Sending Service.

In other words :

* <span style="color: #C00000">'''The <u>.properties</u> file contains all the variables needed to run the Service Service.'''</span>

* <span style="color: #C00000">'''Any modification of the <u>.properties</u> file must be followed by an installation of the Sending Service to be really applied.'''</span>

<span style="color: #C00000">'''Please find below important information on how to configure your <u>.properties</u> file.''' </span>

<span style="color: #C00000">'''Please note, that at the end of setup, no '?' should remain in this file. </span>

'''E-file configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''efile.hostname=????'''''
|style="width:20em"| <span style="color: #C00000">'''www.e-file.lu'''</SPAN> for production environment,<br> or <br><span style="color: #C00000">'''homologation.e-file.lu'''</span> for test environment.
|-
|style="width:20em"| '''''efile.userId.Login=????'''''
|style="width:20em"| e-file login of the Sending Service user (Example: abcSD)
|-
|style="width:30em"| '''''keystore.path=@PROJECT_ROOT_PATH@/keystores/????.ks'''''
|style="width:20em"| path of the keystore (xxxx.ks)
|-
|style="width:20em"| '''''lang.code=FR??EN'''''
|style="width:100em"| language of the acknowledgement files
|}

'''Proxy configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''proxy.required=false??true'''''
|style="width:50em"| <span style="color: #C00000">'''true'''</span> if a proxy is used to access the internet through HTTP or HTTPS.
|-
|style="width:30em"| '''''proxy.host=???? <br> proxy.port=???? <br> proxy.user=???? <br> proxy.domainNTLM=????'''''
|style="width:100em"| Complete all other parameters according your network infrastructure.
|}

'''Configuration of connection for authority acknowledgement / feedback files'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''reportingXXXXXX.state=up??down'''''
|style="width:50em"| All subsequent blocks in the .properties file corespond to a particular type of reporting.

Please consult our [[Sending Service#Listener list|'''Listener list''']] to verify which reporting type is linked to which listener.

Example: if you only have to sent FATCA reportings, the state of the listener reportingFATCA.state has to be up: '''reportingFATCA.state='''<span style="color: #C00000">'''up'''</span>'''

The other listeners should be <span style="color: #C00000">'''down'''</span>.

|-
|style="width:30em"| '''''reportingXXXXXX.remoteDir'''''
|style="width:50em"| <span style="color: #C00000">'''Path to file location'''</span> for the relevant reporting.

|-
|style="width:30em"| '''''@PROJECT_ROOT_PATH@'''''
|style="width:50em"| <span style="color: #C00000">'''Dynamic parameter'''</span> indicating the Sending Service installation path.<br>
To change if you want to locate the user working directory elsewhere on the server or another machine.
In this case, indicate the full path to file (separator = '/').

|-
|style="width:30em"| '''''reportingXXXXXX.scheduleTime'''''''
|style="width:50em"| <span style="color: #C00000">'''Execution frequency'''</span> of Window Service to process files from this folder (30mn by default).
Feel free to '''reduce this value, but do not fall below 5mn= <i><span style="color: #C00000">300000</span></i>'''.

|-
|style="width:30em"| '''''reportingXXXXXX.deeplevel'''''''
|style="width:100em"| <span style="color: #C00000">Number of '''sub-levels'''</span> to scan.<br>
By default the value is <span style="color: #C00000">'''0'''</span>, which means that only files at the root of the folder will be taken in account.

|}

'''Business environment properties'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''domain.descr'''''
|style="width:20em"| Not relevant. You can provide '''abbreviated name''' of the Central Administration.
|-
|style="width:20em"| '''''domain.env.ac.id.cssf'''''
|style="width:20em"| Your <span style="color: #C00000"> '''CSSF identifier'''</span> of 7 characters, 1 letter and 6 numbers'''
|-
|style="width:30em"| '''''domain.env.ac.id.bcl'''''
|style="width:20em"| Your <span style="color: #C00000"> '''BCL identifier'''</span>
|-
|style="width:20em"| domain.env.ac.pwd
|style="width:50em"| Doesn't appear anymore in the .properties, it will be asked when installing. <span style="color: #C00000">'''Password'''</span> of the Central Administration provided by the CSSF
|-
|style="width:20em"| domain.env.ac.cd_auth
|style="width:100em"| Doesn't appear anymore in the .properties, it will be asked when installing. <span style="color: #C00000">'''Authentication code'''</span> of the Central Administration provided by the CSSF.

The CSSF has provided you in an official letter your <span style="color: #C00000">'''password'''</span> and <span style="color: #C00000">'''authentication code'''</span>. The above mentioned IDs, passwords and codes are necessary for the successful processing of the O4.1, O4.2; O1.2 and the former O1.1 reporting.
|}

'''Configuration of monitoring'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''mon.app.heartbeat=false'''''
|style="width:20em"| If parameter is "true", we will be able to send you an alert if an interruption of your service is detected on our side (within 72 hours).
'''Should you want to use this feature feel free to contact us'''

|-
|style="width:20em"| '''''mon.app.origin=????'''''
|style="width:20em"| <span style="color: #C00000">'''Unique name'''</span> , without space, to enable us to identify your Sending Service. Not mandatory.
|-
|style="width:30em"| '''''mon.task.dist.period=60000'''''
|style="width:100em"| Frequency of the heartbeat (here 60000 milliseconds, 1 min). The monitoring window is set to 9 minutes. At least one heartbeat must have been registered during this interval otherwise the Sending Service is considered as down.
|-
|}

== Listener list ==

{|border="1" cellspacing="2" cellpadding="10"
|-
! Listener
! Sending Service folder
! Reporting type
! Business group
|<span style="color: #868686"> <small>''Internal <br /> Technical <br /> Business ID''</small/> </span>
|-
|<span style="color: #868686"> <small>''Please be informed that the listener '''efile.listener.state''' is no longer available in the properties file''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|-
|<span style="color: #868686"> <small>''Please be informed that the listener '''efile.replies.listener.state''' is no longer available in the properties file''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|-
| reportingMMF=up
|(-) ReportingDiffusion/MMF''
| <small>CSSF - MMF
| Money Market Fund Reporting
| <span style="color: #868686"> <small>''83-Money Market Fund Reporting''</small/> </span>
|-
| reportingOPC.automatique.state=up
|(-) ReportingDiffusion/OPC/envoi_Automatique/fichiersCCLUX<br><span style="color: #868686"> <small>''(-) ReportingDiffusion/OPC/envoi_Automatique/fichiersCCLUX/Enrichment''</small/> </span><br><span style="color: #868686"> <small>''(-) ReportingDiffusion/OPC/envoi_Automatique/TPT_FINESTI''</small/> </span>
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL : S1.3, S1.6, S2.13, TPTOBS, S4.4, S2.20 </small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPCExportXLS.automatique.state=up
| ReportingDiffusion/OPC/envoi_Automatique/ExportXLS
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL : S1.3, S1.6, S2.13, TPTOBS</small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPC.envoi_Historique.state=up
| ReportingDiffusion/OPC/envoi_Historique/fichiersCCLUX
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL: S1.3, S1.6, S2.13, TPTOBS</small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPC.semiAuto.state=up
| n/a
| n/a
| n/a
| n/a
|-
|reportingVni.state=up
|ReportingDiffusion/VNI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingDividende.state=up
| ReportingDiffusion/Dividendes
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingTAF.state=up
| (-) ReportingDiffusion/TAF<br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/declaration_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Rapport''</small/> </span>
| <small>CSSF: transactions in financial instruments (TAF)</small/>
| Report TAF-MIFID
| <span style="color: #868686"> <small>''71-MiFIR reporting''</small/> </span>
|-
|-
| reportingTAF.state=up
| (-) ReportingDiffusion/TAF<br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/declaration_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Rapport''</small/> </span>
| <small>CSSF: transactions in financial instruments (TAF)</small/>
| Report TAF-MIFID
| <span style="color: #868686"> <small>''71-MiFIR reporting''</small/> </span>
|-
| reportingIORP.state=up
| ReportingDiffusion/IORP
| <small>CSSF - Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019 </small/>
| Report IORP
| <span style="color: #868686"> <small>''80''</small/> </span>
|-
| reportingCOREP.state=up
| ReportingDiffusion/COREP
| <small>CSSF:<br> SCOREP; SLAREX; SLCRXX; SNSFRX; SALMXX; CCOREP;<br>CLAREX; LCRXX; CNSFRX; CALMXX; CFINRP; SFINRP;<br>AEXXX; SAEXXX; CFPXXX; SFPXXX; CSBPXX;<br>SSBPXX; CSBPIM; SSBPIM; CLCRDA; SLCRDA; ALMXXX</small/>
| Rapport COREP
| <span style="color: #868686"> <small>''72-COREP reporting''</small/> </span>
|-
| reportingFINREP.state=up
| ReportingDiffusion/FINREP
| <small>CSSF: B2.4; B2.5; LCRDAX</small/>
| Rapport FINREP
| <span style="color: #868686"> <small>''73-FINREP reporting''</small/> </span>
|-
| reportingFINREP.EDIFACT.state=up
| ReportingDiffusion/FINREP/EDIFACT_CSSF
| <small>CSSF: B4.4</small/>
| Reporting EDIFACT
| <span style="color: #868686"> <small>''16-Edifact''</small/> </span>
|-
| reportingBOP.state=up
| ReportingDiffusion/BOP
| <small>BCL - Credit institutions: Balance of payments (BOP1.1; BOP1.2)</small/>
| Balance des Paiements
| <span style="color: #868686"> <small>''12-Edifact reporting''</small/> </span>
|-
| reportingBCLStat.state=up
| ReportingDiffusion/BCL_Statistics
| <small>BCL - Credit institutions: S0.1; S1.1; S1.4; S1.5; S1.8; S1.9;S1.12<br>S2.5-L; S2.5-N; S2.8; S2.9-L; S2.9-N; S3.2</small/>
| Statistiques BCL
| <span style="color: #868686"> <small>''13-BCL statistics''</small/> </span>

|-
| reportingAnacredit.state=up
| ReportingDiffusion/Anacredit
| <small>ANTREF; ANTT1M; ANTT2M; ANTT2Q</small/>
| Rapport Anacredit
| <span style="color: #868686"> <small>''74 ANACREDIT reporting''</small/> </span>

|-
| reportingSecurisation.state=up
| ReportingDiffusion/Securisation
| <small>BCL - Securitation vehicles: S2.14; S2.15; TPTTBS</small/>
| Véhicule titrisation
| <span style="color: #868686"> <small>''23-Véhicule titrisation''</small/> </span>
|-
|reportingSecurisationS2.14ExportXLS.state=up<br>reportingSecurisationS2.15ExportXLS.state=up<br>reportingSecurisationTPTTBSExportXLS.state=up
| ReportingDiffusion/Securisation/ExportXLS
| <small>BCL - Securitation vehicles:S2.14; S2.15; TPTTBS</small/>
| Véhicule titrisation
| <span style="color: #868686"> <small>''23-Securitisation vehicule''</small/> </span>
|-
| reportingTPTB.state=up
| ReportingDiffusion/TPT
| <small>BCL - Credit institutions: TPTBBL; TPTBBN; TPTBHR; TPTBHN</small/>
| Titre par Titre Bancaire
| <span style="color: #868686"> <small>''20-Security by security reporting''</small/> </span>
|-
| reportingTPTBExportXLS.state=up
| ReportingDiffusion/TPT/ExportXLS
| <small>BCL - Credit institutions: TPTBBL; TPTBBN; TPTBHR; TPTBHN</small/>
| Titre par Titre Bancaire
| <span style="color: #868686"> <small>''20-Security by security reporting''</small/> </span>
|-
| reportingESP.state=up
| ReportingDiffusion/ESP
| <small>CSSF: Special Enquiries (ESPREP)</small/>
| Rapport Enquête
| <span style="color: #868686"> <small>''15-CSSF polls''</small/> </span>
|-
| reportingPSF.state=up
| ReportingDiffusion/PSF
| <small>CSSF - Professional of the financial sector (PSFREP)</small/>
| Rapport PSF
| <span style="color: #868686"> <small>''18-PSF reporting''</small/> </span>
|-
| reportingSICAR.state=up
| ReportingDiffusion/SICAR
| <small>CSSF - SICAR</small/>
| Rapport SICAR
| <span style="color: #868686"> <small>''17-SICAR reporting''</small/> </span>
|-
| reportingOTH.state=up
| ReportingDiffusion/OTH
| <small>CSSF - Other reporting (OTHREP)</small/>
| Reporting OTHER (CSSF)
| <span style="color: #868686"> <small>''19-OTHER reporting (CSSF)''</small/> </span>
|-
| reportingRFOPC.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_OPC
| <small>CSSF UCI: <br /> (-) Annual Report (AR) <br /> (-) Semi-annual report (SR) <br /> (-) Letter of explanation (LE) <br /> (-) Other periodic report(RO) <br /> (-) Movements in the securities portfolios (MP)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>

|-
| reportingRAFIS.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_FIS
| <small> CSSF SIF: <br />
(-) Annual Report (AR) <br />
(-) Semi-annual report (SR) <br />
(-) Letter of explanation (LE) <br />
(-) Other periodic report (RO) <br />
(-) Movements in the securities portfolios (PM)</small/> <br />
<small> SICAR: <br />
(-) Annual Report (AR) <br />
(-) Annual Report (RO) </small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingPOPC.state=up
| ReportingDiffusion/DOC_FIS_OPC/PROSP_OPC
| <small>CSSF UCI: <br /> (-) Prospectus (PC) <br /> (-) Simplified prospectus (PS) <br /> (-) Letter of explanation (LE)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingPFIS.state=up
| ReportingDiffusion/DOC_FIS_OPC/PROSP_FIS
| <small>CSSF SIF: <br /> (-) Prospectus (PC) <br /> (-) Offering document (DE) <br /> (-) Letter of explanation (LE)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingKID.state=up
| ReportingDiffusion/DOC_FIS_OPC/KID_OPC
| <small> Key Investor Information Document (KID) <br />
(-) O: OPC Law 2010 and Law 2007 <br />
(-) K: SICAR <br />
(-) V: non-reglem. <br />
[[Sending Service#Automating process for KID packages|=> Automated process for KID packages]]</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingMR.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_REGUL
| <small>CSSF - Management Regulations of UCITS (MR)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingAI.state=up
| ReportingDiffusion/DOC_FIS_OPC/ART_INCORP
| <small>CSSF - Articles of Incorporation of UCITS (AI)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingML.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_LETTER
| <small>CSSF - Management Letters (ML) <br />
(-) O: OPC Law 2010 and Law 2007 <br />
(-) K: SICAR <br />
(-) V: non-reglem. <br />
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingLF.state=up
| ReportingDiffusion/DOC_FIS_OPC/LONG_FORM
| <small>CSSF - Long Form reports (LF)
(-) O: OPC Law 2010
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
|reportingMLGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_GFI
|<small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingRGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_GFI
|<small> CSSF <br />
Annual management company report <br />
Management company report, other frequency <br />
Explanation letter</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingDOC_OTH.state=up
| ReportingDiffusion/DOC_FIS_OPC/OTHER
|<small> CSSF <br />
Auditor's report (RR) <br />
Explanation letter (LE) (for funds or Sicar, CSSF codification S or A) <br />
Report Hong Kong Securities and Futures (HK)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingCSDR.state=up
| ReportingDiffusion/CSDR
|<small> CSSF <br />
Report CSDR</small/>
| Reporting CSDR-9
| <span style="color: #868686"> <small>''78-Reporting CSDR''</small/> </span>
|-
| reportingGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/DOC_GFI
| <small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)

(-) Risk management function(GR) <br />
(-) OPCVM instruments information (ID) <br />
(-) Compliance Function (FC)<br />
(-) Internal audit function report (IA)<br />
(-) Complaints handling (TP) <br />
(-) Authorized third party complaints (LP) <br />
(-) Risk Management Procedure (PG)<br />
(-) Organization chart (OG) <br />
(-) Mandates table (TM) <br />
(-) Delegates of RFI (RD) <br />
(-) Branch activity (AS), <br />
(-) Own funds ratio (FP) <br />
(-) Risk management procedure AIFM (PN) <br />

</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingAML-AIFM-REG.state=up
| ReportingDiffusion/DOC_FIS_OPC/AML_AIFM_REG
| <small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)

(-) Letter of explanation (LE) <br />

</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingCD.state=up
| ReportingDiffusion/Various_Correspondence
| <small>BCL - Other reporting (OTX)</small/>
| Reporting OTHER (BCL)
| <span style="color: #868686"> <small>''22-Various correspondence (OTH=> BCL)''</small/> </span>
|-
| reportingSGO.state=up
| ReportingDiffusion/SGO
| <small>CSSF - Management company reporting (SGOREP)</small/>
| Rapport Société de Gestion
| <span style="color: #868686"> <small>''26-Management company''</small/> </span>
|-
| reportingDOCBNK.state=up
| ReportingDiffusion/DOC_BNK
| <small> AR: Annual Report <br />
AS: Annual report consolidated <br />
CO: Compliance Report <br />
GR: Governance Report <br />
IA: Internal Audit Report <br />
IC: ICAAP <br />
ID: ICAAP Consolidated <br />
LF: Long Form Report <br />
LC: Long Form consolidated <br />
LD: Long form branch or specific participation <br />
ML: ManagementLetter <br />
MC: Management letter consolidated <br />
RC: Risk Control Report <br />
RP: Recovery Plan <br />
SC: Single Customer View <br />
LG: Reconciliation LuxGAAP FINREP <br />
RR: Results distribution <br />
BD: AC member list <br /> IL: ILAAP <br /> IM: ILAAP consolidated
<br />
AC: Audit report on AML/CTF <br />
MF: Audit report on rules of conduct <br />
MM: Head quarter annual report <br />
RE: Report on out-of-court complaint resolution <br />
TR: Table on out-of-court complaint resolution <br />
AD: Circ. 18/697 annexe1 <br />

| Reporting des établissements de crédit
| <span style="color: #868686"> <small>''27-Reporting of credit institutions''</small/> </span>
|-
| reportingEDP.state=up
| ReportingDiffusion/EDP
| <small>CSSF - Payment instituions (EDPREP): Z1.1; Z1.2; Z1.4; Z2.1 </small/>
| Reporting EDP
| <span style="color: #868686"> <small>''29-Periodic reporting scheme for payment instituions (EDP)''</small/> </span>
|-
| reportingEME.state=up
| ReportingDiffusion/EME
| <small>CSSF - Electronic money instituions (EMEREP): W1.1; W1.2; W1.3; W1.4; W2.1 </small/>
| Reporting EDP
| <span style="color: #868686"> <small>''34-Electronic money reporting (EME)''</small/> </span>
|-
| reportingPubDiffu.state=up
| ReportingDiffusion/DOC_FIS_OPC/PUB_FINESTI<br>ReportingDiffusion/DOC_OPC_NOT_LU/PUB_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''32-Envoi pour publication/diffusion''<br>''33-Envoi pour publication/diffusion OPC non LU'' </small/> </span>
|-
| reportingOPCNONLU.state=up
| ReportingDiffusion/DOC_OPC_NOT_LU/LOCAL_REGISTRATION<br>ReportingDiffusion/DOC_OPC_NOT_LU/LOCAL_NOTIFICATION
| <small>HOST_UPDATE: [[Sending Service#Automating process for KID packages|Automated process for KID packages]]</small/>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''30-Enregistrement pour OPC non LU''<br>''31-Notification pour OPC non LU'' </small/> </span>
|-
| reportingMAJDOCLU.state=up
| ReportingDiffusion/DOC_FIS_OPC/HOST_UPDATE
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''37-Enregistrement/Mise à jour de documents Fond LU vers pays HOST''</small/> </span>
|-
| reportingSE.state=up
| ReportingDiffusion/SE
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingSEExportXLS.state=up
| ReportingDiffusion/SE/ExportXLS
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingSETransfoXLS.state=up
| ReportingDiffusion/SE
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingASS.state=up
| ReportingDiffusion/ASS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-Reporting BCL pour les assurances''</small/> </span>
|-
| reportingASSExportXLS.state=up
| ReportingDiffusion/ASS/ExportXLS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-BCL report for insurances''</small/> </span>
|-
| reportingASSTransfoXLS.state=up
| ReportingDiffusion/ASS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-BCL report for insurances''</small/> </span>
|-
| reportingDP.state=up
| ReportingDiffusion/CDP
| <small> BCL - Data on payment operation: V 1.1 - V 1.14 </small/>
| Collecte des données de paiement (CDP)
| <span style="color: #868686"> <small>''36-Data on payment instruments and operations''</small/> </span>
|-
| reportingNotifUcitsIV.state=up
| ReportingDiffusion/DOC_FIS_OPC/NOTIFICATIONS_UCITSIV
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''28-UCITS IV notification''</small/> </span>
|-
| reportingFINESTI.state=up<br>reportingLIBFINLU.state=up
| ReportingDiffusion/DOC_FIS_OPC/LIBRARY_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingLIBFINNOTLU.state=up
| ReportingDiffusion/DOC_OPC_NOT_LU/LIBRARY_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| <span style="color: #868686"> <small>''OBSOLETE : reportingCRF.state=up''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
|-
| <span style="color: #868686"> <small>''OBSOLETE : reportingCRFEncrypted.state=up''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
|-
| reportingAIF.state=up
| ReportingDiffusion/AIF
| <small> CSSF - Alternative Investment Fund managers: AIF / AIFM </small/>
| (-) AIF <br /> (-) AMfine
| <span style="color: #868686"> <small>''54-AIFMD reporting''</small/> </span>
|-
| reportingFATCA.state=up
| ReportingDiffusion/FATCA
| <small> ACD - Financial Institutions - Foreign Account Tax Compliance Act (FATCA) </small/>
| Rapport FATCA
| <span style="color: #868686"> <small>''60-FATCA reporting''</small/> </span>
|-
| reportingCAA.state=up
| ReportingDiffusion/CAA
| <small> (-) CAA - Rapports narratifs (N01-N10 <br /> (-) CAA - XBRL reports Solvency II (S01-S23) </small/>
| Reporting CAA|
| <span style="color: #868686"> <small>''63-BCL report for insurances|''</small/> </span>
|-
| reportingCRS.state=up
| ReportingDiffusion/CRS
| <small> ACD - Financial Institutions - Common Reporting Standard (CRS) </small/>
| Reporting CRS
| <span style="color: #868686"> <small>''68-CRS reporting''</small/> </span>
|-
| reportingGRP_BNK.state=up
| ReportingDiffusion/GRP_BNK
| <small>«SHS-Group» report </small/>
| BCL SHS report
| <span style="color: #868686"> <small>''75-SHS Reporting''</small/> </span>
|-
| reportingUCIAR.state=up
| ReportingDiffusion/UCIAR
| <small>CSSF UCIAR </small/>
| UCIAR Reporting
| <span style="color: #868686"> <small>''86-UCIAR Reporting''</small/> </span>
|
|-
| reportingESP.state=up
| ReportingDiffusion/ESP
| <small>ICS reporting </small/>
| Rapport Enquête
| <span style="color: #868686"> <small>''15-CSSF polls''</small/> </span>
|
|-
| reportingCAADoraROI=up
| ReportingDiffusion/CAA
| <small>DORA Register of Information</small/>
| CAA reporting
| <span style="color: #868686"> <small>''62-CAA reporting''</small/> </span>
|
|-
| reportingCAADoraDIN.state=up
| ReportingDiffusion/CAA
| <small>DORA Incident Reporting</small/>
| CAA reporting
| <span style="color: #868686"> <small>''62-CAA reporting''</small/> </span>
|
|-
| reportingPDAOFI.state=up
| ReportingDiffusion/PDAOFI
| <small>PDAOFI Reporting</small/>
| self-assessment questionnaire PDAOFI
| <span style="color: #868686"> <small>''88-PDAOFI reporting''</small/> </span>
|}

= Installation as a Windows Service =

Once the installation the Sending Service is completed, the <span style="color: #C00000">'''InstallServiceNT.bat'''</span> file is available and you can complete your Sending Service installation by creating the Windows Service <span style="color: #C00000">'''ServiceDeposant'''</span>.

Execution frequency of Window Service ServiceDeposant to process files from this folder is 30mn by default [[Sending_Service#Configuration of the properties file | => Configuration of the properties file]].

Double click the <span style="color: #C00000">'''InstallServiceNT.bat'''</span> file.

[[File:InstallServiceNT.png|600 px]]

A Command Prompt window opens up and closes as quickly as it popped up. The new Windows Service <span style="color: #C00000">'''ServiceDeposant'''</span> is now available.

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

[[File:WindowsService.png]]

<u>IMPORTANT</u>: Please ensure the '''Sending Service user''' that is linked to this Windows Service has <span style="color: #C00000">'''Internet rights'''</span> (=> Right click on ''Service deposant'' > select ''Properties'' > select ''Log On'' tab).

If you want to uninstall the Windows Service, please double click the <span style="color: #C00000">'''UninstallServiceNT.bat'''</span> file.

= Installation on Unix/Linux =

*Move to the ServiceDeposant directory
<u> Example </u>: /opt/ServiceDeposant/

*Check that you have execution rights (x) on the Install.sh file
<u> Example </u>: ls -l

*If not, just add this right using the chmod command
<u> Example </u>: chmod 755 install.sh

*Launch Install.sh with the configuration file as parameter
<u> Example </u>: install.sh config.properties

*Press the Enter key and enter the Java path when requested

*Press the Enter key again and wait for the ‘BUILD SUCCESSFUL’ message.

* Once installed, launch the run.sh to run the sending service

= How to start the Sending Service =

* Double click the <span style="color: #C00000">'''run.bat'''</span> command available at the root folder of your Sending Service

In the case you created a '''Windows Service'''

* Double click the <span style="color: #C00000">'''StartService NT.bat'''</span> command available at the root folder of your Sending Service

or

* Browse to the <span style="color: #C00000">'''Windows Services'''</span> console (''Start > Control Panel > Administrative Tools > Services'') and right click the '''ServiceDeposant''' service and start the service.

[[File:WindowsService.png]]

The message *Fin Ok* means that the installation was successful.

= How to stop the Sending Service =

* If you launched the Sending Service using the <span style="color: #C00000">'''run.bat'''</span> command, you can stop it pressing the keys Ctrl+C+Y.

In the case you created a '''Windows Service'''

* Double click the <span style="color: #C00000">'''StopService NT.bat'''</span> command available at the root folder of your Sending Service

or

* Browse to the <span style="color: #C00000">'''Windows Services'''</span> console (''Start > Control Panel > Administrative Tools > Services'') and right click the '''ServiceDeposant''' service and stop the service.

[[File:WindowsService.png]]

= Automatic and semi-automatic sending of O4.1 and O4.2 reports =

<span style="color: red;>'''Changed on July 2023'''</span>

For [http://www.cssf.lu/en/supervision/ivm/ucits/legal-reporting/ '''O4.1 and O4.2 reports'''] the [http://www.cssf.lu/en/supervision/'''CSSF'''] is expecting '''EDIFACT''' file format (ISO 9735).

Please note that you have to generate yourself a '''flat text file''' for these reports, which, once dropped into the dedicated directory of the Sending Service, will be transformed into the expected EDIFACT format.

'''The structure of the flat file is detailed in the document [[Media:StructMess_EN.pdf|Structure of messages for interface files from fund manager host system]], pages 8 to 14.'''

The Sending Service provides two sending ways :

<u>Automatic sending</u>

In this case, the flat files must be dropped into the '''OPC\envoi_Automatique\fichiersCCLUX''' folder of your Sending Service.

If the flat file is well formed, the reports are '''changed to ''.T62'' for O4.1, respectively ''.T63'' for O4.2''' into the subfolder '''Edifact''' by default ([[#IdBothCasesEdifact |see how to change it]]).

On sending, the ''.T6x'' is transformed into ''.trt''.
If the sending is OK, a ''.acq'' is generated otherwise a ''.err''. All this in the Edifact subdirectory.<br/>
If nothing appears in the Edifact subdirectory, it means that things are not going well.<br/>
<blockquote>You must check the Edifact subfolder for .acq or .err</blockquote>

Note : The .err that may be temporary generated within the PDF file for O4.2 reports must be ignored.

<u>Semi-automatic sending</u>

If you want to use this kind of sending, you have to drop your flat file into the '''OPC\envoi_SemiAutomatique\fichiersCCLUX_aTraiter''' folder of your Sending Service, where it will be converted to a PDF file and stored in the '''OPC\envoi_SemiAutomatique\fichiersPDF_aValider''' folder.

The PDF file allows you to check the data of your flat file in a more user friendly way before you transmit it to the supervisory authority.

Once checked/validated, the PDF file must be dragged into '''OPC\envoi_SemiAutomatique\fichiersPDF_aEnvoyer''' folder.

After being checked for errors, the reports are '''changed to ''.T62'' for O4.1, respectively ''.T63'' for O4.2''' into the subfolder '''Edifact''', <span style="color: red;>BE CAREFUL : this folder is in OPC\envoi_Automatique\fichiersCCLUX\'''Edifact''' by default.</span>([[#IdBothCasesEdifact |see how to change it]])

On sending, the ''.T6x'' is transformed into ''.trt''.
If the sending is OK, a ''.acq'' is generated otherwise a ''.err''. All this in the Edifact subdirectory.<br/>
If nothing appears in the Edifact subdirectory, it means that things are not going well.<br/>
<blockquote>You must check the Edifact folder for .acq or .err</blockquote>

<div id="IdBothCasesEdifact"></div>
<u>In both cases</u>

* The reports sent are .T62, resp. .T63, you will find them into the transmission follow-up with such names. The CSSF answsers with EDOFBR....xml files as feedbacks.<br/>

* The .ack files are not sent anymore, even for the O4.1 Fundsquare file.

* The '''Edifact results subfolder''' is the same for the two ways of sending : automatic and semi-automatic. You can choose the one you want by changing the property '''''reportingOPC.automatique.edifact.remoteDir''''' into the .properties file. In the installation assistant (assistantSD), this property is under reportingOPC.automatic.state's button 'More'. <br>Then install again to enable it.

= Automating process for KID packages =

In the context of KID updates to be filed to the CSSF, it is possible to set up the automatic sending of KIDs packages (.zip files) from our server to your Sending Service. Once the Sending Service has received the KIDs, they are copied in one of the following directory:

'''Luxembourgish fund'''
\ReportingDiffusion\DOC_FIS_OPC\KID_OPC

'''Foreign fund'''
\ReportingDiffusion\DOC_OPC_NOT_LU\HOST_UPDATE

Then the files are sent to the CSSF in the usual way.

If you want to use this feature, please
* Install the Sending Service [[Sending Service#Installation with Sending Service Installer|'''=> Installation with Sending Service Installer''']] or [[Sending Service#Manual installation with Command Prompt|'''=> Manual installation with Command Prompt''']]
* Ensure that the listeners <span style="color: #C00000">'''reportingOPCNONLU.state'''</span> and <span style="color: #C00000">'''reportingKID.state''' </span> in your properties file are <span style="color: #C00000">'''=up'''</span>
* Contact our Regulatory Service department and request the installation of this specific feature.
* Generate the KID package (.zip file) in the UCITS IV Document Management application (https://www.e-file.lu). Please note that in some cases an automated process on our servers can be installed.

Do not hesitate to contact our [[How to contact us|'''Client Support & Operations Desk''']] if you need further assistance.

= Sending progress and follow up =

== Transmission following ==

Here are the default transmission followup files that are created depending on the state in the transmission workflow.

<div style="text-align: left;">
{| border="1" cellspacing="2" cellpadding="10"
|-
! scope="col" | '''File extension'''
! scope="col" | '''Description'''
|-
||<span style="color: #C00000">''' .trt'''</SPAN>
|| <u> Example </u>: file processing of '''FileName.ext'''
Once the file has been dropped into the appropriate folder, the Sending Service will start processing it and rename it as follows:

'''FileName.ext_YYYYMMDDhhmmssmmm.'''<span style="color:#C00000">'''trt'''</SPAN>
|-
|| <span style="color: #C00000">'''.acq'''</SPAN>
|| Once the processing finished an <span style="color:#C00000">'''.acq'''</SPAN> file will be generated in the same folder by the Sending Service in order to confirm the transmission:

'''FileName.ext_YYYYMMDDhhmmssmmm.'''<span style="color:#C00000">'''acq'''</SPAN>

|-
||<span style="color: #C00000">'''.err'''</SPAN>
||An <span style="color: #C00000">'''.err</SPAN> file is created in case or an error:

'''FileName.ext_YYYYMMDDhhmmssmmm'''<span style="color:#C00000">'''.err'''</SPAN>

Please open this file and analyse the error message.

|-

|}

</div>
<br/>

== Feedback files (Replies folder) ==

For some reporting, the administration will give you more detailed feedback. In this case, those feedback will replace the corresponding ones in the previous section.

By default, <u> feedback files</u> are dropped into <span style="color:#C00000">'''Replies'''</span> sub-folders. <span style="color:#C00000">'''Replies'''</SPAN> folders are created dynamically in the initial transmission folder of the files. They only appear when feedback files, sent by the supervisory authorities, have to be stored. If the folder is deleted, it will be automatically recreated upon receipt of new feedback files.

The name and location of the <span style="color:#C00000">'''Replies'''</SPAN> folder may be configured differently from the implementation of the solution with your company’s project coordinator [[Sending_Service#Configuration|=> Configuration .properties file.]]

<div style="text-align: left;">
{| border="1" cellspacing="2" cellpadding="10"
|-
! scope="col" | '''Autority'''
! scope="col" | '''Description'''

|-
||<span style="color: #C00000">'''CSSF'''</SPAN>
||Feedback files generated and sent by the CSSF.

Please click the picture below to access the '''Naming convention for CSSF reportings''' document:

[[File:FBR CSSF.png|500 px|link=http://www.cssf.lu/fileadmin/files/Reporting_legal/transport_securisation_reporting/Convention_de_nom.pdf]]

|-
||<span style="color: #C00000">'''BCL'''</SPAN>
||Feedback files generated and sent by the BCL.

The BCL sends feedback with the following naming convention :

FDBTECH_[OK/KO]_[YYYYMMDD]_[SENT FILE NAME]_[RANDOM CARACTERS].xml

With
* [OK/KO] : replaced either by OK (if the files has been transmitted and processed successfully) or KO (if there has been an error)
* [YYYYMMDD] : replaced by the date of the feedback
* [SENT FILE NAME] : replaced by the complete name of the original file (including it's extension)
* [RANDOM CARACTERS] : replaced by a random and unique caracters.

|-
||<span style="color: #C00000">'''ACD'''</SPAN>
||Feedback files generated and sent by the ACD.

ACD's feedback files are available in the sub-folder "Replies". For example, /ServiceDeposant/ReportingDiffusion/FATCA/Replies/

Each feedback has a specific status which is available in the file name: ACK, NAK, VAL, WAR, ERR (Cf. Status feedback ACD).

Example feedback from ACD :

FATCA_20150520080022_F0_2016_B_1970010112345_006M8M.00000.LE.442_P_ack.xml

FATCA_20150520080023_F1_2016_B_19700202123_ZZLRV4.99999.SL.442_T_ack.xml

The "Replies" folder is created upon feedback receipt. Please check the Sending Service's configuration if the "Replies" folder is not available. In the configuration file (properties file), the variable corresponding to "Configuration of connection for feedback" and the one corresponding to "Configuration of connection for authority acknowledgement" should be set to "up".
|}

* '''For other reporting''' (08/371 / VNI...), '''there is no additionnal acknowledgment'''. <br>
This means that only <span style="color: #C00000">'''acq'''</span> will be created. <br><br>

<u>'''Conclusion'''</u> : <span style="color: #C00000">'''Checking that both trt and acq files were generated is a good way to ensure the good working of the Sending Service'''</span>. Doing this way, you can be sure that your data was correctly sent and '''e-file will be in charge of forwarding them to authoritites'''.

= Sending Service versions and updates =

Please be informed that our system is able to check the version of the program you are running. This information is sent to our database when the service is launched.

Please note that the <b>''RELEASE_README.txt''</b> file, located at the root folder provides you information on the different Sending Service versions.
The example below indicates that the Sending Service version 4.5.6 is being used:
[[File:SD evol.png| 800 px]]

In case of major Sending Service changes, our [[How to contact us|'''Client Support & Operations Desk''']] will notify you by sending an INFO-email to your local e-file administrator.

= Functional testing and test environment =

In fact, it is not necessary to test the working of the Sending Service by performing a test sending.

Indeed, all '''technical checks''' are performed during the startup process.

In other words, if the startup process does not generate any error message, then the Sending Service is running properly.

* Launch the Sending Service through the dos <b>''run.bat''</b> file or through the Windows Service.
* '''Check the log files''' generated in the <b>''log''</b> folder of Service Deposant.
* The Sending Service is running properly if the '''error.log file''' is empty or if it does not contain any line in relation to the starting process.

<u>'''Remark'''</u> : If a problem occurs after this check, it would certainly be a functional problem or could also be linked to the e-file configuration.

In this case, we recommand to '''check the ''.err'' file''' automatically generated during the sending process.

If you want to install a '''test environment''' in order to validate the your source files or to anticipate a migration procedure, please follow the steps below:

* '''Duplicate the production Sending Service''' by copying the whole ''Service Deposant'' folder to another location.
* '''Adjust the properties file''' to redirect the service to our test environment : Homologation. <b>''e-file.hostname''</b> = <span style="color: #C00000">'''homologation.e-file.lu'''</span>

Please note that, if the user login may remain the same, the password will be changed in our test environment.
Feel free to set a new password

Do not forget to '''modify the path''' to your test files if these ones are stored in a specific location.

Finally, to identify cleary both Windows services, you must adjust the parameters used to identify the Windows Service name : <b>''wrapper.app.long.name''</b> and <b>''wrapper.app.name''</b>

* <span style="color: #C00000">'''Relaunch the Sending Service installation'''</span>

= Common Problems =

== The service does not start ==

Please refer to following procedure if a Sending Service, launched through <u>the Windows Services</u> does not start in order to analyze the origin of the problem.

<br><br>
<u>'''Attempt to start it with the DOS command line'''</u><br>
<br>
* Open a '''DOS''' window and make sure to have '''administrator rights''' on the computer (''Start>run : cmd'')
* Move to the folder where the sending service is installed
* '''Run the command : <span style="color: #C00000">''run.bat''</span>'''
<br>

'''If the sending service runs properly''' through this DOS command, without generating error logs, we recommand to follow [[Sending Service#IdSolve|this solving method]]'''.<br>
<span style="color: #C00000">'''Otherwise, a log analysis is necessary'''</span><br><br>

=== Log Analysis===

The <b>''error.log''</b> file located in the <b>''log''</b> folder at the root of Sending Service, contains the error trace causing this dysfunction.<br>

'''You will find below the most common known problems.'''<br>
<br>
In all cases, we are at your disposal to assist you in this analysis. Feel free to contact our <span style="color: #C00000">'''[[How to contact us|'''Client Support & Operations Desk''']].'''</span><br>

==== Network Problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Error when webservice's call 'obtenirVersionsDocument'.Unrecognized SSL message, plaintext connection.</span><br><br>

<u>'''Solving Method'''</u><br>
* Check the proxy parameters of your properties file
* '''Relaunch the sending service installation process''' so that the changes are taken into account.

<u>'''Error 2'''</u> : <span style="color: blue">java.net.ConnectException: Connection timed out: connect.</span><br>
<u>'''Error 3'''</u> : <span style="color: blue">Connection timed out: connect [TIP: The machine can be unauthorized by the proxy]</span><br><br>

<u>'''Solving Method'''</u><br>
* Check the configuration of your proxy with your network team : It must be correctly configured to allow outbound connections to our server [http://www.e-file.lu www.e-file.lu] HTTP and HTTPS.

==== Other time out problem====

<u>'''Error'''</u> : <span style="color: blue">Startup failed: Timed out waiting for signal from JVM.</span><br>

<u>'''Solving Method'''</u><br>
* '''Increase''' the value of <b>''wrapper.startup.timeout''</b> parameter from your properties file. As an example, increase from 300 to 600.
* '''Relaunch the sending service installation''' to take the changes in account.

This parameters indicates the duration allocated to the service startup. Is some cases, 5 mn may not be enough, particularly with slow proxy connections to e-file.

==== Administrator rights issue with Windows service ====
[[File:SDadmin.jpg]]

By default, a windows service runs through a '''non administrator system user'''.<br>
Depending on your architecture, it is possible that this user account has not enough rights to ensure a proper start of the Sending Service. (proxy issue for example)<br>

Then simply change this setting this way: <br>

<div id="IdSolve"></div>
<u>'''Solving Method'''</u><br>
* Open the '''Windows services''' window. (Start > Control Panel > Administrative tools > Services)
* Right click on the service named <b>''ServiceDéposant''</b>
* Select the <b>''Properties''</b> item
* Indicate an administrator user account and password in <b>''LogOn''</b> tag.
* Relaunch the service

== Errors are raised during sending ==

The generation of an <b>''.err''</b> file during the processing of your report indicates an issue during the sending.<br>

In this case,''' it is necessary to analyze the problem because the data could not be transmitted to the authorities.'''<br><br>

The <b>''.err''</b> file contains the explanation of the error that generates this dysfunction.<br><br>

'''You will find below the most common problems.'''<br>
In all cases, we are at your disposal to assist you in this analysis. Feel free to contact <span style="color: #C00000">'''[[How to contact us|'''Client Support & Operations Desk''']].'''</span><br>

==== Functional Problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Failed to validate XML</span><br>
<u>'''Error 2'''</u> : <span style="color: blue">All error indicating a data problem</span><br><br>

<u>'''Solving Method'''</u><br>
* '''Correct the source file''' according to the error messages indicated in the <b>''.err''</b> file.
* '''Resend the file'''.

==== User account problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Getting addressees information Une erreur est survenue lors de l'execution du Workflow</span><br>

<u>'''Solving Method'''</u><br>
* '''Link''' the sending service user account to the right '''User Group''' according to the kind of reporting your are trying to send. His profils should be <b>''SD with response''</b>

= Certificate Update =

Once your Luxtrust certificate is activate in E-file, you need to replace the new keystore in the sending service.

If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
In this case you can use a simplified process by '''<u>simply replacing the keystore:</u>'''
(-) Stop the Sending Service
(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
(-) Copy the newkeystore (to the sending service keystores folder.
(-) Rename this copy as the previous one.
(-) Restart the Sending Service

In case of a '''different kesytore password''', you '''<u>will have to reinstall the Sending Service</u>'''.<br>
Please find below what you need to do:
* Stop your sending service
* Copy your new keystore in the keystores folder of the Sending Service.
* Update the configuration: It is possible that your new Keystore has a different name than the previous Keystore therefore it is necessary to update the configuration.
'''E-file configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''keystore.path=@PROJECT_ROOT_PATH@/keystores/????.ks'''''
|style="width:20em"| path of the keystore (xxxx.ks)
|-
|}

* Install the sending service: To install the Sending Service, you have to click on the '''Install''' button. A pop-up window opens where you have to enter your passwords.

''Note : If you do not use a proxy, you can leave a blank for the proxy password''

[[File:Doc_SDInstaller_12.png|border|500 px]]

Once finished a pop-up windows opens stating that the installation has been successful:

[[File:Doc_SDInstaller_13.png|border|500 px]]

To start your Sending Service open the folder where you installed it and run the file '''run.bat''' or '''InstallServiceNT.bat''' if you want to install the Service as a '''Windows Service'''.

[[Sending Service#Installation as a Windows Service|=> Installation as a Windows Service]]

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

Sending Service java-less version

2026-05-04T08:43:42Z

Cso: /* Solving known problems */

''<small>Page's last update : 30 May 2024</small>''
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

''You can click on the picture.''
<imagemap>
File:SDjl_general.png|center|900px|alt=clickable image : form description| titre
rect 23 39 332 149 [[Sending_Service_java-less_version#Prerequisites | Prerequisites ]]
rect 425 91 678 182 [[Sending_Service_java-less_version#Purpose |Purpose]]
rect 703 3 911 96 [[Sending_Service_java-less_version#Manual_installation_using_command_prompt | Installation ]]
rect 782 110 1057 208 [[Sending_Service_java-less_version#Update_the_sending_service | Upgrade or change the configuration ]]
rect 47 264 413 350 [[Sending_Service_java-less_version#Administration_Interface | Using the administration interface ]]
rect 491 266 694 357 [[Sending_Service_java-less_version#Process_overview | Process ]]
rect 767 266 1056 349 [[Sending_Service_java-less_version#Sending_Folders | Folders ]]
rect 46 459 212 582 [[Sending_Service_java-less_version#Administration_Interface | through the administration interface]]
rect 246 566 470 669 [[Sending_Service_java-less_version#Logs| Is my sending service running ?]]
rect 387 457 514 531 [[Sending_Service_java-less_version#Stop_the_application | Stop ]]
rect 534 496 722 592 [[Sending_Service_java-less_version#Start_the_application | Start ]]
rect 803 455 969 546 [[Sending_Service_java-less_version#Submit_a_report | How can I submit a report ?]]
rect 987 508 1181 590 [[Sending_Service_java-less_version#Check_for_acknowledgment_and_feedbacks | Check my sends ]]
rect 730 600 950 700 [[Sending_Service_java-less_version#Solving known problems | Solutions ]]
desc none
</imagemap>

= Purpose =

The '''Sending Service''' is our solution for the '''automatic transmission''' of reports and documents to authorities.

It is an application consisting of a set of '''processes''' (called listeners) that periodically exchange files with authorities through a set of designated '''folders'''. Everything is configured via an '''administration interface'''.

This solution is useful if you have a '''large number of reports''' to submit or if the manual sending does not suit your needs.

Please be aware that, in this case you will have to provide the files yourself according to the authorities' file specifications.

This tool is usually <span style="color: #C00000">'''installed on a server'''</span> on your side.

With a suitable '''network mapping''', users can simply '''drop the file to be sent into the appropriate directory'''. It is then automatically '''encrypted and sent'''.

= Prerequisites =

*Internet access
*If you use a proxy, authorise outgoing calls to [https://www.e-file.lu www.e-file.lu]. Port 443 (HTTPS) must be open.
*<span style="color: #C00000">'''Windows Administrator rights''' </span> to install the Sending Service <span style="color: #C00000">on the computer</span> ''(Windows Start button > Control Panel > User Accounts > Manage User Accounts)''.
*'''OS''': Windows - ''Linux will be developed''
*Processor: Pentium 2 GHz or equivalent
*8 GB of RAM
*300 MB of free space on hard disk drive. Think of providing regular purges.
*500 MB of free space on hard disk drive for logs. Regular purges are necessary as well.
*A <span style="color: #C00000">'''Sending Service user''' </span>, ''for example: aacSD'', and its password, ''for example: formation'', have to be available [[E-file_Administration#e-file_administrator_functions_.28e-file_v1.29|'''=> e-file administration''']].
*The e-file account of the Sending Service user has to be linked to groups/modules, ''for example FATCA reporting + profile "Sending Service".''
*A valid <span style="color: #C00000">'''keystore''' </span>(keystore.ks) and its <span style="color: #C00000">'''password''' </span>must be available as soon your file must be encrypted. (You do not need a keystore anymore if all your reports are going through S3 API).
*The Sending Service user has to be properly configured in the e-file user administration tool in order to be able to receive <span style="color: #C00000">'''alerts''' </span> (receipt of acknowledgement and feedback files).

Note that you can find the prerequisites for the manual transmission there : [[Transmission_Module#System_requirements]]

= Sending service version 1 vs version 2 =
{| class="wikitable"
|+Differences between v1 and v2
!
!<span style="color: #21C8DB">v1</span>
!<span style="color: #21C8DB">v2</span>
|-
|needs Java
|x
|
|-
|support S3 protocol
|x
|x
|-
|allow pre-encrypted files send
|x
|
|-
|U11 enrichment
|x
|
|-
|export to XLS
|x
|
|-
|XLS to XML (TPTIBS)
|x
|
|-
|O4.x semi-automatic (txt to PDF)
|x
|not yet
|-
|allow O4.x PDF direct send
|x
|x
|-
|user interface for configuration
|
|x
|-
|deep level (deposit in sub-directories)
|x
|x
|-
|automatic upgrade
|
|x
|-
|self-managable heartbeat monitoring
|
|x
|-
|Linux-compatible
|x
|not yet
|-
|unit of time used in set up
|milliseconds
|minutes
|}

= Process overview =
The sending service can be run in the <u>console mode</u> through '''launcher.exe'''. It then runs in a line-command window which must stay open.

On the first launch see [[#Manual_installation_using_command_prompt|installation]] paragraph to locate it, otherwise [[#Start_the_application|start]].

The sending service can also be installed as a <u>Windows' service</u> through '''''run-as-service.bat'''''. Once done, it is visible into the Windows' services list. Then it is launched on the workstation boot.

See chapter [[#Start_the_application|Start the application]].

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">''<small>Click to see more technical details</small>''</div>
<div class="mw-collapsible-content">
</br></br>
''launcher.exe'' is the launcher application. It launches and updates the main application described below. It contains proxy and environment configuration files.

''<nowiki>get</nowiki>-service-status.bat'' displays the status of the sending service when it is installed as a Windows service

''remove-service.bat'' uninstalls the Windows service

''run-as-service.bat'' installs then runs the sending service as a Windows service

''sending-service.exe'' is located in the .\system\bin folder. This is the main application, used to send documents and containing all the business rules and configuration files linked to the operation of the application, such as dictionary-xsd and dictionary-workflow.

<span id="folder-hierarchy"></span>
== Folder hierarchy ==

Once installation is complete, three sub-folders will be present:

'''system''': this is the folder containing the technical elements of the application, and contains also three sub-folders:

::'''bin''': contains the main application executable

::'''config''': contains all client configuration files

::'''log''': contains all logs generated during application execution

'''sendingservice''': this is the folder containing all the sub-folders in which we will place our files for sending.<br />
For example, in the default configuration, if you want to send a KID file, you'll need to save the file in the following folder: ''sendingservice\fundregistration\luxembourg\opc''

'''tmp''': This is the folder containing all temporary files related to the application's operation.

</div>
</div>

<span id="logsy"></span>
== Logs ==
Each process creates its own log.</br>
sending-service.exe creates '''service-deposant-''timestamp''.log''' into .\system\log : it mainly contains information on the processing of your reports </br>
launcher.exe creates '''launcher-''timestamp''.log into .\log''' : it contains in particular information about the installation process</br>

[[File:SDjl_logs.png|400px|where are the log files ?]]

In case you think something goes wrong, you can open these files into a text editor and check if you see error messages. Also send them to us if you need us to check for you.

For a continuous monitoring, see also [[#Details_on_heartbeat_system]]

Running as a Windows' service, you can check the sending service's status launching '''''<nowiki>get</nowiki>-service-status.bat'''''

<span id="start-the-application"></span>

== Start the application ==

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the console mode... click</div>
<div class="mw-collapsible-content">
</br></br>
Once the application is installed:

Double-click [[File:SDjl_2.png|169x25px]] (''if you get this message:[[File:SDjl_3.png|264x89px|A windows's error message]], [[#protect_error|solve it]]'')

</div>
</div>

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the windows service mode... click</div>
<div class="mw-collapsible-content">
</br></br>
Once the sending service is installed as a Windows' service, use the windows' services app to start it :

[[File:SDjl_StartStopService.png|StartStopService|800px]]

</div>
</div>

<span id="stop-the-process"></span>

== Stop the application ==
<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the console mode... click</div>
<div class="mw-collapsible-content">
</br></br>

hit the keys '''Ctrl+C'''

</div>
</div>

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the windows service mode... click</div>
<div class="mw-collapsible-content">
</br></br>

If the sending service is running as a Windows' service, use the windows' services app to stop it :

[[File:SDjl_StartStopService.png|StartStopService|800px]]

</div>
</div>

<span id="administration-interface"></span>

= Administration Interface =

''New : The former .properties file is no longer a file onto your disk but the data are stored in our database and you can access them through the administration interface.''

In the administration interface, you can retrieve all the parameters you can set up. Note that some of them have default values and some are set up when the installation is done. You can make all the changes needed.

Sign in with the sending service account (or as an administrator) and click [[File:SDjl_8.png|194x55px|the administration module access button]]

then [[File:SDjl_9.png|158x37px]], you get :

[[File:SDjl_10.png|800px|the sending services control panel]]

Click the name of the sending service to change, click [[File:SDjl_11.png|47x39px]] to go back to the list.

[[File:SDjl_12.png|800px|the details' control panel]]

To change a value, click [[File:SDjl_13.png|60x39px|the edit button]], make your changes then save or discard.

[[File:SDjl_14.png|349x46px|group of three buttons]]

The ‘edit all workflows’ button, allow you to make massive changes in one shot.

Once the changes saves, you will get: [[File:SDjl_15.png|309x59px|a positive answer]]

The buttons [[File:SDjl_16.png|193x39px]], respectively exporting/importing the properties to/from .json format : to backup, to move from UAT to production or to import manual changes onto properties.

Note

* the automatic update set up:<br />
[[File:SDjl_17.png|246x46px]]<br />
This is related to the sending service’s version delivered by our IT team. Click the icon to change the automatic update’s status.
* the categories of parameters: [[File:SDjl_18.png|377x84px|the parameters categories menu]]
* the [[File:SDjl_19.png|137x50px|the expand button]] button

<span id="details-on-workflows-part"></span>
== Details on workflows part ==

Regarding the workflows, each one takes care of specific reports. You must enable those you want the sending service to send.

''For example, to send'' U11 reports'', you must enable the'' reporting_u ''workflow, the active box must be ticked, and a folder must be entered, you can keep the default one or change it. The'' intervalTimeInMinute ''is the frequency with which the directory will be scanned.''

[[File:SDjl_21.png|601x203px|example reporting U details]]

You can find the reports and their matching sending service workflow in our [[ProductCoverage|product coverage page]].

<span id="details-on-heartbeat-system"></span>

== Details on heartbeat system ==

The heartbeat is a monitoring system to check whether the sending service is still up or not. It pings the sending service at the chosen frequency and send an alert e-mail if the sending service doesn’t answer.

In the ‘properties’ category, you can set it up or down by ticking the box or not, and choose the frequency or the monitoring.

[[File:SDjl_22.png|601x338px|Heartbeat activation]]

In the ‘Heartbeat’ section, you can find statistics on heartbeat running and you can choose who will receive an alert e-mail when needed.

[[File:SDjl_23.png|800px|Heartbeat monitoring]]

<span id="section"></span>

= Manual installation using command prompt =
<span id="step-1-Stop_former"></span>
== <u>Step 1</u>: Stop the former instance ==

Be sure that no former instance of the sending service is running on the same environment. If so, [[Sending_Service_java-less_version#Stop_the_application | stop ]] it.

''If you install to replace the version with java, plan to use a new directory.''

<span id="step-2-download-the-launcher."></span>

== <u>Step 2</u>: Download the launcher. ==

The official version is always on the production site. You will be asked for homologation or production environment during the installation process. </br>To monitor and manage the properties, use the administration module on the relative website.

Connect to www.e-file.lu as the sending service (or as an administrator).

In the administration module, Sending service management:

[[File:V2_access.png|332x231px]]

Click:

[[File:SDjl_25.png|604x172px]]

The launcher will be downloaded into your default folder:

[[File:SDjl_26.png|262x101px]]

<blockquote>An alternative is to use this direct link, after logging into e-file :https://www.e-file.lu/fsq-graph/file/download/launcher-version/download?distribution=WINDOWS</blockquote><span id="step-3-install-the-new-sending-service-with-the-launcher"></span>

== <u>Step 3</u>: Install the new Sending Service with the launcher ==

<span id="copy-launcher.exe"></span>
=== copy ''launcher.exe'' ===
into the folder where you want to install the sending service

<span id="open-launcher.exe"></span>
=== Open launcher.exe ===
Double-click it [[File:SDjl_2.png|169x25px]] (''if you get this message:[[File:SDjl_3.png|264x89px|A windows's error message]], [[#protect_error|solve it]]'')

You will be asked:

<span id="enter-y-yes-or-n-no-for-the-question-are-you-using-a-proxy"></span>

=== Enter Y (yes) or N (no) for the question: Are you using a proxy? ===
[[File:SDjl_27.png|222x29px|question about the proxy]]

<span id="enter-the-environment-production-or-homologation"></span>
=== Enter the environment: PRODUCTION or HOMOLOGATION ===
The name must be entirely typed</br>
[[File:SDjl_28.png|604x22px]]

The sending service will be downloaded, wait a little.

[[File:SDjl_29.png|604x147px|See the progression bars]]

<span id="enter-username"></span>
=== Enter username ===
Enter the sending service’s account user name (the one usually ended by ...SD)

<span id="enter-the-username-password"></span>

=== Enter the username password ===
<span id="either-if-a-properties-config-file-is-found-on-the-server-and-you-want-to-use-it"></span>

=== Either: it is not the first installation : a properties file is found on the server ===

When you have already done an installation in the past, even if you have deleted it on your workstation, your previous setup is saved on our servers. So you will be asked if you want to overwrite it :

Enter N (no) for the question: ''overwrite the existing properties config file'', if you want to keep the previous setup.

Enter the password of your keystore.

<span id="or-if-no-properties-config-file-is-found-on-the-server-or-you-want-to-overwrite-the-existing-one"></span>

=== Or: If no properties file is found on the server OR you want to overwrite the existing one ===

Enter Y (yes) for the question: ''overwrite the existing properties config file''.

[[File:SDjl_30.png|604x15px]]

Then you will be asked :

<span id="enter-the-root-folder"></span>
: <span style="color:#21b8b5">'''Enter the root folder '''</span>
::It is the folder where you want the sending service to be installed: it must already exist.
::Entering none will take the current one.
::It is in this folder that the tree structure of sending folders will be generated. After that, for each upload there will be a concatenation between the root folder and the subfolder for each workflow. For example Let's take the rootFolder: "C:\NewSendingService" and the folder for the Key Investor Document "sendingservice/fundregistration/luxembourg/opc". The service will then fetch the documents with the path "C:\NewSendingService\sendingservice\fundregistration\luxembourg\opc". Be careful not to put an \ at the end of the specified path

<span id="enter-the-configuration-name"></span>
: <span style="color:#21b8b5">'''Enter the configuration name '''</span>
::Choose a name for your setup.

<span id="enter-your-keystore-file-path-optional."></span>
: <span style="color:#21b8b5">'''Enter your keystore file path (optional).'''</span>
::Please note that you must enter your keystore to transmit to Luxembourg authorities.

<span id="enter-authentication-cssf-optional"></span>
: <span style="color:#21b8b5">'''Enter Authentication CSSF (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-authentication-bcl-optional"></span>
: <span style="color:#21b8b5">'''Enter Authentication BCL (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-the-password-optional"></span>
: <span style="color:#21b8b5">'''Enter the password (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-authentication-code-optional"></span>
: <span style="color:#21b8b5">'''Enter authentication code (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-y-yes-or-n-no-for-the-question-do-you-want-to-close-the-app-after-installation"></span>
: <span style="color:#21b8b5">'''Enter Y (yes) or N (no) for the question: Do you want to close the app after installation ?'''</span>
::Yes means that only the installation will be done.
::No means that the sending service itself will be run after the installation and starts to file reports.

The process will continue, installing all the xsd files …

You can close the window, click the right-corner red cross.

<span id="update-the-sending-service"></span>

= Update the sending service =

== Change your setup ==

To change the sending service's setup: '''workflows; heartbeat, ... and also groups and permissions'''
* use the administration interface
* then [[#Stop_the_application|stop the application]] and [[#Start_the_application|start]] it again.

To change only the '''proxy''' setup
* In the folder .\system\config, delete the ''proxy-conf.json''
* then [[#Stop_the_application|stop the application]]
* On the root folder, launch ''launcher'' again, keep the existing properties config file.
* If you want to use the Windows' service, exit launcher (Ctrl+C) and [[#Start_the_application|restart]].

To change only one or several '''passwords'''

Note that the passwords are encrypted and asked just one time at the first installation. If you have to change them, you must install the whole application again :
* In the folder .\system\config, delete all the .json files (you can keep the ''proxy-conf.json'' and the ''environment.json'' files if they won't change)
* then [[#Stop_the_application|stop the application]]
* On the root folder, launch ''launcher'' again, keep the existing properties config file.
* If you want to use the Windows' service, exit launcher (Ctrl+C) and [[#Start_the_application|restart]].

<span id="upgrade-the-application"></span>

== Upgrade the application ==
=== Automatic upgrade===

This feature concerns the application updates affecting the sending service (SD) itself and that are applicable to all clients / users.

''Short description:''

Whenever the sending service starts, restarts, and every 30 minutes when it is up and running, it will check for updates. If an update is detected, and automatic update is selected (you can modify the value in the admin module page), the SD will stop the current process, reinstall the new version and rerun the process automatically. After a successful (or unsuccessful) update a notification will be sent per email.

If the client did not subscribe for automatic application updates and a new version of SD is available, an email will be sent to the client requesting them to update the SD. The client will then have to rerun the application and install the new version.

If the client does not update its SD in a specific timeframe, the sending service will stop running until it has been updated.

===Manual upgrade===

When a new version is available from our IT team you <span style="color: #C00000"> '''simply need to'''</span>: [[#Stop_the_application|stop the application]] then [[#Start_the_application|start]] it again through the launcher.exe.</br>
A prompt will as you to download the update: ''A new version is available do you want to download it now (Y/n) ?''</br>
You need to press ''Y'' and hit the ''Enter'' key.</br>
Once completed, the Sending Service will be updated.</br>
If the tool is installed as a Service, we advise you: '''to close this windows and restart the Service'''.</br>

'''<u>Important note :</u> unless a request from the FEFI team, there is no need to (re)download the ''Launcher.exe'' '''

<span id="submit-a-report"></span>

=Submit a report=

To send a report just copy it in the relevant folder depending on its type.

See the default sending folders tree:

[[File:SDjl_32.png|195x333px]]

You can relocate this folders tree to adapt it to your needs, using the administration interface to change the setup.

Then either enter ''root folder + relative tree folder path'' or ''empty root folder'' and enter an ''absolute path'' for the listener :

[[File:SDjl_ExplicPathFolder.png]]

<span id="sending-folders"></span>
==Default Sending Folders==

Scroll this list to find the sending type you need and where you must copy your reports for them to be processed:

<div style="height:300px; width:auto; overflow-y:scroll">

{| class="wikitable table-filterable sortable"
|+<span style="white-space:nowrap"></span>
|- <div style="position:sticky;top:-1px;z-index:10">
! width="44%" style="background-color:#21b8b5" |Sending type / type d'envoi
! width="55%" style="background-color:#21b8b5" | To be copied into / à déposer dans

|-
|08/371 FIS Prospectus
|sendingservice/fundregistration/luxembourg/fis
|-
| 08/371 FIS Reports
|sendingservice/fundregistration/luxembourg/fis
|-
|Non-LU UCI Registration
|sendingservice/fundregistration/luxembourg/fundsnotlu
|-
|Other closing docs of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Management letters of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Fin rep of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Key Investor Document
|sendingservice/fundregistration/luxembourg/opc
|-
|Management letters for CSSF 09/423
|sendingservice/fundregistration/luxembourg/opc
|-
|CSSF Attestation
|sendingservice/fundregistration/luxembourg/opc
|-
|Management regulation status
|sendingservice/fundregistration/luxembourg/opc
|-
|Notification Full
|sendingservice/fundregistration/luxembourg/opc
|-
|Long forms for CSSF 09/423
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 UCI Prospectus
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 Report
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 report not in 08/371
|sendingservice/fundregistration/luxembourg/other
|-
|BCL report for insurances
|sendingservice/regulatoryreporting/luxembourg
|-
|BCL SHS
| sendingservice/regulatoryreporting/luxembourg
|-
|AIF Reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting_s112-l
|sendingservice/regulatoryreporting/luxembourg
|-
|MIFIR reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting U
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting EDIFACT
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting IORP
| sendingservice/regulatoryreporting/luxembourg
|-
|Reporting CSDR
|sendingservice/regulatoryreporting/luxembourg
|-
|FATCA Report
|sendingservice/regulatoryreporting/luxembourg
|-
|CRS Report
| sendingservice/regulatoryreporting/luxembourg
|-
|FINREP
|sendingservice/regulatoryreporting/luxembourg
|-
|SICAR Reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|PSF Report
|sendingservice/regulatoryreporting/luxembourg
|-
|COREP Report
|sendingservice/regulatoryreporting/luxembourg
|-
|EME Report
|sendingservice/regulatoryreporting/luxembourg
|-
|EDP Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Credit institution reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Management company report
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting Money Market Fund
|sendingservice/regulatoryreporting/luxembourg
|-
|CSSF enquiry
|sendingservice/regulatoryreporting/luxembourg
|-
| TAF MIFID Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport distinct solvabilité 2 du réviseur
| sendingservice/regulatoryreporting/luxembourg
|-
|Distinct solvency company Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport Narratif (Réviseur)
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport Narratif (compagnie)
|sendingservice/regulatoryreporting/luxembourg
|-
|Solvency II reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Titrisation Vehicles
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting TPT
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting securities by securities of issuing companies
|sendingservice/regulatoryreporting/luxembourg
|-
|Issuing companies reporting
|sendingservice/regulatoryreporting/luxembourg
|-
| Payment’s balance
|sendingservice/regulatoryreporting/luxembourg
|-
| AnaCredit
|sendingservice/regulatoryreporting/luxembourg
|-
|Security by Security banks
|sendingservice/regulatoryreporting/luxembourg
|-
|BCL statistics
|sendingservice/regulatoryreporting/luxembourg
|-
|Data payment collection
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting S
|sendingservice/regulatoryreporting/luxembourg
|-
|Various correspondence (OTH)
|sendingservice/regulatoryreporting/luxembourg/otherbcl
|-
|Other reporting for CSSF
|sendingservice/regulatoryreporting/luxembourg/othercssf
|-
|Reporting O
|sendingservice/regulatoryreporting/luxembourg/reporting_o
|-
|Reporting ICS
|sendingservice/regulatoryreporting/luxembourg/
|-
|DORA Incident Reporting
|sendingservice/regulatoryreporting/luxembourg/
|-
|DORA Register of Information
|sendingservice/regulatoryreporting/luxembourg/
|-
|Self-assessment questionnaire PDAOFI
|sendingservice/regulatoryreporting/luxembourg/
|}
</div>

<span id="check-for-acknowledgment-and-feedbacks"></span>

=Check for acknowledgment and feedbacks=

Once a report is sent, it is renamed as .trt and move into an auto-generated subfolder called ''reporttransmitted, ''
a file with extension .acq is also created as an acknowledgement.

[[File:SDjl_33.png|276x70px|the reporttransmitted folder]]

If an error occurs, you get a file with extension ''.err''. Open it and read the messages.

The feedbacks from the authority will come into ''feedbacks.'' Remember to read them.

<span id="transmission-following"></span>
==Transmission following==

Here are the default transmission follow up files that are created depending on the state in the transmission workflow.

{|
! width="13%" |'''File extension'''
! width="86%" | '''Description'''
|-
| '''.trt'''
|
<u>Example </u>: file processing of '''FileName.ext'''

Once the file has been dropped into the appropriate folder, the Sending Service will start processing it and rename it as follows:

'''FileName.ext_YYYYMMDDhhmmssmmm.trt'''
|-
|'''.acq'''
|
Once the processing finished an '''.acq''' file will be generated in the same folder by the Sending Service in order to confirm the transmission:

'''FileName.ext_YYYYMMDDhhmmssmmm.acq'''
|-
|'''.err'''
|
An '''.err file is created in case or an error:'''

'''FileName.ext_YYYYMMDDhhmmssmmm.err'''

Please open this file and analyse the error message.
|}

<span id="feedback-files-replies-folder"></span>
==Feedback files (Replies folder)==

For some reporting, the administration will give you a more detailed feedback. The feedbacks from the authority will come into ''feedbacks.''

<s>By default, <u>feedback files</u> are dropped into '''Replies''' sub-folders. '''Replies''' folders are created dynamically in the initial transmission folder of the files. They only appear when feedback files, sent by the supervisory authorities, have to be stored. If the folder is deleted, it will be automatically recreated upon receipt of new feedback files.

The name and location of the '''Replies''' folder may be configured differently from the implementation of the solution with your company’s project coordinator </s>

{|
! width="10%" |'''Autority'''
! width="89%" |'''Description'''
|-
|'''CSSF'''
|
Feedback files generated and sent by the CSSF.

Please click the picture below to access the '''Naming convention for CSSF reportings''' document:

[[File:SDjl_34.png|500x135px|A close-up of a screen Description automatically generated]]
|-
|'''BCL'''
|
Feedback files generated and sent by the BCL.

The BCL sends feedback with the following naming convention :

FDBTECH_[OK/KO]_[YYYYMMDD]_[SENT FILE NAME]_[RANDOM CARACTERS].xml

With

<ul>
<li> <blockquote><p>[OK/KO] : replaced either by OK (if the files has been transmitted and processed successfully) or KO (if there has been an error)</p></blockquote></li>
<li><blockquote><p>[YYYYMMDD] : replaced by the date of the feedback</p></blockquote></li>
<li><blockquote><p>[SENT FILE NAME] : replaced by the complete name of the original file (including it's extension)</p></blockquote> </li>
<li><blockquote><p>[RANDOM CARACTERS] : replaced by a random and unique caracters.</p></blockquote></li></ul>
|}

<ul>
<li><blockquote><p>'''For other reporting''' (08/371 / VNI...), '''there is no additional acknowledgment'''.</p></blockquote></li></ul>

This means that only '''acq''' will be created.

'''<u>Conclusion</u>''' : '''Checking that both trt and acq files were generated is a good way to ensure the good working of the Sending Service'''. Doing this way, you can be sure that your data was properly sent and '''e-file will be in charge of forwarding them to authorities'''.

=Solving known problems=

<span id="protect_error"></span>
*If you get this when double-clicking the launch.exe :

[[File:SDjl_3.png|552x140px|Protection Error Windows]]

Right-click the launch.exe file, then tick unblock : [[File:Sdjl_LauncherProperties.png|Protection Error Windows Solution]]

Or

click the address bar in the file explorer: [[File:SDjl_4.png|409x40px]] [[File:SDjl_5.png|335x33px|the adress bar]]

type ''cmd,'' [[File:SDjl_6.png|137x71px|where to type cmd]] then type ''launcher'' [[File:SDjl_7.png|379x83px|the command line windows]]

<span id="process_blocked"></span>
*Sometimes in console mode, the process seems to be blocked :

[[File:SDjl_BlockedProcessExamples.png|552x140px|Blocked processes]]

First try to hit ''Enter'' or ''space''. <br> If it is still blocked, you must stop it (CTRL+C) and [[#Start_the_application| restart it]].

*Error message when installing :

[[File:SDjl_InstallErr1.png|800px|Installation error message 1]]

Hit ''Enter'' twice, the program will ask for the username again, and go on.

*Error message after stop and start (401):

[[File:SDjl_InstallErr2_401.png|800px|Installation error message 2]]

The sending service password may have changed. You must install it again.

*Setup changes not applied despite being saved

After each change through the administration module, please [[#Stop_the_application|stop]] and [[#Start_the_application|start]] the sending service again.

= Certificate Update =

Once your Luxtrust certificate is activate in E-file, you need to replace de new keystore in the sending service.

If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
In this case you can use a simplified process by '''<u>simply replace the keystore:</u>'''
(-) Stop the Sending Service
(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
(-) Copy the attached keystore (to the sending service keystores folder.
(-) Rename this copy as the previous one.
(-) Restart the Sending Service

In case of a '''different kesytore password''', you '''<u>will have to reinstall the Sending Service</u>'''.<br>
You need import the new keystore and then [[#Change_your_setup|change the step-up ]] of your Sending Service

Sending Service

2026-05-04T08:35:42Z

Cso: /* Certificate Update */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

__TOC__

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

= Operating principle =

The '''Sending Service''' is our solution for the '''automatic transmission''' of reports and documents to authorities.

This solution is useful if you have a '''large number of reports''' to submit or if the manual sending does not suit your needs.

Please be aware that, in this case you will have to provide the files yourself according to the authorities' file specifications.

This tool is compatible with most of the current operating systems (Windows / Unix / Linux) and is usually <span style="color: #C00000">'''installed on a server'''</span> on your side.

With a suitable '''network mapping''', users can simply '''drop the file to be sent into the appropriate directory'''.

The file is then automatically ''' encrypted and sent'''.

= Prerequisites =

*Internet access
*<span style="color: #C00000">'''Java version 1.8 </span> <u>Note :</u> versions 8_351 and higher need a patch to be used with our system, see :[[Error_messages_list#JCE_cannot_authenticate_the_provider_BC]]'''
*If you use a proxy, authorize outgoing calls to [https://www.e-file.lu www.e-file.lu]. Port 443 (HTTPS) must be open.
*<span style="color: #C00000">'''Administrator rights''' </span> to install the Sending Service on the computer ''(Windows Start button > Control Panel > User Accounts > Manage User Accounts)''.
*OS: Windows or Linux
*Processor: Pentium 2 GHz or equivalent
*8 GB of RAM
*1 GB of free space on hard disk drive if the files are downloaded by ftp. If files are locally stored, provide a free space of above 100 MB or a regular purges.
*1 GB of free space on hard disk drive for logs. Regular purges are necessary as well.
*A <span style="color: #C00000">'''Sending Service user''' </span>, ''for example: aacSD'', and its password, ''for example: formation'', have to be available [[E-file_Administration#e-file_administrator_functions_.28e-file_v1.29|'''=> e-file administrator''']].
*The e-file account of the Sending Service user has to be linked to groups/modules, for example FATCA reporting + profile "Sending Service".
*A valid <span style="color: #C00000">'''keystore''' </span> (keystore.ks) and its <span style="color: #C00000">'''password''' </span> must be available
*The Sending Service user has to be properly configured in the e-file user administration tool in order to be able to receive <span style="color: #C00000">'''alerts''' </span> (receipt of acknowledgement and feedback files).

Note that you can find the prerequisites for the manual transmission there : [[Transmission_Module#System_requirements]]

= Installation / update with Sending Service Installer =

The Sending Service Installer is a tool that helps you install or configure quickly your Sending Service.

It can be downloaded from these links:

'''[https://www.e-file.lu/WSEfileFlex/messagebroker/assistantSD?cdLangIso=EN English version]'''

'''[https://www.e-file.lu/WSEfileFlex/messagebroker/assistantSD?cdLangIso=FR French version]'''

Once you have downloaded the application you will have to run it with Java by clicking the Run button.

[[File:Doc_SDInstaller_01.png|border|400 px]]

''If the message'' unable to run the application ''occurs, [[Transmission_Module#Delete_Java_cache|delete the java cache.]]''

'''The front page of the Sending Service Installer opens and shows you the different functionalities you can select: '''

* Install a new Sending Service
* Configure an existing Sending Service
* Update an existing Sending Service
* Send logs

[[File:Doc_SDInstaller_02.png|border|600 px]]

== Installation ==

'''Controls before installation:'''
* Check that the connected user is administrator of the computer
* Have an e-file Sending service user (login and password) (e.g. : aacSD)

To check whether a Sending service user exists, log on as an e-file administrator.
<u>'''Step 2</u>:'''

Click the '''Administration module'''

[[File:AdminAccess.png|700px]]

The user linked to the Sending Service usually follows the bellow naming rules : three
letters referring to the company (in lower case) following by "SD" in upper case. (e.g. :
aacSD)

[[File:User Sending service.png|900px]]
If the user doesn't exist, please contact us.

'''Start installation:'''
To install a <u> new </u> Sending Service, click on the button Install on the front page.

<u>'''Step 1'''</u>: Select the folder where you want to install your Sending Service.

[[File:Doc_SDInstaller_03.png]]

<u>'''Step 2'''</u>: The Sending Service is downloaded and saved in the selected folder.

<u>'''Step 3'''</u>: Select the keystore file, containing your LuxTrust certificate.

[[File:Doc_SDInstaller_04.png]]

<u>'''Step 4'''</u>: The Sending Service is ready to be configured. By clicking the '''Configuration''' button, you will be redirected to the '''Configuration menu''' of the '''.properties file'''.

[[File:Doc_SDInstaller_05.png]]

==Configuration==

To configure an <u>existing</u> Sending Service you have to select the folder where it is stored and click on the '''Configuration''' button.

[[File:10 SendServConf.png|border|600 px]]

The '''configuration''' of an existing Sending Service is similar to a new Sending Service.

<span style="background:yellow"> '''IMPORTANT:''' </span> each time you make changes to the properties (configuration) file, you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]] before, make your changes and then install the Sending Service again.

'''Configuration''' menu of the '''.properties file''' ([[Sending_Service#Configuration of the properties file | => Help: Configuration of the properties file]]):

[[File:Doc_SDInstaller_06.png|border|500 px]]

The '''Configuration''' menu allows you to setup your Sending Service.

The message ''Error: There are errors in your setup'' indicates that nothing has been set-up so far.

You have to configure each field marked in red.

If you have a '''proxy''', select ''True'' in the dropdown list and select ''More'' to type in the proxy settings.

''Note: The passwords will be asked during the finalization of the installation, all passwords are encrypted.''

''Note 2: You can edit each field by clicking the More button''

[[File:Doc_SDInstaller_07.png|border|600 px]]

The '''listeners''' can be activated in one shot by clicking on the button ''Listener state : Activate all''.

''Note: This functionality will force the Sending Service to scan all the folders, if you do not want all listeners to be activated, please activate manually the listeners you need.

Please consult our [[Sending_Service#Listener_list | Listener list]].

[[File:Doc_SDInstaller_08.png|border|600 px]]

If you have to submit Investment Funds reporting O4.1; O4.2 (EDIFACT format), you must complete this fields :

'''domain.descr''': Not relevant. You can provide abbreviated name of the Central Administration.

'''domain.env.ac.id.bcl''': this code is composed of a letter and six digits and has been provided to you by the CSSF (Example: P123, should be written as “P000123”).

'''domain.env.ac.id.cssf''': this code is composed of a letter and six digits and has been provided to you by the CSSF (Example P123, should be written as “P000123”).

The two others will be asked when installing (domain.en.ac.cd_auth and domain.env.ac.pwd)

[[File:Doc_SDInstaller_09.png|border|500 px]]

Once the configuration finished, you can click on '''Control''' to check if there is a configuration error.

The message ''No error in your setup'' means that the setup is correct.

[[File:Doc_SDInstaller_10.png|border|500 px]]

If there are no errors, you can click on '''Save''' to save your actual configuration.

[[File:Doc_SDInstaller_11.png|border|500 px]]

To install the Sending Service, you have to click on the '''Install''' button.

A pop-up window opens where you have to enter your passwords.

If you do not use a proxy, you can leave a blank for the proxy password<br/>
If you need to send O4.1 or O4.2 reports enter also those :<br/>
CA Password = '''domain.env.ac.pwd''': this '''authentication password''' has been provided to you by the CSSF (postal mail).<br/>
CA Code = '''domain.en.ac.cd_auth''': this '''authentication code''' has been provided to you by the CSSF (postal mail).<br/>

[[File:Doc_SDInstaller_12.png|border|500 px]]

Once finished a pop-up windows opens stating that the installation has been successful:

[[File:Doc_SDInstaller_13.png|border|500 px]]

To start your Sending Service open the folder where you installed it and run the file '''run.bat''' or '''InstallServiceNT.bat''' if you want to install the Service as a '''Windows Service'''.

[[Sending Service#Installation as a Windows Service|=> Installation as a Windows Service]]

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

==Update==

<span style="background:yellow"> '''IMPORTANT:''' </span> before updating your Sending Service you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]].

To update an <u> existing </u> Sending Service you have to click the ''Update'' button.

Then click on '''Check''' in order to verify if a new version is available.

[[File:Doc_SDInstaller_16.png|border|600 px]]

If your Sending Service is up-to-date you will get the following message:

[[File:Doc_SDInstaller_17.png|border|600 px]]

If there is a new version of the Sending Service available the following window will appear:

[[File:Doc_SDInstaller_18.png|border|600 px]]

To continue the update, click on Ok.

During the first steps, the new version will be downloaded.

Once you have reached step 3, the tool will ask you to select your old '''configuration''' file ('''.properties file''')

[[File:Doc_SDInstaller_19.png|border|600 px]]

The tool will automatically back-up of your old Sending Service. You have to wait until the process is finished.

[[File:Doc_SDInstaller_20.png|border|600 px]]

Step 5 will be the '''configuration''' of the updated Sending Service. You have to click on '''Configuration''' to access the '''Configuration''' menu.

[[File:Doc_SDInstaller_21.png|border|600 px]]

If there are changes in the configuration file of the Sending Service with the new version, the fields will be marked in red. You will have to select the proper setup and save the changes.

[[File:Doc_SDInstaller_22.png|border|600 px]]

Once the configuration finished, you can click on '''Control''' to check if there is a configuration error.

The message ''No error in your setup'' means that the setup is correct.

[[File:Doc_SDInstaller_10.png|border|500 px]]

If there are no errors, you can click on '''Save''' to save your actual configuration.

[[File:Doc_SDInstaller_11.png|border|500 px]]

To install the Sending Service, you have to click on the '''Install''' button.

A pop-up window opens where you have to enter your passwords.

''Note : If you do not use a proxy, you can leave a blank for the proxy password''

[[File:Doc_SDInstaller_12.png|border|500 px]]

==Send logs==

If you encounter issues with your Sending Service, you can use the Help function to send an email to the [[How to contact us|'''Client Support & Operations Desk''']].

The tool will create automatically a zip file containing the log files of your Sending Service you can attach to the email.<br><br>

[[File:Doc_SDInstaller_23.png]]

[[File:Doc_SDInstaller_24.png]]

= Manual installation with Command Prompt =

* Download the latest Sending Service version here: [https://www.e-file.lu/WSEfileFlex/SD/SD.zip '''Download latest Sending Service version''']
For UAT environment the latest version [https://homologation.e-file.lu/WSEfileFlex/SD/SD.zip '''is available here''']

* Extract and copy the entire content of the directory ServiceDeposant in the Sending Service directory. Ensure that the directory is <span style="color: #C00000">'''not read only''' </span>.
[[File:SD.png| 600 px]]

* Copy your <span style="color: #C00000">'''keystore'''</span> in the keystores folder of the Sending Service.

* Copy the <span style="color: #C00000">'''template_configInstall.properties'''</span> file and rename it [sender''Name''].properties.

* Complete the <span style="color: #C00000">'''properties file'''</span> as explained in [[Sending Service#Configuration of the properties file|'''Configuration of the properties file''']] chapter.

* Install the new Sending Service:
(-) Open Command Prompt
(-) Move to the root folder of your new Sending Service (for example: C:\Program Files\e-file\ServiceDeposant\)
(-) install.bat [sender''Name''].properties
(-) enter the root path of your JRE (for example: C:\Program Files\Java\jre1.8)
(-) Enter the password of the e-file Sending Service user
(-) Enter the password of your keystore
(-) Enter the password of your proxy if you use a proxy
(-) Enter the O4.x password for CSSF/BCL if needed
(-) Enter the O4.x authentication code for CSSF/BCL if needed
(-) Press the ENTER key

<span style="background:yellow"> '''IMPORTANT:''' </span>

SECURITY ENHANCEMENTS (june 2023)

The security settings of the Sending Service have been enhanced for O4.1 and O4.2 reports, the related passwords are now encrypted.

Please note that the installation procedure of the Sending Service slightly changed due to the implementation of this feature:

[[File:SD_CmdInstall.png | 800 px]]

At the end of the script you must get the following message: <span style="background:yellow"> '''BUILD SUCCESSFUL''' </span> indicating that the installation was successful.

[[File:SD_CmdInstall_success.png | 200 px]]

<span style="background:yellow"> '''IMPORTANT:''' </span> each time you make changes to the properties (configuration) file, you have to [[Sending Service#How to stop the Sending Service|stop the Sending Service]] before, make your changes and then install the Sending Service again.

== Configuration of the properties file ==

The <u>.properties</u> file (''template_configInstall.properties'') contains important information which are necessary to '''generate your configuration files''' during the physical installation.

The latter are used to start and use the Sending Service.

In other words :

* <span style="color: #C00000">'''The <u>.properties</u> file contains all the variables needed to run the Service Service.'''</span>

* <span style="color: #C00000">'''Any modification of the <u>.properties</u> file must be followed by an installation of the Sending Service to be really applied.'''</span>

<span style="color: #C00000">'''Please find below important information on how to configure your <u>.properties</u> file.''' </span>

<span style="color: #C00000">'''Please note, that at the end of setup, no '?' should remain in this file. </span>

'''E-file configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''efile.hostname=????'''''
|style="width:20em"| <span style="color: #C00000">'''www.e-file.lu'''</SPAN> for production environment,<br> or <br><span style="color: #C00000">'''homologation.e-file.lu'''</span> for test environment.
|-
|style="width:20em"| '''''efile.userId.Login=????'''''
|style="width:20em"| e-file login of the Sending Service user (Example: abcSD)
|-
|style="width:30em"| '''''keystore.path=@PROJECT_ROOT_PATH@/keystores/????.ks'''''
|style="width:20em"| path of the keystore (xxxx.ks)
|-
|style="width:20em"| '''''lang.code=FR??EN'''''
|style="width:100em"| language of the acknowledgement files
|}

'''Proxy configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''proxy.required=false??true'''''
|style="width:50em"| <span style="color: #C00000">'''true'''</span> if a proxy is used to access the internet through HTTP or HTTPS.
|-
|style="width:30em"| '''''proxy.host=???? <br> proxy.port=???? <br> proxy.user=???? <br> proxy.domainNTLM=????'''''
|style="width:100em"| Complete all other parameters according your network infrastructure.
|}

'''Configuration of connection for authority acknowledgement / feedback files'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''reportingXXXXXX.state=up??down'''''
|style="width:50em"| All subsequent blocks in the .properties file corespond to a particular type of reporting.

Please consult our [[Sending Service#Listener list|'''Listener list''']] to verify which reporting type is linked to which listener.

Example: if you only have to sent FATCA reportings, the state of the listener reportingFATCA.state has to be up: '''reportingFATCA.state='''<span style="color: #C00000">'''up'''</span>'''

The other listeners should be <span style="color: #C00000">'''down'''</span>.

|-
|style="width:30em"| '''''reportingXXXXXX.remoteDir'''''
|style="width:50em"| <span style="color: #C00000">'''Path to file location'''</span> for the relevant reporting.

|-
|style="width:30em"| '''''@PROJECT_ROOT_PATH@'''''
|style="width:50em"| <span style="color: #C00000">'''Dynamic parameter'''</span> indicating the Sending Service installation path.<br>
To change if you want to locate the user working directory elsewhere on the server or another machine.
In this case, indicate the full path to file (separator = '/').

|-
|style="width:30em"| '''''reportingXXXXXX.scheduleTime'''''''
|style="width:50em"| <span style="color: #C00000">'''Execution frequency'''</span> of Window Service to process files from this folder (30mn by default).
Feel free to '''reduce this value, but do not fall below 5mn= <i><span style="color: #C00000">300000</span></i>'''.

|-
|style="width:30em"| '''''reportingXXXXXX.deeplevel'''''''
|style="width:100em"| <span style="color: #C00000">Number of '''sub-levels'''</span> to scan.<br>
By default the value is <span style="color: #C00000">'''0'''</span>, which means that only files at the root of the folder will be taken in account.

|}

'''Business environment properties'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''domain.descr'''''
|style="width:20em"| Not relevant. You can provide '''abbreviated name''' of the Central Administration.
|-
|style="width:20em"| '''''domain.env.ac.id.cssf'''''
|style="width:20em"| Your <span style="color: #C00000"> '''CSSF identifier'''</span> of 7 characters, 1 letter and 6 numbers'''
|-
|style="width:30em"| '''''domain.env.ac.id.bcl'''''
|style="width:20em"| Your <span style="color: #C00000"> '''BCL identifier'''</span>
|-
|style="width:20em"| domain.env.ac.pwd
|style="width:50em"| Doesn't appear anymore in the .properties, it will be asked when installing. <span style="color: #C00000">'''Password'''</span> of the Central Administration provided by the CSSF
|-
|style="width:20em"| domain.env.ac.cd_auth
|style="width:100em"| Doesn't appear anymore in the .properties, it will be asked when installing. <span style="color: #C00000">'''Authentication code'''</span> of the Central Administration provided by the CSSF.

The CSSF has provided you in an official letter your <span style="color: #C00000">'''password'''</span> and <span style="color: #C00000">'''authentication code'''</span>. The above mentioned IDs, passwords and codes are necessary for the successful processing of the O4.1, O4.2; O1.2 and the former O1.1 reporting.
|}

'''Configuration of monitoring'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:20em"| '''''mon.app.heartbeat=false'''''
|style="width:20em"| If parameter is "true", we will be able to send you an alert if an interruption of your service is detected on our side (within 72 hours).
'''Should you want to use this feature feel free to contact us'''

|-
|style="width:20em"| '''''mon.app.origin=????'''''
|style="width:20em"| <span style="color: #C00000">'''Unique name'''</span> , without space, to enable us to identify your Sending Service. Not mandatory.
|-
|style="width:30em"| '''''mon.task.dist.period=60000'''''
|style="width:100em"| Frequency of the heartbeat (here 60000 milliseconds, 1 min). The monitoring window is set to 9 minutes. At least one heartbeat must have been registered during this interval otherwise the Sending Service is considered as down.
|-
|}

== Listener list ==

{|border="1" cellspacing="2" cellpadding="10"
|-
! Listener
! Sending Service folder
! Reporting type
! Business group
|<span style="color: #868686"> <small>''Internal <br /> Technical <br /> Business ID''</small/> </span>
|-
|<span style="color: #868686"> <small>''Please be informed that the listener '''efile.listener.state''' is no longer available in the properties file''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|-
|<span style="color: #868686"> <small>''Please be informed that the listener '''efile.replies.listener.state''' is no longer available in the properties file''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|<span style="color: #868686"> <small>''-''</small/> </span>
|-
| reportingMMF=up
|(-) ReportingDiffusion/MMF''
| <small>CSSF - MMF
| Money Market Fund Reporting
| <span style="color: #868686"> <small>''83-Money Market Fund Reporting''</small/> </span>
|-
| reportingOPC.automatique.state=up
|(-) ReportingDiffusion/OPC/envoi_Automatique/fichiersCCLUX<br><span style="color: #868686"> <small>''(-) ReportingDiffusion/OPC/envoi_Automatique/fichiersCCLUX/Enrichment''</small/> </span><br><span style="color: #868686"> <small>''(-) ReportingDiffusion/OPC/envoi_Automatique/TPT_FINESTI''</small/> </span>
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL : S1.3, S1.6, S2.13, TPTOBS, S4.4, S2.20 </small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPCExportXLS.automatique.state=up
| ReportingDiffusion/OPC/envoi_Automatique/ExportXLS
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL : S1.3, S1.6, S2.13, TPTOBS</small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPC.envoi_Historique.state=up
| ReportingDiffusion/OPC/envoi_Historique/fichiersCCLUX
| <small>CSSF - Investment Funds: O4.1, O4.2, O1.2, U1.1<br>BCL: S1.3, S1.6, S2.13, TPTOBS</small/>
| Station Finesti
| <span style="color: #868686"> <small>''8-Transmission of UCI regulatory reports''</small/> </span>
|-
| reportingOPC.semiAuto.state=up
| n/a
| n/a
| n/a
| n/a
|-
|reportingVni.state=up
|ReportingDiffusion/VNI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingDividende.state=up
| ReportingDiffusion/Dividendes
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingTAF.state=up
| (-) ReportingDiffusion/TAF<br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/declaration_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Rapport''</small/> </span>
| <small>CSSF: transactions in financial instruments (TAF)</small/>
| Report TAF-MIFID
| <span style="color: #868686"> <small>''71-MiFIR reporting''</small/> </span>
|-
|-
| reportingTAF.state=up
| (-) ReportingDiffusion/TAF<br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/declaration_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Transaction''</small/> </span><br>
<span style="color: #868686"> <small>''(-) OBSOLETE: ReportingDiffusion/TAF/annulation_Rapport''</small/> </span>
| <small>CSSF: transactions in financial instruments (TAF)</small/>
| Report TAF-MIFID
| <span style="color: #868686"> <small>''71-MiFIR reporting''</small/> </span>
|-
| reportingIORP.state=up
| ReportingDiffusion/IORP
| <small>CSSF - Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019 </small/>
| Report IORP
| <span style="color: #868686"> <small>''80''</small/> </span>
|-
| reportingCOREP.state=up
| ReportingDiffusion/COREP
| <small>CSSF:<br> SCOREP; SLAREX; SLCRXX; SNSFRX; SALMXX; CCOREP;<br>CLAREX; LCRXX; CNSFRX; CALMXX; CFINRP; SFINRP;<br>AEXXX; SAEXXX; CFPXXX; SFPXXX; CSBPXX;<br>SSBPXX; CSBPIM; SSBPIM; CLCRDA; SLCRDA; ALMXXX</small/>
| Rapport COREP
| <span style="color: #868686"> <small>''72-COREP reporting''</small/> </span>
|-
| reportingFINREP.state=up
| ReportingDiffusion/FINREP
| <small>CSSF: B2.4; B2.5; LCRDAX</small/>
| Rapport FINREP
| <span style="color: #868686"> <small>''73-FINREP reporting''</small/> </span>
|-
| reportingFINREP.EDIFACT.state=up
| ReportingDiffusion/FINREP/EDIFACT_CSSF
| <small>CSSF: B4.4</small/>
| Reporting EDIFACT
| <span style="color: #868686"> <small>''16-Edifact''</small/> </span>
|-
| reportingBOP.state=up
| ReportingDiffusion/BOP
| <small>BCL - Credit institutions: Balance of payments (BOP1.1; BOP1.2)</small/>
| Balance des Paiements
| <span style="color: #868686"> <small>''12-Edifact reporting''</small/> </span>
|-
| reportingBCLStat.state=up
| ReportingDiffusion/BCL_Statistics
| <small>BCL - Credit institutions: S0.1; S1.1; S1.4; S1.5; S1.8; S1.9;S1.12<br>S2.5-L; S2.5-N; S2.8; S2.9-L; S2.9-N; S3.2</small/>
| Statistiques BCL
| <span style="color: #868686"> <small>''13-BCL statistics''</small/> </span>

|-
| reportingAnacredit.state=up
| ReportingDiffusion/Anacredit
| <small>ANTREF; ANTT1M; ANTT2M; ANTT2Q</small/>
| Rapport Anacredit
| <span style="color: #868686"> <small>''74 ANACREDIT reporting''</small/> </span>

|-
| reportingSecurisation.state=up
| ReportingDiffusion/Securisation
| <small>BCL - Securitation vehicles: S2.14; S2.15; TPTTBS</small/>
| Véhicule titrisation
| <span style="color: #868686"> <small>''23-Véhicule titrisation''</small/> </span>
|-
|reportingSecurisationS2.14ExportXLS.state=up<br>reportingSecurisationS2.15ExportXLS.state=up<br>reportingSecurisationTPTTBSExportXLS.state=up
| ReportingDiffusion/Securisation/ExportXLS
| <small>BCL - Securitation vehicles:S2.14; S2.15; TPTTBS</small/>
| Véhicule titrisation
| <span style="color: #868686"> <small>''23-Securitisation vehicule''</small/> </span>
|-
| reportingTPTB.state=up
| ReportingDiffusion/TPT
| <small>BCL - Credit institutions: TPTBBL; TPTBBN; TPTBHR; TPTBHN</small/>
| Titre par Titre Bancaire
| <span style="color: #868686"> <small>''20-Security by security reporting''</small/> </span>
|-
| reportingTPTBExportXLS.state=up
| ReportingDiffusion/TPT/ExportXLS
| <small>BCL - Credit institutions: TPTBBL; TPTBBN; TPTBHR; TPTBHN</small/>
| Titre par Titre Bancaire
| <span style="color: #868686"> <small>''20-Security by security reporting''</small/> </span>
|-
| reportingESP.state=up
| ReportingDiffusion/ESP
| <small>CSSF: Special Enquiries (ESPREP)</small/>
| Rapport Enquête
| <span style="color: #868686"> <small>''15-CSSF polls''</small/> </span>
|-
| reportingPSF.state=up
| ReportingDiffusion/PSF
| <small>CSSF - Professional of the financial sector (PSFREP)</small/>
| Rapport PSF
| <span style="color: #868686"> <small>''18-PSF reporting''</small/> </span>
|-
| reportingSICAR.state=up
| ReportingDiffusion/SICAR
| <small>CSSF - SICAR</small/>
| Rapport SICAR
| <span style="color: #868686"> <small>''17-SICAR reporting''</small/> </span>
|-
| reportingOTH.state=up
| ReportingDiffusion/OTH
| <small>CSSF - Other reporting (OTHREP)</small/>
| Reporting OTHER (CSSF)
| <span style="color: #868686"> <small>''19-OTHER reporting (CSSF)''</small/> </span>
|-
| reportingRFOPC.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_OPC
| <small>CSSF UCI: <br /> (-) Annual Report (AR) <br /> (-) Semi-annual report (SR) <br /> (-) Letter of explanation (LE) <br /> (-) Other periodic report(RO) <br /> (-) Movements in the securities portfolios (MP)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>

|-
| reportingRAFIS.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_FIS
| <small> CSSF SIF: <br />
(-) Annual Report (AR) <br />
(-) Semi-annual report (SR) <br />
(-) Letter of explanation (LE) <br />
(-) Other periodic report (RO) <br />
(-) Movements in the securities portfolios (PM)</small/> <br />
<small> SICAR: <br />
(-) Annual Report (AR) <br />
(-) Annual Report (RO) </small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingPOPC.state=up
| ReportingDiffusion/DOC_FIS_OPC/PROSP_OPC
| <small>CSSF UCI: <br /> (-) Prospectus (PC) <br /> (-) Simplified prospectus (PS) <br /> (-) Letter of explanation (LE)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingPFIS.state=up
| ReportingDiffusion/DOC_FIS_OPC/PROSP_FIS
| <small>CSSF SIF: <br /> (-) Prospectus (PC) <br /> (-) Offering document (DE) <br /> (-) Letter of explanation (LE)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingKID.state=up
| ReportingDiffusion/DOC_FIS_OPC/KID_OPC
| <small> Key Investor Information Document (KID) <br />
(-) O: OPC Law 2010 and Law 2007 <br />
(-) K: SICAR <br />
(-) V: non-reglem. <br />
[[Sending Service#Automating process for KID packages|=> Automated process for KID packages]]</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingMR.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_REGUL
| <small>CSSF - Management Regulations of UCITS (MR)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingAI.state=up
| ReportingDiffusion/DOC_FIS_OPC/ART_INCORP
| <small>CSSF - Articles of Incorporation of UCITS (AI)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingML.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_LETTER
| <small>CSSF - Management Letters (ML) <br />
(-) O: OPC Law 2010 and Law 2007 <br />
(-) K: SICAR <br />
(-) V: non-reglem. <br />
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingLF.state=up
| ReportingDiffusion/DOC_FIS_OPC/LONG_FORM
| <small>CSSF - Long Form reports (LF)
(-) O: OPC Law 2010
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
|reportingMLGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/MGMT_GFI
|<small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingRGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/REPORT_GFI
|<small> CSSF <br />
Annual management company report <br />
Management company report, other frequency <br />
Explanation letter</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingDOC_OTH.state=up
| ReportingDiffusion/DOC_FIS_OPC/OTHER
|<small> CSSF <br />
Auditor's report (RR) <br />
Explanation letter (LE) (for funds or Sicar, CSSF codification S or A) <br />
Report Hong Kong Securities and Futures (HK)</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingCSDR.state=up
| ReportingDiffusion/CSDR
|<small> CSSF <br />
Report CSDR</small/>
| Reporting CSDR-9
| <span style="color: #868686"> <small>''78-Reporting CSDR''</small/> </span>
|-
| reportingGFI.state=up
| ReportingDiffusion/DOC_FIS_OPC/DOC_GFI
| <small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)

(-) Risk management function(GR) <br />
(-) OPCVM instruments information (ID) <br />
(-) Compliance Function (FC)<br />
(-) Internal audit function report (IA)<br />
(-) Complaints handling (TP) <br />
(-) Authorized third party complaints (LP) <br />
(-) Risk Management Procedure (PG)<br />
(-) Organization chart (OG) <br />
(-) Mandates table (TM) <br />
(-) Delegates of RFI (RD) <br />
(-) Branch activity (AS), <br />
(-) Own funds ratio (FP) <br />
(-) Risk management procedure AIFM (PN) <br />

</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingAML-AIFM-REG.state=up
| ReportingDiffusion/DOC_FIS_OPC/AML_AIFM_REG
| <small> CSSF <br />
CSSF-Management Letter of Investment Fund Managers (IFM EN) <br />
Gestionnaires des fonds d'investissement (GFI FR)

(-) Letter of explanation (LE) <br />

</small/>
| Doc OPC et FIS (circ. CSSF)
| <span style="color: #868686"> <small>''21-Métier des circulaires CSSF 08/371 et 09/423''</small/> </span>
|-
| reportingCD.state=up
| ReportingDiffusion/Various_Correspondence
| <small>BCL - Other reporting (OTX)</small/>
| Reporting OTHER (BCL)
| <span style="color: #868686"> <small>''22-Various correspondence (OTH=> BCL)''</small/> </span>
|-
| reportingSGO.state=up
| ReportingDiffusion/SGO
| <small>CSSF - Management company reporting (SGOREP)</small/>
| Rapport Société de Gestion
| <span style="color: #868686"> <small>''26-Management company''</small/> </span>
|-
| reportingDOCBNK.state=up
| ReportingDiffusion/DOC_BNK
| <small> AR: Annual Report <br />
AS: Annual report consolidated <br />
CO: Compliance Report <br />
GR: Governance Report <br />
IA: Internal Audit Report <br />
IC: ICAAP <br />
ID: ICAAP Consolidated <br />
LF: Long Form Report <br />
LC: Long Form consolidated <br />
LD: Long form branch or specific participation <br />
ML: ManagementLetter <br />
MC: Management letter consolidated <br />
RC: Risk Control Report <br />
RP: Recovery Plan <br />
SC: Single Customer View <br />
LG: Reconciliation LuxGAAP FINREP <br />
RR: Results distribution <br />
BD: AC member list <br /> IL: ILAAP <br /> IM: ILAAP consolidated
<br />
AC: Audit report on AML/CTF <br />
MF: Audit report on rules of conduct <br />
MM: Head quarter annual report <br />
RE: Report on out-of-court complaint resolution <br />
TR: Table on out-of-court complaint resolution <br />
AD: Circ. 18/697 annexe1 <br />

| Reporting des établissements de crédit
| <span style="color: #868686"> <small>''27-Reporting of credit institutions''</small/> </span>
|-
| reportingEDP.state=up
| ReportingDiffusion/EDP
| <small>CSSF - Payment instituions (EDPREP): Z1.1; Z1.2; Z1.4; Z2.1 </small/>
| Reporting EDP
| <span style="color: #868686"> <small>''29-Periodic reporting scheme for payment instituions (EDP)''</small/> </span>
|-
| reportingEME.state=up
| ReportingDiffusion/EME
| <small>CSSF - Electronic money instituions (EMEREP): W1.1; W1.2; W1.3; W1.4; W2.1 </small/>
| Reporting EDP
| <span style="color: #868686"> <small>''34-Electronic money reporting (EME)''</small/> </span>
|-
| reportingPubDiffu.state=up
| ReportingDiffusion/DOC_FIS_OPC/PUB_FINESTI<br>ReportingDiffusion/DOC_OPC_NOT_LU/PUB_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''32-Envoi pour publication/diffusion''<br>''33-Envoi pour publication/diffusion OPC non LU'' </small/> </span>
|-
| reportingOPCNONLU.state=up
| ReportingDiffusion/DOC_OPC_NOT_LU/LOCAL_REGISTRATION<br>ReportingDiffusion/DOC_OPC_NOT_LU/LOCAL_NOTIFICATION
| <small>HOST_UPDATE: [[Sending Service#Automating process for KID packages|Automated process for KID packages]]</small/>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''30-Enregistrement pour OPC non LU''<br>''31-Notification pour OPC non LU'' </small/> </span>
|-
| reportingMAJDOCLU.state=up
| ReportingDiffusion/DOC_FIS_OPC/HOST_UPDATE
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''37-Enregistrement/Mise à jour de documents Fond LU vers pays HOST''</small/> </span>
|-
| reportingSE.state=up
| ReportingDiffusion/SE
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingSEExportXLS.state=up
| ReportingDiffusion/SE/ExportXLS
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingSETransfoXLS.state=up
| ReportingDiffusion/SE
| <small> BCL - Financial companies: S2.16; S2.17; TPTIBS</small/>
| Reporting des sociétés émettrices
| <span style="color: #868686"> <small>''35-Issuing companies reporting''</small/> </span>
|-
| reportingASS.state=up
| ReportingDiffusion/ASS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-Reporting BCL pour les assurances''</small/> </span>
|-
| reportingASSExportXLS.state=up
| ReportingDiffusion/ASS/ExportXLS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-BCL report for insurances''</small/> </span>
|-
| reportingASSTransfoXLS.state=up
| ReportingDiffusion/ASS
| <small> BCL - Insurance companies: S0218-L; S0219-L; S0403-L; TPTASS </small/>
| Reporting BCL pour les assurances
| <span style="color: #868686"> <small>''63-BCL report for insurances''</small/> </span>
|-
| reportingDP.state=up
| ReportingDiffusion/CDP
| <small> BCL - Data on payment operation: V 1.1 - V 1.14 </small/>
| Collecte des données de paiement (CDP)
| <span style="color: #868686"> <small>''36-Data on payment instruments and operations''</small/> </span>
|-
| reportingNotifUcitsIV.state=up
| ReportingDiffusion/DOC_FIS_OPC/NOTIFICATIONS_UCITSIV
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''28-UCITS IV notification''</small/> </span>
|-
| reportingFINESTI.state=up<br>reportingLIBFINLU.state=up
| ReportingDiffusion/DOC_FIS_OPC/LIBRARY_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| reportingLIBFINNOTLU.state=up
| ReportingDiffusion/DOC_OPC_NOT_LU/LIBRARY_FINESTI
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
| <span style="color: #868686"> <small>''tbd''</small/> </span>
|-
| <span style="color: #868686"> <small>''OBSOLETE : reportingCRF.state=up''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
|-
| <span style="color: #868686"> <small>''OBSOLETE : reportingCRFEncrypted.state=up''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
| <span style="color: #868686"> <small>''n/a''</small/> </span>
|-
| reportingAIF.state=up
| ReportingDiffusion/AIF
| <small> CSSF - Alternative Investment Fund managers: AIF / AIFM </small/>
| (-) AIF <br /> (-) AMfine
| <span style="color: #868686"> <small>''54-AIFMD reporting''</small/> </span>
|-
| reportingFATCA.state=up
| ReportingDiffusion/FATCA
| <small> ACD - Financial Institutions - Foreign Account Tax Compliance Act (FATCA) </small/>
| Rapport FATCA
| <span style="color: #868686"> <small>''60-FATCA reporting''</small/> </span>
|-
| reportingCAA.state=up
| ReportingDiffusion/CAA
| <small> (-) CAA - Rapports narratifs (N01-N10 <br /> (-) CAA - XBRL reports Solvency II (S01-S23) </small/>
| Reporting CAA|
| <span style="color: #868686"> <small>''63-BCL report for insurances|''</small/> </span>
|-
| reportingCRS.state=up
| ReportingDiffusion/CRS
| <small> ACD - Financial Institutions - Common Reporting Standard (CRS) </small/>
| Reporting CRS
| <span style="color: #868686"> <small>''68-CRS reporting''</small/> </span>
|-
| reportingGRP_BNK.state=up
| ReportingDiffusion/GRP_BNK
| <small>«SHS-Group» report </small/>
| BCL SHS report
| <span style="color: #868686"> <small>''75-SHS Reporting''</small/> </span>
|-
| reportingUCIAR.state=up
| ReportingDiffusion/UCIAR
| <small>CSSF UCIAR </small/>
| UCIAR Reporting
| <span style="color: #868686"> <small>''86-UCIAR Reporting''</small/> </span>
|
|-
| reportingESP.state=up
| ReportingDiffusion/ESP
| <small>ICS reporting </small/>
| Rapport Enquête
| <span style="color: #868686"> <small>''15-CSSF polls''</small/> </span>
|
|-
| reportingCAADoraROI=up
| ReportingDiffusion/CAA
| <small>DORA Register of Information</small/>
| CAA reporting
| <span style="color: #868686"> <small>''62-CAA reporting''</small/> </span>
|
|-
| reportingCAADoraDIN.state=up
| ReportingDiffusion/CAA
| <small>DORA Incident Reporting</small/>
| CAA reporting
| <span style="color: #868686"> <small>''62-CAA reporting''</small/> </span>
|
|-
| reportingPDAOFI.state=up
| ReportingDiffusion/PDAOFI
| <small>PDAOFI Reporting</small/>
| self-assessment questionnaire PDAOFI
| <span style="color: #868686"> <small>''88-PDAOFI reporting''</small/> </span>
|}

= Installation as a Windows Service =

Once the installation the Sending Service is completed, the <span style="color: #C00000">'''InstallServiceNT.bat'''</span> file is available and you can complete your Sending Service installation by creating the Windows Service <span style="color: #C00000">'''ServiceDeposant'''</span>.

Execution frequency of Window Service ServiceDeposant to process files from this folder is 30mn by default [[Sending_Service#Configuration of the properties file | => Configuration of the properties file]].

Double click the <span style="color: #C00000">'''InstallServiceNT.bat'''</span> file.

[[File:InstallServiceNT.png|600 px]]

A Command Prompt window opens up and closes as quickly as it popped up. The new Windows Service <span style="color: #C00000">'''ServiceDeposant'''</span> is now available.

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

[[File:WindowsService.png]]

<u>IMPORTANT</u>: Please ensure the '''Sending Service user''' that is linked to this Windows Service has <span style="color: #C00000">'''Internet rights'''</span> (=> Right click on ''Service deposant'' > select ''Properties'' > select ''Log On'' tab).

If you want to uninstall the Windows Service, please double click the <span style="color: #C00000">'''UninstallServiceNT.bat'''</span> file.

= Installation on Unix/Linux =

*Move to the ServiceDeposant directory
<u> Example </u>: /opt/ServiceDeposant/

*Check that you have execution rights (x) on the Install.sh file
<u> Example </u>: ls -l

*If not, just add this right using the chmod command
<u> Example </u>: chmod 755 install.sh

*Launch Install.sh with the configuration file as parameter
<u> Example </u>: install.sh config.properties

*Press the Enter key and enter the Java path when requested

*Press the Enter key again and wait for the ‘BUILD SUCCESSFUL’ message.

* Once installed, launch the run.sh to run the sending service

= How to start the Sending Service =

* Double click the <span style="color: #C00000">'''run.bat'''</span> command available at the root folder of your Sending Service

In the case you created a '''Windows Service'''

* Double click the <span style="color: #C00000">'''StartService NT.bat'''</span> command available at the root folder of your Sending Service

or

* Browse to the <span style="color: #C00000">'''Windows Services'''</span> console (''Start > Control Panel > Administrative Tools > Services'') and right click the '''ServiceDeposant''' service and start the service.

[[File:WindowsService.png]]

The message *Fin Ok* means that the installation was successful.

= How to stop the Sending Service =

* If you launched the Sending Service using the <span style="color: #C00000">'''run.bat'''</span> command, you can stop it pressing the keys Ctrl+C+Y.

In the case you created a '''Windows Service'''

* Double click the <span style="color: #C00000">'''StopService NT.bat'''</span> command available at the root folder of your Sending Service

or

* Browse to the <span style="color: #C00000">'''Windows Services'''</span> console (''Start > Control Panel > Administrative Tools > Services'') and right click the '''ServiceDeposant''' service and stop the service.

[[File:WindowsService.png]]

= Automatic and semi-automatic sending of O4.1 and O4.2 reports =

<span style="color: red;>'''Changed on July 2023'''</span>

For [http://www.cssf.lu/en/supervision/ivm/ucits/legal-reporting/ '''O4.1 and O4.2 reports'''] the [http://www.cssf.lu/en/supervision/'''CSSF'''] is expecting '''EDIFACT''' file format (ISO 9735).

Please note that you have to generate yourself a '''flat text file''' for these reports, which, once dropped into the dedicated directory of the Sending Service, will be transformed into the expected EDIFACT format.

'''The structure of the flat file is detailed in the document [[Media:StructMess_EN.pdf|Structure of messages for interface files from fund manager host system]], pages 8 to 14.'''

The Sending Service provides two sending ways :

<u>Automatic sending</u>

In this case, the flat files must be dropped into the '''OPC\envoi_Automatique\fichiersCCLUX''' folder of your Sending Service.

If the flat file is well formed, the reports are '''changed to ''.T62'' for O4.1, respectively ''.T63'' for O4.2''' into the subfolder '''Edifact''' by default ([[#IdBothCasesEdifact |see how to change it]]).

On sending, the ''.T6x'' is transformed into ''.trt''.
If the sending is OK, a ''.acq'' is generated otherwise a ''.err''. All this in the Edifact subdirectory.<br/>
If nothing appears in the Edifact subdirectory, it means that things are not going well.<br/>
<blockquote>You must check the Edifact subfolder for .acq or .err</blockquote>

Note : The .err that may be temporary generated within the PDF file for O4.2 reports must be ignored.

<u>Semi-automatic sending</u>

If you want to use this kind of sending, you have to drop your flat file into the '''OPC\envoi_SemiAutomatique\fichiersCCLUX_aTraiter''' folder of your Sending Service, where it will be converted to a PDF file and stored in the '''OPC\envoi_SemiAutomatique\fichiersPDF_aValider''' folder.

The PDF file allows you to check the data of your flat file in a more user friendly way before you transmit it to the supervisory authority.

Once checked/validated, the PDF file must be dragged into '''OPC\envoi_SemiAutomatique\fichiersPDF_aEnvoyer''' folder.

After being checked for errors, the reports are '''changed to ''.T62'' for O4.1, respectively ''.T63'' for O4.2''' into the subfolder '''Edifact''', <span style="color: red;>BE CAREFUL : this folder is in OPC\envoi_Automatique\fichiersCCLUX\'''Edifact''' by default.</span>([[#IdBothCasesEdifact |see how to change it]])

On sending, the ''.T6x'' is transformed into ''.trt''.
If the sending is OK, a ''.acq'' is generated otherwise a ''.err''. All this in the Edifact subdirectory.<br/>
If nothing appears in the Edifact subdirectory, it means that things are not going well.<br/>
<blockquote>You must check the Edifact folder for .acq or .err</blockquote>

<div id="IdBothCasesEdifact"></div>
<u>In both cases</u>

* The reports sent are .T62, resp. .T63, you will find them into the transmission follow-up with such names. The CSSF answsers with EDOFBR....xml files as feedbacks.<br/>

* The .ack files are not sent anymore, even for the O4.1 Fundsquare file.

* The '''Edifact results subfolder''' is the same for the two ways of sending : automatic and semi-automatic. You can choose the one you want by changing the property '''''reportingOPC.automatique.edifact.remoteDir''''' into the .properties file. In the installation assistant (assistantSD), this property is under reportingOPC.automatic.state's button 'More'. <br>Then install again to enable it.

= Automating process for KID packages =

In the context of KID updates to be filed to the CSSF, it is possible to set up the automatic sending of KIDs packages (.zip files) from our server to your Sending Service. Once the Sending Service has received the KIDs, they are copied in one of the following directory:

'''Luxembourgish fund'''
\ReportingDiffusion\DOC_FIS_OPC\KID_OPC

'''Foreign fund'''
\ReportingDiffusion\DOC_OPC_NOT_LU\HOST_UPDATE

Then the files are sent to the CSSF in the usual way.

If you want to use this feature, please
* Install the Sending Service [[Sending Service#Installation with Sending Service Installer|'''=> Installation with Sending Service Installer''']] or [[Sending Service#Manual installation with Command Prompt|'''=> Manual installation with Command Prompt''']]
* Ensure that the listeners <span style="color: #C00000">'''reportingOPCNONLU.state'''</span> and <span style="color: #C00000">'''reportingKID.state''' </span> in your properties file are <span style="color: #C00000">'''=up'''</span>
* Contact our Regulatory Service department and request the installation of this specific feature.
* Generate the KID package (.zip file) in the UCITS IV Document Management application (https://www.e-file.lu). Please note that in some cases an automated process on our servers can be installed.

Do not hesitate to contact our [[How to contact us|'''Client Support & Operations Desk''']] if you need further assistance.

= Sending progress and follow up =

== Transmission following ==

Here are the default transmission followup files that are created depending on the state in the transmission workflow.

<div style="text-align: left;">
{| border="1" cellspacing="2" cellpadding="10"
|-
! scope="col" | '''File extension'''
! scope="col" | '''Description'''
|-
||<span style="color: #C00000">''' .trt'''</SPAN>
|| <u> Example </u>: file processing of '''FileName.ext'''
Once the file has been dropped into the appropriate folder, the Sending Service will start processing it and rename it as follows:

'''FileName.ext_YYYYMMDDhhmmssmmm.'''<span style="color:#C00000">'''trt'''</SPAN>
|-
|| <span style="color: #C00000">'''.acq'''</SPAN>
|| Once the processing finished an <span style="color:#C00000">'''.acq'''</SPAN> file will be generated in the same folder by the Sending Service in order to confirm the transmission:

'''FileName.ext_YYYYMMDDhhmmssmmm.'''<span style="color:#C00000">'''acq'''</SPAN>

|-
||<span style="color: #C00000">'''.err'''</SPAN>
||An <span style="color: #C00000">'''.err</SPAN> file is created in case or an error:

'''FileName.ext_YYYYMMDDhhmmssmmm'''<span style="color:#C00000">'''.err'''</SPAN>

Please open this file and analyse the error message.

|-

|}

</div>
<br/>

== Feedback files (Replies folder) ==

For some reporting, the administration will give you more detailed feedback. In this case, those feedback will replace the corresponding ones in the previous section.

By default, <u> feedback files</u> are dropped into <span style="color:#C00000">'''Replies'''</span> sub-folders. <span style="color:#C00000">'''Replies'''</SPAN> folders are created dynamically in the initial transmission folder of the files. They only appear when feedback files, sent by the supervisory authorities, have to be stored. If the folder is deleted, it will be automatically recreated upon receipt of new feedback files.

The name and location of the <span style="color:#C00000">'''Replies'''</SPAN> folder may be configured differently from the implementation of the solution with your company’s project coordinator [[Sending_Service#Configuration|=> Configuration .properties file.]]

<div style="text-align: left;">
{| border="1" cellspacing="2" cellpadding="10"
|-
! scope="col" | '''Autority'''
! scope="col" | '''Description'''

|-
||<span style="color: #C00000">'''CSSF'''</SPAN>
||Feedback files generated and sent by the CSSF.

Please click the picture below to access the '''Naming convention for CSSF reportings''' document:

[[File:FBR CSSF.png|500 px|link=http://www.cssf.lu/fileadmin/files/Reporting_legal/transport_securisation_reporting/Convention_de_nom.pdf]]

|-
||<span style="color: #C00000">'''BCL'''</SPAN>
||Feedback files generated and sent by the BCL.

The BCL sends feedback with the following naming convention :

FDBTECH_[OK/KO]_[YYYYMMDD]_[SENT FILE NAME]_[RANDOM CARACTERS].xml

With
* [OK/KO] : replaced either by OK (if the files has been transmitted and processed successfully) or KO (if there has been an error)
* [YYYYMMDD] : replaced by the date of the feedback
* [SENT FILE NAME] : replaced by the complete name of the original file (including it's extension)
* [RANDOM CARACTERS] : replaced by a random and unique caracters.

|-
||<span style="color: #C00000">'''ACD'''</SPAN>
||Feedback files generated and sent by the ACD.

ACD's feedback files are available in the sub-folder "Replies". For example, /ServiceDeposant/ReportingDiffusion/FATCA/Replies/

Each feedback has a specific status which is available in the file name: ACK, NAK, VAL, WAR, ERR (Cf. Status feedback ACD).

Example feedback from ACD :

FATCA_20150520080022_F0_2016_B_1970010112345_006M8M.00000.LE.442_P_ack.xml

FATCA_20150520080023_F1_2016_B_19700202123_ZZLRV4.99999.SL.442_T_ack.xml

The "Replies" folder is created upon feedback receipt. Please check the Sending Service's configuration if the "Replies" folder is not available. In the configuration file (properties file), the variable corresponding to "Configuration of connection for feedback" and the one corresponding to "Configuration of connection for authority acknowledgement" should be set to "up".
|}

* '''For other reporting''' (08/371 / VNI...), '''there is no additionnal acknowledgment'''. <br>
This means that only <span style="color: #C00000">'''acq'''</span> will be created. <br><br>

<u>'''Conclusion'''</u> : <span style="color: #C00000">'''Checking that both trt and acq files were generated is a good way to ensure the good working of the Sending Service'''</span>. Doing this way, you can be sure that your data was correctly sent and '''e-file will be in charge of forwarding them to authoritites'''.

= Sending Service versions and updates =

Please be informed that our system is able to check the version of the program you are running. This information is sent to our database when the service is launched.

Please note that the <b>''RELEASE_README.txt''</b> file, located at the root folder provides you information on the different Sending Service versions.
The example below indicates that the Sending Service version 4.5.6 is being used:
[[File:SD evol.png| 800 px]]

In case of major Sending Service changes, our [[How to contact us|'''Client Support & Operations Desk''']] will notify you by sending an INFO-email to your local e-file administrator.

= Functional testing and test environment =

In fact, it is not necessary to test the working of the Sending Service by performing a test sending.

Indeed, all '''technical checks''' are performed during the startup process.

In other words, if the startup process does not generate any error message, then the Sending Service is running properly.

* Launch the Sending Service through the dos <b>''run.bat''</b> file or through the Windows Service.
* '''Check the log files''' generated in the <b>''log''</b> folder of Service Deposant.
* The Sending Service is running properly if the '''error.log file''' is empty or if it does not contain any line in relation to the starting process.

<u>'''Remark'''</u> : If a problem occurs after this check, it would certainly be a functional problem or could also be linked to the e-file configuration.

In this case, we recommand to '''check the ''.err'' file''' automatically generated during the sending process.

If you want to install a '''test environment''' in order to validate the your source files or to anticipate a migration procedure, please follow the steps below:

* '''Duplicate the production Sending Service''' by copying the whole ''Service Deposant'' folder to another location.
* '''Adjust the properties file''' to redirect the service to our test environment : Homologation. <b>''e-file.hostname''</b> = <span style="color: #C00000">'''homologation.e-file.lu'''</span>

Please note that, if the user login may remain the same, the password will be changed in our test environment.
Feel free to set a new password

Do not forget to '''modify the path''' to your test files if these ones are stored in a specific location.

Finally, to identify cleary both Windows services, you must adjust the parameters used to identify the Windows Service name : <b>''wrapper.app.long.name''</b> and <b>''wrapper.app.name''</b>

* <span style="color: #C00000">'''Relaunch the Sending Service installation'''</span>

= Common Problems =

== The service does not start ==

Please refer to following procedure if a Sending Service, launched through <u>the Windows Services</u> does not start in order to analyze the origin of the problem.

<br><br>
<u>'''Attempt to start it with the DOS command line'''</u><br>
<br>
* Open a '''DOS''' window and make sure to have '''administrator rights''' on the computer (''Start>run : cmd'')
* Move to the folder where the sending service is installed
* '''Run the command : <span style="color: #C00000">''run.bat''</span>'''
<br>

'''If the sending service runs properly''' through this DOS command, without generating error logs, we recommand to follow [[Sending Service#IdSolve|this solving method]]'''.<br>
<span style="color: #C00000">'''Otherwise, a log analysis is necessary'''</span><br><br>

=== Log Analysis===

The <b>''error.log''</b> file located in the <b>''log''</b> folder at the root of Sending Service, contains the error trace causing this dysfunction.<br>

'''You will find below the most common known problems.'''<br>
<br>
In all cases, we are at your disposal to assist you in this analysis. Feel free to contact our <span style="color: #C00000">'''[[How to contact us|'''Client Support & Operations Desk''']].'''</span><br>

==== Network Problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Error when webservice's call 'obtenirVersionsDocument'.Unrecognized SSL message, plaintext connection.</span><br><br>

<u>'''Solving Method'''</u><br>
* Check the proxy parameters of your properties file
* '''Relaunch the sending service installation process''' so that the changes are taken into account.

<u>'''Error 2'''</u> : <span style="color: blue">java.net.ConnectException: Connection timed out: connect.</span><br>
<u>'''Error 3'''</u> : <span style="color: blue">Connection timed out: connect [TIP: The machine can be unauthorized by the proxy]</span><br><br>

<u>'''Solving Method'''</u><br>
* Check the configuration of your proxy with your network team : It must be correctly configured to allow outbound connections to our server [http://www.e-file.lu www.e-file.lu] HTTP and HTTPS.

==== Other time out problem====

<u>'''Error'''</u> : <span style="color: blue">Startup failed: Timed out waiting for signal from JVM.</span><br>

<u>'''Solving Method'''</u><br>
* '''Increase''' the value of <b>''wrapper.startup.timeout''</b> parameter from your properties file. As an example, increase from 300 to 600.
* '''Relaunch the sending service installation''' to take the changes in account.

This parameters indicates the duration allocated to the service startup. Is some cases, 5 mn may not be enough, particularly with slow proxy connections to e-file.

==== Administrator rights issue with Windows service ====
[[File:SDadmin.jpg]]

By default, a windows service runs through a '''non administrator system user'''.<br>
Depending on your architecture, it is possible that this user account has not enough rights to ensure a proper start of the Sending Service. (proxy issue for example)<br>

Then simply change this setting this way: <br>

<div id="IdSolve"></div>
<u>'''Solving Method'''</u><br>
* Open the '''Windows services''' window. (Start > Control Panel > Administrative tools > Services)
* Right click on the service named <b>''ServiceDéposant''</b>
* Select the <b>''Properties''</b> item
* Indicate an administrator user account and password in <b>''LogOn''</b> tag.
* Relaunch the service

== Errors are raised during sending ==

The generation of an <b>''.err''</b> file during the processing of your report indicates an issue during the sending.<br>

In this case,''' it is necessary to analyze the problem because the data could not be transmitted to the authorities.'''<br><br>

The <b>''.err''</b> file contains the explanation of the error that generates this dysfunction.<br><br>

'''You will find below the most common problems.'''<br>
In all cases, we are at your disposal to assist you in this analysis. Feel free to contact <span style="color: #C00000">'''[[How to contact us|'''Client Support & Operations Desk''']].'''</span><br>

==== Functional Problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Failed to validate XML</span><br>
<u>'''Error 2'''</u> : <span style="color: blue">All error indicating a data problem</span><br><br>

<u>'''Solving Method'''</u><br>
* '''Correct the source file''' according to the error messages indicated in the <b>''.err''</b> file.
* '''Resend the file'''.

==== User account problem ====

<u>'''Error 1'''</u> : <span style="color: blue">Getting addressees information Une erreur est survenue lors de l'execution du Workflow</span><br>

<u>'''Solving Method'''</u><br>
* '''Link''' the sending service user account to the right '''User Group''' according to the kind of reporting your are trying to send. His profils should be <b>''SD with response''</b>

= Certificate Update =

Once your Luxtrust certificate is activate in E-file, you need to replace de new keystore in the sending service.

If you have followed the renewal process, the '''updated keystore should have the same password''' as the old one <br>
In this case you can use a simplified process by '''<u>simply replace the keystore:</u>'''
(-) Stop the Sending Service
(-) Rename the existing (previous) .ks found in the sending service keystores folder (to ***_old.ks for example.)
(-) Copy the attached keystore (to the sending service keystores folder.
(-) Rename this copy as the previous one.
(-) Restart the Sending Service

In case of a '''different kesytore password''', you '''<u>will have to reinstall the Sending Service</u>'''.<br>
Please find below what you need to do:
* Stop your sending service
* Copy your new keystore in the keystores folder of the Sending Service.
* Update the configuration: It is possible that your new Keystore has a different name than the previous Keystore therefore it is necessary to update the configuration.
'''E-file configuration'''

{| class="wikitable;style="background:#112233"
|-
! Variable
! Description
|-
|style="width:30em"| '''''keystore.path=@PROJECT_ROOT_PATH@/keystores/????.ks'''''
|style="width:20em"| path of the keystore (xxxx.ks)
|-
|}

* Install the sending service: To install the Sending Service, you have to click on the '''Install''' button. A pop-up window opens where you have to enter your passwords.

''Note : If you do not use a proxy, you can leave a blank for the proxy password''

[[File:Doc_SDInstaller_12.png|border|500 px]]

Once finished a pop-up windows opens stating that the installation has been successful:

[[File:Doc_SDInstaller_13.png|border|500 px]]

To start your Sending Service open the folder where you installed it and run the file '''run.bat''' or '''InstallServiceNT.bat''' if you want to install the Service as a '''Windows Service'''.

[[Sending Service#Installation as a Windows Service|=> Installation as a Windows Service]]

[[Sending Service#How to start the Sending Service|=> How to start the Sending Service]]

[[Sending Service#How to stop the Sending Service|=> How to stop the Sending Service]]

ProductCoverage

2026-04-17T14:14:04Z

Cso:

__NOTOC__

<small>''Page's last update : {{REVISIONDAY2}}/{{REVISIONMONTH}}/{{REVISIONYEAR}}''</small>

You can find below the list of reports that can be managed through e-file.

<div style="height:500px; width:auto; overflow-y:scroll">

{| class="wikitable filterable mw-collapsible sortable"
|+ <span style="white-space:nowrap">Available reports</span>
|- <div style="font-weight:bold; vertical-align:top; position:sticky;top:-1px;z-index:10">
! style= "background-color:#52BBBD; color:#FFF" | Concerned companies
! style= "background-color:#52BBBD; color:#FFF" | Report<br /> naming convention
! style= "background-color:#52BBBD; color:#FFF" | Table
! style= "background-color:#52BBBD; color:#FFF" | Details
! style= "background-color:#52BBBD; color:#FFF" | Authority
! style= "background-color:#52BBBD; color:#FFF" | Sending way
! style= "background-color:#52BBBD; color:#FFF" | An e-file form exists
! style= "background-color:#52BBBD; color:#FFF" | Sending type in transmission module
! style= "background-color:#52BBBD; color:#FFF" | Example
</div>
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| NOTREP
| INI or<br /> UPD
| Notification procedures to be followed by a UCITS governed by Luxembourg law wishing to market its units in another Member State of the European Union
| CSSF
| S3
| yes
| -
|
|- style="vertical-align:bottom;"
| Investment Funds
| -
| O1.2
| Monthly financial information for guaranteed funds
| CSSF
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| -
| O4.1
| Yearly financial information
| CSSF
| KS
| yes
| -
|
|- style="vertical-align:bottom;"
| Investment Funds
| -
| O4.2
| Interventions on the futures and options markets
| CSSF
| KS
| yes
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0103
| S1.3
| Monthly statistical balance sheet for money market funds (MMF)
| BCL
| KS
| yes
| -
| S0103_L4_202302_B000000999_O009990099_20240619_001.xml
|- style="vertical-align:bottom;"
| Investment Funds
| TPTOBS
| TPTOBS
| Monthly Security by security reporting for investment funds
| BCL
| KS
| yes
| -
| TPTOBS_L3_202107_B000000009_O009990000_20240807_001.xml<br /> TPTOBS_L3_202107_P000000999_NAF99999999900000_20240603_001.xml<br />
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| (-) PC<br /> (-) DE<br /> (-) LE
| SIF:<br /> (-) Prospectus (PC)<br /> (-) Offering document (DE)<br /> (-) Letter of explanation (LE)
| CSSF
| KS
| no
| 08/371 FIS prospectus
| PROSP-O0000xxxx-2025-04-01-41c13c08-ef59-4183-870f-80d7a00c54e8.zip<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-DE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> PROSP-K0000xxxx-2025-04-01-41c13c08-ef59-4183-870f-80d7a00c54e8.zip<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-DE-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| (-) AR<br /> (-) SR<br /> (-) LE<br /> (-) RO<br /> (-) PM
| SIF Law 2007:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report SIF (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (PM)<br /> SICAR:<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| CSSF
| KS
| no
| 08/371 FIS report
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| RR<br /> HK
| Auditor report<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| KS
| no
| 08/371 report not in 08/371
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-HK-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (SICAR)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| RR<br /> HK
| Auditor report<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| KS
| no
| 08/371 report not in 08/371
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-HK-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (SICAR)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RR-LL-0000.pdf (Inv. Fund Manag.)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| (-) PC<br /> (-) PS<br /> (-) LE
| UCI:<br /> (-) Prospectus (PC)<br /> (-) Simplified prospectus (PS)<br /> (-) Letter of explanation (LE)
| CSSF
| KS
| no
| 08/371 UCI prospectus
| PROSP-O0000xxxx-2025-04-01-41c13c08-ef59-4183-870f-80d7a00c54e8.zip<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PS-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| AIF
| Alternative Investment Fund reporting
| CSSF
| S3
| yes
| AIF Reporting
| AIFREP-P12345678-A00000001-F00000000-00000000-MAN-20140129145000.zip<br /> AIFREP-P12345678-A00000111-V00002222-00003333-AIF-20140129145000.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| MAN
| Alternative Investment Fund reporting (AIF Manager)
| CSSF
| S3
| yes
| AIF Reporting
| AIFREP-P12345678-A00000001-F00000000-00000000-MAN-20140129145000.zip<br /> AIFREP-P12345678-A00000111-V00002222-00003333-AIF-20140129145000.zip
|- style="vertical-align:bottom;"
| Credit Institutions
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| AnaCredit:<br /> Collection of granular credit and credit risk data
| BCL
| KS
| no
| AnaCredit
| ANTREF_201801_LUB00999_20180205-001.xml<br /> ANTT1M_201801_LUB00999_LUB00999_20180205-001.xml<br /> ANTT2M_201801_LUB00999_LUB00999_20180205-001.xml<br /> ANTT2Q_201803_LUB00999_LUB00999_20180405-001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0218-L
| n/a
| Quarterly statistical balance sheet of insurance corporations – Luxembourg entity
| BCL
| KS
| yes
| BCL report for insurances
| S0218-L_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom;"
| Insurance Corporations
| S0219-L
| n/a
| Information on valuation effects on the balance sheet of insurance corporations
| BCL
| KS
| yes
| BCL report for insurances
| S0219-L_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0403-L
| n/a
| Annual Premiums, claims and commissions of insurance corporations – Luxembourg entity
| BCL
| KS
| yes
| BCL report for insurances
| S0403-L_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom;"
| Insurance Corporations
| TPTASS
| n/a
| Monthly Security by security reporting of insurance corporations
| BCL
| KS
| yes
| BCL report for insurances
| TPTASS_L0_aaaamm_Rrrrrrrrrr_Dddddddd_aaaammjj_nnn
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SHSGRP
| SHSGRP
| «SHS-Group» report:<br /> Statistics on holdings of securities by reporting banking groups
| BCL
| KS
| no
| BCL SHS
| SHSGRP_201709_LUB00999_20171206_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0001
| S0.1
| Daily deposit
| BCL
| KS
| no
| BCL statistics
| S0001_L2_20130616_B000000999_B000000999_20130617_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0101
| S1.1
| Monthly statistical balance sheet
| BCL
| KS
| no
| BCL statistics
| S0101_L6_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0104
| S1.4
| Adjustments due to valuation effects|
| BCL
| KS
| yes
| BCL statistics
| S0104_L3_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0105
| S1.5
| Information on interest rates in EUR
| BCL
| KS
| yes
| BCL statistics
| S0105_L4_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0108
| S1.8
| Information on securititation<br /> transactions launched<br /> by credit institutions
| BCL
| KS
| yes
| BCL statistics
| S0108_L2_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0109
| S1.9
| Information on CNY (renmibi) operations
| BCL
| KS
| yes
| BCL statistics
| S0109_L0_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0205-L
| S2.5-L
| Quarterly statistical balance sheet
| BCL
| KS
| no
| BCL statistics
| S0205-L_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0205-N
| S2.5-N
| Quarterly statistical balance sheet<br /> of credit institutions -<br /> Luxembourg entity and its branches
| BCL
| KS
| no
| BCL statistics
| S0205-N_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0208
| S2.8
| Real estate loans for<br /> Lxuembourg buildings
| BCL
| KS
| no
| BCL statistics
| S0208_L0_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0209-L
| S2.9-L
| Staff report -<br /> Luxembourg entity
| BCL
| KS
| no
| BCL statistics
| S0209-L_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| S0209-N
| S2.9-N
| Staff report -<br /> Luxembourg entity and its branches
| BCL
| KS
| no
| BCL statistics
| S0209-N_L0_202403_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0302
| S3.2
| Non balance sheet information
| BCL
| KS
| no
| BCL statistics
| S0302_L0_202407_B000000999_B000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| COFREP
| SMRTLA<br /> CMRTLA<br /> MRTLAX<br /> CRESOL<br /> RESOLX<br /> SRESOL<br /> CFRXXX<br /> CIRXXX<br /> FMIRXX<br /> LDRXXX
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| KS
| no
| COREP report
| COFREP-B00000999-2014-03-CCOREP-00-L-N-S-CCOREP.xbrl<br /> COFREP-B00000999-2014-03-CCOREP-00-L-N-S.zip<br /> COFREP-B00000999-2019-12-SRESOL-00-L-N--.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| COFREP
| SMRTLA<br /> CMRTLA<br /> MRTLAX<br /> CRESOL<br /> RESOLX<br /> SRESOL<br /> CFRXXX<br /> CIRXXX<br /> FMIRXX<br /> LDRXXX
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| KS
| no
| COREP report
| COFREP-B00000999-2014-03-CCOREP-00-L-N-S-CCOREP.xbrl<br /> COFREP-B00000999-2014-03-CCOREP-00-L-N-S.zip<br /> COFREP-B00000999-2019-12-SRESOL-00-L-N--.zip
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AC
| Audit Report on AML/CTF
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-AC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AD
| Circ. 18/697 annexe1
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-AD-EN-0000.pdf
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| AR
| Annual Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-AR-EN-0000.pdf
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AS
| Annual report consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-AS-EN-0000.pdf
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | BD
| AC Member List
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-BD-EN-0000.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| CO
| Compliance Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-CO-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| GR
| Governance Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-GR-EN-0000.pdf<br />
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| IA
| Internal Audit Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-IA-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| IC
| ICAAP
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-IC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | ID
| ICAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-ID-EN-0000.pdf
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | IL
| ILAAP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-IL-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | IM
| ILAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-IM-EN-0000.pdf<br />
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LC
| Long Form Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-LC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LD
| Long Form Branch or Specific Participation
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-LD-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| LF
| Long Form Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-LF-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LG
| Reconciliation LuxGAAP FINREP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-LG-EN-0000.pdf<br />
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | MC
| Management Letter Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-MC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | MF
| Audit report on rules of conduct
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-MF-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| ML
| Management Letter
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-ML-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | MM
| Head quarter annual report
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-MM-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| RC
| Risk Control Report
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-RC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | RE
| Report on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-RE-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| RP
| Recovery Plan
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-RP-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | RR
| Results Distribution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-RR-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| SC
| Single Customer View
| CSSF
| KS
| no
| Credit institution reporting
| DOCREP-B00000998-00000000-0000-2009-12-31-SC-EN-0000.pdf<br />
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | TR
| Table on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Credit institution reporting
| style="vertical-align:bottom;" | DOCREP-B00000998-00000000-0000-2009-12-31-TR-EN-0000.pdf<br />
|- style="vertical-align:bottom;"
| Financial Institutions - Common Reporting Standard (CRS)
| CRS
| CRS
| Automatic exchange of<br /> financial account information<br /> on a global level
| ACD
| KS
| yes
| CRS report
| CRS_20170615114523_CRS701_2016_B_19751234567_01234567890M00000000_P.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| BRA
| Quarterly reporting on the<br /> financial health of the branches<br /> parent entities
| CSSF
| KS
| no
| CSSF enquiry
| ESPREP-B0999-2024-06-BRA.xlsx
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| DEP
| Residential credit deposits
| CSSF
| KS
| no
| CSSF enquiry
| ESPREP-B0999-2024-06-DEP.xlsx
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DCOR
| n/a
| Reporting Entity<br /> B: Credit institution
| CSSF
| S3
| no
| CSSF enquiry
| DCOR-ENNNNNNNN-YYYY-MM-DD_UUID.json
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DCOR
| n/a
| Reporting Entity<br /> P: PFS
| CSSF
| S3
| no
| CSSF enquiry
| DCOR-ENNNNNNNN-YYYY-MM-DD_UUID.json
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| RES
| Residential real estate market
| CSSF
| S3
| no
| CSSF enquiry
| ESPREP-B0999-2024-06-RES.xlsx
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| STT
| Stress test in order to assess<br /> the interest rate risk<br /> arising from non-trading<br /> book activities
| CSSF
| KS
| no
| CSSF enquiry
| ESPREP-B0999-2008-06-STT.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0101
| V1.1
| Customer transfers
| BCL
| KS
| no
| Data payment collection (CDP)
| V0101_L2_201601_W000000003_B000000999_20160201_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0110
| V1.10
| Stock taking of payment accounts in bank money
| BCL
| KS
| no
| Data payment collection (CDP)
| V0110_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01100
| V1.100
| Payment services provided by e-money institutions and payment institutions without the provision of payment accounts
| BCL
| KS
| no
| Data payment collection (CDP)
| V01100_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0111
| V1.11
| OTC cash transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0111_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01110
| V1.110
| Payment initiation services (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01110_L0_202407_Z000000999_Z000000999_20240808_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01110-F
| V1.110-F
| Payment initiation services (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01110-F_L0_202405_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0112
| V1.12
| Transactions via telecommunication, digital or IT device
| BCL
| KS
| no
| Data payment collection (CDP)
| V0112_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0113
| V1.13
| Credits to the accounts by simple book entry
| BCL
| KS
| no
| Data payment collection (CDP)
| V0113_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0114
| V1.14
| Debits from the account by simple book entry
| BCL
| KS
| no
| Data payment collection (CDP)
| V0114_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0102
| V1.2
| Interbank transfers
| BCL
| KS
| no
| Data payment collection (CDP)
| V0102_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0120
| V1.20
| Customer Credit transfers sent (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0120_L0_202309_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0120-F
| V120-F
| Customer Credit transfers sent (Fraud)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01200
| V1.200
| Stock of issued payment cards
| BCL
| KS
| no
| Data payment collection (CDP)
| V01200_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01201
| V1.201
| Stock of distributed payment cards
| BCL
| KS
| no
| Data payment collection (CDP)
| V01201_L0_202407_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0121
| V1.21
| Customer credit transfers received
| BCL
| KS
| no
| Data payment collection (CDP)
| V0121_L0_202201_B000000999_B000000999_20230421_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01210
| V1.210
| Stock of terminals by terminal type
| BCL
| KS
| no
| Data payment collection (CDP)
| V01210_L0_202407_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01220
| V1.220
| Stock of accounts (except e-money accounts)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01220_L0_202206_W000000099_W000000099_20240613_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01221
| V1.221
| Stock of e-money accounts
| BCL
| KS
| no
| Data payment collection (CDP)
| V01221_L0_202407_B000000999_B000000999_20240806_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01222
| V1.222
| Stock of accessed accounts - account information services (AIS)
| BCL
| KS
| no
| Data payment collection (CDP)
| V01222_L0_202407_B000000999_B000000999_20240814_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01230
| V1.230
| Number of customers
| BCL
| KS
| no
| Data payment collection (CDP)
| V01230_L0_202407_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0103
| V1.3
| Domiciliations
| BCL
| KS
| no
| Data payment collection (CDP)
| V0130_L0_202407_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130
| V1.30
| Direct debits - reporting as creditor's PSP (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0103_L0_202407_B000000099_B000000099_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01300-F
| V1.300-F
| Losses due to fraud per liability bearer
| BCL
| KS
| no
| Data payment collection (CDP)
| V01300-F_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130-F
| V1.30-F
| Direct debits - reporting as creditor's PSP (fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0130-F_L0_202403_B000000999_B000000999_20240412_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0131
| V1.31
| Direct debits - reporting as debtor's PSP
| BCL
| KS
| no
| Data payment collection (CDP)
| V0131_L0_202407_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0104
| V1.4
| Inventory cards / terminals
| BCL
| KS
| no
| Data payment collection (CDP)
| V0104_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0140
| V1.40
| SEPA R-transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0140_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0141
| V1.41
| Interbank payment transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0141_L0_202407_B000000999_B000000999_20240731_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0142
| V1.42
| Intermediated payment transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0142_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0105
| V1.5
| Card transactiosn (Issuing part)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0105_L0_202405_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0150
| V1.50
| Card transactions with cards issued by resident PSPs (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0150_L0_202405_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0150-F
| V1.50-F
| Card transactions with cards issued by resident PSPs (fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0150-F_L0_202405_B000000099_B000000099_20240820_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0151
| V1.51
| Electronic card transactions with cards issued by resident PSPs, split by Merchant Category Codes (MCC)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0151_L0_202407_B000000999_B000000999_20240813_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0152
| V1.52
| Card transactions acquired by resident PSPs (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0152_L0_202405_B000000999_B000000999_20240802_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0152F
| V1.52F
| Card transactions acquired by resident PSPs (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0152-F_L0_202405_B000000999_B000000999_20240802_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0153
| V1.53
| Fundings and withdrawals related to prepaid cards
| BCL
| KS
| no
| Data payment collection (CDP)
| V0153_L0_202407_B000000999_B000000999_20240812_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0106
| V1.6
| Card transactiosn (Acquiring part)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0106_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0160
| V1.60
| Cheques and money remittances (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0160_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0160-F
| V1.60-F
| Cheques and money remittances (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0160-F_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0107
| V1.7
| Cheques and money orders
| BCL
| KS
| no
| Data payment collection (CDP)
| V0107_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0170
| V1.70
| Over-the-counter (OTC) cash transactions
| BCL
| KS
| no
| Data payment collection (CDP)
| V0170_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0108
| V1.8
| Electronic money scheme
| BCL
| KS
| no
| Data payment collection (CDP)
| V0108_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0180
| V1.80
| Book entries
| BCL
| KS
| no
| Data payment collection (CDP)
| V0180_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0109
| V1.9
| Card based e-money schemes
| BCL
| KS
| no
| Data payment collection (CDP)
| V0109_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0190
| V1.90
| Fundings and withdrawals in e-money (except prepaid cards)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0190_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0191
| V1.91
| E-money transfers (payments)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0191_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0191-F
| V1.91-F
| E-money transfers (Fraud)
| BCL
| KS
| no
| Data payment collection (CDP)
| V0191-F_L0_202405_B000000999_B000000999_20240809_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| DCO
| Fonds de garantie<br /> des dépôts Luxembourg<br /> (FGDL)
| CSSF
| KS
| no
| DCOR reporting
| DCOR-ENNNNNNNN-YYYY-MM-DD_UUID.json<br /> DCOR-B00057255-2024-02-23_c15473ff-53c7-d38c-5219-3bdf950121f1.json
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Z1.1
| Balance sheet
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z11-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Z1.2
| Identification of third-party<br /> funds held and incorporated in the balance sheet
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z12-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Z1.4
| Capital adequacy of<br /> payment institutions
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z14-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Z2.1
| Profit and loss accoount
| CSSF
| KS
| no
| EDP report
| EDPREP-Z9999-2011-03-Z21-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| W1.1
| Balance sheet
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W11-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| W1.2
| Identification of third-party<br /> funds held and incorporated<br /> in the balance sheet
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W12-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| W1.3
| Statement of<br /> authorised reinvestments
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W13-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| W1.4
| Capital adequacy of<br /> electronic money institutions
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W14-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| W2.1
| Profit and loss account
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W21-L0-L-N--.xls
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| W4.5
| Analysis of shareholdings
| CSSF
| KS
| no
| EME report
| EMEREP-W9999-2011-03-W45-L0-L-N--.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Institutions - Foreign Account Tax Compliance Act (FATCA)
| FATCA
| FATCA
| Foreign Account Tax Compliance Act Reporting
| ACD
| KS
| yes
| FATCA sending
| FATCA_20150520080022_F0_2016_B_1970010112345_006M8M.00000.LE.442_P.xml
|-
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | (-) LE
| (-) Letter of explanation (LE)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Fin. Rep. of GFI
| style="vertical-align:bottom;" | DOCREP-S00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> no naming convention<br /> no naming convention<br /> no naming convention
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AR
| Annual report of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Fin. Rep. of GFI
| style="vertical-align:bottom;" | DOCREP-S00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-LE-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> no naming convention<br /> no naming convention<br /> no naming convention
|- style="vertical-align:bottom;"
| Credit Institutions
| FRCREP
| B2.4
| Information on participating interest<br /> and subordinated loans
| CSSF
| S3
| no
| FINREP report
| PARTANDSUBLOANS-ENNNNNNNN-L-YYYY-MM-DD_UUID.zip (eg:PARTANDSUBLOANS-B00000499-L-2023-12-31_eb6809e1-bbf1-6cbc-5be1-35da4a526817.zip)<br />
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| FRCREP
| B2.5
| Information on staff costs and taxes<br /> and subordinated loans
| CSSF
| KS
| no
| FINREP report
| CFEREP-B00000999-2025-12-COREPY-L-N_133e79ec-d891-403c-983b-84af00c5b25b.zip<br /> B25.xml<br /> FRCREP-B9999-2007-12-B25-L0-L-N--.zip
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| LCRDA
| LCRDAX
| CSSF
| S3
| no
| FINREP report
| CFEREP-B00000999-2024-08-LCRDAX-N-N_a6fca981-2f2c-2a98-ddba-b241c2366a1a.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Companies
| S0216
| S2.16
| Quarterly statistical balance of Financial Companies
| BCL
| KS
| yes
| Issuing companies reporting
| S0216_L1_201406_DSE0003524_DSE0003524_20140720_001.xml<br />
|- style="vertical-align:bottom;"
| Financial Companies
| S0217
| S2.17
| Transactions of Financial Companies
| BCL
| KS
| yes
| Issuing companies reporting
| S0217_L1_201406_DSE0003524_DSE0003524_20140720_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| KI
| Key Investor Information Document<br /> (-) O: OPC Law 2010 and Loi 2007<br /> (-) K: SICAR<br /> (-) V: non-reglem.
| CSSF
| S3
| no
| PRIIPS Document
| DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf<br /> DOCREP-VNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-KI-LL-0000.pdf
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | LF
| Long Form reports (UCI Law 2010)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Long forms CSSF 09/423
| style="vertical-align:bottom;" | DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LF-LL-0000.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| SGOREP
| G21
| (-) SG 1A: Financial situation<br /> (-) SG 1B: Profit and loss account<br /> (-) SG 1C: Table relating to other activities<br /> (-) SG 2: Other activities<br /> (-) SG: Personnel Table relating to staff
| CSSF
| KS
| no
| Management company report
| SGOREP-S9999-2009-03-G21-L2-S-N--.xls
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | ML
| Management letters<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007<br /> (-) K: SICAR
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Management letters CSSF 09/423
| style="vertical-align:bottom;" | DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf (OPC Loi 2010)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf (OPC Loi 2007)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf (SICAR)
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | ML
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Management letters of GFI
| style="vertical-align:bottom;" | DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ML-LL-0000.pdf<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| AI
| Articles of Incorporation of UCITS<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| S3
| no
| Management regulation/status
| DOCOFF-ENNNNNNNN-UUID.zip<br /> containing DOCREP-ENNNNNNNN-YYYY-MM-DD-AI-LL.pdf <br /> - The expected format of an UUID is: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX<br /> - E in (O, K, V)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| MR
| Management Regulations of UCITS<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007
| CSSF
| S3
| no
| Management regulation/status
| DOCOFF-ENNNNNNNN-UUID.zip<br /> containing DOCREP-ENNNNNNNN-YYYY-MM-DD-MR-LL.pdf <br /> - The expected format of an UUID is: XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX<br /> - E in (O, K, V)
|- style="vertical-align:bottom;"
| MiFID II / MiFIR
| TAFREP
| TAF
| Article 26 of Regulation<br /> No 600/2014:<br /> Obligation to report transactions<br /> (Markets in financial instruments => MiFIR)
| CSSF
| KS
| no
| Mifir reporting
| TAFREP-B00000001-2017-04-15-123456.xml
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| (-) GR<br /> (-) ID<br /> (-) FC<br /> (-) IA<br /> (-) TP<br /> (-) LP<br /> (-) PG<br /> (-) OG<br /> (-) TM<br /> (-) RD<br /> (-) AS<br /> (-) FP<br /> (-) PN
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Other closing documents of GFI
| style="vertical-align:bottom;" | DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (SIAG Partie I Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (GFI chapitre 15 Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (SIAG/FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (FIAAG)<br />
|- style="vertical-align:bottom;"
| Other reporting CSSF BCL
| OTHREP
| OTH
| Other reporting
| CSSF
| KS
| no
| OTHER reporting<br /> (=> CSSF)
| OTHREP-B9999-HELLO_WORLD.xlsx
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| BOP101
| BOP1.1
| Balance of payments reporting
| BCL
| KS
| no
| Payments balance
| BOP101_20130616_B000000999_B000000999_20130617_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| BOP102
| BOP1.2
| Cross-border payments<br /> executed for the account<br /> of the resident counterparts
| BCL
| KS
| no
| Payments balance
| BOP102_20240731_B000000999_B000000999_20240801_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| PSFREP
| (-) Basic reporting<br /> (-) Ad hoc reporting<br /> (-) Annual information
| Reporting population:<br /> (-) Investment firms<br /> (-) Specialised PFS<br /> (-) Support PFS
| CSSF
| KS
| no
| PSF report
| PSFREP-P9999-2008-03-P11-L1-L-N--.xlsx
|- style="vertical-align:bottom;"
| Insurance Corporations
| N01 (Comp); N02 (Comp); N03 (Comp);<br /> N04 (Comp); N05 (Réviseur); N06( Réviseur);<br /> N07 (Comp); N08 (Comp); N09 (Comp); N10 (Comp); N11 (Comp); N12 (Réviseur);<br /> N13<br /> (Comp);<br /> N14<br /> 'Comp)
| n/a
| Rapports narratifs
| CAA
| KS
| no
| Rapport narratif (CAA) (Companie) -<br /> Governance Re<br /> <br /> Rapport narratif (CAA) (Réviseur) -<br /> Governance Rep
| N01V-LU-01-20181231-CAA-LEIDéclarant-LEIDéposant.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CSDREP
| CSDR
| Reporting CSDR:<br /> Introduction of quarterly internalised settlement reporting requirements<br /> pursuant to Article 9(1) of EU Regulation No 909/2014 (CSDR)
| CSSF
| KS
| no
| Reporting CSDR
| CSDREP-B00000001-B00000001-2018-Q4-20190101-1.zip
|- style="vertical-align:bottom;"
| Credit Institutions
| BNNNN
| B4.4
| List of head offices, agencies,<br /> branches and representative offices
| CSSF
| KS
| no
| Reporting EDIFACT
| B0001809.T01
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Institutions for Occupational Retirement Provision
| FNDREP
| IORP
| Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019
| CSSF
| S3
| no
| Reporting IORP
| FNDREP-ENNNNNNNN-NNNNNNNN-YYYY-MM-DD-SUBTYPE-L-D_UUID.zip
|- style="vertical-align:bottom;"
| Money Market Funds (MMF)
| MMFREP
| MMF
| • According to Article 37 of Regulation (EU) 2017/1131, the manager of a MMF must report information to the competent authority (CSSF) of the MMF, at least on a quarterly basis or - for MMF with assets under management of less than Eur 100 million - on at least an annual basis.<br /> • The first quarterly report should be sent to the competent authority of the MMF no later than 30 days after the end of Q1 2020.
| CSSF
| S3
| no
| Reporting Money Market Fund
| MMFREP-P00000789-O00000654-00000123-2020-Q1-0001.zip<br /> MMFREP-P00000789-O00000654-00000123-2020-Y1-0001.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0112-L
| S1.12-L
| Indirect withdrawal and remittance of banknotes denominated in EUR through an intermediary
| BCL
| KS
| no
| Reporting S1.12-L
| S0112-L_L0_201905_B000000999_B000000999_20130605_001.xml
|- style="vertical-align:bottom;"
| Financial Companies
| TPTIBS
| TPTIBS
| Monthly security by security reporting of Financial Companies
| BCL
| KS
| yes
| Reporting securities by securities of issuing companies
| TPTIBS_L1_201406_DSE0003524_DSE0003524_20140720_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| U11
| U1.1
| Monthly financial information UCITS and UCI
| CSSF
| KS
| yes
| Reporting U
| U11REP-B00000012-O00008450-00000002-201512-RAP-1421893257541.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBBL
| TPTBBL
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| KS
| no
| Security by security Banks
| TPTBBL_L5_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBBN
| TPTBBN
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| KS
| no
| Security by security Banks
| TPTBBN_L5_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBHN
| TPTBHN
| Security by security report–<br /> Off-balance sheet data–<br /> Non-resident
| BCL
| KS
| no
| Security by security Banks
| TPTBHN_L2_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBHR
| TPTBHR
| Security by security report–<br /> Off-balance sheet data–<br /> Resident customers
| BCL
| KS
| no
| Security by security Banks
| TPTBHR_L2_201804_B000000999_B000000999_20180617_001.xml
|- style="vertical-align:bottom;"
| Investment Funds
| SFDR
| Periodical disclosures
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| KS
| no
| SFDR Reporting
| SFDR-ENNNNNNNN-TTTTT-YYYY-MM-DD-UUID.zip<br /> SFDR-O00000406-PERIO-2023-03-31-41c13c08-ef59-4183-870f-80d7a00c54e8
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| SFDR
| Precontractual disclosures
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| KS
| no
| SFDR Reporting
| SFDR-ENNNNNNNN-PRECO-UUID.zip<br /> SFDR-O00000406-PRECO-41c13c08-ef59-4183-870f-80d7a00c54e8.zip
|- style="vertical-align:bottom;"
| Investment Funds
| SIC
| K3.1
| Financial information to be submitted by investment companies in risk capital (SICARs)
| CSSF
| KS
| no
| Sicar reporting
| SICREP-B999999-K999990000-2008-06-K31-L0-L-N.xls
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| (-) AR<br /> (-) SR<br /> (-) LE<br /> (-) RO<br /> (-) PM
| UCI Law 2010:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (MP)
| CSSF
| KS
| no
| SIF or SICAR : 08/371 FIS report<br /> UCI : 08/371 report
| SIF:<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf<br /> SICAR:<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf<br /> UCI:<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-AR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-SR-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-LE-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-RO-LL-0000.pdf<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-PM-LL-0000.pdf
|- style="vertical-align:bottom;"
| Insurance Corporations
| S01; S02; S03; S04; S05;<br /> S06 (Réviseur); S07; S08;<br /> S09; S10; S11; S12; S13;<br /> S14; S15; S16; S17; S18;<br /> S19; S20; S23
| n/a
| XBRL reports Solvency II
| CAA
| KS
| no
| Solvency II Reporting
| S01V-LU-01-20181231-CAA-LEIDéclarant-LEIDéposant.pdf
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| S0214
| S2.14
| Quarterly statistical balance
| BCL
| KS
| yes
| Titrisation vehicles
| S0214_L1_201412_T000000999_T000123001_20150120_001.xml<br />
|- style="vertical-align:bottom;"
| Securitisation Vehicles
| S0215
| S2.15
| Transactions and write-offs/write-downs on securitised loans
| BCL
| KS
| yes
| Titrisation vehicles
| S0215_L1_201412_T000000999_T000123001_20150120_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| TPTTBS
| TPTTBS
| Security by security reporting
| BCL
| KS
| no
| Titrisation vehicles
| TPTTBS_L1_201412_T000000999_T000123001_20150120_001.xml
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| UCIAR
| n/a
| Reporting Entity<br /> A: Alternative Investment fund manager (AIFM)
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| UCIAR
| n/a
| Reporting Entity<br /> B: Credit institution
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom;"
| Investment Funds
| UCIAR
| n/a
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| UCIAR
| n/a
| Reporting Entity<br /> S: Management company
| CSSF
| KS
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| UCIAR
| n/a
| Reporting Entity<br /> (-) P: PFS<br /> (-) I: Support PFS
| CSSF
| S3
| no
| UCIAR Reporting
| UCIAR-ENNNNNNNN-YYYY-MM-DD-UUID.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Other reporting CSSF BCL
| OTXREP
| OTX
| Various correspondence
| BCL
| KS
| no
| Various correspondence (OTH)<br /> (=> BCL -OTHER reporting)
| OTXREP-B0nnn-BOP_IDE_2015_B0nnn_20160615_001.xls
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| (-) GR<br /> (-) ID<br /> (-) FC<br /> (-) IA<br /> (-) TP<br /> (-) LP<br /> (-) PG<br /> (-) OG<br /> (-) TM<br /> (-) RD<br /> (-) AS<br /> (-) FP<br /> (-) PN
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Other closing documents of GFI
| style="vertical-align:bottom;" | DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-GR-LL-0000.pdf (FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (SIAG Partie I Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-ID-LL-0000.pdf (GFI chapitre 15 Loi 2010)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-FC-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-IA-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP-YYYY-MM-DD-TP-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-LP-LL-0000.pdf FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-PN-LL-0000.pdf FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-OG-LL-0000.pdf (FIAAG<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (SIAG/FIAAG)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xls (FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-TM-LL-0000.xlsx (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-RD-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (IFMs) (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-AS-LL-0000.pdf (FIAAG)<br /> DOCREP-SNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ANNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (IFMs)<br /> DOCREP-ONNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (SIAG/FIAAG)<br /> DOCREP-KNNNNNNNN-CCCCCCCC-PPPP -YYYY-MM-DD-FP-LL-0000.pdf (FIAAG)
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| style="vertical-align:bottom;" | AR<br /> RO
| Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI)(FR)<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | KS
| style="vertical-align:bottom;" | no
| style="vertical-align:bottom;" | Fin. Rep. of GFI
| style="vertical-align:bottom;" | DOCREP-S00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-S00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-AR-EN-0000.pdf<br /> DOCREP-A00001234-00000000-0000-2018-01-15-RO-EN-0000.pdf
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| ALM
| ALMXXX
| CSSF
| S3
| no
| -
| CFEREP-B00000999-2024-08-ALMXXX-N-N_a6fca981-2f2c-2a98-ddba-b241c2366a1a.zip
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| LF
| Long Form Report
| CSSF
| KS
| no
|
|
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| ML
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| CSSF
| KS
| no
|
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| ML
| Management Letter
| CSSF
| KS
| no
|
|
|- style="vertical-align:bottom;"
| Investment Funds
| S0106
| S1.6
| Monthly statistical balance sheet for non-money market funds (non-MMF)
| BCL
| KS
| yes
| -
| S0106_L2_202402_B000000999_NAF00000000000000_20240625_001.xml<br /> S0106_L2_202402_P000000999_O999990009_20240605_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0213
| S2.13
| Quarterly statistical balance sheet for non-MMF investment funds
| BCL
| KS
| yes
| -
| S0213_L2_202103_P000000999_O009990009_20240731_001.xml<br /> S0213_L2_202103_S000000999_O099990009_20240606_001.xml
|- style="vertical-align:bottom;"
| Investment Funds
| S0220
| S2.20
| Quarterly financial information
| BCL
| KS
| yes
| -
| S0220_L0_202512_B000000999_NAF66999999900000_20260127_001.xml
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0404
| S4.4
| Marketing countries
| BCL
| KS
| yes
| -
| S0404_L0_202512_B000000999_NAF66999999900000_20260209_001.xml<br /> S0404_L0_202512_B000000999_O999990009_20260209_001.xml
|- style="vertical-align:bottom;"
| Insurance Corporations
| CED
| Source file reception from CAA
| Etat de situation relatif aux contrats en déshérence
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| CPR
| Source file reception from CAA
| Compte rendu
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| ESP
| Source file reception from CAA
| Enquête spécifique
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ETR
| Source file reception from CAA
| Etat trimestriel
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| FIR
| Source file reception from CAA
| Fiche de renseignement
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| PDA
| Source file reception from CAA
| Rapport PDAL (Procédure de Dissolution Administrative sans Liquidation)
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RAC
| Source file reception from CAA
| Rapport actuariel
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RDC
| Source file reception from CAA
| Rapport distinct complémentaire du réviseur
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RDI
| Source file reception from CAA
| Rapport distinct du réviseur
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RGO
| Source file reception from CAA
| Rapport de gouvernance
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RLB
| Source file reception from CAA
| Rapport LBCFT
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RRE
| Source file reception from CAA
| Rapports sur le traitement des réclamations
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Insurance Corporations
| RSE
| Source file reception from CAA
| Rapport distinct Solvabilité 2 de l'entreprise
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RSO
| Source file reception from CAA
| Rapport distinct Solvabilité 2 du réviseur
| CAA
| KS
| no
| -
|
|- style="vertical-align:bottom;"
| Credit Institutions
| ICS
| ICS
| Yearly Survey on Covered Investment claims (SIIL)
| CSSF
| S3
| no
| ICS Reporting
| ICS-ENNNNNNNN-YYYY-MM-DD_UUID.json <br /> (eg:ICS-B00057255-2024-02-23_c15473ff-53c7-d38c-5219-3bdf950121f1.json)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ROI<br /> DIN
| n/a
| DORA Register of Information<br /> DORA Incident Reporting
| CAA
| KS
| no
| Rapport narratif (CAA) (Companie) -<br /> Governance Re<br /> <br /> Rapport narratif (CAA) (Réviseur) -<br /> Governance Rep
| ROIV-LU-01-20250303-CAA-LEIDéclarant-LEIDéposant.zip<br /> DINV-LU-01-20250303-CAA-LEIDéclarant-LEIDéposant.zip
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DPAAIF
| n/a
| self assessment <br /> questionnaire PDAOFI
| CSSF
| S3
| no
| PDAOFI Reporting
| DPAAIF-EIIIIIIII-YYYY-UUID.zip <br /> (e.g.: DPAAIF-P99999999-2024-41c13c08-ef59-4183-a456-870f80d7a00c54e8.zip)
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CFEREP
| Monthly modules:<br /> - ALMXXX<br /> - LCRDAX<br /> Quarterly modules:<br /> - AEXXXX<br /> - COREPX<br /> - FINREP<br /> - FRTBXX<br /> - IRRBBX<br /> - LAREXX<br /> - LEVERX<br /> - NSFRXX
| (-) ALM corep_alm_con.xsd<br /> corep_alm_ind.xsd corep_alm.xsd<br /> (-) LCRDA corep_lcr_da_con.xsd<br /> corep_lcr_da_ind.xsd corep_lcr_da.xsd<br /> (-) IRRBB irrbb.xsd
| CSSF
| S3
| no
| COREP report
| CFEREP-B00000999-2024-08-ALMXXX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.xbrl<br /> inside <br /> CFEREP-B00000999-2024-08-ALMXXX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.zip<br /> <br /> <br /> CFEREP-B00000999-2024-08-LCRDAX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.xbrl<br /> inside<br /> CFEREP-B00000999-2024-08-LCRDAX-NN_a6fca981-2f2c-2a98-ddbab241c2366a1a.zip
|}
</div>

Useful link :
<span class="plainlinks">[https://www.cssf.lu/wp-content/uploads/Naming-convention.pdf <span style="display: inline-block;
background-color: #009ACE;
color: white; text-align: center; font-family: sans-serif; font-size:0.8vw;
width: auto; height: auto;
border: none; border-style: outset; border-radius: 10px;
padding: 0.5%; margin: 1%;">CSSF Naming convention</span>]</span>

Communications EN

2026-04-17T14:04:30Z

Cso:

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

The latest product-related communications are available in the table below.<br>

<div style="text-align: center;">
{| border="1" cellspacing="2" cellpadding="10"
|'''DATE'''
|'''SUBJECT'''
|'''REMARK'''
|-
|[https://www.e-file.lu/wiki/images/7/71/20260417_Important_Update_Upcoming_changes_to_the_CRS_reporting_to_Administration_des_Contributions_Directes.pdf 17/04/2026]
|Upcoming regulatory change affecting the CRS reporting to Administration des Contributions Directes (ACD)
|
|-
|[https://www.e-file.lu/wiki/images/2/29/20260206_Important_Update_Changes_to_your_National_Reporting_B2.4_transmission_method.pdf 06/02/2026]
|National Reporting B2.4. (participating interests and subordinated loans) reporting transmission migrated to S3 channel
|
|-
|[https://www.e-file.lu/wiki/images/4/4c/20260126_Important_Update_Changes_to_your_Institutions_for_Occupational_Retirement_Provision_%28IORP%29_transmission_method.pdf 26/01/2026]
|Institutions for Occupational Retirement Provision (IORP) reporting transmission migrated to S3 channel
|
|-
|[https://www.e-file.lu/wiki/images/d/dc/20260123_Regulatory_Update_Action_required_for_AnaCr%C3%A9dit_1.0.13_in_e-file.pdf 23/01/2026]
|Sending Service and Transmission module will be updated on 30 January 2026 to be compliant with AnaCrédit new version V1.0.13
|
|-
|[https://www.e-file.lu/wiki/images/5/56/20260116_Important_Update_Changes_to_your_connection_method_for_e-file_SSO_MFA.pdf 16/01/2026]
|Single Sign-On (SSO) and Multi-Factor Authentication (MFA) login method will be available on e-file from 23 January 2026
|
|-
|[https://www.e-file.lu/wiki/images/0/0e/20251205_Important_Information_Updates_to_fund_reporting_via_e-file_supporting_BCL_2024_245_%26_CSSF_24_866.pdf 05/12/2025]
|Go-Live timeline for upcoming changes to fund reporting requirements (circulars CSSF 24/866 and BCL 2024/245)
|
|-
|[https://www.e-file.lu/wiki/images/7/7c/20251204_Important_Information_Update_BCL_reports_in_UAT_S2.20.pdf 04/12/2025]
|Web form for S2.20 available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/d/df/20251127_Important_Update-_Updated_U11_web_form_in_UAT_for_CSSF_reports.pdf 27/11/2025]|| Updated U11 web form available in UAT for CSSF reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/b/b6/20251126_Important_Information_Update_BCL_reports_in_UAT.pdf 26/11/2025]|| Updated TPTOBS web form (L3) available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/c/c8/20251119_Important_Update_BCL_reports_in_UAT.pdf 19/11/2025]|| Updated S1.3 (L4) S1.6 (L2), S2.13 web form (L2) available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/c/c3/20251114_Important_Update_BCL_reports_in_UAT.pdf 14/11/2025]|| Sending Service and Transmission module available in UAT for TPTOBS (L3), S1.3(L4), S2.13(L2), S1.6(L2), U11
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/a/a1/20251110_Important_Update_S404_report_available_in_UAT.pdf 10/11/2025]|| Web form for S4.04 available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/d/d7/20251027_Important_Update_Changes_to_fund_reporting_via_e-file_supporting_BCL_2024_245_%26_CSSF_24_866_Oct2025.pdf 27/10/2025]|| Changes to fund reporting via e-file supporting BCL 2024/245 & CSSF 24/866 (Updates timeline 2)
|
|-
| [https://www.e-file.lu/wiki/images/8/84/20250915_Important_Update_Changes_to_fund_reporting_via_e-file_supporting_BCL_2024245_%26_CSSF_24866_Sept2025.pdf 15/09/2025]|| Changes to fund reporting via e-file supporting BCL 2024245 & CSSF 24866 (Updates timeline)
|
|-
| [https://www.e-file.lu/wiki/images/e/e4/20250901_Upcoming_AnaCr%C3%A9dit_reporting_update_effective_1_October_2025.pdf 15/09/2025]||Updates on Transmission module and Sending Service for AnaCrédit V1.0.12 from 1 October 2025
|
|-
| [https://www.e-file.lu/wiki/images/8/8f/20250804_-AHA-_FSQ_S3_MMF_migration_to_S3.pdf 04/08/2025]||Money Market Funds Reporting (MMF) reporting transmission migrated to S3 from 1 September 2025
|
|-
| [https://www.e-file.lu/wiki/images/7/70/20250725_Important_update_changes_to_your_CSDR_transmission_method.pdf 25/07/2025]||Sending Service no longer required when using the e-file Document Library and scheduled automation for KID documents transmission
|
|-
| [https://www.e-file.lu/wiki/images/0/07/20250711_Important_update_changes_to_your_CSDR_transmission_method.pdf 01/07/2025]||CSDR Article 9 reporting transmission migrated to S3 channel
|
|-
| [https://www.e-file.lu/wiki/images/4/49/20250619_Upcoming_changes_to_the_Key_Information_Document.pdf 19/06/2025]||New delegation system implemented on e-file for the Key Information Document (KIDs) submissions
|
|-
| [https://www.e-file.lu/wiki/images/4/4a/20250616_Important_Update_%E2%80%93_CSSF_Prospectus_Transmission_through_e-file.pdf 16/06/2025]||New web form available to enable Prospectus filing
|
|-
| [https://www.e-file.lu/wiki/images/c/cc/20250523_S3_KID_Delegation_System_Updated_by_CSSF.pdf 23/05/2025]||New delegation system for the Key Information Document (KIDs) submissions will be effective from 26 June 2025
|
|-
| [https://www.e-file.lu/wiki/images/4/41/20250415_Important_CSSF_Update_e-file_Prospectus_Transmission.pdf 15/04/2025]||Implementation plan of CSSF Prospectus Transmission
|
|-
| [https://www.e-file.lu/wiki/images/c/ca/20250401_Important_update_upcoming_changes_to_your_quarterly_and_annual_COREP_FINREP_transmission_method.pdf 01/04/2025]||COREP/FINREP reporting transmission migrated to S3 from 1 April 2025 (reminder)
|
|-
| [https://www.e-file.lu/wiki/images/6/65/20250328_Important_Update_CSSF_Prospectus_Change_for_Product_1.1%2C_1.2_%26_1.5.pdf 28/03/2025]||Important change in the CSSF prospectus transmission workflow
|
|-
| [https://www.e-file.lu/wiki/images/7/74/20250325_Important_Update_Upcoming_changes_to_the_electronic_VISA_procedure_for_UCITS%2C_Part_II_UCIs%2C_SICARs_and_SIFs_Prospectuses.pdf 25/03/2025]||The CSSF CSSF published the technical guidelines for the e-Identification system for prospectus filing
|
|-
| [https://www.e-file.lu/wiki/images/9/91/20250314_Important_update_upcoming_changes_to_the_electronic_VISA_procedure_for_UCITS%2C_Part_II_UCIs%2C_SICARs_and_SIFs_Prospectuses.pdf 14/03/2025]||The CSSF announced the new e-Identification system for prospectus filing
|
|-
| [https://www.e-file.lu/wiki/images/b/b4/20250307_Important_Information_%E2%80%93_Fundsquare_e-file_Enhancement_for_UCITS_filings.pdf 07/03/2025]||Enhancement for UCITS filings with automatic generation of notification letters for ‘light’ filings
|
|-
| [https://www.e-file.lu/wiki/images/1/12/20250305_Covered_Investment_claims_%28SIIL%29_transmission_method_has_changed.pdf 05/03/2025]||Covered Investment claims (SIIL) reporting transmission migrated to S3 channel
|
|-
| [https://www.e-file.lu/wiki/images/c/c3/20250221_Final_reminder_your_U1.1._Report_transmission_method_is_about_to_expire.pdf 21/02/2025]||U11 reporting transmission migrated to S3 channel (final reminder)
|
|-
| [https://www.e-file.lu/wiki/images/e/e8/20250206_Changes_to_quarterly_and_annual_COREP_FINREP_transmission_method.pdf 06/02/2025]||COREP/FINREP reporting transmission migrated to S3 from 1 April 2025
|
|-
| [https://www.e-file.lu/wiki/images/b/bb/20250205_Your_U.1.1._Report_transmission_method_is_about_to_expire.pdf 05/02/2025]||U11 reporting transmission migrated to S3 channel (reminder)
|
|-
| [https://www.e-file.lu/wiki/images/b/b1/20241121_KID_and_official_documents_-_Delegating_to_a_Third-Party_professional.pdf 21/11/2024]||KID and MR/AI transmission migrated to S3 (reminder)
|
|-
|[https://www.e-file.lu/wiki/images/a/a9/20241107_Important_reminder_your_U1.1_Report_transmission_method_is_about_to_change.pdf 07/11/2024]
|U11 reporting transmission migrated to S3 channel (reminder)
|
|-
|[https://www.e-file.lu/wiki/images/d/d3/20241106_Important_reminder_your_U1.1_Report_transmission_method_is_about_to_change.pdf 06/11/2024]
|KID and MR/AI transmission migrated to S3 (reminder)
|
|-
|[https://www.e-file.lu/wiki/images/6/66/20241028_Important_reminder_your_KIDs_and_official_documents_%28MR_AI%29_transmission_method_is_about_to_change.pdf 28/10/2024]
|Key Information Documents (KID) and Management Regulations or Articles of Incorporation documents (MR/AI)
transmission migrated to S3
|
|-

|}
</div>

[[Category: FAQ e-file]]

Communications EN

2026-04-17T10:01:05Z

Cso:

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

The latest product-related communications are available in the table below.<br>

<div style="text-align: center;">
{| border="1" cellspacing="2" cellpadding="10"
|'''DATE'''
|'''SUBJECT'''
|'''REMARK'''
|-
|[https://www.e-file.lu/wiki/images/7/71/20260417_Important_Update_Upcoming_changes_to_the_CRS_reporting_to_Administration_des_Contributions_Directes.pdf 17/04/2026]
|Uupcoming regulatory change affecting the CRS reporting to Administration des Contributions Directes (ACD)
|
|-
|[https://www.e-file.lu/wiki/images/2/29/20260206_Important_Update_Changes_to_your_National_Reporting_B2.4_transmission_method.pdf 06/02/2026]
|National Reporting B2.4. (participating interests and subordinated loans) reporting transmission migrated to S3 channel
|
|-
|[https://www.e-file.lu/wiki/images/4/4c/20260126_Important_Update_Changes_to_your_Institutions_for_Occupational_Retirement_Provision_%28IORP%29_transmission_method.pdf 26/01/2026]
|Institutions for Occupational Retirement Provision (IORP) reporting transmission migrated to S3 channel
|
|-
|[https://www.e-file.lu/wiki/images/d/dc/20260123_Regulatory_Update_Action_required_for_AnaCr%C3%A9dit_1.0.13_in_e-file.pdf 23/01/2026]
|Sending Service and Transmission module will be updated on 30 January 2026 to be compliant with AnaCrédit new version V1.0.13
|
|-
|[https://www.e-file.lu/wiki/images/5/56/20260116_Important_Update_Changes_to_your_connection_method_for_e-file_SSO_MFA.pdf 16/01/2026]
|Single Sign-On (SSO) and Multi-Factor Authentication (MFA) login method will be available on e-file from 23 January 2026
|
|-
|[https://www.e-file.lu/wiki/images/0/0e/20251205_Important_Information_Updates_to_fund_reporting_via_e-file_supporting_BCL_2024_245_%26_CSSF_24_866.pdf 05/12/2025]
|Go-Live timeline for upcoming changes to fund reporting requirements (circulars CSSF 24/866 and BCL 2024/245)
|
|-
|[https://www.e-file.lu/wiki/images/7/7c/20251204_Important_Information_Update_BCL_reports_in_UAT_S2.20.pdf 04/12/2025]
|Web form for S2.20 available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/d/df/20251127_Important_Update-_Updated_U11_web_form_in_UAT_for_CSSF_reports.pdf 27/11/2025]|| Updated U11 web form available in UAT for CSSF reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/b/b6/20251126_Important_Information_Update_BCL_reports_in_UAT.pdf 26/11/2025]|| Updated TPTOBS web form (L3) available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/c/c8/20251119_Important_Update_BCL_reports_in_UAT.pdf 19/11/2025]|| Updated S1.3 (L4) S1.6 (L2), S2.13 web form (L2) available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/c/c3/20251114_Important_Update_BCL_reports_in_UAT.pdf 14/11/2025]|| Sending Service and Transmission module available in UAT for TPTOBS (L3), S1.3(L4), S2.13(L2), S1.6(L2), U11
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/a/a1/20251110_Important_Update_S404_report_available_in_UAT.pdf 10/11/2025]|| Web form for S4.04 available in UAT for BCL reports
|Only UAT
|-
| [https://www.e-file.lu/wiki/images/d/d7/20251027_Important_Update_Changes_to_fund_reporting_via_e-file_supporting_BCL_2024_245_%26_CSSF_24_866_Oct2025.pdf 27/10/2025]|| Changes to fund reporting via e-file supporting BCL 2024/245 & CSSF 24/866 (Updates timeline 2)
|
|-
| [https://www.e-file.lu/wiki/images/8/84/20250915_Important_Update_Changes_to_fund_reporting_via_e-file_supporting_BCL_2024245_%26_CSSF_24866_Sept2025.pdf 15/09/2025]|| Changes to fund reporting via e-file supporting BCL 2024245 & CSSF 24866 (Updates timeline)
|
|-
| [https://www.e-file.lu/wiki/images/e/e4/20250901_Upcoming_AnaCr%C3%A9dit_reporting_update_effective_1_October_2025.pdf 15/09/2025]||Updates on Transmission module and Sending Service for AnaCrédit V1.0.12 from 1 October 2025
|
|-
| [https://www.e-file.lu/wiki/images/8/8f/20250804_-AHA-_FSQ_S3_MMF_migration_to_S3.pdf 04/08/2025]||Money Market Funds Reporting (MMF) reporting transmission migrated to S3 from 1 September 2025
|
|-
| [https://www.e-file.lu/wiki/images/7/70/20250725_Important_update_changes_to_your_CSDR_transmission_method.pdf 25/07/2025]||Sending Service no longer required when using the e-file Document Library and scheduled automation for KID documents transmission
|
|-
| [https://www.e-file.lu/wiki/images/0/07/20250711_Important_update_changes_to_your_CSDR_transmission_method.pdf 01/07/2025]||CSDR Article 9 reporting transmission migrated to S3 channel
|
|-
| [https://www.e-file.lu/wiki/images/4/49/20250619_Upcoming_changes_to_the_Key_Information_Document.pdf 19/06/2025]||New delegation system implemented on e-file for the Key Information Document (KIDs) submissions
|
|-
| [https://www.e-file.lu/wiki/images/4/4a/20250616_Important_Update_%E2%80%93_CSSF_Prospectus_Transmission_through_e-file.pdf 16/06/2025]||New web form available to enable Prospectus filing
|
|-
| [https://www.e-file.lu/wiki/images/c/cc/20250523_S3_KID_Delegation_System_Updated_by_CSSF.pdf 23/05/2025]||New delegation system for the Key Information Document (KIDs) submissions will be effective from 26 June 2025
|
|-
| [https://www.e-file.lu/wiki/images/4/41/20250415_Important_CSSF_Update_e-file_Prospectus_Transmission.pdf 15/04/2025]||Implementation plan of CSSF Prospectus Transmission
|
|-
| [https://www.e-file.lu/wiki/images/c/ca/20250401_Important_update_upcoming_changes_to_your_quarterly_and_annual_COREP_FINREP_transmission_method.pdf 01/04/2025]||COREP/FINREP reporting transmission migrated to S3 from 1 April 2025 (reminder)
|
|-
| [https://www.e-file.lu/wiki/images/6/65/20250328_Important_Update_CSSF_Prospectus_Change_for_Product_1.1%2C_1.2_%26_1.5.pdf 28/03/2025]||Important change in the CSSF prospectus transmission workflow
|
|-
| [https://www.e-file.lu/wiki/images/7/74/20250325_Important_Update_Upcoming_changes_to_the_electronic_VISA_procedure_for_UCITS%2C_Part_II_UCIs%2C_SICARs_and_SIFs_Prospectuses.pdf 25/03/2025]||The CSSF CSSF published the technical guidelines for the e-Identification system for prospectus filing
|
|-
| [https://www.e-file.lu/wiki/images/9/91/20250314_Important_update_upcoming_changes_to_the_electronic_VISA_procedure_for_UCITS%2C_Part_II_UCIs%2C_SICARs_and_SIFs_Prospectuses.pdf 14/03/2025]||The CSSF announced the new e-Identification system for prospectus filing
|
|-
| [https://www.e-file.lu/wiki/images/b/b4/20250307_Important_Information_%E2%80%93_Fundsquare_e-file_Enhancement_for_UCITS_filings.pdf 07/03/2025]||Enhancement for UCITS filings with automatic generation of notification letters for ‘light’ filings
|
|-
| [https://www.e-file.lu/wiki/images/1/12/20250305_Covered_Investment_claims_%28SIIL%29_transmission_method_has_changed.pdf 05/03/2025]||Covered Investment claims (SIIL) reporting transmission migrated to S3 channel
|
|-
| [https://www.e-file.lu/wiki/images/c/c3/20250221_Final_reminder_your_U1.1._Report_transmission_method_is_about_to_expire.pdf 21/02/2025]||U11 reporting transmission migrated to S3 channel (final reminder)
|
|-
| [https://www.e-file.lu/wiki/images/e/e8/20250206_Changes_to_quarterly_and_annual_COREP_FINREP_transmission_method.pdf 06/02/2025]||COREP/FINREP reporting transmission migrated to S3 from 1 April 2025
|
|-
| [https://www.e-file.lu/wiki/images/b/bb/20250205_Your_U.1.1._Report_transmission_method_is_about_to_expire.pdf 05/02/2025]||U11 reporting transmission migrated to S3 channel (reminder)
|
|-
| [https://www.e-file.lu/wiki/images/b/b1/20241121_KID_and_official_documents_-_Delegating_to_a_Third-Party_professional.pdf 21/11/2024]||KID and MR/AI transmission migrated to S3 (reminder)
|
|-
|[https://www.e-file.lu/wiki/images/a/a9/20241107_Important_reminder_your_U1.1_Report_transmission_method_is_about_to_change.pdf 07/11/2024]
|U11 reporting transmission migrated to S3 channel (reminder)
|
|-
|[https://www.e-file.lu/wiki/images/d/d3/20241106_Important_reminder_your_U1.1_Report_transmission_method_is_about_to_change.pdf 06/11/2024]
|KID and MR/AI transmission migrated to S3 (reminder)
|
|-
|[https://www.e-file.lu/wiki/images/6/66/20241028_Important_reminder_your_KIDs_and_official_documents_%28MR_AI%29_transmission_method_is_about_to_change.pdf 28/10/2024]
|Key Information Documents (KID) and Management Regulations or Articles of Incorporation documents (MR/AI)
transmission migrated to S3
|
|-

|}
</div>

[[Category: FAQ e-file]]

File:20260417 Important Update Upcoming changes to the CRS reporting to Administration des Contributions Directes.pdf

2026-04-17T09:59:15Z

Cso: An upcoming regulatory change affecting the Common Reporting Standard (CRS) reporting to Administration des Contributions Directes (ACD) in Luxembourg. The new CRS reporting format will apply from January 2027 for the 2026 reporting period.

== Summary ==
An upcoming regulatory change affecting the Common Reporting Standard (CRS) reporting to Administration des Contributions Directes (ACD) in Luxembourg. The new CRS reporting format will apply from January 2027 for the 2026 reporting period.

E-file Administration

2026-04-16T13:16:31Z

Cso: /* Correspondance table */

__NOTOC__
= e-file FAQ - Administrator's section =
<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

[[File:Administration module icon (Figure 2).png|300px]]

== Knowing the interface ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_am_I_allowed_to_do_as_an_administrator></span>
<div style="font-weight:bold;line-height:2.5;">What am I allowed to do as an administrator ?</div>
<div class="mw-collapsible-content">

The '''Administration module''' opens. Tabs are available in the '''e-file administrator''' module: (Figure 3).

[[File:Users, Groups and Certificates (Figure 3).png|900px]]

{|
|+
!'''Users tab'''
!'''Groups tab'''
!'''Certificates tab'''
!'''Sending service tab'''
!'''S3 keys tab'''
|-
|
*[[#How_can_I_create_a_new_e-file_user|Create a new user]]

*[[#Managing_permission_on_user's_account|Assign groups to a user]]

*[[#Explore_the_interface's_items|Force password change]]

*[[#Explore_the_interface's_items|Lock/ unlock user]]

*[[#Explore_the_interface's_items|Delete user]]
|
*[[#Groups'_management|User management at group level]]

* Add users to a group

* Assign a group to users

* Manage user profiles at group level
|
* [[#How_do_I_order_a_LUXTRUST_certificate|Order a new '''Luxtrust certificate''']]

* [[#How_do_I_order_a_LUXTRUST_certificate|Renew your Luxtrust certificate]]

* [[#How_do_I_activate_my_LUXTRUST_certificate_into_e-file|Activate Luxtrust certificate]]
|
:''Sending service user's management :''

* [[#What_about_the_Sending_Service_account|Assign groups to the '''Sending Service user''']]

* [[#What_about_the_Sending_Service_account|Subscribe the Sending Service user to '''alerts''']]
:''Sending service user's management - V2 :''
* [[Sending_Service_java-less_version|Sending service java-less version]]
|
* [[#S3_system|'''S3''' key management]]
|}
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Explore_the_interface's_items></span>
<div style="font-weight:bold;line-height:2.5;">Explore the interface's items</div>
<div class="mw-collapsible-content">

:<u>'''Explanations'''</u>

<imagemap>
File:AdminInterface.png|center|1200px|alt=clickable image : admin interface
rect 83 11 944 69 [[#hereExplainAction| This is the tabs' menu ]]
rect 1812 154 1686 93 [[#hereExplainAction| Click to create a new user's account ]]
rect 237 234 28 168 [[#hereExplainAction| The vertical menu can be reduce ]]
rect 238 281 31 239 [[#hereExplainAction| Here you can set who will receive some e-mail notifications in relation with the administration ]]
rect 256 186 1286 232 [[#hereExplainAction| You can filter the list on a group's members or a profile]]
rect 406 345 450 375 [[#hereExplainAction| The crown indicates an administrator]]
rect 793 285 878 300 [[#hereExplainAction| By hovering over their headers, text columns can be sorted]]
rect 1618 281 1748 332 [[#hereExplainAction| Each line allow its actions among : * Edit, * Force password, * Lock/Unlock, * Delete]]
rect 1618 337 1647 369 [[#hereExplainAction| Edit the user details or group permissions]]
rect 1652 337 1681 369 [[#hereExplainAction| Force password change : an email is sent to the user for him to reset]]
rect 1687 337 1711 369 [[#hereExplainAction| Lock or Unlock the account. The icon is greyed out for new users.]]
rect 1716 337 1743 369 [[#hereExplainAction| Delete the account. You can not delete administrators, ask us.]]
desc none
</imagemap>
</div>
</div>

== Accounts' management ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How many users can I create ?</div>
<div class="mw-collapsible-content">
:You can create as many as users' accounts you need. It is free of charge.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_create_a_new_e-file_user></span>
<div style="font-weight:bold;line-height:2.5;">How can I create a new e-file user ?</div>
<div class="mw-collapsible-content">

:Enter the administration module [[File:SDjl_8.png|150px]], you should be on the 'users' tab.
:Click the '''Create a user''' button [[File:Create_a_user_button_(Figure_5).png|150px]]

:The '''Create a user''' window pops up. Complete the form as shown in the figure below and click the '''Create''' button.

<imagemap>
File:4CreateUser.png|center|900px|alt=clickable image : create user form
rect 1081 737 41 282 [[#hereCreatUser|All fields are mandatory]]
rect 991 835 42 770 [[#hereCreatUser|You must choose a first group and a user's profile ]]
rect 475 856 637 914 [[#hereCreatUser|Click here to validate]]
rect 1363 993 1216 939 [[#hereCreatUser|Click here to cancel]]
circle 1355 58 34 [[#hereCreatUser|Click here to cancel]]
desc none
</imagemap>

:<span style="color: #C00000">'''Important note : You do not have to create a password for the user, an automatic mail will be sent to the new user to activate his account and create a password</span>'''

:The '''Create a user''' window closes and you return automatically to the '''Users List''' screen.

:At the same time a '''confirmation''' window pops up on the top of the screen indicating that the user creation was successful.

:[[File:User creation was successful (Figure 7).png|800px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_an_existing_account's_e-mail></span>
<div style="font-weight:bold;line-height:2.5;">How can I change an existing account's e-mail ?</div>
<div class="mw-collapsible-content">

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon.

[[File:SDjl_8.png|300px]]

<u>'''Step 2</u>:'''

The '''Users List''' screen opens. Click the Edit button on the line of the account to be changed.

[[File:AdminModuleChangeEmail.png|border]]

<u>'''Step 3</u>:'''
Click the detail tab, then Edit button

[[File:AdminModuleChangeEmail2.png|border|400px]]

<u>'''Step 4</u>:'''
Change the e-mail then click Validate button

[[File:AdminModuleChangeEmail3.png|border|400px]]
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_about_the_Sending_Service_account></span>
<div style="font-weight:bold;line-height:2.5;">What about the Sending Service account ?</div>
<div class="mw-collapsible-content">

As an administrator, you can manage the permission for the sending service account too.
See more information upon the [[Sending_Service_home|sending service]]

<imagemap>
File:SDPermission.png|center|800px|alt=clickable image on SD permission
rect 385 1 615 68 [[#hereSDPerm| Click the sending service tab ]]
rect 7 172 192 211 [[#hereSDPerm| In the vertical menu, choose the proper version of your sending service ]]
rect 1370 310 1421 374 [[#hereSDPerm| On the matching line, click the edit icon ]]
rect 1378 442 1473 384 [[#hereSDPerm| A panel opens from the right, click the edit button ]]
rect 248 545 1231 778 [[#hereSDPerm| You can add or delete a group, the profile is always 'Service Déposant', subscribe to receive the authorities' feedbacks. ]]
desc none
</imagemap>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Managing_permission_on_user's_account></span>
<div style="font-weight:bold;line-height:2.5;">Managing permission on user's account </div>
<div class="mw-collapsible-content">

See: [[#How_do_I_assign_groups_and_profiles_to_users|How do I assign groups and profiles to users ?]]
</div>
</div>

== Groups' management ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_an_e-file_group></span>
<div style="font-weight:bold;line-height:2.5;">What is an e-file group ?</div>
<div class="mw-collapsible-content">

In e-file, a group allows you to manage permissions for similar reports in terms of type, circulars, costs or technical constraints.

Instead of managing groups for a user, the '''Groups''' tab allows you to manage users for a given group.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Which_group_do_I_need></span>
<div style="font-weight:bold;line-height:2.5;">Which group do I need ?</div>
<div class="mw-collapsible-content">

<div style="height:500px; width:auto; overflow-y:scroll">

{| class="wikitable filterable mw-collapsible sortable"
|+ <span style="white-space:nowrap">Which group for my report ?</span>
|- <div style="font-weight:bold; vertical-align:top; position:sticky;top:-1px;z-index:10">
! style= "background-color:#52BBBD; color:#FFF" | Concerned companies
! style= "background-color:#52BBBD; color:#FFF" | Report<br /> naming convention
! style= "background-color:#52BBBD; color:#FFF" | Details
! style= "background-color:#52BBBD; color:#FFF" | Authority
! style= "background-color:#FF7F27; color:#FFF" | e-file Group
! style= "background-color:#52BBBD; color:#FFF" | Sending way

</div>

|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| NOTREP
| Notification procedures to be followed by a UCITS governed by Luxembourg law wishing to market its units in another Member State of the European Union
| CSSF
| (-) Gestion documentaire<br /> (-) Dashboard<br /> (-) Matrice d'enregistrement et de distribution
| S3
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Monthly financial information for guaranteed funds
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| -
| Yearly financial information
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| -
| Interventions on the futures and options markets
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0103
| Monthly statistical balance sheet for money market funds (MMF)
| BCL
| Station Finesti
| KS
|-
|Investment Funds
|S0404
|Country of Marketing
|BCL
|Station Finesti
|KS
|-
|Investment Funds
|S0220
|Quarterly Financial Information
|BCL
|Station Finesti
|KS
|- style="vertical-align:bottom;"
| Investment Funds
| TPTOBS
| Monthly Security by security reporting for investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| SIF:<br /> (-) Prospectus (PC)<br /> (-) Offering document (DE)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| SIF Law 2007:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report SIF (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (PM)<br /> SICAR:<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Auditor report<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Management Companies
| DOCREP
| Auditor report<br /> (-) S: Investment fund manager (IFM)<br /> (-) A: Investment fund manager (IFM)<br /> <br /> Report Hong Kong Securities and Futures (HK)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI:<br /> (-) Prospectus (PC)<br /> (-) Simplified prospectus (PS)<br /> (-) Letter of explanation (LE)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Alternative Investment Fund Managers (AIFM)
| AIF
| Alternative Investment Fund reporting (AIF Manager)
| CSSF
| (-) AIF<br /> (-) AMfine
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| ANTREF<br /> ANTT1M<br /> ANTT2M<br /> ANTT2Q
| AnaCredit:<br /> Collection of granular credit and credit risk data
| BCL
| Reporting Anacredit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0218-L
| Quarterly statistical balance sheet of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S0219-L
| Information on valuation effects on the balance sheet of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| S0403-L
| Annual Premiums, claims and commissions of insurance corporations – Luxembourg entity
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| TPTASS
| Monthly Security by security reporting of insurance corporations
| BCL
| Reporting BCL pour les assurances
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SHSGRP
| «SHS-Group» report:<br /> Statistics on holdings of securities by reporting banking groups
| BCL
| SHS reporting
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0001
| Daily deposit
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0101
| Monthly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0104
| Adjustments due to valuation effects|
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0105
| Information on interest rates in EUR
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0108
| Information on securititation<br /> transactions launched<br /> by credit institutions
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0109
| Information on CNY (renmibi) operations
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0205-L
| Quarterly statistical balance sheet
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0205-N
| Quarterly statistical balance sheet<br /> of credit institutions -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0208
| Real estate loans for<br /> Lxuembourg buildings
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0209-L
| Staff report -<br /> Luxembourg entity
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| S0209-N
| Staff report -<br /> Luxembourg entity and its branches
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0302
| Non balance sheet information
| BCL
| Statistiques BCL
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| COFREP
| (-) SMRTLA (EBA V3.0 module mrel_tlac_ind)<br /> (-) CMRTLA (EBA V3.0 module mrel_tlac_con)<br /> (-) MRTLAX (EBA V3.2 module mrel_tlac)<br /> (-) CRESOL until V3.1 (EBA – data : RESOL_CON)<br /> (-) SRESOL until V3.1 (EBA – data : RESOL_IND)<br /> (-) RESOLX from V3.2 (EBA – data : RESOL_CON and <br /> RESOL_IND)<br /> (-) CFRXXX based <br /> on EBA V3.2 (data : cfr)<br /> (-) CIRXXX defined based on <br /> EBA V3.2 (data : cir)<br /> (-) FMIRXX based <br /> on EBA V3.2 (data : fmir)<br /> (-) LDRXXX based <br /> on EBA V3.2 (data : ldr)
| CSSF
| Rapport COREP
| KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit Report on AML/CTF
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Circ. 18/697 annexe1
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Annual Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Annual report consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| AC Member List
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Compliance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Governance Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| DOCREP
| Internal Audit Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| ICAAP
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ICAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| ILAAP Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Long Form Branch or Specific Participation
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Long Form Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Reconciliation LuxGAAP FINREP
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|-
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Management Letter Consolidated
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Audit report on rules of conduct
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Management Letter
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Head quarter annual report
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Risk Control Report
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Report on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Recovery Plan
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Results Distribution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| DOCREP
| Single Customer View
| CSSF
| Reporting des établissements de crédit
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DOCREP
| Table on out-of-court complaint resolution
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Reporting des établissements de crédit
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Financial Institutions - Common Reporting Standard (CRS)
| CRS
| Automatic exchange of<br /> financial account information<br /> on a global level
| ACD
| Reporting CRS
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Quarterly reporting on the<br /> financial health of the branches<br /> parent entities
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Residential credit deposits
| CSSF
| Enquêtes
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Credit Institutions
| style="vertical-align:bottom;" | DCOR
| style="vertical-align:bottom;" | Reporting Entity<br /> B: Credit institution
| style="vertical-align:bottom;" | CSSF
| Enquetes
| style="vertical-align:bottom;" | S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DCOR
| Reporting Entity<br /> P: PFS
| CSSF
| Enquetes
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ESPREP
| Residential real estate market
| CSSF
| Enquêtes
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Stress test in order to assess<br /> the interest rate risk<br /> arising from non-trading<br /> book activities
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0101
| Customer transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0110
| Stock taking of payment accounts in bank money
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01100
| Payment services provided by e-money institutions and payment institutions without the provision of payment accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0111
| OTC cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01110
| Payment initiation services (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01110-F
| Payment initiation services (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0112
| Transactions via telecommunication, digital or IT device
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0113
| Credits to the accounts by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0114
| Debits from the account by simple book entry
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0102
| Interbank transfers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0120
| Customer Credit transfers sent (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0120-F
| Customer Credit transfers sent (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01200
| Stock of issued payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01201
| Stock of distributed payment cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0121
| Customer credit transfers received
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01210
| Stock of terminals by terminal type
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01220
| Stock of accounts (except e-money accounts)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01221
| Stock of e-money accounts
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01222
| Stock of accessed accounts - account information services (AIS)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V01230
| Number of customers
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0103
| Domiciliations
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130
| Direct debits - reporting as creditor's PSP (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V01300-F
| Losses due to fraud per liability bearer
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0130-F
| Direct debits - reporting as creditor's PSP (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0131
| Direct debits - reporting as debtor's PSP
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0104
| Inventory cards / terminals
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0140
| SEPA R-transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0141
| Interbank payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0142
| Intermediated payment transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0105
| Card transactiosn (Issuing part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0150
| Card transactions with cards issued by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0150-F
| Card transactions with cards issued by resident PSPs (fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0151
| Electronic card transactions with cards issued by resident PSPs, split by Merchant Category Codes (MCC)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0152
| Card transactions acquired by resident PSPs (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0152F
| Card transactions acquired by resident PSPs (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0153
| Fundings and withdrawals related to prepaid cards
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0106
| Card transactiosn (Acquiring part)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0160
| Cheques and money remittances (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0160-F
| Cheques and money remittances (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0107
| Cheques and money orders
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0170
| Over-the-counter (OTC) cash transactions
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0108
| Electronic money scheme
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0180
| Book entries
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0109
| Card based e-money schemes
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0190
| Fundings and withdrawals in e-money (except prepaid cards)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Payment Institutions/Electronic Money Institutions
| V0191
| E-money transfers (payments)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions/Electronic Money Institutions
| V0191-F
| E-money transfers (Fraud)
| BCL
| Collecte des données de paiement (CDP)
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| ESPREP
| Fonds de garantie<br /> des dépôts Luxembourg<br /> (FGDL)
| CSSF
| Enquête
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Identification of third-party<br /> funds held and incorporated in the balance sheet
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Payment Institutions
| EDPREP
| Capital adequacy of<br /> payment institutions
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom;"
| Payment Institutions
| EDPREP
| Profit and loss accoount
| CSSF
| Reporting EDP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Identification of third-party<br /> funds held and incorporated<br /> in the balance sheet
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Statement of<br /> authorised reinvestments
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Capital adequacy of<br /> electronic money institutions
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Electronic Money Institutions
| EMEREP
| Profit and loss account
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom;"
| Electronic Money Institutions
| EMEREP
| Analysis of shareholdings
| CSSF
| Reporting EME
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Institutions - Foreign Account Tax Compliance Act (FATCA)
| FATCA
| Foreign Account Tax Compliance Act Reporting
| ACD
| Groupe FATCA
| KS
|-
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| (-) Letter of explanation (LE)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Annual report of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Credit Institutions
| FRCREP
| Information on participating interest<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| FRCREP
| Information on staff costs and taxes<br /> and subordinated loans
| CSSF
| Rapport FINREP
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| LCRDAX
| CSSF
| Rapport FINREP
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Financial Companies
| S0216
| Quarterly statistical balance of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| S0217
| Transactions of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Key Investor Information Document<br /> (-) O: OPC Law 2010 and Loi 2007<br /> (-) K: SICAR<br /> (-) V: non-reglem.
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Long Form reports (UCI Law 2010)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| SGOREP
| (-) SG 1A: Financial situation<br /> (-) SG 1B: Profit and loss account<br /> (-) SG 1C: Table relating to other activities<br /> (-) SG 2: Other activities<br /> (-) SG: Personnel Table relating to staff
| CSSF
| Rapport Société de Gestion
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007<br /> (-) K: SICAR
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Investment Funds
| DOCREP
| Articles of Incorporation of UCITS<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| Management Regulations of UCITS<br /> (-) O: OPC Law 2010<br /> (-) O: Law 2007
| CSSF
| Doc OPC et FIS (circ. CSSF)
| S3
|- style="vertical-align:bottom;"
| MiFID II / MiFIR
| TAFREP
| Article 26 of Regulation<br /> No 600/2014:<br /> Obligation to report transactions<br /> (Markets in financial instruments => MiFIR)
| CSSF
| Report TAF-MIFID
| KS
|- style="background-color:#CAEDFB;"
| style="vertical-align:bottom;" | Management Companies
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)<br />
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom;"
| Other reporting CSSF BCL
| OTHREP
| Other reporting
| CSSF
| Reporting OTHER (CSSF)
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| BOP101
| Balance of payments reporting
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BOP102
| Cross-border payments<br /> executed for the account<br /> of the resident counterparts
| BCL
| Balance des Paiements
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| PSFREP
| Reporting population:<br /> (-) Investment firms<br /> (-) Specialised PFS<br /> (-) Support PFS
| CSSF
| Rapport PSF
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| N01 (Comp); N02 (Comp); N03 (Comp);<br /> N04 (Comp); N05 (Réviseur); N06( Réviseur);<br /> N07 (Comp); N08 (Comp); N09 (Comp); N10 (Comp); N11 (Comp); N12 (Réviseur);<br /> N13<br /> (Comp);<br /> N14<br /> 'Comp)
| Rapports narratifs
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CSDREP
| Reporting CSDR:<br /> Introduction of quarterly internalised settlement reporting requirements<br /> pursuant to Article 9(1) of EU Regulation No 909/2014 (CSDR)
| CSSF
| Reporting CSDR-9
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| BNNNN
| List of head offices, agencies,<br /> branches and representative offices
| CSSF
| Reporting EDIFACT
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Institutions for Occupational Retirement Provision
| SUFREP
| Annual and quarterly reporting according to Circular CSSF 19/726 of 26 July 2019
| CSSF
| Reporting IORP
| KS
|- style="vertical-align:bottom;"
| Money Market Funds (MMF)
| MMFREP
| • According to Article 37 of Regulation (EU) 2017/1131, the manager of a MMF must report information to the competent authority (CSSF) of the MMF, at least on a quarterly basis or - for MMF with assets under management of less than Eur 100 million - on at least an annual basis.<br /> • The first quarterly report should be sent to the competent authority of the MMF no later than 30 days after the end of Q1 2020.
| CSSF
| Money market fund reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| S0112-L
| Indirect withdrawal and remittance of banknotes denominated in EUR through an intermediary
| BCL
| Reporting S1.12
| KS
|- style="vertical-align:bottom;"
| Financial Companies
| TPTIBS
| Monthly security by security reporting of Financial Companies
| BCL
| Reporting des sociétés émettrices
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| U11
| Monthly financial information UCITS and UCI
| CSSF
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBBL
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBBN
| Security by security report–<br /> Balance sheet data–<br /> Luxembourg
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Credit Institutions
| TPTBHN
| Security by security report–<br /> Off-balance sheet data–<br /> Non-resident
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| TPTBHR
| Security by security report–<br /> Off-balance sheet data–<br /> Resident customers
| BCL
| Titre par Titre Bancaire
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| SFDR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR<br /> (-) F: Pension Fund
| CSSF
| SFDR reporting
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| SIC
| Financial information to be submitted by investment companies in risk capital (SICARs)
| CSSF
| Reporting SICAR
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| DOCREP
| UCI Law 2010:<br /> (-) Annual Report (AR)<br /> (-) Semi-annual report (SR)<br /> (-) Letter of explanation (LE)<br /> (-) Other periodic report (RO)<br /> (-) Movements in the securities portfolios (MP)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| S01; S02; S03; S04; S05;<br /> S06 (Réviseur); S07; S08;<br /> S09; S10; S11; S12; S13;<br /> S14; S15; S16; S17; S18;<br /> S19; S20; S23
| XBRL reports Solvency II
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| S0214
| Quarterly statistical balance
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Securitisation Vehicles
| S0215
| Transactions and write-offs/write-downs on securitised loans
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Securitisation Vehicles
| TPTTBS
| Security by security reporting
| BCL
| Véhicule titrisation
| KS
|- style="vertical-align:bottom;"
| Alternative Investment Fund Managers (AIFM)
| UCIAR
| Reporting Entity<br /> A: Alternative Investment fund manager (AIFM)
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| UCIAR
| Reporting Entity<br /> B: Credit institution
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| UCIAR
| Reporting Entity<br /> (-) O: UCI Law 2010<br /> (-) O: UCI Law 2007<br /> (-) K: SICAR
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| UCIAR
| Reporting Entity<br /> S: Management company
| CSSF
| (-) UCIAR reporting
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| UCIAR
| Reporting Entity<br /> (-) P: PFS<br /> (-) I: Support PFS
| CSSF
| (-) UCIAR reporting
| S3
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Other reporting CSSF BCL
| OTXREP
| Various correspondence
| BCL
| Reporting OTHER (BCL)
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM):<br /> (-) Risk management function(GR)<br /> (-) OPCVM instruments information (ID)<br /> (-) Compliance Function (FC)<br /> (-) Internal audit function report (IA)<br /> (-) Complaints handling (TP)<br /> (-) Authorized third party complaints (LP)<br /> (-) Risk Management Procedure (PG)<br /> (-) Organization chart (OG)<br /> (-) Mandates table (TM)<br /> (-) Delegates of RFI (RD)<br /> (-) Branch activity (AS)<br /> (-) Own funds ratio (FP)<br /> (-) Risk management procedure AIFM (PN)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| SPJ
| Notification and execution of court orders
| SPJ
| Perquisitions électroniques
| KS
|-
| style="vertical-align:bottom;" | Investment Funds
| style="vertical-align:bottom;" | DOCREP
| Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI)(FR)<br /> (-) Annual Report (AR)<br /> (-) Other periodic report (RO)
| style="vertical-align:bottom;" | CSSF
| style="vertical-align:bottom;" | Doc OPC et FIS (circ. CSSF)
| style="vertical-align:bottom;" | KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| CFEREP
| ALMXXX
| CSSF
| Rapport COREP
| S3
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Long Form Report
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Management Companies
| DOCREP
| Management letters of Investment fund managers (IFM) (EN)<br /> Gestionnaires des fonds d'investissement (GFI) (FR)
| CSSF
| Doc OPC et FIS (circ. CSSF)
| KS
|- style="vertical-align:bottom;"
| Professionals of the Financial Sector (PFS)
| DOCREP
| Management Letter
| CSSF
| Rapport des établissements de crédit
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Investment Funds
| S0106
| Monthly statistical balance sheet for non-money market funds (non-MMF)
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom;"
| Investment Funds
| S0213
| Quarterly statistical balance sheet for non-MMF investment funds
| BCL
| Station Finesti
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| CED
| Etat de situation relatif aux contrats en déshérence
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| CPR
| Compte rendu
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| ESP
| Enquête spécifique
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| ETR
| Etat trimestriel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| FIR
| Fiche de renseignement
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| PDA
| Rapport PDAL (Procédure de Dissolution Administrative sans Liquidation)
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RAC
| Rapport actuariel
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RDC
| Rapport distinct complémentaire du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RDI
| Rapport distinct du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RGO
| Rapport de gouvernance
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RLB
| Rapport LBCFT
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RRE
| Rapports sur le traitement des réclamations
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Insurance Corporations
| RSE
| Rapport distinct Solvabilité 2 de l'entreprise
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom;"
| Insurance Corporations
| RSO
| Rapport distinct Solvabilité 2 du réviseur
| CAA
| Reporting CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Credit Institutions
| ICS
| Yearly Survey on Covered Investment claims (SIIL)
| CSSF
| Enquête
| S3
|- style="vertical-align:bottom;"
| Insurance Corporations
| ROI<br /> DIN
| DORA Register of Information<br /> DORA Incident Reporting
| CAA
| Groupe CAA
| KS
|- style="vertical-align:bottom; background-color:#CAEDFB;"
| Professionals of the Financial Sector (PFS)
| DPAAIF
| self-assessment <br /> questionnaire PDAOFI
| CSSF
| PDAOFI reporting
| S3
|- style="vertical-align:bottom;"
| Credit Institutions
| CFEREP
| (-) ALM corep_alm_con.xsd<br /> corep_alm_ind.xsd corep_alm.xsd<br /> (-) LCRDA corep_lcr_da_con.xsd<br /> corep_lcr_da_ind.xsd corep_lcr_da.xsd<br /> (-) IRRBB irrbb.xsd
| CSSF
| Rapport COREP
| S3
|}

</div>
----------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<div style="font-weight:bold;line-height:2.5;">How can I get a missing group ?</div>
<div class="mw-collapsible-content">
If you think that the group you need is not available in your list, please [[How_to_contact_us|ask us]] to check and/or add it.
</div>
</div>
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_manage_users_at_group_level></span>
<div style="font-weight:bold;line-height:2.5;">How can I manage users at group level ?</div>
<div class="mw-collapsible-content">

Connect to [https://e-file.lu e-file.lu] with your '''e-file administrator''' login (adminXXX) and click the '''Administration module''' icon (Figure 21).

[[File:SDjl_8.png|400px]]

(Figure 21)

<u>'''Example'''</u>:

If you want to know the users to which the group '''Group FATCA''' has been assigned or if you want to add a new user to the group, please follow the instructions below.

<u>'''Step 1</u>:'''

Press the '''Groups''' button. The '''Groups list''' page opens. All groups assigned to your company are shown here (Figure 22).

[[File:3GroupList.png|800px]]

(Figure 22)

<u>'''Step 2</u>:'''

Click the '''Edit groups''' icon [[File:EditGroupSD.png|20px]] in order to view all the users assigned to '''Groupe FATCA''' group (Figure 23).

[[File:2EditGroup.png|800px]]

(Figure 23)

The '''Group detail''' page opens. Here you can find detailed information on the '''Group FATCA''' (e.g. Status date, number of inactive users, number of locked users) (Figure 24).

[[File:GroupDetailPage.png|500px]]

(Figure 24)

<u>'''Step 3</u>:'''

Press the '''Users''' button (Figure 25)

[[File:GroupDetailUsers.png|500px]]

(Figure 25)

The Group detail / Users page opens. All users assigned to the '''Group FATCA''' are listed here(Figure 26).

[[File:GroupUsrsList2.png|600px]]

(Figure 26)

<u>'''Step 4</u>:'''

Press the '''Edit Users''' button [[File:EditUserButton.png|100px]] (Figure 27)

[[File:EditUsersGroup.png|600px]]

(Figure 27)

The '''Users''' page opens in '''Edit mode''' (Figure 28)

[[File:UsersEditGroup.png|600px]]

(Figure 28)

The following actions can be done here:

1. '''ADD A USER'''. Select the user and his profile you want to add.

2. Change the '''Profile''' of the user

3. Delete the '''User'''

4. Once you have made your changes, press the VALDATE CHANGES button [[File:ValidateChanges.png|100px]]

The '''Users''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a confirmation window pops up on the top of the screen indicating that the assignment was successful (Figure 29).

[[File:AssignmentsSaved.png|800px]]

(Figure 29)
-------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_assign_groups_and_profiles_to_users></span>
<div style="font-weight:bold;line-height:2.5;">How do I assign groups and profiles to users ?</div>
<div class="mw-collapsible-content">

<u>Example</u>:

If a user has to send '''FATCA reportings''' to the authority, the e-file administrator must assign the <u>group</u> '''Rapport FATCA''' and the <u>profile</u> '''Manager''' to the user.

<u>'''Step 1</u>:'''

Open the '''User management''' screen in the '''Users''' tab and click the '''Edit''' [[File:EditGroupSD.png|20px]] icon of the user to whom you want assign [[E-file_Administration#Which_group_do_I_need|'''groups''']] and a specific [[E-file_Administration#User_profiles |'''profile''']] (Figure 11).

[[File:A specific profile (Figure 11).png|900px]]

(Figure 11)

<u>'''Step 2</u>:'''

The '''User details''' screen opens. Click the '''Groups''' button (Figure 12).

[[File:2AddGroup.png|500px]]

(Figure 12)

<u>'''Step 3</u>:'''
The '''User details / Groups''' screen opens. Click the '''Edit button''' (Figure 13).

[[File:2GroupDetails.png|500px]]

(Figure 13)

<u>'''Step 4</u>:'''

The '''User details / Groups''' screen opens in '''Edit''' mode (Figure 14).

Click the '''ADD A GROUP''' button [[File:AddGroup.png|100px]], select the [[E-file_Administration#Which_group_do_I_need|'''groups''']] and '''profile''' you want to assign and click the '''Validate''' button.

[[File:4Add group.png|800px]]

(Figure 14)

The '''User details / Groups''' window closes and you return automatically to the '''Groups List''' screen.

At the same time a '''confirmation''' window pops up on the top of the screen indicating that the group assignment was successfully saved (Figure 15).

[[File:AssignmentsSaved.png|800px]]

(Figure 15)

Please be informed that you can find detailed information on all groups on our Wikipage [[E-file_Administration#Which_group_do_I_need|''''e-file Administrator FAQ'''']]; column <u>e-file user account: "groupe"</u>.

=== User profiles ===

====Administrator (EN)/ Administrateur (FR)====

The Administrator profile allows the e-file administrator to order and activate LuxTrust certificate(s), manage user accounts, groups, user profiles, lock and un lock user account.

==== Guest (EN) */ Visiteur (FR) * ====

* The Guest can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Guest cannot submit reports or documents via e-file.

====Manager (EN)/ Responsable (FR)====

* The Manager can consult the information or documents of his affected group(s).<br>

* He can access the follow up tools and open the documents linked to the group(s).<br>

* The Manager can submit reports linked to his group(s) via e-file.

====Operator (EN) */ Opérateur (FR) * ====

* The Operator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* The Operator submit reports linked to his group(s) to validation by a Validator.

====Validator (EN) */ Valideur (FR) * ====

* The Validator can consult the information or documents of his affected group(s).

* He can access the follow up tools and open the documents linked to the group(s).

* He validates or rejects reports awaiting for validation linked to his group(s).

(*) Available depending the group
---------------
</div>
</div>

== Security's management ==

<span id=keystore_system></span>
=== * keystore system, Luxtrust certificate, SSL security ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_order_a_LUXTRUST_certificate></span>
<span id=LUXTRUST_certificate_purchase_order></span>
<div style="font-weight:bold;line-height:2.5;">How do I order a LUXTRUST certificate ?</div>
<div class="mw-collapsible-content">

Certain reporting files transmitted to the supervisory authorities must be encrypted.<br>
Prior your first filing you will have to order and activate a Luxtrust certificate.<br>
The only certificate authorised for the file encryption by the reporting entity are '''SSL certificates''' from the certification authority [https://www.easyssl.lu/?product=e-file LUXTRUST].

Please check the [[Transmission_Module#System_requirements|system requirements]] to run the e-file applications.

=== Key and Certificate Request generation ===

Please be informed that during the next steps <span style="background:yellow"> <u>two files</u> </span> will be generated:

<span style="background:yellow"> 1- </span> the keystore file '''keystore.ks''' containing your new keys

<span style="background:yellow"> 2- </span> the certificate request file '''Certificate Request.csr''' containing a copy of your new keys. <u>This file must be uploaded on LUXTRUST's website during your purchase order</u> .

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate purchase order and its activation have to be performed on the same computer workstation.</span>'''

<u>'''Step 1</u>:'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 30).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 30)

<u>'''Step 2</u>:'''

Click the '''Certificates ''' button (Figure 31)

[[File:AdminModule_2.png|border|500px]]

(Figure 31)

<u>'''Step 3</u>:'''

The '''Certificates Management''' screen opens. Click the '''CERTIFICATE REQUEST - ACTIVATION MENU''' link (Figure 32).

[[File:AdminModule_3.png|border|1000px]]

(Figure 32)

<u>Result</u>: A new screen opens displaying GENERATE CERTIFICATE KEYS - BEFORE LUXTRUST WEBSITE ORDER on the left side of the page

<u>'''Step 4</u>:'''

Configure your keystore (Figure 33).

[[File:Configure_your_keystore.png|border|1000px]]<br>

(Figure 33)

a. <u>Select the keystore import method</u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, select '''Create a new keystore file''' option and indicate a keystore name.

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, you '''<u>must</u> '''select your '''curent keystore file''' by using the ''browse file'' or ''drag & drop'' feature to import it.

<span style="color: #C00000">'''Important note : in both case, the new keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

- File name: choose your keystore name, for example '''keystore.ks'''

- File type : .ks

b. <u>Password </u>

If you order the certificate for the <span style="background:yellow"> <u>'''very first time'''</u> </span>, you have to define a brand-new '''keystore password'''.
A confirmation is required

In the case you have to <span style="background:yellow"> <u>'''renew'''</u> </span> your certificate, e.g. its validity date expired, you <u>must</u> use the '''keystore password''' that had been created when you ordered the certificate for the '''very first time'''.

<span style="color: #C00000">''' Important note : the keystore password has to be shared with all e-file users who have to transmit encrypted documents or decrypt feedback files received from the supervisory authorities. </span>.

<span style="color: #C00000">''' Important note : if you loose your keystore password, you will have to generate a new key and order a new certificate. </span>

c. <u>Certificate request name (.csr)</u>

You have to define a name for the technical certificate request file required by Luxtrust, for example '''CertificateRequest.csr'''

<span style="color: #C00000">'''Important note : the certificate request will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

- File name: '''CertificateRequest.csr'''

- File type : .csr

<u>'''Step 5</u>:'''

Verify the Company information. (Figure 34) :

[[File:Company_information.png|border|1300px]]

(Figure 34)

The related fields will be pre-filled in with information we currently have in our system. Feel free to make changes if necessary.

<u>'''Step 6</u>:'''

Click the '''Generate keys''' button.

A window will pop up inviting you to download the Keystore file and Certificate Signing Request (Figure 35).

[[File:Keystore CSR download window.PNG|border|500px]]

(Figure 35)

You must click on each of the Download buttons in order to activate the OK button.<br>
Then click OK to clear the message window.

<span style="color: #C00000">'''Both keystore and certificate request files will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name as follows: <br>The name of the previous keystore + a timestamp displayed as yyyymm + onhold. <br><br>Example: oldname : MyKeystore.ks / new name : MyKeystore_202212_onhold.ks''' </span>

<span style="color: #C00000">'''Important note : we advise you to back up the keystore.ks and CertificateRequest files.''' </span>

=== Finalize your LUXTRUST purchase order ===

<span style="color: #C00000">'''Before to start order in the Luxtrust website make sure that you have process the previous part (Key and Certificate Request generation). </span>

-Open the [https://www.easyssl.lu/?product=e-file LUXTRUST easy SSL e-file website].

-Browse to SSL Certificate section and click the E-FILE icon
[[File:Sans titre.png|50px]]

-Choose the period of validity of your certificate and click the ORDER E-FILE button.

-If you do not have a LUXTRUST easy SSL e-file account you have to get registered.

-Once registered, complete the whole order form, upload your '''CertificateRequest<span style="background:yellow">.csr </span>''' file, accept the TERMS AND CONDITIONS and click the PLACE ORDER button.

-Shortly afterwards, you will receive an e-mail from LUXTRUST confirming your purchase order.

-Please follow all instructions provided in the e-mail and its PDF attachment (Send signed PDF by post with all required documents to the address indicated inside, process the payment etc.)

----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_do_I_activate_my_LUXTRUST_certificate_into_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How do I activate (integrate) my LUXTRUST certificate into e-file ?</div>
<div class="mw-collapsible-content">

The certificate file will be sent to the e-mail address you provided in your purchase order.

The extension of this file will be .txt, in order to prevent your firewall from blocking the attached file.

<u>'''Step 1</u>:'''

<span style="color: #C00000">'''Important note: save the file .txt on your computer workstation and <u>replace</u> the .txt extension by <span style="background:yellow">.cer </span> </span>

Double-click the <span style="background:yellow"> .cer </span> file. You should be able to see your certificate as shown below (Figure 36):

[[File:Certificate visual example.png|alt=Certificate example|377x377px]]

(Figure 36)

<u>'''Step 2</u>:'''

<span style="color: #C00000">'''Important note : the Luxtrust SSL certificate ordering and its activation have to be performed on the same computer workstation.</span>'''

Connect to [https://e-file.lu e-file.lu] with your [[E-file Administration|'''e-file administrator''']] credentials (adminXXX) and click the '''Administration module''' icon (Figure 37).

[[File:Administration module icon (Figure 2).png|400px]]

(Figure 37)

<u>'''Step 3</u>:'''

Click the '''Certificates ''' button (Figure 38).

[[File:AdminModule2.png|border|500px]]

(Figure 38)

<u>'''Step 4</u>:'''

Click the '''CERTIFICATE ACTIVATION – AFTER RECEPTION OF LUXTRUST CERTIFICATE''' link (Figure 40).

[[File:Certificate_activation.png|border|1500px]]

(Figure 40)

<u>'''Step 5</u>:'''

Configure your keystore (Figure 41).

[[File:Certificate_activation_steps.png | 1000px]]

(Figure 41)

a. <u>Select the Group you need to use (by default Principal)</u>

b. <u>Import the keystore that was generated at the same time as the Certificate Signing Request</u>
(from previous step )

c. <u>Enter the keystore password</u>

d. <u>Import the certificate you received from Luxtrust </u>

<u>'''Step 6</u>:'''

Click the '''ACTIVATE CERTIFICATE''' button.

A window will pop up and inform you that the activation has been done successfully.

Your keystore.ks is now updated. It contains your activated LUXTRUST certificate and your encryption keys.

[[File:AdminModule_15.png | 300px]]

'''Note''': The display and the position of the pop up may differ regarding the Web browser you are using

<span style="color: #C00000">'''Important note : the updated keystore will be generated in the configured download folder of your Web browser e.g.: C:\Users\xxx\Downloads.'''</span>

<span style="color: #C00000">'''Important note : the updated keystore will be generated with a new name : the name of the previous keystore + a timestamp displayed as yyyymm + completed.<br>Example: previous name : MyKeystore.ks / new name : MyKeystore_202212_completed.ks''' </span>

<span style="color: #C00000">'''Important note : if you loose your keystore and/or its password,you will have to generate a new encryption key and order a new certificate. </span>.
-------------

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_must_I_do_with_the_keystore></span>
<div style="font-weight:bold;line-height:2.5;">What must I do with the keystore ?</div>
<div class="mw-collapsible-content">

===Manual file transmission===

The activated keystore, containing your LUXTRUST certificate and your encryption keys must now be provided to the workstations of each e-file user.

<u>'''Step 1</u>:'''

Open the Transmission module

[[File:Icon1.png | 300px]]

<u>'''Step 2</u>:'''

[[File:Keystore selection After(1).PNG| 600px]]

===Automatic file transmission===

In the case you are using the [[Sending_Service|Sending Service]] for automatic file transmission, the activated keystore.ks must be provided as well.
----------------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_register_my_LUXTRUST_certificate_with_the_CSSF></span>
<div style="font-weight:bold;line-height:2.5;">How can I register my LUXTRUST certificate with the CSSF ?</div>
<div class="mw-collapsible-content">

For some reportings, the LUXTRUST e-file SSL certificate used by the reporting entity must be registered with the CSSF, before sending any files, according to the registration procedure described in the '''[https://www.cssf.lu/wp-content/uploads/Naming-convention.pdf#page=8 CSSF 23/833, naming convention part.]'''

The LUXTRUST e-file SSL certificate must be registered with the CSSF for the below reportings:</br>
(list extracted from [https://www.cssf.lu/fr/transport-et-securisation/#specifications-techniques Transport et sécurisation via les canaux de transmission externes])

* COREP/FINREP reporting
* ESP – Special enquiries
* SIC – SICAR reporting
* PFS – Reporting PFS and support PFS
* EDP – Payment institutions reporting
* EME – Electronic money institution
* SGO – Management companies reporting
* OPC – Fund XML reporting (O1.2)
* DOC – Non-structured electronic documents (circ. 19/731)
* OTH – Other
* OCB – Other reportings for CSSF and BCL
* SUF – XBRL reportings for subfund-based structured products (IORP)
* O4.x – Edifact report

[[Media:How to declare your Luxtrust certificate to the CSSF.pdf|=> e-file User Guide: CSSF Certificate registration]]
----------------
</div>
</div>

=== * S3 system ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_is_the_S3_digital_key_management_in_e-file></span>
<div style="font-weight:bold;line-height:2.5;">How is the S3 digital key management in e-file ?</div>
<div class="mw-collapsible-content">

The CSSF has updated its submission methods to allow AIFMs to file specific regulatory reports via the CSSF’s API from 2nd November.
Please note, this is not the deadline to make the change, it is the point at which the new method is available to use. <br>
FE Fundinfo are ready to support you through the transition.
Your current setup in e-file will remain in place and only minor one-off changes are required from you to ensure the continuation of your existing functionality on e-file and future proof the communication method for all reporting and filing with the CSSF going forward.
<br><br>

<u>'''Explanation in context of AIFMD reporting</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/7273286345756229380 November 21st webinar in English] and the [https://c2rv804.na1.hubspotlinks.com/Ctc/ZO+113/c2RV804/VWQ8Fx5Hw7JyVdSL7w2rxckBW20x2Jc566MpmN31NNCl5nXHsW7Y9pgv6lZ3kLW8mzYxT1ZSlmLW7yCpDW2jmg69W73tZTZ5yBySkW7jL_zN8my412W9hGQQt71RszSVkgkWT3FF-R2W1VryJ67bk_NmW1RKWr345DTFjV1PBRM2KwkQsW4P0bYq6h4FhzW2Y0TlL8jm7QlW6N2qBz9lFm9yW1bNKCy1qGVgGW7dJWkQ8TTtG5N3kH6ptzC816W33qG8b10K_BtW8gQSgN4g3h5TW9h3bp34KXCJHV_q02d6BgPGWW5xJSX81p0bg6W8jK_6G221K5qW3_hsX93mN9kwW2RyrBr7f39YJW8v09kD7Cw1nxW37qD826JSxdcW4Rc7yD85pl3PW109fZz4mxLcHW26Y0Y03k4GNWW8zPXjF1t6bspW78yjPn71W4ftW8-MxR372T_w5V13CVl6qstVRW21LWhW2dlqL_W2Xs3ZP6K5mZ2W1THZsw1FrpXLW54G4QN27qB0BW3yXpwm7rd3qwW23mB7r301kH7W19MCT85QW6wbW218pPC2z-WjCVQRHvT30nLTNW1qM-sk29_0TFd2XXgW04 related presentation]

[https://attendee.gotowebinar.com/recording/2231697877960308483 Webinaire en français]

<u>'''Explanation in context of UCITS Cross-Border notification</u>:'''<br>
See our online webinar for more explanations : [https://attendee.gotowebinar.com/recording/2670031382955110830 December 12th webinar in English] and the [https://445778.fs1.hubspotusercontent-na1.net/hubfs/445778/FE%20fundinfo%20presentations/FSQ%20channel%20change_Webinar%2012%20December.pdf related presentation]

This new system works via a bucket system.<br>
There is one bucket for each filing context (i.e. Cross-border notification, AIFMD)<br>
The CSSF imposes a technical size limit for filing per bucket on 30 rolling days.<br>
Should you encounter any issue, feel free to contact us directly [[How to contact us|'''Client Support & Operations Desk''']] we will liaise with the CSSF.<br>

<br>
The below is a step-by step guide to appoint FE Fundinfo as a delegate within the CSSF’s eDesk platform, the easiest path to allow us to maintain our services. <br>
Once the set-up is complete you can continue to use your familiar eFile interface and do not need to interact with eDesk as this will all be channelled within your existing workflows in eFile.
<br><br>
To perform the set-up in eFile you have two options:
<br>

* You as IT expert import the S3 keys on eFile

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide for eDesk IT Experts to connect CSSF’S eDesk to FE Fundinfo’s eFile system''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Your entity’s appointed IT Expert will need to log into the IT Management
area of eDesk ([https://edesk.apps.cssf.lu/edesk-itmgt/s3/accesses here]). This must be using the same LuxTrust Device and
account that the IT Expert role was assigned to. Please note, that these
steps can only be implemented from the appointed IT Expert account
|
|-
|
Step 2
|
Once logged in, go to the ‘S3 ACCESS DASHBOARD’ at the top of the page,
which will take you to a screen similar to the below
|
[[File:02-S3Dashboard.png|S3Dashboard|800px]]
|-
|
Step 3
|
Select ‘Create Access’
|
[[File:03-S3CreateAccess.png|S3CreateAccess|800px]]
|-
|
Step 4
|
This will provide you with an option to select a ‘scope’ which will be the
reporting type you have been appointed as IT Expert for and select create:
<br>
[[#Correspondance table|You can refer to our correspondance table]]
|
[[File:04-S3CreateScope.png|S3CreateScope|800px]]
|-
|
Step 5
|
This will create a line in the S3 access dashboard with the report type, the
status (this should show ‘Granted’) and the date of this creation.
<br>
Each report type generates 3 codes on eDesk, (the Bucket code, the Access
Key, and the Secret Key). To reveal these keys, click the magnifying glass
with a ‘+’ icon under the actions column (located on the far right of the
screen).
|
[[File:05-S3Granted.png|S3Granted|800px]]
|-
|
Step 6
|
This will reveal the information about the who the access has been granted to, when and what report it is for. It will also provide details of the unique codes specific to the entity, report type and individual.
|
[[File:06-S3Access.png|S3Access|800px]]
|-
|
Step 7
|
Once the Keys have been generated, keeping your connection to eDesk open, in another window, open your efile environment. Log in using the efile Admin account for your entity and open the ‘Keys Management’ tab.
|
[[File:07-efileMenu.png|efileMenu|800px]]
|-
|
Step 8
|
Select ‘Add Key’ on the far right of the screen
|
[[File:08-eFileAddKey.png|eFileAddKey|800px]]
|-
|
Step 9
|
A pop out will appear and provide you with several drop down lists to
complete. Under ‘Scope’ you should choose the report type that you are
providing the Keys for. In this instance AIFMD should be selected.
|
[[File:09-eFileScope.png|eFileScope|800px]]
|-
|
Step 10
|
Returning to eDesk, copy the Bucket code, the Access key and Secret key
and paste each of these into the applicable boxes on efile.
|[[File:10-BucketCopy.png|BucketCopy|800px]]
|-
|}

===Correspondance table===
'''Please find the correspondence table of e-file and e-Desk scopes'''<br>

{| class="sortable" border="1" cellspacing="2" cellpadding="1"
|- <div style="position:sticky;top:-1px;z-index:10">
! scope="col" | '''Label scope in e-file'''
! scope="col" | '''Label scope in e-Desk'''
! scope="col" | '''CSSF reference'''
! scope="col" | '''Deadline'''
</div>
|-
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | Reporting AIFM
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/AIFM_Reporting_Technical_Guidance.pdf AIFM reporting -Technical guidance]
| style="vertical-align:middle; color:#202122;" | 30 June 2024
|-
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | Cross-border marketing notifications
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_guide_notifications_CBDF.pdf User guide notifications CBDF]
| style="vertical-align:middle; color:#202122;" | 2nd January 2024
|-
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | UCI Adminsitrator - Annual reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/cssf22_811eng.pdf CSSF 22/811]
| style="vertical-align:middle; color:#202122;" | 30 June 2023
|-
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | Quarterly survey of covered deposits (FGDL)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSSF_CPDI_2440eng.pdf CSSF-CPDI 24/40]
| style="vertical-align:middle; color:#202122;" | 15 May 2024
|-
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - Precontractual disclosures - SFO
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Precontractual_Data_Collection_-_practical-guide.pdf SFDR precontractual data collection]
| style="vertical-align:middle; color:#202122;" | 31 October 2023
|-
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures
| style="vertical-align:middle; color:#202122;" | SFDR - periodical disclosures - SFPER
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User_Guide_-_SFDR_UCI_Data_Collection_-_practical-guide.pdf SFDR UCI Data Collection]
| style="vertical-align:middle; color:#202122;" | 31 January 2024
|-
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | EBA ITS standard reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Bank_prudential_reporting.pdf Bank prudential reporting]
| style="vertical-align:middle; color:#202122;" | 1st September 2024

|-
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | Regulatory Documents and Reports
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Regulatory-documents-and-reports.pdf User Guide for Regulatory Documents and Reports]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | Key Information Document (KID PRIIPs/KID)
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/User-Guide-Key-Information-Document.pdf User Guide for Key Information Document]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | U1.1 reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_U1.1.pdf Guidelines on the U1.1 reporting]
| style="vertical-align:middle; color:#202122;" | 15th November 2024

|-
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | Information on covered investment claims
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_Yearly_Survey_on_Covered_Investment_Claims.pdf Guidelines for the Yearly Survey on Covered Investment claims (SIIL)]
| style="vertical-align:middle; color:#202122;" | 17th January 2025

|-
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | SAQ PDAOFI
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/Guidelines_SAQ_DPAAIF.pdf Guidelines on the self-assessment questionnaire PDAOFI]
| style="vertical-align:middle; color:#202122;" | 31st March 2025

|-
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | Prospectus identification
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2025/03/upcoming-evolution-in-the-electronic-visa-stamp-procedure-for-the-prospectuses-of-ucits-part-ii-ucis-sicars-and-sifs/ Procedure change for visa "stamp" prospectuses]
| style="vertical-align:middle; color:#202122;" | 1st April 2025

|-
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | Csdr article 9
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/CSDR9_Handbook.pdf User Guide Internalised Settlement Reporting Under Article 9 OF CSDR]
| style="vertical-align:middle; color:#202122;" | 1st July 2025

|-
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | MMF Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/wp-content/uploads/MMFR_Handbook.pdf MMF reporting Handbook]
| style="vertical-align:middle; color:#202122;" | 1st September 2025

|-
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | IRP XBRL Reporting
| style="vertical-align:middle; color:#202122;" | [https://www.cssf.lu/en/2026/01/iorp-reporting-circular-cssf-19-726-new-edesk-procedure/ new IORP procedure]
| style="vertical-align:middle; color:#202122;" | 15th January 2026

|}
---------------
</div>
</div>
</br></br>

===Special cases===
'''For Key Information Document (KID PRIIPs/KID) and Regulatory Documents and Reports scopes'''<br>
Due to the way the CSSF has implemented the third-party delegation process we have adapted our S3 scope import system in order to enable
</br>
the possibility for a client who is a service provider to onboard multiple S3 keys for the same scope on different Asset Managers / Self-managed funds / Filing entity based on the FSQ referential
</br></br>
To do so after having selected Key Information Document (KID PRIIPs/KID) or Regulatory Documents and Reports scope.<br>
You have to use the dedicated radio button Asset Manager, Self-Managed funds or Filing Entity
<br>
The list is automatically refreshed to only display third-party without S3 key onboarded.<br>
In case of a Filing Entity, the name of the Third party linked to the eFile user will be pre-filed (and can't be changed)<br>
[[File:AssetManager-SelfManaged-FilingEntity.png|Asset Manager, Self-Manged fund or Filing Entity|400px]]

To help you identifying which key has already been imported on eFile a dedicated page has been added in the S3 Keys Management module <br>
This page lists the already imported key for scope(s) allowing delegation. <br>
The Bucket owner (entity that owns the S3 key) and the Provider (entity who uploaded the S3 key on eFile) are displayed.<br>
[[File:DelegationList.png|S3 Key list|800px]]

* Grant us with the IT expert role to perform such changes for you
To start the process please send us an email to '''[mailto:cso.desk@fundsquare.net cso.desk@fundsquare.net]''' with both '''name''' and '''CSSF identification number''' of the entity you want we become IT Expert

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">'''Step by step guide on how to assign FE Fundinfo as a CSSF IT Expert on eDesk''' <span style="color: #C00000">click to expand</span></div>
<div class="mw-collapsible-content">
</br></br>
{|border="1" cellspacing="2" cellpadding="10"
|+
!'''Steps'''
!'''Actions'''
!'''Additional information'''
|-
|
Step 1
|
Log into [https://edesk.apps.cssf.lu/ eDesk] with the Advanced User account using your LuxTrust Device and Password. Please note that these changes can only be implemented from the Advanced User account
|
|-
|
Step 2
|
Once logged in, go to the top right corner of the screen, click on your account user name, and select ‘Entity Management’
|
[[File:02-EntityManagement.png|EntityManagement|800px]]
|-
|
Step 3
|
Now select ‘Access Requests’ from the tabs at the top of the screen:
|
[[File:03-AccessRequest.png|AccessRequest|800px]]
|-
|
Step 4
|
As FEfundinfo will have made a request to connect from our Fundsquare account, you will see us on a list of users requests to connect with your entity. You will be able to identify our request as it will be with the LuxTrust SN: <span style="color: #C00000">100115278245548987357</span>
|
[[File:04-LuxtrustSN.png|LuxtrustSN|800px]]
|-
|
Step 5
|
Once you have identified the FE fundinfo request from our Fundsquare account, you can go to the far right of the screen and select ‘ACCEPT ACCESS’ or ‘REJECT ACCESS’. Remember to only
accept requests and provide access to users you are associated with. You will need to ‘ACCEPT ACCESS’ on our request:
|
[[File:05-AcceptAccess.png|AcceptAccess|800px]]
|-
|
Step 6
|
Once you have clicked accept, go to the ‘Specific roles within entity’ tab:
|
[[File:06-SpecificRole.png|SpecificRole|800px]]
|-
|
Step 7
|
Under the ‘Specific roles within entity’ tab, on the right of the screen, click the ‘Add’ button:
|
[[File:07-AddSpecificRole.png|AddSpecificRole|800px]]
|-
|
Step 8
|
You will now be able to click on the ‘User’ box and select a user within the list of approved users connected with your entity. One of these will be FE fundinfo’s Fundsquare account, select this option and the user details will populate automatically:
|
[[File:08-FSQUser.png|FSQUser|800px]]
|-
|
Step 9
|
Now you can select a role for that user, in this case you will need to select IT EXPERT for FE fundinfo in the drop down selection and click save on the top right to make the change
|
[[File:09-ITExpert.png|ITExpert|800px]]
|-
|
Step 10
|
You have now completed all you need to ensure continued use of efile and secure submission of your reports to the CSSF! FE fundinfo will do the rest and can now ensure that the changing transmission methods gradually introduced by the CSSF over the next 18 months are updated as needed without any impact on you
|
|-
|}
----------------
</div>
</div>

::== Onboarding workflow map ==
''You can click on the picture.''
<imagemap>
File:Wkf_S3_onboarding.png|center|1500px|alt=clickable image : form description| titre
rect 106 355 277 452 [[E-file_Administration#You_as_IT_Expert | You as IT Expert ]]
rect 776 541 947 630 [[E-file_Administration#FE_Fundinfo_as_IT_Expert |FE Fundinfo as IT Expert]]
rect 1024 376 1193 482 [https://edesk.apps.cssf.lu/edesk-dashboard/homepage?lng=en eDesk User Guide ]
rect 477 530 646 691 [https://www.cssf.lu/wp-content/uploads/Methods-of-transmitting-reports-via-S3-Application-Programming-Interface-Technical-guidance.pdf S3 transmitting method ]
desc none
</imagemap>
-----------
</div>
</div>

=== * general security questions ===

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_change_the_local_e-file_administrator></span>
<div style="font-weight:bold;line-height:2.5;">How can I change the local e-file administrator ?</div>
<div class="mw-collapsible-content">

Each e-file administrator account is linked to a single email at a time.

3 cases :
* You have access to the account
:then change the email of the administrator by using the <b>administration module</b> and update the administrator account's owner (name, firstname). The new administrator will just have to request a new password.
* You have access to the administrator's e-mail box
:you can use the "forgotten password" button on https://www.e-file.lu to change the password and get access.
* You do not have access to the administrator account nor to the email of this account
:then for security reason you will have to follow this specific procedure:

::Your request must be sent by email and paper mail.

::The paper can be replaced by a mail with a scan of the letterhead paper => Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com].

<u>'''The request must be submitted on letterhead of your company and signed by a legal representative with the following information'''</u>:
*Administrator's login adminXXX
*The current email address which is linked to the administrator
*The new email address to link to the administrator
*A brief explanation of the reason why you need to change it
*Send your email to '''[mailto:e-file.support@fefundinfo.com e-file.support@fefundinfo.com]'''

Once Fundsquare has received and checked your request we will update your email and send you the procedure to update the password.

If you have further questions do not hesitate to contact our [[How to contact us|'''Client Support & Operations Desk''']].

-----------------
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=What_is_the_e-file_password_policy></span>
<div style="font-weight:bold;line-height:2.5;">What is the e-file password policy ?</div>
<div class="mw-collapsible-content">

[[File:Password.png|300 px]]

(Figure 42)

The password you will have to provide must follow the rules below:

*At least one upper and one lower case letter
*At least one number
*At least one special character from this list: ! # $ % & ( ) * + , . /: ; < = > ? ^ _ @ { | } [ ] ~
*At least 8 characters and at most 20

<u> Please note that </u>:

The validity of your password is not limited in time.

Our system blocks the user after 3 incorrect attempts and it is the e-file administrator who has to unblock the account.

Passwords are encrypted in our database and we do not keep them. You may re-use them.
-----------
</div>
</div>

== Being informed ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_important_information></span>
<div style="font-weight:bold;line-height:2.5;">How can I get important information ?</div>
<div class="mw-collapsible-content">

As an administrator, you will received all significant information regarding e-file changes, maintenance or enhancement through the e-mail address set up onto your account.
You can also manage some alerts through e-file, see the notifications system.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=How_can_I_get_custom_notifications></span></span>
<div style="font-weight:bold;line-height:2.5;">How can I get custom notifications ?</div>
<div class="mw-collapsible-content">

Please be informed that you can receive alert by email triggered by specific events.

<u>Example</u> : Court orders sent by the Luxembourgish judicial police [http://www.cssf.lu/fileadmin/files/Lois_reglements/Circulaires/Hors_blanchiment_terrorisme/cssf13_566eng.pdf (=> CSSF - Circular 13/566)]

If you want to be notified by email each time the Luxembourgish judicial police sends you court orders, you have to follow the steps below.

<u>'''Step 1'''</u> : Connect to e-file with your user credentials : '''https://www.e-file.lu/e-file/'''

<u>'''Step 2'''</u> : Select Update my profile

[[File:Select Update my profile.png |200 px]]

<u>'''Step 3'''</u> : Verify that your email address registered in your e-file account is valid.

[[File:Your e-file account is valid.png |400 px]]

<u>IMPORTANT :</u> if your email address is not valid, please ask your [[Administration#e-file_administrator_functions_.28e-file_v1.29|'''e-file administrator''']] to replace it by a valid one.

<u>'''Step 4'''</u> : Select Customize your notifications.

[[File:Customize your notifications.png |200 px]]

<u>'''Step 5'''</u> : Select group.

[[File:Select group555.png |400 px]]

<u>'''Step 6'''</u> : Select the Alert type.

[[File:Notification.png |500 px]]

<u>IMPORTANT :</u>

A green window will pop-up stating that the update has been saved.

<u>'''Optional Step 7'''</u> : Receive only your alerts and not the group's ones.

Ticking also the group box, the sends from other users of the same reports group will be ignored.

[[File:Alerte Notification.png |500 px]]

[[Category: FAQ e-file]]

----------------------
</div>
</div>

Glossary

2026-04-15T08:11:52Z

Cso: /* S */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CAA></span>
<div style="font-weight:bold;line-height:2.5;">CAA</div>
<div class="mw-collapsible-content">

:The Commissariat aux Assurances (CAA) is the Luxembourg supervisory authority for the insurance sector.
:[https://www.caa.lu/ Accueil - Commissariat aux Assurances]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ContactForm></span>
<div style="font-weight:bold;line-height:2.5;">Contact Form</div>
<div class="mw-collapsible-content">

:A form to be filled in to add the depositor’s and declarant’s information in e-File’s referential.
:More details: [[Onboarding|Onboarding - E-fileWiki]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSR></span>
<div style="font-weight:bold;line-height:2.5;">CSR file</div>
<div class="mw-collapsible-content">

:The .csr file is a technical file that you must upload when you order the LuxTrust certificate on [https://www.easyssl.lu/?product=e-file their website]
:You need '''first''' to log on to [https://www.ee-file.lu e-File] with your company’s '''administrator account''' to generate this file.
:More details [[E-file_Administration#How_do_I_order_a_LUXTRUST_certificate|How do I order a LUXTRUST certificate ?]]
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FDF></span>
<div style="font-weight:bold;line-height:2.5;">FDF form</div>
<div class="mw-collapsible-content">
:Fundamental Data Form. To be filled in to ask creation or changes on fund's tree information in e-File’s referential
:More information can be found on: [[E-file_Static_Data_Management#How_to_use_FSQ_IDs_in_the_Fundamental_Data_Form_(FDF) | How to use the FDF form]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
: More details on [[ReportGeneration | ReportGeneration Wiki page]]
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingType></span>
<div style="font-weight:bold;line-height:2.5;">Sending Type</div>
<div class="mw-collapsible-content">

:In eFile, a ''Sending Type'' defines how a report or document is technically transmitted to the authority, which sub-channel is used.
:By importing a file in the [[#TransmissionModule | Transmission module]] the ''Sending Type'' is generally automatically selected by our tool.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Glossary

2026-04-15T08:09:39Z

Cso: /* S */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CAA></span>
<div style="font-weight:bold;line-height:2.5;">CAA</div>
<div class="mw-collapsible-content">

:The Commissariat aux Assurances (CAA) is the Luxembourg supervisory authority for the insurance sector.
:[https://www.caa.lu/ Accueil - Commissariat aux Assurances]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ContactForm></span>
<div style="font-weight:bold;line-height:2.5;">Contact Form</div>
<div class="mw-collapsible-content">

:A form to be filled in to add the depositor’s and declarant’s information in e-File’s referential.
:More details: [[Onboarding|Onboarding - E-fileWiki]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSR></span>
<div style="font-weight:bold;line-height:2.5;">CSR file</div>
<div class="mw-collapsible-content">

:The .csr file is a technical file that you must upload when you order the LuxTrust certificate on [https://www.easyssl.lu/?product=e-file their website]
:You need '''first''' to log on to [https://www.ee-file.lu e-File] with your company’s '''administrator account''' to generate this file.
:More details [[E-file_Administration#How_do_I_order_a_LUXTRUST_certificate|How do I order a LUXTRUST certificate ?]]
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FDF></span>
<div style="font-weight:bold;line-height:2.5;">FDF form</div>
<div class="mw-collapsible-content">
:Fundamental Data Form. To be filled in to ask creation or changes on fund's tree information in e-File’s referential
:More information can be found on: [[E-file_Static_Data_Management#How_to_use_FSQ_IDs_in_the_Fundamental_Data_Form_(FDF) | How to use the FDF form]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
: More details on [[ReportGeneration | ReportGeneration Wiki page]]
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingType></span>
<div style="font-weight:bold;line-height:2.5;">Sending Type</div>
<div class="mw-collapsible-content">

In eFile, a ''Sending Type'' defines how a report or document is technically transmitted to the authority, which sub-channel is used.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Glossary

2026-04-15T07:57:08Z

Cso: /* R */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CAA></span>
<div style="font-weight:bold;line-height:2.5;">CAA</div>
<div class="mw-collapsible-content">

:The Commissariat aux Assurances (CAA) is the Luxembourg supervisory authority for the insurance sector.
:[https://www.caa.lu/ Accueil - Commissariat aux Assurances]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ContactForm></span>
<div style="font-weight:bold;line-height:2.5;">Contact Form</div>
<div class="mw-collapsible-content">

:A form to be filled in to add the depositor’s and declarant’s information in e-File’s referential.
:More details: [[Onboarding|Onboarding - E-fileWiki]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSR></span>
<div style="font-weight:bold;line-height:2.5;">CSR file</div>
<div class="mw-collapsible-content">

:The .csr file is a technical file that you must upload when you order the LuxTrust certificate on [https://www.easyssl.lu/?product=e-file their website]
:You need '''first''' to log on to [https://www.ee-file.lu e-File] with your company’s '''administrator account''' to generate this file.
:More details [[E-file_Administration#How_do_I_order_a_LUXTRUST_certificate|How do I order a LUXTRUST certificate ?]]
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FDF></span>
<div style="font-weight:bold;line-height:2.5;">FDF form</div>
<div class="mw-collapsible-content">
:Fundamental Data Form. To be filled in to ask creation or changes on fund's tree information in e-File’s referential
:More information can be found on: [[E-file_Static_Data_Management#How_to_use_FSQ_IDs_in_the_Fundamental_Data_Form_(FDF) | How to use the FDF form]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
: More details on [[ReportGeneration | ReportGeneration Wiki page]]
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Glossary

2026-04-15T07:55:19Z

Cso: /* F */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CAA></span>
<div style="font-weight:bold;line-height:2.5;">CAA</div>
<div class="mw-collapsible-content">

:The Commissariat aux Assurances (CAA) is the Luxembourg supervisory authority for the insurance sector.
:[https://www.caa.lu/ Accueil - Commissariat aux Assurances]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ContactForm></span>
<div style="font-weight:bold;line-height:2.5;">Contact Form</div>
<div class="mw-collapsible-content">

:A form to be filled in to add the depositor’s and declarant’s information in e-File’s referential.
:More details: [[Onboarding|Onboarding - E-fileWiki]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSR></span>
<div style="font-weight:bold;line-height:2.5;">CSR file</div>
<div class="mw-collapsible-content">

:The .csr file is a technical file that you must upload when you order the LuxTrust certificate on [https://www.easyssl.lu/?product=e-file their website]
:You need '''first''' to log on to [https://www.ee-file.lu e-File] with your company’s '''administrator account''' to generate this file.
:More details [[E-file_Administration#How_do_I_order_a_LUXTRUST_certificate|How do I order a LUXTRUST certificate ?]]
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FDF></span>
<div style="font-weight:bold;line-height:2.5;">FDF form</div>
<div class="mw-collapsible-content">
:Fundamental Data Form. To be filled in to ask creation or changes on fund's tree information in e-File’s referential
:More information can be found on: [[E-file_Static_Data_Management#How_to_use_FSQ_IDs_in_the_Fundamental_Data_Form_(FDF) | How to use the FDF form]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Glossary

2026-04-15T07:45:44Z

Cso: /* C */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CAA></span>
<div style="font-weight:bold;line-height:2.5;">CAA</div>
<div class="mw-collapsible-content">

:The Commissariat aux Assurances (CAA) is the Luxembourg supervisory authority for the insurance sector.
:[https://www.caa.lu/ Accueil - Commissariat aux Assurances]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ContactForm></span>
<div style="font-weight:bold;line-height:2.5;">Contact Form</div>
<div class="mw-collapsible-content">

:A form to be filled in to add the depositor’s and declarant’s information in e-File’s referential.
:More details: [[Onboarding|Onboarding - E-fileWiki]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSR></span>
<div style="font-weight:bold;line-height:2.5;">CSR file</div>
<div class="mw-collapsible-content">

:The .csr file is a technical file that you must upload when you order the LuxTrust certificate on [https://www.easyssl.lu/?product=e-file their website]
:You need '''first''' to log on to [https://www.ee-file.lu e-File] with your company’s '''administrator account''' to generate this file.
:More details [[E-file_Administration#How_do_I_order_a_LUXTRUST_certificate|How do I order a LUXTRUST certificate ?]]
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Glossary

2026-04-15T07:37:44Z

Cso: /* C */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CAA></span>
<div style="font-weight:bold;line-height:2.5;">CAA</div>
<div class="mw-collapsible-content">

:The Commissariat aux Assurances (CAA) is the Luxembourg supervisory authority for the insurance sector.
:[https://www.caa.lu/ Accueil - Commissariat aux Assurances]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ContactForm></span>
<div style="font-weight:bold;line-height:2.5;">Contact Form</div>
<div class="mw-collapsible-content">

:A form to be filled in to add the depositor’s and declarant’s information in e-File’s referential.
:More details: [[Onboarding|Onboarding - E-fileWiki]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Glossary

2026-04-15T07:34:21Z

Cso: /* C */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CAA></span>
<div style="font-weight:bold;line-height:2.5;">CAA</div>
<div class="mw-collapsible-content">

:The Commissariat aux Assurances (CAA) is the Luxembourg supervisory authority for the insurance sector.
:[https://www.caa.lu/ Accueil - Commissariat aux Assurances]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Glossary

2026-04-15T07:32:38Z

Cso: /* A */

<small>''Page's last update : {{REVISIONDAY2}} {{CURRENTMONTHABBREV}} {{REVISIONYEAR}}''</small>

Please find below some useful vocabulary and acronyms you can find on eFile and on our Wiki:
<br>

<span id="BackToTop"></span>
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

<div style="text-align: right; direction: ltr; margin-left: 1em;">[[Welcome_to_e-file_and_Fundsquare_FAQ|Home page ]][[File:Home.png|Return homepage|link=Welcome_to_e-file_and_Fundsquare_FAQ]]</div>

== A ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Administrator></span>
<div style="font-weight:bold;line-height:2.5;">Administrator</div>
<div class="mw-collapsible-content">

:The '''Administrator''' is a specific type of user on '''eFile'''
:The purpose of such account is to manage the [[#EndUser|end-user accounts]] and ensure prerequisites are met such as an active [[#Certificate|Luxtrust certificate]] or the S3 key has been imported
:No filing is expected to be done via an administrator account
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ACD></span>
<div style="font-weight:bold;line-height:2.5;">ACD</div>
<div class="mw-collapsible-content">

:The '''Administration des Contributions Directes''' The Luxembourg Tax authority.<br>
:This is the recipient of [[#CRS|CRS]] and [[#FATCA|FATCA]] reporting
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIF></span>
<div style="font-weight:bold;line-height:2.5;">AIF</div>
<div class="mw-collapsible-content">

:The '''Alternative Investment Fund (AIF)''' is a type of investment vehicle regulated under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AIFM></span>
<div style="font-weight:bold;line-height:2.5;">AIFM</div>
<div class="mw-collapsible-content">

:The Manager of an '''Alternative Investment Fund (AIF)''' under the AIFMD framework.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Alerting></span>
<div style="font-weight:bold;line-height:2.5;">Alerting system</div>
<div class="mw-collapsible-content">

:A user can subscribe to receive notification [[E-file_User#I_want_to_receive_notifications_by_mail|by email]] when conditions are met.
:It could be after reception of a feedback from the regulator or before the expiry of the [[#Certificate|Luxtrust certificate]].
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=AnnexIV></span>
<div style="font-weight:bold;line-height:2.5;">Annex IV</div>
<div class="mw-collapsible-content">

:Refers to Annex IV of the EU Alternative Investment Fund Managers Directive (AIFMD) Directive 2011/61/EU.
:It sets out the mandatory regulatory reporting template that Alternative Investment Fund Managers (AIFMs) must submit to their National Competent Authority
:[https://eur-lex.europa.eu/eli/dir/2011/61/oj/eng Directive - 2011/61 - EN - aifmd - EUR-Lex]
</div>
</div>

== B ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=BCL></span>
<div style="font-weight:bold;line-height:2.5;">BCL</div>
<div class="mw-collapsible-content">
:The Central Bank of Luxembourg (BCL) is Luxembourg’s monetary authority and a member of the Eurosystem and the European System of Central Banks.
</div>
</div>

== C ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CBDF></span>
<div style="font-weight:bold;line-height:2.5;">CBDF</div>
<div class="mw-collapsible-content">

:The ‘Cross Border Distribution Framework’ (CBDF) is a piece of legislation issued by ESMA with an original effective date of August 2021.
:The purpose is to establish a harmonised approach to distribution rules from EEA country to EEA country with less barriers to entry.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Certificate></span>
<div style="font-weight:bold;line-height:2.5;">Certificate</div>
<div class="mw-collapsible-content">

:As a secure channel, eFile needs a secure way to transmit reports and documents to regulators.
:A Luxtrust SSL certificate is required to encrypt documents before sending to '''Lux regulators'''.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CSSF></span>
<div style="font-weight:bold;line-height:2.5;">CSSF</div>
<div class="mw-collapsible-content">

:The Commission de Surveillance du Secteur Financier is a public institution which supervises the professionals and products of the Luxembourg financial sector.

</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=CRS></span>
<div style="font-weight:bold;line-height:2.5;">CRS</div>
<div class="mw-collapsible-content">

:The Common Reporting Standard (CRS) is a global regulation developed by the OECD for the automatic exchange of financial account information between countries to combat tax evasion. It requires financial institutions to identify foreign tax residents and report their financial account details to local tax authorities, who then share this data internationally.
: The local tax authorities in Luxembourg processing such reports is the [[#ACD|ACD]] - Administration des contributions directes
</div>
</div>

== E ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=eFile></span>
<div style="font-weight:bold;line-height:2.5;">e-File</div>
<div class="mw-collapsible-content">

:'''eFile''' is a secure regulatory filing platform that enables financial institutions to prepare, transmit, and monitor regulatory reports electronically.
:It supports report generation, manual or automated transmission, validation controls, and status follow‑up with authorities.
:The solution centralises [[Transmission_Module|filing activities]] , [[UCITS_Cross-Border_Notifications|notifications]], and auditability across multiple regulatory reporting use cases.
: On eFile there is a dedicated module [[UCITS_Cross-Border_Notifications|UCITS Cross-border Notification]]
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=EndUser></span>
<div style="font-weight:bold;line-height:2.5;">End-user</div>
<div class="mw-collapsible-content">

:Their main tasks include [[ReportGeneration|generating ]] or uploading reports, [[Transmission_Module|transmitting]] filings, and monitoring feedback and status via the [[#TransmissionFollowUp|Transmission Follow‑up]] module.
:This certificate is stored in the [[#Keystore|keystore]]
</div>
</div>

== F ==
<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=FATCA></span>
<div style="font-weight:bold;line-height:2.5;">FATCA</div>
<div class="mw-collapsible-content">
:FATCA (Foreign Account Tax Compliance Act) is a US law requiring foreign financial institutions, including those in Luxembourg, to report information about financial accounts held by U.S. persons to local tax authorities ( [[#ACD|ACD]] - Administration des contributions directes). The ACD then automatically exchanges this data with the US IRS to prevent tax evasion.
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Feedback></span>
<div style="font-weight:bold;line-height:2.5;">Feedback</div>
<div class="mw-collapsible-content">
:In the '''eFile''' context, feedback is the official response sent by the regulator after a report has been transmitted, indicating its processing status (e.g. accepted, compliant, or rejected).
:It is made available to [[EndUser|users]] via the [[EndUser|Transmission Follow‑up]] module and allows them to verify whether the filing has been correctly received and validated by the authority.
</div>
</div>

== K ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=Keystore></span>
<div style="font-weight:bold;line-height:2.5;">Keystore</div>
<div class="mw-collapsible-content">

:The keystore is a file containing the [[#Certificate|Luxtrust certificate]].
:This allow encryption and decryption of files to communicate with '''Lux regulators'''
:The keystore contains ''historical'' certificates to enable decryption of old filing
</div>
</div>

== R ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=ReportGeneration></span>
<div style="font-weight:bold;line-height:2.5;">Report Generation</div>
<div class="mw-collapsible-content">

:The '''Report Generation''' module in '''eFile''' allows users to prepare regulatory reports directly within the platform by entering required data.
:It performs controls such as mandatory field and data‑consistency [[ReportGeneration|to ensure reports comply]] with authority requirements before submission.
</div>
</div>

== S ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=S3></span>
<div style="font-weight:bold;line-height:2.5;">S3 key</div>
<div class="mw-collapsible-content">

:The '''S3 key system''' in eFile is a '''secure authentication mechanism''' used to transmit regulatory reports to authorities, '''replacing the legacy '''[[#Certificate|SSL]] / [[#Keystore|keystore ]] model for certain filings.
:It relies on S3 digital keys generated via the '''CSSF eDesk''' and imported into eFile, '''while keeping the user filing process unchanged within the platform.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SendingService></span>
<div style="font-weight:bold;line-height:2.5;">Sending Service</div>
<div class="mw-collapsible-content">

:The '''Sending Service''' is our [[Sending_Service_home|solution for the automatic transmission ]] of reports and documents to the authorities, by a simple deposit of files in a designated directory.
:It is particularly interesting '''for sending many documents.'''
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=SSO></span>
<div style="font-weight:bold;line-height:2.5;">SSO</div>
<div class="mw-collapsible-content">

:The '''Single Sign-On (SSO)''' aims to ease your user experience and the reinforce the security (with the introduction of MFA)
:For now, this feature is only suitable for human users (who needs to access the portal), Sending Service accounts can't used such feature.
:It allows you to '''log to other FEFI's application''' and '''replace the login / password''' connection method
</div>
</div>

== T ==

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionModule></span>
<div style="font-weight:bold;line-height:2.5;">Transmission module</div>
<div class="mw-collapsible-content">

:The '''Transmission module''' is the module to encrypt and send documents to Lux regulators such as CSSF, BCL....
:The module needs [[Transmission_Module|to be set with]] the [[#Keystore|keystore]] to work
</div>
</div>

<div class="mw-collapsible mw-collapsed" data-expandtext="Show" data-collapsetext="Hide" style="width:60%; overflow:visible; >
<span id=TransmissionFollowUp></span>
<div style="font-weight:bold;line-height:2.5;">Transmission Follow-up</div>
<div class="mw-collapsible-content">

:The '''Transmission Follow-up''' also called '''Transmission monitoring''' allows users to [[Transmission_Monitoring|track submitted reports and view feedback and status]] sent by regulatory authorities after transmission
</div>
</div>

Sending Service java-less version

2026-04-09T09:46:27Z

Cso: /* Step 2: Download the launcher. */

''<small>Page's last update : 30 May 2024</small>''
<div class="noprint" style="background-color:#FAFAFA; position:fixed; bottom:10%; right:0.25%; padding:0; margin:0;">
<span style="color:blue; border:0.3em outset #abd99f; padding:0.2em; font-weight:bolder; -moz-border-radius:8px; ">
[[#BackToTop|Back to the Top]]
</div>

''You can click on the picture.''
<imagemap>
File:SDjl_general.png|center|900px|alt=clickable image : form description| titre
rect 23 39 332 149 [[Sending_Service_java-less_version#Prerequisites | Prerequisites ]]
rect 425 91 678 182 [[Sending_Service_java-less_version#Purpose |Purpose]]
rect 703 3 911 96 [[Sending_Service_java-less_version#Manual_installation_using_command_prompt | Installation ]]
rect 782 110 1057 208 [[Sending_Service_java-less_version#Update_the_sending_service | Upgrade or change the configuration ]]
rect 47 264 413 350 [[Sending_Service_java-less_version#Administration_Interface | Using the administration interface ]]
rect 491 266 694 357 [[Sending_Service_java-less_version#Process_overview | Process ]]
rect 767 266 1056 349 [[Sending_Service_java-less_version#Sending_Folders | Folders ]]
rect 46 459 212 582 [[Sending_Service_java-less_version#Administration_Interface | through the administration interface]]
rect 246 566 470 669 [[Sending_Service_java-less_version#Logs| Is my sending service running ?]]
rect 387 457 514 531 [[Sending_Service_java-less_version#Stop_the_application | Stop ]]
rect 534 496 722 592 [[Sending_Service_java-less_version#Start_the_application | Start ]]
rect 803 455 969 546 [[Sending_Service_java-less_version#Submit_a_report | How can I submit a report ?]]
rect 987 508 1181 590 [[Sending_Service_java-less_version#Check_for_acknowledgment_and_feedbacks | Check my sends ]]
rect 730 600 950 700 [[Sending_Service_java-less_version#Solving known problems | Solutions ]]
desc none
</imagemap>

= Purpose =

The '''Sending Service''' is our solution for the '''automatic transmission''' of reports and documents to authorities.

It is an application consisting of a set of '''processes''' (called listeners) that periodically exchange files with authorities through a set of designated '''folders'''. Everything is configured via an '''administration interface'''.

This solution is useful if you have a '''large number of reports''' to submit or if the manual sending does not suit your needs.

Please be aware that, in this case you will have to provide the files yourself according to the authorities' file specifications.

This tool is usually <span style="color: #C00000">'''installed on a server'''</span> on your side.

With a suitable '''network mapping''', users can simply '''drop the file to be sent into the appropriate directory'''. It is then automatically '''encrypted and sent'''.

= Prerequisites =

*Internet access
*If you use a proxy, authorise outgoing calls to [https://www.e-file.lu www.e-file.lu]. Port 443 (HTTPS) must be open.
*<span style="color: #C00000">'''Windows Administrator rights''' </span> to install the Sending Service <span style="color: #C00000">on the computer</span> ''(Windows Start button > Control Panel > User Accounts > Manage User Accounts)''.
*'''OS''': Windows - ''Linux will be developed''
*Processor: Pentium 2 GHz or equivalent
*8 GB of RAM
*300 MB of free space on hard disk drive. Think of providing regular purges.
*500 MB of free space on hard disk drive for logs. Regular purges are necessary as well.
*A <span style="color: #C00000">'''Sending Service user''' </span>, ''for example: aacSD'', and its password, ''for example: formation'', have to be available [[E-file_Administration#e-file_administrator_functions_.28e-file_v1.29|'''=> e-file administration''']].
*The e-file account of the Sending Service user has to be linked to groups/modules, ''for example FATCA reporting + profile "Sending Service".''
*A valid <span style="color: #C00000">'''keystore''' </span>(keystore.ks) and its <span style="color: #C00000">'''password''' </span>must be available as soon your file must be encrypted. (You do not need a keystore anymore if all your reports are going through S3 API).
*The Sending Service user has to be properly configured in the e-file user administration tool in order to be able to receive <span style="color: #C00000">'''alerts''' </span> (receipt of acknowledgement and feedback files).

Note that you can find the prerequisites for the manual transmission there : [[Transmission_Module#System_requirements]]

= Sending service version 1 vs version 2 =
{| class="wikitable"
|+Differences between v1 and v2
!
!<span style="color: #21C8DB">v1</span>
!<span style="color: #21C8DB">v2</span>
|-
|needs Java
|x
|
|-
|support S3 protocol
|x
|x
|-
|allow pre-encrypted files send
|x
|
|-
|U11 enrichment
|x
|
|-
|export to XLS
|x
|
|-
|XLS to XML (TPTIBS)
|x
|
|-
|O4.x semi-automatic (txt to PDF)
|x
|not yet
|-
|allow O4.x PDF direct send
|x
|x
|-
|user interface for configuration
|
|x
|-
|deep level (deposit in sub-directories)
|x
|x
|-
|automatic upgrade
|
|x
|-
|self-managable heartbeat monitoring
|
|x
|-
|Linux-compatible
|x
|not yet
|-
|unit of time used in set up
|milliseconds
|minutes
|}

= Process overview =
The sending service can be run in the <u>console mode</u> through '''launcher.exe'''. It then runs in a line-command window which must stay open.

On the first launch see [[#Manual_installation_using_command_prompt|installation]] paragraph to locate it, otherwise [[#Start_the_application|start]].

The sending service can also be installed as a <u>Windows' service</u> through '''''run-as-service.bat'''''. Once done, it is visible into the Windows' services list. Then it is launched on the workstation boot.

See chapter [[#Start_the_application|Start the application]].

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">''<small>Click to see more technical details</small>''</div>
<div class="mw-collapsible-content">
</br></br>
''launcher.exe'' is the launcher application. It launches and updates the main application described below. It contains proxy and environment configuration files.

''<nowiki>get</nowiki>-service-status.bat'' displays the status of the sending service when it is installed as a Windows service

''remove-service.bat'' uninstalls the Windows service

''run-as-service.bat'' installs then runs the sending service as a Windows service

''sending-service.exe'' is located in the .\system\bin folder. This is the main application, used to send documents and containing all the business rules and configuration files linked to the operation of the application, such as dictionary-xsd and dictionary-workflow.

<span id="folder-hierarchy"></span>
== Folder hierarchy ==

Once installation is complete, three sub-folders will be present:

'''system''': this is the folder containing the technical elements of the application, and contains also three sub-folders:

::'''bin''': contains the main application executable

::'''config''': contains all client configuration files

::'''log''': contains all logs generated during application execution

'''sendingservice''': this is the folder containing all the sub-folders in which we will place our files for sending.<br />
For example, in the default configuration, if you want to send a KID file, you'll need to save the file in the following folder: ''sendingservice\fundregistration\luxembourg\opc''

'''tmp''': This is the folder containing all temporary files related to the application's operation.

</div>
</div>

<span id="logsy"></span>
== Logs ==
Each process creates its own log.</br>
sending-service.exe creates '''service-deposant-''timestamp''.log''' into .\system\log : it mainly contains information on the processing of your reports </br>
launcher.exe creates '''launcher-''timestamp''.log into .\log''' : it contains in particular information about the installation process</br>

[[File:SDjl_logs.png|400px|where are the log files ?]]

In case you think something goes wrong, you can open these files into a text editor and check if you see error messages. Also send them to us if you need us to check for you.

For a continuous monitoring, see also [[#Details_on_heartbeat_system]]

Running as a Windows' service, you can check the sending service's status launching '''''<nowiki>get</nowiki>-service-status.bat'''''

<span id="start-the-application"></span>

== Start the application ==

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the console mode... click</div>
<div class="mw-collapsible-content">
</br></br>
Once the application is installed:

Double-click [[File:SDjl_2.png|169x25px]] (''if you get this message:[[File:SDjl_3.png|264x89px|A windows's error message]], [[#protect_error|solve it]]'')

</div>
</div>

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the windows service mode... click</div>
<div class="mw-collapsible-content">
</br></br>
Once the sending service is installed as a Windows' service, use the windows' services app to start it :

[[File:SDjl_StartStopService.png|StartStopService|800px]]

</div>
</div>

<span id="stop-the-process"></span>

== Stop the application ==
<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the console mode... click</div>
<div class="mw-collapsible-content">
</br></br>

hit the keys '''Ctrl+C'''

</div>
</div>

<div class="mw-collapsible mw-collapsed" >
<div class="mw-collapsible-toggle" style="float:left; margin-left:0; margin-right:1em;">In the windows service mode... click</div>
<div class="mw-collapsible-content">
</br></br>

If the sending service is running as a Windows' service, use the windows' services app to stop it :

[[File:SDjl_StartStopService.png|StartStopService|800px]]

</div>
</div>

<span id="administration-interface"></span>

= Administration Interface =

''New : The former .properties file is no longer a file onto your disk but the data are stored in our database and you can access them through the administration interface.''

In the administration interface, you can retrieve all the parameters you can set up. Note that some of them have default values and some are set up when the installation is done. You can make all the changes needed.

Sign in with the sending service account (or as an administrator) and click [[File:SDjl_8.png|194x55px|the administration module access button]]

then [[File:SDjl_9.png|158x37px]], you get :

[[File:SDjl_10.png|800px|the sending services control panel]]

Click the name of the sending service to change, click [[File:SDjl_11.png|47x39px]] to go back to the list.

[[File:SDjl_12.png|800px|the details' control panel]]

To change a value, click [[File:SDjl_13.png|60x39px|the edit button]], make your changes then save or discard.

[[File:SDjl_14.png|349x46px|group of three buttons]]

The ‘edit all workflows’ button, allow you to make massive changes in one shot.

Once the changes saves, you will get: [[File:SDjl_15.png|309x59px|a positive answer]]

The buttons [[File:SDjl_16.png|193x39px]], respectively exporting/importing the properties to/from .json format : to backup, to move from UAT to production or to import manual changes onto properties.

Note

* the automatic update set up:<br />
[[File:SDjl_17.png|246x46px]]<br />
This is related to the sending service’s version delivered by our IT team. Click the icon to change the automatic update’s status.
* the categories of parameters: [[File:SDjl_18.png|377x84px|the parameters categories menu]]
* the [[File:SDjl_19.png|137x50px|the expand button]] button

<span id="details-on-workflows-part"></span>
== Details on workflows part ==

Regarding the workflows, each one takes care of specific reports. You must enable those you want the sending service to send.

''For example, to send'' U11 reports'', you must enable the'' reporting_u ''workflow, the active box must be ticked, and a folder must be entered, you can keep the default one or change it. The'' intervalTimeInMinute ''is the frequency with which the directory will be scanned.''

[[File:SDjl_21.png|601x203px|example reporting U details]]

You can find the reports and their matching sending service workflow in our [[ProductCoverage|product coverage page]].

<span id="details-on-heartbeat-system"></span>

== Details on heartbeat system ==

The heartbeat is a monitoring system to check whether the sending service is still up or not. It pings the sending service at the chosen frequency and send an alert e-mail if the sending service doesn’t answer.

In the ‘properties’ category, you can set it up or down by ticking the box or not, and choose the frequency or the monitoring.

[[File:SDjl_22.png|601x338px|Heartbeat activation]]

In the ‘Heartbeat’ section, you can find statistics on heartbeat running and you can choose who will receive an alert e-mail when needed.

[[File:SDjl_23.png|800px|Heartbeat monitoring]]

<span id="section"></span>

= Manual installation using command prompt =
<span id="step-1-Stop_former"></span>
== <u>Step 1</u>: Stop the former instance ==

Be sure that no former instance of the sending service is running on the same environment. If so, [[Sending_Service_java-less_version#Stop_the_application | stop ]] it.

''If you install to replace the version with java, plan to use a new directory.''

<span id="step-2-download-the-launcher."></span>

== <u>Step 2</u>: Download the launcher. ==

The official version is always on the production site. You will be asked for homologation or production environment during the installation process. </br>To monitor and manage the properties, use the administration module on the relative website.

Connect to www.e-file.lu as the sending service (or as an administrator).

In the administration module, Sending service management:

[[File:V2_access.png|332x231px]]

Click:

[[File:SDjl_25.png|604x172px]]

The launcher will be downloaded into your default folder:

[[File:SDjl_26.png|262x101px]]

<blockquote>An alternative is to use this direct link, after logging into e-file :https://www.e-file.lu/fsq-graph/file/download/launcher-version/download?distribution=WINDOWS</blockquote><span id="step-3-install-the-new-sending-service-with-the-launcher"></span>

== <u>Step 3</u>: Install the new Sending Service with the launcher ==

<span id="copy-launcher.exe"></span>
=== copy ''launcher.exe'' ===
into the folder where you want to install the sending service

<span id="open-launcher.exe"></span>
=== Open launcher.exe ===
Double-click it [[File:SDjl_2.png|169x25px]] (''if you get this message:[[File:SDjl_3.png|264x89px|A windows's error message]], [[#protect_error|solve it]]'')

You will be asked:

<span id="enter-y-yes-or-n-no-for-the-question-are-you-using-a-proxy"></span>

=== Enter Y (yes) or N (no) for the question: Are you using a proxy? ===
[[File:SDjl_27.png|222x29px|question about the proxy]]

<span id="enter-the-environment-production-or-homologation"></span>
=== Enter the environment: PRODUCTION or HOMOLOGATION ===
The name must be entirely typed</br>
[[File:SDjl_28.png|604x22px]]

The sending service will be downloaded, wait a little.

[[File:SDjl_29.png|604x147px|See the progression bars]]

<span id="enter-username"></span>
=== Enter username ===
Enter the sending service’s account user name (the one usually ended by ...SD)

<span id="enter-the-username-password"></span>

=== Enter the username password ===
<span id="either-if-a-properties-config-file-is-found-on-the-server-and-you-want-to-use-it"></span>

=== Either: it is not the first installation : a properties file is found on the server ===

When you have already done an installation in the past, even if you have deleted it on your workstation, your previous setup is saved on our servers. So you will be asked if you want to overwrite it :

Enter N (no) for the question: ''overwrite the existing properties config file'', if you want to keep the previous setup.

Enter the password of your keystore.

<span id="or-if-no-properties-config-file-is-found-on-the-server-or-you-want-to-overwrite-the-existing-one"></span>

=== Or: If no properties file is found on the server OR you want to overwrite the existing one ===

Enter Y (yes) for the question: ''overwrite the existing properties config file''.

[[File:SDjl_30.png|604x15px]]

Then you will be asked :

<span id="enter-the-root-folder"></span>
: <span style="color:#21b8b5">'''Enter the root folder '''</span>
::It is the folder where you want the sending service to be installed: it must already exist.
::Entering none will take the current one.
::It is in this folder that the tree structure of sending folders will be generated. After that, for each upload there will be a concatenation between the root folder and the subfolder for each workflow. For example Let's take the rootFolder: "C:\NewSendingService" and the folder for the Key Investor Document "sendingservice/fundregistration/luxembourg/opc". The service will then fetch the documents with the path "C:\NewSendingService\sendingservice\fundregistration\luxembourg\opc". Be careful not to put an \ at the end of the specified path

<span id="enter-the-configuration-name"></span>
: <span style="color:#21b8b5">'''Enter the configuration name '''</span>
::Choose a name for your setup.

<span id="enter-your-keystore-file-path-optional."></span>
: <span style="color:#21b8b5">'''Enter your keystore file path (optional).'''</span>
::Please note that you must enter your keystore to transmit to Luxembourg authorities.

<span id="enter-authentication-cssf-optional"></span>
: <span style="color:#21b8b5">'''Enter Authentication CSSF (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-authentication-bcl-optional"></span>
: <span style="color:#21b8b5">'''Enter Authentication BCL (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-the-password-optional"></span>
: <span style="color:#21b8b5">'''Enter the password (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-authentication-code-optional"></span>
: <span style="color:#21b8b5">'''Enter authentication code (optional)'''</span>
::This is used for O4.1 and O4.2 reports only.

<span id="enter-y-yes-or-n-no-for-the-question-do-you-want-to-close-the-app-after-installation"></span>
: <span style="color:#21b8b5">'''Enter Y (yes) or N (no) for the question: Do you want to close the app after installation ?'''</span>
::Yes means that only the installation will be done.
::No means that the sending service itself will be run after the installation and starts to file reports.

The process will continue, installing all the xsd files …

You can close the window, click the right-corner red cross.

<span id="update-the-sending-service"></span>

= Update the sending service =

== Change your setup ==

To change the sending service's setup: '''workflows; heartbeat, ... and also groups and permissions'''
* use the administration interface
* then [[#Stop_the_application|stop the application]] and [[#Start_the_application|start]] it again.

To change only the '''proxy''' setup
* In the folder .\system\config, delete the ''proxy-conf.json''
* then [[#Stop_the_application|stop the application]]
* On the root folder, launch ''launcher'' again, keep the existing properties config file.
* If you want to use the Windows' service, exit launcher (Ctrl+C) and [[#Start_the_application|restart]].

To change only one or several '''passwords'''

Note that the passwords are encrypted and asked just one time at the first installation. If you have to change them, you must install the whole application again :
* In the folder .\system\config, delete all the .json files (you can keep the ''proxy-conf.json'' and the ''environment.json'' files if they won't change)
* then [[#Stop_the_application|stop the application]]
* On the root folder, launch ''launcher'' again, keep the existing properties config file.
* If you want to use the Windows' service, exit launcher (Ctrl+C) and [[#Start_the_application|restart]].

<span id="upgrade-the-application"></span>

== Upgrade the application ==
=== Automatic upgrade===

This feature concerns the application updates affecting the sending service (SD) itself and that are applicable to all clients / users.

''Short description:''

Whenever the sending service starts, restarts, and every 30 minutes when it is up and running, it will check for updates. If an update is detected, and automatic update is selected (you can modify the value in the admin module page), the SD will stop the current process, reinstall the new version and rerun the process automatically. After a successful (or unsuccessful) update a notification will be sent per email.

If the client did not subscribe for automatic application updates and a new version of SD is available, an email will be sent to the client requesting them to update the SD. The client will then have to rerun the application and install the new version.

If the client does not update its SD in a specific timeframe, the sending service will stop running until it has been updated.

===Manual upgrade===

When a new version is available from out IT team: [[#Stop_the_application|stop the application]] then [[#Start_the_application|start]] it again through the launcher.exe.

<span id="submit-a-report"></span>

=Submit a report=

To send a report just copy it in the relevant folder depending on its type.

See the default sending folders tree:

[[File:SDjl_32.png|195x333px]]

You can relocate this folders tree to adapt it to your needs, using the administration interface to change the setup.

Then either enter ''root folder + relative tree folder path'' or ''empty root folder'' and enter an ''absolute path'' for the listener :

[[File:SDjl_ExplicPathFolder.png]]

<span id="sending-folders"></span>
==Default Sending Folders==

Scroll this list to find the sending type you need and where you must copy your reports for them to be processed:

<div style="height:300px; width:auto; overflow-y:scroll">

{| class="wikitable table-filterable sortable"
|+<span style="white-space:nowrap"></span>
|- <div style="position:sticky;top:-1px;z-index:10">
! width="44%" style="background-color:#21b8b5" |Sending type / type d'envoi
! width="55%" style="background-color:#21b8b5" | To be copied into / à déposer dans

|-
|08/371 FIS Prospectus
|sendingservice/fundregistration/luxembourg/fis
|-
| 08/371 FIS Reports
|sendingservice/fundregistration/luxembourg/fis
|-
|Non-LU UCI Registration
|sendingservice/fundregistration/luxembourg/fundsnotlu
|-
|Other closing docs of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Management letters of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Fin rep of GFI
|sendingservice/fundregistration/luxembourg/gfi
|-
|Key Investor Document
|sendingservice/fundregistration/luxembourg/opc
|-
|Management letters for CSSF 09/423
|sendingservice/fundregistration/luxembourg/opc
|-
|CSSF Attestation
|sendingservice/fundregistration/luxembourg/opc
|-
|Management regulation status
|sendingservice/fundregistration/luxembourg/opc
|-
|Notification Full
|sendingservice/fundregistration/luxembourg/opc
|-
|Long forms for CSSF 09/423
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 UCI Prospectus
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 Report
|sendingservice/fundregistration/luxembourg/opc
|-
|08/371 report not in 08/371
|sendingservice/fundregistration/luxembourg/other
|-
|BCL report for insurances
|sendingservice/regulatoryreporting/luxembourg
|-
|BCL SHS
| sendingservice/regulatoryreporting/luxembourg
|-
|AIF Reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting_s112-l
|sendingservice/regulatoryreporting/luxembourg
|-
|MIFIR reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting U
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting EDIFACT
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting IORP
| sendingservice/regulatoryreporting/luxembourg
|-
|Reporting CSDR
|sendingservice/regulatoryreporting/luxembourg
|-
|FATCA Report
|sendingservice/regulatoryreporting/luxembourg
|-
|CRS Report
| sendingservice/regulatoryreporting/luxembourg
|-
|FINREP
|sendingservice/regulatoryreporting/luxembourg
|-
|SICAR Reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|PSF Report
|sendingservice/regulatoryreporting/luxembourg
|-
|COREP Report
|sendingservice/regulatoryreporting/luxembourg
|-
|EME Report
|sendingservice/regulatoryreporting/luxembourg
|-
|EDP Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Credit institution reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Management company report
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting Money Market Fund
|sendingservice/regulatoryreporting/luxembourg
|-
|CSSF enquiry
|sendingservice/regulatoryreporting/luxembourg
|-
| TAF MIFID Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport distinct solvabilité 2 du réviseur
| sendingservice/regulatoryreporting/luxembourg
|-
|Distinct solvency company Report
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport Narratif (Réviseur)
|sendingservice/regulatoryreporting/luxembourg
|-
|Rapport Narratif (compagnie)
|sendingservice/regulatoryreporting/luxembourg
|-
|Solvency II reporting
|sendingservice/regulatoryreporting/luxembourg
|-
|Titrisation Vehicles
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting TPT
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting securities by securities of issuing companies
|sendingservice/regulatoryreporting/luxembourg
|-
|Issuing companies reporting
|sendingservice/regulatoryreporting/luxembourg
|-
| Payment’s balance
|sendingservice/regulatoryreporting/luxembourg
|-
| AnaCredit
|sendingservice/regulatoryreporting/luxembourg
|-
|Security by Security banks
|sendingservice/regulatoryreporting/luxembourg
|-
|BCL statistics
|sendingservice/regulatoryreporting/luxembourg
|-
|Data payment collection
|sendingservice/regulatoryreporting/luxembourg
|-
|Reporting S
|sendingservice/regulatoryreporting/luxembourg
|-
|Various correspondence (OTH)
|sendingservice/regulatoryreporting/luxembourg/otherbcl
|-
|Other reporting for CSSF
|sendingservice/regulatoryreporting/luxembourg/othercssf
|-
|Reporting O
|sendingservice/regulatoryreporting/luxembourg/reporting_o
|-
|Reporting ICS
|sendingservice/regulatoryreporting/luxembourg/
|-
|DORA Incident Reporting
|sendingservice/regulatoryreporting/luxembourg/
|-
|DORA Register of Information
|sendingservice/regulatoryreporting/luxembourg/
|-
|Self-assessment questionnaire PDAOFI
|sendingservice/regulatoryreporting/luxembourg/
|}
</div>

<span id="check-for-acknowledgment-and-feedbacks"></span>

=Check for acknowledgment and feedbacks=

Once a report is sent, it is renamed as .trt and move into an auto-generated subfolder called ''reporttransmitted, ''
a file with extension .acq is also created as an acknowledgement.

[[File:SDjl_33.png|276x70px|the reporttransmitted folder]]

If an error occurs, you get a file with extension ''.err''. Open it and read the messages.

The feedbacks from the authority will come into ''feedbacks.'' Remember to read them.

<span id="transmission-following"></span>
==Transmission following==

Here are the default transmission follow up files that are created depending on the state in the transmission workflow.

{|
! width="13%" |'''File extension'''
! width="86%" | '''Description'''
|-
| '''.trt'''
|
<u>Example </u>: file processing of '''FileName.ext'''

Once the file has been dropped into the appropriate folder, the Sending Service will start processing it and rename it as follows:

'''FileName.ext_YYYYMMDDhhmmssmmm.trt'''
|-
|'''.acq'''
|
Once the processing finished an '''.acq''' file will be generated in the same folder by the Sending Service in order to confirm the transmission:

'''FileName.ext_YYYYMMDDhhmmssmmm.acq'''
|-
|'''.err'''
|
An '''.err file is created in case or an error:'''

'''FileName.ext_YYYYMMDDhhmmssmmm.err'''

Please open this file and analyse the error message.
|}

<span id="feedback-files-replies-folder"></span>
==Feedback files (Replies folder)==

For some reporting, the administration will give you a more detailed feedback. The feedbacks from the authority will come into ''feedbacks.''

<s>By default, <u>feedback files</u> are dropped into '''Replies''' sub-folders. '''Replies''' folders are created dynamically in the initial transmission folder of the files. They only appear when feedback files, sent by the supervisory authorities, have to be stored. If the folder is deleted, it will be automatically recreated upon receipt of new feedback files.

The name and location of the '''Replies''' folder may be configured differently from the implementation of the solution with your company’s project coordinator </s>

{|
! width="10%" |'''Autority'''
! width="89%" |'''Description'''
|-
|'''CSSF'''
|
Feedback files generated and sent by the CSSF.

Please click the picture below to access the '''Naming convention for CSSF reportings''' document:

[[File:SDjl_34.png|500x135px|A close-up of a screen Description automatically generated]]
|-
|'''BCL'''
|
Feedback files generated and sent by the BCL.

The BCL sends feedback with the following naming convention :

FDBTECH_[OK/KO]_[YYYYMMDD]_[SENT FILE NAME]_[RANDOM CARACTERS].xml

With

<ul>
<li> <blockquote><p>[OK/KO] : replaced either by OK (if the files has been transmitted and processed successfully) or KO (if there has been an error)</p></blockquote></li>
<li><blockquote><p>[YYYYMMDD] : replaced by the date of the feedback</p></blockquote></li>
<li><blockquote><p>[SENT FILE NAME] : replaced by the complete name of the original file (including it's extension)</p></blockquote> </li>
<li><blockquote><p>[RANDOM CARACTERS] : replaced by a random and unique caracters.</p></blockquote></li></ul>
|}

<ul>
<li><blockquote><p>'''For other reporting''' (08/371 / VNI...), '''there is no additional acknowledgment'''.</p></blockquote></li></ul>

This means that only '''acq''' will be created.

'''<u>Conclusion</u>''' : '''Checking that both trt and acq files were generated is a good way to ensure the good working of the Sending Service'''. Doing this way, you can be sure that your data was properly sent and '''e-file will be in charge of forwarding them to authorities'''.

=Solving known problems=

<span id="protect_error"></span>
*If you get this when double-clicking the launch.exe :

[[File:SDjl_3.png|552x140px|Protection Error Windows]]

Right-click the launch.exe file, then tick unblock : [[File:Sdjl_LauncherProperties.png|Protection Error Windows Solution]]

Or

click the address bar in the file explorer: [[File:SDjl_4.png|409x40px]] [[File:SDjl_5.png|335x33px|the adress bar]]

type ''cmd,'' [[File:SDjl_6.png|137x71px|where to type cmd]] then type ''launcher'' [[File:SDjl_7.png|379x83px|the command line windows]]

<span id="process_blocked"></span>
*Sometimes in console mode, the process seems to be blocked :

[[File:SDjl_BlockedProcessExamples.png|552x140px|Blocked processes]]

First try to hit ''Enter'' or ''space''. <br> If it is still blocked, you must stop it (CTRL+C) and [[#Start_the_application| restart it]].

*Error message when installing :

[[File:SDjl_InstallErr1.png|800px|Installation error message 1]]

Hit ''Enter'' twice, the program will ask for the username again, and go on.

*Error message after stop and start (401):

[[File:SDjl_InstallErr2_401.png|800px|Installation error message 2]]

The sending service password may have changed. You must install it again.

*Setup changes not applied despite being saved

After each change through the administration module, please [[#Stop_the_application|stop]] and [[#Start_the_application|start]] the sending service again.