Back-solve reconciliation tolerances from your NAV threshold

On any given morning, a mid-sized asset manager holds at least three versions of the truth. The custodian reports settled holdings. The fund administrator holds its own book, built from custodian files, trade feeds and its own vendor prices. The investment book of record (IBOR) shows trade-date positions priced by whichever vendor the front office prefers. When these disagree, the version that reaches the NAV is usually the one the administrator used. Performance and client reports then inherit it, and the manager learns about the gap when a client, an auditor or a depositary asks.

That arrangement is getting harder to defend, for regulatory and operational reasons at once. In Luxembourg, under CSSF Circular 24/856, the IFM corrects and compensates, even when the NAV is calculated by an administrator. In Europe, the move to T+1 settlement on 11 October 2027 cuts the time available to reconcile. My argument: the reconciled position and price record should be a product the manager owns, gated before NAV is struck, with tolerances back-solved from the fund's own NAV error threshold. Default tolerances inherited from the vendor and break reports read after the fact are how a manager ends up paying compensation for errors it never saw.

How to build a single trusted position and pricing record

Step 1: Assign authority field by field

Arguing about whether the custodian or the administrator is the "golden source" goes nowhere, because each one is right about different fields. Decide authority per attribute and write it down:

• Settled quantity and cash: the custodian, because it holds the assets and the depositary relies on its records.
• Traded quantity and pending settlements: the IBOR, reconciled to the custodian once settlement happens.
• Price: your pricing policy. That means a named primary vendor per asset class, a named challenger, and a documented hierarchy for overrides.
• FX rates: a single snapshot time, fixed in policy and applied consistently across NAV, performance and reporting.
• Corporate action terms: one source of announcements, with custodian confirmation of entitlements.

The administrator owns none of these fields by default. Its job is to calculate from the record you hand it, and your reconciliation checks that it did. Here is the rule for the whiteboard:the custodian owns quantity, the IBOR owns intent, the price policy owns price, and NAV waits until open breaks are under a quarter of the threshold.

Step 2: Back-solve tolerances from the NAV error threshold

Most reconciliation tolerances are absolute numbers copied from vendor defaults: a quantity break of zero, a price break of 1%, a cash break of 100 units of currency. None of them is linked to the thing that triggers regulatory consequences, which is the fund-level NAV error.

The CSSF thresholds give you the anchor. The Circular provides for materiality thresholds in relation to Money Market Funds (0.2%), UCITS (1% for equity funds, 0.5% for fixed income and mixed funds). The clause that matters most for reconciliation design is the aggregation rule: significant NAV calculation errors are to be understood not only as isolated calculation errors which have a significant impact on the NAV but also as simultaneous or successive calculation errors which have not been treated and were each below the tolerance threshold but reachreachThe number of unique people exposed to your message in a given period. Unlike impressions, reach counts each person once, no matter how often they see it.View full definition → it when added together. A pile of small unresolved breaks is a regulatory event in waiting.

So set two numbers per fund:

• Single-break escalation: any break whose potential NAV impact exceeds 10% of the fund's threshold goes to a named owner the same day.
• Aggregate gate: NAV is not released while the summed absolute NAV impact of open position and price breaks exceeds 25% of the threshold.

The 10% and 25% levels are my design choices. Set your own, but derive them from the threshold rather than from a vendor screen.

Worked example (hypothetical, arithmetic only). Take a €500m fixed income UCITS. Its threshold is 0.5%, or €2.5m. Single-break escalation sits at €250k and the aggregate gate at €625k. A €20m bond position mispriced by one point near par is a €200k break. That is 8% of threshold, so no single-break alarm fires. Four of them open at the same time come to €800k and close the gate. Twelve of them, left to age for a week, come to €2.4m, close enough to the threshold that one more break makes it a notifiable error. Systematic price bias is the less obvious risk. Bloomberg, which sells both of the price products concerned (so read its figures as vendor analysis), found that before a methodology change its trade reference and evaluated prices for a corporate bond universe showed 4.5 to 5 cents absolute difference between the products, falling to (or just below) 2 cents by the end of July. Apply a 5-cent bias to a €500m book priced near par and you get €250k, a tenth of the fund's threshold, before a single genuine error has occurred.

Step 3: Run the gate before the administrator strikes NAV

Put the reconciliation upstream of the NAV calculation. Send the administrator your reconciled position and price file, then reconcile its output back to that file. Don't check its NAV against your records the next morning. This changes the timetable: custodian files, vendor prices and IBOR positions all have to land, match and clear the gate before the administrator's cut-off.

T+1 makes this harder. On 20 July 2026, the European Securities and Markets Authority said that 2026 is a critical year for firms to finalise preparations and highlighted 7 December 2026 as the first regulatory milestone for allocation and confirmation processes. The EU T+1 Industry Committee's handbook tells asset managers to align legal fund document updates, pricing, NAV calculation, and reconciliation processes with the new settlement cycle. If your morning gate depends on an overnight batch that already finishes late, that batch is now on the critical path.

Step 4: Challenge every price with a second source and keep the evidence

A price that passes a staleness check has still not been validated. Run every evaluated price against a challenger. Route divergences above your back-solved tolerance to a pricing analyst, and log the decision with its evidence. Thebenchmarking of golden-source pricing against challengers should be periodic and data-drivendata-drivenAn approach where decisions are systematically informed by data analysis rather than intuition alone.View full definition →, not a one-off vendor selection exercise.

