Outsourcing: Why NAV Oversight Should Not Be an Afterthought

By Director, Mark Beattie and Senior Consultant, Grant Palmer

Generally with outsourcing programmes, NAV oversight often slips down the agenda. The focus is naturally on transitioning processes, standing up the new model, and hitting deadlines – governance is often left to “sort out later.” The problem is that oversight isn’t just another box to tick. Frameworks tend to be reactive, manual, and fragmented, which leads to missed pricing errors, manual firefighting, and a loss of confidence in both your vendor and your own controls. Leave it too late, and you create gaps that quickly turn into problems that are costly and difficult to unwind.

What we’ve seen time and again is that the firms who treat oversight as a foundation, not an afterthought, avoid these pitfalls. They go live with a model that is lean, resilient, and future-proof and not one that needs addressing months down the line.

Why does oversight get left so late?

There are two recurring themes we see.

Resource constraints and conflicting priorities are key factors, pressing project activities often take precedence over establishing an early oversight framework. Teams are under pressure to hit transition deadlines, and oversight gets deferred until “later,” when it’s much harder to retrofit effectively.

The second is that people underestimate the complexity of building an oversight function. On paper it looks straightforward: “we’ll just put a check in place.” In practice, if you haven’t designed it properly up front, you’re left firefighting with spreadsheets and manual reconciliations. We’ve seen oversight teams’ balloon to the point where they’re larger than the original in-house team the client thought they were replacing.

Investing time to agree tolerances and business rules can help mitigate this, and we have some proven design principles to assist this.

The real risks of bolting it on

Leaving oversight to the last minute creates issues that are very hard to unwind:

• Manual burden – Oversight becomes a patchwork of Excel trackers and ad-hoc reports. You might outsource the function, but suddenly you need an army of people just to chase exceptions.
• Missed NAV errors – The worst-case scenario: mispriced funds. Once investors have to be compensated, the cost is not just financial but reputational.
• Vendor drift – A provider may look solid on day one. Then a year later they decide to offshore half the team, and performance starts to slip. If you haven’t put proper metrics and tolerances in place, you have no way of proving service levels are deteriorating.
• Reactive fixes – Most often, firms only strengthen controls after a major error. By then, it’s too late; you’re building oversight in response to failures, not to prevent them.

We’ve even seen firms run for years with reports being churned out daily by the administrator only for it to emerge that no one on the client side had reviewed them since the oversight team was stood down a decade ago. Without a proper model, you don’t know which controls matter, which are redundant, and whether your oversight effort is actually protecting you.

What it looks like when you do it properly

Contrast that with the firms who build oversight in from the outset.

One client we worked with designed automated NAV oversight right at the start of their outsourcing programme. We ran parallel testing with their vendor, incorporating automation and exception-based validation enhanced by AI. This replaced manual processes, streamlined operations, improved efficiency, and significantly reduced errors. Exceptions were designed around NAV impact, not noise. When they went live, the model was clean, the oversight team was lean, and the vendor knew exactly what they would be held accountable to.

Another example: a firm we supported on a multi-year programme built design principles into their TOM, things like standardisation, using native system functionality rather than tactical workarounds, and focusing on data completeness and quality from day one. That gave them an anchor to keep coming back to as the programme evolved. It meant when the vendor inevitably made changes to their operating model, the client had the governance in place to spot performance drift immediately.

The difference is night and day.

The non-negotiables for NAV oversight

From our experience, four things matter above all else:

1. Leverage automation and AI – Implement intelligent automation and AI-driven validations to streamline NAV oversight processes, reduce manual intervention, and minimise the risk of errors.
2. Get the data right – Oversight systems are only as strong as the data feeding them. Define exactly what you need from your outsourcer and make it contractual. “Rubbish in, rubbish out” applies here more than anywhere.
3. Agree tolerances up front – Don’t wait until you’re live to decide what “good” looks like. Set the thresholds early: how many basis points is acceptable, which exceptions matter, and how they’ll be escalated.
4. Test in parallel – Dual running before go-live is invaluable. It tells you the true volume of exceptions, helps you size the oversight team properly, and avoids nasty surprises once you’ve transitioned.

Closing thought

Outsourcing NAV doesn’t mean outsourcing responsibility. You are still accountable, and regulators will hold you to it.

Treat oversight as an afterthought, and you’ll spend years firefighting with manual processes, inflated teams, and costly errors. Build it in from day one, and you get a model that’s efficient, resilient, and fit for the future.

In our experience, that’s the difference between outsourcing that works and outsourcing that unravels.

Outsourcing oversight doesn’t mean losing control; it means gaining independent, expert eyes before gaps become risks. Let us help you put the right model in place from day one. Get in touch to find out more.