HomeLibraryServicesCase studiesBlogAbout
consultance.ai
Book a discovery call →

Services

  • AI consulting
  • AI implementation
  • AI agents
  • Workflow automation
  • RAG systems
  • Voice AI
  • Custom AI development
  • All services

Library

  • AI build library
  • Finance AI automation
  • AiToEarn content agent
  • Fincept Terminal
  • ERPNext
  • SEO + GEO Claude skill
  • Claude for Legal
  • Free Claude Code proxy

Resources

  • Case studies
  • Blog
  • Industries
  • Locations
  • Guide: AI for property management
  • Guide: AI for marketing agencies
  • Guide: AI agents vs Zapier
  • AI glossary
  • vs traditional consulting

Company

  • About
  • Book a call
  • Contact
  • Privacy
  • Terms

© 2026 consultance.ai · AI, implemented.

audit → build → deploy

← Libraryconsultance.ai
Book a build call
Finance and data

In-House Fund NAV Close

17 prompts that run your monthly fund NAV close in-house, so COOs and controllers reconcile, book fees, run the LP waterfall, and draft investor letters without a fund administrator.

Free — runs in your own ClaudeMedium setup · 4 steps13 ready-to-run prompts+ live interactive tool
Set it up free — takes 3 minutes ↓Or have us wire it in →
Step 1 · setup
Three minutes, four steps, nothing to install by hand

Claude sets it up for you. You just paste.

Never used Claude? It is free and takes 30 seconds to open. Copy the instruction below, paste it into Claude, and it reads this page and walks you through everything, one question at a time.

  1. 1

    Tell Claude how to talk to you

    One tap. It changes how much Claude explains, and how slowly it goes. You can change it any time.

  2. 2

    Copy your setup instruction

    A short instruction plus a link to this page lands on your clipboard. First copy asks for your email once. That unlocks every button across the whole library.

  3. 3

    Open Claude in a new tab

    Free account, no card, 30 seconds. This tab stays open so you can come back.

    Open claude.ai ↗
  4. 4

    Paste, send, and answer one question

    Claude reads this page, asks one question about your work, then guides you step by step until your first output is right. If anything looks wrong, tell Claude what you see, and it fixes it with you.

▸Prefer the full prompt instead of the link? (optional)
Click to copy
I am comfortable copy-pasting and following instructions, but I am not a developer.
There is nothing to install for this one and no commands to type: it all happens inside Claude. If any instruction below implies a Terminal, translate it into the equivalent click path for me instead.
- Plain English. Define jargon the first time it appears.
- One step at a time, then wait for me to confirm before the next one.
- Tell me what success looks like at each step, and diagnose any error before moving on.

Follow the instructions below with those rules applied.

I want to INSTALL the real setup so Claude runs the monthly NAV close on my actual fund books, not just a chat demo. Walk me through it step by step, do not skip the install. Treat me like a fund controller or COO who has never built a Claude Project or installed an Office add-in, and define every term once.

This is NOT a Terminal or coding install. There is nothing to compile. It is two paths: a private Claude Project for the fund records (recommended) and an optional Excel add-in for the NAV strike, the reconciliations, and the fee math.

## Path 1 (RECOMMENDED), a private Claude Project for the close
This is where the trade blotter, prime broker and custodian statements, general ledger, and LP register live so every prompt reads from one governed place.

Walk me through ONE step at a time, waiting for me to confirm each:

1. **What I need.** A Claude account on a Team or Enterprise plan so the data stays in my tenant. Pin **Opus 5**. Nothing to install for this path.
2. **Create the close workspace.** In Claude, create a new **Project** named for the fund and the period. A Project is a private workspace with its own knowledge that other chats cannot see. Your blotter, statements, GL, and LP register stay in your own tenant.
3. **Load the records.** Drop the trade blotter, the prime broker and custodian statements, the GL or trial balance, the LP register, and your fee terms into the Project knowledge. If you run multiple funds, keep one Project per fund.
4. **Run the vault.** Run prompt 01, pick your fund type (hedge, PE/VC, fund of funds, family office), and data source (A) upload (or (D) connector if you pull from an administrator portal, prime broker feed, or fund-accounting system under governed access). Run 02 to 13 in order: strike the NAV, reconcile to the broker and custodian, book the fees, run the waterfall, reconcile the capital accounts, work the breaks, draft the letter, build the statements, re-derive the numbers a second way as a self-check, sign off, accrue expenses, and assemble the audit binder.
5. **Gate it.** Treat prompt 10 (the reconciliation self-check) and prompt 11 (the controller sign-off) as hard gates. Any red item or any self-check FAIL blocks publication. The person who strikes the NAV is not the only one who reviews it. A named human signs the NAV, a prompt cannot.
6. **Parallel run first.** Run the close alongside your administrator for one or two cycles and tie your NAV to theirs within tolerance before you trust it or change anyone's scope. See the 90 day rollout in the bundle.

## Path 2 (OPTIONAL), Claude for Excel add-in for the strike, recon, and fee math
If I want the NAV strike, the reconciliations, and the fee schedule to live in real formulas:
1. In Excel (Microsoft 365 desktop or web): **Home** or **Insert** tab, **Add-ins** / **Get Add-ins**, search **"Claude"**, **Add**. Tell me where the button is in my version.
2. Sign in to the docked Claude side panel.
3. In vault prompt 01 choose data source (C) Excel add-in. For prompt 02 (NAV), prompt 03 (reconciliation), and prompt 04 (fees) say "build this into my workbook as real formulas," so the NAV recomputes, the breaks list updates, and the high-water mark math runs on live cells.
4. Pin **Opus 5** for the strike, the fee and allocation math, and the sign-off.

## Rules for walking me through this
- One step at a time. Define every term once: Project, knowledge, NAV, trade blotter, prime broker, custodian, administrator, high-water mark, hurdle, waterfall, capital account, equalization, Level 3, SOC 1, `<review_gate>`, `{{TOKEN}}`.
- Do NOT tell me a step is "not possible." If the Excel add-in is missing, check Excel for Microsoft 365, try Excel on the web, or AppSource. For the Project path there is nothing to install.
- Never paste live investor PII or fund records into a public Claude window outside a Project. Use a Project with your tenant controls; respect your administrator's and data providers' terms.
- This moves the labor in-house. It does not replace independent NAV verification, SOC 1 controls, or the annual audit. Read the audit and compliance overlay before you reduce your administrator's scope. A named human signs every NAV. Not accounting or audit advice.

First message: ask me "Path 1 (Claude Project for the fund records, recommended) and do you also want Path 2 (Excel add-in for the NAV strike and fee math)? And is this a hedge fund with NAV per share, or a closed-end PE or VC vehicle with capital accounts?" Then start step 1.
Step 2 · run it on your data

Step 1 set it up. These 13 prompts do the work.

the vault

The 13 prompts

Grab the whole pack as one file, or tap any prompt below to copy it on its own. Placeholders that look like {{THIS}} get swapped for your own numbers — and if you ran Step 1, Claude fills them in for you.

One .md file · all 13 prompts, numbered, in order · nothing left out.
Click to copy
<role>You are a fund finance team in one: a fund controller who has struck 200+ monthly NAVs, a fund accountant from a top administrator (SS&C, Citco, State Street, Northern Trust), and a hedge fund COO. You run the close with the rigor of an institutional administrator, and you flag the things an administrator would escalate.</role>

<onboarding>
Before any work, set up the close. Ask me to confirm each block. Offer the options. Do not assume.

1. FUND TYPE, which is this?
   (A) Hedge fund, open-ended, NAV per share with subscriptions and redemptions
   (B) Private equity / VC / closed-end, capital accounts and commitments
   (C) Fund of funds
   (D) Family office / SMA / managed account
   (E) Other, tell me the structure

2. WHERE IS YOUR DATA? Pick all that apply. This decides how the next prompts run.
   (A) I will upload statements and exports (trade blotter, PB/custodian statements, GL, LP register) into this Claude project's knowledge.
   (B) I will paste raw data (positions, cash, capital activity) into the prompt.
   (C) I have the Claude add-in for Microsoft Excel or Word, work directly in my workbook or build the letter in my document.
   (D) I have a governed connector (administrator portal, prime broker feed, fund-accounting system, market-data), pull under controlled access.
   (E) Mix of the above.

3. FUND CONTEXT, fill what you have:
   Fund: {{FUND_NAME}}
   Base currency: {{BASE_CCY}}
   Period being closed: {{PERIOD}}
   NAV frequency: {{NAV_FREQUENCY}}
   Prime broker / custodian: {{PRIME_BROKER}}
   Administrator (if any, for parallel tie-out): {{ADMIN_NAME}}
   Management fee terms: {{MGMT_FEE_TERMS}}
   Performance fee / carry terms (hurdle, high-water mark, crystallization): {{PERF_FEE_TERMS}}

4. OUTPUT BAR, confirm: every figure must trace to a source line in my data. Every estimate is labeled ASSUMPTION. Debits equal credits. Allocations sum to 100 percent. The NAV ties out before anything ships.
</onboarding>

<rules>
Shared rules, stated once here, they govern every later prompt.
- Never fabricate a number. If a figure is not in my data, ask or label ASSUMPTION. Do not plug.
- Match every later prompt to the data source I chose in block 2.
- An unreviewed area is UNKNOWN, never clean.
- When two sources disagree, name both and stop. Do not average them and do not pick the tidier one.
- Flag any break, stale price, or missing statement early, not in the appendix.
- Always end with "Next step:" and the next prompt to run.
</rules>

<adapt>
Four things are meant to be edited, everything else is the control.
- Fund type: block 1 and {{FUND_TYPE}}. Open ended strikes NAV per unit, closed end carries net assets to the capital accounts in prompt 06.
- Evidence standard: the constraints block in prompts 02 and 03. Tighten to administrator statement only for an audit cycle, loosen to manager records for a management estimate.
- Fee convention: {{FEE_BASIS}} and {{CRYSTALLISATION}} in prompt 04. The LPA governs, not the default.
- Tolerance: {{TOLERANCE}} in prompt 10. Default 1 basis point of NAV. Tighten for a final strike, never loosen to clear a break.
</adapt>

<no_override>
Four faults are cleared only by fixing the defect, never by a signed reason and never by me saying proceed:
a price or holding that appears in no source document; a tolerance widened after the break was seen; a completeness gap in the position file; and any argument built for why a FAIL does not matter. That last one is itself the finding.
</no_override>

Confirm my four blocks back to me, then wait for prompt 02.
Click to copy
<role>Fund accountant striking the period NAV from the books of record.</role>

<task>
Using the data source I selected in prompt 01, strike the NAV for {{PERIOD}}.
1. Build the position-level valuation: quantity times price, by instrument, with the price source and price date for every line.
2. Add cash by currency, accrued interest, dividends receivable, and any other receivables.
3. Subtract accrued expenses, accrued fees, redemptions payable, and other liabilities.
4. Roll to gross assets, total liabilities, and net assets (the NAV).
5. For an open-ended fund, divide by units outstanding to get NAV per unit. For a closed-end fund, carry net assets to the capital accounts in prompt 06.
6. Output a one-page NAV pack: the headline NAV, NAV per unit, and the period-over-period change with the three largest drivers.
</task>

<constraints>Every position needs a price source and price date. Flag any price older than the valuation date as STALE. Flag any position you cannot price as UNPRICED, do not estimate it into the NAV. A price that exists but has not moved in weeks is ILLIQUID, which is not the same as stale, say which.

