Fund Administration Systems for Private Markets and Alternatives
Running the Books for Assets That Have No Daily Price
Fund administration for public funds is a high-volume, well-defined problem: securities have observable prices, a daily NAV is computed, subscriptions and redemptions process against it. Private markets administration looks superficially similar and works nothing like it. Valuations are periodic and judgmental, capital arrives when called rather than when subscribed, and the economics of the fund are defined by a partnership agreement whose terms differ per investor because of side letters.
That is why private markets fund administration platforms are built around the investor capital account rather than around a unit price. Everything else in the system exists to keep that account correct.
What makes this different from public funds?
Six structural differences, each of which changes the data model.
| Dimension | Public funds | Private markets |
|---|---|---|
| Valuation | Daily, observable prices | Periodic, judgmental, sometimes restated |
| Capital flows | Subscriptions and redemptions | Commitments, calls, distributions, recycling |
| Investor economics | Uniform per share class | Varies by investor via side letters |
| Fees | Management fee on NAV | Multiple bases, offsets, step-downs, carry |
| Performance | Return per unit | Multiples and internal rates of return, since-inception |
| Reporting | Standardised, frequent | Template plus bespoke, quarterly, with commentary |
Why does NAV mean something different here?
Because it is an estimate produced by a process, not a computation from prices.
Net asset value in private markets reflects valuations of holdings that were not traded, produced on a methodology, reviewed, sometimes approved by a committee, and occasionally revised afterwards. The platform must therefore treat valuation as a versioned, sourced, approvable input rather than a market data feed, and it must be able to answer which valuation was used in a given report. That single requirement rules out designs that store a current value and overwrite it.
Can your platform state which valuation version produced last quarter's reported capital account?
Talk to Digiqt about valuation versioning and capital account design
What does the platform have to do?
Nine functions, resolving into the capital account.
| Function | Responsibility |
|---|---|
| Investor register | Investors, vehicles, commitments, transfers, side letter terms |
| Commitment tracking | Called, uncalled, recallable, expired |
| Capital calls | Notice generation, allocation, funding tracking, defaults |
| Distributions | Allocation, characterisation, recycling, withholding |
| Capital accounts | Contributions, allocations, fees, carry, balances by investor |
| Valuations | Per holding, versioned, sourced, approved |
| Waterfall and carry | Tiered allocation of proceeds, clawback tracking |
| Fees | Management fee across bases, offsets, step-downs |
| Reporting | Capital account statements, standard templates, bespoke requests |
Why is the capital account the core record?
Because it is what the investor owns and what every statement renders.
Every other function is an input to it: a call increases contributed capital, a distribution reduces it or returns profit, a valuation change flows through allocations, a fee reduces it, and carry moves value between limited and general partners. Model it as an append-only ledger of movements with as-at querying rather than as a balance, since investors ask about periods and restatements require recomputation. Institutions that model capital accounts as current balances discover the limitation at the first restatement.
How do capital calls and distributions work?
Through allocation by commitment, with notices, funding tracking, and the awkward cases modelled.
A call allocates a required amount across investors by commitment proportion, generates notices with payment instructions and deadlines, tracks receipt, and handles the investor who does not fund. A distribution allocates proceeds, characterises them as return of capital or profit, applies withholding where relevant, and may be recallable. The awkward cases are where systems fail: partial funding, defaulting investors with their consequences under the agreement, excused investors for particular investments, and recycling of distributed capital back into available commitment.
What is equalisation, and why is it unexpected?
The adjustment that brings later investors into the same economic position as earlier ones.
When a fund holds subsequent closes, investors joining later must be treated as if they had invested from the start, which requires them to fund their share of prior calls plus an interest-style adjustment paid to earlier investors. The calculation involves rates, periods, and sometimes fee catch-up, and it must be reproducible because investors check it. Most generic administration platforms do not model this natively, which is why it is frequently performed in spreadsheets and becomes the source of disputes. Build it into the platform with the terms as configuration and the calculation stored.
How should the waterfall be modelled?
As configurable tiers with stored calculation, never as code.
Distribution waterfalls vary by fund: return of capital, preferred return, general partner catch-up, and carried interest split, applied whole-fund or deal-by-deal, with clawback provisions and sometimes hurdles compounding differently. Model tiers as ordered configuration with parameters, evaluate them per distribution with the inputs and result stored, and support reproduction of any historical calculation. The economics of tiered participation are the same shape as the commission waterfall structures described in this guide to fee structures and waterfall economics.
Why do side letters break generic models?
Because they vary economics per investor rather than per class.
A side letter may grant a fee discount, a different carry arrangement, excusal rights for certain investments, or reporting entitlements. A platform whose economics are defined at fund or class level cannot express that, so the terms end up maintained outside the system and applied manually, which is both an operational risk and an audit finding. Model investor-specific term overrides explicitly with effective dates, and require every override to reference the document that granted it, since the question at audit is always what the investor was entitled to and on what basis.
Are your side letter terms held in the platform or applied manually at allocation time?
Talk to Digiqt about investor terms and side letter modelling
How do you handle valuation of illiquid assets?
As a versioned process with methodology, source, approval, and restatement support.
Hold valuations per holding per period with the methodology used, the preparer, the reviewer, the approval, and the effective date. Support multiple versions of the same period, because valuations get revised, and record which version was used in each report. Then support look-through where investors require it, which means holding portfolio company financial data with its own vintage and provenance. That data arrives late, in inconsistent formats, and sometimes needs chasing, so treat collection as a tracked workflow rather than an input assumption.
Why is restatement handling a design requirement?
Because a revised valuation changes allocations, carry, and reported performance after the fact.
When a prior period valuation is revised, capital account allocations change, carry may change, reported multiples and rates of return change, and investors have already received statements based on the old figures. The platform needs to recompute cleanly, retain the prior version, and produce a clear explanation of what changed and why. Designs that overwrite cannot do this, and the manual workaround is a spreadsheet reconciliation nobody can audit. Restatement is not an edge case in this asset class, it is routine.
What about fund structures and consolidation?
Control assessment per vehicle, because structures determine what consolidates.
Master-feeder arrangements, parallel funds, blockers, and special purpose vehicles all affect what consolidates into what and how investor economics flow. IFRS 10 Consolidated Financial Statements, issued in May 2011, defines the principle of control and establishes control as the basis for consolidation, setting out how to apply the control principle to determine whether an investor controls an investee. For a platform that means the structure is data with effective dating and a documented consolidation basis per vehicle, not a static configuration, since structures change with new vehicles and restructurings. Cash flow presentation follows its own requirements, with IAS 7 Statement of Cash Flows setting the operating, investing, and financing classification framework.
How should fees be calculated?
Across multiple bases with offsets and step-downs, all versioned.
Management fees may be charged on committed capital during the investment period and on invested or net asset value afterwards, with step-downs at defined dates, offsets for transaction or monitoring fees received, and investor-specific discounts. Each of those is a rule with an effective period, and the combination is where errors occur. Store the fee calculation with its inputs and rule versions like any other financial computation, which is the same discipline described in interest accrual and fee calculation engines.
How should investor reporting be delivered?
From one canonical model through a rendering layer, with bespoke requests as templates.
Investors expect capital account statements, standard reporting templates that have become industry practice, performance figures, and increasingly bespoke data cuts for their own reporting. The failure mode is a pipeline per investor request, which multiplies maintenance and guarantees inconsistency between reports. Render everything from the canonical capital account and valuation data, treat each format as a template, and never let investor-specific transformation logic enter the data layer. That approach is the same one that controls format proliferation in global custody data consolidation, and the reporting discipline resembles this guide to structuring investor reporting.
How should delivery be sequenced?
Capital accounts first, then calls and distributions, then waterfall, then valuation versioning, then reporting.
| Phase | Duration | Deliverable |
|---|---|---|
| Investor register and commitments | 2 to 3 months | Investors, vehicles, commitments, transfers, side letter terms |
| Capital account ledger | 3 to 4 months | Append-only movements, as-at querying, restatement capable |
| Calls and distributions | 3 to 4 months | Allocation, notices, funding tracking, defaults, recycling |
| Equalisation | 1 to 2 months | Configurable terms, stored calculation, reproducible |
| Valuation versioning | 2 to 3 months | Methodology, source, approval, multiple versions per period |
| Waterfall and carry | 3 to 4 months | Configurable tiers, clawback tracking, stored calculations |
| Fee engine | 2 to 3 months | Multiple bases, offsets, step-downs, investor discounts |
| Reporting rendering layer | 3 to 4 months | Templates over canonical model, bespoke requests as templates |
Capital accounts before everything else, because every other function writes to them and a platform that models them as balances rather than as movement history will need rebuilding at the first restatement. Period-end discipline matters throughout, and the reconciliation-timing lessons in cutting close reconciliation time apply directly to quarterly reporting cycles.
Which metrics matter?
Reporting cycle time, restatement frequency and cause, allocation exceptions handled manually, equalisation and waterfall reproducibility, and investor query volume.
Report cycle time from period end to investor statements issued, since that is the service investors experience. Track restatements with cause, because a high rate indicates a valuation process problem rather than a platform one. Count allocations requiring manual intervention, which measures how much of the economics the platform actually models. Verify that equalisation and waterfall calculations reproduce identically when re-run, and treat any failure as blocking. And measure investor query volume and the share answerable from the platform without a manual reconstruction, since that is the operational load the system exists to remove.
Private markets administration rewards precision in a small number of places: the capital account as movement history, valuations as versioned approvals, waterfalls and equalisation as configuration with stored calculations, and investor terms held in the platform rather than in a folder of side letters. Get those right and the reporting is rendering. Get them wrong and every quarter becomes a reconciliation exercise.
Frequently Asked Questions
How does private markets administration differ from public funds?
Valuation is periodic and judgmental rather than daily and observable, capital moves through calls and distributions rather than subscriptions, and investor terms vary individually.
What is the core record in the platform?
The investor capital account. Commitments, calls, distributions, allocations, fees, and carry all resolve into it, and every investor statement is a rendering of it.
What is equalisation and why is it unexpected?
When later investors join at a subsequent close, they must be brought into the same economic position as earlier ones, which requires interest-style adjustments most systems do not model.
Why is hard-coding a waterfall a mistake?
Because tiers, preferred return, catch-up, and carry vary by fund and are modified by side letters, so the waterfall must be configuration with an audit trail rather than code.
Why do side letters break generic models?
Because they vary economics per investor, including fee discounts and different carry treatment, so allocations must support investor-specific terms rather than one fund-level rule.
Why is restatement handling a design requirement?
Because valuations get revised after reporting, which changes allocations, carry, and reported returns, so the platform must restate cleanly and show what changed.
What does consolidation require in fund structures?
A control assessment per vehicle, since master-feeder and SPV structures determine what consolidates, and IFRS 10 establishes control as the basis for consolidation.
What should investor reporting be built on?
One canonical data model with a rendering layer, so standard templates and bespoke investor requests are both templates rather than separate extraction paths.
