Fund Operations
Fund operations checklist: owners, evidence, approvals, and close controls
Use one operating register to connect governing authority, investor records, cash, accounting, reporting, tax, compliance, security, and retained evidence across every vehicle.
Start with a controlled operating register
A checklist is useful only when each obligation has an owner, governing source, due rule, reviewer, evidence location, exception path, and current status. Governing documents and accounting policies control. Counsel, tax professionals, auditors, administrators, banks, and regulators may impose additional or different requirements for a particular adviser, entity, investor, or jurisdiction.5,1
- ✓Create a separate record for every fund, SPV, feeder, blocker, parallel vehicle, manager, and general partner entity.
- ✓Link each task to the document, policy, engagement letter, filing instruction, or approved decision that creates it.
- ✓Use effective-dated owners and escalation contacts so the calendar survives staff and provider changes.
1. Formation and closing readiness
Before accepting or deploying capital, confirm that the legal entities, governing agreements, offering and subscription materials, management arrangements, service-provider engagements, tax identifiers, bank accounts, signing authority, accounting basis, valuation policy, expense policy, insurance, and required registrations or exemptions have been reviewed for the actual structure. Do not copy another vehicle's setup without a documented applicability review.5
- ✓Maintain an entity chart with legal names, jurisdictions, identifiers, roles, ownership, and authorized signers.
- ✓Record every governing-document version, amendment, side letter, consent, and effective date.
- ✓Open a launch exception for any missing approval, provider, policy, account, or filing determination.
2. Investor onboarding and master data
Admit an investor only through the process in the governing and subscription documents. Keep legal identity, commitment, ownership, tax classification, contacts, notice instructions, payment details, side-letter terms, excuse or exclusion rights, transfer history, and document status in an effective-dated investor register. Separate sensitive data from routine contact fields and restrict access by role.5,4
- ✓Reconcile executed documents to the commitment and ownership ledgers before activation.
- ✓Independently verify new or changed payment instructions through an approved channel.
- ✓Record who prepared, reviewed, approved, and released each investor setup or material change.
3. Treasury and payment controls
Maintain a bank-account register, signer matrix, payment authority schedule, verification procedure, liquidity forecast, and daily or event-driven exception review appropriate to the fund's risk. There is no universal dollar threshold for dual approval. Set limits from governing authority, bank controls, staffing, transaction risk, insurance, and policy, then review them when the operating model changes.4
- ✓Separate payment preparation, approval, release, and reconciliation where staffing permits.
- ✓Treat instruction changes, first-time recipients, urgent requests, and unusual destinations as heightened-risk events.
- ✓Preserve bank evidence, approvals, callbacks, payment references, rejects, returns, and corrections.
4. Capital calls and distributions
Connect approved cash needs or distributable proceeds to the investor and commitment ledger, allocation method, notice package, payment instructions, delivery evidence, receipts or payments, accounting entries, and final reconciliation. ILPA's current template defines standardized fund-level, investor-level, transaction, and unfunded-commitment fields, but the fund documents and accounting policies determine the actual mechanics.3,5
- ✓Freeze the approved population, inputs, formulas, and overrides before notice generation.
- ✓Track delivery, acknowledgments, late or partial activity, corrections, and governed exceptions.
- ✓Close the event only when bank, investor, commitment, and general-ledger records agree or carry approved open items.
5. Period close and fund accounting
Build a close checklist around the fund's accounting basis, chart of accounts, administrator and custodian records, bank activity, investment records, fee and expense allocations, accruals, intercompany balances, capital accounts, and financial statements. Every reconciliation should name the source, preparer, reviewer, difference, resolution, and retained evidence.1,2
- ✓Lock the period and input versions used for reporting after approval.
- ✓Carry unresolved differences in an exception register rather than forcing a balancing entry without support.
- ✓Require a controlled reopening process for post-close corrections and restatements.
6. Valuation and performance records
Apply the valuation policy, accounting framework, governing documents, and approved methodology consistently. Retain source records, assumptions, models, approvals, conflicts, subsequent events, and changes from the prior period. Map actual cash flows and balances into the performance methodology the fund uses; do not create model transactions merely to populate a template.2,1
- ✓Separate valuation preparation, challenge, approval, and reporting roles where practicable.
- ✓Reconcile investment-level values and cash flows to the fund ledger and reporting population.
- ✓Explain methodology changes and retest every affected report or metric.
The operating system for private capital.
Archstone runs the back office for venture, PE, real estate, and credit funds — LP reporting, capital calls, portfolio tracking, and fund accounting, in one platform. Now in alpha.
7. LP reporting and document delivery
Use the reporting cadence and content required by the governing documents, investor agreements, accounting framework, and applicable obligations. Build each package from the approved close, then reconcile narrative, financial statements, fee and expense detail, performance, portfolio information, capital accounts, and investor-specific data. ILPA's Reporting and Performance templates can standardize parts of the package without replacing the fund's primary reports.1,2
- ✓Approve one final package and preserve its exact version before delivery.
- ✓Record recipient, channel, timestamp, access result, correction, and superseding version.
- ✓Route investor questions and data changes through controlled owners instead of editing issued reports informally.
8. Tax, audit, and filing calendar
Maintain a tax and filing calendar confirmed by the fund's tax adviser and counsel for each entity, jurisdiction, adviser status, investor population, and tax year. Current IRS Form 1065 instructions govern federal partnership-return preparation for the covered year and direct readers to the IRS form page for later developments. Do not hard-code a prior year's date, threshold, penalty, or e-filing rule into a permanent operations manual.6
- ✓Track information requests, source owners, review milestones, extensions, signatures, filing evidence, and investor delivery.
- ✓Tie partner tax information to the approved investor and capital-account records.
- ✓Set retention periods with counsel and tax advisers, then place holds on records involved in audits, disputes, or inquiries.
9. Compliance and regulatory change control
Maintain an obligation register for the adviser and every managed vehicle. Record the authority, applicability analysis, owner, frequency, evidence, reviewer, filing or delivery result, and change history. Regulatory status and requirements are fact-specific and can change; use current primary materials and qualified counsel instead of a generic asset threshold or an inherited checklist.5
- ✓Calendar periodic filings, policy reviews, attestations, training, conflicts, complaints, and regulatory correspondence that apply.
- ✓Document why an obligation applies or does not apply and who approved the conclusion.
- ✓Review source changes before updating workflows, systems, or investor communications.
10. Security, access, and continuity
Govern investor, banking, portfolio, tax, and personnel information as operational risk. NIST CSF 2.0 organizes cybersecurity outcomes across Govern, Identify, Protect, Detect, Respond, and Recover without prescribing a single certification or product. Translate those outcomes into approved access, vendor, device, backup, incident, recovery, and offboarding controls that fit the fund's systems and data.4
- ✓Review privileged access, stale accounts, shared credentials, provider access, and material changes on a defined cadence.
- ✓Test backup restoration, critical-provider continuity, incident contacts, and manual fallback procedures.
- ✓Retain evidence for access reviews, incidents, recovery tests, exceptions, and remediation.
11. Close the year with a control review
At least once per operating cycle, compare the register to actual work performed, exceptions, audit and tax findings, investor questions, provider changes, incidents, and new governing terms. Retire duplicate tasks, add missing obligations, update owners and evidence locations, and obtain approval for material policy or system changes. The output should be a shorter, more accurate control set—not a longer checklist no one can execute.4,1
- ✓Measure overdue work, repeat exceptions, reconciliation aging, late evidence, and untested recovery paths.
- ✓Assign remediation owners and due rules based on risk and governing obligations.
- ✓Archive the approved register version and preserve an auditable change history.
Frequently Asked Questions
How often should the fund operations checklist be reviewed?
Review it whenever a governing term, entity, investor right, provider, system, regulatory conclusion, accounting policy, or responsible owner changes, and perform a documented full-cycle review on a cadence approved for the operating model.
Does using a fund administrator transfer operational responsibility?
No. An administrator may prepare records and execute defined workflows, but the fund and adviser still need clear ownership, oversight, approvals, reconciliations, exception handling, service evidence, and an exit or continuity plan under their agreements and obligations.
What wire amount should require dual approval?
There is no universal amount. Set an authority matrix from the governing documents, bank capabilities, staffing, transaction risk, insurance, and approved policy. Apply heightened verification to instruction changes and unusual payments regardless of amount.
Is a secure portal always required for investor delivery?
Use the delivery method required by the governing documents and appropriate to the sensitivity, access, authentication, retention, and evidence needs of the material. A portal is one option, not a substitute for access governance, delivery evidence, and incident controls.
Does every private fund need the same audit or regulatory calendar?
No. Adviser status, vehicle structure, governing documents, investor terms, accounting basis, tax classification, and jurisdiction affect the calendar. Counsel, accountants, auditors, and administrators should confirm the obligations and dates for each entity.
How long should fund records be retained?
Use a written retention schedule approved by counsel and tax advisers for each record class and obligation. Current IRS instructions require supporting records to remain available while their contents may be material, and litigation, audit, examination, or dispute holds may extend normal periods.
What proves a checklist item is complete?
A dated result tied to the governing source, source records, preparer, reviewer or approver, output version, delivery or filing evidence where applicable, and resolved or assigned exceptions. A checked box without reproducible evidence is only a status assertion.
Sources & References
- 1.ILPA Reporting Template (v. 2.0) Suggested GuidanceInstitutional Limited Partners Association(Standardized quarterly reporting fields, governing-document alignment, and implementation considerations for GP, LP, and service-provider reporting workflows.)primary · industry guidance · LP reporting · reporting-standard
- 2.ILPA Performance Template — Granular Methodology (v. 1.1)Institutional Limited Partners Association(Standardized private-fund cash-flow mappings and fund- and portfolio-level performance outputs released in 2025.)primary · industry standard · LP reporting · performance-standard
- 3.ILPA Capital Call & Distribution Template (v. 2.0)Institutional Limited Partners Association(Standardized fund-level, investor-level, transaction, and unfunded-commitment fields for capital calls and distributions.)primary · industry standard · Capital calls · reporting-standard
- 4.The NIST Cybersecurity Framework (CSF) 2.0National Institute of Standards and Technology(A non-prescriptive framework for governing, identifying, protecting, detecting, responding to, and recovering from cybersecurity risk across organizations of any size or sector.)primary · government framework · Data rooms · security-framework
- 5.Starting a Private FundU.S. Securities and Exchange Commission(Private-fund documents govern core legal and economic mechanics, including capital commitments, calls, fees, and investor relationships.)primary · regulatory context · Private capital operations · regulatory-source
- 6.Instructions for Form 1065 (2025)Internal Revenue Service(Current federal partnership-return instructions, including filing, partner-information, record-retention, and future-development guidance for tax year 2025.)primary · government instructions · Private capital operations · tax-source
Form D Radar
See who just filed to raise a fund
A monthly brief built on our warehouse of SEC Form D filings — new pooled-fund filings, fund sizes, and momentum by strategy. The raw signal on the emerging-manager market, before it shows up anywhere else.
- New VC and PE fund filings, every month
- Fund-size distribution and quarter-over-quarter trends
- Built from SEC EDGAR primary sources — no scraped guesses
Delivered by email, plus The VC Beast Brief weekly. No spam. Unsubscribe anytime.