Net Asset Value Calculation

Net asset value (NAV) calculation requires an investment company to compute NAV at least once daily, at a consistent time, using current market values for securities with readily available quotations and fair value (in good faith) for all other securities. Your job is to run a controlled daily pricing and accrual process that produces an auditable NAV used to price subscriptions and redemptions. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

Key takeaways:

• Calculate NAV at least once daily, using market quotes when available and fair value when they are not. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• Treat NAV as an operational control system: data feeds, valuation rules, review, exceptions, and sign-off.
• Retain artifacts that prove inputs, overrides, approvals, and the final NAV package for each calculation date.

For a CCO or GRC lead, the “net asset value calculation requirement” is rarely a pure accounting question. It is a pricing control requirement with direct investor impact: the NAV you publish becomes the price for share issuance and redemption, so weak controls can create dilution, mispricing, or unequal treatment across shareholders.

The rule expectation is straightforward: compute NAV at least once daily at a consistent time, valuing instruments with readily available market quotations at current market value, and valuing everything else at fair value in good faith. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1) Operationalizing it means building a repeatable daily runbook that covers data acquisition, classification of holdings by valuation method, accruals and liabilities, reconciliation to positions and cash, and a governed exception process for stale or missing prices.

This page translates the requirement into a practical implementation you can stand up quickly: who owns what, the minimum process steps, what evidence exam teams usually ask for, where errors happen, and how to structure a 30/60/90 execution plan that improves control without stalling operations.

Regulatory text

Requirement (operator view): Investment companies must calculate net asset value at least once daily using current market values for securities with readily available market quotations, and fair value for all other securities. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

What this means in practice

• You need a daily NAV “strike” at a consistent time (for example, end-of-day or another defined cut-off). (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• You must have a valuation hierarchy decision for each holding:
  • Market value for instruments with readily available quotations. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
  • Fair value in good faith for anything without readily available quotations (thinly traded instruments, private assets, disrupted markets, pricing outages). (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• NAV must incorporate the full balance sheet reality for the fund: portfolio holdings, accrued income, liabilities, and shares outstanding so the per-share price is correct for subscriptions/redemptions. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

Plain-English interpretation (what you must be able to prove)

You must be able to show, for each NAV date:

1. You struck NAV on schedule (at least daily, consistent time). (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
2. Every position had a documented price source (market quote or fair value method) and you can explain exceptions. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
3. Accruals and liabilities were included (fees, expenses, income accruals, payables). (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
4. Shares outstanding were accurate at the strike time so the NAV per share matches the dealing activity. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

Who it applies to (entities and operational context)

Entities

• Registered investment companies / funds that issue redeemable securities priced off NAV. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• Operationally, the requirement typically touches the adviser, fund accounting/administrator, and any pricing agents or data providers (all are relevant third parties because they affect an investor-facing price).

Operational contexts where this becomes “real”

• Daily dealing funds with end-of-day NAV.
• Portfolios holding instruments that frequently require fair value (private placements, complex structured products, restricted securities).
• Funds relying on third parties for pricing feeds, corporate actions, and reconciliation.

What you actually need to do (step-by-step)

Use this as a minimum viable NAV control workflow. Tailor roles to your model (in-house vs. administrator), but keep the control points.

1) Define the NAV strike and cut-offs

• Document the NAV calculation time and the data cut-off for trades, corporate actions, and cash movements.
• Confirm operational alignment: transfer agent (shares), custodian (positions/cash), and administrator/accounting all use the same cut-offs.

Control objective: consistent daily NAV timing. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

2) Build and maintain a valuation source matrix (by instrument type)

Create a matrix that maps each holding type to:

• Primary price source (exchange close, evaluated pricing, broker quote, model).
• Fallback source if primary is missing.
• Fair value trigger criteria (no quote, stale quote, market disruption, idiosyncratic events).
• Approval requirements for overrides and fair value determinations.

Control objective: market value where readily available; fair value otherwise. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

3) Daily price capture and exception triage

• Pull pricing inputs.
• Run automated checks for missing prices, stale prices, outliers, corporate actions anomalies.
• Route exceptions into a pricing exception log with owner, rationale, and required approval.

Common operator rule: no manual price override without (a) rationale, (b) approver, (c) timestamp, (d) source support.

4) Fair value process (good-faith valuation)

When fair value is required:

• Apply the documented methodology (model inputs, comparable securities, observable transactions).
• Record assumptions and input sources.
• Obtain the required approvals (often valuation committee or delegated approver) before NAV finalization.

Control objective: fair value in good faith for non-quoted instruments. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

5) Accrue income, fees, and expenses; book liabilities

• Accrue interest/dividends receivable as appropriate.
• Accrue management fees and fund expenses.
• Record payables/receivables and other liabilities.

Control objective: NAV reflects assets and liabilities, not just security prices. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

6) Reconcile positions, cash, and shares outstanding

• Reconcile portfolio holdings to custodian (position and cash breaks investigated and resolved or documented with timing items).
• Reconcile shares outstanding to transfer agent activity at the strike time (subscriptions/redemptions).

Control objective: the denominator (shares) is correct for the pricing used in dealing. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

7) Produce the NAV package and approvals

• Generate the NAV calculation report: total assets, total liabilities, net assets, NAV per share.
• Require reviewer sign-off (maker-checker) and escalation for material exceptions.

8) Publish NAV and retain the full audit trail

• Release NAV through controlled channels.
• Lock records for the day: inputs, logs, overrides, approvals, and final reports.

