How to choose an investor portal

An investor portal is where your limited partners meet your back office. It holds capital call and distribution notices, capital account statements, quarterly reports, K-1s and other tax documents, and often subscription paperwork. LPs judge a manager partly by how easy it is to get these documents, and increasingly by whether their own systems can collect them without a person logging in.

This guide sets out what to evaluate, which standards matter, and what to ask vendors. It does not recommend a product. The registry data below is community research, and most entries are unverified, so use it to frame questions rather than to decide.

The requirements checklist

1. Investor experience

• One login across funds and vehicles. An LP in several of your funds, feeders or SPVs should see all positions in one place, with clear entity names.
• Delegated users. Institutional LPs send documents to consultants, auditors, custodians and administrators. Check how you grant and revoke access per entity and per document type.
• Search and filtering by fund, entity, document type and period, plus bulk download.
• Data, not only PDFs. Capital account balances, commitments, unfunded amounts and cash flows shown as data and exportable to CSV or Excel.
• Accessibility and language support if your LP base is international.

2. Document delivery and notifications

• Notifications by email when a document is posted, configurable per user and per document type.
• Whether the email contains only a link, or also a summary or attachment. Many LPs route these emails into automated intake, so consistent subject lines and sender addresses help.
• Read receipts and download tracking, so investor relations can see who has opened a notice.
• Versioning and corrections: how a restated statement replaces the original, and how LPs are told.

The registry records email notifications as available for 13 portals of the 32 LP and fund administrator portals it covers. For most of the rest, notification behaviour has not been checked.

3. Capital call and distribution workflow

• Generating notices per investor from the fund ledger, with allocation detail and wire instructions.
• Controls on wire instructions: how changes are approved, and how LPs verify them. Treat any change to wire instructions as a fraud risk.
• Tracking receipts against calls, with reminders for late payers.
• Structured notice data that follows the ILPA Capital Call and Distribution Template, not only a PDF.

For a deeper look at the LP side of this workflow, read how LPs automate capital call and distribution notices.

4. Fund administrator integration

If a third-party administrator keeps your books, the portal has to take its output reliably. Ask how documents and data move from the administrator into the portal: an API, SFTP drops, a file-naming convention, or manual upload. Ask who owns the mapping of investor entities between the two systems, and what happens when you change administrator. Some administrators run their own portal; then the question becomes whether you can also publish to a GP-branded portal without duplicate work. The administrator directory shows which administrators are linked to which portals in the registry.

5. Security: SSO, MFA and audit

• MFA for investors, with methods stated: TOTP apps, hardware keys, SMS or email codes.
• SSO for your staff through SAML or OIDC, and ideally SCIM for provisioning.
• Audit logs of logins, views, downloads and permission changes, exportable for your auditors and for LP due diligence questionnaires.
• Independent assurance reports such as SOC 2 or ISO 27001, penetration test summaries, and an incident notification commitment in the contract.

Few registry entries state these details yet: 2 entries list investor MFA methods and 1 lists SSO options. That is a gap in public documentation, not proof of absence, so ask.

6. Data residency and regulation

The registry records each vendor's country and the regions it serves, not where data is hosted. Ask for hosting regions, subprocessors and backup locations, and whether you can pin data to a region. EU fund managers should also check obligations under the Digital Operational Resilience Act, which applies from January 2025, covers alternative investment fund managers and requires a register of ICT third-party arrangements (Regulation (EU) 2022/2554). A portal vendor is one of those arrangements.

7. Machine access for LPs: API, MCP, SFTP and email

This item is newer, and it is where portals differ most. Institutional LPs, family offices and their administrators hold positions in many funds, so they automate intake rather than log in to each portal. Commercial services exist to do this for them: Canoe states that it covers more than 3,000 connected portals and uses APIs or RPA scripts to log in on clients' behalf (Canoe Connect), and Arch collects statements, capital calls and K-1s from portals and inboxes (Arch). When a portal offers no machine route, the LP's tooling stores credentials and drives your web interface, which is fragile for them and opaque for you.

The options, from most to least structured:

• API for investors. A documented API an LP can use with its own credentials, scoped to its own accounts. Distinct from a GP-side API, which lets you push data in but does nothing for LPs.
• MCP server. The Model Context Protocol lets AI assistants and agents call tools such as "list documents" directly. Public servers are listed in the official MCP Registry. See investor portals with an API or MCP server.
• SFTP feeds of documents and data files per investor, common with larger LPs and their administrators.
• Structured email with consistent metadata or attachments, which LP intake tools can parse.

