The alternative investment industry’s relationship with delegation has always rested on a quiet assumption: that how an AIFM structures and supervises its delegates is an internal governance matter, visible to the regulator principally through authorisation submissions and periodic supervisory dialogue.
AIFMD II materially changes that assumption.
From April 2027, the mechanics of every material delegation arrangement, including who the delegate is, what they manage, how many people oversee them, when due diligence was last conducted and what issues were found, will be disclosed in structured, field level data to the national competent authority on a recurring basis.
This is not an incremental expansion of existing disclosure requirements. It is a change in the regulatory model.
Delegation governance becomes a continuous reporting obligation rather than a documented internal control. The operational infrastructure required to meet that obligation does not yet exist in most firms.
What the new delegation disclosure requirements demand
The starting point is the directive itself.
AIFMD II’s amendments to Article 24 require AIFMs to include delegation specific data in their Annex IV submissions from April 2027.
That data includes the full time equivalent number of employees performing day to day portfolio management and risk management within the AIFM, the number of FTEs dedicated to monitoring delegation arrangements, the names, domiciles and regulatory status of each delegate and sub delegate, the specific activities delegated, the percentage of AuM under delegation per delegate, contract start and end dates, the dates and outcomes of due diligence reviews conducted on each delegate, and the issues identified through oversight and the remediation timelines applied.
Reading that list as a compliance requirement, it looks manageable.
Reading it as a data architecture requirement reveals the problem.
This is not financial data. It does not live in fund administration systems, custodian feeds or risk platforms.
It lives across HR systems for FTE counts, legal and compliance document repositories for delegation agreements and due diligence records, governance calendar systems for oversight meeting schedules and, in some cases, email threads and Word documents that have never been structured for systematic extraction.
The AIFMD II delegation disclosure is asking AIFMs to take data that is currently distributed across four or five organisational systems, none of which were designed to feed a regulatory reporting pipeline, and produce it in a standardised, validated, recurring format that connects directly to Annex IV.
The legal requirement is clear. The operational pathway from current state to compliant submission is not, for most firms, straightforward.
AIFMD II does not ask whether your delegation arrangements are well governed. It asks whether you can prove it in structured data, on a recurring basis, to a regulatory template. Those are different questions with different answers.
The letterbox entity problem
To understand why AIFMD II’s delegation reporting requirements are as granular as they are, it is worth understanding what ESMA and the European Commission were trying to address.
The concern, longstanding in European supervisory circles, is the proliferation of AIFMs that are formally domiciled in EU jurisdictions for passport purposes while the substantive investment management activity sits outside the EU, in locations such as London, New York or Hong Kong, with the EU entity functioning as a structural shell rather than a genuine management centre.
The original AIFMD delegation framework was intended to prevent this.
In practice, the combination of light touch delegation disclosure requirements and divergent NCA supervisory standards meant that the line between adequate substance and a letterbox entity was policed inconsistently.
ESMA’s own supervisory convergence work identified material variation across member states in how they assessed AIFM delegation arrangements, including cases where significant portfolio management was delegated to third countries with minimal residual substance in the EU entity.
The AIFMD II delegation data requirements are the structural response to that finding.
The FTE disclosures are specifically designed to give regulators a quantitative basis for assessing whether the substance claimed by an AIFM is real.
An AIFM reporting that two FTEs perform day to day portfolio management internally, against a delegation arrangement covering 95% of AuM, is providing ESMA with exactly the data needed to assess whether the delegation model crosses the line into letterbox territory, regardless of what the AIFM’s legal submissions have historically maintained.
This matters for how firms should interpret the new requirements.
The delegation data in Annex IV will not be assessed in isolation. It will be cross referenced against authorisation data, compared against prior submissions and analysed at an industry level to identify patterns.
Firms whose delegation disclosures are inconsistent with their authorisation submissions, or whose FTE counts have declined materially while delegated AuM has grown, should expect supervisory attention that goes beyond a DQEF warning.
Governance records were never built for reporting
The most significant operational challenge in meeting the AIFMD II delegation disclosure requirements is not capturing the data going forward.
Most compliance functions, once they understand the requirements, can design a framework for collecting it systematically from the point of implementation.
The challenge is the historical record and the current state of the governance documentation that will be needed to populate the first filings.
Consider due diligence records.
AIFMD has always required AIFMs to conduct due diligence on their delegates and maintain appropriate oversight. Most firms have done this.
But the format of those records varies widely.
Some firms maintain structured due diligence questionnaires in a dedicated compliance system. Others maintain narrative due diligence reports in a document management system. Others maintain a combination of completed questionnaires, meeting minutes and email correspondence that together constitute the due diligence record, but have never been organised in a way that makes specific data points, such as dates, findings and remediation actions, systematically extractable.
Annex IV requires dates and outcomes of due diligence reviews, and issues identified with remediation timelines. That is structured, field level data.
Producing it from an unstructured document archive under a submission deadline is a materially different exercise from producing it from a system that captures it in a structured format at the point of each review.
Firms that begin now can redesign their governance processes to produce structured data going forward. Firms that wait until the template arrives will face the additional challenge of retrofitting historical records that were never designed to be reported.
FTE disclosure creates a new governance challenge
The FTE disclosure creates a parallel challenge of a different type.
Counting the FTEs who perform day to day portfolio and risk management within the AIFM sounds straightforward.
In practice, many individuals perform mixed functions: part portfolio management, part risk oversight, part client reporting, part operational management.
How is a 0.6 FTE allocation to portfolio management calculated, validated and evidenced?
What happens when that allocation changes between reporting periods?
Who in the organisation owns the accuracy of the FTE figure and can demonstrate, if a regulator asks, how it was arrived at?
These questions require a governance process that connects HR data to compliance reporting in a way that has never previously been required.
This is why AIFMD II delegation reporting should not be treated as a template completion exercise.
It requires firms to define ownership, calculation methodology, approval workflow and evidence retention for data that previously sat outside regulatory reporting infrastructure.
What fund service providers need to confront
For fund administrators and service providers managing Annex IV on behalf of multiple AIFM clients, the delegation reporting requirements present a specific commercial and operational challenge that has not yet been fully addressed in most service relationships.
The data required for delegation disclosure, including FTE counts, due diligence records, oversight outcomes, delegate identities and contract terms, sits primarily with the AIFM client, not the service provider.
The administrator can collect and validate it, but only if the client provides it in a form that is accurate, complete and structured.
Most current service agreements do not specify how delegation governance data flows from the AIFM to the administrator. Most data collection interfaces between AIFMs and their reporting service providers were not built with delegation data in mind.
This creates a gap that will become acute as the April 2027 deadline approaches.
If a service provider waits until ESMA publishes the final template before redesigning its client data collection workflows, it will be building new data pipelines simultaneously with the production cycle for the first compliant filings.
That is an operationally high risk position for both the provider and the client.
The service providers that are engaging with AIFM clients now on delegation data governance, identifying what records exist, what format they are held in and what structural changes are needed to make them reportable, are in a fundamentally stronger position to deliver clean submissions at first filing.
For the AIFM, the implication is symmetrical.
Firms that have outsourced Annex IV production and are assuming the service provider will handle the delegation data requirement without significant client side input are likely to be disappointed.
This is not data the administrator can enrich from external reference sources. It is governance data that only the AIFM holds. The quality of the submission will reflect the quality of the governance records the AIFM has maintained.
Key takeaways
AIFMD II’s delegation disclosure requirements change the regulatory model. Delegation governance becomes a continuous reporting obligation, not an internal control evidenced mainly through authorisation submissions.
The new Article 24 data requirements cover FTE counts, delegate identities and regulatory status, percentage of AuM under delegation, due diligence dates, oversight outcomes and remediation timelines. None of this data currently sits in systems designed to feed a regulatory reporting pipeline.
The FTE and due diligence disclosures are specifically designed to give ESMA a quantitative basis for assessing AIFM substance against delegation scope. Disclosures inconsistent with authorisation submissions are likely to generate supervisory attention.
The operational challenge is not only building a new data collection process. It is the current state of governance records, including due diligence archives, oversight meeting logs and FTE allocation methodologies, which were never structured for systematic reporting extraction.
Fund service providers cannot enrich delegation data from external sources. The quality of the Annex IV delegation disclosure will directly reflect the quality of the AIFM’s own governance records. Service agreements and data flows need to be redesigned before the template arrives.
The question for SMF16 holders and COOs
The question every SMF16 and COO should be asking of their current delegation governance framework is not whether it satisfies AIFMD.
Most do.
The question is whether the evidence of that governance, including due diligence records, oversight outcomes, FTE allocations and remediation logs, exists in a form that can be extracted, structured and submitted to a regulator on a recurring basis without a manual reconstruction effort at each filing cycle.
For most firms, the honest answer is not yet.
AIFMD II does not change what good delegation governance looks like.
It changes who can see it, and in what format they expect to find it.
How Datox helps
Datox helps fund managers, fund administrators and compliance teams turn fragmented governance and reporting information into structured, controlled regulatory data.
By connecting source records, standardising data collection workflows and maintaining an evidence trail from source data to final submission, Datox helps firms prepare for AIFMD II delegation reporting and the broader evolution of Annex IV.
To see how Datox can support AIFMD II and Annex IV reporting, book a demo with our team.