# Automating NAV and investor reporting in fund administration

Published 20 May 2026 by Spark · Sector playbooks · 4 min read
Canonical: https://hellospark.co.uk/writing/automating-nav-investor-reporting-fund-administration

> The NAV cycle is a deadline machine that runs on manual assembly. Automate the reconciliation, the validation and the drafting, surface only the exceptions, and the cycle runs faster with fewer late nights. The numbers still get checked by a human.

The NAV cycle is a deadline machine, and most of what your team does inside it is assembly. Gather prices and positions from the same places, reconcile them, chase the exceptions, then draft the same investor documents under the same monthly or quarterly pressure. Automate the assembly and the reconciliation, let AI handle the messy documents and the first drafts, and surface only the exceptions that need a person. Done well, the manual effort on a reporting cycle drops by half or more, and the late nights at period end stop being the norm. The numbers still get checked and signed by a human. That never changes.

This is the core of the work we build for fund administrators, and it splits cleanly into three jobs: get the data right, reconcile it, then draft from it. Here is each one, and where the human stays in the loop.

## Data validation before anything else

A NAV is only as good as the data feeding it, and the data arrives in a mess: custodian statements as PDFs, price files in three formats, a manager’s spreadsheet with a column moved since last month. The first win is turning all of that into clean, structured data automatically, which is the same [document extraction](/writing/ai-document-extraction) problem the whole back office shares. Prices, positions, cash movements and corporate actions get read, normalised and validated against expectations before they touch the NAV. A price that has moved 40 percent overnight or a position that appeared from nowhere gets flagged at the door, not discovered three steps later when it is far more expensive to unpick.

## Reconciliation that surfaces only the exceptions

Reconciliation is where administrators lose their evenings, and it is the most automatable step in the whole cycle. Matching positions and cash across custodians, the accounting system and the manager’s records is rule-based work at heart. Automation runs the match, applies your tolerances, and presents only what breaks: the handful of genuine exceptions, each one with the two sides laid side by side and a plausible explanation drafted. Instead of an analyst working through a thousand matched lines to find the five that do not, they open a queue of five. The tedious 95 percent runs itself; the human attention goes where the judgement actually is.

## Drafting investor reports and capital call notices

Once the numbers are locked, the documents write themselves from source, into your templates. Quarterly investor reports, capital call notices, distribution notices and regulatory returns are all structured outputs built from data you already hold. AI drafts each one, personalised per investor, with the figures pulled straight from the validated model rather than re-keyed. A capital call that took an afternoon of copy-paste per investor becomes a batch generated in minutes and reviewed as a set. The commentary in an investor report can be drafted too, in your house tone, for the fund controller to edit rather than write from a blank page. Drafting is the machine’s job. Sign-off is not.

## The checks are the whole point

None of this releases a NAV or sends an investor notice on its own. Every number the automation produces is checked against your model, and every document waits for a human to review and approve before it goes out. This is not caution for its own sake. Getting a capital call amount wrong or publishing a NAV with a stale price is the kind of failure that reaches investors and regulators, which puts it squarely in the high-stakes tier where [meaningful human oversight](/writing/human-in-the-loop-ai) is not optional. The reviewer sees the exceptions, the drafts and the underlying figures, can override anything, and signs the release themselves. The automation removes the assembly, not the accountability.

## An audit trail the depositary can inspect

Every cycle leaves a complete, inspectable record: which data came in from where, what was flagged and why, how each exception was resolved and by whom, and who approved the final NAV and each investor document, with the prompt and model version logged. For a regulated fund administrator, and for the depositary and auditors sitting behind you, that trail is not a nice-to-have. Build it in from day one and it is nearly free. Retrofit it after a query and it is painful, sometimes impossible. It is the difference between a fast cycle you can defend and a fast cycle you cannot.

## Where to start

Do not try to automate the whole cycle at once. Pick the single most painful step, usually the reconciliation or the investor report drafting, and prove the pattern there with the checks and the audit trail working properly. It pays to map the sequence first so you build in the order that returns the most soonest. Prove it once, then roll it across fund types and across the cycle.

If your reporting cycle runs on late nights and manual assembly, a 30-minute [review](/book-a-review) will get you a straight read on which step to automate first and what it is worth in hours recovered per cycle. No deck. Just the number.
