GP Data
Your fund's own figures — uploaded directly, aggregated from your portfolio, or loaded in bulk from history.
Not available in the current release. LP Reporting is switched off for all organisations while it is finished. The screens described on this page are not reachable yet — the navigation shows them under "Coming soon", and opening one directly returns you to your workspace home.
This documentation is published now so you can see what is coming and tell us what matters most. Nothing here describes behaviour you can use today.
GP Data holds the figures that belong to the fund itself rather than to any one portfolio company: fund-level KPIs your LPs ask for alongside the investee data.
Fund-level data is entered once for the fund as a whole, not per LP. There is no LP selector on this screen — every upload and roll-up runs fund-wide.
Three ways figures get here
1. Upload a fund file
Upload your own workbook for a period, in the same formats accepted elsewhere — Excel, CSV, Word or PDF. The upload runs through the quality check before anything is stored: if the check fails, nothing is written and the platform tells you so.
2. Aggregate from your investees
Roll approved portfolio-company submissions up to fund level. The roll-up applies each KPI's aggregation rule, resolved from Nia's KPI reference library where the KPI is linked to it — including weighted-average denominators and markers for metrics that are not safe to aggregate.
Two safeguards worth knowing:
- A figure your fund uploaded is never overwritten by the investee roll-up.
- Re-running aggregation for the same period replaces the previous roll-up rather than adding a second one.
3. Load history in bulk
One workbook covering several past periods can be imported in a single pass. Period labels are
normalised — Q2 2025, FY2024, Jan 2025, 2025-01 and similar all resolve — and each period is
run through the usual map, merge-mode, quality-check and store pipeline.
The dialog previews the result period by period before anything is written, so you confirm a ledger rather than trusting a black box. One bad period does not roll back the rest, and rows the platform cannot attribute to a period are shown for review rather than dropped.
Historical import protects older periods by default: it fills gaps rather than overwriting, and never replaces a period whose figures came from an earlier upload.
Bulk historical import covers fund-level data. Portfolio-company submissions are still uploaded one period at a time. And because period pickers offer the last two years, figures loaded for older periods cannot yet be selected when generating a report.
Reviewing and removing
Stored fund figures can be opened in a detail view, and a submission recorded in error can be deleted.