AIFMD II Annex IV XML: Complete Technical Guide

Table of Contents

If you manage an alternative investment fund in the European Union, Annex IV reporting is one of the most consequential regulatory obligations you face. It is also one of the most technically demanding. This guide covers everything you need to know — from the legal basis and filing deadlines to the XML schema structure, common validation pitfalls, and how modern tooling can eliminate manual effort entirely.

1. What Is Annex IV Reporting?

Annex IV is a standardised data template defined in Directive 2011/61/EU (the AIFM Directive). It requires Alternative Investment Fund Managers (AIFMs) to periodically report detailed information about each fund they manage to their home National Competent Authority (NCA) — for example, BaFin in Germany, the CSSF in Luxembourg, or the AMF in France.

The report covers a wide range of data points grouped into roughly 300 fields across several sections:

• Fund identification — legal name, LEI, domicile, inception date, AIF type
• Investment strategy & principal exposures — asset classes, geographical focus, NAV breakdown
• Leverage — gross and commitment method, borrowing embedded in financial structures
• Liquidity profile — investor redemption frequencies, portfolio liquidity buckets
• Risk measures — VaR, market risk, credit risk, counterparty exposures
• Stress test results — as required under AIFMD Article 15(3)(b)
• Investor concentration — beneficial ownership thresholds

The purpose is systemic risk monitoring. ESMA aggregates the data across all EU NCAs and publishes statistical reports on the AIF industry. NCAs also use it for firm-level supervision.

2. Who Must File?

Every authorised or registered AIFM in the EU must file Annex IV reports. This includes:

• Full-scope AIFMs authorised under Article 6 of AIFMD
• Sub-threshold AIFMs registered under Article 3(3) — with reduced reporting obligations
• Non-EU AIFMs marketing funds into the EU under National Private Placement Regimes (NPPRs)

Under AIFMD II (Directive 2024/927), the reporting scope is expanded. Key changes effective April 2026 include:

• More granular data on delegation arrangements and substance requirements
• Enhanced liquidity risk reporting, including liquidity management tool (LMT) usage
• Additional fields for loan-originating AIFs
• Expanded ESG and sustainability-related disclosures
• Revised XML schema (ESMA is expected to publish RTS/ITS updates)

3. Filing Deadlines

Reporting frequency depends on AuM thresholds:

AuM Threshold	Reporting Frequency	Deadline After Period End
< €100 M (sub-threshold)	Annual	Within 1 month (NCA-specific)
€100 M – €500 M	Semi-annual	30 working days
€500 M – €1 Bn	Semi-annual	30 working days
> €1 Bn	Quarterly	30 working days
Leveraged funds > €500 M	Quarterly	30 working days

Note: Some NCAs (e.g., BaFin) impose stricter deadlines or request additional data fields beyond the ESMA minimum. Always check your NCA's local guidance.

4. The XML Schema — ESMA XSD Rev 6

Annex IV reports must be submitted as XML files validated against ESMA's official XSD schema. The current production schema is AIFMD_DATAIF_V1.2.xsd, commonly referred to as "Rev 6".

4.1 Root Structure

<?xml version="1.0" encoding="UTF-8"?>
<AIFReportingInfo
  xmlns="urn:aifmd:aif:reporting"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  CreationDateAndTime="2025-06-30T14:30:00"
  Version="1.2"
  ReportingMemberState="DE">

  <AIFRecordInfo>
    <!-- One block per AIF -->
  </AIFRecordInfo>

</AIFReportingInfo>

Key attributes on the root element:

• Version — must be "1.2" for Rev 6
• ReportingMemberState — ISO 3166-1 alpha-2 code of the home NCA
• CreationDateAndTime — ISO 8601 timestamp of file generation

4.2 AIFRecordInfo Section

Each <AIFRecordInfo> block describes one AIF. It contains nested elements for:

• <AIFCompleteDescription> — the main payload with strategy, exposures, leverage, liquidity, risk
• <AIFIndividualInfo> — fund-level identifiers (ISIN, LEI, national code)
• <AIFPrincipalInfo> — principal markets, instruments, and investor breakdown

4.3 Enumerations and Code Lists

ESMA defines strict enumerations for many fields. Examples:

