OpenIM The Open Investment Model

SD-13.6 — GP & Manager Report Ingestion

Business Domain: BD-13 Investment Data & Reporting (Cross-cutting — data) · Applies: PRIV

Purpose

Captures, structures and validates the unstructured reporting an institution receives from the external managers and GPs it has committed capital to — capital-account statements, quarterly reports, capital-call and distribution notices, portfolio-company updates. It is the unstructured-data on-ramp for the entire private-markets book: where public-markets data arrives structured from feeds (SD-13.4), private-markets data arrives as PDFs and spreadsheets, in every manager’s own format, and must be read before it can be used. SD-13.6 is the capability that turns those documents into structured, validated data. It is one of OpenIM’s named frequently-omitted Service Domains — routinely treated as a data-entry afterthought rather than a governed capability. It is the extraction capability; SD-13.11 Document & Content Management is the repository the documents live in, and BD-12 processes the operational event SD-13.6’s extracted data describes.

Service Operations

  • Report intake and registration — receive manager reports from manager portals, administrators and email, register each as a document (with SD-13.11), and route it for extraction.
  • Document parsing and data extraction — read the capital-account statement, quarterly report or notice and extract the structured data points — NAV, contributions, distributions, unrealised value, fees, portfolio-company holdings — from each manager’s own layout.
  • Extraction validation — check the extracted figures for internal consistency: that the capital-account roll-forward ties (opening NAV + calls − distributions ± value change = closing NAV), that totals reconcile to line items, that figures are in the expected currency and units.
  • Entity and fund resolution — resolve the funds, vehicles and portfolio companies named in a report against the SD-13.3 fund master and the SD-13.2 entity master; private records resolve largely on alias, and confirmed new names are written back as Entity Aliases.
  • Exception and steward queue management — route extractions that fail validation or resolution to a data steward, and capture the steward’s resolution as feedback that improves the next cycle.
  • As-of and provenance tagging — tag every extracted data point with the document it came from and the period it is as of (a Q1 report filed in Q2 is as-of Q1), so downstream use carries provenance.
  • Structured-data handoff — publish the validated, resolved data to the operational domains that act on it and to the data platform.

Inputs and outputs

  • Inputs: manager and GP documents — capital-account statements, quarterly reports, capital-call and distribution notices, portfolio-company updates — held in SD-13.11’s repository; the fund and entity masters for resolution.
  • Outputs: structured, validated, provenance-tagged private-markets data — consumed by SD-12.8 Capital Call & Distribution Processing and SD-12.7 Income & Distribution Processing (which process the operational event), SD-08.3 Private-Asset Valuation (the GP mark), SD-09.8 Private-Markets Performance Analytics, SD-03.6 GP & Manager Monitoring, and SD-13.10 reporting.

Entities

  • Owns: E-23 Extraction Record — the versioned record of what was parsed from a source manager document (the extracted fields, their confidence and validation status, the E-15 Document Metadata reference, the as-of period). So an extracted figure carries audit provenance — it extends the computed-metric-as-entity principle from computed to parsed figures. Beyond the Extraction Record, SD-13.6 populates entities owned by other Service Domains rather than owning their masters — it is a data-capture capability whose provenance trail is E-23.
  • Consumes: E-15 Document Metadata (the source document, owned by SD-13.11); PM-01 Fund & Vehicle, PM-04 Portfolio Company (resolution targets); E-13 Entity Alias (fund-side partition for the fund / vehicle resolution, entity-side partition for the GP, manager and portfolio-company resolution — read for resolution, written back on steward confirmation).
  • Produces (into entities owned by other Service Domains): the input data behind PM-07 Capital Call, PM-08 Distribution, PM-09 Fund Investment and the GP-mark valuations (the method = manager_mark partition of E-07, owned by SD-08.3).

Standards

  • ILPA (Institutional Limited Partners Association) — the ILPA Reporting Template (v2.0, January 2025) and the ILPA Capital Call & Distribution Template are the closest thing to a standard format for the documents SD-13.6 ingests; extraction is far easier where a manager has adopted them.
  • The fee-and-expense detail carried within the ILPA Reporting Template (its Capital Account Statement section and the fee, expense and carried-interest line items) shapes the fee and expense data points extracted from capital-account statements.
  • DAMA-DMBOK — the data-quality and stewardship discipline applied to the exception queue.

Open extensions

  • The field-level lineage from an E-23 Extraction Record to each business record it populates.
  • The steward-feedback loop — how a confirmed resolution improves automated extraction accuracy.
  • Coverage of GP-led-secondary and continuation-vehicle reporting formats.

Built from open-investment-model v0.3.0 · f7452ad