Where Daydream fits naturally If you struggle with “proof” (missing rationale for overrides, scattered emails for approvals, inconsistent exception logs), Daydream can act as the system of record for NAV controls: standardized checklists, exception workflows, and evidence retention mapped to 17 CFR § 270.22c-1 requirements. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

Required evidence and artifacts to retain

Retain artifacts per NAV date and in standing governance files.

Per NAV date (daily package)

• Final NAV report (assets, liabilities, shares, NAV per share).
• Price files (raw vendor feed outputs; timestamps; identifiers).
• Pricing exception log (missing/stale/outlier items) with resolutions.
• Manual override records (who/what/why/approver/support).
• Fair value worksheets/models and approval evidence.
• Reconciliation reports (positions, cash, corporate actions, shares outstanding).
• Maker-checker sign-off or approval ticket.

Standing governance artifacts

• NAV policy and procedures (strike time, cut-offs, roles, escalation).
• Valuation source matrix and fair value methodology documentation.
• Delegations of authority (who can approve overrides/fair value).
• Third-party oversight records for administrators/pricing providers (service descriptions, issue management, periodic reviews).

Common exam/audit questions and hangups

Expect questions that test whether NAV is controlled, not whether you can describe it.

• “Show me how you determine ‘readily available market quotations.’” Provide instrument classification rules and examples. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• “Where is fair value documented and who approves it?” Produce the fair value policy, daily worksheets, and approvals. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• “How do you detect and resolve stale/missing prices?” Show exception reports, thresholds/rules, and the resolution log.
• “How do you ensure shares outstanding are correct at strike time?” Show transfer agent reconciliation and cut-off alignment. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• “What happens when a key pricing third party has an outage?” Show fallback sources and escalation paths.

Frequent implementation mistakes (and how to avoid them)

1. Inconsistent cut-offs across teams.
   Fix: One documented strike schedule and cut-off table shared with transfer agent, custodian, and administrator.

2. Fair value triggers exist on paper but not in daily operations.
   Fix: Put triggers into automated exception checks and require disposition for every hit.

3. Manual overrides with weak rationale.
   Fix: Require structured fields: reason code, source support attachment, approver, timestamp.

4. Reconciliations happen after NAV is released.
   Fix: Define “must-clear” breaks vs “timing items allowed with documentation” before publication.

5. Third-party pricing/admin dependencies are not governed.
   Fix: Treat pricing/administrator as high-impact third parties: documented SLAs, issue logs, periodic oversight, and contingency processes.

Enforcement context and risk implications

No public enforcement cases were provided in the supplied sources, so this page does not list specific actions. Practically, regulators and auditors focus on NAV because it directly affects investor transactions. Weak NAV controls create exposure to investor harm (mispricing, dilution), operational errors, disclosure issues, and governance failures around fair value determinations. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

Practical 30/60/90-day execution plan

The goal is fast control uplift without redesigning your entire fund accounting stack.

First 30 days (stabilize and document)

• Write/refresh the NAV runbook: strike time, cut-offs, roles, escalation. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)
• Inventory price sources and create the first valuation source matrix draft.
• Implement a daily pricing exception log (even if it starts as a controlled spreadsheet with approvals).
• Identify where approvals occur today (email, chat, tickets) and standardize the approval path.

Days 31–60 (add governance and repeatability)

• Formalize fair value triggers and required documentation fields.
• Add maker-checker review requirements and define “no-go” conditions for NAV release.
• Build reconciliation checklists (positions, cash, shares) and require sign-off before publish.
• Review third-party dependencies (administrator, pricing vendors) and document fallbacks.

Days 61–90 (test, evidence, and harden)

• Run a tabletop scenario for pricing outages and market disruption; document outcomes and runbook changes.
• Sample prior NAV dates and confirm you can recreate the NAV with retained artifacts.
• Move logs, approvals, and evidence into a system workflow (Daydream or your existing GRC/work management tool) so audit trails are consistent and searchable.
• Establish periodic QA reviews of overrides and fair value determinations for trend spotting.

Frequently Asked Questions

Do we have to calculate NAV more than once per day?

The requirement is at least once daily at a consistent time. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1) Some funds calculate more frequently for operational reasons, but that is a business decision and must remain controlled and consistent.

What counts as a “readily available market quotation”?

The rule draws the line between instruments you can price from current market quotations and those you cannot. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1) Operationally, define criteria by instrument type and document exceptions (thin trading, stale quotes, disrupted markets).

How do we document “fair value in good faith” without overengineering it?

Use a standardized fair value worksheet that records method, inputs, assumptions, and approval for each impacted holding. Tie it to pre-defined triggers in your valuation matrix so the team follows the same steps each time. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

We outsource fund accounting to an administrator. Are we still on the hook?

Outsourcing changes who performs the work, not the need for a controlled NAV process and audit trail. Keep oversight artifacts: procedures, exception reporting, approvals, and issue management with the administrator as a high-impact third party. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

What evidence is most persuasive in an exam?

A complete NAV package for selected dates: raw pricing inputs, exception and override logs with approvals, fair value support, reconciliations, and final NAV sign-off. Examiners want to see repeatability and traceability from source data to published NAV. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)

How should we handle a late corporate action or trade booked after the cut-off?

Treat it as an exception: document timing, assess NAV impact, follow your escalation rules, and ensure the correction path is governed. The critical point is consistent cut-offs and disciplined exception handling around the daily calculation. (15 U.S.C. § 80a-22; 17 CFR § 270.22c-1)