Capital activity
Capital event types, the capital account engine, reversal-based amendments, the approval lifecycle and notices, and how wire instructions are handled.
Overview
Capital activity is the ledger of everything that moves capital between LPs and the fund: calls, distributions, transfers, and the corrections to all of the above. It is deliberately the most rigorously controlled part of the platform, because a mistake here is a mistake in money actually moving.
Capital event types
NAVdryx tracks the full set of events a fund’s life actually produces:
- Contributions and distributions
- In-kind contributions and in-kind distributions
- Transfers between investors who already hold a commitment in the fund (a transfer to an investor new to the fund is not yet supported end to end)
- Recallable distributions
- Tax distributions
The capital account engine
Every LP’s capital account rolls forward the same way: beginning balance, plus contributions, less distributions, plus or minus income and loss allocation, less expense allocation, to an ending balance. The rollforward is reproducible from source records rather than a number someone typed in, and the GP entity and management company keep their own capital accounts alongside every LP’s — tracked from the fund’s first day of operations, not bolted on at year-end.
Reversal-based amendments
Capital events are not edited in place once issued. A correction is a reversing entry, linked back to the event it corrects, so the history of what happened — and what was later found to be wrong — stays intact. This is the same append-only discipline that governs the audit log; see Security and trust.
The approval lifecycle
Every capital event moves through the same stages, each one audit-logged: draft, review, approval, notice, sent, settled, reconciled — and the person who prepared an event can’t approve it. Once an event is approved, the fund team can download a PDF notice for each LP allocation, an Excel schedule, and a CSV export. At the notice stage, NAVdryx issues each LP’s notice PDF, with its own verification code, for the fund team to review; LPs see nothing yet. When the event is sent, each LP finds it, with its own amount and notice, on the portal’s capital activity page, and is told by email and push notification. Per-party notice packages are not yet available, and GP and management-company allocations get no notice. See Issue a capital call.
The one exception is history imported when a fund migrates from another system. It is approved in bulk and stops there: it is never noticed, sent, settled, or reconciled, approving it notifies nobody, and it is never reversed — a wrong import is voided while the migration is open. See Migrate an existing fund.
Wire instructions
Wire details are field-level encrypted, and any change to a bank account requires dual control, callback verification, and a recorded change history, routed through its own approval chain. NAVdryx never executes a wire — it generates the instructions the counterparties use to execute the transfer at their bank. Moving money is always a human, at a bank, acting on instructions the fund has approved. On a sent capital call, the portal shows each LP the fund’s receiving account masked, and the full details only after a fresh authenticator code; no email or notice PDF carries bank details. See The LP portal.