How to File Annex IV with BaFin
A practical, step-by-step guide to submitting AIFMD II Annex IV reports to BaFin in 2026. Covers the MVP Portal SOAP integration, XML schema validation, BaFin-specific quirks, and the new AIFMD II reporting fields that take effect this year.
Quick Facts
- Regulator
- BaFin (Bundesanstalt fur Finanzdienstleistungsaufsicht)
- Filing Portal
- MVP Portal (portal.mvp.bafin.de)
- Filing Format
- XML (ESMA AIFMD_DATAIF_V1.2.xsd schema)
- Submission Method
- SOAP / WS-Security via MVP Portal API
- Deadline
- 30 calendar days after reporting period end (Art. 24 AIFMD II)
- Frequency
- Annual for sub-EUR 1B AUM, semi-annual for EUR 1B+
Prerequisites
Before you can submit an Annex IV filing to BaFin, ensure you have the following in place:
- 1.BaFin MVP Portal credentials — Entity ID, username, and password issued by BaFin. Apply via the BaFin registration portal — approval typically takes 2-4 weeks.
- 2.LEI (Legal Entity Identifier) — Must be active and current (renewed annually). Check status at gleif.org. A lapsed LEI is the most common cause of filing rejection.
- 3.WM-Datenservice fund classification codes — Required for all German-domiciled funds. Obtain from WM Datenservice GmbH. These are distinct from ISIN and WKN codes.
- 4.Valid XML signing certificate — WS-Security UsernameToken credentials for SOAP envelope signing. BaFin does not require X.509 certificate-based signing for Annex IV, but your SOAP client must correctly implement password digest generation.
Step-by-Step Filing Process
Gather fund data
Collect the data points required by the ESMA Annex IV schema: net asset value (NAV) in the fund's base currency and EUR equivalent, gross and net asset values, leverage ratios (both gross and commitment methods), investor concentration breakdown by type (professional, retail, fund-of-funds) and geography, counterparty exposure, geographic and sector allocation of investments, and liquidity profile across defined time buckets. For German-domiciled funds, also prepare WM-Datenservice classification codes and BaFin internal fund IDs.
Map data to ESMA Annex IV XML schema fields
Transform your raw fund data into the XML structure defined by AIFMD_DATAIF_V1.2.xsd. Key mapping areas include: AIFMIdentifier (your LEI), AIFNationalCode (BaFin fund ID), ShareClassIdentifier (ISIN per share class), AIFBaseCurrencyDescription, and the nested reporting sections for risk, leverage, portfolio, and investor data. Pay close attention to ESMA enumeration values — e.g., geographic codes must use the ESMA-defined ISO 3166 subset, not free text. Leverage must be expressed as a percentage of NAV (e.g., 150% = 1.5).
Validate XML against AIFMD_DATAIF_V1.2.xsd
Run your generated XML through XSD validation using the official ESMA schema file (AIFMD_DATAIF_V1.2.xsd). This catches structural errors: missing required elements, incorrect data types, invalid enumeration values, and nesting issues. BaFin additionally enforces business rules beyond XSD — for example, NAV consistency checks across sections, leverage ratio plausibility bounds, and mandatory WM-Datenservice code presence. Use BaFin's XML-Prueftool if available, or validate against both the ESMA XSD and BaFin's supplementary rules.
Sign XML with WS-Security credentials
BaFin's MVP Portal API requires SOAP messages secured with WS-Security (WSS). This means constructing a SOAP envelope with a WS-Security header containing your BaFin portal credentials (entity ID, username, password). The credentials are embedded as a UsernameToken with password digest. Ensure your SOAP client correctly generates the nonce, timestamp, and password digest according to the OASIS WSS UsernameToken Profile 1.0 specification. Incorrect WS-Security headers result in HTTP 401 or SOAP fault responses.
Submit via SOAP to MVP Portal endpoint
Send the signed SOAP envelope to BaFin's MVP Portal SOAP endpoint. The endpoint URL follows the pattern https://portal.mvp.bafin.de/services/AnnexIVSubmission. Use HTTP POST with Content-Type: text/xml; charset=utf-8. The SOAP action header must match the operation defined in BaFin's WSDL. On success, the portal returns a SOAP response containing a filing reference number (Eingangsnummer) and timestamp. On failure, you receive a SOAP fault with error details in German.
Monitor for acknowledgment or rejection feedback
After submission, poll the MVP Portal status endpoint or check for email notifications from BaFin. Acknowledgment typically arrives within 24-48 hours. The response includes one of three statuses: accepted (Angenommen), accepted with warnings (Angenommen mit Hinweisen), or rejected (Abgelehnt). Accepted-with-warnings filings are valid but may require follow-up corrections. Save the filing reference number and acknowledgment for your compliance records — you will need these for audit purposes.
Address validation errors and resubmit if needed
If BaFin rejects the filing, parse the SOAP fault response for error codes. Common issues include: INVALID_LEI (LEI not found in GLEIF database or lapsed), MISSING_FIELD (required data point omitted), INVALID_ENUM (enumeration value not in allowed set), PERIOD_MISMATCH (reporting period dates don't match expected filing window), and NAV_INCONSISTENCY (NAV figures don't reconcile across sections). Fix each error in your source data or mapping logic, regenerate the XML, revalidate, and resubmit. There is no limit on resubmission attempts.
Common Pitfalls
Leverage calculation errors: commitment vs. gross method
The Annex IV schema requires leverage reported under both the gross method and the commitment method. The gross method includes all positions at absolute market value without netting. The commitment method allows netting of hedging arrangements and excludes certain cash equivalents. A common error is applying commitment-method netting rules to the gross calculation, or vice versa. BaFin cross-checks both figures for plausibility — if your gross leverage is lower than commitment leverage, the filing will be flagged.
Missing or lapsed LEI
BaFin strictly requires a valid, active LEI (Legal Entity Identifier) for the AIFM entity and every reported AIF. LEIs must be renewed annually with the issuing Local Operating Unit (LOU). If your LEI has lapsed — even by one day — BaFin's validation will reject the filing. Check LEI status at gleif.org before every submission. This is the single most common cause of first-time filing rejections.
Incorrect reporting period format
BaFin expects reporting period dates in the format YYYY-MM-DD, with the period end date matching the exact calendar quarter/half-year/year boundary. Filing for Q4 2025 must use 2025-12-31 as the period end, not 2025-12-30 or 2026-01-01. Mismatched period dates trigger a PERIOD_MISMATCH error that prevents acceptance.
NAV currency mismatches
The schema requires NAV in the fund's base currency AND a EUR equivalent. The EUR equivalent must use the ECB reference rate for the reporting period end date. Using a different exchange rate source or date causes NAV_INCONSISTENCY warnings. For funds denominated in EUR, both fields must contain identical values — leaving the EUR equivalent blank is a rejection trigger.
Failing to include all share classes
Every active share class of the AIF must be included in the filing with its own ISIN, WM-Datenservice code, and NAV breakdown. If you launched a new share class mid-period, it must still appear even with partial-period data. BaFin cross-references share class data against its internal register — omitting a registered share class triggers a manual review query.
Geographic exposure codes not matching ESMA enumeration
Geographic allocation must use the exact ISO 3166-1 alpha-2 codes defined in the ESMA Annex IV enumeration, not free-text country names or alternative code sets. The ESMA enumeration also includes supranational codes (e.g., XS for supranational entities) that differ from standard ISO lists. Using "DE" is correct; using "GER" or "Germany" causes XSD validation failure.
BaFin-Specific Quirks
WM-Datenservice codes required alongside ISIN
Unlike most EU NCAs that accept ISIN alone, BaFin requires WM-Datenservice fund classification codes (WKN-adjacent identifiers used in the German market data ecosystem) for all German-domiciled funds. These codes must be obtained from WM Datenservice GmbH and included in the AIFNationalCode field. Filings without WM codes for German funds are rejected during BaFin's supplementary validation layer.
German-language error messages in rejection feedback
All SOAP fault responses and validation error messages from the MVP Portal are returned exclusively in German. Error codes like "Pflichtfeld fehlt" (mandatory field missing) or "Ungueltiger Wert" (invalid value) require German language comprehension or a translation layer to parse programmatically. BaFin has no English-language API documentation for the MVP Portal.
Stricter validation than ESMA minimum
BaFin enforces additional validation rules beyond the base ESMA XSD. These include: NAV cross-section consistency checks (NAV reported in the identification section must match NAV in the financial section), leverage plausibility bounds (gross leverage below 100% triggers a warning), and mandatory population of fields that ESMA marks as optional (e.g., PrincipalExposures must have at least one entry, even for cash-only funds).
MVP Portal maintenance windows
The BaFin MVP Portal undergoes scheduled maintenance typically on weekends (Saturday 22:00 to Sunday 06:00 CET) and occasionally on German federal holidays. During maintenance, SOAP submissions return HTTP 503. Unscheduled maintenance is communicated via the BaFin website (bafin.de) with typically 24 hours advance notice. Plan submissions to avoid Friday evenings and weekends, especially near filing deadlines.
AIFMD II Changes for 2026
AIFMD II (Directive 2024/927) introduces significant new reporting obligations that affect all Annex IV filings from 2026 onward. The following changes are particularly relevant for BaFin filers:
New Liquidity Management Tool (LMT) disclosures
AIFMD II introduces mandatory reporting on liquidity management tools available to the fund, including swing pricing, redemption gates, side pockets, and anti-dilution levies. The Annex IV schema adds new fields for LMT activation history, threshold parameters, and investor impact assessments. Funds must disclose which LMTs are documented in their rules and which were actually activated during the reporting period.
Loan-originating AIF reporting fields
Funds that originate loans must now report loan portfolio composition, borrower concentration, maturity profiles, non-performing loan ratios, and risk retention levels. The new LoanOriginationAIF section in the schema contains approximately 30 additional data fields. This applies to any AIF where loan origination represents more than a de minimis share of the investment strategy.
Enhanced leverage reporting
AIFMD II expands leverage reporting beyond the existing gross and commitment methods. New requirements include: reporting leverage limits set by the NCA (if any), breakdown of leverage by instrument type (repo, securities lending, derivatives, borrowing), and incremental leverage contributed by each borrowing counterparty. The schema now requires a LeverageLimits section even if no NCA-imposed limits apply.
Delegation reporting requirements
AIFMs must now report detailed information about delegated portfolio management and risk management arrangements. This includes the identity (LEI) of each delegate, the percentage of AUM managed by each delegate, the jurisdiction of each delegate, and whether the AIFM retains sufficient substance to avoid being a "letter-box entity." BaFin is particularly strict on delegation reporting given the ongoing EU-wide focus on substance requirements.
How Caelith Automates This
Caelith eliminates manual XML construction and portal wrangling. Here is what the platform handles for you:
- ✓AI-powered data mapping from any source format (Excel, CSV, portfolio systems) to ESMA Annex IV XML — no manual field mapping required
- ✓Automated XSD validation against AIFMD_DATAIF_V1.2.xsd plus BaFin-specific supplementary rules before submission
- ✓Native BaFin SOAP integration with WS-Security credential management — submit directly from the platform without touching the MVP Portal manually
- ✓Complete audit trail with cryptographic proof for every filing, satisfying BaFin record-keeping requirements under Section 44 KAGB
- ✓Multi-NCA support for passported funds — file with BaFin, CSSF, AMF, and other NCAs from a single dataset with automatic format adaptation
Frequently Asked Questions
How long does BaFin take to acknowledge an Annex IV filing?▾
What happens if my Annex IV filing is rejected by BaFin?▾
Do I need to file separately for each share class?▾
Can I submit a test filing to BaFin?▾
What's the penalty for late Annex IV filing with BaFin?▾
Related Resources
Ready to simplify your AIFMD II compliance?
Try our AI-powered Compliance Copilot or book a personal demo with the Caelith team.