← Luxembourg

Reminder – New U1.1 reporting transmission procedures

Published on 15 November 2024 Email this Share this on LinkedIn Share this on Facebook Communiqué Reminder – New U1.1 reporting transmission procedures (published on 12 September 2024, updated on 31 October 2024 and 15 November 2024) As announced in the 5 April 2024 communication regarding the direct submission of filings to the CSSF, the methods for transmitting U1.1 reports will change from 15 November 2024. The expected reports may now be transmitted using the following methods: A dedicated eDesk procedure An API solution based on the submission of XML reports via the S3 protocol A user guide detailing the submission procedures for the U1.1 reports is available below. Please note that it will still be possible to transmit U1.1 reports via external transmission channels until 28 February 2025. For any questions, please contact edesk@cssf.lu. 3 June 2016 - Updated on 27 April 2026 Guidelines on the U1.1 reporting Version 6.7 Technical document PDF (1.23Mb) Relevant for Investment companies in risk capital (SICARs) Specialised investment funds (SIFs) Undertakings for collective investment in transferable securities (UCITS) Undertakings for collective investment subject to Part II of the Law of 17 December 2010 (Part II UCIs) Guidelines on the U1.1 reporting User Guide Guidelines on the U1.1 reporting User Guide Update information Date Version Changes 27/04/2026 6.7 Addition of control RINVAL02 19/01/2026 6.6 - Correction of Annex 2, column NR, items 2040-2110 Added "report's status" information in chapter 4.3 31/12/2025 6.5 - Item 2110: updated description Added Annex 2 Correction of minor typos (not highlighted) - Addition of the "Definition of the Reporting Declarant" and information concerning delegation Addition of information concerning the new dashboards available on eDesk module Deletion of controls RNOM01 – RNOM15, RNOM18, RNOM19, RNOM21, R2080B, R4050C, R6041A, R1020A, RINT03, RFMAN01-RFMAN03 (they are integrated in new rules) Modification of R5090A Change of severity of the controls (shown in yellow) Addition of new controls (RNOM24, RNOM25, R2040B, R4040B, R1020E, RNA03, RNA04, RNA05, RU25[XX]). 16/12/2025 6.4 - 02/10/2025 6.3 Deletion of rule R5100B. 25/09/2025 6.2 Addition of controls as stated in February 2025 12/02/2025 6.1 Addition of the mention of the removal of external channels from the transmission methods 11/02/2025 6.0 Update following publication of Circular CSSF 24/866, applicable from December 2025. The list of additional controls will be published in due course. 18/11/2024 5.1 Addition of information concerning XML format (cf. chapter 2.2) 15/11/2024 5.0 Addition of eDesk and API transmission channels GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 2/51 Table of CONTENTS 1. Specifications of the U1.1 reporting files ........................................................................ 4 1.1. U1.1 reporting format............................................................................................... 4 1.2. The content of the U1.1 reporting file ......................................................................... 4 1.2.1. Authorisation date of a UCI.................................................................................. 4 1.2.2. Authorisation date of a sub-fund .......................................................................... 4 1.2.3. Section 1: General information on the report and the sender ................................... 4 1.2.4. Section 2: General information on the UCI ............................................................ 8 1.2.5. Section 3: Financial information of the UCI in the base currency of the UCI ............. 14 1.2.6. Section 4: General information on the unit/share class (to be filled in separately for each unit/share class) .................................................................................................. 15 1.2.7. Section 5: Financial information on the unit/share class for the reference month (to be filled in separately for each unit/share class) .................................................................. 18 1.2.8. Section 6: Information on the investment income and expenses for the reference month in the base currency of the UCI ........................................................................... 24 2. Definition of the Reporting Declarant........................................................................... 30 3. Delegation management ............................................................................................ 31 4. Transmission of the U1.1 reporting files to the CSSF ..................................................... 35 4.1. Transmission channels pursuant to Circular CSSF 23/833 ........................................... 35 4.1.1. Application Programming Interface (API) ............................................................. 35 4.1.2. eDesk ............................................................................................................. 35 4.2. Sending of U1.1 reporting files ................................................................................ 37 4.3. CSSF feedback files ................................................................................................ 38 5. Contact information .................................................................................................. 41 Annex 1: List of controls concerning U1.1 reporting file ......................................................... 42 Annex 2: U1.1 reporting item description ............................................................................. 50 GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 3/51 1. Specifications of the U1.1 reporting files 1.1. U1.1 reporting format The U1.1 reporting must be transmitted in the XML format. The technical description (XSD) of the files to be transmitted in the context of the U1.1 reporting can be downloaded on the CSSF website (https://www.cssf.lu/en/Document/schemas-xml-u-1-1/ for reference period until 11/2025 and https://www.cssf.lu/en/Document/schemas-xml-u1-1applicable-as-of-the-12-2025-reference-period/ for reference period as of 12/2025). 1.2. The content of the U1.1 reporting file This paragraph contains definitions, explanations and examples in relation to the items referred to in the Annex of Circular CSSF 15/627. 1.2.1. Authorisation date of a UCI Each Undertaking for collective investment (UCI) authorised by the CSSF and entered on the official list is notified by the CSSF and the respective authorisation date is communicated to the UCI. This authorisation date is, in principle, the date of incorporation of the investment company or the date of the management regulations of the common fund. 1.2.2. Authorisation date of a sub-fund When a new umbrella UCI is authorised, all the sub-funds included in the very first offering document have the same authorisation date as the UCI. In the case of a new sub-fund of an existing umbrella UCI, the authorisation date of the sub-fund is notified by the CSSF to the UCI. In the remainder of this document, the term "UCI" is used for both a non-umbrella fund and a subfund. Where necessary, a distinction will be made between a UCI and a sub-fund. 1.2.3. Section 1: General information on the report and the sender 1.2.3.1. 1010 - Reference month [mandatory] All UCIs are requested to submit to the CSSF monthly information on, among other things, their financial situation at the end of a month (e.g. total net asset value) or for the whole month (e.g. proceeds from all units/shares issued). The year and month to which the requested information relates, must be indicated in the field "reference month" in the format "YYYYMM", where "YYYY" stands for the year and "MM" for the month. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 4/51 Example: If a UCI submits its U1.1 reporting for December 2025, the field "reference month" must be filled in with the value "202512". 1.2.3.2. 1020 - Reporting status [mandatory] A UCI must provide the most accurate and up-to-date information for any given reference month. U1.1 reporting can only have three statuses: 1) "null report"; 2) "final report" or; 3) "provisional report". 1) Any UCI that has been authorised by the CSSF but that has not yet been launched, must submit a "null report" as from the reference month during which it was authorised. In this case, the UCI must only report static data, i.e. items 1010 to 2030. Items 2040 to 2110 are optional. For the sake of clarity, it should be noted that the fact of accepting only capital commitments does not impact the transmission of a "null report" 1. Example 1: Sub-fund 1 of the UCI A receives its authorisation on 15 December 2025. The UCI does not receive any subscription since its authorisation and for the next 18 months (according to Circular CSSF 12/540, the fund has 18 months to receive the first subscriptions). Reference Reporting Deadline for Comment on the content of the month status submission reporting file null report 10 calendar days at the Only items 1010 to 2030 to be latest after the last day filled in 202512 to of the reference month 202705 202706 null report 10 July 2027 at the Only items 1010 to 2030 to be latest filled in and the "closing date" (item 2080) to be filled in with "reason for closing" (item 2090) being "The UCI is definitely closed" 2) A UCI must submit a U1.1 reporting with the status "final report" when the financial information included in the reporting file is based on data relating to the reference month. This does not exclude the possibility for a UCI to submit an update or a correction of this U1.1 reporting with the same status after the deadline, if necessary. If the UCI’s net asset value calculation is less frequent than monthly (e.g. quarterly, semiannually or annually), the UCI must submit a U1.1 reporting including estimated financial information based on the accounting records (i.e. unofficial net asset value based on the last In other words, commitments are not considered as subscriptions. Consequently, neither a "provisional" nor a "final" report is requested. 1 GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 5/51 available information/valuation prices) with the status "final report" for the reference months other than the reference months for which an official net asset value is calculated in accordance with the net asset value calculation frequency laid down in the offering document. For the reference months for which an official net asset value is calculated, UCIs must provide a "final report" based on the financial information underlying the official net asset value. Example 2: UCI B receives its authorisation on 15 December 2025. The first capital commitments are received on 28 January 2026. The first subscriptions (e.g. capital call cash flow) are received on 5 February 2026. The fund calculates its net asset value on a quarterly basis, i.e. 31 March, 30 June, 30 September and 31 December. Financial figures for these reference months are available before the deadline for the U1.1 reporting. Reference Reporting Deadline for Comment on the content of month status submission the reporting file null report 10 January 2026 Only items 1010 to 2030 to be at the latest filled in 10 February 2026 Only items 1010 to 2030 to be at the latest filled in 10 March 2026 at The UCI must provide estimated the latest data based on the accounting 202512 202601 202602 null report final report records (i.e. unofficial net asset value based on last available information/ valuation prices) 202603 202604 final report final report 10 April 2026 at Official figures calculated on 31 the latest March 2026 10 May 2026 at The UCI must provide estimated the latest data based on the accounting records (i.e. unofficial net asset value based on last available information/valuation prices) Example 3: UCI C calculates its net asset value on a daily basis. On 20 April 2026, after the deadline for submitting the monthly report for March 2026 on 10 April 2026, the UCI must adjust financial data for this reference month. On 10 April 2026 at the latest, the UCI must transmit a "final report" for March 2026. On 20 April 2026, the UCI must submit a revised "final report" for March 2026. Example 4: UCI D calculates its net asset value on a weekly basis, e.g. every Friday. For the reference month May 2026, the UCI calculates its NAV dated 5 May 2026, 12 May 2026, 19 May 2026, 26 May 2026 and 2 June 2026. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 6/51 On 10 June 2026 at the latest, the UCI must transmit a "final report" for May 2026 based on the financial information underlying the official net asset value as of 26 May 2026. 3) A UCI must submit a U1.1 reporting with the status "provisional report" if the financial information included in the reporting file is not based on data relating to the reference month. This status must typically be used for UCIs with a reporting less frequent than weekly when final valuation prices are not available within the deadline for a reference month where an official net asset value must be calculated. Example 5: UCI E calculates its net asset value on an annual basis. The process to get the valuation of all assets takes two months. Reference Reporting Deadline for Comment on the content of the month status submission reporting file provisional 10 January 2026 The UCI must provide estimated data report at the latest based on the accounting records (i.e. 202512 unofficial net asset value based on last available information/valuation prices) 202601 provisional 10 February 2026 The UCI must provide estimated data report at the latest based on the accounting records (i.e. unofficial net asset value based on last available information/valuation prices) Final figures for 2025 available at the end of February 2026 202512 final report As soon as final Official figures for 2025 figures for 2025 are available 202601 final report As soon as final The UCI must provide estimated data figures for 2025 based on the accounting records (i.e. are available unofficial net asset value based on last available information/valuation prices) thereby using at least the official figures for the end of 2025 202602 final report 10 March 2026 at The UCI must provide estimated data the latest based on the accounting records (i.e. unofficial net asset value based on last available information/valuation prices) thereby using at least the official figures for the end of 2025 1.2.3.3. 1030 - CSSF code of the sender [mandatory] This item refers to the CSSF code of the sender of the U1.1 reporting. The CSSF code consists of one letter or number (depending on the CSSF status of the sender) and 8 digits for the entity number. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 7/51 Example: If the "Bank XYZ" submits the U1.1 reporting, its CSSF code is derived from its status as a bank (i.e. the letter "B") and its number (e.g. "1" which must be filled in with 7 digits of "0" before the number "1"). In other words, "Bank XYZ" must enter "B00000001" in the field "CSSF code of the sender". 1.2.3.4. 1031 – Intentionally left blank This item is not used for the U1.1 report but is displayed to mirror the BCL report S 2.20 schema. 1.2.3.5. 1032 – Intentionally left blank This item is not used for the U1.1 report but is displayed to mirror the BCL report S 2.20 schema. 1.2.3.6. 1040 - Name of the employee and phone number [mandatory for at least one contact person] This item refers to the name and the telephone number of the person responsible for the transmission of the U1.1 reporting to the CSSF and who can answer CSSF queries related to the reporting. 1.2.3.7. 1050 - Email address [mandatory for at least one contact person] This item refers to the email address of the person(

  1. s)responsible for the transmission of the U1.1 reporting to the CSSF. Items 1040 and 1050 are linked. It is mandatory to indicate at least one contact person. Of course, each sender can fill in data for more than one contact person. 1.2.4. Section 2: General information on the UCI 1.2.4.1. 2010 - CSSF code of the UCI (CSSF code of the entity and CSSF code of the sub-fund) [mandatory] This item refers to the UCI identifier attributed by the CSSF using the format FMMMMMMMM_CCCCCCCC, where: • "F" is to be replaced by either the constant value "O" (for UCIs subject to the Law of 17 December 2010 on undertakings for collective investment or the Law of 13 February 2007 on specialised investment funds) or "K" (for SICARs subject to the Law of 15 June 2004); • "MMMMMMMM" is the identification number of the UCI (preceded by zeros when the number has less than 8 digits); GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 8/51 • • followed by "_" (underscore); and where "CCCCCCCC" is the identification number of the sub-fund (preceded by zeros when the number has less than 8 digits, or "00000000" if the UCI in not an umbrella UCI). The CSSF codes of all UCIs are available on the CSSF website under the link: Identifiers of UCI/SIF/SICAR – CSSF Examples: 1) In the case of transmission of the U1.1 reporting for the UCI "ABC", which is an umbrella UCI (e.g. CSSF code "1" which must be filled in with 7 digits of "0" before the number "1"), sub-fund "A" (e.g. CSSF code "1" which must be filled in with 7 digits of "0" before the number "1"), the field "CSSF code of the UCI" must be filled in with the following unique identifier code: "O00000001_00000001". 2) In the case of transmission of the U1.1 reporting for the UCI "DEF", which is not an umbrella UCI (e.g. CSSF code "2" which must be filled in with 7 digits of "0" before the number "2"), the field "CSSF code of the UCI" must be filled in with the following unique identifier code: "O00000002_00000000". 1.2.4.2. 2011 – Intentionally left blank This item is not used for the U1.1 report but is displayed to mirror the BCL report S 2.20 schema. 1.2.4.3. 2012 – Intentionally left blank This item is not used for the U1.1 report but is displayed to mirror the BCL report S 2.20 schema. 1.2.4.4. 2020 - Name of the UCI (name of the entity and name of the sub-fund) [mandatory] This item refers to the name of the UCI as mentioned in the offering document and any subsequent changes authorised by the CSSF, which is composed of the name of the entity and the sub-fund in the case of an umbrella UCI and only of the name of the entity in the case of a non-umbrella UCI. The names of the UCIs are available on the CSSF website under the link: Identifiers of UCI/SIF/SICAR – CSSF Examples: 1) In the case of transmission of the U1.1 reporting for the UCI "ABC" (which is an umbrella UCI), sub-fund "A" the "Name of the UCI"-field must be filled in with the following content: "ABC – A". 2) In the case of transmission of the U1.1 reporting for the UCI "DEF", (which is not an umbrella UCI), the field "Name of the UCI" must be filled in with the following content: "DEF". GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 9/51 1.2.4.5. 2030 - Base currency of the UCI [mandatory] This item refers to the base currency of the UCI in which the total net asset value is expressed as at the valuation date of the reference month as laid down in the articles of incorporation/management regulations/offering document and any subsequent changes of the UCI. The base currency of the UCI must be reported by using the ISO 4217 codes. 1.2.4.6. 2040 - Legal Entity Identifier (LEI) [mandatory if the UCI has been allocated a LEI] This item refers to the Legal Entity Identifier of the UCI. For umbrella funds, the LEI must be filled in for each specific sub-fund. 1.2.4.7. 2050 - Valuation date [mandatory] Since UCIs must transmit each month the most accurate and up-to-date financial information, the information underlying the U1.1 reporting must be based on the valuation date that is the closest to the end of the reference month. Consequently, the valuation date is, in principle, the last business day of the reference month. For UCIs which calculate their net asset value at least on a weekly basis, the valuation date, is in principle, the last day of the reference month for which the net asset value is calculated. For UCIs which calculate their net asset value at least on a monthly basis, the valuation date should refer to the date which is the closest to the last day of a reference month for which the net asset value is calculated. In this case, the valuation date can also refer to a day within the following month if the UCI calculates its net asset value after the month’s end, but before the 10th calendar day of the following month. For UCIs which calculate their net asset value less than monthly, the valuation date should refer to the day for which the estimated data based on the accounting records has been calculated (i.e. unofficial net asset value based on last available information/valuation prices) or to the day for which the net asset value has been calculated (for the official net asset values). In the case of estimated data, at least the last (official) net asset value determined in accordance with the net asset value calculation frequency as laid down in the offering document and any subsequent changes must be used. Examples: 1) A UCI calculates its NAV on a weekly basis every Friday. Therefore, the UCI calculates its NAV dated 8 May 2026, 15 May 2026, 22 May 2026, 29 May 2026 and 5 June 2026. The valuation date for the reference month of May 2026 is 29 May 2026. 2) A UCI calculates its NAV on a monthly basis, namely on the third business day of each month. Therefore, the UCI calculates its NAV dated 6 May 2026 and 3 June 2026. For submitting the monthly report for May 2026, the UCI could use the financial data for this reference month calculated on 3 June 2026. The valuation date in this case is 3 June 2026 for the reference month May 2026. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 10/51 3) A UCI calculates its NAV on a quarterly basis (March, June…) as well as for each subscription or redemption. During the second quarter, the UCI receives new subscriptions on 12 May 2026. As a result, the UCI must calculate its NAV dated 31 March 2026, 12 May 2026 and 30 June 2026. The valuation date for the reference month of March 2026 is the 31 March 2026. The valuation date for the reference month of April 2026 is the date of the estimated data as based on the accounting records (i.e. unofficial net asset value based on last available information/valuation prices) as at 30 April 2026, thereby using at least the official net asset value as at 31 March 2026. The valuation date for the reference month of May 2026 is the date of the estimated data as based on the accounting records (i.e. unofficial net asset value based on last available information/valuation prices) as at 31 May 2026, thereby using at least the official net asset value as at 12 May 2026. The valuation date for the reference month of June 2026 is 30 June 2026. 1.2.4.8. 2060 – Net asset value calculation frequency [mandatory] This item refers to the net asset value calculation frequency, the following frequencies being available: Option NAV calculation frequency number 1 Daily 2 Daily and month-end 3 Semi-weekly 4 Semi-weekly and month-end 5 Weekly 6 Weekly and month-end 7 Weekly and first day of the month 8 Weekly and for each subscription or redemption 9 Semi-monthly 10 Semi-monthly and month-end 11 Semi-monthly and quarter-end 12 Semi-monthly and for each subscription or redemption 13 Monthly 14 Monthly and for each subscription or redemption 15 Quarterly 16 Quarterly and for each subscription or redemption 17 Semi-annually 18 Semi-annually and for each subscription or redemption 19 Annually 20 Annually and for each subscription or redemption Examples: 1) A UCI that calculates its net asset value on the third Friday of each month is considered as having a "monthly" net asset value calculation frequency (option 13). GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 11/51 2) A UCI that calculates its net asset value on a weekly and end-of- month basis is considered as having a "weekly and end-of-the-month" net asset value calculation frequency (option 6). The UCI can add a comment in the free text box providing further details on its frequency. 1.2.4.9. 2070 - Launch date [mandatory] The launch date is the date on which the UCI receives its first subscription(s). The UCI can only submit, in terms of reporting status, a "final report" or a "provisional report" for the reference month in which the first subscription was received. If the UCI is temporarily closed (see option 4 of item number 2090), the subsequent launch date is the date on which the UCI receives its new subscription(s). 1.2.4.10. 2080 - Closing date [optional] The closing date is the date in the reference month for which the UCI transmits its last final U1.1 reporting. If the UCI is temporarily closed, it will submit a "null report" for each subsequent reference month (see option 4 of item number 2090). 1.2.4.11. 2090 - Reason for closing [optional] Option Reason for closing number 1 Put into liquidation Consequences/comments No further U1.1 reporting files are requested after the reference month that relates to the closing date. 2 Merger into another No further U1.1 reporting files are requested after the reference UCI (wherever it is month that relates to the closing date. domiciled) For reporting purposes, it should be noted that, in the case of a merger, the absorbing (sub-)fund, if domiciled in Luxembourg, should treat the shares issued to the unitholders of the absorbed (sub-)fund (in exchange for the transfer of all the assets/liabilities by the absorbed (sub-)fund), as new subscriptions and should include this amount in its subscriptions for the reference month (see item number 3030 below). 3 The UCI status has No further U1.1 reporting files are requested after the reference been abandoned and month that relates to the closing date. the UCI has adopted a different legal status from the UCI 4 The UCI is As long as there are no new proceeds from subscriptions for a temporarily closed reference month, the UCI must submit U1.1 reporting files with (see Circular CSSF the "reporting status" of "null report". Based on Circular CSSF 12/540) 12/540 the UCI can be reactivated within 18 months. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 12/51 5 The UCI is The sub-fund of the UCI has not received any new proceeds for definitively closed 18 months and has been consequently closed. No further U1.1 (see Circular CSSF reporting files are requested after the reference month that 12/540) relates to the closing date. 1.2.4.12. 2100 – Redemption frequency [mandatory] This item refers to the redemption frequency. The following frequencies are available: Option number Redemption frequency 1 Daily 2 Weekly 3 Semi-monthly 4 Monthly 5 Quarterly 6 Biannual 7 Annual 8 Only at the end of maturity 9 Other/Irregular 1.2.4.13. 2110 – Open- / Closed-end [mandatory] This item refers to the type of investment funds in relation to the issuance and redemption of shares or units. The distinguishing factor in determining whether an investment fund is of the open-ended or closedended type is whether the fund repurchases or redeems its shares or units with its investors, at the request of any of its shareholders or unitholders, prior to the commencement of its liquidation phase or wind-down and does so according to the procedures and frequency set out in its rules or instruments of incorporation, prospectus or offering documents. A decrease in the capital of an investment fund resulting from distributions made in accordance with its rules or instruments of incorporation, prospectus, or offering documents - including distributions authorised by a resolution of the shareholders or unitholders adopted in accordance with those documents - shall not be taken into account for the purpose of determining whether the fund is of the open-ended type. Investment funds that do not meet the above criteria shall be considered closed-ended. Option number Open- / Closed-end 1 Open-end investment funds 2 Closed-end investment funds GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 13/51 1.2.5. Section 3: Financial information of the UCI in the base currency of the UCI 1.2.5.1. 3010 - Total net asset value of the preceding reference month [mandatory] This item refers to the total net asset value of the preceding reference month of the UCI. The amount shown must be identical to the one stated in the last submitted version of the "final report" or "provisional report" of the preceding month under "Total net asset value of the reference month" (cf. item 3020). If the UCI submits a "final report" or "provisional report" for the very first time, i.e. it has received its first subscription(
  2. s)during the reference month, field 3010 must state "0". If the UCI submits a revised version of a U1.1 reporting in which the field "Total net asset value of the reference month" changes, the field "Total net asset value of the preceding reference month" in the U1.1 reporting file for the subsequent reference month must be revised as well and the amended U1.1 reporting file must be submitted to the CSSF. 1.2.5.2. 3020 - Total net asset value of the reference month [mandatory] This item refers to the total net asset value of the reference month calculated on the valuation date. 1.2.5.3. 3030 - Proceeds from all units/shares issued during the reference month [mandatory] This item refers to the net proceeds (after deduction of all fees/costs) received by the UCI from all units/shares issued for the different units/share classes during the reference month. In case of subscriptions in kind, the corresponding net proceeds are to be reported under this item. 1.2.5.4. 3040 - Payments made for all units/shares redeemed during the reference month [mandatory] This item refers to the payments made by the UCI in settlement of redemptions of all units or shares redeemed for the different units/share classes during the reference month. In case of redemptions in kind, the corresponding payments are to be reported under this item. 1.2.5.5. 3050 - Total distributions made during the reference month [mandatory] This item refers to the total distributions (including interim dividends) made by the UCI for all units/share classes with distribution rights, whose ex-dividend date falls within the reference month, GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 14/51 regardless of whether the distributions are cash dividends or dividends in the form of bonus units/shares. It should be noted that distributions made in the form of bonus units/shares must be reflected in the field "Proceeds from all units/shares issued during the reference month" (see item 3030) and in the field "Proceeds from units/shares issued in the base currency of the UCI" (see item 5050). 1.2.6. Section 4: General information on the unit/share class (to be filled in separately for each unit/share class) Each unit/share class of the UCI to be issued must be authorised by the CSSF. For each unit/share class launched, the submission of the information, as requested in Section 4, is mandatory until the unit/share class is closed. 1.2.6.1. 4010 - CSSF code of the unit/share class [mandatory] This item refers to the sequential number, composed of four digits, given by the CSSF to the unit/share class. Example: In the case of the transmission of the U1.1 reporting for the UCI "ABC", sub-fund "A", share class "CAP" (e.g. CSSF code "1"), the field "CSSF code of the unit/share class" must be filled in with the following unique identifier code: "0001". The CSSF code of the units/share classes are available on the CSSF website under the link: Identifiers of UCI/SIF/SICAR – CSSF 1.2.6.2. 4020 - Name of the unit/share class [mandatory] This item refers to the name of the unit/share class as laid down in the latest offering document and any subsequent changes authorised by the CSSF. Example: In the case of the transmission of the U1.1 reporting for the UCI "ABC", sub-fund "A", share class "CAP", the field "CSSF Name of the unit/share class" must be filled in with the share class name: "CAP". The names of the units/share classes are available on the CSSF website under the link: Identifiers of UCI/SIF/SICAR – CSSF 1.2.6.3. 4030 - Base currency of the unit/share class [mandatory] This item refers to the base currency of the unit/share class. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 15/51 1.2.6.4. 4040 - ISIN code of the unit/share class [mandatory if the unit/share class has been assigned an ISIN code] This item refers to the International Securities Identification Number ("ISIN") of the unit/share class. Although this field is optional, if the unit/share class has an ISIN code, it must be indicated in the U1.1 reporting. 1.2.6.5. 4050 - Launch date of the unit/share class [mandatory] This item refers to the date on which the UCI receives its first subscription(
  3. s)for the specific unit/share class. If the unit/share class is temporarily closed, (see option 4 of item number 4070), the subsequent launch date is the date on which the UCI receives its new subscription(s). 1.2.6.6. 4060 - Closing date of the unit/share class [optional] This item refers to the date on which the last investor(
  4. s)exit(
  5. s)from the specific unit/share class by redeeming all the units/shares issued/in circulation. The UCI transmits the information requested under sections 4 and 5 for the specific unit/share class for the last time for this reference month. 1.2.6.7. 4070 - Reason for closing of the unit/share class [optional] There are only four reasons for closing a unit/share class: Option number 1 Reason for closing Consequences/comments Put into liquidation The whole UCI or a unit/share class is liquidated. No further U1.1 reporting files are requested for this specific unit/share class after the reference month that relates to the closing date. 2 Merger into another unit/share The unit/share class is merged into another UCI or class (wherever it is domiciled) another unit/share class of the UCI. No further U1.1 reporting files are requested for this specific unit/share class after the reference month that relates to the closing date. 3 4 The UCI status is relinquished The whole UCI ceases to be a UCI. No further U1.1 and the UCI has adopted a reporting legal status other than that of unit/share class after the reference month that a UCI relates to the closing date. The unit/share class temporarily closed is files are requested for this specific As long as there are no new proceeds from subscriptions for a reference month, the UCI does not have to submit information for this specific unit/share class after the reference month in which the last investor(
  6. s)was/were redeemed. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 16/51 1.2.6.8. 4080 - Unit/share class with specific instruments – FX [mandatory] This item refers to the existence ("true/false") of specific financial instruments related to foreign exchange "FX" (e.g. currency forward transactions) at the level of the unit/share class. No distinction should be made between FX transactions for hedging purposes and FX transactions for investment purposes. Example: A UCI A may create a unit/share class (with base currency US dollar (USD)) whose intention is to hedge the value of the net assets of that unit/share class (expressed in USD) in the base currency of the UCI (for example, Euro (EUR)) by using USD/EUR currency forward contracts, whereby the costs and expenses arising from the currency forward transactions will only be borne by that unit/share class. For that specific unit/share class the field "Unit/share class with specific assets – FX" must be flagged as "true". 1.2.6.9. 4090 - Unit/share class with specific instruments – Interest Rate [mandatory] This item refers to the existence ("true/false") of specific financial instruments related to interest rates (e.g. bond future transactions) at the level of the unit/share class. No distinction should be made between interest rate transactions for hedging purposes and interest rate transactions for investment purposes. Example: A UCI A may create a unit/share class whose intention is to reduce/limit the impact of interest rate movements (e.g. target duration of 6 months) on its net asset value by using bond future contracts, whereby the costs and expenses arising from the bond future transactions will only be borne by that unit/share class. For that specific unit/share class the field "Unit/share class with specific assets – Interest Rate" must be flagged as "true". 1.2.6.10. 4100 - Unit/share class with specific instruments – Other [mandatory] This item refers to the existence ("true/false") of specific financial instruments related to other factors other than FX or interest rates (e.g. equity index future for hedging the equity risk) at the level of the unit/share class. No distinction should be made between transactions for hedging purposes and transactions for investment purposes. 1.2.6.11. 4110 - Investor base [mandatory] This item refers to the type of shareholders. The investor base is determined on the basis of the predominant (more than 50 %) type of investors, in terms of their value (number of units/shares outstanding * net asset value per unit/share in the base currency of the fund). GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 17/51 Please refer to Annex II of Directive 2014/65/EU for detailed definitions of the different categories. • "Professional investor" means a client meeting the criteria laid down in Annex II, point I • "Well-informed investor" means a client meeting the criteria laid down in Annex II point II ("Categories of client who are considered to be professionals"); ("Clients who may be treated as professionals on request"); • "Retail investor" means a client who is neither a professional client nor a well-informed investor; • "Mixed" should be used if no predominant type can be determined on a best-effort basis. Option number 1.2.7. Investor base 1 Professional investor 2 Well-informed investor 3 Retail investor 4 Mixed Section 5: Financial information on the unit/share class for the reference month (to be filled in separately for each unit/share class) For each unit/share class launched, the submission of the information as requested in Section 5 is mandatory until the unit/share class is closed. 1.2.7.1. 5010 - Number of units/shares outstanding [mandatory] This item refers to the number of units/shares in circulation at the end of the reference month (or at the valuation date if it does not match with the last day of the reference month) for a given unit/share class. 1.2.7.2. 5020 - Net asset value per unit/share in the base currency of the UCI [mandatory] This item refers to the net asset value per unit/share in the base currency of the UCI at the valuation date of the reference month. Example: A UCI, with EUR as base currency, has issued two share classes: type A expressed in EUR and type B expressed in USD. The net asset value of the UCI (see item 3020) is the sum of the product [number of units/shares * net asset value per unit/share in the base currency of the UCI] of each unit/share class. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 18/51 Number of NAV per unit/share in Exchange rate NAV per unit/share in units/shares the base currency of the (e.g., USD/EUR= the base currency of outstanding unit/share class 0.8695) the UCI Class A 1,000 100 (EUR) 1 100 (EUR) Class B 500 115 (USD) 0.8695 100 (EUR) The net asset value of the UCI (see item 3020) is [1,000 * 100] + [500 * 100] = EUR 150,000. The net asset value per unit/share in the base currency of the UCI for Class A is 100 (EUR). The net asset value per unit/share in the base currency of the UCI for Class B is 100 (EUR). 1.2.7.3. 5030 - Net asset value per unit/share in the base currency of the unit/share class [mandatory] This item refers to the net asset value per unit/share in the base currency of the unit/share class (see item 4030) at the valuation date of the reference month. Example: A UCI, with EUR as its base currency, has issued two share classes: type A denominated in EUR and type B denominated in USD. The net asset value of the UCI (see item 3020) is the sum of the product [number of units/shares * net asset value per unit/share in the base currency of the unit/share class * exchange rate] of each unit/share class. Exchange rate NAV per unit/share in units/shares the base currency of the (e.g. USD/EUR= outstanding unit/share class 0.8695) Number of NAV per unit/share in the base currency of the UCI Class A 1,000 100 (EUR) 1 100 (EUR) Class B 500 115 (USD) 0.8695 100 (EUR) The net asset value of the UCI (see item 3020) is [1,000 * 100 * 1] + [500 * 115 * 0.8695] = EUR 150,000. The net asset value per unit/share in the base currency of the unit/share class for Class A is 100 (EUR) [see item 5020]. The net asset value per unit/share in the base currency of the unit/share class for Class B is 115 (USD). 1.2.7.4. 5040 - Net return per unit/share in the base currency of the unit/share class [mandatory] This item refers to the monthly performance (in percentage, positive or negative) of the unit/share class as derived from the net asset value per unit/share (in the base currency of the unit/share class) of the unit/share class of the reference month and the preceding reference month. The GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 19/51 calculation should be made on the basis that any distributable income at the level of the unit/share class has been reinvested. The monthly investment return should not be rescaled to an annual basis. Examples: 1) A UCI has issued three share classes: A is a non-distributing share class, B is a monthly distributing share class (end of the month) and C is a monthly distributing share class (beginning of the month). The net return on investments for the month is 1.5%. Net asset value per Share unit/share in the base Distri- class currency of the unit/share butions Net returns (in percent) class Preceding Reference month month A 100.00 101.50 None (101.50 - 100.00)/100.00 = 1.5% B 100.00 99.50 2 ((99.50+2) – 100.00)/100.00 = 1.5% C 100.00 99.47 2 ((99.47+2.03) - 100.00)/100.00 = 1.5% 2 The net return per unit/share in the base currency of the unit/share class for classes A, B and C is 1.5 %. 2) A UCI calculates its net asset value on a weekly basis and has issued two share classes: A is a non-distributing share class and B is weekly distributing share class. The net returns on investments during the month are 0.50% for week 1, -1.00% for week 2, 0.75% for week 3 and 1.25% for week 4. Share class A Net asset value per unit/share in the base currency of the Distributions unit/share class Preceding Reference month month Weekly returns (in percent) 100.00 week 1 100.50 None week 2 99.495 None week 3 100.241 None (100.241-99.495) None (101.494-100.241) /100.241 = 1.25% (100.50-100.00) /100.00 = 0.50% (99.495-100.50) /100.50 = -1.00% /99.495 = 0.75% week 4 101.494 (1.005 *0.990 *1.0075*1.0125) = 1.494% (101.494 - 100.00)/100.00 = 1.494% 2 The dividend is considered as being reinvested at the same rate as the investments (2*1.015=2.03) GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 20/51 B 100.00 week 1 100.00 0.5 ((100.00+0.5)-100.00) week 2 99.00 0 ((99.00+0)-100.00) week 3 99.243 0.5 ((99.243+0.5)-99.00) /100.00 = 0.50% /100.00 = -1.00% /99.00 = 0.75% week 4 99.483 1 ((99.483+1)-99.243) /99.243 = 1.25% (1.005 *0.990 *1.0075*1.0125) = 1.494% The net return per unit/share in the base currency of the unit/share class for classes A and B is 1.494 %. 1.2.7.5. 5050 - Proceeds from units/shares issued in the base currency of the UCI [mandatory] This item refers to the net proceeds (after deduction of all fees/costs) received by the UCI from units/shares issued during the reference month for the unit/share class. In the case of subscriptions in kind the corresponding net proceeds are to be reported under this item. This also includes the proceeds of units/shares issued (in exchange for the transfer of assets/liabilities by the absorbed UCI) in the context of the merger of another UCI (domestic or foreign) into the relevant UCI. 1.2.7.6. 5060 - Payments made for units/shares redeemed in the base currency of the UCI [mandatory] This item refers to the payments made by the UCI in settlement of redemptions of units/shares redeemed during the reference month for the unit/share class. In the case of redemptions in kind the corresponding payments should be reported under this item. 1.2.7.7. 5070 - Total distributions made in the base currency of the UCI [mandatory] This item refers to the total distributions (including interim dividends) in the base currency of the UCI made by the UCI for the unit/share class with distribution rights, whose ex-dividend date falls within the reference month, whether in the form of cash dividends or dividends in the form of bonus units/shares. It should be noted that distributions made in the form of bonus units/shares must be reflected in the "Proceeds from units/shares issued in the base currency of the UCI" (see item 5050) and in the "Proceeds from all units/shares issued during the reference month" (see item 3030). Example: A UCI, with EUR as its base currency, has issued two distribution share classes: type A denominated in EUR and type B denominated in USD. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 21/51 The total distributions (including interim dividends) made by each unit/share class in the base currency of the UCI is equal to the product [number of units/shares for the unit/share class with distribution rights * dividend per unit/share in the base currency of the unit/share class * exchange rate] of each unit/share class. Number of Dividend per units/shares for unit/share class with The total unit/share distributions (e.g. in the base made in the base USD/EUR= currency of currency of the class 0.8695) the UCI UCI the base currency of the distribution unit/share rights Exchange Dividend per unit/share in rate Class A (EUR) 1,000 0.5 (EUR) 1 0.5 (EUR) 500 (EUR) Class B (USD) 500 0.575 (USD) 0.8695 0.5 (EUR) 250 (EUR) The total distributions in the base currency of the UCI made by Class A are [1,000 * 0.5 * 1] = EUR 500 The total distributions in the base currency of the UCI made by Class B are [500 * 0.575 * 0.8695] = EUR 250 1.2.7.8. 5080 - Amount of distributions made per unit/share in the base currency of the UCI [mandatory] This item refers to the distributions (including interim dividends) in the base currency of the UCI made by the UCI per unit/share for the unit/share class with distribution rights, whose ex-dividend date falls within the reference month, whether in the form of cash dividends or dividends in the form of bonus units/shares. Example: A UCI, with EUR as its base currency, has issued two distribution share classes: type A denominated in EUR and type B denominated in USD. The dividend per unit/share in the base currency of the UCI is the product of [dividend per unit/share in the base currency of the unit/share class * exchange rate]. Number of units/shares for unit/share class with distribution rights Dividend per Exchange rate unit/share in the base (e.g. currency of the USD/EUR= unit/share class 0.8695) Dividend per unit/share in the base currency of the UCI Class A (EUR) 1,000 0.5 (EUR) 1 0.5 (EUR) Class B (USD) 500 0.575 (USD) 0.8695 0.5 (EUR) The dividend per unit/share in the base currency of the UCI (EUR) is 0.5 for Class A. The dividend per unit/share in the base currency of the UCI (EUR) is 0.5 for Class B. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 22/51 1.2.7.9. 5090 - Amount of distributions made per unit/share in the base currency of the unit/share class [mandatory] This item refers to the distributions (including interim dividends) in the base currency of the unit/share class made by the UCI per unit/share for the unit/share class with distribution rights, whose ex-dividend date falls during the reference month, whether in the form of cash dividends or dividends in the form of bonus units/shares. Example: A UCI, with EUR as its base currency, has issued two distribution share classes: type A denominated in EUR and type B denominated in USD. Dividend per Number of Dividend per Exchange rate units/shares unit/share in the base (e.g. with distribution currency of the USD/EUR= rights unit/share class 0.8695) Class A (EUR) 1,000 0.5 (EUR) 1 0.5 (EUR) Class B (USD) 500 0.575 (USD) 0.8695 0.5 (EUR) unit/share in the base currency of the UCI The dividend per unit/share in the base currency of the unit/share class is 0.5 for Class A (EUR). The dividend per unit/share in the base currency of the unit/share class is 0.575 for Class B (USD). 1.2.7.10. 5100 – Income in the base currency of the UCI [mandatory] This item refers to the part of the income of the UCI allocated to the unit/share class. This amount consists of income due in respect of the month and income accrued during the reference month. Items: Dividends on units/shares

