Upload your prime broker extract. Get a filing-ready AIF001 and AIF002 XML in minutes — not days. Built by the operators who actually file these every quarter.
Most AIFMs still file Annex IV by typing answers into a 200-field web form, copy-pasting from Excel pivots their CCO built five years ago. It's slow, error-prone, and expensive in time the team should be spending on alpha.
The current process punishes everyone who isn't filing 50 funds at scale. Errors only surface after submission — meaning a single bad SubAssetType code can cost a half-day round-trip.
And full-scope AIFMs? They get extra sections — leverage, liquidity buckets, risk measures, counterparty exposures — with conditional logic that's impossible to learn from the form alone.
From the standard NAV admin / prime broker exports your team already pulls every quarter, straight to validator-ready XML.
Drop in your position appraisal and transaction history Excel files from NAV Consulting, Marex, or any major prime broker. We auto-detect format.
The engine classifies each instrument by AIFMD sub-asset type, aggregates principal markets and exposures, and shows you every assumption it made — editable inline.
Both AIF001 and AIF002 XMLs are produced from a single workflow, schema-validated against the FCA template before they leave the page.
Got a validation error from RegData? Paste it back in. The engine resolves it and regenerates — same loop we use internally on real filings.
AIF001 (manager-level) and AIF002 (fund-level) generated from the same dataset. No double entry, no reconciliation work between them.
Catches the errors RegData would catch — percentages summing wrong, conditional fields, invalid sub-asset codes — before you submit. Saves the round-trip.
If the FCA validator does flag something, paste the error back in. The engine identifies the field, proposes the fix, and regenerates. Loop closes in seconds.
Pre-loaded with the full AIFMD sub-asset taxonomy. Every classification is shown — override per ticker if your fund's products are unusual, and we remember it next quarter.
Compare this filing against the last one. Spot when AUM, geography, leverage, or counterparty exposure has shifted materially — useful for both compliance and CIO review.
Every input file, every transformation, every override is preserved. If FCA queries a number 18 months later, the lineage is one click away.
Your portfolio is the most sensitive data your fund holds. Our default architecture keeps it out of any third-party LLM, full stop.
The XML generation is rules-based Python, not generative AI. No position data is ever sent to OpenAI, Anthropic, or any third-party model.
For funds with strict data residency requirements, we offer a containerised deployment that runs entirely inside your own AWS, Azure, or GCP account.
For the validation-error fix-up loop, we send only the error message and the abstract structure of the offending field — never ISINs, amounts, or counterparty names.
TLS 1.3 end-to-end. AES-256 at rest. Files auto-purge after 30 days unless your retention policy says otherwise. SOC 2 Type II in flight.
The decision to send positions to an LLM should never be the user's accidental click. We've built around that.
Annual subscription. Cancel any time. Bring your own deployment if you need it.
For small AIFMs filing AIF001 + AIF002 once or twice a year.
For full-scope AIFMs and managers running multi-fund structures.
For funds requiring data residency or single-tenant deployment.
Frontier Reporting was incubated inside Frontier Road Limited — an FCA-authorised investment manager — by the team that runs filings on its own master fund.
Every quarter, our compliance officer used to spend the better part of two days populating Annex IV by hand — copy-paste from NAV Consulting exports into RegData, validation rejections, second submission, and a third for good measure.
The core insight: 95% of the work is deterministic. Position file plus a mapping table plus a schema gives you the XML. The only judgment calls are at the edges, and those are the same edges every quarter.
"Once we automated our own filings, the obvious next thing was to let other small AIFMs use it. The pain is universal." — Baptiste Aubert, Frontier Road
We're FCA-authorised, we file these reports for real, and we know what an FCA validator error looks like when it lands in your inbox at 4pm on a deadline day.
An EM credit hedge fund. Full-scope AIFM. We file AIF001 and AIF002 every cycle on our own master fund, and we built the engine to make our own life easier first.
The public sandbox is live with synthetic data — try it now. For your own filings, drop us a line: we'll set up a single-tenant deployment so your position data never leaves your perimeter.