Real-time NAV calculation is the ability to produce an accurate, validated net asset value continuously throughout the day rather than waiting for an overnight batch cycle. Under regulatory frameworks like DORA, real-time calculations become a primary point of investor trust and a single workflow whose failure can create reputational, regulatory and financial consequences within hours.

Legacy fund accounting platforms weren’t built for this expectation. They run batch processes, surface errors after the fact and depend on shadow NAV procedures that are often manual and slow.

Modern resilience expectations require a fundamentally different architecture: real-time validation, a true accounting-based contingency and an architecture where continuity is designed from the ground up.

What’s at Stake When a NAV Fails

A delayed or inaccurate NAV is one of the few operational events in fund administration that creates immediate consequences across regulators, distributors, investors and the business at the same time. Even a short delay can trigger subscription and redemption issues, force investor compensation and undermine confidence among investors and distribution partners that can take far longer to rebuild than the disruption itself.

The real-world consequences typically include:

  • Investor compensation for trades executed on incorrect or delayed NAVs

  • Audit and regulatory fines where NAV failures point to control weaknesses

  • Mandatory incident reporting under operational resilience frameworks like DORA

  • Reputational damage that affects investor confidence and client retention

  • Loss of trust with distributors and platform partners who depend on timely, reliable NAV delivery

  • Operational disruption as teams divert from normal work to remediate, restate and report

NAV failure is also one of the few operational events that becomes immediately visible to investors and distribution networks alike, which is why it sits at the top of most asset servicers’ impact tolerance assessments.

Why Batch-Based NAV Processing Is a Risk

Batch-based NAV processing is risky because validation only happens at the end of the cycle, which means errors are discovered after they’ve already affected the published NAV. By the time an issue surfaces, subscriptions and redemptions may already have been processed, reports distributed and downstream systems updated.

The specific risks of batch NAV processing include:

  • Delayed detection of pricing, position or data-quality errors

  • Inability to validate NAV continuously throughout the day

  • Operational dependency on a single overnight processing window

  • Limited transparency into how errors propagated through the calculation process

  • No resilient fallback when a calculation cycle fails or data is incomplete

Real-time NAV processing changes this model entirely. Validation runs continuously as data arrives, allowing anomalies to be identified and addressed before NAV publication.

The architecture is event-driven rather than tied to overnight cycles, and independent contingency processing can be invoked immediately without waiting for the next batch window.

In this model, real-time NAV is not simply faster NAV production — it becomes a resilience mechanism designed to reduce operational impact before errors propagate downstream.

Real-Time vs. As-Of: Understanding the Difference

Real-time and as-of are often used interchangeably, but they describe different things and modern fund accounting platforms need both.

Real-time NAV: Real-time NAV means the system produces a current valuation continuously, reflecting every event including trades and pricing updates as they happen. The real-time view is always up-to-the-moment.

As-of NAV accuracy: As-of NAV accuracy means the system can reconstruct the exact NAV that existed at any prior point in time, including what was known at that point and what has since been corrected. The as-of view supports audit, restatement and regulatory evidence.

Both are essential.

Real-time supports operational decisions, intraday risk monitoring and continuous validation. As-of supports the audit trail, the regulator’s investigation and the auditor’s historical reconciliation. 

Modern fund accounting increasingly requires both capabilities, which requires a bitemporal accounting architecture such as FundGuard’s, where every record carries both an economic date and a system date. This is what makes both views possible from the same underlying dataset.

The Case for an Independent NAV Contingency

An independent NAV contingency is a separate accounting capability that can produce a valid NAV if the primary system becomes unavailable. The traditional approach to NAV continuity has relied on shadow NAV processes that are typically manual. The limitations of traditional shadow NAV approaches include:

  • Manual workflows that introduce human error and don’t scale under stress

  • Lagging validation that only catches issues after the primary NAV has already been struck

  • Shared dependencies on the same data feeds, infrastructure or workflows, allowing failures to propagate across both environments

  • Limited confidence in recoverability because the contingency process is not continuously exercised under production conditions

  • Insufficient evidence to satisfy operational resilience and impact tolerance testing requirements under frameworks such as DORA

  • During periods of market volatility, the ability to maintain continuous NAV operations becomes a competitive trust signal for both investors and distribution partners

Under DORA, asset managers and fund administrators must prove that critical functions, including NAV production, are resilient. A manual shadow NAV process built on the same infrastructure as the primary doesn’t meet this standard.

A genuine NAV contingency is architecturally independent, cloud-native, continuously validated and capable of operating in parallel with the primary accounting environment.

Because it runs continuously rather than existing only as a dormant backup process, it can assume NAV production immediately if the primary system becomes unavailable.

How FundGuard’s Contingent NAV Works

