Overcoming the Challenges of ABOR and NAV Oversight
ABOR oversight is the independent checking of the accounting book of record (ABOR) and the NAVs that fund administrators produce from it. Investment managers and Management Companies (ManCo’s) that outsource NAV production still own the result. Regulators expect them to show, every day, that administrator outputs were checked, challenged and approved. As the fund landscape diversifies across fund vehicles, administrators and jurisdictions, doing this well has become one of the harder operational problems in asset management.
The need for NAV oversight
Outsourcing NAV production transfers the work, not the accountability. The investment manager and the ManCo remain responsible for every price released to market.
The operating reality for most global managers looks like this:
- Several third-party administrators, each with its own formats and processes
- A mix of internal and outsourced NAV production
- Daily-dealing funds
- Tight release timelines that leave little room for manual review
In this environment, oversight has a clear job. It must validate administrator outputs, identify material NAV movements, challenge exceptions, and evidence each review and approval. Above all, it must be independent and defensible in front of a regulator.
The challenges of NAV oversight
Most current oversight models were built for a smaller, simpler fund range. They struggle once volumes and/or administrator counts grow.
Manual tools do not scale
Oversight often relies on spreadsheet tolerance checks, email-based challenge and manual tracking. Reporting is fragmented, so there is no single view of what was checked, what broke and who approved it. Each new administrator or jurisdiction adds more of the same manual work.
Shadow NAV is rarely the answer
Running a full NAV (shadow accounting) is one way to check an administrator, but it is heavy to operate in a daily environment and costly to maintain globally. For oversight purposes it is often unnecessary. What managers need is independent validation of the administrator’s output, not always a second NAV.
Controls must vary by jurisdiction, administrator and fundOversight expectations differ by jurisdiction, by administrator and by fund structure. Governance teams expect different evidence. A fixed rule set cannot cover this range; the controls themselves must be configurable.
Volume and time pressure
Daily cycles can involve thousands of share classes. Reviewers must find the few movements that matter, investigate them and sign off before the release deadline.
How NeoXam automates NAV oversight
NeoXam replaces manual, fragmented checks with a systematic oversight model: consistent across administrators, tolerance-driven, exception-based and auditable. It complements existing controls rather than duplicating the administrator’s work.
A connected operating model
Three components work together:
- NeoXam DataHub gives the enterprise view of all BORs: consolidated status, global NAV visibility and drill-down to supporting evidence.
- NeoXam Aro runs the oversight controls: tolerance checks, anomaly detection and exception management, with a stored history of every result.
- NeoXam Workflow operationalises governance through a digital oversight checklist with automated step completion.
Oversight, not just reconciliation
Aro independently challenges administrator outputs. It validates across sources, comparing administrator, investment manager and third-party data rather than performing a NAV reconciliation alone, and flags anomalies within a single administrator file using reasonability checks. Risk-based prioritisation keeps reviewers focused on what matters across high-volume daily cycles.
Built for multi-administrator, multi-jurisdiction fund ranges
Aro accepts different administrator formats and applies the same control logic to all of them, giving one oversight framework. Controls are configurable by fund, administrator and jurisdiction, and can be saved as reusable templates that evolve with the operating model.
NAV oversight controls that reflect daily practice
Typical controls include:
- NAV publication check: confirms every price was released, with reference data explaining anomalies
- Fund NAV attribution: tests daily movements against income, P&L and portfolio drivers
- NAVs Plausibility Checks: tests on share class movement, main class deviation, benchmark deviation, hedge class deviation
- Share class divergence: compares classes against the lead class to catch valuation or fee issues early
- Hedge ratio monitoring: tracks ratios against agreed ranges and escalates sustained breaches
- Swing pricing calculation and verification: rebuilds the expected swing from transfer agent flows and compares it with the administrator
- Master–feeder tie-out: matches master NAV against feeder holdings on price, quantity and NAV
- Management fee oversight: recalculates fees from reference data and compares them with the administrator
- Outsourced reconciliation oversight: applies checks to third-party reconciliation outputs in line with the manager’s risk tolerance
- Transaction Fees: recalculates transaction fees and compares to trading partners
- Tax & Withholding: allows users to configure the tax and withholding tax and ensure the fund administrator calculations are correct
Evidence regulators can rely on
Every exception moves through a defined lifecycle: identification, assignment, investigation, commentary and approval. This creates a provable oversight history, including control execution, review and approval tracking, and monitoring of recurring issues.
The result
Managers get consistent ABOR oversight across administrators and jurisdictions, less manual review, faster resolution of NAV issues and a clear audit trail. Investment manager, ManCo and governance teams share one central view of fund administrator oversight, and the model scales across large daily fund ranges.
Want to explore further with a demo?
What is ABOR oversight?
ABOR oversight is the independent checking of the accounting book of record and the NAVs that fund administrators produce from it. Investment managers and ManCos that outsource NAV production must show that administrator outputs were checked, challenged and approved before prices are released.
What is the difference between ABOR and IBOR?
The accounting book of record (ABOR) is the official record used to strike the NAV and produce fund accounts. The investment book of record (IBOR) is the front-office view of positions and cash that portfolio managers use to make investment decisions during the day.
Do you need a shadow NAV to oversee a fund administrator?
Not always. A full shadow NAV is heavy to run daily and costly to maintain globally. For oversight, independent validation of the administrator’s output, using tolerance checks, cross-source comparison and reasonability checks, is usually enough.
What checks does NAV oversight include?
Typical controls include NAV publication checks, fund NAV attribution, plausibility checks on share class and benchmark movements, share class divergence, hedge ratio monitoring, swing pricing verification, master–feeder tie-out and management fee recalculation.
How do you evidence NAV oversight to a regulator?
By giving every exception a defined lifecycle, from identification and assignment to investigation, commentary and approval, and keeping a history of control execution, review and sign-off.