(6010), Dividends on UCI units/shares
(6020), Interest on bonds and other debt securities
(6030), Interest on loans, bank and other interest-bearing accounts
(6040), Other income
(6050), and Realised and Unrealised profit or loss on investments and foreign exchange positions (6090 and 6100) should be reported under this item. 1.2.7.11. 5110 – Expenses in the base currency of the UCI [mandatory] This item refers to the part of expenses incurred by the UCI that are allocated to the unit/share class. This amount consists of expenses due in respect of the month and expenses accrued during the reference month. Items: Charges
(6060), Performance fees
(6070), and Other expenses
(6080)should be reported under this item. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 23/51 1.2.
  1. Section 6: Information on the investment income and expenses for the reference month in the base currency of the UCI Items 6010 to 6100 all refer to information relating to the reference month. No cumulative amounts, i.e. including income/expenses in respect of preceding months of the financial year, are to be reported under the below items. Moreover, amounts should be shown net of taxes. 1.2.8.
  2. 6010 - Dividends on shares [mandatory] This item refers to the total amount of dividends received by the UCI in respect of shares and other participating securities, other than UCIs, at their ex-dividend date. 1.2.8.1.
  3. 6011 - Dividends on shares - of which from Luxembourg [mandatory] This item refers to the amount of dividends received by the UCI in respect of shares and other participating securities, except UCIs, at their ex-dividend date from Luxembourg domiciled companies. 1.2.8.
  4. 6020 - Dividends on UCI units/shares [mandatory] This item refers to the total amount of dividends received by the UCI in respect of UCIs at their exdividend date. 1.2.8.2.
  5. 6021 - Dividends on UCI units/shares - of which from Luxembourg [mandatory] This item refers to the amount of dividends received by the UCI in respect of UCIs at their exdividend date from Luxembourg domiciled UCIs. 1.2.8.
  6. 6030 - Interest on bonds and other debt securities [mandatory] This item refers to the total amount of interest income received by the UCI in respect of bonds and other debt securities, such as money market instruments, whatever their maturity may be. This amount consists of interest due in respect of the month and interest accrued during the reference month. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 24/51 1.2.8.3.
  7. 6031 - Interest on bonds and other debt securities - of which from Luxembourg [mandatory] This item refers to the amount of interest income received by the UCI in respect of bonds and other debt securities, such as money market instruments, whatever their maturity may be, from Luxembourg domiciled issuers. This amount consists of interest due in respect of the month and interest accrued during the reference month. 1.2.8.
  8. 6040 - Interest on loans, bank and other interest-bearing accounts [mandatory] This item refers to the amount of interest income received by the UCI in respect of loans, term deposits and other interest-bearing accounts. This amount consists of interest due in respect of the reference month and interest accrued during the reference month. This item corresponds to the sum of items 6041 and
  9. 1.2.8.4.
  10. 6041 – Bank interest [mandatory] This item refers to the amount of interest income received by the UCI in respect of term deposits and other interest-bearing accounts from banks and other deposit-taking institutions. 1.2.8.4.
  11. 6042 – Bank interest - of which from Luxembourg [mandatory] This item refers to the amount of interest income received by the UCI in respect of term deposits and other interest-bearing accounts from banks and other deposit-taking institutions domiciled in Luxembourg. 1.2.8.4.
  12. 6043 – Other interest [mandatory] This item refers to the amount of interest income received by the UCI in respect of loans, term deposits and other interest-bearing accounts from counterparties other than banks and other deposit-taking institutions. 1.2.8.4.
  13. 6044 – Other interest - of which from Luxembourg [mandatory] This item refers to the amount of interest income received by the UCI in respect of loans, term deposits and other interest-bearing accounts from counterparties other than banks and other deposit-taking institutions domiciled in Luxembourg. 1.2.8.
  14. 6050 - Other income [mandatory] This item refers to all income other than that shown under items 6010, 6020, 6030 and 6040, such as rental income, commission income and other income. This amount consists of income earned in GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 25/51 respect of the month and income accrued during the reference month. This item corresponds to the sum of items 6051 to
  15. 1.2.8.5.
  16. 6051 – Rental income [mandatory] This item refers to the amount of rental income received by the UCI from leased properties and plants. 1.2.8.5.
  17. 6052 – Commission income [mandatory] This item refers to the amount of commission income received by the UCI (e.g. retrocession fees, swing pricing fees, redemption and/or conversion fees). 1.2.8.5.
  18. 6053 – Other [mandatory] This item refers to all income other than that shown under items 6010 to 6052 (e.g. reversal of expenses). 1.2.8.
  19. 6060 – Charges [mandatory] This item refers to the charges deducted from the UCI (i.e. deducted from the assets of the UCI) during the reference month and represents all costs - borne by the UCI whether they represent expenses necessarily incurred in its operation, or the remuneration of any party connected with it or providing services to it - for running the UCI. Examples of costs to be included are the management fee, the advisory fee, the custodian fee, the UCI administration fee, the distribution fee, audit fees, other administrative expenses and taxes. This item corresponds to the sum of items 6061 to
  20. Performance fees and portfolio transaction costs should not be included under this item. 1.2.8.6.
  21. 6061 – Advisory and/or management commissions and/or fees [mandatory] This item refers to commissions and/or fees paid and accrued in respect of advisory and/or management services deducted from the UCI. 1.2.8.6.
  22. 6062 – Depositary commissions and/or fees [mandatory] This item refers to commissions and/or fees paid and accrued in respect of depositary services (from custodian or sub-custodian banks or safekeeping companies) deducted from the UCI. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 26/51 1.2.8.6.
  23. 6063 –UCI administration fees [mandatory] This item refers to expenses paid and accrued in respect of UCI administration services deducted from the UCI. 1.2.8.6.
  24. 6064 – Audit and inspection fees [mandatory] This item refers to expenses paid and accrued in respect of audit and inspection fees deducted from the UCI. 1.2.8.6.
  25. 6065 – Distribution fees [mandatory] This item refers to distribution fees paid and accrued in respect of the marketing and sale of UCI units/shares deducted from the UCI. These fees may cover advertising costs, compensating brokers and others selling fund units/shares, payments for printing and mailing of prospectuses to new investors, and provision of sales literature to prospective investors (e.g. distribution fees related to a master-feeder structure). 1.2.8.6.
  26. 6066 – Other administrative expenses [mandatory] This item refers to all administrative expenses paid and accrued other than that shown under items 6061 to 6065 deducted from the UCI. 1.2.8.6.
  27. 6067 – Subscription tax [mandatory] This item refers to the subscription tax ("taxe d’abonnement") paid and accrued and deducted from the UCI. 1.2.8.6.
  28. 6068 – Other tax [mandatory] This item refers to the tax other than the subscription tax ("taxe d’abonnement") paid and accrued and deducted from the UCI. 1.2.8.
  29. 6070 - Performance fees [mandatory] This item refers to the performance-related fees (positive or negative) deducted from the UCI. 1.2.8.
  30. 6080 - Other expenses [mandatory] This item refers to all expenses deducted other than those shown under items 6060 and 6070, such as interest paid, bank charges, personnel expenses, rents, amortisation deducted from the UCI. This item corresponds to the sum of items 6081 to
  31. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 27/51 Portfolio transaction costs that are directly attributable to the acquisition, issue or disposal of securities are not be included under this item but are added to or deducted from the portfolio positions at the settlement date. 1.2.8.8.
  32. 6081 – Interest paid [mandatory] This item refers to the total amount of interest paid and accrued on bank overdrafts, loans and debt securities issued. 1.2.8.8.
  33. 6082 – Personnel expenses [mandatory] This item refers to the total amount of personnel expenses paid and accrued by the UCI for its salaried employees. Personnel expenses include wages and rewards, pension expenses and other employer contributions. 1.2.8.8.
  34. 6083 – Rental expenses [mandatory] This item refers to the total amount of rental expenses paid and accrued by the UCI for its own use of the building. Rental expenses include charges for ancillary services (water, electricity, heating, etc.). 1.2.8.8.
  35. 6084 – Amortisation [mandatory] This item refers to the total amount of amortisation of establishment costs, intangible and tangible assets. Establishment costs include the charges that incurred at the launch of the investment funds (typically legal and notary services), and do not relate to the portfolio acquisition and the financing structure. Intangible assets include the goodwill. Tangible assets include the building owned by the UCI for its own use. 1.2.8.8.
  36. 6085 – Other [mandatory] This item refers to all expenses deducted other than those shown under items 6081 to
  37. 1.2.8.
  38. 6090 - Net realised profit or loss on investments and foreign exchange positions [mandatory] This item refers to the amount of net gains/losses (positive or negative) realised during the reference month. This amount must be calculated by offsetting the realised gains and losses on the disposal of investments (securities, derivatives, etc.), including realised foreign exchange related gains/losses. For reporting purposes, portfolio transaction costs on sale of securities are to be included in the net realised profit or loss on investments and foreign exchange positions. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 28/51 1.2.8.
  39. 6100 - Net unrealised profit or loss on investments and foreign exchange positions [mandatory] This item refers to the increase or decrease over the reference month of net unrealised gains or losses originating from the valuation of investments (securities, derivatives, etc.), including foreign exchange related to unrealised gains/losses. For reporting purposes, portfolio transaction costs on the purchase of securities are to be included in the acquisition or issue of the securities and are therefore recognised within net unrealised profit or loss on investments and foreign exchange positions. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 29/51
  40. Definition of the Reporting Declarant The Reporting Declarant is defined as the entity identified as UCI administrator with the function "NAV calculation and accounting function" ("ADM-NAV"). This entity is deemed the legally and operationally responsible party for the submission of all reporting files and is automatically allowed to transmit the Reporting. The ADM-NAV may, where applicable, delegate the technical transmission of the reporting to another entity – the Sender. In such cases, the delegated entity is authorised to submit the reporting on behalf of the ADM-NAV. Notwithstanding such delegation, the ADM-NAV remains fully responsible for the accuracy, completeness, and timely submission of all reported data. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 30/51
  41. Delegation management Any delegation arrangement must be clearly established and, where required, formally documented to ensure the correct identification of both the responsible entity and the transmitting entity within the reporting process. The "Management of delegations" menu allows a declarant or a sender to consult their entity’s delegations by clicking on the "Management of delegations" button. Declarant: Entity responsible for transmitting the U1.1 reporting, which can designate one or more senders to transmit U1.1 reportings for the funds under its responsibility. Sender: Entity designated by the declarant to transmit U1.1 reportings via S3 and eDesk for a scope of funds defined by the declarant. The following screen appears: This section allows the declarant and/or the sender to manage their delegation. The declarant can delegate the submission of the U1.1 reporting for a scope of funds to an entity, for the months for which they are declarant for that scope of funds. The sender can thus transmit the U1.1 reporting S3 or eDesk at their discretion. The sender can accept/refuse a delegation received by a declarant. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 31/51 Only advanced users are authorised to manage delegations as a declarant or sender. Other users are allowed to consult delegations. The As a declarant, can click on the "Create a new delegation" button. A pop-up window will then appear, and they can: • Enter the sender (name or the reference of the entity) who will be responsible for filing the U1.1 reporting on behalf of the declarant. • Add a communication (optional). • Select the funds under responsibility for which they wish to grant a delegation. There are two options: o "Select all funds permanently": this option allows the declarant to permanently authorise all funds of their entity. When a new fund is linked to their entity, they do not have to add it to the delegation; • o "Select fund by fund": this option allows the declarant to authorise a scope of funds. At the end, the declarant can click on the "Confirm" button. All advanced users of the sender receive an email with the subject: "[eDesk][U11 – transmission of U1.1 reports] Invitation to contribute by YXXX" (where YXXX is the CSSF code of the declarant entity). An eDesk link is available in the email to consult the delegation and thus accept or refuse the declarant’s delegation (only an advanced user of the sender can accept or refuse). GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 32/51 When the advanced user of the sender accepts the declarant’s delegation, a pop-up window appears: The sender acknowledges the funds delegated by the declarant. The sender also acknowledges that they are automatically authorised to transmit the U1.1 reporting on behalf of the declarant (for delegated funds only, concerning the months under the responsibility of the declarant) via S
  42. The sender can therefore transmit a report concerning a fund delegated by their declarant and for a month under the responsibility of the declarant for this fund via their own bucket. Finally, the sender must select the eDesk users linked to their entity who will be authorised to submit the transmitted U1.1 reporting/consult the U1.1 reporting. There are two options: • "Select all users permanently": this option allows the sender to permanently authorise all eDesk users of their entity. When a new eDesk user is linked to the entity, they do not have to be added to the delegation. • "Select user by user": this option allows the sender to authorise a scope of eDesk users. At the end, click on the "Confirm" button. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 33/51 The sender is therefore authorised to consult all U1.1 reportings transmitted for the delegated funds and period, regardless of the submitting entity. At any time, the sender can (as seen below): • consult the details of a delegation by clicking the "Consult this delegation" button; • modify the eDesk users authorised for a delegation by clicking the "Modify authorised users" button; • cancel a delegation by clicking the "Cancel this delegation" button At any time, the declarant can (as seen below): • consult the details of a delegation by clicking the "View this delegation" button; • modify the delegated funds by clicking the "Modify delegated funds" button; • cancel a delegation by clicking the "Cancel this delegation" button. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 34/51
  43. Transmission of the U1.1 reporting files to the CSSF 4.
  44. Transmission channels pursuant to Circular CSSF 23/833 The channels to be used are those operating in accordance with the provisions of Circular CSSF 23/
  45. Two means of transmission are available for this reporting: - Application Programming Interface (API); - eDesk. 4.1.
  46. Application Programming Interface (API) The method of transmitting reports via Application Programming Interface can be found on our website at the following link: https://www.cssf.lu/en/Document/methods-of-transmitting-reportsvia-s3-application-programming-interface-technical-guidance/ On the eDesk IT management console, the "IT Expert" must create a bucket "U1.1 reporting". For this type of reporting, the "U1.1 reporting" bucket must be created by the entity identified as declarant to the CSSF (cf. chapter 2) and/or by a sender defined by the declarant through the delegation process (cf. chapter 3). The API channel allows: - the submission of reports; - the reception of corresponding feedback. Reports submitted via the API channel follow the naming convention described in chapter 4.
  47. 4.1.
  48. eDesk The method of monitoring and transmitting reports via eDesk is available at the following link: https://edesk.apps.cssf.lu/reportingu/edesk-reportingu. The eDesk module allows a declarant (or the senders by delegation) to consult the expected reports for the funds/sub-funds and the reference month under their responsibility (allowed by delegation for a sender), as well as the corresponding status on the CSSF side. The possible statuses are: - Expected: no report has been transmitted for the corresponding fund/sub-fund and reference month, even though one is expected - Derogated: the CSSF has derogated the expected report - Ongoing: the last report received concerning the fund/sub-fund is under the process of validation. Once the validation is complete, the status of the expected report will change depending on the result of the validation - Error: the last report received concerning the fund/sub-fund and reference month has been validated with errors that must be corrected GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 35/51 - Final pending: a "provisional report" for the corresponding fund/sub-fund and reference month has been received and validated without error. A "final report" must be provided as soon as an official net asset value is calculated - Accepted: a "final report" (or "null report" if applicable) has been received and validated without error The consultation of expected reports is available: - by reference months and funds. In this case, the statuses of the expected reports concerning the sub-funds of a specific fund are consolidated in different columns, and details for each sub-fund are accessible through the "Consult" link in the "Action" column; - by reference to months and sub-funds with the status of each expected report displayed directly on the dashboard. For each expected report, defined by a reference month and a sub-fund, a detail screen is available through the "Consult" link in the "Action" column. This detail screen is composed of four tabs: - Summary: it contains all the general information concerning a report - File: it shows all the specific information contained in the report, at sub-fund or share class(es) level - Error: it contains the list of the errors that have eventually been raised during the last validation of the report. For each error, the "Consult and add explanation" button allows the declarant (or the sender allowed by delegation) and/or the CSSF agent to exchange information about a specific error. - Comments: it allows the declarant (or the sender allowed by delegation) and/or the CSSF agent to exchange information about an expected report. The "Upload" button allows the transmission of a report for the fund/sub-fund and reference month, defined in the expected report that has been consulted. The reference month, the fund and the subfund in the file name must correspond to this expected report. At the top of the screen, a drop-down list allows the selection of one report among all the reports that have been linked to an expected report. The last report received is selected by default, as it is the report that is considered as up to date by the CSSF. A received report can only be linked to an expected report: - if it has been uploaded via eDesk, with the action described just above; - if it has been transmitted via S3 channel and has been validated without any "REJECTED" rules raised during its validation (cf. Annex 1 for the list of rules and corresponding severity). It is possible to download the report thanks to a button available in the "Summary" and the "File" tabs. On the homepage of the module, a third dashboard shows all the reports transmitted by a specific entity via S3 bucket. In this dashboard, the data are only accessible for the entity concerned. The technically rejected reports and the reports under validation are only accessible on this dashboard. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 36/51 4.
  49. Sending of U1.1 reporting files All files must be created in XML format (encoded in UTF-8), based on the .XSD model defined in chapter 1.
  50. A new format is available for reference periods as of 12/
  51. New fields are optional in the XSD scheme. Rules RU25[XX] will check that these new fields are filled in for reference periods as of 12/
  52. For reference periods until 11/2025, tags concerning new fields should be omitted; the old format must therefore be used for these periods. It is not possible to add the new tags with an empty value for these periods. The XML initial declaration (<?xml version="1.0" encoding="UTF-8"?>) must be present at the beginning of the report. The files must comply with the following naming convention: TYRDIR-EIIIIIIII-FMMMMMMMM-CCCCCCCC-YYYYMM-TYP-TTTTTTTTTTTT.ext where Code Meaning Structure Authorised values TYR Reporting type Char
