AIFMD II Annex IV Reporting Changes: What Luxembourg Fund Managers Must Prepare Before April 2027

ByOfficer

AIFMD II Annex IV Reporting Changes: What Luxembourg Fund Managers Must Prepare Before April 2027

Last updated: May 2026

Luxembourg transposed Directive (EU) 2024/927 (AIFMD II) via the Law of 3 March 2026 (originating from Bill No. 8628), published in Memorial A on 9 March 2026. The substantive AIFM provisions apply from 16 April 2026. The law is live. But for AIFMD II Annex IV reporting, the real pressure point is still ahead: ESMA must deliver the final RTS and ITS defining the new Annex IV template by 16 April 2027, and first filings under the revised framework are expected shortly after. That gives Luxembourg AIFMs roughly one year from today to overhaul how they collect, structure, and submit Annex IV data.

The scope of what changes is not incremental. Article 24 has been rewritten. The current Annex IV template, whose core schema dates from 2014 and has been refreshed through Circular CSSF 23/844 (which repealed Circular 14/581) and ESMA’s AIFMD Reporting Technical Guidance revision 6 in November 2023, will be replaced by a harmonized EU-wide format covering delegation chains, loan origination portfolios, marketing footprints, and full instrument-level data. If your reporting team is still treating this as a “wait for ESMA” situation, you are already behind.

I have worked with the existing Annex IV XML schemas since the original CSSF Circular 14/581, and later through Circular CSSF 23/844. The gap between the current template and what AIFMD II demands is the largest structural shift the AIFM reporting framework has seen since its inception.

Related reading: AIFMD II Liquidity Management Tools: What Changes April 2026

Timeline: Three Dates That Matter

The transition runs across three fixed dates. Missing the sequence means missing the preparation window entirely.

16 April 2026: Member States must have transposed AIFMD II into national law. Luxembourg has done this via the Law of 3 March 2026. The substantive AIFM rules (delegation, loan origination, liquidity tools) are now in force.

H2 2026 (expected): ESMA is expected to launch its consultation on the RTS and ITS that will define the new Annex IV reporting template, XML schema, field definitions, reporting frequencies, and validation rules. This is the window where the detailed template design becomes visible.

16 April 2027: Deadline for ESMA to submit final RTS/ITS to the European Commission. First reporting under the new template and harmonized standards applies from this date. All EU AIFMs in scope must file under the revised framework.

The common mistake here is treating 2027 as a distant deadline. In practice, once ESMA publishes its consultation draft (expected H2 2026), teams will have at most six to eight months to map existing data fields to the new template, build or reconfigure XML generation, and test submissions. That timeline compresses fast, especially for firms running multiple AIFs across jurisdictions.

What Changes in the AIFMD II Annex IV Template

The revised Article 24 of the AIFMD replaces the current reporting scope with a substantially broader set of requirements. While the exact field-by-field template depends on the forthcoming ESMA RTS/ITS, the directive itself prescribes specific categories of data that must be reported. These are not optional or subject to national discretion.

From “Principal” to “All”: Expanded Instrument and Market Coverage

Under AIFMD I Article 24, AIFMs reported on the principal markets and instruments in which they trade on behalf of each AIF, with the Annex IV template using “main markets” and “main instruments” as the operative reporting fields. This allowed discretion in what got included. AIFMD II removes that ambiguity. The new text requires reporting on all markets, all instruments, all exposures, and all assets for each AIF.

This is where many teams will underestimate the effort. Moving from a curated subset to a full inventory means your data extraction must cover every position, not just the largest. Asset classification, ISIN tagging, and Market Identifier Codes (MICs) need to be accurate across the entire book. If your current feed only pulls top-20 positions by NAV weight, that workflow breaks.

Delegation and Sub-Delegation Disclosures

This is the most operationally disruptive change. Under the current template, delegation information was minimal and largely unstructured. AIFMD II introduces mandatory, structured fields covering:

Names, domiciles, and regulatory status of all delegates and sub-delegates.

Activities delegated (portfolio management, risk management, or both) and the percentage of AIF assets managed under delegation.

Number of FTEs performing portfolio and risk management internally.

Number of FTEs monitoring delegation arrangements.

Dates and outcomes of due diligence reviews on delegates.

