Kapintelligence by Kapnative
PORTFOLIO REPORTING

Every manager reports differently. You need one view.

Every fund commitment brings its own stream of quarterly reports, capital accounts, call and distribution notices - each in a different format, on a different calendar, with a different definition of the same metric. Kapintelligence consolidates all of it into one consistent, source-linked portfolio view.

Every figure retains its source, validation status and audit trail. Data is updated as new source documents arrive, not continuously.

CONSOLIDATION

Many managers in. One portfolio view out.

Whatever your managers send, in whatever shape they send it.

WHAT ARRIVES
  • Quarterly report PDF
  • Capital account statement PDF / XLSX
  • Capital call notice PDF
  • Distribution notice PDF
  • Audited annual accounts PDF
  • Manager portal export XLSX / CSV
KAPINTELLIGENCE
  1. 01

    Ingest

    GP reports, capital calls, distribution notices, financial statements and agreed Excel formats.

  2. 02

    Normalise

    Map commitments, NAV, cash flows, exposures and performance metrics into the approved portfolio model.

  3. 03

    Reconcile

    Identify late reports, restatements, inconsistencies, methodology breaks and validation exceptions.

  4. 04

    Deliver

    Publish approved data to dashboards, Excel files and APIs with source and status retained.

ONE CONSISTENT VIEW
  • Cash-flow history Commitment, paid-in, distributions, NAV and the complete cash-flow event list.
  • Performance IRR, TVPI, DPI and RVPI with the methodology, source and validation state attached.
  • Exposure Fund, strategy, sector, geography and currency, with asset-level look-through where the source data supports it.
  • Exception queue Late, restated, missing, contradictory or policy-breaking data with an owner and a resolution state.
  • Delivery Dashboard, Excel workbook and API output with lineage retained.
  • Audit record Who ingested, changed, approved and exported each figure, and when.

Different managers. Different formats. One consistent portfolio view.

EXCEPTION WORKFLOW

The reporting cycle is not the hard part. The exceptions are.

Late reports, restatements, methodology breaks and contradictions each get an owner, a severity and a resolution state. Filter the queue the way an operations team actually works.

Filter:
Q1 2026 cycle · 34 positions
Exception Owner Period Status
Expected: quarterly report + capital account statement

No Q1 documents have arrived. The position is carried at the Q4 2025 NAV and flagged as stale, so it does not silently enter the portfolio total as current.

SeverityHigh
Effect if unresolvedPortfolio NAV would understate one position by up to one quarter of movement.
Nothing is published to a dashboard, workbook or API until each exception is resolved or explicitly accepted with a recorded reason. Illustrative queue, anonymised funds.
LINEAGE ON EVERY FIGURE

Reported, adjusted, approved - and which document says so.

Where a reconciliation is required, all three values stay visible. The approved value is the one that leaves the platform.

Sample Buyout Fund II · NAV as at 31 March 2026 · illustrative
€96.7m
Analyst-approved

The lower value is approved for reporting until the manager confirms the asset valuation. The open exception travels with the figure.

Validation history
12 May Q1 report ingested and classified; NAV extracted from page 6.
12 May Valuation appendix total differs by €0.7m - exception raised automatically.
13 May Manager asked to confirm the carrying value of one asset.
14 May Analyst approved the lower value for reporting, exception left open.
DECISION CONTINUITY

Comparing new reporting evidence against the original IC assumptions.

The underwriting thesis, key risks, IC conditions and expected pacing are already recorded in the decision record.

IMPLEMENTATION

From one mandate to a repeatable reporting feed.

Agree the source formats, load history, configure the portfolio model and validation rules, then reconcile one full reporting cycle before expanding.

Typical timing depends on data history, integrations, validation requirements and customer availability. Four to six weeks is a typical range for a first mandate, not a commitment.

Bring one quarter of GP reports.

We will show consolidation, the exception queue and delivery on documents that look like yours.