KPI Mapping
Bind each LP's template fields to your dictionary KPIs, and merge metrics that are the same thing under different names.
Different LPs ask for the same metric in different words. KPI Mapping is where you tell the platform that "Number of jobs created" and "Total employment generated" are the same thing, and which of your dictionary KPIs fills which cell of which LP's template.
Get this right once and you collect data once, then report it to every LP.
Binding template fields to KPIs
Each field of each LP template version is bound to one dictionary KPI. Those bindings are what fill the cells when a report is generated.
The platform suggests likely bindings automatically after a template is parsed, so you are confirming rather than starting from scratch. Ambiguous or weak matches are deliberately left unset rather than guessed at.
No suggested match applies itself. However confident it is, a person confirms every binding with a tick before it takes effect.
Only what needs attention
The screen opens filtered to the rows that need attention, with a count of outstanding items, so you are not scrolling past hundreds of settled rows to find the handful that matter.
Automatic matching
Matching runs nightly on a schedule as well as on demand. Scheduled matches always land as items awaiting your review — never as silent changes to your data.
Nia's master KPI reference library is used to raise match confidence. The more of the library you have imported into or linked from your dictionary, the more matches resolve.
Duplicate detection and merging
The platform detects when two of your KPIs look like the same metric and shows each candidate pair with a confidence score.
When you merge a pair:
- You choose which KPI survives. The default is the KPI with the most dependencies, falling back to the older KPI on a tie, with a swap control on the confirm dialog if you want the other one.
- Merging is restricted to administrators.
Merge history and undo
A Merge history panel on this screen lists every merge your fund has performed, each with an Undo button.
Undo is fail-closed: it recreates the merged-away KPI and repoints its mappings, calculations, template bindings and submitted values back to it — unless anything the merge touched has since changed (edited, repointed elsewhere, or the survivor merged again), in which case it refuses the whole undo and tells you which rows blocked it rather than guessing.
Standards tagging
Tag KPIs against IFC Performance Standards, IRIS+, GRI, HIPSO and 2X here. Tags carry through to the KPI dictionary Excel export.
The deduplicated collection sheet
Export a single collection sheet covering all your LPs, with each metric appearing once. This is what you send your portfolio companies — they fill it in once, and the platform routes each value back to whichever field each LP asks for.
LP requirements
An LP Requirements column shows each LP's own wording for the field a given KPI satisfies. When an LP queries a number, this is where you see exactly how they asked for it.