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 what replaces the template — AIFMD II on the EU side, and a separate UK framework that has now started to pull away from it. 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. That harmonisation now has a shelf life on the UK side: in July 2026 the FCA consulted on retiring the Annex IV data items altogether in favour of a domestic framework (below), so this is the last stretch in which "one file, three letterboxes" is a fair description of the job.

One structural point before the detail. Almost every operational rule below comes from one of three places, and knowing which one saves you an argument: Article 110 of the Level 2 Regulation (Commission Delegated Regulation 231/2013) sets frequency and deadline; ESMA's reporting guidelines (ESMA/2014/869) set procedure — first reports, frequency changes, structures, liquidations; your NCA's own guidance sets plumbing — portal, file names, sign-off, local validation. When a vendor tells you "the regulator requires X", the useful question is which of those three X lives in.

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 including leverage, or €500m unleveraged with no redemption rights exercisable for 5 years) still report under Article 3(3)(d), but a lighter set of fields and, in the base case, only annually. What that lighter set actually is is three limbs of one paragraph, and it is worth knowing precisely — it is the difference between a week's work and a quarter's. ESMA Guidelines 2014/869
• Non-EU AIFMs marketing under a national private placement regime (NPPR) — report to each NCA in whose jurisdiction they market, under Article 42. Only the AIFs marketed in that Member State go into that NCA's report. ESMA AIFMD Q&A, Section III Q1

Frequency decision tree — quarterly, half-yearly or annual

Frequency is not a choice; it's a function of 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. The bands sit in Article 110(3) of the Level 2 Regulation, and they are worded as four separate limbs — two that classify the manager and two that classify an individual fund. That structure is the part people miss: your AIFM-level and AIF-level reports can land on different frequencies. Commission Delegated Regulation (EU) No 231/2013, Art. 110(3) · UK assimilated text of Art. 110

Worth knowing before you build anything permanent around these bands: ESMA has now recommended replacing the whole AuM-driven frequency structure with a monthly base frequency, calibrated module by module rather than fund by fund. That is years away and the bands above are what you file on today — but it is the reason not to hard-wire "quarterly or half-yearly" into a new reporting system. The horizon section has the detail and the dates.

Reference dates run on the TARGET calendar: reporting periods end on the last business day of March, June, September and December. Quarterly filers report as of all four; half-yearly as of the last business day of June and December; annual as of the last business day of December. ESMA Guidelines 2014/869, §8

Four 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. And if that last business day is a bank holiday in your jurisdiction with no data available, use the previous business day's information but keep the TARGET date as the reporting date. The data moves; the label doesn't. Guidelines §9
• The submission deadline is "as soon as possible and not later than one month" after the reference date — so the Q4/annual report referenced on the last business day of December is due end of January. Where the AIF is a fund of funds the AIFM may extend that period by 15 days, because it needs its underlying funds' data first. Both sentences sit in Article 110(1), and — usefully for UK filers — they survive verbatim in the assimilated UK text. Art. 110(1)
• The fund-of-funds extension does not extend the manager's report — it duplicates it. The 15 days buy time on the fund file only. Where a manager runs both fund-of-funds and ordinary AIFs and takes the extension, the FCA sets out the sequence: at the one-month deadline you file the AIFM report and the AIF reports for everything that is not a fund of funds; then, before the extended date, you file the fund-of-funds AIF reports and an amended AIFM report updated to take account of the fund-of-funds figures now reported. Claiming the extension costs you a second manager-level filing — budget for it, and don't discover it in the last fortnight of the month. FCA Annex IV Q&A, Q5
• Your NCA can raise the frequency. Article 110 lets the competent authority require all or part of the information more often where it deems that necessary. The Regulation sets your floor, not a ceiling.
• Frequency can step up or down mid-life. If AuM crosses a threshold you change band — and when you first report on the new frequency covering several elapsed periods, you send one report, not one per period. The guidelines tabulate every possible transition (Tables 8–10); the worked cases are worth reading once before your first change rather than during it. Guidelines §17–32

The number the tree runs on — how AuM is calculated, monitored and breached

Every band above hangs off one figure, and the Regulation does not leave that figure to you. Four articles at the front of Regulation 231/2013 — a hundred articles before Article 110 — set out how the total value of assets under management is computed, how often, who watches it between computations, and what happens on the day it goes over. They are the difference between a reporting frequency you can defend and one you assumed, and almost no Annex IV guide mentions them. Regulation (EU) No 231/2013, Art. 2–5 · UK assimilated text

The gotcha is the interaction of the first row and the fourth, and it is a control gap rather than a rule. The three-month clock in Article 4 runs from the date the value exceeded the threshold, not from the date you calculated it and found out. Compute annually, monitor loosely, and you can meet Article 4 on a clock that started months before anyone in the firm knew there was one — and when it lands, three things land together: an authorisation application on a 30-day fuse, a reporting scope that jumps from the three Article 110(1) limbs to the full Article 24 field set, and a frequency change with its own transition rules. That sequencing is why Article 3 is the article a sub-threshold manager should implement first and the one it is most likely to have skipped.

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. ESMA's own worked example: an AIFM subject to half-yearly reporting that has information to report as from 15 February would start reporting information as from 1 April to 30 June. ESMA Guidelines 2014/869, §12

A registered AIFM that becomes authorised follows a second set of rules, and the quarter you get your licence in changes the answer: authorised in Q1, you don't report at the end of Q1 but at the end of Q2 covering Q1–Q2; authorised in Q2, you report at end-Q3 covering Q1–Q3; authorised in Q3, at end-Q4 covering Q1–Q4. Get authorised in Q4 and you report on your old (annual) frequency for that year — the new obligation waits. Guidelines §19–20