(3)"U11" for UCI reporting U11 DIR Direction Char
(3)"REP" for Report  file sent to the CSSF - Separator E Entity type of the Char
(1)Constant "-" Char
(1)Usual entity types, e.g. "B" for banks, declarant or sender "P" for PFS, "I" for support PFS, "S" for management companies, "K" for Sicar, "1" for other companies not supervised by the CSSF, … IIIIIIII Identification number of Number
(8)00000001…99999999 the sender - Separator Char
(1)Constant "-" F Type of UCI Char
(1)"O" or "K" MMMMMMM Number allocated by the Number
(8)00000001…99999999 M CSSF to the entity - Separator Char
(1)Constant "-" CCCCCCCC Number allocated by the Number
(8)00000001…99999999, "00000000" if CSSF to the sub-fund no sub-fund - Separator Char
(1)Constant "-" YYYYMM Period Number
(6)Reporting period - Separator Char
(1)Constant "-" TYP Type of document Char
(3)"RAP" for report - Separator Char
(1)Constant "-" GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 37/51 Code Meaning Structure Authorised values TTTTTTTTTT Timestamp Number
(13)Timestamp in millisecond Extension Char
(5)".xml" TTT .ext Example: U11REP-P12345678-O12345678-000000000-202411-RAP-1234567891234.xml The standardised CSSF identifiers can be found at the link Identifiers of UCI/SIF/SICAR. A file with a duplicate name will be rejected. In case of correction of a previously sent file, the timestamp must be different. The data defined into the XML report must be consistent with the information contained in the file name. A detailed description of each field of the reporting is given in chapter 1.
  1. Additional information can be found in the dedicated FAQ. 4.
  2. CSSF feedback files The data contained in the report files are subject to a list of controls (cf. Annex 1). These controls are performed automatically when a report file is submitted but can also be performed a posteriori to a specific file: - automatically when a corrective file concerning a previous period is submitted; - manually, if the CSSF considers that some changes in its database impact the status of the reporting file. It is the responsibility of the declarant (or sender) to monitor transmission correctness. In case of submission via API, a feedback file is automatically transmitted for each validation of the reporting file. This feedback file complies with the following naming convention: TYRDIR-EIIIIIIII-FMMMMMMMM-CCCCCCCC-YYYYMM-TYP-ttttttttttttt-TTTTTTTTTTTT.ext where Code Meaning Structure Authorised values TYR Reporting type Char
