The manual process today (PE & VC portfolio tracking)
The recurring workflow that consumes analyst time every reporting cycle looks the same across offices: log into each portal with separate credentials, clear any 2FA prompt, locate the latest capital-call notice or distribution statement, download the PDF, rekey figures into the portfolio spreadsheet, cross-check currency, date and fund name, then repeat across every administrator.
With 10–20 fund positions spread across 5–8 administrators, that is a multi-hour task every quarter — sometimes more often when call notices arrive mid-cycle. Every manual step is a point of failure. A transposed figure, a missed document, or an out-of-date balance does not announce itself.
The structural cause: fund-administration portals were built for fund operations, not for the investor one step removed. Most have no API and no scheduled export. Nothing about that changes unless the extraction work is automated.
Manual vs automated — side by side
The table below compares the manual status quo with what Elementar delivers today, based on the live platform.
| Dimension | Manual process today | With Elementar |
|---|---|---|
| Time per cycle | Multi-hour extraction, per administrator, per period | Automatic extraction; portals checked twice daily; no staff time per cycle |
| Error / staleness | Rekeying introduces transcription errors; data as fresh as the last manual run | Every figure traceable to its source document |
| Unified view | Fragmented across portals and spreadsheets; no single view of fund positions, capital calls, distributions and NAV across administrators | One dashboard across all administrators and funds, PE and VC |
| Extraction accuracy | Untracked manual transcription errors | Uncertain fields flagged before reaching your dashboard |
| Credential security | Password managers, shared files, staff memory | Per-tenant encryption (Fernet, AES-128-CBC + HMAC-SHA256) in Azure Key Vault; never plaintext; 2FA automatic |
| Refresh cadence | As often as someone logs in manually | Portals checked twice daily; email digest on new data |
| Audit trail | Spreadsheet version history at best | Document library with original PDFs and extracted fields |
| Currency normalization | Manual, per administrator | 8 currencies normalized automatically |
| New portal onboarding | A new manual workflow each time | Any portal your office uses can be requested |
What Elementar extracts
Across all 20 connected fund-administration portals, Elementar reads 15 document types and extracts:
- Capital calls — amounts called per fund and period
- Distributions — amounts returned to investors
- NAV — net asset value per fund and reporting period
All figures are normalized across 8 currencies.
No API, no IT project
Fund-administration portals have no data feed your office can consume directly. Elementar works with portals exactly as they are: nothing for administrators to enable, no API contract to negotiate, no IT project to scope. You provide credentials once, securely. 20 portals are covered today — Buligo, Apex, Moonfare, Harbor Group, Aduro, Citco, Intralinks, Sun Holdings, Agora, Aminim Holdings, Orca, Clockwork Admin, iCapital, Alter Domus (CorPro), Flow Inc, BDO Admin, IBI Investment House Ltd, TitanBay, Carta, and NAV Fund Services — and you can request any other portal your office uses.
See the full list of covered portals and how extraction works on the portal coverage page.
Security: credential handling is a design constraint
Portal credentials are encrypted with per-tenant keys — Fernet, AES-128-CBC combined with HMAC-SHA256 — and held in Azure Key Vault. They are never stored in plaintext and no human reads your passwords. Portal access is read-only: Elementar can view and download documents, but no funds ever move. Elementar accesses each portal using the credentials you provide, in the same manner as you would yourself — it claims no authorization beyond the access rights you already hold.
Two-factor authentication is handled automatically. Data is processed and stored exclusively in European Azure regions (EU and Switzerland). Elementar is Swiss-domiciled and operates under nFADP and GDPR. Per-tenant isolation ensures no commingling between clients. Data is encrypted at rest with AES-256 (Azure Storage and Cosmos DB) and in transit with TLS 1.2 or higher.
See the full security overview on the platform page.
The direction: automating family-office operations
The automated data layer — extraction, normalization, unified reporting — is the proven first step. The longer-term direction is to automate the broader operational work that consumes analyst time each cycle: collection, reconciliation, distribution. Today you stop rekeying.
To see how this applies to your specific context, read the pages for multi-family offices and wealth advisors, or get in touch.