Ireland reduces all of that to one table, and it is the clearest statement of the stub rule any regulator publishes. The Central Bank's AIFMD Reporting Date Matrix covers authorised AIFMs, non-EU AIFMs under a private placement regime and registered AIFMs under Article 3(3)(d) alike, and works the answer by the quarter in which you were authorised, registered or notified. Read across your frequency; the pattern is the product, and it transfers to any year: CBI — AIFMD Reporting Date Matrix

Two things fall out of it that no summary of the guidelines gives you. First, the label describes the cadence you settle into, not the length of your first file — a half-yearly filer authorised in Q1 or Q3 has a first "half-yearly" report covering three months, and an annual filer authorised in Q1 has a first "annual" report covering nine. Second, Q4 is the long wait at every frequency, and at annual it is extreme: authorised in October, an annual filer's first report covers the whole of the next calendar year and is not due until the January after that — roughly fifteen months of nothing, then a full year's file. That is a gap in which a reporting process built at launch is forgotten, staff turn over, and the data for the early months is no longer where anyone left it. Build the file before the gap, not after it. The matrix also carries the fund-of-funds extension forward as a footnote: the 15 days apply to the first report too.

Nil returns are mandatory. Where there is a gap between authorisation and the start of activity, or between an AIF's creation and its first investments, you still file — indicating that no information is available using the designated field. "We had nothing to say" is not a reason to skip a period; a missing return is a breach, a nil return is compliance. The flag is a specific data point, and it is destructive: in the Irish implementation, data point 21 on the AIFM file ("AIFM no reporting flag") or data point 23 on the AIF file must be set to T and every field after it left empty — populate anything downstream and the file fails validation. Guidelines §11 · CBI Reporting Guidance for AIFMs

Structures — umbrellas, feeders and funds of funds

How you slice a structure into reports is a procedural rule, not a judgement call:

• Umbrella AIFs report per compartment. AIF-specific information is reported at the level of each sub-fund or compartment, not for the umbrella as a whole. (The FCA reinforces this from the other end: PRNs are issued at compartment/sub-fund level.)
• Feeder AIFs are reported individually — one report each, never aggregated with their siblings or with the master. Identify the master the feeder invests into, but do not look through it to its holdings. Investments made at feeder level (derivatives, say) are reported in full.
• Funds of funds don't look through either — you report the AIF's holdings in the underlying funds, not the underlying funds' portfolios. Which is precisely why the 15-day extension exists, and also why claiming it doesn't excuse you from having the underlying NAVs.
• But a master you market nowhere can still owe its own report. This is the scope trap, and it sits awkwardly next to the rule above: you don't look through the master, yet in one case you file on it. Where you are on quarterly reporting, an offshore master AIF that you manage but market in no member state is reported in its own right because its feeder is in scope. In the UK it is a Handbook rule — FUND 3.4.6AR obliges a full-scope UK AIFM subject to quarterly reporting to report AIF-level information for each non-UK AIF it manages that is not marketed in the UK, and the same applies to a non-UK AIFM marketing a feeder here; the master needs its own PRN, which the FCA assigns on request via [email protected]. Ireland runs the same logic through identifiers — the Central Bank issues the non-EU master its own C-code. The underlying basis is ESMA's Article 24(5) opinion on collecting information for systemic-risk monitoring (ESMA/2013/1340), so expect the question in any domicile. Note the trigger: it is quarterly status that switches this on, so a step up in frequency can silently add funds to your filing list. FUND 3.4.6AR · FCA Annex IV reporting guide, §30

ESMA Guidelines 2014/869, §33–36

Life events — the reports you owe when something ends

• The AIFM changes mid-period. The outgoing AIFM reports nothing at period end. The incoming AIFM files one report covering the whole period, using data handed over by the predecessor. Same rule where an AIFM is merged away. Build the data handover into the transfer, not after it. Guidelines §14
• An AIF is liquidated or merged. File the last report immediately after — and ESMA puts a hard edge on "immediately": not later than one month after the end of the quarter in which the AIF was liquidated or put into liquidation. The final report may be empty, turnover-only, or complete, depending on how much was unwound; where a liquidator takes over, the AIFM reports before handing across. ESMA Q&A, Section III Q7

What's actually in the report

Annex IV is two linked reports, delivered as ESMA-schema XML — and they are two separate files, which is why they can run on different frequencies:

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

• Identification — AIF name, LEI/ISIN, domicile, inception date, base currency, AIF type (hedge, PE, real estate, fund of funds, other), and reporting-code type (24(1), 24(2), 24(4)). "Inception date" has a defined meaning: the date of authorisation where the AIF is pre-authorised, otherwise the date it was established.
• Investment strategy & breakdowns — predominant strategy, then the portfolio broken down by instrument type, geographical focus, and the currency of exposures. Strategy percentages are of NAV and can be negative; the predominant type is the strategy with the highest absolute percentage, and where nothing exceeds 50% you use "multi-strategy hedge fund".
• 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 (BIC and LEI of the five biggest; name only, where a counterparty has neither).
• 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. Investor liquidity is allocated by the shortest period in which each investor may withdraw; illiquid assets with indeterminate future liquidity go conservatively into the longest bucket.
• 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.

ESMA AIFMD Q&A, Section III · ESMA Guidelines 2014/869 · schema: ESMA AIFMD reporting IT technical guidance