(3)"U11" for UCI reporting U11 DIR Direction Char
(3)"FDB" for feedback  file sent by the CSSF - Separator Char
(1)Constant "-" E Entity type of Char
(1)Usual entity types, e.g. "B" for banks, "P" for the sender PFS, "I" for support PFS, "S" for management companies, "K" for Sicar, "1" for other companies not supervised by the CSSF, … GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 38/51 Code Meaning Structure Authorised values IIIIIIII Identification Number
(8)00000001…99999999 number of the sender - Separator Char
(1)Constant "-" F Type of UCI Char
(1)"O" or "K" MMMMMMMM Number Number
(8)00000001…99999999 allocated by the to CSSF the entity - Separator Char
(1)Constant "-" CCCCCCCC Number Number
(8)00000001…99999999, allocated by the to CSSF "00000000" if no sub-fund the sub-fund - Separator Char
(1)Constant "-" YYYYMM Period Number
(6)Reporting period - Separator Char
(1)Constant "-" TYP Type Char
(3)"RAP" for report of document - Separator Char
(1)Constant "-" ttttttttttttt Timestamp Number
(13)Timestamp in millisecond of the generation of the feedback file - Separator Char
(1)Constant "-" TTTTTTTTTTTTT Timestamp Number
(13)Timestamp in millisecond of the reporting file concerned by the feedback .ext Extension Char
(5)".xml" Example: U11FDB-P12345678-O12345678-000000000-202411-RAP-98765432198761234567891234.xml There is an exception if there is an issue with the name of a report file submitted via the API channel. In this case, the feedback complies with the following naming convention: OriginalFileName-FEEDBACK-U11XXXXXXXXXXXXXXXXXXXXXXXX.ext GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 39/51 where Code Meaning Structure Authorised values OriginalFileName Name Varchar Name of the of the original reporting file original reporting file - Separator Char
(1)Constant "-" FEEDBACK Direction Char
(8)Constant "FEEDBACK" - Separator Char
(1)Constant "-" U11XXXXXXXXXXXXXXXXXXXXXXXX Identifier Varchar U11 + unique identifier .ext Extension Char
(5)".xml" The feedback file generated contains two pieces of information: - the identifier of the report; - the global status of the controls. This feedback reflects the report's status following the completion of all technical checks. Please note that, for each report, the CSSF performs additional validations after these technical checks. Consequently, the sender must consult the report's status directly on eDesk, as this is the source that prevails. This status is subject to change after the initial receipt of the report. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 40/51
  1. Contact information For any questions, please contact edesk@cssf.lu. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 41/51 Annex 1: List of controls concerning U1.1 reporting file Error code Severity Error message Error description R1010B ERROR The reference month [YYYYMM] is invalid. The reference month (field 1010) is invalid. The field must contain a value greater than or equal to "201606". ERROR Launch date, financial information on the UCI and on the unit/share class, general information on the unit/share class and information on investment income and expenses must be empty for "null report". Launch date, financial information on the UCI and on the unit/share class, general information on the unit/share class and information on investment income and expenses must be empty for "null report". R1020D ERROR Launch date, financial information on the UCI and on the unit/share class, general information on the unit/share class and information on investment income and expenses must be filled for "final report" or "provisional report". Launch date, financial information on the UCI and on the unit / share class, general information on the unit/share class and information on investment income and expenses must be filled for "final report" or "provisional report". R1020E ERROR This report is a final report. Some previous reports are provisional. Please submit the final versions. This report is a final report. Some previous reports are provisional. Please submit the final versions. R1030A ERROR The sender code does not exist. The sender code (field 1030) must exist in the CSSF database. R1030B REJECTED The sender is not authorised to transmit a report for this UCI and this reference period. The sender must be defined as responsible for the NAV calculation and accounting function for the fund and the reference period. The sender can also be delegated by the responsible for this function and reference period. R1050A ERROR The email address does not have a valid format. The email address must have a valid format. R2010A ERROR The UCI code does not exist. This UCI code (fund) must exist in the CSSF database. R2010B ERROR The sub-fund code does not exist. This UCI code (sub-fund) must exist in the CSSF database. R2030A ERROR The ISO3 capital currency code does not exist. The currency code must exist in the CSSF database. R2030B ERROR The ISO3 capital currency code does not match the historic code referenced for the UCI inside the CSSF database. The currency must correspond to the currency in the CSSF database on the last day of the reference month. R2040A ERROR The LEI code does not have a valid format. The LEI code does not have a valid format. It must contain 20 digits and be a valid code according to the LEI code rules. R2040B ERROR The LEI code does not match the one defined in the CSSF database. The LEI code does not match the one defined in the CSSF database. R1020C Error code Severity Error message Error description R2050A ERROR The valuation date is invalid: it must be before or equal to the reference month plus 10 days. The valuation date (field 2050) is invalid. The field must contain a date before or on the 10th day after the end of the reference period (e.g. for the reference period 201606, the validation date must be before or equal to 10.07.2016). R2050B ERROR The valuation date is invalid: it must be less than or equal to the maturity date. The valuation date is invalid, it must be a date before the maturity date. R2070A ERROR The launch date is invalid: it must be before or equal to the valuation date. The launch date (field 2070) is invalid. The launch date must be before or equal to the valuation date. R2070B ERROR The launch date is invalid: it must be included in the reference month as the previous report is a null report. The launch date in the file is invalid. For a UCI which is no longer temporarily closed, the launch date must be included in the reference month. R2070C ERROR The launch date is invalid: it must be equal to the previous report launch date. The launch data in the file is invalid. For a UCI which has not been temporarily closed in the previous period, the launch date must be equal to the launch date in the previous report. R2080A ERROR The closing date is invalid: it must be before or equal to the valuation date. The closing date (field 2080) is invalid. If the closing date field is filled, this date must be before or equal to the valuation date. R2080C ERROR The closing date is invalid: it must be later than or equal to the launch date. The closing date (field 2080) is invalid. If the closing date field is filled, this date must be later than or equal to the launch date. The total NAV of preceding reference month is invalid. The total NAV of the preceding reference month (field 3010) is invalid. In the case of a "Null Report", for the preceding reference month the NAV must be
  2. In all other cases, the NAV of the current report must be the same as the NAV of the preceding report (field 3020 in the preceding report). R3010A ERROR The total NAV (field 3020) of the reference month is invalid. The total NAV must be equal to total NAV of the preceding month (field 3010) R3020A ERROR The total NAV of the reference month is invalid. + proceeds from all unit/shares issued during the reference month (field 3030) - payments made for all units/shares redeemed during the reference month (field 3040) - total distribution made during the reference month (field 3050) + Sum of dividends on all shares (field 6010) GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 43/51 Error code Severity Error message Error description + dividends on all UCI units/shares (field 6020) + all the interests on bonds and other debt securities (field 6030) + all Interest on loans, bank and other interest-bearing accounts (field 6040) + other income (field 6050) - charges (field 6060) - performance fees (field 6070) - other expenses (field 6080) + net realised profit or loss on investments and foreign exchange positions (field 6090) + net unrealised profit or loss on investments and foreign exchange positions (field 6100) ERROR The total NAV of the reference month is invalid. The total NAV (field 3020) of the reference month is invalid. The total NAV must be equal to the sum of all number of outstanding units/shares multiplied by the NAV per unit/share in the UCI base currency (sum of all (field 5010 * field 5020)). ERROR The proceeds from all units/shares issued during the reference month are invalid. The proceeds from all units/shares issued during the reference month are invalid. This figure must be equal to the sum of proceeds of all from units/shares issued for the unit/share class in the UCI base currency (sum of all fields 5050). ERROR The payments made for all units/shares redeemed during the reference month are invalid. The payments made for all units/shares redeemed during the reference month are invalid. This figure must be equal to the sum of all payments made for the units/shares redeemed for the unit/share class in the UCI base currency (sum of all fields 5060). R3050A ERROR The total distributions made during the reference month are invalid. The total distributions made during the reference month are invalid. This figure must be equal to the sum of all the total distributions made for the unit/share class in the UCI base currency (sum of all fields 5070). R4010A ERROR The UCI unit/share class type code does not exist. This UCI unit/share class type must exist in the CSSF database. R4030A ERROR The ISO3 capital currency code of the unit/share class does not exist. This currency code of the UCI unit/share class must exist in the CSSF database. R4040A ERROR The ISIN code does not follow the expected format for an ISIN code. The ISIN code does not have a valid format. It must contain 12 digits and be a valid code according to the ISO 6166 rules. R3020B R3030A R3040A GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 44/51 Error code Severity Error message Error description R4040B ERROR The ISIN code does not match the one defined in the CSSF database. The ISIN code does not match the one defined in the CSSF database. R4050A ERROR The launch date of the unit/share class is invalid: it must be before or equal to the valuation date. The launch date of the unit/share class (field 4050) is invalid. The launch date of the unit/share class must be before or equal to the UCI valuation date (field 2050). R4050B ERROR The launch date of the unit/share class is invalid: it must be later than or equal to the launch date. The launch date of the unit/share class (field 4050) is invalid. The launch date must be later than or equal to the UCI launch date (field 2070). R4060A ERROR The closing date of the unit/share class is invalid: it must be before or equal to the valuation date. The closing date of the unit/share class (field 4060) is invalid. The closing date of the unit/share class must be empty or contain a date before or equal to the valuation date. R4060B ERROR The closing date of the unit/share class is invalid: it must be later than or equal to the launch date of the unit/share class. The closing date of the unit/share class (field 4060) is invalid. The closing date of the unit/share class must be empty or contain a date later than or equal to the launch date. R4080A ERROR The unit/share class with specific instruments - FX is invalid: it must be the same as in the preceding report. The field "Unit/share with specific instruments -FX" is invalid. The field must contain the same value as in the preceding report. R4090A ERROR The unit/share class with specific instruments - Interest Rate is invalid: it must be the same as in the preceding report. The field "Unit/share with specific instruments -Interest Rate" is invalid. The field must contain the same value as in the preceding report. R4100A ERROR The unit/share class with specific instruments - Other is invalid: it must be the same as in the preceding report. The field "Unit/share with specific instruments -other" is invalid. The field must contain the same value as in the preceding report. ERROR The amount of distributions made per unit/share in the UCI base currency is invalid. The amount of distributions made per unit/share in the UCI base currency (field 5080) is invalid. If the total distribution made in the UCI base currency (field 5070) is a positive figure, this field must also contain a positive figure. R5090A ERROR The amount of distributions made per unit/share in the base currency of the unit/share class is invalid. The amount of distributions made per unit/share in the base currency of the unit/share class (field 5090) is invalid. If the total distribution made in the UCI base currency (field 5070) is a positive figure, this field must also contain a positive figure. R5100A ERROR The total income per unit/share of the reference month is invalid. The sum of the income per unit/share (fields 5100) of the reference month is invalid. R5080A GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 45/51 Error code Severity Error message Error description The sum of all incomes per unit/share in the base currency of the UCI (the sum of all fields 5100) must be equal to the sum of: dividends on all shares (field 6010) + dividends on all UCI units/shares (field 6020) + all the interests on bonds and other debt securities (field 6030) + all bank interests (field 6040) + other income (field 6050) + net realised profit or loss on investments and foreign exchange positions (field 6090) + net unrealised profit or loss on investments and foreign exchange positions (field 6100) R5110A ERROR The total expenses per unit/share of the reference month is invalid. The sum of expenses per unit/share (fields 5110) of the reference month is invalid. The sum of all the expenses per unit/share in the base currency of the UCI (sum of all fields 5110) must be equal to the sum of: charges (field 6060) + performance fees (field 6070) + other expenses (field 6080) R6011A ERROR The dividends on units/shares of which from Luxembourg are invalid: the field must be less than or equal to the dividends on units/shares. The dividends on units/shares of which from Luxembourg (field 6011) are invalid. This field must contain a figure which is less than or equal to the dividends on units/shares (field 6010). R6021A ERROR The dividends on UCI units/shares of which from Luxembourg are invalid: the field must be less than or equal to the dividends on UCI units/shares. The dividends on UCI units/shares of which from Luxembourg (field 6021) are invalid. This field must contain a figure which is less than or equal to the dividends on UCI units/shares (field 6020). ERROR The interest on bonds and other debt securities of which from Luxembourg is invalid: it must be less than or equal to the interest on bonds and other debt securities. The interest on bonds and other debt securities of which from Luxembourg (field 6031) is invalid. This field must contain a figure which is less than or equal to the interest on bonds and other debt securities (field 6030). R6031A R6040A ERROR The interest on loans, bank and other interest-bearing accounts is invalid. The interest on loans, bank and other interest-bearing accounts (field 6040) is invalid. The interest on loans, bank and other interest-bearing accounts (field 6040) must be equal to the sum of: bank interest (field 6041) + other interest (field 6043) GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 46/51 Error code Severity Error message Error description R6042A ERROR The bank interest of which from Luxembourg is invalid: it must be less than or equal to the bank interest. The bank interest of which from Luxembourg (field 6042) is invalid. This field must contain a figure which is less than or equal to the bank interest (field 6041). R6044A ERROR The other interest of which from Luxembourg is invalid: it must be less than or equal to the other interest. The other interest of which from Luxembourg (field 6044) is invalid. This field must contain a figure which is less than or equal to the other interest (field 6043). The other income (field 6050) is invalid. The other income (field 6050) must be equal to sum of: R6050A ERROR The other income is invalid. rental income (field 6051) + commission income (field 6052) + other (field 6053) The charges (field 6060) are invalid. The charges (field 6060) must be equal to sum of: advisory and/or management commissions and/or fees (field 6061) + depositary commissions and/or fees (field 6062) R6060A ERROR The charges are invalid. + UCI administration fees (field 6063) + audit and inspection fees (field 6064) + distribution fees (field 6065) + other administrative expenses (field 6066) + subscription tax (field 6067) + other tax (field 6068) The other expenses (field 6080) are invalid. The other expenses (field 6080) must be equal to sum of: interest paid (field 6081) R6080A ERROR The other expenses are invalid. + personnel expenses (field 6082) + rental expenses (field 6083) + amortisation (field 6084) + other (field 6085) RINVAL01 REJECTED The report is invalid. The report is rejected for security policy reasons. RINVAL02 REJECTED Error during the transmission of the report. Please try again later. Error during the transmission of the report. Please try again later. RNA01 ERROR The report was not expected for the reporting period. No report was expected for this UCI for this reference period. No report is expected for a UCI which is closed, liquidated or merged. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 47/51 Error code Severity Error message Error description RNA02 REJECTED The report for this sub-fund was not expected for the reporting period. The report for this sub-fund was not expected for the reporting period. RNA03 REJECTED The report is not required for the reporting period due to the liquidation, merger, or another event related to the UCI RNA04 REJECTED The report is not required for the reporting period due to the liquidation, merger, or another event related to the sub-fund. The report is not required for the reporting period due to the liquidation, merger, or another event related to the sub-fund. RNA05 REJECTED The report for this sub-fund is not required for the reporting period, as the sub-fund has been removed from the prospectus The report for this sub-fund is not required for the reporting period, as the sub-fund has been removed from the prospectus. RNOM00 REJECTED The filename doesn’t respect the expected naming convention The filename must respect the naming convention "TYRDIR-EIIIIIIIIFMMMMMMMM-CCCCCCCC-YYYYMM-RAP-TTTTTTTTTTTTT.ext". RNOM16 ERROR The CSSF code of the UCI in the filename does not match the UCI defined in the report content. The entity code (field 2010) in the file must correspond to the UCI type and code in the file name. RNOM17 ERROR The CSSF code of the sub-fund in the filename does not match the sub-fund defined in the report content. The UCI sub-fund code (field 2010) in the file must correspond to the UCI sub-fund code in the file name. RNOM20 ERROR The CSSF code of the sender in the filename does not match the CSSF code of the sender defined in the report content. The code of the sender (field 1030) in the file must correspond to the code of the sender in the file name. RNOM22 ERROR The reference month in the filename does not match the reference month defined in the report content. The reference month (field 1010) in the file must correspond to the period in the file name. RNOM23 REJECTED The CSSF sender code in the file name must correspond to the CSSF entity code associated to the S3 bucket used for the transmission. The CSSF sender code in the file name must correspond to the CSSF entity code associated to the S3 bucket used for the transmission. RNOM24 REJECTED The UCI or the sub-fund defined in the filename does not exist. The UCI code in the filename must exist in the CSSF's database. RNOM25 REJECTED The reference month defined in the filename must be later than or equal to
  3. The reference month defined in the filename must be later than or equal to
  4. RSGN06 ERROR According to the data in the CSSF database, a closing date is expected for this sub-fund. A closing date is expected for this sub-fund. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 The report is not required for the reporting period due to the liquidation, merger, or another event related to the UCI. 48/51 Error code Severity Error message Error description RSTAT02 ERROR The calculated net return in the base currency of the share class should be equal to the net return displayed in line
  5. A margin of 10% is permitted. The calculated net return in the base currency of the share class should be equal to the net return displayed in line
  6. A margin of 10% is permitted. RU25[XX] ERROR The field "NomDuChamp" must be provided as the reporting period is equal to or greater than December
  7. The field "NomDuChamp" must be provided as the reporting period is equal to or greater than December
  8. RXSD ERROR Technical error: Invalid XML format from report U
  9. This is a technical error message. The XML format of the report is invalid. GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 49/51 Annex 2: U1.1 reporting item description Code Field name EN M/O*1 NR*2
  10. General information on the report and the sender 1010 1020 1030 1031 1032 1040 1050 Reference month Reporting status CSSF code of the sender Intentionally left blank Intentionally left blank Name of the employee and phone number Email address M M M M*3 M*3 M*4 M*4 M M M M*3 M*3 M*4 M*4 M M*3 M*3 M M M*5 M M M O O M M M M*3 M*3 M M O O O O O O O O
  11. General information on the UCI 2010 2011 2012 2020 2030 2040 2050 2060 2070 2080 2090 2100 2110 CSSF code of the UCI (CSSF code of the entity and CSSF code of the sub-fund) Intentionally left blank Intentionally left blank Name of the UCI (name of the entity and name of the sub-fund) Base currency of the UCI LEI code Valuation date NAV calculation frequency Launch date Closing date Reason for closing Redemption frequency Open- / Closed-end
  12. Financial information on the UCI in the base currency of the UCI 3010 3020 3030 3040 3050 Total net asset value of the preceding reference month Total net asset value of the reference month Proceeds from all units/shares issued during the reference month Payments made for all units/shares redeemed during the reference month Total distributions made during the reference month M M M M M
  13. General information on the unit/share class (to be filled in separately for each unit/share class) 4010 4020 4030 4040 4050 4060 4070 4080 4090 4100 4110 CSSF code of the unit/share class Name of the unit/share class Base currency of the unit/share class ISIN code Launch date of the unit/share class Closing date of the unit/share class Reason for closing of the unit/share class Unit/share class with specific instruments – FX Unit/share class with specific instruments – Interest Rate Unit/share class with specific instruments – Other Investor base M M M M*6 M O O M M M M
  14. Financial information on the unit/share class for the reference month (to be filled in separately for each unit/share class) 5010 5020 5030 5040 5050 5060 Number of outstanding units/shares Net asset value per unit/share in the base currency of the UCI Net asset value per unit/share in the base currency of the unit/share class Net return per unit/share in the base currency of the unit/share class Proceeds from units/shares issued in the base currency of the UCI Payments made for units/shares redeemed in the base currency of the UCI M M M M M M 5070 5080 5090 5100 5110 Total distributions made in the base currency of the UCI Amount of distributions made per unit/share in the base currency of the UCI Amount of distributions made per unit/share in the base currency of the unit/share class Income in the base currency of the UCI Expenses in the base currency of the UCI M M M M M
  15. Information on investment income and expenses for the reference month in the base currency of the UCI 6010 6011 6020 6021 6030 6031 6040 6041 6042 6043 6044 6050 6051 6052 6053 6060 6061 6062 6063 6064 6065 6066 6067 6068 6070 6080 6081 6082 6083 6084 6085 6090 6100 Dividends on shares - of which from Luxembourg Dividends on UCI units/shares - of which from Luxembourg Interest on bonds and other debt securities - of which from Luxembourg Interest on loans, bank and other interest-bearing accounts Bank interest - of which from Luxembourg Other interest - of which from Luxembourg Other income Rental income Commission income Other Charges Advisory and/or management commissions and/or fees Depositary commissions and/or fees UCI administration fees Audit and inspection fees Distribution fees Other administrative expenses Subscription tax Other tax Performance fees Other expenses Interest paid Personnel expenses Rental expenses Amortisation Other Net realised profit or loss on investments and foreign exchange positions Net unrealised profit or loss on investments and foreign exchange positions M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M M *1Mandatory/Optional *2Null report *3with a no value *4for at least one contact person *5if the UCI has been allocated a LEI *6if the unit/share class has been assigned an ISIN code GUIDELINES ON THE U1.1 REPORTING Version 6.7 (EN) of 27/04/2026 51/51

🔗 Vers la source officielle

AI explanation based on the official legal text. Indicative, not a substitute for legal advice.