AIFMD Annex IV reporting — the practical guide (who, what, when, where per NCA)

Every AIFM that manages or markets an alternative fund in the EU or the UK owes its regulator a periodic transparency report under Article 24 of the AIFMD (Article 3 for sub-threshold "registered" managers) — the file the industry calls Annex IV, after the annex of the Level 2 Regulation that lists the data points. The vendor guides that rank for this search are selling you their filing engine. This page is the neutral how-to: how your reporting frequency is decided, what actually sits in the file, how each regulator wants it delivered, what trips up first-time filers, and the AIFMD II change landing in 2027. For the deadline dates across Luxembourg, Ireland, the UK, Jersey and Guernsey, this page's sibling holds the table — the 2026 regulatory calendar.

The reporting regime is EU-harmonised at the template level: the same ESMA XML schema, the same data points, the same AuM-driven frequency logic apply whether you file in Luxembourg, Dublin or (post-Brexit, onshored almost verbatim) London. What differs is the plumbing — the portal, the upload mechanics, the local validation layer. So most of this guide is domicile-neutral; the per-NCA table isolates what genuinely changes by regulator.

Who has to file

• Authorised (full-scope) AIFMs — the full Article 24 report at AIFM level plus one AIF-level report per fund managed or marketed.
• Registered (sub-threshold / "de minimis") AIFMs — managers below the AIFMD thresholds (€100m with leverage, or €500m unleveraged and closed for 5 years) still report under Article 3, but a lighter set of fields and, in the base case, only annually. ESMA Guidelines 2014/869
• Non-EU AIFMs marketing under a national private placement regime (NPPR) — report to each NCA in whose jurisdiction they market. (This guide covers the EU/UK NCAs; NPPR filers inherit the same template.)

Frequency decision tree — quarterly, half-yearly or annual

Frequency is not a choice; it's a function of your assets under management (AuM, measured on the AIFMD "regulatory" basis, which is not the same as NAV — derivatives are counted at their converted-to-underlying value) and whether the fund is leveraged. Work down this tree per manager, using total AuM across all AIFs; the AIF-level obligation follows the AIFM's frequency, with two carve-outs noted below. ESMA Guidelines 2014/869 · Alter Domus guide

Three things the tree hides that catch people out:

• Reference dates are the last business day of the period, not the calendar quarter-end. Your data snapshot date moves with the calendar each year — don't hard-code 30 June/31 December.
• The submission deadline is one month (30 days) after the reference date — so the Q4/annual report referenced on the last business day of December is due end of January. Fund-of-funds get a further ~15 days (a 44–45-day window) because they need their underlying funds' data first. ESMA Guidelines 2014/869
• Frequency can step up mid-life. If AuM crosses a threshold, you move to the higher frequency; ESMA's guidelines set transition rules for when the change takes effect. Review frequency at least annually against actual AuM — don't assume last year's cadence still holds.

Your first report after authorisation

New AIFMs consistently get this wrong. You do not wait a full year. You start reporting from the first day of the quarter after you have information to report, through to the end of your first reporting period, and file within 30 days of that period end. ESMA's own worked example: an AIFM with reportable information as of 16 February first reports the period 1 April–30 June. A manager authorised part-way through the year reports a stub period to the next natural period end. Matterhorn RS · ESMA Guidelines 2014/869

Nil returns are mandatory. A fund that has raised no capital or not deployed still files — you submit the report and flag, in the designated field, that there is no information to report. "We had nothing to say" is not a reason to skip a period; a missing return is a breach, a nil return is compliance. Alter Domus guide

What's actually in the report

Annex IV is two linked reports, both delivered in one ESMA-schema XML submission:

The AIF-level report is where the work is. Field groups, in plain terms:

• Identification — AIF name, LEI/ISIN, domicile, inception, base currency, AIF type (hedge, PE, real estate, fund of funds, other), and reporting-code type (24(1), 24(2), 24(4)).
• Investment strategy & breakdowns — predominant strategy, then the portfolio broken down by instrument type, geographical focus, and the currency of exposures.
• Principal exposures & concentration — the AIF's principal markets, the five main instruments traded, the value of the assets, and its principal exposures and most important concentrations of counterparties.
• Risk profile — market risk (net equity/interest-rate/FX deltas, DV01, CS01), counterparty risk, liquidity profile (portfolio and investor liquidity buckets, redemption terms, gates/side-pockets), operational and other risk, and the results of stress tests.
• Leverage — leverage calculated under both the gross method and the commitment method (report each; they are separate mandatory figures for a leveraged AIF), plus the sources of borrowing.

Matterhorn RS · ESMA Guidelines 2014/869 · schema: ESMA AIFMD reporting IT technical guidance (Rev 6)

The validation failures that bounce a filing

Rejections are almost never about the numbers — they're schema/format failures caught before a human ever looks. The recurring ones, per ESMA's technical guidance and vendor validation notes: ESMA IT technical guidance Rev 6 · Caelith technical guide

Validation runs in layers: the ESMA XSD schema check, then ESMA business-rule checks (cross-field consistency, percentages summing, conditional logic), then any NCA-specific rules layered on top by your regulator's portal. Passing the schema is necessary, not sufficient — a file can be well-formed XML and still fail a business rule.

Per-NCA filing mechanics

Same report, different letterbox. The portal, format and quirks by regulator:

Jersey and Guernsey funds are outside the AIFMD Annex IV regime itself, but a Channel Islands manager marketing into the EU/UK under NPPR files Annex IV to each host NCA where it markets — so a Jersey manager selling into Germany and the Netherlands files to BaFin and the AFM, each with its own portal and local validation quirks. The deadline dates for all five domiciles' own periodic obligations sit in the 2026 regulatory calendar.

First-time filer gotchas

• Regulatory AuM ≠ NAV. The AuM that sets your frequency is computed under the AIFMD method — derivatives converted to their underlying equivalent — so a modest-NAV fund running derivatives can sit in a higher bracket than its NAV suggests. Compute AuM the AIFMD way before you assume your frequency.
• Don't wait a year. See the first-report rule above — file the stub period within 30 days of your first period end, not twelve months on.
• File the nil return. No capital deployed is still a reporting period.
• Both leverage methods, every time. Gross and commitment are separate mandatory figures for a leveraged AIF; omitting one is a conditional-field rejection.
• Reference date drifts. Last business day, not calendar quarter-end — re-derive it each period.
• Validate before you submit. Run the file through the ESMA XSD and the business-rule set locally; the portal will reject on the same rules, but on the deadline, at the worst possible time.
• Confirm your assigned frequency with the NCA. Especially in Ireland, where the Bank advises the interval per firm — a self-assessed cadence that disagrees with your Portal profile is a problem waiting to surface.

The 2027 horizon — AIFMD II reshapes Annex IV

AIFMD II (Directive (EU) 2024/927) applies from 16 April 2026, but the enhanced Annex IV reporting applies from 16 April 2027 — the new template does not bite in 2026. What changes, once ESMA's Regulatory and Implementing Technical Standards (due to the Commission by 16 April 2027) are finalised: CSSF Circular 25/901 · EY Luxembourg · PwC Luxembourg

• Full portfolio coverage. Reporting moves from principal markets, instruments and top exposures to all markets, instruments, exposures and assets per AIF — materially more data per fund.
• Delegation transparency. New data points on delegation arrangements — what is delegated, the percentage of assets under delegation, contract dates, the delegate's regulatory status, and internal FTEs performing and overseeing portfolio and risk management, plus due-diligence outcomes.
• One EU-standard XML. A single ESMA-coordinated schema replaces today's national variations — the harmonisation the current regime never fully achieved.
• UCITS reporting arrives too. AIFMD II amends the UCITS Directive to add a new supervisory reporting obligation for UCITS ManCos, broadly mirroring the AIFMD logic, also from April 2027 — if you run both, budget for two reporting build-outs, not one.

Practical read: 2026 is business-as-usual on the current template; 2026–27 is a data-sourcing and systems project to capture the new fields (especially delegation and full-portfolio detail) before the April 2027 switch.