Last updated
CSSF AIFM European Passport: Luxembourg Notification and Evidence Guide
AIFM passport evidence map
Use CSSF AIFM European Passport: Luxembourg Notification and Evidence Guide when a CSSF-facing question needs a structured file rather than a loose policy summary. It explains understanding the Luxembourg regulatory obligation, supervisory evidence, internal ownership, and escalation points in CSSF AIFM European Passport: Luxembourg Notification and Evidence Guide, then shows how to map the controlling rule, prepare board or compliance evidence, and know when a CSSF-facing specialist should review the file. The later sections connect aifm passport evidence map, what to check first, and checklist so the next step is easier to judge. Read it before assigning owners or responding to a supervisory request, so the evidence file matches the regulatory question.
| Passport layer | Evidence to retain | Question it answers |
|---|---|---|
| Scope and host state | Management or marketing route, host-state list, fund details and notification package. | What activity is being passported and into which country? |
| Investor and fund documents | Offering documents, AIFM details, depositary/service-provider evidence and risk disclosures. | Do investor-facing materials match the passport notification? |
| Amendment control | Change log, CSSF or host-state correspondence, board approvals and implementation date. | Was the passport file updated when the fund or activity changed? |
Direct answer
Direct regulatory answer: a Luxembourg-based authorised AIFM that intends, for the first time, to manage AIFs established in another Member State must notify the CSSF of the Member State and provide a programme of operations; if it intends to establish a branch, it must also provide branch structure, document address, and responsible-person details. The operational decision is whether the planned activity is direct management, branch activity, services under Article 5(4), a later material change, or an inbound EU/EEA AIFM matter. Verify first: AIFM authorisation status, AIF identity, host Member State, service route, complete documentation, eDesk submission requirement, and whether any host-state or ESMA Q&A point needs separate handling.
This page provides general regulatory information, not legal advice. It uses the CSSF AIFM European passport page, last updated by the CSSF on 22 April 2026, as the controlling source.
What to check first
The first control is scope. The CSSF page concerns Luxembourg-based AIFMs managing AIFs in another Member State, and it also explains how EU/EEA AIFMs intending to manage Luxembourg AIFs interact through their Home State authority. Do not treat "passport" as a generic marketing clearance. The file should state exactly which AIFM, which AIF, which host Member State, which service, and which route are covered.
The second control is timing. The CSSF states that notifications must be submitted exclusively through the dedicated eDesk portal. Once complete documentation is received, the CSSF transmits within one month for direct management and within two months for a branch, subject to the legal conditions stated on the CSSF page. Material changes must be notified at least one month before planned implementation, or immediately after an unplanned change.
Decision matrix
| Situation | Source/evidence | Operational action | Supervision risk | Fallback |
|---|---|---|---|---|
| Luxembourg AIFM first manages AIFs directly in another Member State | CSSF AIFM passport page; AIFM authorisation; Member State; programme of operations | Prepare complete eDesk notification and track one-month CSSF transmission period after completeness | Starting from an incomplete or untransmitted file can create cross-border control gaps | Hold activity until CSSF process status and host scope are confirmed |
| Luxembourg AIFM establishes a branch | Branch structure, document address, responsible-person names and contact details | Add branch-specific information to eDesk notification and track two-month CSSF transmission period after completeness | Missing branch governance details can delay or weaken the file | Escalate to compliance/legal adviser before branch launch if responsibility or address evidence is incomplete |
| Article 5(4) services are included | Programme of operations and applicable CSSF forms/annexes | Check whether additional annex documentation is needed before submission | Services may be misdescribed or over-claimed | Freeze distribution language until source documents match the notified service |
| Material change to original information | Change log, planned date, affected notification, updated documents | Notify CSSF at least one month before planned change, or immediately after unplanned change | Change made before notification can undermine the passport file | Escalate and document interim controls if change is urgent or already occurred |
| EU/EEA AIFM entering Luxembourg | Home State authority route; CSSF page; ESMA Q&A 711 point where relevant | Use Home State authority process and check whether direct notification to [email protected] is needed | Wrong authority route can delay Luxembourg activity | Ask legal adviser to confirm inbound route and any direct CSSF notification point |
Checklist
- Artifacts/documents: AIFM authorisation evidence, AIF list, target Member State list, programme of operations, branch organisation chart if applicable, address for obtaining documents, responsible-person contacts, forms/annexes, eDesk submission receipt, CSSF transmission notice, and change log.
- Internal owner: regulatory reporting or compliance should control the notification file; portfolio or product team should own business-scope facts; legal adviser should review unclear passport perimeter or host-state issues.
- Evidence to keep: completeness checklist, submission date, CSSF acknowledgement or transmission notice, versioned documents, host-country scope, investor or activity assumptions, and material-change assessment.
- Official source to check: the CSSF AIFM European passport page before using deadlines, forms, eDesk requirements, or inbound AIFM instructions.
- Escalate when: the activity includes branch establishment, Article 5(4) services, a planned or unplanned material change, uncertainty about complete documentation, or an EU/EEA AIFM direct-notification question.
Next steps
Create a passport register for each AIFM. It should list active and planned Member States, AIFs, service type, branch status, notification date, CSSF status, document versions, planned changes, and the internal decision maker for each file. Distribution and portfolio teams should check this register before using passport language in marketing, investor communications, or internal launch plans.
For inbound EU/EEA AIFMs, create a separate Luxembourg intake note. Record the Home State authority, the Luxembourg AIFs concerned, the source of the notification, and whether the ESMA Q&A 711 direct-notification point is relevant. Do not invent a CSSF approval date; record only the evidence actually received.
The register should also record negative decisions. If a country, AIF, branch feature, service, or investor route is reviewed and excluded, keep the reason, source checked, reviewer, and date. That prevents later teams from reviving an unsupported passport assumption because only approved routes were visible to future reviewers and distribution controls.
Official source
- CSSF, AIFM European passport, last update 22 April 2026.
- EUR-Lex, Directive 2011/61/EU on Alternative Investment Fund Managers.
- ESMA, Questions and answers area for supervisory clarifications.
- European Commission, investment funds policy area for the EU framework context.
Keep the source page, submission evidence, and internal approval note together so later reviewers can see why the firm treated the passport file as complete.
Source pack and related controls
A passport file should sit beside the wider AIFM control file, not outside it. Before relying on passport language, compare the CSSF passport page with the AIFMD text on EUR-Lex, the ESMA Q&A area, and the firm's own authorisation, risk-management, delegation, and distribution records. The decision may depend on current facts, host-country perimeter, the exact service route, and whether a branch or material change is involved.
Useful internal reading includes CSSF AIFM authorisation application file, CSSF AIFM risk management, leverage and liquidity, CSSF registered AIFM registration and amendments, CSSF UCI authorisation and fund launch approval, CSSF UCI reporting obligations calendar, and CSSF prospectus approval and passporting.
If the passport question affects live launch timing, investor communication, or cross-border activity, ask a qualified adviser or the competent authority route to confirm the perimeter before activity starts. This page is general regulatory information, not a substitute for legal advice on a specific AIFM, AIF, service, or host Member State.
For completeness, keep a deadline and fee note beside the notification file even when the CSSF page is the main source. Record planned launch date, eDesk submission date, completeness evidence, host-country communication, internal approval date, document owner, any fee or payment evidence, and fallback action if the transmission period, branch file, or material-change notice does not align with the business timetable. Exceptions should be documented explicitly rather than left as informal launch assumptions.