For Investment Funds
The operating system funds run their LP reporting on.
Cross-border banking in one schema, multi-currency P&L without an FX spreadsheet, hash-chain audit log, enterprise SAML/OIDC/SCIM. The substrate your LPs already ask about, shipped before your first quarter-close.
The fund operator reality
Four gaps between operations and LP reporting that generic ERPs do not close.
Reporting frictions
LP-report cycle · Q3 2026
6 phases · 30-day windowT+30 LP-report lag is the industry median. Fund operators ship quarterly reports thirty-plus days after quarter-end because consolidation runs across portfolios, spreadsheets, and bank statements that nobody lines up until someone re-keys the numbers. Your CFO signs a report that is already a month stale. BasePro anchors operations, banking, and compliance to one reconciliation ledger from the start. The LP-facing report is a roll-up, not a rebuild.
Observed: Median quarterly LP-statement issuance, 2024–2026
One canonical cockpit for the quarterly LP cycle.
Eight SPVs across one vintage roll up into a single GP cockpit. Deployment %, IRR delta vs underwrite, AUM by SPV, waterfall state, LP-statement queue, NAV currency — all on one canvas. The same canvas your internal IC opens for deal approvals, your IR lead opens before the quarterly LP cycle, and your fund administrator reconciles against the ILPA-formatted report. No version-of-truth ambiguity, no fund-administrator handoff translating between GP-internal and LP-facing views. The cockpit IS the canonical view; specialists project per-domain depth where their expertise lives.
Fund III · 8 SPVs · vintage 2024
Quarterly LP report · 14dSPVs
8
Deployed
73%
IRR Δ
+2.4%
vs underwrite
LP statements
32 / 40
Waterfall: pref met · catch-up active · LP statements: 32 of 40 sent · NAV: signed · 14d ago
One banking schema for every rail your fund uses
CLABE for Mexico, ABA for the US, SWIFT and IBAN for international, all in one normalized table tagged to currency and country. Bank-feed reconciliation runs on the same substrate. Multi-currency P&L roll-ups land in the committee report without an FX-conversion spreadsheet in the loop. A cross-border distribution, a local-currency rent collection, and a USD-denominated capital call all reconcile against the same ledger.
SHA-256 hash-chain audit log, for LP transparency
Every write to your fund's portfolio anchors to a tamper-evident chain. Sensitive fields redact cleanly for external review without breaking the chain. When an LP's auditor asks whether a disbursement was altered after the fact, the answer is a cryptographic comparison with ten-year retention behind it. That is the substrate that lets your next LP update be a summary instead of a defense.
LP audit chain — Q3 cycle
SHA-256 sealedGP issues quarterly capital call. Notice hash-anchored; LPs receive cryptographically verifiable PDF + companion JSON in their portal.
LP acknowledges within commitment window. Each LP's signature event hash-chained to its capital-call parent.
GP deploys called capital into SPV. Bank-feed reconciliation auto-anchors the event to the chain at the moment funds clear.
External fund administrator publishes quarterly valuation. NAV roll-up, fee accrual, and per-LP P&L hash-anchored.
Quarterly distribution executed. Each LP's distribution receipt hash-chained back through the call → deploy → valuation chain it traces.
Enterprise IdP surfaces: SAML, OIDC, SCIM
Production-verified SAML SSO, OIDC providers, and SCIM inbound provisioning. Your investor-admin team authenticates through your existing IdP — Okta, Azure AD, Google Workspace. Provisioning events land in the security audit log. When a team member is deprovisioned from the IdP, BasePro revokes their access inside the same cycle — not at the next support ticket. Joiner-mover-leaver runs through one control plane, not a list of usernames in a shared note.
Fund-team SCIM lifecycle
IdP-drivenPer-user permission overrides, without performance degradation
Role-level permissions define the baseline. Per-user overrides layer on top, atomic per CRUD action. A fifty-seat fund-admin team with three roles and forty-five individual overrides runs on a parameterised permission matrix, not a combinatorial explosion. Your compliance officer can hold read-only on one fund's transactions while an analyst has write on another. The override vocabulary speaks in nouns operators already use: view, create, update, delete, approve.
Per-user permission overrides
atomic per-actionRole baselines + per-user overrides. Every grant logged, every revoke audited, no permission drift.
Currency-agnostic configuration
Per-portfolio currency, per-property currency, automatic conversion at recorded FX rates, no Excel-based adjustment layer. When a portfolio spans MXN operations and USD-denominated investor capital, the consolidation report holds both, with FX conversion traceable back to the source rate and timestamp. Your LP statement arrives in the currency your LP asked for, with the conversion evidence attached, not appended.
Multi-currency rollup — fund P&L
FX-awareCross-LLC portfolio layer for fund structures
One fund with multiple underlying SPV, SAPI, or CKD entities, each with its own properties, rolls up into fund-level reporting. Portfolio-layer config for shared settings, per-property overrides where operations differ, one-country-per-org for regulatory clarity. The same architecture that serves a single-fund family office serves a multi-fund institutional platform. You add the next fund without adding the next reimplementation.
Portfolio cockpit
$324M AUM · 5 SPVsFund AUM
$324M
+8.4% YoY
SPVs
5
1,847 units
Avg occupancy
87%
AUM-weighted
Distributions YTD
$18.6M
On schedule
Units: 1,847 across 62 assets · Avg occupancy: 87% · Distributions YTD: $18.6M
Data residency, envelope encryption, ten-year retention
Choose the region that holds your data at signup — EU, US, or APAC. Sensitive personal data sits behind envelope encryption with per-organisation keys. Audit log retention extends to ten years. When your LP's legal counsel asks where the data lives, who holds the keys, and for how long the record is preserved, the answers are documented policy. Cross-border funds can align data residency to investor-jurisdiction preference without leaving the platform.
Enterprise tier, priced for fund-shape operations.
Custom pricing anchored to fund count, entity count, seat count, and compliance surface. No per-seat gotchas that fight the SSO rollout.
How BasePro reads against your current options.
Academy · Cohort 1 · for funds
One method across the portfolio.
Six weeks. Twelve modules. Cohort 1 trains the operators who run the platform that closes, audits, and reports on what you hold.
Walk us through your LP-reporting cadence.
We show you BasePro against your specific LP-report template, consolidation chart of accounts, and audit-evidence requirements. We open the call in the platform, not in slides.
Not ready? Explore by role: