Annex IV, generated from the fund ledger and validated before it leaves the building.
For most AIFMs the Annex IV cycle is a quarterly reassembly: figures from the administrator, a template for the filing portal, and validation errors discovered at submission. On this platform the AIFM and AIF reports are generated from fund data the platform already holds, checked for completeness before generation, and validated against ESMA's schemas before you download the package.
What does AIFMD Annex IV reporting software do?
AIFMD Annex IV reporting software brings together the information needed for the return, creates the required files, and checks them before filing. Ariadnah uses data already held in the fund records where possible and clearly marks anything that still needs to be entered by hand.
It produces the manager report (DATMAN) and fund report (DATAIF) in the required XML format. It also works out whether reporting is quarterly, half-yearly, or annual from the manager and fund profile.
Before download, Ariadnah checks the files against ESMA's rules and shows missing information or errors on the dashboard. Problems can therefore be fixed before the package reaches the filing portal.
Report values are projections of the ledger, marked as such.
The usual Annex IV process re-keys: the fund administrator's statements are transcribed into a template, and the transcription is the risk. Each datapoint on this platform carries a source instead: projected (derived from the fund ledger the platform maintains) or manual, entered by a person for what the ledger does not hold.
Where the fund administration module records commitments, capital calls, distributions, NAV observations, and portfolio holdings, the AIFMD projection reads them directly: investor concentration, principal markets and instruments, AuM from the NAV series. Update the ledger and the projected values follow. What remains manual is visibly manual.
The specific claim: the Annex IV package is not assembled at the deadline. It accumulates during the quarter, and the deadline becomes a generation-and-validation step, not a research project.
Filing portals validate at upload. This module validates at the source.
The common stack is a consultant with an Excel model and a national filing portal that rejects malformed XML. Everything between the fund's records and the portal (assembly, mapping, plausibility) is a manual service performed each quarter, with the working files living in someone's mailbox.
Here the mapping from data to Annex IV fields is code, the ESMA schemas ship inside the product, and validation is an in-product step with a per-run report. The consultancy stays where it belongs (interpretation, first-time setup, judgement on classification) as our specialists' work, recorded on the platform.
And because the module is a plugin on the same reporting runtime that produces the DORA Register of Information package, the operational pattern is one your team already knows: run, validate, download, file.
Generation is in product. Submission is still yours.
The platform does not submit to the national competent authority. You download the validated package and file it through your NCA's channel; regulator-side submission interfaces differ per member state and are not wired.
The filing workflow defines a formal sign-off point, but the in-product gate does not yet block generation on approval; four-eyes discipline on filings is carried procedurally today, with our specialists in the loop. Similarly, manual datapoints carry a source marker and version history, not yet the full asserted-by and review-due evidence pattern the supplier modules use.
Scope is Annex IV. UCITS reporting, PRIIPs documents, and national statistical returns are flagged on the fund's regulatory profile but not generated by this module.
The practical questions behind this solution.
Plain answers about what the platform does today, where people still decide, and what remains outside its scope.
Which data does Ariadnah use for AIFMD Annex IV reporting?
Ariadnah uses information about the manager and fund, where the fund is marketed, commitments, capital activity, NAV, and portfolio holdings where those records are available. Anything that cannot be taken from the platform is clearly marked for manual input.
Which AIFMD Annex IV files does Ariadnah produce?
Ariadnah produces the DATMAN report for the manager and the DATAIF report for each fund in the required XML format. It checks the files against ESMA's rules and keeps a validation report for each run.
Can Ariadnah determine the Annex IV reporting frequency?
Yes. Ariadnah works out whether reporting is quarterly, half-yearly, or annual using information about the manager and fund, including assets under management, leverage, domicile, and where the fund is marketed. If information is missing, the platform flags it instead of guessing.
Does Ariadnah submit Annex IV reports directly to the regulator?
No. Ariadnah prepares and checks the reporting package for download. The organisation then files it through the channel required by its national authority.
A discovery call, not a product demo.
You describe the compliance problem consuming the most of your team's time. We walk the platform through an example close enough to your operation that you can judge whether this way of modelling compliance fits how you want to work.
Book a discovery call →