Separate collection, calculation, review, and release
Start with a specific fund, reporting date, currency, and reporting basis. Keep fund-level financial statements, investor-level allocations, valuation evidence, and cash movements at their native grains. A single file can contain several grains; importing it successfully does not establish that the rows can be aggregated.
Use four visible states: collected, reconciled, approved, and released. A file can be collected without being reconciled. A reconciled calculation may still await valuation or narrative approval. Release should refer to the exact approved version, so a later upload cannot silently change a report already delivered to investors.
Define the reporting handoffs
The following is a workflow template, not a promised close timetable. Set dates with the administrator and reporting owners based on the fund's obligations. Each handoff needs an owner and an acceptance condition, not only a due date.
| Handoff | Owner | Acceptance evidence |
|---|---|---|
| Source collection | Fund finance / administrator | Expected files, periods, units, and source versions present |
| Cash reconciliation | Fund finance | Contributions and distributions tied to approved schedules |
| NAV bridge | Finance and valuation reviewers | Opening NAV plus movements and net change equals closing NAV |
| Template preparation | Reporting preparer | Required fields mapped; missing inputs flagged |
| Approval | Named authorized reviewer | Data, valuations, narrative, and audience approved |
| Release | Reporting owner | Versioned pack, recipient process, and correction record retained |
Worked example: an unexplained NAV difference
A fictional fund opens a quarter with $105 million NAV. It receives $10 million in contributions, distributes $8 million, and reports $5 million of net valuation and operating change. Expected closing NAV is $112 million. If the draft administrator extract shows $111 million, the workflow has a $1 million exception.
Do not insert an unexplained $1 million adjustment to force a tie. Check whether a transaction falls after the cutoff, a fee appears twice, a source is incomplete, or the valuation version changed. Record the resolution with the corrected source. Only then should the pack progress to approval. The fund reporting demo exposes this same bridge and its residual.
Automate preparation while preserving release decisions
An integration can validate filenames, schemas, required periods, duplicates, totals, and approved source versions. It can assemble tables and identify gaps. It cannot decide whether a valuation is appropriate or whether a narrative fairly explains the quarter. Route those decisions to the assigned reviewers.
For late corrections, preserve the released pack, create a revised version, explain what changed, and obtain the required approval. Avoid overwriting the original artifact or silently changing a download link to an unapproved file. Keep recipient management and confidential investor documents inside the fund's approved systems; the public Permadyn example contains only fictional data.
- Confirm the current template and reporting basis before mapping.
- Freeze the exact inputs used by each released pack.
- Reject missing figures instead of substituting zero.
- Validate both quarter activity and since-inception totals.
- Document the correction and approval path before the first automated release.
Primary sources
Related services and experience
- Inspect the fund reporting pack (Synthetic data and calculation record)
- Private capital reporting and analytics (Implementation service)
- Private equity portfolio analytics (Industry overview)
Need help with this system?
Use your current reporting process to define the source, calculation, or review problem and a bounded first engagement.
Discuss fund reporting