What a registered (sub-threshold) AIFM actually files — the same template, three limbs of it

"A lighter set of fields" is the phrase every guide uses, and almost none of them says which fields. The answer is readable off one article, and the drafting is the point: Article 110(1) of the Level 2 Regulation hooks the second subparagraph of Article 24(1) and point (d) of Article 3(3) in the same sentence, then lists three things. Those three limbs are the whole of the Article 3 content obligation:

• (a) the main instruments in which it is trading — including a break-down of financial instruments and other assets, and the AIF's investment strategies with their geographical and sectoral investment focus.
• (b) the markets of which it is a member or where it actively trades.
• (c) the diversification of the AIF's portfolio — "including, but not limited to, its principal exposures and most important concentrations."

What sits outside that is the more useful half of the answer, and it is a clean structural cut rather than a field-by-field judgement. Article 110(2) — which carries the special-arrangements percentage, any new liquidity arrangements, the risk-management systems, the current risk profile (market and liquidity), the main asset categories with their short and long market values, turnover and performance, and the stress-test results — opens "For each of the EU AIFs they manage and for each of the AIFs they market in the Union … in accordance with Article 24(2)". That is the authorised manager's paragraph, and a registered AIFM is not in it. Nor is it in the substantially-levered block: Article 110(5) attaches the Article 24(4) information to paragraph 2, so a manager outside paragraph 2 is outside the extra questions whatever its funds' gearing. Two practical consequences follow: Regulation (EU) No 231/2013, Art. 110(1), (2), (5) and (6)

• It is not a different form. Article 110(6) applies the Annex IV pro-forma template to paragraphs 1, 2 and 5 alike. A registered AIFM files the same template as everyone else with fewer fields populated — which is why the field-state discipline above matters just as much to it: leaving a field blank and being forbidden from populating it are still two different things. Article 5(3) says the same thing from the registration side — the Article 110(1) information is provided "in accordance with the pro-forma reporting template as set out in the Annex IV".
• It is still two files, not one. The guidelines' own decision diagram for a registered AIFM reads "Annual AIFM and AIF minimum reporting obligation (3(3)(d) contents)" — the manager report and a per-AIF report, both at that minimum content. Registration reduces the depth of each file, not the number of them. Guidelines, Annex I §3

The one-month submission tail and the fund-of-funds 15-day extension sit in that same paragraph 1, so they travel with the Article 3 filer too. And the gotcha is what happens when you cross the line in either direction: step down from authorised to registered and you report only the Article 3(3)(d) information, in one report, covering the full period since your last filing (Guidelines §22, Table 8 Case 10) — but step up by opting in to full authorisation and the scope jumps to the whole Article 24 field set while your frequency stays annual (§26–27). Scope and frequency are separate levers and they move independently. The sub-threshold manager that budgets for its first full return by counting filings has budgeted the wrong axis.

Which currency — the two files answer differently

A first-filer trap that costs a rejection rather than an argument: the manager report and the fund report are not denominated the same way, and neither is denominated in your reporting entity's home currency by default.

• The AIFM report is in euro, always. The value of assets under management for all AIFs managed is reported in EUR whatever the funds are denominated in, converted at the European Central Bank rate; where the ECB publishes no rate for a currency, you report the rate you used. The figure is struck as of the last business day of the reporting period — the same date discipline as everything else. Only where every AIF the manager runs shares one single non-euro base currency is that euro figure additionally complemented by the base-currency value. ESMA Guidelines 2014/869, §51
• The AIF report is in the fund's base currency. Monetary values in the fund-level file are denominated in that AIF's base currency — including the currency-exposure block, where long and short values are given at AIF level in base currency and any currency outside the template's list is identified by its code. Guidelines §106
• The FX-rate fields are conditional, and that is how they fail. The exchange-rate fields are mandatory only where the base currency is not euro. Where it is euro, the FCA's instruction on the UK equivalents (AIF002 Q24 and Q31) is to enter 1 or make no entry at all — populate them with anything else and you are back in the conditional-field failure described below. FCA Annex IV Q&A, Q36 & Q38

The Article 24(4) block — and the leverage test that switches it on

The extra Article 24(4) questions (296–301 in the consolidated template) are not for everyone: only AIFMs managing AIFs that employ leverage on a substantial basis answer them. That phrase has an arithmetic definition — exposure calculated under the commitment method exceeding three times NAV — and ESMA tightened how you test it: compare the average daily commitment-method exposure over the reporting period against the average daily NAV, not a point-in-time snapshot at period end. A fund that gears up mid-quarter and unwinds before the reference date can still be substantially leveraged for reporting purposes. UK filers should note this whole test is proposed for deletion — FRAME would drop both leverage metrics and the substantially-levered trigger with them — but it is live law until the FCA's final rules land, so keep testing it. Art. 111 · ESMA Q&A, Section III Q18 & Q31

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. It helps to know the template's three field states: mandatory (everyone reports it), optional (report it if you have it), and conditional (a flag elsewhere makes it required — answer the flag "yes" and the dependent fields become compulsory; answer "no" and they must be left empty). Most "inexplicable" rejections are a conditional pair out of step. ESMA Q&A, Section III Q21