Administrator-run benchmarks help, with a caveat. SS&C, which is itself a fund administrator and technology vendor, is preparing a 2026 study that evaluates several leading pricing providers, including Bloomberg BVAL, ICE Data Services, JP Morgan PricingDirect, LSEG, MarketAxess, S&P Global and Trumid. SS&C says the study can support compliance with SEC Rule 2a-5 by helping firms evidence effective oversight of pricing services used in regulated funds. Use it as one input and test it against your own holdings and trade prints.

The cost of weak price challenge is now on public record. On 25 February 2026, the SEC announced settled charges against Madison Capital Funding LLC, an Illinois-based formerly registered investment adviser, for selling loans to private fund clients ("the Funds") without reasonably determining whether those trades were at fair market value. The firm repaid approximately $5 million plus interest to affected funds, agreed to a cease-and-desist order, was censured, and must pay a $900,000 civil penalty. The conduct dates back to 2020, but the lesson holds today: a valuation policy that leaves adjustments to discretion, with no record of the challenge, does not survive an examination.

Step 5: Pay down identifier debt before anything else

Most position breaks are not real economic differences. They come from the same security carrying an ISIN at the custodian, a SEDOL at the vendor and an internal ID in the IBOR, or from one account mapped differently across three systems. Invesco's T+1 work shows the payoff. For the US migration, Invesco began preparations 18-24 months ahead of the US go-live, standing up a cross-functional project focused on automation, affirmation rates and data integrity. The single biggest operational win was consolidating affirmation IDs. The EU T+1 Industry Committee's write-up reaches a conclusion that applies directly to NAV reconciliation: legacy ID mesh and reconciliation debt become critical-path items under T+1.

The wider industry is starting from behind. According to the Committee's second readiness survey, sixty-one per cent of asset managers now have a formal implementation plan in place, up sharply on six months ago, though asset managers still trail the most prepared segmentssegmentsDividing a market into distinct groups of customers who share similar needs, characteristics or behaviours, so each group can be served with a tailored approach.View full definition →.

Step 6: Report breaks to the board in money, not counts

A ManCo or fund board can't act on "347 open breaks". It can act on "open breaks on Fund X total 18% of its NAV error threshold, the oldest is nine days old, and it belongs to the custodian". Express every open break as potential NAV impact against the fund's threshold, age it, and name its owner. This is how you turnpractical data checks and controls into something a conducting officer will sign off.

Why do custodian and administrator reconciliations still fail?

They fail because the controls measure agreement between systems, and agreement says nothing about whether the numbers are correct or whether anyone owns the gap. Here are the specific failure modes:

Circular matching. If you reconcile your IBOR to the administrator, and the administrator built its book from the same custodian file and the same vendor price, a clean match proves nothing. Reconcile quantity to the custodian and price to an independent challenger.

Inherited tolerances. A 1% price tolerance on an equity fund with a 1% NAV threshold can hide most of a material error on a concentrated position. Re-derive tolerances fund by fund using Step 2.

Letting breaks age below the radar. The CSSF's aggregation clause means a break aged for a week and a break that is large are both problems. Once an error is significant, the clock runs: within four to eight weeks of the date of detection, using the notification form on the CSSF website. If total compensation exceeds EUR 50,000, or a single investor is owed more than EUR 5,000, the fund's auditor must issue a special report to the CSSF within three months of the notification.

Assuming the contract moves the liability. Your administration agreement may give you recourse against the administrator, but regulators look to the manager. Correction costs also stay off the fund: the cost of the correction, staff time, legal advice and the auditor's special report included, is never charged to the fund.

Testing T+1 dry runs on synthetic datasynthetic dataArtificially generated data that mimics the statistical patterns of real data, used when real data is scarce, sensitive or expensive to collect.View full definition →. Synthetic positions often break the joins between securities, accounts and prices that reconciliation depends on. The New Stack recently reported that only 34% of practitioners trust the referential integrity of synthetic data. Use masked production snapshots for gate testing.

Treating the morning gate as an operations project. The cut-off timings, the escalation thresholds and the price override hierarchy are governance decisions. Put them in the valuation policy and get the board to approve them.

What to do on monday

• Pull each fund's NAV error threshold from its prospectus or valuation policy, and compute the 10% single-break and 25% aggregate levels for your five largest funds.
• Rerun last Friday's open breaks as potential NAV impact against those levels, and see which funds would have failed the gate.
• Write the field-authority list from Step 1 on a single page and get the heads of operations, valuation and fund administration oversight to sign it.
• Count how many distinct identifiers your top 50 holdings carry across custodian, administrator, vendor and IBOR, and start the cross-reference cleanup with the worst ten.
• Ask your primary pricing vendor and your administrator for their evaluated prices on the same 100 bonds for the same date, and measure the average difference in cents.
• MapMapUsing software to automate repetitive marketing tasks and campaigns, enabling personalisation at scale across channels like email, web, and social.View full definition → your current custodian-file arrival and administrator cut-off times against a T+1 timetable, and flag every batch that finishes after 06:00.

The cheapest NAV error is the one your own gate catches before the administrator strikes the price. Build the gate using your fund's threshold, report it in money, and the compensation calculations under Circular 24/856 or a Rule 2a-5 examination become a file you already have.

The full course on this sector:Data in Asset & Wealth Management.