Issues identified during oversight and remediation timelines.

This data does not sit in a single system. I have seen delegation arrangements where contract details live in legal files, FTE counts sit with HR, and due diligence dates are tracked in compliance spreadsheets. Getting this into a structured XML field set requires a data collection project, not just a template update.

The anti-letterbox provisions behind these fields reflect regulators’ concerns about AIFMs that delegate substantially all management activity while retaining only a minimal local presence. Expect the CSSF to pay close attention to how Luxembourg AIFMs populate these fields.

Marketing Footprint Reporting

AIFMD I did not require AIFMs to report where their funds were marketed. AIFMD II changes this. AIFMs must now disclose each EU Member State where an AIF’s units or shares are distributed, whether directly by the AIFM or through distributors.

For Luxembourg AIFMs managing cross-border funds, this means maintaining an accurate, current list of distribution jurisdictions per AIF per reporting period. If your distribution team updates marketing registrations without informing the reporting team, that gap will show up in the Annex IV filing.

Leverage Reporting Overhaul

AIFMD I already required AIFMs to set a maximum leverage level per AIF under Article 15(4) and to report leverage data under Articles 24(2) and 24(4). AIFMD II introduces a standardised EU definition of “leveraged AIF” and tightens AIF-level leverage reporting, in a methodology that will be specified by the ESMA RTS.

The calculation methodology will be defined in the ESMA RTS. But the directive itself makes clear that leverage figures must be AIF-specific, not aggregated. This requires sourcing all relevant market exposure values at the individual fund level.

Loan Origination Reporting

AIFMD II introduces a dedicated regulatory regime for loan-originating AIFs. These funds must include detailed loan portfolio information in their Article 24 filings: loan types, maturity profiles, borrower data, and portfolio quality metrics. This is an entirely new section in the reporting template with no AIFMD I equivalent.

If you manage or administer loan-originating AIFs in Luxembourg, the data architecture for this section needs to be built from scratch. The loan book data that funds currently report internally for risk or NAV purposes may not match the granularity or structure the new template requires.

Look-Through Requirements and Data Sourcing

The expanded scope to “all instruments, exposures, and assets” combined with delegation chain reporting effectively creates a look-through obligation, even if the directive does not use that exact term for Annex IV.

For fund-of-funds structures, this means reporting must capture the underlying positions, not just the name of the sub-fund. For delegation chains, the look-through extends to sub-delegates and their regulatory status. For marketing, it extends to distributors acting on behalf of the AIFM.

Teams that rely on third-party administrators for position data will need to verify that their data feeds deliver at the right granularity. A common error in the current regime is accepting aggregated position data from sub-funds without validating classification codes. Under the new rules, aggregated data without proper instrument-level breakdown will likely fail validation.

Harmonized Format: One EU Template, One XML Schema

Today, the Annex IV template is defined at the EU level by ESMA guidelines, but national regulators retain discretion over submission format and frequency. Luxembourg uses the CSSF’s eDesk/API (S3) channel. Other Member States have their own portals and formats.

AIFMD II directs ESMA to create a single harmonized reporting standard: one XML schema, one set of validation rules, and one set of reporting instructions across all EU Member States. NCAs will then transmit all Annex IV data to ESMA, which will maintain a central EU database.

For Luxembourg AIFMs already filing via the CSSF portal, the immediate question is whether the CSSF’s submission infrastructure will change. As of May 2026, the CSSF has not published specific guidance on the transition. Circular CSSF 23/844 remains the operative reference for current Annex IV filings. A new or updated circular reflecting the AIFMD II changes is expected once ESMA finalizes its RTS/ITS.

Reporting Frequency: Expect Tighter Deadlines

Under the current regime, reporting frequency depends on fund size and type: quarterly for larger funds, semi-annually or annually for smaller ones. The AIFMD II RTS will harmonize reporting frequency and timing across the EU.

The directive gives ESMA the mandate to set uniform deadlines and processes. While the exact frequencies are not yet published, the direction is toward more frequent reporting with tighter submission windows. AIFMs currently on annual or semi-annual cycles should prepare for the possibility of quarterly reporting.