The two codes in that second row are worth separating properly, because the gap between them is where first-time filers lose a return. They are not interchangeable and they do not share a scale. A full-scope AIFM with a quarterly obligation answers 5 for its registration status — but a leveraged EU AIF it manages answers 29, not 5, for that fund's own reporting code. A below-threshold non-UK AIFM marketing under a private placement regime happens to answer 1 in both, which is exactly why the two get conflated. And "authorised" is the wrong thing to sort on: a small authorised AIFM is authorised, but it answers 1 with the registered managers, not 2–5 with the full-scope ones. The FCA publishes the complete mapping — manager category to registration status to AIF reporting code to filing content — as reference tables, with worked examples. FCA, Important information for AIFMD Annex IV transparency reporters, Q1 and annex 2. The field identifiers above are the FCA's; the same two-field structure carries across the EU schema, which numbers the fields differently.

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.

That business-rule layer has a published rule book — and it is worth reading before your first file

The middle layer is not a black box, and this is the part vendor guides skip because knowing it is what you would otherwise pay them for. Each rule has a reference: CAF- codes govern the AIF file, CAM- codes the manager file, and NCAs publish the catalogue. The Central Bank of Ireland publishes it as a spreadsheet — 162 distinct AIF-level rules running CAF-002 to CAF-219, and 21 manager-level rules from CAM-002 to CAM-025, each with its error message, the field it attaches to and the exact control applied. BaFin publishes the same two catalogues as annexes to its § 35 KAGB guidance notice, dated 5 March 2015. The published copies therefore differ in vintage, and the date does real work here: a catalogue dated before revision 6 became applicable in November 2023 predates the CAF-201–219 family below. Check the date on the copy you are working from before you build a control against it. CBI — AIFMD reporting, list of CAF and CAM errors · BaFin — AIF error codes (Anlage 1) · BaFin — AIFM error codes (Anlage 2)

Two structural things to take from the catalogue before any individual rule. First, not every failure bounces the file. The rules are graded — content error, warning, notification, or ungraded — and on the CBI's list 153 of the 162 AIF rules are content errors while 8 are warnings; on the manager side 17 of 21 are content errors, 2 are notifications. A warning does not stop the filing, but it is a flag your regulator can see and you cannot, unless you run the rules yourself first. Second, and more usefully, the catalogue exposes a fourth field state the template documentation does not name. Alongside mandatory, optional and conditional there is forbidden — a field that must be absent, not blank-ish, not zero, not "N/A". A large share of the rules are exactly this shape, and it is why the instinct to fill everything in is the single most reliable way to fail:

The manager file has one arithmetic check worth knowing because it is graded as a notification rather than an error and so passes quietly: your total AuM in base currency must equal your total AuM in euro multiplied by the FX rate you reported (CAM-016). It will not stop the filing. It will still be wrong.

The practical use of all this is not to memorise codes — it is to run the catalogue against your file before the portal does. The rules are published, they are the same layer for everyone, and the deadline is the worst possible moment to meet CAF-201 for the first time.

And there is a fourth layer behind the portal that most filers never see: your NCA is a relay, not the destination. It validates, accepts, and then forwards to ESMA — which can refuse what your regulator took. The plumbing makes this explicit at both ends of the EU. Luxembourg returns up to three files against a single submission: an acknowledgement of receipt, then the CSSF's own feedback after it analyses the content, then a third — a distinct file type — carrying ESMA's refusal back to you after the CSSF had already accepted it. The Netherlands does the same thing through status: the AFM validates first and forwards second, so a report showing "Submitted" is not yet accepted, and an ESMA rejection lands as a new open obligation. The operational consequence is the same everywhere: "accepted by my regulator" is an interim state. Don't close the reporting period on it, and don't schedule the person who can fix the file to be on leave the week after the deadline. CSSF AIFM Reporting Technical Guidance

The production schema is revision 6 (XSD version 1.2), applicable since 22 November 2023 — the reference period for first reporting under it was Y1/H2/Q4/X2 2023. Revision 6 is the revision that tightened validation, making more fields mandatory or subject to stricter rules, so a file built against an older revision fails on fields that used to pass. This is the ESMA-wide baseline, not a national variant: national guidance points at the same revision (the CBI's mandated header names AIFMD_DATAIF_V1.2.xsd / AIFMD_DATMAN_V1.2.xsd). ESMA AIFMD reporting IT technical guidance (rev 6)

Correcting a return you have already filed

Every regime on this page lets you fix a filed return, and every one of them fails the same way if you treat the fix as a fresh submission. The mechanism is a filing type inside the file, not a button on the portal:

• INIT once, AMND for ever after. The first clean file for a given report type, period type, period year and manager code is INIT. Send a second INIT for that same combination and the whole report is refused — not merged, not duplicated, refused. Every resubmission for a period you have already filed must carry AMND. Luxembourg and the Netherlands both bounce this at their own error codes, which tells you it is a template-level rule and not a national quirk.
• An amendment resends the whole record. A correction is not a delta: where you correct a previously sent data record, the complete record goes again. Building a "changed fields only" export is building a rejection.
• Cancelling is a third thing, with its own flag. A cancellation is its own record type carrying a cancellation flag — and it only works against a report the regulator already holds: cancel something it has no record of and you get an error rather than a silent no-op. Practical order: amend to correct, cancel only to withdraw a filing that should never have existed. CSSF AIFM Reporting Technical Guidance · AFM portal manual
• There is a deadline on your corrections too. The UK is the one that puts a number on it: no separate resubmission request is needed for Annex IV (unlike other returns), but the FCA expects the amendment function used sparingly and expects amended data that is complete, accurate and final no later than one month after the reporting deadline — two months after the reference date. Treat that as the outer edge of the correction window rather than a second deadline you plan around. FCA Annex IV Q&A, Q31
• Ireland adds a lock. Once a return is signed off it cannot be amended until the Central Bank unlocks it — so the correction path in Dublin starts with a request, not an upload. Build in the turnaround.

Per-NCA filing mechanics

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

If you file under a private placement regime, add a letterbox per country

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, its own account-opening lead time and its own local validation. The template is Brussels'; the plumbing is not, and it moves independently. Three of the common destinations:

The pattern across all three is the same and it is the one that catches NPPR filers out: the account is the long pole, not the file. Portal registration, procedure authorisation and — in Germany — a second approval step are all prerequisites with lead times measured in weeks, and none of them can be started on deadline day. The deadline dates for all five domiciles' own periodic obligations sit in the 2026 regulatory calendar; the sub-threshold and NPPR routes are mapped in sub-threshold AIFM regimes by jurisdiction.

And your home regulator may want a copy — Jersey does, Guernsey doesn't

The two Channel Islands domiciles diverge on a point that costs almost nothing to comply with and is easy to miss entirely, because it is not in the Directive at all — it sits in the local code:

• Jersey — file it twice. A Jersey AIFM that files Annex IV with a UK or EEA regulator must send the JFSC a copy of that same reporting, on the same frequency it files it with the host state, to [email protected]. No filing fees are payable to the JFSC for it. Where the identical report goes to several EEA states and/or the UK, one copy to the JFSC is enough — but it must carry written confirmation of where the reporting was filed. Where a Jersey AIF has a non-Jersey AIFM, the copy is only required on the JFSC's request. The obligation's base is the Alternative Investment Funds Code of Practice; the FAQ is its operational statement. JFSC — AIFMD FAQs
• Guernsey — file it once. The GFSC is explicit that the detailed Article 42 reporting goes to the EEA member state's regulatory authority and not to the Commission. What the GFSC does want is the marketing notification — it must be told within 14 calendar days of marketing commencing. Notify the fact locally; report the detail to the host. GFSC — Guernsey's AIFMD regime

Jersey's own frame moved this year, and it moved in the same direction as everything else on this page. On 16 April 2026 the JFSC split its AIF Code of Practice in two: a new EU/EEA regime code transposing AIFMD II (Directive (EU) 2024/927) alongside the Level 1 and Level 2 texts, and the pre-existing code, which from that date applies only to the UK-focused regime. Both were published on 8 April 2026. That is a domicile reading the same divergence this page describes from the reporting end — one rulebook could no longer serve both letterboxes — and it is a fair warning that "Channel Islands manager, EU and UK" is now two compliance positions, not one. Jersey's private-placement route into the EU is itself unaffected. JFSC — AIF Code of Practice, EU/EEA regime · JFSC — AIF Code of Practice, UK regime

The event-based notification that already sits next to Annex IV

One duty is not Annex IV, is not periodic, and gets missed because it arrived through a different door and lands in a different letterbox. Since 16 April 2026 an AIFM managing an open-ended AIF has to tell its regulator each time it switches a liquidity management tool (LMT — the suspension, gate, notice-period, swing-pricing, redemption-fee and side-pocket levers a fund pulls when redemptions outrun what it can sell) on or off. It belongs on this page for two reasons: it is the event-based reporting the horizon section describes, arriving years ahead of the template that was meant to carry it; and the notification does not travel through your Annex IV channel. Consolidated AIFMD, Art. 16

• Pick two before anything happens. An AIFM managing an open-ended AIF selects at least two appropriate tools from Annex V points 2–8, and communicates the activation and deactivation policies for them to its regulator. The single exception is an AIF qualifying as a money market fund under Regulation (EU) 2017/1131, which may select one. (Art. 16(2b).) Ireland glosses which two: the AIF Rulebook has the fund ensure its AIFM considers, where appropriate, selecting at least one quantitative-based tool (redemption gate, extension of notice period, redemption in kind) and at least one anti-dilution tool (redemption fee, swing pricing, dual pricing, anti-dilution levy) — a steer on the composition of the pair, not just the count. It also requires the selected tools and the terms on which each is activated and deactivated to be disclosed in the fund's governing documents, so a selection that never reached the constitutional documents is not a selection. CBI AIF Rulebook (July 2026), Liquidity Management Tools
• Then the notification clock — and it runs in two directions depending on the tool. Suspension of subscriptions, repurchases and redemptions (Annex V point 1), and any of the points 2–8 tools activated or deactivated in a manner that is not in the ordinary course of business, are notified without delay — after the event. Side pockets (point 9) invert it: notification is due within a reasonable timeframe before activation or deactivation. (Art. 16(2d).) Read that paragraph before you need it — a side pocket decided and executed in the same board meeting has already missed its notification.
• Luxembourg gave it its own eDesk procedure — not the AIFM reporting one. The CSSF built a dedicated "Liquidity Management Tool" procedure in two modules: an LMT selection module live from 23 March 2026, through which the initial selection and its policies had to reach the CSSF by 16 April 2026, and an LMT activation module live from 16 April 2026 for the ongoing notifications. Same portal, different procedure — being a registered Annex IV sender does not give you this one. CSSF communication, 18 March 2026
• Ireland answers the same question with a daily return, not a portal procedure. The Central Bank had already been collecting daily subscription and redemption data from every Irish-resident non-money-market fund through the Daily Investment Funds Return (DIFR) since December 2024, and extended it to liquidity-management-tool usage in a second phase in August 2025 — the Bank's own description of the return is that it "replaces trigger-based liquidity reporting". So when the revised AIF Rulebook took effect on 5 May 2026, the general LMT notification came out of the Rulebook on the strength of that daily collection. What survives as a notification is the suspension — and read out of the Rulebook itself it is tighter than the summaries of it. The duty sits in the Liquidity Management Tools sub-section of each fund chapter (Chapter 1 for Retail Investor AIFs, Chapter 2 for QIAIFs, and the ELTIF chapter carry the same four paragraphs), under the heading Suspensions, and it applies only to open-ended funds and open-ended funds with limited liquidity. Paragraph 1 splits the trigger in two — suspension of subscription, repurchase and redemption is one notification, suspension of NAV calculation is a second — and each is due immediately upon activation or deactivation taking effect, so lifting a suspension is as notifiable as imposing one. Paragraph 2 adds an update at the expiry of 21 working days and at each subsequent 21-working-day period while it persists. Paragraph 3 is the one almost nobody carries in a control: where another member state's regulator uses its Article 46(2)(j) power to require your AIFM to activate or deactivate a suspension, the fund must inform the Central Bank immediately on becoming aware of the instruction — a notification triggered by someone else's regulator rather than by your own decision. Paragraph 4 then obliges you to keep the Bank informed as it develops. The gate and side-pocket rules alongside are mechanical: an activated redemption gate reduces that dealing day's requests rateably and carries them to each subsequent dealing day until satisfied, and a side pocket may use physical or accounting segregation where the governing documents provide for it and unitholders were told in advance. One carve-out is worth knowing because it stops a false positive: retaining redemption proceeds until the underlying fund pays out, where the prospectus provides for it, is expressly not the activation of a redemption gate. None of that touches the Level 1 duty — an Irish AIFM still owes the without-delay notification under Article 16(2d) as transposed by S.I. No. 181 of 2026 — but the operational answer to "where does it go" is a return you already file every dealing day, not a procedure built for the purpose. The DIFR is an Excel return filed T+2 off the NAV valuation, and the obligation sits with the fund's directors however the work is delegated. If you run funds in both domiciles, the same obligation leaves your shop through two entirely different pipes — and the Irish one is owned by whoever files the daily return, who is usually not whoever owns Annex IV. CBI — Daily Investment Funds Return · CBI AIF Rulebook · S.I. No. 181/2026
• It does not reach a UK AIFM by this route. The UK is not transposing AIFMD II. But the FCA is proposing its own event-based trigger for large hedge funds under FRAME — the same idea arriving by a different road, which is worth noting if you file in both places and are deciding where event-driven filings live in your controls.

The practical point for whoever owns the Annex IV process: an LMT activation is not something you report in next quarter's file, and what it needs in your calendar is a trigger, not a date. If your reporting controls are all keyed to period ends, this obligation has nowhere to sit. The substantive rule — which tools count toward the two, the Level 2 detail, and the transitional period for funds constituted before 16 April 2026 — is on the AIFMD II implementation tracker.

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.
• Your AIFM return and your AIF returns can be on different clocks. Article 110(3) classifies the manager and individual funds separately, and the CBI says so explicitly: "AIFMs may need to report their own data at a different frequency to the AIFs under their management." One calendar entry for "Annex IV" is not enough.
• The schedule the portal shows you is not your obligation. Both the Central Bank and the FCA put frequency determination on the manager, and the FCA goes further: where the schedule displayed in your account disagrees with the frequency you have determined, you file on your frequency and use the change-of-frequency code in the report to correct the schedule. A system that says "half-yearly" is not a defence for having filed half-yearly.
• Don't wait a year — except in the one case where you wait fifteen months. File the stub period one month after your first period end, not twelve months on, and note the Q4-authorisation quirk that keeps you on your old frequency. The mirror image is the trap: an annual filer authorised in Q4 has no report at all until January of the year after next, and then owes a full calendar year. The longest gap in the regime is the one where the process is most likely to have been forgotten.
• "Left blank" and "forbidden" are different, and one of them fails. A conditional flag answered "no" does not merely make its dependent fields optional — it makes them forbidden, so entering "0", "none" or "N/A" is a rejection. The closed-ended fund that fills in its redemption terms as "none" is the standard case.
• File the nil return, and file it empty. No capital deployed is still a reporting period; set the no-reporting flag and leave every subsequent field blank, or validation fails.
• Two files, two currencies. The manager report goes in euro at the ECB rate whatever your funds are denominated in; the fund report goes in that fund's base currency. And the FX-rate fields are conditional on the base currency not being euro — where it is euro, they take 1 or nothing.
• The fund-of-funds 15 days don't cover the manager report. Take the extension and you file the AIFM report twice: once at one month for everything else, then an amended one carrying the fund-of-funds figures. It is extra work, not less.
• A master you market nowhere may still need its own report — and its own identifier. Quarterly status pulls in offshore masters of in-scope feeders. The identifier for that master has to be requested from the regulator; nobody issues it because you filed.
• Never send a second INIT. Once a period has been accepted, every further file for it is an amendment, carrying the whole record again. A "resubmit the fixed file" reflex is a rejection.
• Get registered as a sender before you have a file to send. In Luxembourg the link between the submitting entity and the manager has to exist in the regulator's register first — and if an administrator files for you, that has to be declared. In the UK nothing is available until the fund and firm identifiers are issued. Neither is a same-week job.
• Both leverage methods, every time. Gross and commitment are separate mandatory figures for a leveraged AIF; omitting one is a conditional-field rejection. And test "substantial" leverage on average daily figures, not the period-end snapshot. (The UK proposes to stop asking for either figure — but not yet, and not for your next return.)
• Reference date drifts. Last business day, not calendar quarter-end — re-derive it each period, and keep the TARGET date on the file even if you had to use the previous day's data.
• Tell the regulator about the fund before you report on it — and allow for the step you don't control. New AIF, new compartment, changed manager–fund relationship: notify first. Portals that cross-check their own register will simply refuse the return. Worse, the business rules check your codes against ESMA's register of authorised entities, which your NCA populates by notification — so the return can fail on an entity your own regulator has already authorised, for a step neither you nor it takes on your timetable. You find out on deadline day.
• Check whether your home regulator wants a copy. Filing to the host NCA can be only half the job: a Jersey AIFM owes the JFSC the same report on the same frequency, while a Guernsey one owes the GFSC only a marketing notification. Nothing in the Directive tells you this — it is in the local code, so establish it before your first period end rather than after.
• Uploading is not filing. Every portal we have looked at needs a second, explicit step — sign-off in Dublin, the reporting schedule in London, a separate Submit click in Amsterdam. A file sitting validated-but-unsubmitted is a missed return.
• "Completed" is not permanent. ESMA runs a Data Quality Engagement Framework — periodic re-examination of filings already marked complete. A return that passed can be reopened as a re-report months later (the AFM portal flags these with a DQEF marker on the sequence number). Keep the source data and the exact file you filed, not just the confirmation.
• Not every reporting duty is periodic any more. If you run an open-ended AIF, an LMT activation or deactivation is notifiable in its own right — without delay for suspension and out-of-the-ordinary tool use, and in advance for a side pocket. It goes through a different procedure from your Annex IV file, so a process built entirely around period ends has nowhere to put it.
• 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.

The horizon — AIFMD II reshapes Annex IV, and ESMA has now sketched the replacement

AIFMD II (Directive (EU) 2024/927) has applied since 16 April 2026 — but its transposition article carves out the supervisory-reporting overhaul: the measures transposing Article 1(12), which rewrites AIFMD Article 24, apply only from 16 April 2027 (alongside Article 2(7), which inserts the new UCITS Article 20a). The current template does not change in 2026. What changes after that: Directive (EU) 2024/927 · CSSF Circular 25/901 · EY Luxembourg

That carve-out is not a Brussels abstraction you have to take on trust — two of the domiciles on this page have already written it into national law at article level, and if you want to know what applies to you on 17 April 2027 those are the texts to read rather than the Directive. Ireland's transposition, S.I. No. 181 of 2026, came into operation on 1 May 2026 — two weeks after the EU deadline — with its reporting provision, Regulation 14, held back to 16 April 2027. Luxembourg's Law of 3 March 2026 did the same thing through its Article 57, deferring two reporting articles while the rest took effect on 16 April 2026. Same split, same date, two different statutory hooks — which matters if you are citing an authority to your own committee. S.I. 181/2026 · Legilux, Mémorial A 115

The detail below is read off the Level 1 text itself — Article 1(12) of the amending Directive, which replaces Article 24(1), swaps out points (c) and (d) of Article 24(2) and adds a new point (f). Points (a) and (b) — illiquid-asset special arrangements and new liquidity-management arrangements — are untouched. Worth reading in the original rather than in summary, because the delegation block is considerably longer than the coverage of it suggests.

• Full portfolio coverage — the word "principal" comes out. Amended Article 24(1) has the AIFM report, for each AIF, on "the instruments in which it is trading, on markets of which it is a member or where it actively trades, and on the exposures and assets of each AIF" — with no qualifier narrowing that to the principal ones or the top five. And the data has to carry "the identifiers that are necessary to connect" it to other supervisory or publicly available data sources, which makes identifier coverage a reporting requirement rather than a nice-to-have.
• Delegation transparency — eight sub-points, not one field. New Article 24(2)(d) enumerates what you file: (i) each delegate's name, domicile, close links, whether it is an authorised or regulated entity for asset-management purposes, its supervisory authority and its identifiers; (ii) the FTEs you employ performing day-to-day portfolio or risk management; (iii) a list and description of the delegated activities; (iv) where portfolio management is delegated, the amount and percentage of the AIF's assets under that delegation; (v) the FTEs you employ to monitor the delegation; (vi) the number and dates of your periodic due-diligence reviews, a list of the issues they identified, and where relevant the measures adopted and the date by which those measures are to be implemented; (vii) the same treatment for sub-delegates; (viii) commencement and expiry dates of every delegation and sub-delegation. Point (vi) is the one to sit with: your own oversight findings and your own remediation dates become a supervisory return.
• Where the fund is actually marketed. Wholly new point (f): "the list of Member States in which the units or shares of the AIF are actually marketed by the AIFM or by a distributor which is acting on behalf of that AIFM." Note both halves. Actually marketed is not the same set as the states you hold an Article 32 notification for — and the distributor limb means the answer partly lives with third parties. If your distribution agreements do not oblige anyone to tell you where units were placed, that is a contract change, not a reporting change.
• Leverage folds into the risk-profile point. Amended 24(2)(c) states the current risk profile as including market, liquidity, counterparty and other risks "including operational risk, and the total amount of leverage employed by the AIF" — leverage sits inside the risk block rather than beside it. (The separate Article 110 frequency test and the Article 111 substantially- levered trigger are Level 2 and are not touched by this article.)
• One EU-standard XML. A single ESMA-coordinated schema replaces today's national variations — the harmonisation the current regime never fully achieved. The hook is new Article 24(5b), which mandates implementing standards on "the format and data standards" for the reports, on the connecting identifiers, and on the methods and arrangements for submitting them. ESMA has since set the format direction as ISO 20022 (below).
• UCITS reporting arrives too — near-identically worded. AIFMD II inserts Article 20a into the UCITS Directive, and it is the AIFMD article with the nouns changed: the same full-portfolio limb, the same eight-point delegation block, the same actually-marketed list. One difference matters if you run both. The UCITS file carries, at Article 20a(2)(a), "the arrangements for managing the liquidity of the UCITS, including the current selection of liquidity management tools, and any activation or deactivation thereof" — so on the UCITS side the LMT information the AIF world notifies event-by-event under Article 16(2d) sits inside the periodic report. Same clock, 16 April 2027: budget for two build-outs, not one.

Two things in the same article are worth acting on now rather than waiting for the standards. First, the delegation list is a ceiling, not a starting point: Article 24(5a) tells ESMA to specify the "appropriate level of standardisation" of the point (d) information and then expressly forbids it from introducing reporting obligations in addition to those set out in point (d). The eight sub-points above are therefore the whole of the delegation ask, whatever the RTS says about format — which means the data-sourcing work can start today against Level 1, without waiting to see the template. Second, there is a new escalation route: amended Article 24(5) lets ESMA, after consulting the ESRB, ask NCAs to impose additional reporting requirements in exceptional circumstances where needed for the stability and integrity of the financial system — a Union-level version of the local "your NCA can ask for more" power under Article 110.

What the replacement template actually looks like — and when it arrives

Until May 2026 the shape of the post-AIFMD II file was guesswork. It no longer is. ESMA owed the Commission a report on an integrated reporting system for funds by 16 April 2026 under Article 69a of AIFMD and Article 20b of the UCITS Directive, and delivered it on 4 May 2026. It is the closest thing to a blueprint for what replaces Annex IV, and four things in it change how you should plan. ESMA Final Report on the integrated collection of funds' data (ESMA12-2121844265-5150, 4 May 2026)

The timing trap — and it is bigger than most coverage suggests. The obligation date and the template date are not the same thing, and they are now years apart. The amended Article 24 applies from 16 April 2027. But ESMA is only mandated to deliver draft RTS/ITS by that same date; the Commission then has to adopt them, and industry then needs an implementation period. ESMA's own arithmetic, stated plainly in the final report: a consultation paper on the standards later in 2026, IT-system development starting in 2027 subject to funding, and go-live of the new reporting expected in H1 2029 at the earliest — with the wider integration of MMFR and ECB statistical reporting (Phase 2) following "a few additional years" after that. Crucially, ESMA also states that existing templates and instructions remain in force and continue to be applied until superseded. So there is an interim in which the amended Article 24 is law and you are still filing something very like today's file.

Read this before you buy anything. Any roadmap selling you a firm 2027 switch-on for a new Annex IV template is selling a forecast that ESMA's own report does not support. 2026 and 2027 are business-as-usual on the current template. The real work in that window is data sourcing, not filing: delegation detail down to your own due-diligence findings and remediation dates, full-portfolio granularity with connecting identifiers, and the list of Member States where units were actually placed by your distributors are three field families that are almost certainly not in your reporting warehouse today. All three take longer to source than to file, and the third may take a contract amendment before it can be sourced at all. The AIFMD II timeline as a whole is tracked on the AIFMD II implementation tracker.

The UK's own track — FRAME retires AIF001 and AIF002

The UK is not transposing AIFMD II, and on 14 July 2026 it stopped waiting for it. HM Treasury published a draft statutory instrument rewriting the legal frame of the UK AIFM regime, and the FCA published three consultations alongside it — CP26/28 on the regime itself and CP26/26 "Fund Reporting for Asset Management Entities" (FRAME) on what replaces the reporting. FRAME is the one that matters here: it removes AIF001 outright and replaces AIF002, and it takes the UK off the Annex IV template that this page describes. Consultation closes 22 September 2026 for FRAME and 14 October 2026 for CP26/28 and the Treasury's draft regulations. FCA CP26/26 (FRAME) · CP26/26 full text (PDF) · FCA CP26/28

These are proposals, not rules — but the design choices are specific enough to plan against, and several of them invert the logic the rest of this page runs on:

FSA042 and the DISC 3.5.1R product-summary filing are proposed for decommissioning in the same package (§7.2–7.4), and closed-ended investment companies that are AIFs drop to annual reporting (§7.8). Timing: prototype forms by the end of 2026, a policy statement with final rules in H1 2027, and the complete regime in 2028 — with the FCA explicitly considering an iterative route that brings essential reporting for sub-£500m funds in before the end of 2027 (§8.13).

What this means if you file in both places. The two regimes are now diverging on the two things a reporting build depends on — the unit that sets your obligation and the format it arrives in. The EU is heading for a modular ISO 20022 file on a monthly base frequency, sized by fund characteristics, not before H1 2029. The UK is heading for a domestic form sized by fund NAV, on lags of 30 to 120 days, from 2027–28. Anything you build in that window should treat "which regulator" as a first-class dimension rather than a filing address — and neither destination is final rules yet. In the meantime nothing has actually changed: you file Annex IV, on Article 110 frequencies, into RegData, exactly as before.

The gotcha: the expensive Annex IV failures are almost never analytical. They are a fund the regulator doesn't know you manage, a nil return with one stray populated field, a validated file nobody signed off, or a frequency you assessed once at launch and never revisited. Every one of those is caught by a checklist a week before the deadline — and none of them is caught by the portal until the day itself.