Then run the mark governance check on every level 2 and level 3 line, because this is where NAV is actually lost: name the price source hierarchy the LPA specifies and whether this line followed it; name who signed the mark and their reporting line; state whether the portfolio manager has a vote on the valuation committee; state whether the front office can override a price and whether any override happened this period. Any structure where the person paid on the mark controls the mark is a FINDING, and it is reported even when the price is correct.</constraints>


<trap>Trade date, not settlement date. A trade executed on the last business day settles next period: it belongs in positions and in the payable, never in neither and never in both. Second trap, price the position at its local market close but convert at the FX snap the LPA names. Mixing the two snaps silently moves NAV and reconciles to nothing.</trap>

<review_gate>State total assets, total liabilities, and net assets. Confirm the accounting equation holds. List every STALE or UNPRICED line for human pricing before sign-off.</review_gate>

Then "Next step:".
Click to copy
<role>Fund controller reconciling the books to the prime broker and custodian statements.</role>

<task>
Reconcile my book (from prompt 02) to the broker and custodian statements in my data source.
1. Position reconciliation: match book quantity and market value to the broker, line by line. List every break with the instrument, book figure, broker figure, and the difference.
2. Cash reconciliation: match book cash by currency and account to the statement. List timing items (in-transit trades, pending settlements) separately from true breaks.
3. Classify each break: pricing difference, quantity difference, missing trade, corporate action not booked, FX, or unknown.
4. Rank breaks by absolute dollar impact on NAV.
5. Output a reconciliation summary with a clean / not-clean call and the dollar value of unreconciled items.
</task>

<constraints>Work only from the statements I provided. Do not assume a break clears. Separate timing differences from genuine breaks. A reconciliation with any unexplained break is NOT clean.</constraints>


<trap>The prime broker report is financing inclusive and may net long and short across accounts, and a rehypothecated position can sit on the PB statement and not the custodian's. Reconcile quantity by identifier and by account, never by market value alone: two errors of opposite sign net to a clean total.</trap>

<review_gate>State the total dollar value of unreconciled breaks and that value as a fraction of NAV in basis points. If it exceeds my tolerance, the NAV is not ready to strike.</review_gate>

Then "Next step:".
Click to copy
<role>Fund accountant booking fees under the fund's terms.</role>

<task>
Calculate and book the fees for {{PERIOD}} from my terms in prompt 01 and the NAV from prompt 02.
1. Management fee: apply {{MGMT_FEE_TERMS}} to the correct base (NAV, committed capital, or invested capital) for the period. Show the base, rate, day count, and amount.
2. Performance fee or carried interest: apply {{PERF_FEE_TERMS}}. Walk the hurdle, the high-water mark per investor or per series, and whether the fee crystallizes this period.
3. For a high-water mark fund, show each investor or series at, above, or below their mark, and accrue only where above.
4. Book the journal entries: fee expense, fee payable, and any offset or waiver.
5. Output a fee schedule with every input shown and the resulting accrual.
</task>

<constraints>Use only the fee terms I confirmed. Do not accrue a performance fee where the investor is below their high-water mark. Show the high-water mark and hurdle math for every investor or series, do not net them into one number.</constraints>


<trap>The incentive fee is circular. It accrues on a NAV that is itself net of the accrual. Solve iteratively or state the convention the LPA names, and never accrue on gross. A fund level high water mark is the wrong base whenever investors entered at different NAVs.</trap>

<review_gate>State the management fee, the performance fee accrued, and the number of investors or series below their high-water mark (where no performance fee is due). Flag any term you had to assume.</review_gate>

Then "Next step:".
Click to copy
<role>Fund controller allocating the period result across investors.</role>

<task>
Allocate the period profit and loss across investors using the structure I confirmed in prompt 01.
1. For an open-ended fund: allocate P&L pro rata by units or by capital, then apply equalization or series accounting for investors who subscribed mid-period (handled in detail in the bonus pack).
2. For a closed-end fund: run the distribution waterfall, return of capital, preferred return / hurdle, GP catch-up, then the carried interest split.
3. Show the allocation tier by tier with the dollar amount flowing to each tier.
4. Reconcile: the sum of all investor allocations must equal the fund-level result. Show the tie-out.
5. Output the allocation table by investor or LP.
</task>

<constraints>The sum of investor allocations must equal the fund result to the cent. If it does not, stop and show the reconciling difference. Apply the waterfall tiers in the exact order in the LPA or offering document, do not reorder.</constraints>


<trap>Equalisation. An investor who subscribed mid period must not pay performance fee on gain earned before they arrived. Apply series of shares or an equalisation credit, whichever the offering document names, and apply it consistently across every investor in that series.</trap>

<review_gate>State that total allocated equals the fund result and the difference is zero. If non-zero, do not proceed.</review_gate>

Then "Next step:".
Click to copy
<role>Fund accountant maintaining the investor capital accounts.</role>

<task>
Roll each investor or LP capital account for {{PERIOD}}.
1. Opening balance, plus contributions or subscriptions, less distributions or redemptions, plus or minus the P&L allocation from prompt 05, less fees from prompt 04, equals closing balance.
2. Maintain the components separately: contributed capital, distributed capital, unrealized and realized gain, and accrued carry.
3. Reconcile the sum of all capital accounts to the fund net assets from prompt 02. Show the tie-out.
4. Flag any account that went negative or breached a side-letter term.
5. Output the capital account roll-forward by investor.
</task>

<constraints>The sum of capital accounts must equal fund net assets. Keep contributions, distributions, and gains in separate columns, do not collapse them. Honor side-letter terms where I provided them.</constraints>


<trap>The high water mark is per investor per series, never per fund. A fund above its fund level HWM can still hold investors below theirs.</trap>

<review_gate>State that the sum of capital accounts ties to fund net assets, difference zero. List any account that is negative or breached a side letter.</review_gate>

Then "Next step:".
Click to copy
<role>Internal auditor on the close, root-causing reconciling items.</role>

<task>
Take every break and exception raised in prompts 02 through 06 and work them.
1. For each open item: state the root cause hypothesis, the dollar impact, and the evidence needed to clear it.
2. Sort into: clears with a known entry, needs a document I do not have, or needs a human decision.
3. Propose the correcting journal entry for the items that clear, with the offsetting accounts.
4. List the items that must NOT be cleared without a human decision and say who should decide.
5. Output an exception log with status for every item.
</task>

<constraints>Do not clear a break by assumption. If clearing needs a document or a judgment call, mark it OPEN and name what is required. An exception log with an unexplained item blocks the close.</constraints>


<trap>Two breaks of opposite sign that net to zero are still two breaks. Never report a netted total as reconciled.</trap>

<review_gate>State the count of items cleared, the count still open, and the dollar value still open. The close is not ready while any material item is open.</review_gate>

Then "Next step:".
Click to copy
<role>Investor relations associate drafting the period letter from the struck numbers.</role>

<task>
Draft the {{PERIOD}} investor letter using only the numbers produced in this close.
1. Headline performance: period return gross and net of fees, and since-inception where I provided the history.
2. Attribution: the three largest contributors and the three largest detractors, by the numbers in my data, not invented.
3. Portfolio commentary, positioning, and any change in exposure, in plain operator language.
4. Capital activity: subscriptions, redemptions, and net flows for the period.
5. A clean, calm tone. No promises about future returns. No number that did not come from the close.
</task>

<constraints>Every figure in the letter must trace to a prior prompt's output. Do not state a return, attribution, or exposure figure that is not in my data. Mark anything I need to fill as [INPUT NEEDED]. Show gross and net clearly labeled.</constraints>


<trap>Any prior period figure that has moved is a restatement and must be labelled as one in the letter. A quietly corrected comparative is the fastest way to lose an LP.</trap>

<review_gate>List every number used in the letter with its source prompt. Confirm no forward-looking guarantee was made.</review_gate>

Then "Next step:".
Click to copy
<role>Fund accountant producing the per-investor statement.</role>

<task>
For each investor or LP, build the capital account statement they receive.
1. Header: investor name, vehicle, period, ownership percentage.
2. The roll-forward from prompt 06: opening, contributions, distributions, allocated P&L, fees, closing.
3. Performance: period and since-inception net return for that investor, and for a PE vehicle, paid-in, distributed (DPI), and remaining value (RVPI / TVPI) where I provided the history.
4. Unfunded commitment remaining, for closed-end vehicles.
5. Output one statement per investor in a consistent template, ready to format and send.
</task>

<constraints>Use only that investor's figures from prompt 06. The statement total must match the capital account roll-forward exactly. Do not show another investor's data on a statement. Where a metric needs history I did not provide, mark [INPUT NEEDED].</constraints>


<trap>Subscriptions received before their effective date are a liability, not capital. Redemptions payable were struck at the prior NAV and stay a liability at that figure.</trap>

<review_gate>Confirm each statement closing balance ties to the prompt 06 roll-forward for that investor. Confirm no cross-investor data leaked between statements.</review_gate>

Then "Next step:".
Click to copy
<role>Independent reviewer recomputing the close from scratch to catch an error in the strike. You did not see the earlier work. You re-derive, then compare.</role>

<task>
Re-derive the key numbers a SECOND, independent way. Do not copy the earlier prompt outputs. Recompute from the source data, then compare to what prompts 02 through 06 produced.
1. NAV: rebuild net assets a different way (opening NAV plus period P&L plus capital activity less fees) and compare to the prompt 02 struck NAV.
2. P&L: independently total realized plus unrealized plus income less expenses, and compare to the allocated result in prompt 05.
3. Fees: recompute the management and performance fees from first principles and compare to prompt 04.
4. Capital: re-sum the LP capital accounts and compare to net assets, independently of prompt 06.
For every comparison, show both numbers and the delta. Anything outside {{TOLERANCE}} (default 1 basis point of NAV) is a FAIL.
</task>

<constraints>Recompute, do not restate. If you reuse an earlier output instead of re-deriving it, this check is worthless. Claude does the math in chat, so this self-check is your guard. Report deltas honestly, do not round a mismatch to zero.</constraints>


<trap>Re-deriving from a spreadsheet that itself descends from prompt 02 is not an independent derivation. Go back to the source statements, or this check is theatre.</trap>

<review_gate>State PASS or FAIL for each of the four re-derivations with both numbers and the delta. Any FAIL blocks the close. Exactly one thing unblocks it: a named human resolving the discrepancy, with their explanation recorded verbatim in the binder. Me saying proceed anyway does NOT unblock it, and neither does widening {{TOLERANCE}}. If you find yourself building the case for why a FAIL is immaterial, that argument is the finding.</review_gate>

Then "Next step:".
Click to copy
<role>Fund controller running the final review gate before the NAV is published.</role>

<task>
Run the close sign-off checklist before anything leaves the fund.
1. NAV struck and the accounting equation holds (prompt 02).
2. Broker and custodian reconciliations clean or breaks within tolerance and documented (prompt 03).
3. Fees booked with high-water mark and hurdle math shown (prompt 04).
4. Allocation ties to the fund result, difference zero (prompt 05).
5. Capital accounts tie to net assets, difference zero (prompt 06).
6. Exception log has no open material items (prompt 07).
7. Investor letter and statements use only struck numbers (prompts 08, 09).
8. Reconciliation self-check passed, every re-derivation within tolerance (prompt 10).
9. Segregation of duties: confirm the person who struck the NAV is not the only reviewer. Name the independent reviewer.
Output a green / amber / red sign-off pack with the one or two items still blocking, if any.
</task>

<constraints>This is a hard gate. Any red item blocks publication. Do not mark green to be helpful. The point of the gate is to catch what the rush misses.</constraints>


<trap>A sign-off collected before the last break cleared is not a sign-off. Date and time stamp every approval against the break log, because an approval that predates the fix is the audit finding, not the fix.</trap>

<review_gate>State the overall call and every item that is not green. Name the human who signs off. A prompt cannot sign off a NAV.</review_gate>

Then "Next step:".
Click to copy
<role>Fund accountant accruing fund expenses for the period.</role>

<task>
Accrue and true-up fund operating expenses for {{PERIOD}}.
1. Recurring accruals: audit, legal, administration (if retained), custody, tax prep, regulatory, amortized organizational costs.
2. Apply any expense cap or expense ratio limit in the offering documents, and calculate the manager reimbursement or fee waiver required to hold the cap.
3. True-up prior estimates to actuals where invoices arrived this period.
4. Show the expense ratio for the period and against the cap.
5. Output the expense schedule with each accrual, its basis, and the cap math.
</task>

<constraints>Use the actual cap terms I provided. Show the reimbursement or waiver calculation, do not net it silently into one expense line. Flag any expense without an invoice or a documented accrual basis.</constraints>


<trap>An expense cap with a clawback is not a waiver. The waived amount remains a contingent liability until the clawback window closes, and it belongs in the disclosure even when it is not accrued.</trap>

<review_gate>State the period expense ratio, the cap, and the waiver or reimbursement amount. Flag any unsupported accrual.</review_gate>

Then "Next step:".
Click to copy
<role>Fund controller building the prepared-by-client package for the annual auditor.</role>

<task>
Assemble the tie-out binder for this period so the close is audit ready.
1. Index: NAV pack, reconciliations, fee schedules, allocation, capital accounts, exception log, expense schedule, investor letter and statements.
2. For each, state the source document and the tie-out reference so an auditor can trace any number to evidence.
3. Build the lead schedules: net assets, P&L, fees, and capital, each tying to the financial statements.
4. List the open items an auditor will ask about and the support you have for each.
5. Output a binder index and a one-page tie-out map.
</task>

<constraints>Every schedule must reference its source. Do not present a number without a trace. Mark any item lacking support as an OPEN PBC item for the team to resolve before the audit.</constraints>


<trap>The binder must contain the working that FAILED and was corrected, not only the clean final. An auditor who finds no evidence of a caught error concludes the check was never run.</trap>

<review_gate>Confirm every lead schedule ties to the NAV and the capital accounts. List the OPEN PBC items. This binder supports the audit, it does not replace it.</review_gate>

Then "Next step:".

Got the prompts. Want them wired into your actual stack? We map that on a free AI audit.

Book the free audit
🔥 optional · live interactive tool

Open the shadow NAV desk

Browser-based. No signup. Drop in your numbers and see the trade in real time. Opens in a new tab so the prompts stay where you left them.

Launch the live tool ↗

Rent it forever, or own it once.

17 prompts that run your monthly fund NAV close in-house, so COOs and controllers reconcile, book fees, run the LP waterfall, and draft investor letters without a fund administrator.

Path A · free

You just did it

The setup rail and every prompt above are free and stay free. The cost is your time, and the risk of wiring it wrong on live data.

Back to the prompts ↑
Path B · done with you

We wire it into your business

We would deliver a deployed close workspace: the prompts loaded into your Claude tenant, governed connectors to your prime broker, custodian, and fund-accounting system, the NAV strike and fee math wired to your terms, a parallel-run tie-out against your administrator, segregation-of-duties review gates, and an auditor-ready PBC binder. Done with you, then handed over so you own it.

Book a build call →
data safety

Before you use live numbers

  • • Run last quarter's numbers first. Live data is not a test bed.
  • • Nothing here uploads to us. It runs in your own Claude account, on your own machine.
  • • A named human reviews and signs every output before it reaches a board, lender, or client.
  • • Mask account numbers and names to the minimum the task needs.
the fine print

Straight answers on ownership

Prompt set authored by consultance.ai. SS&C, Citco, State Street, and Northern Trust are referenced as the administrator standard the pack matches, no affiliation implied. Your fund and investor data stays in your own Claude tenant; we never see it. This moves the labor in-house, it does not replace independent NAV verification, SOC 1 controls, or the annual audit; a named human signs every NAV. Not accounting, audit, or investment advice.

Want this running in your business, not just your laptop? We build it and hand you the keys.

Book a build callBack to the library

Want this wired into your stack instead of running it yourself? That is our AI deal desk and finance automation service.

the newsletter

AI news worth opening.

The AI tools, launches, and shifts that actually matter, in plain English. New library drops the moment they land.

100% freeNo paywall, everUnsubscribe anytime

More like this

Other builds worth a weekend

All repos →
Finance and data

Free Portfolio Quant Research Desk

For family offices and serious individual investors: run a portfolio backtest, tax loss harvesting, and model risk checks on your own holdings, locally, in your own Claude. Replaces the $250k quant seat you would otherwise hire.

Setup guide →
Finance and data

Private Equity Deal Sourcing Playbook

For lower and mid market private equity origination teams: turn one mandate into a ranked, owner verified proprietary deal flow pipeline. Six Claude agents with Exa and Scrapling replace a rented deal sourcing subscription.

Setup guide →
Finance and data

Free Jira Alternative for Deal Teams

For PE deal teams and IC members still tracking a live process on a sprint board: a self hosted deal tracker your Claude can write to, plus 10 prompts that move a workstream only when the document actually lands.

Setup guide →
Get the free kitBook a call

Forward this to whoever owns the workflow.

The person drowning in this every week is the one who'll actually want it.

Forward by email
in one line

What is In-House Fund NAV Close?

In-House Fund NAV Close is a finance and data build in the consultance.ai AI Build Library. 17 prompts that run your monthly fund NAV close in-house, so COOs and controllers reconcile, book fees, run the LP waterfall, and draft investor letters without a fund administrator. It fits hedge fund COOs, PE and VC fund CFOs, fund controllers, emerging managers, and family office finance leads paying an administrator basis points on AUM for the monthly NAV close. Setup difficulty is Medium, with 4 plain-English steps.

What does In-House Fund NAV Close do?

17 prompts that run your monthly fund NAV close in-house, so COOs and controllers reconcile, book fees, run the LP waterfall, and draft investor letters without a fund administrator.

Who is In-House Fund NAV Close for?

It fits hedge fund COOs, PE and VC fund CFOs, fund controllers, emerging managers, and family office finance leads paying an administrator basis points on AUM for the monthly NAV close.

How hard is In-House Fund NAV Close to set up?

Medium to set up — one guided setup instruction covering 4 plain-English steps, plus 13 ready-to-run prompts on the resource page.

How would consultance.ai build this out?

We would deliver a deployed close workspace: the prompts loaded into your Claude tenant, governed connectors to your prime broker, custodian, and fund-accounting system, the NAV strike and fee math wired to your terms, a parallel-run tie-out against your administrator, segregation-of-duties review gates, and an auditor-ready PBC binder. Done with you, then handed over so you own it.

What are the licensing terms?

Prompt set authored by consultance.ai. SS&C, Citco, State Street, and Northern Trust are referenced as the administrator standard the pack matches, no affiliation implied. Your fund and investor data stays in your own Claude tenant; we never see it. This moves the labor in-house, it does not replace independent NAV verification, SOC 1 controls, or the annual audit; a named human signs every NAV. Not accounting, audit, or investment advice.

Want this built into your workflow?

In-House Fund NAV Close is the starting point. On a free AI audit we map where it fits your stack and what consultance.ai would build around it.

This build comes from our AI consulting and AI implementation practice — see the full AI in finance guide and how we work with CFO teams.

Book your free AI audit