AIFMD Regulatory Reporting · Knowledge Base

← Part of: AIFMD Annex IV Reporting — The Complete Guide

AIFM-specific reporting — Article 24(1)

The manager-level AIFMD Annex IV file (items 1–38): technical header, AIFM identification, the five principal markets and instruments, and total assets under management — each field with its verbatim template wording, ESMA sources, an example and practical guidance.

Last updated: 2026-07-01 · For fund managers, AIFM staff, depositaries & reporting teams

The AIFM file is filed once per manager and per reporting period. It identifies the manager, states the total assets under management across all AIFs it manages, and reports the five principal markets and instruments in which it trades on behalf of those AIFs. Many fields here are technical “header” data that also appear, in the same form, on every AIF file.

Header — file identification

Q1Reporting Member State

Theory

The EEA Member State whose NCA receives the file — the country where the AIFM is authorised or registered.

ESMA guidelines

ESMA treats the reporting Member State as the AIFM's home Member State (or, for non-EU managers, the Member State of reference / of marketing). It anchors the whole submission to one authority.

Example

A management company authorised by the CSSF reports LU; a French SGP reports FR.

Practical

Enter the ISO 3166 country code of your home NCA. It must match the jurisdiction under which you are authorised, not the fund domicile.

Sources

Template (Annex IV, Reg. 231/2013), item 1: “Reporting Member state”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element ReportingMemberState (attr) (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q2Version

Theory

Item 2. The version of the XML Schema Definition (XSD) used to generate the file — it is not a resubmission counter.

ESMA guidelines

XSD attribute Version (type VersionType), mandatory on the root AIFMReportingInfo element. It states which ESMA schema version the file conforms to. Corrections/updates are handled by the filing type (Q4: INIT/AMND), and full withdrawals by a separate cancellation record — never by this field.

Example

A file built against the ESMA v1.2 schema carries the version value defined by that schema (e.g. 1.2); the same value is used for the initial file and any amendment.

Practical

Populate with the schema version your reporting tool validates against. It is fixed by the XSD, not chosen per submission.

Sources

Template (Annex IV, Reg. 231/2013), item 2: “Version”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element Version (attr) (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q3Creation date and time of the file

Theory

Item 3. Timestamp marking when the XML file was generated.

ESMA guidelines

XSD attribute CreationDateAndTime (type xs:dateTime), mandatory. ISO 8601 extended format yyyy-mm-ddThh:mm:ss, and it must be expressed as Coordinated Universal Time (UTC).

Example

A file built on 12 April 2026 at 09:30 UTC carries 2026-04-12T09:30:00.

Practical

Populate automatically from your reporting tool in UTC; it reflects file creation, not the reporting period end.

Sources

Template (Annex IV, Reg. 231/2013), item 3: “Creation date and time of the file”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element CreationDateAndTime (attr) (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Header — reporting section

Q4Filing type

Theory

Item 4. Flag indicating whether the AIFM reporting is an initial filing for the period or an amendment to a reporting previously submitted.

ESMA guidelines

XSD element FilingType (type FilingTypeType). Only two values are admitted: INIT = initial reporting for the reporting period; AMND = amendment to a reporting previously submitted. A full withdrawal is done separately via a CancellationAIFMRecordInfo record carrying CancelledRecordFlag = C plus the national code, period type and year identifying the report to cancel.

Example

First submission for Q1 2026 = INIT; a corrected refile of that quarter = AMND; to remove a report entirely, send a cancellation record with flag C.

Practical

Use INIT once per period, AMND for any subsequent correction of that period, and the cancellation record only to withdraw a filing.

Sources

Template (Annex IV, Reg. 231/2013), item 4: “Filing type”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element FilingType (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q5AIFM content type

Theory

Item 5. Code indicating the contents/scope of the AIFM reporting.

ESMA guidelines

XSD element AIFMContentType. Admitted values: 1 = 24(1) reporting contents for all AIFs managed; 2 = 3(3)(d) reporting contents for all AIFs managed; 3 = 24(1) reporting contents for all AIFs marketed in the Member State.

Example

An authorised EU AIFM reporting all the funds it manages uses content type 1; a registered sub-threshold manager uses 2; a non-EU manager reporting funds marketed in the Member State uses 3.

Practical

Pick the code matching your regime and scope; it must be consistent with your AIFM reporting code (Q16).

Sources

Template (Annex IV, Reg. 231/2013), item 5: “AIFM content type”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMContentType (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q6Reporting period start date

Theory

First calendar day of the period the report covers.

ESMA guidelines

ESMA aligns the period to the AIFM's assigned frequency (Section V of the guidelines); it must be consistent with the period end and type.

Example

For a quarterly filer, Q1 2026 starts 2026-01-01.

Practical

Use the first day of the quarter, half-year or year being reported. It must align with your assigned frequency.

Sources

Template (Annex IV, Reg. 231/2013), item 6: “Reporting period start date”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element ReportingPeriodStartDate (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q7Reporting period end date

Theory

Last calendar day of the reporting period.

ESMA guidelines

Point-in-time fields (NAV, AuM, exposures) are measured as at this date; flow fields (returns, subscriptions) cover the whole period.

Example

Q1 2026 ends 2026-03-31; a full-year 2026 report ends 2026-12-31.

Practical

Enter the period end. All “as at reporting date” questions are measured here.

Sources

Template (Annex IV, Reg. 231/2013), item 7: “Reporting period end date”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element ReportingPeriodEndDate (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q8Reporting period type

Theory

Item 8. The code describing which period the file covers.

ESMA guidelines

XSD element ReportingPeriodType. Admitted codes: quarterly Q1–Q4; half-yearly H1, H2; yearly Y1; and, for a period spanning an obligation change, X1 (1st to 3rd quarter) and X2 (2nd to 4th quarter).

Example

A quarterly filer reports Q1 for the first quarter; an AIFM whose obligation changes mid-year may report a combined X1 or X2 period (see Appendix E).

Practical

Match the code to your frequency and any change code from Appendix E; it must be consistent with the start/end dates (Q6–Q7).

Sources

Template (Annex IV, Reg. 231/2013), item 8: “Reporting period type”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element ReportingPeriodType (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q9Reporting period year

Theory

The calendar year of the reporting period.

ESMA guidelines

A simple four-digit year used to key the submission.

Example

2026.

Practical

Enter the four-digit year.

Sources

Template (Annex IV, Reg. 231/2013), item 9: “Reporting period year”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element ReportingPeriodYear (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q10Change in AIFM reporting obligation frequency code

Theory

Notifies the NCA that the AIFM's reporting frequency has changed (for instance after crossing an AuM threshold).

ESMA guidelines

The code comes from Table 10 (Appendix E): YQ, YH, HQ, QY, QH, NQ…. It tells the NCA how the transition periods are split.

Example

An AIFM moving from yearly to quarterly reporting during Q1 reports code YQ and files Q1–Q2 together, then Q3 and Q4 separately.

Practical

Only populate when your frequency actually changes; pick the code from Appendix E. A change usually takes effect from the next period.

Sources

Template (Annex IV, Reg. 231/2013), item 10: “Change in AIFM reporting obligation frequency Code”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMReportingObligationChangeFrequencyCode (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q11Change in AIFM reporting obligation contents code

Theory

Notifies a change in the content/scope of the reporting obligation (e.g. a registered manager becoming authorised).

ESMA guidelines

The contents change codes are mapped in the AIFM status-change matrix (Appendix F), which pairs a before-status with an after-status and the code to report.

Example

A registered (3(3)(d)) AIFM becoming an authorised quarterly filer reports contents change code 6 (per Appendix F).

Practical

Complete only when the applicable dataset changes; read the code from Appendix F. Coordinate with the AIF-level changes.

Sources

Template (Annex IV, Reg. 231/2013), item 11: “Change in AIFM reporting obligation contents Code”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMReportingObligationChangeContentsCode (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q12Change in AIFM reporting obligation quarter

Theory

The quarter in which a notified change in obligation takes effect.

ESMA guidelines

Used with Q10/Q11 and Appendix E to determine exactly which periods are reported at the new frequency.

Example

If the change occurs in Q3, report quarter Q3; Appendix E then shows Q1–Q2 and Q3–Q4 groupings for an HY transition.

Practical

Populate together with Q10/Q11 to tell the NCA from which quarter the new frequency or content applies.

Sources

Template (Annex IV, Reg. 231/2013), item 12: “Change in AIFM reporting obligation Quarter”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMReportingObligationChangeQuarter (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q13Last reporting flag

Theory

Indicates that this is the final report the AIFM will submit (e.g. authorisation withdrawn or activity ceased).

ESMA guidelines

Section VIII of the guidelines covers cessation; the flag closes the AIFM's reporting series cleanly.

Example

An AIFM surrendering its licence sets the flag true on its final filing.

Practical

Set to true only on your genuinely final filing. Setting it in error can close your reporting profile with the NCA.

Sources

Template (Annex IV, Reg. 231/2013), item 13: “Last reporting flag”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element LastReportingFlag (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Assumptions applied

Q14–15Assumption descriptions

Where you have relied on assumptions, estimates or methodological choices to complete any question, you disclose them here so the NCA can interpret the figures correctly.

  • Q14 — Question number to which the assumption relates
  • Q15 — Free-text description of the assumption
ESMA guidelines

ESMA expects assumptions to be applied consistently across periods, and specifically requires an explanation whenever a “0” is reported for a risk measure (guideline ¶111).

Example

“Q139 — Net DV01 reported as 0 because the AIF holds no interest-rate-sensitive instruments”; or “Q33 — illiquid positions valued using latest available manager NAV as a proxy.”

Practical

Reference the specific question number and describe the assumption plainly (pricing proxies, FX basis, look-through limits, stress-test methodology). Keep it concise but auditable — regulators do read these.

Sources

Template (Annex IV, Reg. 231/2013): Q14 “Question Number” · Q15 “Assumption description”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element Assumptions (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

AIFM identification

Q16AIFM reporting code

Theory

Item 16. A code indicating the AIFM's reporting category/status — not an identifier. (The AIFM's identifier is the national code at Q18.)

ESMA guidelines

XSD element AIFMReportingCode; values from Annex II Table 8 (Appendix F): 1 Registered AIFM (Art. 3); 2 Authorised AIFM (opt-in); 3 Authorised, only unleveraged AIFs investing in non-listed companies/issuers to acquire control; 4 Authorised, half-yearly obligation; 5 Authorised, quarterly obligation; 6–9 Non-EU AIFM under the Private Placement Regime (annual / unleveraged-control / half-yearly / quarterly respectively).

Example

A €2bn authorised EU manager reports code 5 (quarterly obligation); a registered sub-threshold manager reports 1.

Practical

Select the status code matching your authorisation and frequency (Appendix F lists every case). Do not confuse it with the AIFM national code (Q18), which is your identifier.

Sources

Template (Annex IV, Reg. 231/2013), item 16: “AIFM reporting code”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMReportingCode (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q17AIFM jurisdiction

Theory

The jurisdiction (country) of the AIFM.

ESMA guidelines

Normally identical to the reporting Member State (Q1); differs only in specific cross-border set-ups.

Example

LU for a Luxembourg AIFM.

Practical

Enter the ISO country code of the AIFM's home state.

Sources

Template (Annex IV, Reg. 231/2013), item 17: “AIFM jurisdiction”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMJurisdiction (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q18AIFM national code

Theory

The national identification code of the AIFM as held by the NCA.

ESMA guidelines

The code NCAs of the home Member State use to identify the manager (guideline ¶53 for the analogous AIF code).

Example

The CSSF entity code registered for the management company.

Practical

Populate with the identifier the NCA issued. Use exactly the NCA format — do not invent one.

Sources

Template (Annex IV, Reg. 231/2013), item 18: “AIFM National Code”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMNationalCode (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q19AIFM name

Theory

Legal name of the Alternative Investment Fund Manager.

ESMA guidelines

ESMA requires the legal name, matching authorisation and LEI records.

Example

“Example Asset Management S.à r.l.” — not “Example AM”.

Practical

Enter the full registered legal name; avoid abbreviations.

Sources

Template (Annex IV, Reg. 231/2013), item 19: “AIFM Name”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMName (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q20AIFM EEA flag

Theory

Indicates whether the AIFM is established in the EEA.

ESMA guidelines

Distinguishes EU AIFMs from non-EU managers reporting under a national private placement regime (Article 42).

Example

An EU AIFM sets true; a US manager marketing under NPPR sets false.

Practical

Set true for an EEA AIFM, false for a non-EEA AIFM.

Sources

Template (Annex IV, Reg. 231/2013), item 20: “AIFM EEA Flag”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMEEAFlag (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q21AIFM no reporting flag

Theory

Signals that the AIFM has no data to report for the period while still confirming compliance.

ESMA guidelines

Lets a manager file a positive nil return rather than omitting the file; used with the content type (Q5).

Example

A newly authorised AIFM that managed no AIFs during its first quarter files a nil return with the flag true.

Practical

Set true only for a genuine nil return; portfolio-level fields are then left empty.

Sources

Template (Annex IV, Reg. 231/2013), item 21: “AIFM no reporting flag”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Schema: element AIFMNoReportingFlag (AIFMD_DATMAN_V1.2.xsd)
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

AIFM identifier codes

Q22AIFM LEI code

Theory

The Legal Entity Identifier of the AIFM — the primary global identifier used across EU reporting regimes.

ESMA guidelines

ESMA's definitions (Section II) reference the FSB Legal Entity Identifier; where an LEI is unavailable the Interim Entity Identifier (IEI) may be used.

Example

A 20-character LEI such as 222100XXXXXXXXXXXX10, kept in “issued” status.

Practical

Provide the 20-character ISO 17442 LEI and keep it renewed — a lapsed LEI is a common validation failure.

Sources

Template (Annex IV, Reg. 231/2013), item 22: “AIFM LEI Code”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q23AIFM BIC code

Theory

The Business Identifier Code (SWIFT/BIC) of the AIFM, where one exists.

ESMA guidelines

A secondary identifier, only where the entity has a BIC.

Example

An 8 or 11-character BIC such as EXAMLULLXXX.

Practical

Enter the BIC if the entity has one; otherwise leave blank — not mandatory for all managers.

Sources

Template (Annex IV, Reg. 231/2013), item 23: “AIFM BIC Code”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q24Old AIFM national identifier — Reporting Member State

Theory

Where an identifier has changed, the Member State element of the previous code, ensuring continuity of the time series.

ESMA guidelines

Guideline ¶54 (for AIFs) requires the former code to be reported at the first filing after a change and thereafter; the same logic applies to the AIFM.

Example

After a code migration, report the old code's Member State LU alongside the new code.

Practical

Complete only when your national identifier changed; give the Member State of the former code.

Sources

Template (Annex IV, Reg. 231/2013), item 24: “Old AIFM national identifier - Reporting Member State”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Q25Old AIFM national identifier — National code

Theory

The previous national code itself, so the NCA can link historic and current filings.

ESMA guidelines

Reported for continuity following a code change.

Example

The superseded CSSF code, quoted next to the current one.

Practical

Populate only in a transition period after an identifier change; otherwise leave blank.

Sources

Template (Annex IV, Reg. 231/2013), item 25: “Old AIFM national identifier - National code”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Five principal markets traded

Report the five markets in which the AIFM trades the largest volumes on behalf of all the AIFs it manages, ranked by aggregated value.

Q26–29Five principal markets (ranked)

For each of the five ranks, provide the market and its aggregated traded value:

  • Q26 — Ranking (1st to 5th)
  • Q27 — Code type of market (MIC, XXX OTC, NOT none, etc.)
  • Q28 — Market code (the actual MIC or applicable code)
  • Q29 — Aggregated value of the market
ESMA guidelines

ESMA asks for the markets where the manager trades the largest volumes across all AIFs, using ISO 10383 Market Identifier Codes; where there is no exchange, the special values XXX (OTC) and NOT (not applicable) are used.

Example

1st: XEUR (Eurex) €450m · 2nd: XPAR (Euronext Paris) €300m · 3rd: XXX (OTC) €120m.

Practical

Rank by aggregated value across all AIFs. Use MIC codes for exchanges and the special codes where no MIC applies. If fewer than five markets are used, complete only the ranks that exist and leave the rest blank.

Sources

Template (Annex IV, Reg. 231/2013): Q26 “Ranking” · Q27 “Code type of market” · Q28 “Market code” · Q29 “Aggregated value of the market”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Five principal instruments traded

Report the five sub-asset types in which the AIFM trades the largest volumes across all its AIFs.

Q30–32Five principal instruments (ranked)

For each of the five ranks:

  • Q30 — Ranking (1st to 5th)
  • Q31 — Sub-asset type code of the instrument
  • Q32 — Aggregated value of the sub-asset type
ESMA guidelines

The sub-asset type codes are those of the ESMA asset-type taxonomy (Appendix A) — the same codes used for AIF-level exposures at Q121–124.

Example

1st: SEC_LEQ_OTHR (listed equity) €500m · 2nd: DER_IRD_INTR (interest-rate derivatives) €220m.

Practical

Use the Appendix A sub-asset codes; rank by aggregated value; complete only as many ranks as apply.

Sources

Template (Annex IV, Reg. 231/2013): Q30 “Ranking” · Q31 “Sub-asset type code” · Q32 “Aggregated value of the sub-asset type”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
Guidance: derived from the template field definition under the article above (no field-specific ESMA/2014/869 paragraph)

Total assets under management

Report the total AuM of all AIFs managed, calculated in line with Articles 2 and 10 of the AIFMR (the leverage-inclusive method), in EUR and, if uniform, in the base currency.

Q33Total AuM amount in Euro

Theory

The manager's total AuM across all AIFs, expressed in EUR — the figure that determines thresholds and frequency.

ESMA guidelines

Guideline ¶51: calculate under Articles 2 and 10 AIFMR (leverage-inclusive), always report in EUR, use the ECB conversion rate, and measure as at the last business day of the period.

Example

Three AIFs of €400m, €350m and USD 300m (≈€275m) give a total AuM of about €1,025m — above €1bn, so quarterly reporting.

Practical

Convert to EUR at the ECB rate (Q36–38). This figure drives your frequency, so reconcile it to the sum of the AIF AuMs.

Sources

Template (Annex IV, Reg. 231/2013), item 33: “Total AuM Amount In Euro”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
ESMA guidelines: ESMA/2014/869 §51 (value of AuM, Articles 2 & 10 of Reg. 231/2013)

Q34Total AuM amount in base currency

Theory

The same total AuM in the AIFM's base currency, if a single base currency applies to all AIFs and it differs from EUR.

ESMA guidelines

Guideline ¶51: only report this when all AIFs share one base currency other than the Euro.

Example

If every AIF is USD-denominated, report the USD total here in addition to the EUR figure at Q33.

Practical

Complete only where all AIFs share one non-EUR base currency; otherwise leave blank and rely on the EUR figure.

Sources

Template (Annex IV, Reg. 231/2013), item 34: “Total AuM amount in base currency (if the same for all AIFs and different than Euro)”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
ESMA guidelines: ESMA/2014/869 §51 (value of AuM, Articles 2 & 10 of Reg. 231/2013)

Q35AIFM base currency

Theory

The single base currency, if the same for all AIFs.

ESMA guidelines

Reported only where a uniform base currency exists.

Example

USD where all AIFs are USD funds.

Practical

Enter the ISO 4217 code only when a uniform base currency applies.

Sources

Template (Annex IV, Reg. 231/2013), item 35: “AIFM Base currency (if the same for all AIFs)”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
ESMA guidelines: ESMA/2014/869 §51 (value of AuM, Articles 2 & 10 of Reg. 231/2013)

Q36Base currency / EUR FX reference rate type

Theory

Identifies the source of the exchange rate used to convert to EUR (typically the ECB reference rate).

ESMA guidelines

Guideline ¶51 mandates the ECB rate for EUR conversion; only where the ECB publishes none does the AIFM use and describe another rate.

Example

For USD, rate type ECB; for an exotic currency with no ECB rate, flag a non-ECB rate and describe it at Q38.

Practical

Select ECB where an ECB reference rate exists; otherwise indicate a non-ECB rate and describe it in Q38.

Sources

Template (Annex IV, Reg. 231/2013), item 36: “Base currency / EUR FX reference rate type”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
ESMA guidelines: ESMA/2014/869 §51 (value of AuM, Articles 2 & 10 of Reg. 231/2013)

Q37Base currency / EUR FX rate

Theory

The actual exchange rate applied to convert the base-currency AuM into EUR.

ESMA guidelines

Measured as at the last business day of the reporting period, consistent with the rate type.

Example

USD/EUR at period end, e.g. 1.0850.

Practical

Report the rate as at period end, consistent with Q36.

Sources

Template (Annex IV, Reg. 231/2013), item 37: “Base currency / EUR FX rate”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
ESMA guidelines: ESMA/2014/869 §51 (value of AuM, Articles 2 & 10 of Reg. 231/2013)

Q38Base currency / EUR FX reference rate description (non-ECB)

Theory

Describes the rate source when no ECB rate is available for the currency.

ESMA guidelines

Only where Q36 indicates a non-ECB rate; ESMA wants the source identified.

Example

“Bloomberg BFIX 16:00 CET fixing” for a currency with no ECB reference rate.

Practical

Complete only when Q36 is non-ECB; name the source and the timing convention.

Sources

Template (Annex IV, Reg. 231/2013), item 38: “Base currency / EUR FX reference rate description for no ECB rates”
Legal basis: Articles 24(1) and 3(3)(d) AIFMD; Annex IV, Commission Delegated Regulation (EU) No 231/2013
ESMA guidelines: ESMA/2014/869 §51 (value of AuM, Articles 2 & 10 of Reg. 231/2013)

Q&A Related ESMA questions & answers

Answers are based on the ESMA guidelines (ESMA/2014/869), Directive 2011/61/EU and Delegated Regulation (EU) No 231/2013; the applicable guideline paragraph (§) or article is cited inline in each answer.

How is total AuM converted into Euro if the AIFM manages funds in several currencies?

ESMA guideline ¶51 requires the total AuM to always be reported in Euro, converted at the European Central Bank reference rate as at the last business day of the reporting period. The base-currency figure (Q34) is only added when all AIFs share a single base currency other than the Euro. Where the ECB publishes no rate for a currency, the AIFM indicates the rate it used (Q38).

Should the five principal markets be the AIFM's or aggregated across all AIFs?

They are aggregated across all AIFs the AIFM manages, ranked by the largest traded volumes on behalf of those funds. The equivalent per-fund question is asked separately for each AIF at Q114–117.

Which value is used to rank markets and instruments — notional or market value?

The template asks for the aggregated value of trading in each market/instrument. Rank consistently on that basis across all five entries; if you must estimate, disclose the basis in the assumptions (Q14–15).

← Previous
Overview & frameworkNext →
AIF file — Art. 24(1)
FUND XP

Need support with your Annex IV filings?

FUND XP provides a dedicated AIFMD Annex IV reporting solution that produces your regulatory reports end to end: it maps your portfolio data to every field described here, runs the ESMA data-quality validations and generates the filing-ready XML for your National Competent Authority — for AIFMs and AIFs in Luxembourg and across the EEA.

Discover our Annex IV solution Contact us

This guide is provided for information purposes only and reflects the ESMA reporting guidelines (ESMA/2014/869), Commission Delegated Regulation (EU) No 231/2013 and the ESMA XSD schemas. It does not constitute legal or regulatory advice. Always confirm current requirements and technical formats with your National Competent Authority and the latest ESMA validation rules before filing.