For Investment Funds
Cross-border banking identifiers in one schema. Multi-currency P&L that rolls up without an FX spreadsheet in the loop. SHA-256 hash-chain audit log. Enterprise SAML, OIDC, and SCIM. The substrate your LPs already ask about, shipped before your first quarter-close.
The fund operator reality
T+30
typical LP-report lag after quarter-end
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.
4+
banking identifier formats across typical fund rails
Your fund routes capital across MX, US, and EU. CLABE, ABA, SWIFT, and IBAN each live in their own tool. Reconciliation is a Google Sheet that nobody wants to own. BasePro carries all four identifier formats in one banking schema, tagged to currency and country, with bank-feed reconciliation built on the same substrate. When a wire misses a day, you see it in the same view you see the rent roll.
0
SAML providers built into most real-estate platforms
Your investor-admin team lives in Okta, Azure AD, or Google Workspace. Your real-estate platform wants them to create separate logins and remember separate passwords. That is how access-provisioning errors happen, and how an ex-employee still has read access three months after separation. BasePro ships Clerk Professional+ SAML, OIDC, and SCIM surfaces. Your IdP is the source of truth. Deprovisioning is an automated event.
Excel
current state of most fund audit trails
Your LP asks whether a specific disbursement was altered after the fact. Your answer is a screenshot of an Excel row, a forwarded email, and a PDF from your accountant. BasePro's SHA-256 hash-chain audit log turns that answer into a cryptographic verification. The chain covers every write at the database layer, not only the transactions your application bothered to log.
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.
Every write to your fund's portfolio anchors to a cryptographic chain. Monthly partitions, nightly verification cron, 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 hash comparison with ten-year retention behind it. That is the substrate that lets your next LP update be a summary instead of a defense.
Clerk Professional+ surfaces production-verified SAML SSO, OIDC providers, and SCIM inbound provisioning. Your investor-admin team authenticates through your existing Okta, Azure AD, or Google Workspace. SCIM events emit to the security audit log. When a team member is deprovisioned from the IdP, BasePro removes their access inside the provisioning cycle. Your joiner-mover-leaver lifecycle runs through one control plane, not a list of usernames in a shared note.
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-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.
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 layer
Fund AUM
MXN 4.2B
USD 212M
12-month occupancy
SPV layer
AUM share
↑ ↓ keys cycle SPVs · click to lock
Unit layer · Occupancy
SPV-B · Build-to-Rent
Entering SPV-B · Build-to-Rent
The org creation dialog lets you pick the Supabase region that holds your data. Sensitive PII sits behind KMS envelope encryption with org-specific 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.
Custom pricing anchored to fund count, entity count, seat count, and compliance surface. No per-seat gotchas that fight the SSO rollout.
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: