under the freedom to provide services (FPS). This includes the management of a UCITS established in another Member State (Articles 114 and 115 of the 2010 Law); Authorised AIFMs that, in accordance with Article 5 of the Law of 12 July 2013 on alternative investment fund managers (the “2013 Law”), intend to manage, either directly (FPS)
via the establishment of a branch, EU AIFs (authorised
not) established in another Member State and/
to provide in another Member State the services referred to in Article 5
via the CSSF API solution (S3 technology). The eDesk Portal can be accessed at https://edesk.apps.cssf.lu/edesk-dashboard/dashboard/getstarted. The relevant procedure is the “IFM Cross-border Management Notifications Tool”. Please note that the subsequent monitoring of these notifications will be carried out exclusively via the eDesk Portal. Additional information and instructions can be found in the dedicated user guide: IFM Guidelines on cross-border management notification and de-notification procedures. For any questions, please contact our helpdesk at edesk@cssf.lu. Finally, the CSSF takes this opportunity to remind the supervised entities concerned that they should notify the CSSF of all the activities and services they intend to provide on a cross-border basis, regardless of whether these activities and services will be provided under the free provision of services
via the establishment of a branch. 22 April 2026 - Updated on 26 June 2026 IFM guidelines on cross-border management notification and de-notification procedures To be followed by Luxembourg investment fund managers Technical document PDF (748.98Kb) Relevant for Alternative investment fund managers Management companies - Chapter 15 IFM Guidelines on crossborder management notification and denotification procedures To be followed by Luxembourg Investment Fund Managers CONTENTS
de-notification submission .................................................................................................................... 5 3.1 The AIFM notification file submitted to the CSSF must contain the following documents: .............................................................................. 5 3.3 CSSF attestation document ................................................................................................................................................................... 9
an API solution. For any questions regarding these guidelines please contact edesk@cssf.lu. 2. Scope The following supervised entities must comply with the cross-border management notification and de-notification procedures, including any updates for: a. Luxembourg-domiciled UCITS management company wishing to: - pursue in another Member State, the activities for which it has been authorised, either by the establishment of a branch
under the freedom to provide services (FPS). This includes the management of a UCITS established in another Member State (Articles 17 and 18 of Directive 2009/65/EC (the “UCITSD”)). b. Luxembourg AIFMs wishing to: - manage, either directly (FPS)
via the establishment of a branch, an AIF (regulated
not) established in another Member State and/
to provide in another Member State the services referred to in Article 6
to manage a fund in another Member State IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 4 � An IFM wishing to notify both the FPS and the establishment of a branch in a given Member State must introduce two separate notifications, one for the FPS and one for the branch 3. Documentation of the notification
de-notification submission 3.1 The AIFM notification file submitted to the CSSF must contain the following documents 1: The following documents are mandatory: Type of document Abbreviation Notification letter of the LN IFM on its intended Specifications on the formatting and mapping of the notification letter are provided in Annex
mandatory only in certain situations: Type of document CSSF Annex to the Abbreviation LNA Notification letter Forecast statements Specifications The latest version of the CSSF Annex to the Notification letter must be annexed to the file for notification of the establishment of a branch. FS The latest version of the Forecast statements must be annexed to the file for notification of the establishment of a branch. Branch
ganisational BOC structure chart Manager The latest version of the
ganisation chart of the branch must be annexed to the file for notification of the establishment of a branch. MOC
ganisational The latest version of the Manager
ganisational structure chart must be annexed to the file for notification of the establishment of a branch. structure chart including the branch Branch manager(s)' BMD documents (CR, CV, The Branch manager(s)’ documents must be annexed to the file for notification of the establishment of a branch. DH and ID) Schedule of planned ST termination of a A schedule of planned termination of the branch must be annexed to the file for de-notification of the branch. branch CSSF Annex – TA Termination of the The latest version of the CSSF Annex to the termination of the operation of the branch must be annexed to the file for de-notification of the branch. operation of a branch CSSF Annex – MiFID MA Annex The latest version of the CSSF Annex - MiFID ANNEX to the notification letter under Articles 17 and/
18 of Directive 2009/65/EC (UCITSD) and/
FID activities are passported. Others OT Any other additional document(
mandatory only in certain situations: 2 Annex 2 provides the detailed list of documents to be submitted depending on the chosen options as well as the expected indexation IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 7 Type of document CSSF Annex to the Abbreviation Specifications LNA The latest version of the CSSF Annex to the Notification letter must be annexed to the file for notification Notification letter Forecast statements of the establishment of a branch. FS The latest version of the Forecast statements must be annexed to the file for notification of the establishment of a branch. Branch
ganisational BOC structure chart Manager The latest version of the
ganisation chart of the branch must be annexed to the file for notification of the establishment of a branch. MOC
ganisational The latest version of the Manager
ganisational structure chart must be annexed to the file for notification of the establishment of a branch. structure chart including the branch Branch manager(s)' BMD documents (CR, CV, The Branch manager(s)’ documents must be annexed to the file for notification of the establishment of a branch. DH and ID) Schedule of planned ST termination of a A schedule of planned termination of the branch must be annexed to the file for de-notification of the branch. branch CSSF Annex – TA Termination of the The latest version of the CSSF Annex to the termination of the operation of the branch must be annexed to the file for de-notification of the branch. operation of a branch CSSF Annex – MiFID MA Annex The latest version of the CSSF Annex - MiFID ANNEX to the notification letter under Articles 17 and/
18 of Directive 2009/65/EC (UCITSD) and/
FID activities are passported. Others OT Any other additional document(
de-notification for IFM can also be transmitted through the CSSF API solution (S3 technology). All data submitted to the CSSF as part of the tool must comply with the information indicated in the notification letter document, which is attached to the notification. 4.1 eDesk portal transmission 4.1.1 Connection to the tool The tool can be accessed through a secured connection module after being authenticated with a Luxtrust certificate. Please note that the prerequisites enabling a connection to eDesk are detailed in the “Authentication and user account management” user guide in the eDesk portal home page (https://edesk.apps.cssf.lu/edesk-dashboard/dashboard/getstarted). 4.1.2 Notification dashboard The main part of the home view is a dashboard providing a general view of all notifications requested by the entity, with filtering and sorting functionalities. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 9 The following columns are provided: - Identifier - IFM type (UCITS, AIFM) - Notification type (IFM – Initial, IFM – Update, IFM - De-notification) - FPS
Branch - IFM ID - IFM name - Host country - Status (Cancelled, Initialisation, Submitted, Accepted by CSSF – Sent to host, Rejected by CSSF, Rejected by host, Accepted by host, Under analysis - CSSF, Under analysis - host) - Creation date - Created by - Submission date - Comments status - Channel - Actions (click on the magnifying glass icon
double-click on a given line). 4.1.3 Creation of a notification request Press the “Add” button on top of the dashboard, a pop-up window is created. Proceed with the following steps: Specify the type of IFM Select the IFM Select FPS
Branch Select the notification type (IFM – Initial, IFM – Update, IFM - De-notification) Select a host country Click on the “Create” button IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 10 4.1.4 Detailed view By double-clicking on a specific line of the dashboard, the detailed view of the notification appears in the main screen. The screen is split into three parts: navigation menu, section content and request summary. 4.1.4.1 Navigation Menu The left part of the screen is dedicated to the navigation through the following tabs: Description, Branch (only for Branch notification not for FPS notification), Activities and Attached documents, which will be described below. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 11 4.1.4.1.1 Description This section enables you to edit the purpose of the notification and, in case of an amendment concerning a branch, to indicate if an update of the CSSF Annex is required. This will also allow you to indicate if you intend to use a tied agent to provide your services. Please also follow the guidance indicated in the blue box on the application. 4.1.4.1.2 Branch This section is available only for establishment of a branch request (not for an FPS request). This section enables you to provide information on the branch (name and address) and its manager(s) (name, birth date, email and phone number). 4.1.4.1.3 Activities This section enables you to indicate the activities you want to passport. This should reflect the information defined in the notification letter document. � In case of an amendment, ALL activities already previously notified should be indicated with the status “Already notified”. Other statuses are “Addition”
“Removal”. When passporting Investment management, you should also indicate whether you also intend to notify the management of a local fund in the notification. In that case, ensure to have already declared the management of that fund to the CSSF via the dedicated eDesk procedure “OPC - Generic Request”. 4.1.4.1.4 Attached documents This section enables you to attach all the necessary documents to the notification file. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 12 The following columns are available: - Document type - Modified name - Document date -
iginal document name - Upload date - Request version id - Status - Actions o o o Delete: To delete a provided document. Details: To view more information regarding the document (document name, document type, entity/instrument, reference date, language, annex number and file extension)
select another document in replacement of an existing one. Download: To download the document to your device. To add a document, simply press the “Add” button. Depending on the size of the file, the upload and feedback of the documents may take additional time. � Documentation related to the notification of the use of a tied agent should be added as Document type “Other”. � There are two sections: one for documents related to the IFM and one for the documents related to the branch manager. 4.1.4.1.5 CSSF comments CSSF exchanges comments with the applicant on its own initiative (if necessary) via a list of topics. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 13 A topic is composed of an identifier (Id), a short but concise description of the subject and the comment itself (“Content”) The light blue box on the top of this screen provides more details on the exchange of comments/information with the CSSF To reply to the comments, the request must be in draft mode (see point 4.1.4.4 below): To reply to a CSSF Comment: Access the detailed view of the respective topic, click on “Add a response” and press “Save” when the response is complete. The selected answers will be sent to the CSSF when you submit the new version of the request. When submitting the request, a blocking message will inform you if not all comments have been replied. Things to know regarding the amendment of a document attached to the notification: You can either delete the document to be modified and attach the new one,
click on the document, (“Detail” button), select the file and upload the new document. The old document will be replaced automatically. Things to know regarding the topic statuses: A single topic can have the following statuses: - “To be replied”: CSSF is awaiting a response - “Replied and to be sent”: the reply is added but not yet transmitted (the name of the person having responded is displayed). If the topic hasn’t been transmitted, it is not visible to the CSSF - “Replied and sent”: after the transmission of the comments, apart from the name, the date and time of transmission are also displayed in the details of the comment. In addition, the “Transmission date” and “Reception date” of a topic are updated in the Comments table after every transmission of the comments 4.1.4.1.6 Host follow-up Once the CSSF has accepted the notification request, the notification is transmitted to the host Member state via email. The follow-up on transmissions is accessible through the "Host follow-up" section. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 14 The following columns are provided: - Country - Status (Accepted by CSSF (Transmitted to HOST), Under analysis HOST, Accepted by HOST, Rejected by HOST) Last modification date 4.1.4.1.7 Submission result See point 4.1.5. 4.1.4.2 Section Content The main part of the screen on the right displays the fields to be filled in related to the section selected on the left. The form can be filled in by pressing the “Edit” button. Then select “Save”
“Cancel” for the applicable data entry action. Please note that: (
BRANCH, notification type, selected IFM, identifier, host country, creation date, status, version, version status, submission date, validation status, agent in charge IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 15 4.1.4.4 Action buttons on the request The last part of the screen (top right) contains the action buttons of the request: The “Submit” button is always visible when the request is in draft mode. The “Draft” button is always visible after submission of the first version of the request to the CSSF. The button is no longer visible once the CSSF has accepted the request, but it is always possible to prepare and submit new versions of the request. The “Cancel” button replaces the “Draft” button when the latter is selected. The button remains visible once the CSSF has accepted the request to ensure that, if there is a draft in progress, it remains possible to revert to the version already accepted o 4.1.5 In case of a draft cancellation, all modifications of the forms and the attached documents will be lost, whereas the possible responses already given to comments received by the CSSF will be kept Notification file processing The CSSF will proceed to evaluate the submitted notification which entails a series of formal verifications to ensure that the notification documentation is complete and compliant. An indicative table of the rules to which a notification request submitted via eDesk may be subject to is available in Annex 4. If any errors are detected when submitting the notification, the "Submission result" section allows you to consult them. If the CSSF notices during the formal checks upon receipt that the file is incomplete
does not comply with the specified technical requirements, it will inform the applicant through the eDesk channel. The CSSF will inform the applicant why the file cannot be transmitted to the corresponding competent authorities. In this case, the applicant will need to transmit an amended version of the notification request taking into account the CSSF feedback. If an authority of a host Member State does not accept a notification file sent by the CSSF, the applicant will be informed of the reason(s) for the rejection through the eDesk channel. In this case, the applicant must transmit an amended version of the notification request. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 16 4.2 Method Application Programming Interface (API) transmission of transmitting reports via Application Programming Interface can be found on our website following the link https://www.cssf.lu/en/Document/methods-of-transmitting-reports-via-s3-application-programming-interface-technical-guidance/ On the edesk IT management console, the “IT Expert” must create a bucket “Cross-border management notifications”. 4.2.1 General principles The API channel can only be used for the initial filing of a notification request. A package transmitted through the API channel will be subject to a list of controls (see Annex 2 below). If at least one error is raised, the package cannot be integrated into the eDesk platform and must be send again with the necessary modifications. If no error is raised, the package is integrated on the eDesk platform, and the request will be processed by the CSSF. All the following modifications, either on the initiative of the intermediary
in response to CSSF comments, can exclusively be done on eDesk and not through the API channel. The entity authorised to do these modifications is the one indicated as contact entity in the JSON (JavaScript Object Notation) file added to the notification package. In case of double licence (S and A, O and A
K and A), the CSSF code of the entity defined in eDesk (i.e. A, S, K
O) must be used. 4.2.2 Notification package format The notification package must be transmitted in a ZIP file. This package is composed of: - all the documents necessary to the notifications in PDF format; IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 17 - a JSON file containing data concerning the notification, such as the Investment Fund Manager concerned, information on the branch and/
branch managers if applicable, information on the activities
the entity, and user of contact for eDesk. It corresponds to the data available on the eDesk online forms 4.2.2.1 ZIP technical specifications Reporting file must be transmitted via a compressed .zip format. The specifications for zip archive are as follows: Compression algorithm RFC 1951 (DEFLATE Compressed Data Format Specification version 1.3) Multi-volume archives (multi-part zipfile) No Maximum size of a file in the archive 2 Gigabytes Codepage UTF-8 4.2.2.2 ZIP naming conventions The mandatory file naming convention for .zip files is specified in Annex
answer to the CSSF comments through this eDesk module. • REJECTED_CSSF when the package is rejected. That is the case, either when the archive is not technically compliant,
when there is a problem with the reported data. • ACCEPTED_CSSF when the package is accepted by the CSSF and transmitted to the corresponding HOST country. • ACCEPTED_HOST when the package is accepted by the corresponding HOST country • REJECTED_HOST when the package is rejected by the corresponding HOST country 4.2.3.2.2 ReportUids recently processed This part is not applicable to the Cross-border management notifications process as only the request’s initialisation can be done through the API channel. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 20 4.2.3.2.3 Feedback messages A list of the controls done following a submission through the API channel is given in Annex 5. 4.2.4 Monitoring of API transmissions A specific dashboard is available in the dedicated module on eDesk to monitor the transmissions done through the API channel. This dashboard is accessible by clicking on the “Request submitted by S3” button on the module homepage. The packages available in this dashboard are: - the packages rejected due to, either an archive not technically compliant
a problem with the reported data. In this case, it is possible to download the package and the corresponding feedback; - the packages accepted. In this case, it is only possible to download the corresponding package. The request created following the processing of this package is available in the principal dashboard. If the entity linked to the bucket used for the transmission is different from the contact entity defined in the JSON file included in the archive, the rejected packages are listed on the dashboard of the entity linked to the bucket, whereas the accepted packages are listed on the dashboard of the contact entity. 4.2.5 Cleaning of API bucket folders The document Method of transmitting reports via Application Programming Interface (https://www.cssf.lu/en/Document/methods-of-transmitting-reportsvia-s3-application-programming-interface-technical-guidance/) defined a retention period of the files in the “submission” and “feedback” folders of 20 days (cf. question 5.11). As the package transmitted for cross-border management of funds can be particularly large, a specific mechanism has been put in place to purge the “submission” folder of the dedicated bucket. As soon as a feedback file is available in the “feedback” folder of the bucket, the corresponding package of the “submission” folder is deleted. The monitoring of the transmissions can be done thanks to the dashboard described in point 4.2.4. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 21 The retention of the files in the “feedback” folder remains at 20 days. 5. Contact information In case of questions, please contact edesk@cssf.lu IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 22 Annex 1: Notification letter and de-notification letter formatting and mapping Language Context Link EN Notification letter – Notification of the Notification letter – Notification of the intention of an AIFM to manage AIFs established in a Member State other intention of an AIFM to manage AIFs than its Home Member State in accordance with Article 33
to establish a branch established in a Member State other than in accordance with Article 33
to establish a branch in accordance with Article 33
18 of Directive 2009/65/EC notification letter under Articles 17 and/
(UCITSD) and/
of Directive 2011/61/EU (AIFMD) 18 of Directive 2009/65/EC (UCITSD) and/
of Directive 2011/61/EU (AIFMD) IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 23 EN Notification letter – Notification made by a Notification letter – Notification made by a Management Company of its intention to pursue the activities for Management Company of its intention to which it has been authorised in another Member State in accordance with Article 17
18 of Directive 2009/65/EC notification letter under Articles 17 and/
(UCITSD) and/
of Directive 2011/61/EU (AIFMD) 18 of Directive 2009/65/EC (UCITSD) and/
of Directive 2011/61/EU (AIFMD) IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 24 Annex 2: File naming convention description to be observed when transmitting a ZIP package Format: NOTREP-ENNNNNNNN-LU-HH-FORB-TYP-UUID.ext Code Meaning Structure Authorised value NOTREP Reporting type Char
S’ NNNNNNN Identification number Number
BRANCH Char
FPS
BRANCH Char
from a to f (hexadecimal authorised characters). You can find more information about the UUID at Universally Unique IDentifier (UUID). IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 27 Annex 3: File naming convention description for CSSF feedback files Format: SourceFileName_FEEDBACK_TrackingCode.json Code Meaning Structure Authorised value SourceFileName Source Char(N) Submitted file name - Refer to Filename the ZIP File name structure in Annex 2 _ Separator Char
de-notification concerning a branch, a branch must be selected in the Branch section. IFMGT005 In case of initial notification
update notification, at least one activity must be selected in the Activities section. IFMGT006 An invalid document has been uploaded. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 29 IFMGT007 At least one document is still uploading. IFMGT008 All topics in the CSSF comments tab must be replied. IFMGT009 Document Notification letter is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT010 In case of initial notification
update notification with modifications in the annex indicated in the Description section, concerning a branch, document CSSF annex is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT011 In case of update notification with no modification in the annex indicated in the Description section
denotification, concerning a branch, document CSSF annex is forbidden. Please remove it from your request in the Attached documents section. IFMGT012 In case of notification concerning FPS, document CSSF annex is forbidden. Please remove it from your request in the Attached documents section. IFMGT013 In case of initial notification concerning a branch, document Manager
ganisation chart is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT014 In case of de-notification concerning a branch, document Manager
ganisation chart is forbidden. Please remove it from your request in the Attached documents section. IFMGT015 In case of notification concerning FPS, document Manager
ganisation chart is forbidden. Please remove it from your request in the Attached documents section. IFMGT016 In case of initial notification
update notification with addition
removal of branch manager(s), concerning a branch, document Branch
ganisation chart is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT017 In case of de-notification concerning a branch, document Branch
ganisation chart is forbidden. Please remove it from your request in the Attached documents section. IFMGT018 In case of notification concerning FPS, document Branch
ganisation chart is forbidden. Please remove it from your request in the Attached documents section. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 30 IFMGT019 In case of initial notification concerning a branch establishment, document Forecast statement for both profit and loss and cash flow is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT020 In case of de-notification concerning a branch, document Forecast statement for both profit and loss and cash flow is forbidden. Please remove it from your request in the Attached documents section. IFMGT021 In case of notification concerning FPS, document Forecast statement for both profit and loss and cash flow is forbidden. Please remove it from your request in the Attached documents section. IFMGT022 In case of de-notification concerning a branch, document Schedule of planned termination is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT023 In case of initial notification
update notification concerning a branch, document Schedule of planned termination is forbidden. Please remove it from your request in the Attached documents section. IFMGT024 In case of notification concerning FPS, document Schedule of planned termination is forbidden. Please remove it from your request in the Attached documents section. IFMGT025 If the technical remitter is not the concerned IFM, document Mandate is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT026 If the technical remitter is the concerned IFM, document Mandate is forbidden. Please remove it from your request in the Attached documents section. IFMGT029 If a MiFID activity is notified, document CSSF Annex - MiFID annex is mandatory to submit your request. Please add it to your request in the Attached documents section. IFMGT030 If no MiFID activity is notified, document CSSF Annex - MiFID annex is forbidden. Please remove it from your request in the Attached documents section. IFMGT031 In case of initial notification
update notification, concerning a branch, a notification letter for each new
modified branch manager is mandatory to submit the request. Please add the document for <name> in the Attached documents section. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 31 IFMGT032 In case of initial notification
update to notify a new branch manager, concerning a branch, a CV for each new branch manager is mandatory to submit the request. Please add the document for <name> in the Attached documents section. IFMGT033 In case of initial notification
update to notify a new branch manager, concerning a branch, a criminal record extract for each new branch manager is mandatory to submit the request. Please add the document for <name> in the Attached documents section. IFMGT034 In case of initial notification
update to notify a new branch manager, concerning a branch, an identification document for each new branch manager is mandatory to submit the request. Please add the document for <name> in the Attached documents section. IFMGT035 In case of initial notification
update to notify a new branch manager, concerning a branch, a declaration of honour for each new branch manager is mandatory to submit the request. Please add the document for <name> in the Attached documents section. IFMGT036 The activity <name> is duplicated. Please correct this error in the Activities section IFMGT037 In case of update notification concerning a branch, document notification letter is forbidden for deleted branch manager. Please remove the document for <name> in the Attached documents section. IFMGT038 In case of update notification concerning a branch, document CV is forbidden for deleted branch manager. Please remove the document for <name> in the Attached documents section. IFMGT039 In case of update notification concerning a branch, document criminal record is forbidden for deleted branch manager. Please remove the document for <name> in the Attached documents section. IFMGT040 In case of update notification concerning a branch, identification document is forbidden for deleted branch manager. Please remove the document for <name> in the Attached documents section. IFMGT041 In case of update notification concerning a branch, document declaration of honour is forbidden for deleted branch manager. Please remove the document for <name> in the Attached documents section. IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 32 3. Rules on submission on the CSSF API channel (by error code) Submission checks are performed as soon as a package is received in an S3 bucket. The list of errors raised will be made available in the feedback file with a technical code, a label and context information, where applicable. Error Code Label IFMGT001 The archive name is invalid. The expected naming convention Context must follow the regex: CSSF code of the IFM NOTREP- (?<entityCssfCode>[AS]\\d{8})(?<homeCountry>LU)-(?<hostCountry>[A-Z]{2})(?<managementType>(FPS|BRANCH))(?<notifType>(INI|UPD|DEN))-(?<reportUid>[0-9af]{8}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9a-f]{4}-[0-9af]{12}).zip IFMGT002 The archive size cannot exceed 80 MB CSSF code of the IFM IFMGT003 The host country defined in the archive name is not CSSF code of the IFM authorized for a management notification IFMGT004 The investment fund manager defined in the archive CSSF code of the IFM name is not in scope for this type of notification IFMGT005 The archive with the reportUid defined in the filename CSSF code of the IFM has already been received for this entity IFMGT006 The archive is corrupted CSSF code of the IFM IFMGT007 The archive must contain a single JSON file CSSF code of the IFM IFMGT008 JSON file does not respect JSON schema CSSF code of the IFM IFMGT009 The unique identifier in the JSON is different from the CSSF code of the IFM unique identifier used in the archive name IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 33 IFMGT010 The CSSF code of the entity in the JSON file is different CSSF code of the IFM from the CSSF code of the entity used in the archive name IFMGT011 The host country defined in the archive name is not CSSF code of the IFM consistent with the country defined in the JSON file IFMGT012 The management type in the archive name is different CSSF code of the IFM from the management type used in the archive name IFMGT013 The notification type in the JSON file is different from CSSF code of the IFM the notification type used in the archive name IFMGT014 The field “fieldname” is required due to field value CSSF code of the IFM [field:value] IFMGT015 Due to the condition <fieldname1:value>, the field CSSF code of the IFM <fieldname2> value must not be provided IFMGT016 The branch concerned by the update notification
the CSSF code of the IFM de-notification is not linked to the investment fund manager for the specified host country IFMGT017 At least one branch manager must be defined for an CSSF code of the IFM initial notification concerning a branch IFMGT018 Only addition of branch manager is possible for an CSSF code of the IFM initial notification concerning a branch IFMGT019 The branch manager is referenced multiple times (same branchManagerId) IFMGT020 At least one activity must be defined for initial
CSSF code of the IFM branchManagerName CSSF code of the IFM update notification IFMGT021 The activity is referenced multiple times CSSF code of the IFM IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 34 activityName IFMGT022 Only addition of activity is possible for an initial CSSF code of the IFM notification IFMGT023 The CSSF code of the contact entity doesn't CSSF code of the IFM The contact person email address doesn't correspond CSSF code of the IFM correspond to an existing eDesk entity IFMGT024 to a user of the eDesk entity corresponding to the contact entity defined IFMGT025 The size of the document cannot exceed 30Mb CSSF code of the IFM documentName IFMGT026 The document is not present in the archive CSSF code of the IFM documentName IFMGT027 The document is present in the archive but is not defined in the JSON file IFMGT028 The document is referenced multiple times CSSF code of the IFM documentName CSSF code of the IFM documentName IFMGT029 The document references a branch manager that doesn't exist in the JSON file
that has a parameter 'branchManagersTypeOfAction' with a value 'DEL' IFMGT030 The document is invalid CSSF code of the IFM documentName CSSF code of the IFM documentName IFMGT031 Notification letter document is mandatory CSSF code of the IFM IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 35 IFMGT032 CSSF annex document is mandatory for an initial CSSF code of the IFM notification
an update notification involving changes in this annex, concerning a branch IFMGT033 Manager
ganisation chart document is mandatory CSSF code of the IFM for an initial notification concerning a branch IFMGT034 Branch
ganisation chart document is mandatory for an initial notification
an update CSSF code of the IFM notification involving addition
removal of branch manager(s), concerning a branch IFMGT035 Forecast statement for both profit and loss and cash CSSF code of the IFM flow document is mandatory for an initial notification concerning a branch IFMGT036 Schedule of planned termination document is CSSF code of the IFM Mandate document is mandatory as the technical CSSF code of the IFM mandatory for a de-notification concerning a branch IFMGT037 submitter is not the investment fund manager IFMGT039 CSSF Annex - MiFID annex document is mandatory as CSSF code of the IFM at least one MiFID activity is notified in the present notification IFMGT040 The document type is forbidden for an initial notification, an update notification
a de-notification concerning Freedom to Provide Services IFMGT041 The document type is forbidden for a de-notification concerning a branch CSSF code of the IFM documentName CSSF code of the IFM documentName IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 36 IFMGT042 CSSF annex document is forbidden for a de- notification
for an update notification involving no change in this annex, concerning a branch IFMGT043 Schedule of planned termination document is forbidden for an initial notification
an update notification, concerning a branch IFMGT044 Mandate document is forbidden as the technical submitter is the investment fund manager IFMGT046 CSSF Annex - MiFID annex document is forbidden as no MiFID activity is notified IFMGT047 Branch manager notification letter is mandatory for this branch manager as it is a new branch manager
modifications are notified concerning this branch CSSF code of the IFM documentName CSSF code of the IFM documentName CSSF code of the IFM documentName CSSF code of the IFM documentName CSSF code of the IFM branchManagerName manager IFMGT048 Branch manager CV is mandatory for this branch manager as it is a new branch manager IFMGT049 Branch manager criminal record is mandatory for this branch manager as it is a new branch manager IFMGT050 Branch manager identification document is mandatory for this branch manager as it is a new branch manager IFMGT051 Branch manager declaration of honour is mandatory for this branch manager as it is a new branch manager IFMGT054 The notification has been successfully processed and CSSF code of the IFM branchManagerName CSSF code of the IFM branchManagerName CSSF code of the IFM branchManagerName CSSF code of the IFM branchManagerName CSSF code of the IFM is available on eDesk for CSSF validation IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 37 IFMGT055 The notification has been accepted by the CSSF and CSSF code of the IFM transmitted to the corresponding HOST IFMGT057 The notification has been rejected by the CSSF for the reason specified above CSSF code of the IFM rejectedReason IFMGT058 The notification has been accepted by the HOST CSSF code of the IFM IFMGT059 The notification has been rejected by the HOST for the CSSF code of the IFM reason specified above rejectedReason IFM GUIDELINES ON CROSS-BORDER MANAGEMENT NOTIFICATION AND DE-NOTIFICATION PROCEDURES TO BE FOLLOWED BY LUXEMBOURG INVESTMENT FUND MANAGERS 38 Annex 5: Required documents The following table provides the list of documents to be submitted depending on the chosen options for notifications and de-notifications:
AI explanation based on the official legal text. Indicative, not a substitute for legal advice.