FundGuard provides a cloud-native, automated shadow NAV that runs continuously alongside the primary accounting system and can be invoked if the primary fails. It works through five integrated capabilities:

  • Real-time NAV calculation with no batch cycles: Positions, prices, cash and corporate actions are processed as events arrive, enabling ongoing NAV validation throughout the day

  • Cloud-native, architecturally independent infrastructure: The contingency runs on separate infrastructure from the client’s primary system, so a failure in the primary doesn’t take the contingency with it, reducing the risk that infrastructure, workflow or data failures propagate across both environments

  • Continuous validation against the primary: The two NAVs are compared in real time allowing discrepancies to be identified and investigated before they become operational or regulatory events

  • Automated invocation if the primary fails: If the primary accounting system becomes unavailable, the contingent NAV is ready to assume NAV production without manual reconstruction or delayed recovery procedures

  • Continuous testing and evidenced resilience: Because the contingent environment runs continuously under live conditions, it produces ongoing operational evidence that supports resilience testing, auditability and DORA-style impact tolerance requirements

Example: Ultimus Fund Solutions

Ultimus Fund Solutions deployed FundGuard’s Contingent NAV after clients requested additional daily oversight and an independent NAV contingency capability. FundGuard’s cloud-native architecture enabled Ultimus to implement a continuously operating contingent NAV environment that supports real-time validation and provides an independent accounting capability if the primary accounting platform becomes unavailable.

The deployment reflects a broader shift in operational resilience expectations under frameworks such as DORA: moving beyond static recovery plans and manual backup procedures toward resilient-by-design operations, where critical functions like NAV production are continuously validated, actively tested and operationally ready under a range of disruption scenarios.

From Compliance Checkbox to Competitive Advantage: NAV Resilience Under DORA

DORA is the EU regulation that requires financial entities to ensure their critical ICT functions remain available, accurate and recoverable under disruption. NAV production is a critical function for asset managers and fund administrators, which puts it directly in scope.

DORA’s core requirements relevant to NAV:

  • ICT risk management mapping critical services like NAV to the systems and dependencies that support them

  • Incident management and reporting that can assess, classify and evidence incidents affecting NAV

  • Resilience testing with stress tests and failover validation that demonstrate continuity under stress scenarios

  • Third-party risk transparency across providers' platforms and operational dependencies

  • Data lineage and traceability needed to support reporting, investigation and supervisory review

Treating DORA as a competitive position means embedding resilience into daily operations, which means running real-time validation, maintaining a live independent NAV contingency and operational evidence that is produced continuously rather than reconstructed periodically for audit purposes.

The competitive advantage shows up in three key places:

  • Faster recovery when something does go wrong, because the contingency is already running rather than being constructed under pressure

  • Greater investor and distributor confidence because resilience is demonstrable rather than assumed

  • Improved audit readiness because the evidence is continuous rather than reconstructed after the fact

In a post-DORA world, resilience is moving from regulatory obligation to commercial differentiator.

Book a Demo

See how FundGuard delivers real-time NAV calculation with as-of accuracy and an independent, cloud-native NAV contingency that meets DORA’s resilience expectations. Request a demo and we’ll show you how it works for your environment.

Frequently Asked Questions

What is real-time NAV calculation?

Real-time NAV calculation is the continuous production of an accurate net asset value as positions, prices, cash movements and corporate actions are processed, rather than waiting for an overnight batch cycle. It allows errors and anomalies to be caught before NAV is published rather than after downstream activity has already occurred.

What is shadow NAV monitoring?

Shadow NAV monitoring is the practice of running a parallel NAV calculation alongside the primary accounting system to validate the primary NAV and provide a fallback if the primary fails. Traditional shadow NAV is often manual; modern contingent NAV architectures are cloud-native, automated and architecturally independent of the primary system.

How does DORA impact fund accounting?

DORA requires asset managers and fund administrators operating in or with the EU to demonstrate that critical ICT functions are resilient, testable and recoverable during disruption scenarios. This means moving toward continuous resilience testing, real-time validation and independent contingency capabilities.

What’s the difference between real-time NAV and as-of NAV accuracy?

Real-time NAV reflects current valuation at a given moment. As-of NAV accuracy means the system can reconstruct the exact NAV that existed at any historical point, including what was known at that point and what has since been corrected. Both are needed: real-time supports operational decisions, monitoring and continuous validation, while as-of supports audit and regulatory evidence.

Why is batch-based NAV processing a risk?

Batch processing means validation only happens at the end of the cycle, so errors are discovered after the NAV has been published and downstream processing has already occurred. It also creates a single point of failure — if the primary system goes down during the batch window, there’s no live fallback to produce the NAV continuously.

How does FundGuard’s Contingent NAV differ from traditional shadow NAV?

FundGuard’s Contingent NAV is cloud-native, architecturally independent of the primary accounting system, runs continuously rather than periodically and can be invoked automatically if the primary fails. Traditional shadow NAV processes are typically manual, run on extracted data and share dependencies with the primary, which limits both their independence and their ability to support continuous resilience testing.

Can a NAV contingency really be invoked without manual intervention?

Yes, if it’s designed to be. A genuine NAV contingency runs continuously against live data on independent infrastructure, which means the contingent NAV is already current at the moment the primary fails. There’s nothing to reconstruct. Manual contingencies, by contrast, require teams to assemble and validate a NAV under pressure. This adds operational pressure at precisely the point when teams need a controlled, reliable response.