LP Reporting overview
The reporting cycle end to end — from an LP's template to that template filled in.
LP Reporting is the core of the platform. It takes the reporting templates your LPs send you, works out what data they ask for, collects that data once from your portfolio, and gives each LP back its own template filled in.
Who uses it
The platform is built for fund managers (GPs) and their teams. Your investees and your LPs do not log in. Investee data reaches the platform because your team uploads it, and reports reach your LPs because your team downloads them and sends them on.
The working sequence
The left-hand navigation follows the order you actually work in.
| Group | Screens | What you do there |
|---|---|---|
| Home | Mission Control, KPI Explorer, Nia Advisor | See what needs doing; explore collected data |
| Set-up | LPs & Templates, KPI Dictionary, KPI Mapping | Register LPs, upload templates, agree your metrics, map fields to them |
| Data | Data Quality Check, Investees, GP Data | Collect and check portfolio and fund-level figures |
| ESG Management | Policy Hub, ESAP Tracker, Investment Process | Govern policy and track action plans |
| Output | Reports, LP Portal Fill-In Sheet | Generate/download reports, or get values to type into an LP's own portal |
The cycle, step by step
Set the reporting period
The period is an explicit fund-level setting. It never rolls over on a calendar date — you change it deliberately. See Reporting periods.
Register your LPs and upload their templates
Upload each LP's reporting template. The platform reads it and proposes the KPIs it asks for. See LPs & Templates.
Review and approve the extracted KPIs
Nothing enters your dictionary without a person approving it. See Template review.
Agree your KPI dictionary
One definition, unit, frequency and methodology per metric, for the whole fund. See KPI Dictionary.
Map each LP's fields to your KPIs
Different LPs word the same metric differently. Mapping means you collect data once and route each value to whichever field each LP asks for. See KPI Mapping.
Collect the data
Upload portfolio-company submissions from the Investees screen and your own fund-level figures from GP Data.
Check its quality and approve it
Every upload runs through a quality check before it is stored, and approval re-checks the data as it stands at that moment. See Data Quality Check.
Generate the report
Choose an LP and a period; the platform fills that LP's template from your approved data. See Reports.
What happens automatically
Once the last outstanding input for a period is approved, the platform continues on its own:
- Aggregation runs, rolling portfolio-company figures up to fund level using each KPI's aggregation rule.
- A draft report is generated per LP once aggregation completes.
- The next reporting period opens, derived from the template's declared reporting frequency — never from a calendar date.
If an automatic run cannot proceed it says so and names what it is waiting for, which appears as a to-do on Mission Control. Automatic runs never overwrite a figure your fund uploaded, never advance the period twice, and cannot run twice at the same time.
A correction that lands after a cycle has already completed raises a visible flag, so nobody carries on relying on figures that have since changed.
Availability
LP Reporting is part of the Full plan, and Nia switches it on per fund. If the reporting screens appear in your sidebar under a greyed-out "Coming soon" heading, your plan includes them but they have not been enabled for your fund yet — contact the Nia team. See Plans & tiers.