Current registry research shows how rare investor-side access is. Of 32 LP and fund administrator portals, 0 list a self-serve API and 13 list a partner-only API, typically for the GP or administrator. 1 entry names LPs as an API audience. 6 portals offer an MCP server in some form, and 2 offer SFTP. A portal that gives LPs a sanctioned machine route removes a reason for scraping and a recurring support burden.

Standards to require

The 2025 ILPA templates

The Institutional Limited Partners Association updated its templates in 2025 (ILPA templates hub):

• Reporting Template v2.0 for fees, expenses and carried interest, released January 2025. It applies to funds in their investment period in Q1 2026 or launched on or after 1 January 2026 (ILPA Reporting Template).
• Capital Call and Distribution Template v2.0, replacing the 2011 template, with first delivery expected in Q1 2027 (ILPA Capital Call and Distribution Template).
• Performance Template v1.1, with granular and gross-up methodologies, for funds starting on or after 1 January 2026 (ILPA Performance Template).

ILPA publishes these as spreadsheet packages with definitions, not as an API or machine-readable schema. So ask vendors two things: can the portal produce each template, and can LPs get the underlying data in a structured form. Only 3 entries in this part of the registry list any ILPA template support today, which mostly reflects missing documentation.

Terms on automation

Read the investor terms of use, not only your own contract. Many portal terms forbid robots, scraping or sharing credentials with advisers. The registry records this as an automation policy: 7 LP or administrator portals prohibit automated access in their terms, and for 25 the policy has not been checked. A ban on automation with no API leaves your LPs with manual downloads only. If the vendor prohibits automation, ask what sanctioned alternative it offers investors, and whether you as the client can enable it.

Questions to ask vendors

1. Can an LP, or an agent or administrator acting for that LP, retrieve its own documents and data without a browser? Through which channel, and at what cost to us or to them?
2. Is the API documented publicly? Who can get credentials: GPs, administrators, LPs?
3. Do you offer an MCP server? Is it read-only, and is it scoped to the user's own permissions?
4. What do your investor terms say about automated access and delegated access by advisers?
5. Which ILPA templates can you produce today, and are they available as data as well as PDF?
6. How do documents and data arrive from our fund administrator, and what breaks if we change administrator?
7. Which MFA methods do investors have, and can we enforce MFA? Which SSO and provisioning standards do you support for our staff?
8. What do your audit logs record, how long are they kept, and can we export them?
9. Where is our data hosted, who are your subprocessors, and can we choose a region?
10. How do you notify investors of new documents, and can LPs subscribe to changes programmatically, for example through webhooks or a change feed?
11. How do we export all documents, data and audit history if we leave?

How LP and administrator portals compare on access

The table is generated from the registry on every request. Each row links to a portal page with sources, notes and terms. Status values: available means documented and self-serve, partner only means it exists but needs a commercial agreement, and unknown means nobody has checked yet. For side-by-side views, see portal comparisons or the full list of LP portals.

Being protocol-ready

OpenInvestorPortal publishes a draft open protocol, OIPP, for this machine access problem. A portal implements a small read-only REST surface for accounts, documents, capital calls, distributions, capital account statements and change notifications, mirrored as MCP tools. The investor signs each request with its own key using HTTP Message Signatures (RFC 9421). No password or token is shared with anyone, the portal decides what each link may read, and it can revoke a link at any time. Payloads are intended to follow the 2025 ILPA templates. No portal in the registry supports it yet; the specification is a draft.

You do not need to adopt the protocol to benefit from its design. A portal is protocol-ready when it keeps stable document identifiers, typed document metadata, ILPA-aligned notice data, a feed of what changed, and per-investor access scopes. Those same properties make any API, SFTP feed or future standard easier to support, and they shorten LP due diligence. How the protocol works explains the trust model in more detail.

Frequently asked questions

Sources

• ILPA, updated templates hub
• ILPA Reporting Template v2.0
• ILPA Capital Call and Distribution Template v2.0
• ILPA Performance Template v1.1
• Canoe Intelligence, Canoe Connect
• Arch, product overview
• Regulation (EU) 2022/2554 (DORA)
• IETF RFC 9421, HTTP Message Signatures
• Model Context Protocol Registry
• Registry entries for each portal, linked in the table above, each with its own sources.