Four portals. One set of data.
Admin, broker, employer and employee all work in the same platform — each sees exactly what their role permits. Tenant separation is not a configuration setting; it is anchored in the database.
Broker portal
Portfolio, client files, advice, documents, reports.
Employer portal
Employees, contracts, payroll export, reports.
Employee portal
Contributions, contract details, funds, documents, requests.
Admin
Tenants, roles, permissions, data quality, feedback.
What the product does
This list contains only features that exist in the product today — nothing that is merely planned.
For brokers
- Client file per employer
- Employee detail view with contribution split
- Advice journey including power of attorney (DocuSign)
- Document inbox with extraction and matching
- Portfolio import: CSV, insurer files, Alte Leipziger sync
- Fund holdings with daily prices
- Insurer comparison
- Reports and client statistics
- Change management with a rule set
- Leaver administration
- User and permission management
- CRM integration (Pipedrive)
- "View as employee"
For employers
- Employee administration
- Contract overview for pensions and corporate health care
- Payroll export with a secure download link
- Document storage
- Reports and analyses
- Onboarding access for new joiners
- Import from HR systems and CSV
- Invitations individually or in bulk
- Own user and permission management
Platform foundations
- Role model with strict tenant separation
- Two-factor authentication
- Four languages: DE · EN · ES · FR
- Responsive for desktop, tablet and phone
For employees
- Dashboard with contribution, employee and employer share, and saving
- Contract details with fund allocation and performance
- Documents available at any time
- Profile and change requests
- Report a change of employer or a leaving date
- Guided onboarding
- Support chat
On the roadmap
- Native apps for iOS and Android
- Pay transparency analysis
- Further insurer interfaces
- Single sign-on
HR system upstream, payroll downstream
Benefits administration rarely fails on the subject matter. It fails on keeping the same data in two places. That is why the Pension Cloud deliberately sits between your systems: master data comes from the HR system, payroll figures go to payroll accounting. Nobody types anything twice.
Upstream · HR system
- Joiners and leavers
- Master data and personnel number
- Salary and salary changes
- Status changes: parental leave, sabbatical, sickness
- Cost centre and legal entity
tridion Pension Cloud
- Mapping person ↔ contract ↔ insurer
- Contribution and employer match logic including thresholds
- Insurer sync and document matching
- Roles, tenants, history, audit trail
- Portals for employers and employees
Downstream · Payroll
- Converted amounts per personnel number
- Employer match shown separately
- Tax- and social-security-free portions
- Changes as at the cut-off date
- Monthly export with a secure download link
Connected systems
Live means: present in the product and in use. Everything else is honestly marked as planned.
If your system is not listed
Integration runs through a generic framework with configurable field mapping — not through a hard-wired special case for each system. A new source system is therefore configuration rather than a project. And for anything without an API, file import remains, with duplicate detection and a protected source hierarchy: curated data is never silently overwritten by an import.