Record the reporting contract before defining exceptions
Specify the fund or investor population, currency, period, gross or net basis, methodology, and source versions for the pack. A check against the wrong population can pass arithmetically while producing an unusable report. Include administrator exports, capital-activity schedules, valuation approvals, and any transformations required by the agreed reporting method.
As checked September 11, 2026, ILPA publishes separate Reporting and Performance templates and supporting guidance. Its Performance page distinguishes Granular and Gross Up methodologies; choose the applicable package and version with the fund's reporting owners. The register below is an original operating template. Its states, thresholds, and release decisions are illustrative controls, not ILPA-prescribed requirements or a claim of certification.
Separate source defects from calculation symptoms
Consider a simplified fictional fund with $10 million of cumulative paid-in capital, $2 million of cumulative distributions, and $9 million of closing NAV. On the disclosed common basis, DPI is 0.20x, RVPI is 0.90x, and TVPI is 1.10x. These demonstration multiples divide by the same positive paid-in capital; they do not cover every production reporting convention.
A duplicated $50,000 contribution raises the imported paid-in amount to $10.05 million. The resulting TVPI becomes $11m ÷ $10.05m, approximately 1.0945x. A summary rounded to one decimal could still display 1.1x, concealing the defect. The duplicate transaction check and the cumulative contribution tie-out can both fail because of this one source issue. Link the related failures to a common root record without deleting either control result.
| Exception | Evidence and impact | Owner / disposition |
|---|---|---|
| E-001: duplicate contribution | Source transaction CC-208 appears twice; cumulative paid-in overstated $50,000 | Fund accounting owner: confirm active source record and rerun totals |
| E-002: valuation scope mismatch | Selected NAV file identifies a different fund; amount is not eligible | Fund-finance reviewer: obtain the correct approved snapshot; release blocked |
| E-003: inconsistent output label | Pack says EUR while the approved source and calculations use USD | Reporting owner: repair label, inspect affected outputs, approve correction |
Make release significance more specific than a dollar threshold
An exception needs a category such as missing source, duplicate record, scope mismatch, reconciliation difference, unsupported calculation, or presentation error. Record the affected pages and measures, estimated amount when known, and whether the effect is fully understood. Unknown impact is not the same as zero impact. A wrong investor, currency, or reporting basis can be significant even when a displayed amount matches another source.
Use a fund-approved release policy to decide what blocks publication, what can be accepted with an explicit explanation, and who has that authority. Do not let the person who loads the data silently waive a failed check by editing its status. An accepted exception should retain its reason, reviewer, affected release, and any required follow-up. A resolved issue needs evidence that the relevant checks passed again.
Use a state sequence that preserves evidence
One workable sequence is detected, assigned, investigated, ready for review, and resolved or accepted for a specified release. A reopened state is useful when new evidence invalidates the earlier disposition. Keep timestamps and source references with transitions. The operating team should be able to see the latest status and reconstruct the status at the moment a pack was approved.
For E-001, retain the duplicated import and the corrected active record set. Reconcile cumulative paid-in back to $10 million and rerun the affected multiple calculations. Also confirm that the next import does not reintroduce CC-208. For E-002, replacing the file is insufficient until its fund identity, reporting date, valuation version, and approval are verified. These are different remediation paths despite both resulting in a red status initially.
| Field group | Required working detail |
|---|---|
| Identity | Exception ID, fund or investor scope, period, output version |
| Detection | Check name, expected behavior, observed result, detection time |
| Evidence | Source IDs and versions, supporting reconciliation, linked root cause |
| Impact | Affected outputs and measures; known amount or explicitly unknown impact |
| Accountability | Resolution owner, reviewer, target review date, escalation path |
| Disposition | Status, decision, rationale, approval, release conditions, retest result |
Review completeness before approving the pack
A register with no open entries is not automatically a complete control record. Check that every expected source arrived and that all scheduled validations actually ran. A failed import can otherwise leave the register empty because no data reached the checks. Preserve check execution status and source coverage alongside the exceptions.
Before release, compare the final pack to its approved source versions and retain the register snapshot that supported the decision. When a later correction arrives, link it to the earlier release instead of overwriting the original review history. The objective is a reproducible explanation of why the output was considered ready, with a controlled path for changes.
- Confirm reporting scope, methodology, currency, and source versions first.
- Retain failed checks even when several point to one root defect.
- Do not infer correctness from rounded displayed multiples.
- Treat missing execution and missing sources as visible conditions.
- Assign resolution and review responsibilities explicitly.
- Preserve accepted exceptions with their rationale and release boundary.
- Save the final register with the approved pack and its source record.
Primary sources
Related services and experience
- Private capital reporting and analytics (Implementation service)
- Private equity analytics toolkit (Ungated methods and synthetic evidence)
- Private capital reporting pack (Synthetic evidence first published 2026-09-09)
- Private equity portfolio analytics (Industry practice)
Need help with this system?
Describe the reporting period, source problem, and review responsibility without sharing confidential records. Define a focused reconciliation or reporting repair using the existing engagement models.
Discuss a fund reporting control