NAV error threshold: back-solving reconciliation tolerances
October 20, 2026 · 11 min · Free, with full transcript
Who pays when a fund's NAV is wrong and the manager never saw the error? Under CSSF Circular 24/856 the investment fund manager corrects and compensates, even when the administrator calculated the price. The episode argues that managers should own one position and pricing record, backed by a written pricing policy, rather than inheriting whatever the administrator used. Listeners learn to back-solve reconciliation tolerances from the 0.5% NAV materiality threshold for fixed income UCITS funds: a tenth of it per break for same-day ownership, a quarter of it in open breaks as a NAV gate. Also covered: the aggregation clause, EU T+1, Invesco's identifier consolidation, circular matching, Bloomberg pricing drift and the SEC's Madison Capital Funding settlement.
Listen to the podcast
10 min
Chapters
Key takeaways
- Set reconciliation tolerances from the fund's regulatory NAV error threshold instead of copying vendor default settings.
- Give any single break worth more than a tenth of the NAV threshold a named owner the same day.
- Do not release the NAV while open breaks add up to more than a quarter of the threshold, and log, own and approve any override.
- Check quantities against the custodian and prices against an independent challenger vendor, because IBOR matching the administrator can be two copies of the same mistake.
- Report breaks to the board as money against threshold, age of the oldest break and its owner, not as a raw count.
Read the full transcript
Host:MBA Training. Today: Back-solve reconciliation tolerances from your NAV threshold. Who actually pays when the fund's price is wrong and nobody at the manager ever saw the error?
Expert:The manager. Almost always the manager.
Host:Even when the administrator calculated it? The outsourced firm that literally strikes the NAV, the net asset value, the daily price per share?
Expert:Even then. In Luxembourg the CSSF, the financial regulator, put it in writing with Circular 24/856: the investment fund manager corrects and compensates. Your contract with the administrator might get you money back eventually. The regulator doesn't care about your contract.
Host:So you can outsource the arithmetic but not the blame.
Expert:Beautifully put. Very bleak.
Host:Okay, walk me through a normal morning. What does a mid-sized manager actually know at eight a.m.?
Expert:It knows three different things and believes all of them. The custodian, the bank physically holding the securities, reports settled holdings. The administrator has its own book, built from the custodian's files plus its own vendor prices. And the IBOR, the investment book of record, shows what the front office thinks it traded, priced by whichever vendor the portfolio managers happen to like.
Host:Three versions of the truth before coffee.
Expert:And the one that wins is whichever the administrator used. Performance reports inherit it. Client reports inherit it. The manager finds out there was a gap when an auditor asks.
Host:Then why not crown one of them the golden source and move on?
Expert:Because that fight goes nowhere. Each one is right about different fields. The custodian is right about how many bonds you settled. The IBOR is right about what you meant to trade. Neither of them should be deciding the price.
Host:Who decides the price, then?
Expert:A pricing policy. A named primary vendor, a named challenger, written rules for overrides. The administrator owns nothing by default. It calculates from what you hand it.
Host:Hang on. That's a pretty big demotion for the people you're paying to run the fund's books.
Expert:It's the correct demotion. Think of a restaurant where the waiter decides what you ordered, the kitchen cooks that, and you discover what you ate from the credit card statement.
Host:And then the health inspector fines you, not the waiter.
Expert:Exactly. That's the current operating model at a lot of firms.
Host:Speaking of nobody owning the mess, IBM published a study last week, picked up in the IBM Newsroom. Four in five executives across Europe, the Middle East and Africa said an AI incident reached their board in the past year. Far fewer actually changed their governance afterwards.
Expert:Same disease, different organ. The incident reaches the boardroom, everyone nods gravely, the policy stays exactly where it was.
Host:Boards love a briefing. They're less keen on a rewrite.
Expert:Which is why I'd rather hand them a number in euros than a slide of red dots. Back to breaks, though, because this is where it gets interesting.
Host:Go on. Tolerances. The thresholds where a mismatch gets flagged.
Expert:Most firms copy them off the vendor's default screen. A price break of one percent, a cash break of a hundred units, whatever shipped with the software. None of it connects to the only thing the regulator measures, which is the error in the fund's overall NAV.
Host:And the regulator does measure that?
Expert:Precisely. A fixed income UCITS fund, the standard EU retail fund wrapper, has a materiality threshold of half a percent of NAV. Cross that, and you're into notification and compensation.
Host:So you work backwards from that line.
Expert:Back-solve it, yes. Take that threshold, decide that any single break worth more than a tenth of it gets a named owner the same day, and that the NAV doesn't go out while open breaks add up to more than a quarter of it.
Host:Make it concrete. I'm getting lost in fractions of fractions.
Expert:Hypothetical fixed income fund. You hold a big position in a bond trading near par, and it's mispriced by one point. That's roughly two hundred thousand euros of NAV impact. On its own, nothing fires. It sits under the single-break alarm.
Host:Fine. One sloppy bond.
Expert:Now four of those, open at once. The gate closes. Leave a dozen to age for a week and you're sitting almost exactly on the regulatory threshold. One more and it's a notifiable error.
Host:Wait, what? A dozen small things nobody escalated add up to a reportable incident?
Expert:That's the aggregation clause, and it's the bit people skip. The Circular counts successive untreated errors that were each below the line but cross it together. A pile of little breaks is a regulatory event that just hasn't been introduced to itself yet.
Host:That's genuinely unnerving. It's like being fined for speeding because you went slightly too fast on twelve different streets.
Expert:Ha, yes. And your rental company set the speedometer.
Host:The vendor defaults being the rental company.
Expert:And sometimes the speedometer is biased. Bloomberg, which sells both of the bond price products it compared, so treat it as vendor analysis, found its two price sets drifting a few cents apart across a corporate bond universe before it changed its methodology. Run that kind of quiet bias across a whole book and you've eaten a chunk of your threshold before a single real mistake happened.
Host:Okay, here's where I push back. You want to hold the NAV until breaks clear. Clients want their price. Distributors want their price. Holding the NAV is its own disaster.
Expert:Holding it is a governance decision, not an ops tantrum. The gate runs before the administrator's cut-off, not after.
Host:And T+1 shrinks that window. Settlement the next business day instead of two.
Expert:Europe moves in October next year. The overnight batch that already finishes late is suddenly on the critical path.
Host:Which is why I think a quarter-of-threshold gate is too twitchy. You'll have ops teams in tears every quarter-end, and sooner or later someone overrides it to get the price out.
Expert:Then the override is logged, owned and approved. Which is still miles better than the current model, where nobody even knows a gate existed.
Host:Unless the override becomes the habit. Then it's theatre with a sign-off.
Expert:Fair. I'd still take theatre with a paper trail over improv with no audience.
Host:We're not settling this today.
Expert:We are not.
Host:Where are people getting it right? Give me a name.
Expert:Invesco on the US move to T+1. It started well over a year ahead, and the biggest win wasn't some shiny platform. It was consolidating identifiers.
Host:Identifiers meaning the codes for a security.
Expert:Right. The same bond carries an ISIN, the international code, at the custodian, a SEDOL, the London Stock Exchange code, at the vendor, and some internal number in the IBOR. Most so-called position breaks are just three systems failing to recognise the same thing.
Host:So the dramatic reconciliation crisis is mostly a spelling problem.
Expert:Mostly a spelling problem with a regulator attached. The EU T+1 Industry Committee basically says it: legacy ID mess becomes a critical-path item.
Host:What's going wrong out there, then?
Expert:Circular matching is my favourite. You reconcile your IBOR to the administrator, the administrator built its book from the same custodian file and the same vendor price, everything matches, and everyone feels wonderful.
Host:Two copies of the same mistake agreeing with each other.
Expert:Agreement isn't correctness. Quantity has to be checked against the custodian, price against an independent challenger. And on price challenge, the SEC, the US securities regulator, settled with Madison Capital Funding in February. Loans sold to its own private funds without reasonably checking fair value. Roughly five million dollars repaid plus a penalty.
Host:That lands badly with me, honestly. Investors in those funds trusted someone to check, and the checking was a shrug.
Expert:It's the discretion with no evidence that kills you. Somebody had a view. Nobody wrote down why.
Host:Even the vendors are selling oversight now. SS&C has a pricing-provider benchmark study coming.
Expert:And SS&C is itself an administrator and tech vendor, so useful input, not gospel. Test it against your own holdings.
Host:One more news aside, since we're on ownership. Illinois just rehired Tammy Roust, its former chief data officer, as chief AI officer, per StateScoop. Her predecessor lasted about a month.
Expert:A month. That's shorter than an aged break.
Host:He'd have tripped the aggregation clause.
Expert:But notice who they reached for. The data person. Because whoever owns the record ends up owning the consequences.
Host:So what does the board actually see in your world?
Expert:Not "three hundred and something open breaks." That means nothing. They see: open breaks on this fund are at a fifth of its threshold, the oldest is nine days, and it belongs to the custodian.
Host:Money, age, owner.
Expert:Something a conducting officer, the named exec on the hook in Luxembourg, will actually sign.
Host:Still think your gate's too tight.
Expert:Still think your loose one is how you end up paying compensation for errors you never saw.
Host:So, back to the restaurant. The waiter's demoted, the kitchen has a recipe, someone tastes before it leaves.
Expert:And the bill is in euros, not dots.
Host:Which leaves the uncomfortable part. If the manager pays for every error anyway, how many of today's NAVs did it actually choose, and how many did it simply receive? Sources: Klavius, Cliffordchance and Cssf. Every link is in the show notes. That's a wrap. Fresh CDO briefings drop every week at mba-training.com.
Read and go deeper
- The article behind this episode: Back-solve reconciliation tolerances from your NAV threshold
- The free Data track