LPs & Templates
Register your LPs, upload their reporting templates, and let the platform read the KPIs each one asks for.
LPs & Templates is where a reporting cycle starts. You register each LP your fund reports to, then upload the reporting template that LP sends you.
Registering an LP
Add each LP as its own record. Everything downstream — templates, bindings, generated reports — hangs off it.
Templates are held per fund. If the same LP issues a different template to a different fund, each fund uploads and owns its own version, so one fund's template never affects another's.
Uploading a template
Upload captures three things:
| Field | Why it matters |
|---|---|
| The LP it belongs to | Ties the template, and everything extracted from it, to that LP |
| Reporting frequency | Quarterly, half-yearly or annual; carries through to the KPIs and to when the next period opens |
| The file | The LP's own template, in one of the accepted formats |
Accepted formats
| Format | Status |
|---|---|
Excel (.xlsx) and CSV | Fully supported, read directly by the platform |
Word (.docx) and PDF | Supported; routed through Nia's approved document-parsing service first |
Screenshots (.png/.jpg) | Supported for LP portals you can only screenshot; read via text recognition |
Word, PDF and image files are read by a document parser before anything else happens. The AI model only ever receives the parsed structure — the raw file is never sent to it.
What happens after upload
- The file is parsed to structure.
- The platform identifies the KPIs the template asks for, including on real-world templates that follow no standard layout — where there is no definition block to read, it infers KPIs from the filled-in values.
- Each proposed KPI is scored for confidence, and likely field-to-KPI bindings are suggested.
- The template lands on the review screen awaiting a person.
Nothing reaches your KPI dictionary until someone reviews and approves it.
The template list
The list shows every template with its status and its LP. A counter on the briefing band tells you how many LPs have an approved template and are therefore ready to report against.
Template statuses run uploaded → parsing → parsed, or failed if the file could not be read.
Working with an existing template
| Action | What it does |
|---|---|
| Open review | Reach the review page from the template name |
| Upload new version | Add a newer version of the same template, with a change summary against the previous one |
| Compare versions | See what changed between two versions |
| Delete | Remove a wrongly uploaded template. KPIs it created go too — unless another template also needs them, in which case they are kept |
Capacity
Templates of roughly 20–25 KPIs are typical and around 50 is the stated design range. In practice there is no per-template KPI limit; the only ceilings are file-size and sheet-size safeguards, which sit well above that range.
LPs that only accept data through their own portal
Where an LP will not take a file at all, generate the report as normal and use the filled Excel export as your fill-in sheet, copying the values across into the LP's portal by hand.
There is no dedicated fill-in-sheet screen for portal-only LPs yet. The export-and-copy route above is the supported path today.