A fund-period source record
Map approved contributions, distributions, NAV, valuation dates, currency, source IDs, and reporting basis. Preserve fund-level and investor-level records as distinct grains.
BI & analytics
Private capital reporting and analytics
Build a reviewable data path for private equity fund finance and investor reporting: contributions, distributions, NAV, performance measures, source mapping, and quarterly approvals.
The problem
Investor reporting pulls from administrators, fund accounting, transaction notices, valuation records, and spreadsheets. When dates, scope, and versions differ, a polished report can conceal a reconciliation gap.
Common signals
When this work becomes useful
- Quarterly reporting requires repeated manual data collection
- Performance multiples differ between the investor pack and administrator reports
- Capital movements, fees, and valuation changes are difficult to trace
- New reporting templates require fields that existing extracts do not expose
Concrete output
What the engagement can produce
Reconciled performance outputs
Calculate defined measures against the agreed reporting basis, with supporting inputs, denominator checks, and ties to the approved source record.
A repeatable quarterly pack
A reviewable reporting assembly with missing-input checks, source mapping, exception ownership, version control, and approval before delivery.
A template readiness record
Map required fields to source systems, transformations, controls, and owners. Record unsupported fields and questions for the fund's reporting advisers.
Scope variants
Shape the engagement around the need
Investor reporting data assessment
Inspect one fund and one reporting period. Trace the existing pack, identify gaps, and produce a prioritized implementation outline through the existing Data and Analytics Diagnostic.
Reporting data integration
Connect approved administrator exports, accounting reports, cash-flow schedules, and valuation snapshots to the existing reporting process.
Controlled pack automation
Implement agreed calculations, templates, reconciliation, exception handling, and release records while retaining fund-finance approval.
Delivery approach
From current state to clear ownership
Agree reporting basis
Specify fund versus investor grain, reporting date, currency, gross or net basis, treatment of fees and recallable distributions, and the responsible reviewer.
Map and reconcile sources
Keep transaction IDs, effective dates, source versions, and valuation evidence. Reconcile cash movements and explain the bridge from opening to closing NAV.
Validate calculations and templates
Compare outputs with independently checked examples and approved reporting. Missing values must not silently become zero.
Release an approved snapshot
Separate preparation from approval, retain an immutable release version, and provide a controlled correction path for late data.
Technical context
Platforms and disciplines
- Administrator exports
- Fund accounting reports
- SQL
- Power BI
- Microsoft Fabric
- Snowflake
- Excel
- Document and workflow integration
What we need to begin
- Approved sample reports with confidential details removed
- Reporting basis, applicable templates, and valuation policy supplied by the fund
- Named fund-finance reviewer and administrator contacts
- Source availability, access constraints, and release requirements
Engagement fit
Clear boundaries make better projects.
Often a good fit
- Private equity fund CFOs and controllers
- Investor relations teams assembling recurring packs
- Fund finance teams reconciling administrator data
- Internal data teams supporting private-capital reporting
Probably not the right fit
- Fund administration, audit, tax, or legal opinions
- Investment recommendations or valuation judgments
- A claim of ILPA certification or guaranteed template compliance
Anonymized proof
Permadyn's existing anonymized finance and investment-operations account describes reporting logic, diligence context, source records, and governed review. It does not establish delivery of a named fund-administration platform or an ILPA-certified implementation.Explore representative work
Questions
What teams often ask first
Do you replace our fund administrator?
No. The work connects and validates approved data for analytics and reporting. Your administrator, fund-finance team, and advisers retain their existing responsibilities.
Can you support ILPA reporting preparation?
We can map source data, transformations, controls, and ownership to an agreed template. Applicability and interpretation must be confirmed with the fund's reporting owners using the official ILPA materials. No certification is implied.
How do you handle DPI, RVPI, and TVPI?
Define scope and basis first. In the simplified public example, DPI is cumulative distributions divided by paid-in capital, RVPI is closing NAV divided by paid-in capital, and TVPI is their sum. Production calculations require the fund's agreed conventions.
What happens when paid-in capital is zero or a source is missing?
Undefined multiples display as unavailable, with the reason retained. Missing inputs are exceptions, not assumed zeros. The reporting owner resolves the source gap before approving publication.
Discuss your investor reporting workflow
Bring a non-sensitive sample pack and the reconciliation or source-mapping problem. We will establish whether a focused diagnostic or reporting repair is the useful first step.
Discuss your investor reporting workflowThe packaged engagements and delivery models make the commercial boundary visible without forcing every project into the same shape.