Field	Allowed Values
AIFType	HFND, PEQF, REST, FOFS, OTHR, NONE
PredominantAIFType	Same as above, qualified by sub-strategy codes
MarketIdentification	MIC codes (ISO 10383)
CurrencyCode	ISO 4217 three-letter codes
CountryCode	ISO 3166-1 alpha-2

Using an incorrect enumeration value is the single most common cause of schema validation failure.

5. Common Validation Errors

After years of working with Annex IV filings across multiple NCAs, these are the errors we see most frequently:

5.1 Namespace Mismatch

The root element must declare the correct namespace URI. A single typo — urn:aifmd:aif:Reporting instead of urn:aifmd:aif:reporting — will cause the entire file to fail validation.

5.2 Date Format Errors

All dates must be xs:date (YYYY-MM-DD) or xs:dateTime (YYYY-MM-DDThh:mm:ss). Excel-sourced dates like 30/06/2025 will be rejected.

5.3 Decimal Precision

Many numeric fields have maximum fractional digits defined in the XSD. For example, NAV values typically allow 2 decimal places. Submitting 1234567.891 instead of 1234567.89 triggers a facet violation.

5.4 Missing Conditional Fields

Certain elements are conditionally required. For instance, if LeverageAIF is set to true, then the <LeverageGrossMethod> and <LeverageCommitmentMethod> elements become mandatory. Omitting them produces a content model error.

5.5 Percentage Fields Not Summing to 100

Several sections require percentage breakdowns that must sum to exactly 100. Rounding errors (e.g., 33.33 + 33.33 + 33.34 = 100.00 ✓ but 33.33 + 33.33 + 33.33 = 99.99 ✗) are a constant source of rejection.

5.6 Incorrect AIF National Code Format

Each NCA expects a specific format for the AIFNationalCode. BaFin uses a numeric identifier; other NCAs may use alphanumeric codes with specific prefix patterns. Misformatting causes the portal to reject the upload even if the XML is schema-valid.

6. Validation Workflow Best Practices

A robust Annex IV validation workflow should include three layers:

1. Schema validation — validate the XML against the official XSD using a conformant parser (e.g., libxml2, xmllint, or Java's javax.xml.validation). This catches structural errors.
2. Business rule validation — check cross-field consistency (percentage sums, conditional requirements, leverage calculations). ESMA publishes supplementary validation rules alongside the XSD.
3. NCA-specific validation — apply any local rules your NCA enforces. BaFin's MVP-Portal, for instance, runs additional checks beyond the ESMA schema.

# Example: validate with xmllint
xmllint --noout --schema AIFMD_DATAIF_V1.2.xsd report.xml

# Expected output:
# report.xml validates

7. AIFMD II Changes to Annex IV

AIFMD II (Directive 2024/927) introduces material changes to the reporting template. While ESMA is still finalising the technical standards, the key changes are:

• Delegation reporting — new fields on the percentage of AuM managed by delegates, risk management delegation, and substance indicators
• Loan origination — dedicated section for funds that originate loans, including maturity profiles, default rates, and concentration limits
• Liquidity management tools — mandatory reporting on which LMTs are available and when they were activated
• Open-ended fund liquidity — enhanced bucketing of portfolio liquidity vs. redemption terms
• ESG data — SFDR classification, principal adverse impacts, taxonomy alignment percentage

Fund managers should expect a new XSD version (likely Rev 7 or v2.0) to be published in 2025, with a transition period aligned to the April 2026 enforcement date.

8. How Caelith Automates Annex IV

Caelith eliminates the complexity of Annex IV reporting through a purpose-built pipeline:

• Data ingestion — connect your portfolio management system, transfer agent, or upload CSV/Excel. Caelith maps your data to the ~300 Annex IV fields automatically.
• Pre-validation — before generating XML, every field is checked against schema constraints, enumeration lists, and cross-field business rules. Errors are flagged with plain-language explanations.
• XML generation — Caelith produces XSD-compliant XML validated against the official ESMA schema (Rev 6, v1.2). The output is ready for direct upload to BaFin's MVP-Portal, CSSF SOFiE, or any NCA portal.
• Audit trail — every generated report is hash-chained into Caelith's cryptographic audit trail. You have immutable proof of what was filed, when, and from what source data.
• AIFMD II ready — as ESMA publishes updated schemas, Caelith updates its templates. No manual XML surgery required.