--- title: "How can fund administrators speed up NAV production and oversight without losing control? | Next Matter" description: "How NAV production and oversight is orchestrated end to end: pulled inputs, routed breaks, maker-checker (four-eyes) sign-off and a complete, timestamped audit trail of every NAV cycle." lang: en json-ld: | [ { "@context": "https://schema.org", "@graph": [ { "@type": "Organization", "@id": "https://nextmatter.com/#organization", "name": "Next Matter", "legalName": "Daizy NM Limited", "url": "https://nextmatter.com", "logo": "https://nextmatter.com/__l5e/assets-v1/aab354c2-e169-46fe-8e9b-0e78438471d3/nextmatter-logo.svg", "description": "Next Matter is the orchestration platform for regulated financial operations - purpose-built for asset managers, fund administrators, and wealth and wealthtech firms, not a generic workflow tool - combining AI agents, your existing systems and human approvals with governance and a complete audit trail.", "sameAs": [ "https://www.linkedin.com/company/nextmatter", "https://www.daizy.com" ] }, { "@type": "WebSite", "@id": "https://nextmatter.com/#website", "url": "https://nextmatter.com", "name": "Next Matter", "publisher": { "@id": "https://nextmatter.com/#organization" }, "inLanguage": "en" } ] }, { "@context": "https://schema.org", "@type": "QAPage", "url": "https://nextmatter.com/answers/speed-up-nav-production-and-oversight", "inLanguage": "en", "datePublished": "2026-07-01", "dateModified": "2026-08-11", "author": { "@type": "Organization", "name": "Next Matter", "legalName": "Daizy NM Limited", "url": "https://nextmatter.com", "logo": "https://nextmatter.com/favicon.ico" }, "publisher": { "@type": "Organization", "name": "Next Matter", "legalName": "Daizy NM Limited", "url": "https://nextmatter.com", "logo": "https://nextmatter.com/favicon.ico" }, "mainEntity": { "@type": "Question", "name": "How can fund administrators speed up NAV production and oversight without losing control?", "answerCount": 1, "acceptedAnswer": { "@type": "Answer", "text": "NAV cycles rarely slow down in the calculation itself. They slow down in the work around it: chasing inputs from custodians, administrators and pricing vendors, reconciling positions and prices, resolving breaks, and then evidencing that a qualified second person reviewed and approved the result. In most fund administrators that work happens in spreadsheets, shared inboxes and chat, which is why a cycle that should take hours takes days, and why the audit trail has to be reassembled after the fact. Next Matter runs NAV production and oversight as one governed, orchestrated process. Inputs are pulled from your source systems through native connectors and a typed API on a schedule, tolerance and completeness checks run automatically, exceptions and reconciliation breaks are raised as structured items and routed to the reviewer who owns that fund or asset class with the full context attached, and the NAV approval step enforces maker-checker (four-eyes) control: the person who prepared or last edited the NAV cannot be the person who signs it off. Every stage writes to a timestamped, immutable audit trail. Nothing is replaced. Your fund accounting system stays the book of record and your pricing vendors stay the price source. Next Matter is the orchestration layer above them that sequences the cycle, holds the state, enforces the controls and produces the evidence pack. Ocorian runs global fund and investor operations on this model with 300+ specialists. A NAV cycle in Next Matter runs in five stages: input assembly from ledgers, custodians and pricing feeds; automated validation against completeness and tolerance rules; exception routing to the accountable reviewer with maker-checker roles assigned; maker-checker (four-eyes) NAV sign-off where preparer and approver must be different identities and failed checks return to the maker with a mandatory reason; and release with an audit-trail evidence pack containing timestamps, identities, source payloads, exceptions raised, resolutions, overrides and approvals. Time is compressed by removing manual input chasing, manual re-keying and reconciliation in spreadsheets, email-based break resolution, and after-the-fact audit trail assembly.", "url": "https://nextmatter.com/answers/speed-up-nav-production-and-oversight", "dateCreated": "2026-07-01", "author": { "@type": "Organization", "name": "Next Matter", "legalName": "Daizy NM Limited", "url": "https://nextmatter.com", "logo": "https://nextmatter.com/favicon.ico" }, "upvoteCount": 0 } }, "isPartOf": { "@id": "https://nextmatter.com/#website" } }, { "@context": "https://schema.org", "@graph": [ { "@type": "BreadcrumbList", "itemListElement": [ { "@type": "ListItem", "position": 1, "name": "Home", "item": "https://nextmatter.com" }, { "@type": "ListItem", "position": 2, "name": "Answers", "item": "https://nextmatter.com/answers" }, { "@type": "ListItem", "position": 3, "name": "How can fund administrators speed up NAV production and oversight without losing control?", "item": "https://nextmatter.com/answers/speed-up-nav-production-and-oversight" } ] } ] } ] --- [![Next Matter Logo](/__l5e/assets-v1/aab354c2-e169-46fe-8e9b-0e78438471d3/nextmatter-logo.svg)](/) - [Solutions](/solutions) [ grid\_view Solutions Overview Personas, capabilities, and proof ](/solutions)[ smart\_toy AI Orchestration Coordinate agents across your stack ](/solutions/ai-orchestration)[ library\_books Workflow Library Remix production-ready workflows ](/remix) Case Studies [ ![Ocorian](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da4e8_Ocorian_trustbar.svg) Ocorian 1,800 Employees • Fund Administrator ](/case-studies/ocorian)[ ![Trade Republic](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da4e9_traderpublic_trustbar.svg) Trade Republic 10M Customers • Online Trading Platform ](/case-studies/trade-republic)[ ![b2Venture](/__l5e/assets-v1/40232f5e-b66d-45f6-8d04-8be40304d172/b2venture-logo.png) b2Venture $800mn AUM • Venture Capital Firm ](/case-studies/b2venture)[ ![Swan](/__l5e/assets-v1/ef4919d4-3042-430f-b1a2-10b7da14c889/swan-logo.webp#lh=1500x401) Swan BaaS leader • Embedded Banking Platform ](/case-studies/swan) - [Platform](/platform) [ hub Platform Overview Built for Fund Operations ](/platform)[ build Workflow Builder Build long-running orchestrations ](/workflow-builder)[ smart\_toy AI & Automation Agents, models and guardrails ](/ai-and-automation)[ extension Integrations Core Ledger & Ecosystem Connectivity ](/integrations)[ verified\_user Governance & Audit Approvals and a full audit trail ](/governance-and-audit)[ shield Security SOC 2, ISO 27001, data residency ](/security) - Resources [ forum Ask a Technical Question Chat with the docs AI assistant ](https://help.nextmatter.com/docs/integrate-across-tools?assistant)[ campaign Opinions Perspectives from our team ](/opinions) [Sign in](https://app.nextmatter.com/login) [Talk to us](/book-a-demo) Answer Q.29 of 50 # How can fund administrators speed up NAV production and oversight without losing control? How NAV production and oversight is orchestrated end to end: pulled inputs, routed breaks, maker-checker (four-eyes) sign-off and a complete, timestamped audit trail of every NAV cycle. By the Next Matter team Updated 11 August 2026 2 min read NAV cycles rarely slow down in the calculation itself. They slow down in the work around it: chasing inputs from custodians, administrators and pricing vendors, reconciling positions and prices, resolving breaks, and then evidencing that a qualified second person reviewed and approved the result. In most fund administrators that work happens in spreadsheets, shared inboxes and chat, which is why a cycle that should take hours takes days, and why the audit trail has to be reassembled after the fact. Next Matter runs NAV production and oversight as one governed, orchestrated process. Inputs are pulled from your source systems through native connectors and a typed API on a schedule, tolerance and completeness checks run automatically, exceptions and reconciliation breaks are raised as structured items and routed to the reviewer who owns that fund or asset class with the full context attached, and the NAV approval step enforces maker-checker (four-eyes) control: the person who prepared or last edited the NAV cannot be the person who signs it off. Every stage writes to a timestamped, immutable audit trail. Nothing is replaced. Your fund accounting system stays the book of record and your pricing vendors stay the price source. Next Matter is the orchestration layer above them that sequences the cycle, holds the state, enforces the controls and produces the evidence pack. Ocorian runs global fund and investor operations on this model with 300+ specialists. Mechanics ## How a NAV cycle is orchestrated, stage by stage Each stage below is a step in a single workflow instance. The instance holds the state of the NAV cycle, so at any moment an operations lead can see which inputs have landed, which checks passed, which breaks are open, who owns them, and whether the NAV is with the maker or the checker. Stage 01 · Input assembly ### Pull inputs from ledgers, custodians and pricing feeds The cycle starts on a schedule (daily, weekly, month-end) rather than on someone remembering. Next Matter calls your fund accounting or ledger system, custodian and administrator files, and pricing and FX feeds through native connectors and a typed REST API; file-based sources land through a monitored SFTP or secure upload step. Each pull is recorded with the endpoint or file name, the request parameters, the response payload, a UTC timestamp and the system identity that made the call. A source that does not respond, returns partial data or delivers a stale as-of date does not silently pass: it raises a structured exception at this stage, before valuation work begins. Stage 02 · Validation ### Automated completeness and tolerance checks Before anything reaches a human, the workflow runs the deterministic checks a NAV controller would otherwise run by hand: position counts and holdings reconciled between ledger and custodian, every security priced with a price of the correct as-of date, price movement inside a configured tolerance band against the prior valuation point, cash reconciled to custodian statements, accruals and fee calculations present, and the total NAV and NAV per unit movement inside its tolerance versus the prior cycle. Checks that pass are recorded as passed, with their inputs, so the review is evidenced rather than assumed. Stage 03 · Exception routing ### Breaks go to the right reviewer, with context attached A failed check becomes a structured exception, not an email. It is routed by rule to the accountable owner (by fund, asset class, jurisdiction or materiality) and lands in that person's queue with the evidence already assembled: the two values that disagree, both source records, the tolerance that was breached, the history of the same break on prior cycles, and the deadline it must clear to keep the cycle on schedule. The reviewer resolves it in place, with a mandatory categorisation and free-text reason, or escalates it. Escalation and time-based SLA breaches route upward automatically. The NAV cannot progress to sign-off while a material exception is open, and the resolution, the resolver's identity and the timestamps stay attached to the cycle. Stage 04 · Maker-checker sign-off ### Four-eyes NAV approval, enforced by the platform NAV approval is where maker-checker (also called four-eyes) is enforced in software rather than trusted to process discipline. - **The maker** is the NAV preparer or fund accountant who assembled the pack, cleared the exceptions and submitted the NAV. Their identity, the version they submitted and the submission timestamp are recorded. - **The checker** is a NAV reviewer, oversight manager or valuation committee member holding the approver role for that fund. The platform blocks the maker and the checker from being the same identity, and blocks anyone without the role from approving. - **If the check fails,** the checker rejects with a mandatory reason. The workflow returns to the maker with the rejection reason attached, the maker re-works and resubmits, and the second submission starts a fresh approval. Both the rejected and approved versions remain in the record. - **If it is escalated,** for example a material valuation judgement or a tolerance override, the workflow routes to a further approver (head of valuations, valuation committee, or a second checker) before release. Escalation thresholds are configured per fund. - **Overrides are never silent.** Approving over an open tolerance breach requires an explicit override with a written justification, and is flagged in the evidence pack rather than buried in a log. Stage 05 · Release and evidence ### Distribution and an audit trail that is already complete On approval the workflow writes the NAV back to the systems that need it, publishes the investor-facing statements or files, and notifies the depositary, transfer agent and downstream reporting processes. Because the audit trail was captured as the work happened, the evidence pack for that cycle exists at the moment of release. There is no reconstruction exercise later, and no one, including administrators, can retroactively edit the recorded history of the cycle. Evidence ## What the audit trail captures at each stage Timestamps High-precision UTC timestamps on every input pull, check, exception, comment, approval and release, so cycle duration and SLA adherence are provable, not estimated. Identities The authenticated user, service account or AI agent behind each action, with the role they held at the time, and the maker and checker recorded distinctly at sign-off. Inputs and payloads The exact request and response payloads or files received from each ledger, custodian and pricing source, retained with the cycle rather than expiring in a developer log. Exceptions raised Every break, which rule or tolerance triggered it, its materiality, who it was routed to, and how long it sat before resolution. Approvals and rejections Each maker submission and checker decision, including rejected versions and the reasons given, so the full four-eyes history of the NAV is visible, not just the final state. Overrides Any tolerance override or manual adjustment, with the mandatory written justification and the approver who accepted it, surfaced in the evidence pack for the cycle. Worked example ## One month-end NAV cycle, with a break caught in flight A closed-ended fund with listed and unlisted holdings strikes a month-end NAV. The example below is a typical shape of a governed cycle, not a guaranteed timeline. 1. 1 The scheduled trigger fires after the valuation point. Next Matter pulls trial balance and positions from the fund accounting system, the custodian position and cash file, vendor prices and FX rates, and the latest unlisted valuations from the data room. 2. 2 Validation runs. Positions and cash reconcile, all listed securities are priced with the correct as-of date, but one holding moved 11 percent against a configured 5 percent tolerance, and one unlisted position has no refreshed valuation for the quarter. 3. 3 Two exceptions are raised and routed. The price break goes to the fund accountant who owns that portfolio, with both prices, the vendor record and the prior three valuation points attached. The stale unlisted valuation escalates straight to the valuation oversight manager. 4. 4 The accountant identifies a corporate action the vendor applied a day late, resolves the break by taking the corrected price, and records the category and reason. The oversight manager attaches the signed valuation memo for the unlisted holding. Both resolutions are timestamped against the cycle. 5. 5 With no material exception open, the accountant (the maker) submits the NAV pack. The NAV reviewer (the checker) opens it, sees the two exceptions and their resolutions in line, queries one, receives an answer in the same thread, and approves. The platform would have refused the approval had the maker attempted it. 6. 6 On approval the NAV is written back, investor statements are generated, and the depositary and transfer agent are notified. The evidence pack for the cycle, every input, check, break, resolution, identity and approval, is complete at the moment of release. Where the time goes ## What "compressing the cycle" actually removes The saving is not a faster calculation. It is the removal of specific manual steps that sit between calculation and sign-off. Chasing and collecting inputs Removed: scheduled connector pulls and monitored file drops replace emails to custodians and manual downloads, and a missing input raises itself instead of being noticed hours later. Re-keying and spreadsheet reconciliation Removed: comparison against tolerance rules runs on the pulled data, so the controller reviews a list of exceptions rather than building the comparison first. Email and chat break resolution Removed: breaks are routed with context to a named owner with a deadline, so the dead time is the reviewer's decision, not the round trips required to find the right reviewer and assemble what they need. Sign-off coordination Removed: the checker is notified the moment the maker submits and approves in the same view as the exception history, instead of a pack being emailed and a reply awaited. Assembling the audit trail afterwards Removed entirely: the audit trail is a by-product of the cycle running, so the days normally spent gathering evidence for auditors, depositaries or the regulator become a query against the record. Keep reading ## Related pages [All answers →](/answers) [Related Operational intelligence](/operational-intelligence) [Related Exception handling](/exception-handling) [Related Governance & audit](/governance-and-audit) [Related Book a demo ](/book-a-demo) On this answer edit\_calendar Updated 11 August 2026 groups Author The Next Matter team verified Grounded in Real customers & capabilities ## See it on your process. 30 minutes with the solutions team on a real fund or client operation. [Book a demo](/book-a-demo) [Browse all answers](/answers) ![Next Matter](/__l5e/assets-v1/aab354c2-e169-46fe-8e9b-0e78438471d3/nextmatter-logo.svg) The agentic operating system for modern financial services. A Daizy company. [](https://www.linkedin.com/company/nextmatter) Case studies - [Ocorian](/case-studies/ocorian) - [Trade Republic](/case-studies/trade-republic) - [Swan](/case-studies/swan) - [b2Venture](/case-studies/b2venture) - [All case studies](/case-studies) Solutions - [Solutions overview](/solutions) - [AI Orchestration](/solutions/ai-orchestration) - [Workflow library](/remix) Platform - [Platform overview](/platform) - [Workflow Builder](/workflow-builder) - [AI & Automation](/ai-and-automation) - [Integrations](/integrations) - [Governance & Audit](/governance-and-audit) - [Security](/security) - [System status](https://status.nextmatter.com/) Capabilities - [AI Financial Reporting](/ai-financial-reporting) - [Operational Intelligence](/operational-intelligence) - [Exception Handling](/exception-handling) - [Team Interfaces](/team-interfaces) - [Guest Interfaces](/guest-interfaces) - [Manager Dashboard](/manager-dashboard) - [Builder Toolbox](/builder-toolbox) Company - [About](/about) - [Careers](/careers) - [Opinions](/opinions) - [Answers](/answers) - [Documentation](https://help.nextmatter.com/docs/integrate-across-tools) - [Ask a Technical Question](https://help.nextmatter.com/docs/integrate-across-tools?assistant) Certified Secure [![AICPA SOC 2 for Service Organizations](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da55f_logo_SOC2.svg)](https://app.drata.com/trust/d62cb1a1-96df-4741-8058-97ecbc4ff345/) [![GDPR compliant](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69a7f71677d8045f0f2da561_logo_GDPR.svg)](https://app.drata.com/trust/d62cb1a1-96df-4741-8058-97ecbc4ff345/) [![SOC 2 Type 2 compliant 2025](https://cdn.prod.website-files.com/69a7f71677d8045f0f2d982a/69eb389eff4de1586e1d2f14_Daizy%20SOC%202%20Type%202.png)](https://app.drata.com/trust/d62cb1a1-96df-4741-8058-97ecbc4ff345/) © 2026 Daizy NM Ltd. All rights reserved. A Daizy company [Terms of Service](/terms-of-service) [Privacy Policy](/privacy-policy) [Data Processing Agreement](/data-processing-agreement) Solutions - [Solutions Overview](/solutions) - [AI Orchestration](/solutions/ai-orchestration) - [Workflow Library](/remix) Case Studies - [Ocorian](/case-studies/ocorian) - [Trade Republic](/case-studies/trade-republic) - [b2Venture](/case-studies/b2venture) - [Swan](/case-studies/swan) Platform - [Platform Overview](/platform) - [Workflow Builder](/workflow-builder) - [AI & Automation](/ai-and-automation) - [Integrations](/integrations) - [Governance & Audit](/governance-and-audit) - [Security](/security) Resources - [Ask a Technical Question](https://help.nextmatter.com/docs/integrate-across-tools?assistant) - [Opinions](/opinions) [Sign in](https://app.nextmatter.com/login) [Talk to us](/book-a-demo)