One area where teams consistently get caught is the transition between reporting frequencies. When a fund crosses a size threshold and moves from annual to quarterly filing, the first filing under the new frequency must cover all prior periods within the reporting year. ESMA’s existing guidelines (ESMA/2014/869) set out detailed transition rules, and similar provisions are expected under the new framework. Getting the transition wrong creates filing gaps that NCAs flag during review.

What Luxembourg AIFMs Should Do Before the ESMA Consultation Lands

The ESMA consultation on the new template is expected in H2 2026. That consultation will reveal the field-by-field structure. But waiting for it before starting preparation is a mistake that several teams made during the original AIFMD I rollout, and it led to last-minute scrambles with XML vendors.

Here is what can and should be done now, based on what the directive already prescribes:

Map Your Delegation Data

Identify every delegate and sub-delegate across all managed AIFs. Collect names, domiciles, regulatory status, contract dates, and scope of delegation. Determine FTE counts for internal portfolio/risk management and for delegation oversight. If this information lives in multiple systems, consolidate it into a single source that your reporting tool can query.

Audit Your Position Data Feeds

Check whether your current data extraction covers all positions or only top exposures. Verify that every instrument has a valid ISIN (where applicable) and that market identifiers use MIC codes. Test whether your data provider can deliver full position-level data with the classification granularity the new rules will require.

Build a Marketing Jurisdiction Register

Create a per-AIF register of every EU Member State where units or shares are marketed, including the distribution channel (direct, distributor, platform). Assign ownership of this register to someone who is notified when marketing registrations change.

Prepare Loan Portfolio Data (If Applicable)

For loan-originating AIFs, assess what loan-level data your systems capture today versus what the directive prescribes. Map the gap. Loan type, maturity, borrower classification, and portfolio quality indicators will all need to feed into the Annex IV XML.

Engage Your XML Vendor Early

If you use a third-party tool for Annex IV XML generation (and most Luxembourg AIFMs do), contact your vendor now about their AIFMD II roadmap. Ask when they expect to release an updated schema and whether their data intake will support the new delegation and loan origination fields. Vendors that wait for the final ESMA template will leave their clients with minimal testing time.

CSSF Expectations and Luxembourg-Specific Considerations

The CSSF has historically been proactive on AIFMD reporting. Circular CSSF 23/844 replaced Circular CSSF 14/581 and tightened technical requirements, including mandating the API (S3) channel or eDesk for submissions from 1 July 2024. The CSSF is expected to issue updated guidance once the ESMA RTS/ITS are finalized.

Luxembourg-specific points to watch:

The Law of 3 March 2026 applies from 16 April 2026. It transposes the full scope of AIFMD II, including operational governance requirements that intersect with DORA obligations for fund administrators.

The CSSF FAQ AIFMD (Version 24, dated 20 May 2025) together with the AIFM Reporting Technical Guidance (Version 1.7, July 2024) require all text fields in Annex IV reporting to be completed in English. This is expected to continue under the new framework.

The CSSF requires reporting files to be submitted only via the API (S3) or eDesk channels. Manual submissions are no longer accepted. Any new ESMA-mandated transmission protocol will need to be implemented through these channels or their successors.

Luxembourg’s fund industry manages thousands of AIFs across regulated and non-regulated structures, and the CSSF processes a high volume of Annex IV filings. Validation rule changes under the new template will likely trigger a wave of rejection notices in the early filing periods. Teams should budget time for iterative resubmissions.

UCITS VI: A Parallel Reporting Track

AIFMD II also amends the UCITS Directive (via what is informally called UCITS VI) to introduce a new supervisory reporting obligation for UCITS management companies. This new UCITS reporting framework will closely mirror the AIFMD Annex IV structure: regular reporting on trading activity, exposures, liquidity management, risk profile, stress testing, delegation, and marketing footprint.

For Luxembourg management companies that manage both AIFs and UCITS, this creates a parallel reporting stream. The data architecture, XML generation, and validation workflows will be similar. Firms that build their AIFMD II reporting infrastructure with UCITS in mind will avoid duplicating effort when the UCITS reporting obligations take effect (also expected from April 2027).

Frequently Asked Questions

When do the new AIFMD II Annex IV reporting rules actually apply?

