AIFMD II Transposition: The Delegation, Loan-Origination and Reporting Systems Managers Must Have Ready

AIFMD II reads like a legal-and-policy exercise, and most of the guidance treats it as one. The parts that will actually catch managers out are the parts that only exist once you have built the data and the controls to run them.

Directive (EU) 2024/927 — AIFMD II — entered into force on 15 April 2024, and member states must transpose it into national law by 16 April 2026. Luxembourg’s transposing text, Bill 8628, was submitted to Parliament on 3 October 2025 and, in the government’s own framing, mirrors the directive without gold-plating. So the honest reading for a manager is this: the deadline is fixed, the domestic detail is nearly settled, and the work that takes the longest is not the policy drafting. It is the plumbing. Three areas turn from policy expectation into examinable system requirement, and each needs data or controls that take months, not weeks, to stand up.

Delegation stops being a paragraph and becomes a dataset

Under AIFMD I, describing your delegation arrangements to the regulator was largely a narrative exercise at authorisation. AIFMD II amends the delegation regime so that the description becomes structured, ongoing data. At authorisation the AIFM must give the competent authority the delegates’ names and domiciles, a description of the human and technical resources committed to portfolio and risk management, whether the delegation is partial or full, and the periodic due-diligence plan for monitoring the delegate. That much is disclosure. The heavier obligation is the periodic reporting that follows: per delegate, the regulatory status and identifiers, the full-time-equivalent staff both performing and monitoring the delegated function, the percentage of assets under management that is delegated where portfolio management is involved, the dates and findings of due-diligence reviews, and the sub-delegation chain with commencement and expiry dates.

Read that as an engineer, not a lawyer, and the requirement is a maintained register with defined fields, refreshed on a reporting cycle, reconcilable against your contracts and your due-diligence records. Most managers do not hold that today. They hold delegation as prose in an authorisation file and a set of agreements in a document store, with headcount and FTE splits living in someone’s head or a supplier’s org chart. The recitals to the directive are pointed about why the granularity matters: the proportion of assets delegated is, on its own, not evidence of adequate substance. In other words, a supervisor is being invited to look past the headline percentage and into the resourcing detail — which only helps you if that detail is captured, current and defensible. This is the same substance question that has been driving Luxembourg managers to restructure their technology functions, now expressed as a reporting field with a filing date attached.

Loan origination is a control system, not a policy

For managers of loan-originating AIFs, AIFMD II introduces hard, monitorable limits, and the mistake would be to file them as a credit policy and move on. The leverage of a loan-originating AIF is capped at 175% of net asset value for open-ended funds and 300% for closed-ended funds, calculated on the commitment method. A single-borrower concentration limit of 20% of the fund’s capital applies where the borrower is a financial undertaking, another AIF or a UCITS, subject to a ramp-up period of up to 24 months from first subscription. Where an originated loan is transferred to a third party, the fund must retain a 5% net economic interest — held to maturity, or for at least eight years on longer-dated loans. And an AIF whose sole strategy is to originate loans in order to sell them on — the originate-to-distribute model — is prohibited outright.

Every one of those is a number you have to be able to produce on demand, from live position data, against a defined denominator. A leverage cap is only meaningful if the commitment-method calculation runs on your actual book and trips before you breach it. A 20% concentration limit needs a borrower-classification that reliably tells you whether a counterparty is a financial undertaking, and an aggregation that rolls exposures up to the right entity. The 5% retention needs a register that tracks originated-then-transferred loans and their retention clocks. There is grandfathering — loans originated before 15 April 2024 sit outside these requirements, and funds constituted before that date that raise no new capital stay outside them — but a live fund has to distinguish the grandfathered book from the in-scope book, which is itself a data problem. Building these as monitoring controls with pre-breach alerting, rather than as quarterly hand-checks, is the difference between managing the limit and discovering you have crossed it.

The Annex IV expansion is a data-plumbing project

Supervisory reporting under AIFMD II is materially wider. The directive removes the old “principal markets and instruments” framing and requires reporting on all instruments traded, the total leverage employed, the member states where units are actually marketed, and the delegation detail described above. The timing is the part worth reading twice: while transposition is 16 April 2026, the expanded reporting itself applies from 16 April 2027, because ESMA is given a twelve-month window to develop the technical standards and the reporting templates that will carry it. That one-year gap reads like breathing room and functions like a trap. The data model you need — instrument-level coverage, a leverage figure computed consistently, marketing footprint by member state, delegation as structured records — is exactly the kind of thing that takes the full year to source, map and reconcile across a fund administrator, a portfolio system and your own registers. Firms that wait for the final template before starting the data work will be sourcing fields under deadline, which is where reporting quality goes wrong.

The unglamorous truth is that most of this is a lineage exercise: knowing where each reportable field originates, who owns it, and whether it reconciles to the golden source. That is the same discipline that decides whether a reporting or analytics layer can be trusted at all — well-governed source data in, defensible output out. Skip it, and you are assembling a regulatory filing from spreadsheets whose provenance nobody can explain.

What a supervisor will actually ask to see

Transposition converts these from things you have written down into things you have to be able to demonstrate operating. On the day, the questions are concrete. Show us the delegation register and the last time each field was refreshed. Show us the leverage calculation for this fund and the control that would have stopped a breach. Show us the retention clock on the loans you have transferred. Show us how a reported figure ties back to source. This is the same evidential posture that operational-resilience supervisors already expect a technology function to be able to show — not the policy, the working system behind it. The instinct will be to treat the transposition date as the start line. For the data and control work, it is the finish.