How to File Annex IV XML to BaFin's MVP Portal: A Complete Guide for KVGs

Filing AIFMD Annex IV reports to BaFin is one of the most technically demanding compliance tasks facing German Kapitalverwaltungsgesellschaften (KVGs). The process requires generating XML files that conform to ESMA's strict XSD schema, navigating BaFin's MVP Portal (Meldeportal und Veröffentlichungsplattform), and ensuring your submission passes validation without errors.

This guide walks through every step of the process — from initial MVP Portal registration to receiving your filing confirmation. Whether you're filing manually for the first time or troubleshooting a failed submission, this is the reference you need.

Step 1: MVP Portal Registration and Access

Step 2: Understanding the XML Format Requirements

BaFin accepts Annex IV reports exclusively in XML format, validated against ESMA's official XSD schema. Here's what you need to know:

XSD Schema Version

The current schema is ESMA Rev 6, AIFMD_DATMAN_V1.2.xsd. This schema defines the complete structure for AIFM-level and AIF-level reports. You can download the official schema from ESMA's website or through Caelith's API documentation.

XML Structure Overview

An Annex IV filing consists of two main components:

1. AIFM-level report (24-Q/S/Y): Information about the management company — AuM, number of AIFs managed, principal exposures, investor concentration.
2. AIF-level report (24-Q/S/Y): Per-fund information — NAV, strategy, instruments, leverage, liquidity profile, risk measures, investor breakdown by type and geography.

Sample XML Header

<?xml version="1.0" encoding="UTF-8"?>
<AIFReportingInfo
  xmlns="urn:aifmd:datman"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="urn:aifmd:datman AIFMD_DATMAN_V1.2.xsd"
  CreationDateAndTime="2026-04-30T10:00:00"
  Version="1.2">

  <AIFMReportingCode>24-Q-1</AIFMReportingCode>
  <AIFMNationalCode>DE-BAFIN-XXXXXX</AIFMNationalCode>
  <AIFMName>Example KVG GmbH</AIFMName>
  <AIFMEEAFlag>true</AIFMEEAFlag>
  ...
</AIFReportingInfo>

Step 3: Generating Valid XML

This is where most KVGs struggle. The Annex IV taxonomy contains 147+ fields, many with interdependencies and conditional requirements. Common generation approaches:

Manual / Spreadsheet-Based

Some KVGs maintain Excel templates that map fund data to Annex IV fields, then use VBA macros or custom scripts to generate XML. This approach works for simple fund structures but breaks down quickly with multiple AIFs, complex strategies, or frequent reporting cycles.

Managed Service Providers

Companies like anevis solutions offer managed Annex IV reporting services. You provide your fund data, they generate and file the XML. This works well but costs €50-80K/year and introduces dependencies on external timelines.

Automated Agent-Based

Caelith's BaFin Filing Agent reads your fund data from the Caelith platform, maps it to the ESMA taxonomy, generates XSD-validated XML, and submits directly to BaFin's MVP Portal. The entire process runs autonomously and produces a SHA-256-hashed audit trail. Cost: included in the €1,490/month Boutique plan for up to 3 funds.

Step 4: XSD Validation

Before submitting to BaFin, your XML must pass validation against the official XSD schema. BaFin will reject any file that fails validation, and you'll receive a generic error message that's often difficult to debug.

How to Validate Locally

Use xmllint (part of libxml2) or any XSD-capable XML editor:

xmllint --schema AIFMD_DATMAN_V1.2.xsd your-filing.xml --noout

If the file is valid, you'll see: your-filing.xml validates. Any errors will output line-by-line with the field path and violation type.

For a detailed breakdown of the most common validation failures, see our companion article: Top 10 Annex IV XML Validation Errors.

Step 5: Submitting to BaFin's MVP Portal

Important Timing Rules

• Quarterly reporters (>€1.5bn AuM or >500 investors): Due within 30 days of quarter-end
• Semi-annual reporters (€500M-€1.5bn AuM): Due within 45 days of half-year-end
• Annual reporters (<€500M AuM): Due within 45 days of year-end
• Late submissions require written explanation to BaFin and may trigger supervisory action

Step 6: Handling Rejections and Corrections

If your submission is rejected by BaFin (either at upload or during post-submission review), you'll receive a notification through the MVP Portal. Common reasons for rejection:

• XSD validation failure: The most common reason. Fix the XML and resubmit.
• Incorrect reporting period: Ensure your ReportingPeriodType and ReportingPeriodYear match the selected period in the portal.
• Duplicate submission: You're submitting a report for a period you've already filed. Use the "Amendment" reporting type instead of "Initial."
• Missing AIF reports: You submitted an AIFM-level report but forgot one or more AIF-level reports. BaFin expects both.

Corrections and amendments follow the same upload process but must be flagged as "Amendment" (Korrekturmeldung) rather than "Initial" (Erstmeldung).

Step 7: Archiving and Audit Trail

German regulatory requirements mandate that you retain copies of all Annex IV submissions, confirmation receipts, and supporting documentation for at least 5 years. Your archive should include:

• The submitted XML file (exact version that was accepted)
• The BaFin confirmation receipt (Eingangsbestätigung)
• Validation logs showing the XML passed XSD validation before submission
• Source data mapping documentation (which fund data fed into which Annex IV fields)
• Any amendment history and the reason for each correction

Caelith automatically generates a SHA-256 cryptographic hash of every submitted file and confirmation receipt, creating a tamper-evident audit trail that satisfies both BaFin and external audit requirements.

Automate the Entire Process

The manual process described above takes an experienced compliance officer 4-8 hours per filing cycle for a single fund. With multiple AIFs, quarterly reporting, and the risk of validation errors requiring resubmission, the annual time investment is substantial.

Caelith's BaFin Filing Agent reduces this to minutes: upload your fund data, the agent generates validated XML, submits to BaFin, captures the confirmation, and logs everything with a cryptographic audit trail. No portal navigation. No XML debugging. No late nights before filing deadlines.

Related Articles

• Top 10 Annex IV XML Validation Errors (And How to Fix Them) — The most common XSD validation failures and their exact fixes. Essential reference for filing season.
• Why General-Purpose AI Agents Fail AIFMD Compliance — Why OpenClaw can't handle BaFin filing, and what purpose-built compliance agents look like.
• Autonomous Filing Agents: How AI Is Replacing Manual Submissions — The shift from manual portal uploads to fully autonomous regulatory filing.

Want to automate the entire process? Explore Caelith's BaFin Filing Agent or try the interactive demo.