The directive was transposed into Luxembourg law by the Law of 3 March 2026, with the substantive AIFM provisions applying from 16 April 2026. However, the new Annex IV reporting obligations (revised template, new fields, harmonized XML) apply from 16 April 2027. ESMA must deliver the final RTS/ITS by that date. Until then, AIFMs continue filing under the current Annex IV template per CSSF Circular 23/844.

Do I need to report delegation data in my current Annex IV filings?

Not under the current template. The detailed delegation fields (delegate names, FTE counts, due diligence dates) are part of the revised Article 24 requirements and will only become reportable once the new ESMA template is in force. But you should be collecting this data now to avoid a rush when the template goes live.

What happens if ESMA delays the RTS/ITS beyond April 2027?

The directive sets 16 April 2027 as the deadline for ESMA to submit the standards to the Commission. If there is a delay, the Commission could extend the timeline or NCAs might issue interim guidance. However, the directive’s substantive requirements (expanded scope, delegation data, loan origination) are already in the transposed law. NCAs could technically require compliance with the directive’s provisions even before the harmonized template is published.

Will the CSSF filing portal change?

This is not yet confirmed. The CSSF currently uses the API (S3) channel and eDesk for Annex IV submissions. The move to a harmonized EU submission standard may require portal updates, but the CSSF has not published specific guidance on this yet. Expect an updated circular once the RTS/ITS are finalized.

Does AIFMD II affect registered (sub-threshold) AIFMs?

Registered AIFMs under Article 3 of the AIFMD have reduced reporting obligations (annual, limited scope). The revised framework maintains this distinction, but the exact scope for registered AIFMs under the new template will be defined in the ESMA RTS. Registered AIFMs should monitor the consultation closely.

How does this relate to the new UCITS reporting requirements?

AIFMD II also introduces supervisory reporting for UCITS management companies, mirroring the Annex IV logic. If you manage both AIFs and UCITS, plan your data and reporting infrastructure to handle both streams. The UCITS reporting obligations are also expected to apply from April 2027.

What is the biggest operational risk in this transition?

Data fragmentation. The new template pulls from HR systems (FTE counts), legal files (delegation contracts), compliance records (due diligence dates), portfolio systems (full position data), and distribution teams (marketing jurisdictions). Most AIFMs do not have a single system that holds all of this. The integration work is the bottleneck, not the XML generation.

Related Articles

Operational Readiness: Key Takeaways

  • AIFMD II Annex IV reporting obligations apply from 16 April 2027. The directive is transposed into Luxembourg law via the Law of 3 March 2026, with substantive AIFM provisions applying from 16 April 2026.
  • The current Annex IV template will be replaced by a harmonized EU-wide format defined in ESMA RTS/ITS, expected to be consulted on in H2 2026.
  • Reporting scope expands from “principal markets and instruments” to all markets, instruments, exposures, and assets per AIF.
  • Delegation reporting becomes structured and mandatory: delegate identities, FTE counts, due diligence records, and remediation timelines.
  • Loan-originating AIFs face a new dedicated reporting section with no AIFMD I precedent.
  • Marketing footprint disclosure (per-AIF, per-Member State) is a new requirement.
  • Data collection across HR, legal, compliance, and portfolio systems is the primary operational bottleneck. Start the integration work now, not when ESMA publishes the final template.
  • The CSSF is expected to issue updated guidance (likely a new or amended circular) once ESMA finalizes the technical standards.

Sources and References

  • Directive (EU) 2024/927 of the European Parliament and of the Council of 13 March 2024 amending Directives 2011/61/EU and 2009/65/EC (AIFMD II): EUR-Lex
  • ESMA Guidelines on reporting obligations under Articles 3(3)(d) and 24(1), (2) and (4) of the AIFMD (ESMA/2014/869): ESMA
  • CSSF Circular 23/844 – Reporting obligations for Alternative Investment Fund Managers: CSSF
  • Luxembourg Law of 3 March 2026 transposing Directive (EU) 2024/927 (originally Bill No. 8628), Memorial A, 9 March 2026: Chambre des Deputes
  • Directive 2011/61/EU (original AIFMD): EUR-Lex

Disclaimer: The information on RegReportingDesk.com is for educational and informational purposes only. It does not constitute legal, regulatory, tax, or compliance advice. Always consult your compliance officer, legal counsel, or the relevant supervisory authority for guidance specific to your institution.

Similar Posts