Why Clients Ignore Your Wealth Portal: Seven Mistakes and the Fix for Each
Most wealth portals fail for fixable reasons: stale numbers, missing held-away assets, email attachments and one shared family login. Here are seven mistakes, the fix for each and how to score vendors on them.
Find out why clients stopped logging in before you change anything
If only a small share of invited households open your wealth management client portal in a given quarter, the interface is rarely the real problem. Clients stop logging in once they learn the portal isn't the most reliable place to get an answer. The number on screen is from yesterday. It leaves out the property fund they hold elsewhere. The tax pack arrives by email anyway. Once the portal becomes the second-best source, clients go back to phoning their adviser.
This guide serves one decision: reconfigure the platform you have, or replace it. It also sets out what to require from client portal software for wealth managers before you sign. The seven mistakes below turn up at private banks in Geneva and Singapore, independent wealth managers in London and Dubai, and multi-family offices in São Paulo and Mumbai. Regulations and data sources differ between those markets. The ways portals fail are much the same.
Start by measuring. Three internal numbers tell you most of what you need:
- Active households: the share of invited households that log in at least once a quarter.
- Document pickup rate: the share of statements and reports opened in the portal within 30 days of posting.
- Avoidable adviser queries: calls and emails asking for information the portal already shows.
Read them together. Healthy logins with low document pickup point to the vault. Low logins with many avoidable queries point to the data. Low numbers on all three usually mean nobody launched the portal properly, which is mistake seven.
Mistakes one and two: stale data and figures that contradict the adviser
Mistake one: showing yesterday's close as if it were live
Most portals load positions overnight, as a batch file from the portfolio management system (PMS). That's fine for a quarterly review. It fails the client who logs in during a market sell-off, sees a calm figure and hears a different number from the adviser that afternoon. Even when the overnight figure is correct, it looks wrong.
The fix: decide which data needs intraday refresh and which can wait for the overnight load. Prices for listed securities and cash balances usually justify intraday updates. Performance figures and alternatives don't. Then require a "valued as of" timestamp on every figure the client sees. When you assess vendors, ask three things:
- How long does data take to get from custodian to screen, broken down by asset class?
- Is intraday market data included, or is it a separate license? Exchange fees vary by venue and can add materially to running cost.
- Can the portal show live prices next to overnight positions without silently mixing them?
Mistake two: portal performance that differs from the review pack
This mistake does the most damage to trust. Take a hypothetical client who sees 6.1% year-to-date in the app and 5.4% in the adviser's quarterly pack. From then on, they believe neither. The usual cause is two calculation engines. The portal works out simple returns from position values; the report uses time-weighted returns from the PMS. The two may also treat fees differently (gross vs net), use different base currencies, or date cash flows differently (trade date vs settlement date).
The fix: keep one book of record. The portal should show results from the same performance engine as your reports, with the method labelled (time-weighted or money-weighted/IRR) and whether fees are deducted. Reporting currency should be the client's choice and consistent everywhere. Before go-live, reconcile a sample of 20 to 30 accounts between portal and report and tolerate nothing beyond rounding. Red flag: a vendor that says the portal "calculates its own performance for speed."
Mistakes three and four: consolidated views that leave out what clients actually own
Mistake three: no held-away assets
Wealthy families seldom keep everything with one firm. A typical multi-family office client might hold accounts at four custodians, a pension, two properties and a stake in an operating business. If the portal shows only the assets you hold, it may show half the family's wealth. The family keeps its own spreadsheet, and that spreadsheet becomes the real record.
The fix: make external-account aggregation a selection criterion, not a phase-two promise. How you connect depends heavily on region and asset type:
| Asset source | Typical connection | Usual freshness | Regional notes |
|---|---|---|---|
| Custodians you work with directly | SWIFT custody and cash statements (MT535, MT940 or ISO 20022 equivalents) or custodian APIs | Daily | Standard practice for private banks and family offices in Switzerland, Luxembourg, Singapore and the Gulf |
| Held-away bank and brokerage accounts | Open banking or open finance connections, or commercial aggregators | Daily, sometimes faster | UK and EU open banking covers payment accounts far better than investment accounts. India has the Account Aggregator framework and Brazil has Open Finance; in North America it's mostly commercial aggregators |
| Private equity, private credit and real estate funds | Data extracted from fund manager (GP) statements, or feeds from fund administrators | Quarterly, often one to four months behind | The same everywhere: the lag comes from the funds, not the portal |
| Direct property, art, private companies | Manual entry with a valuation date and source | Yearly, or when something changes | Valuation rules differ by jurisdiction; record the method used |
Mistake four: treating alternatives as an afterthought
Some portals lump private assets into a single "other" line, or omit them because valuations arrive late. Both mislead clients with large illiquid commitments. A family with a large share of its wealth in private markets needs to see what it committed, what has been called and distributed, the latest net asset value (NAV) and the date of that NAV.
The fix: look for platforms that track commitments and cash flows fund by fund, read capital call and distribution notices automatically, and flag stale valuations rather than hide them. Platforms built for consolidated reporting, such as Addepar, Masttro, Asset Vantage and Altoo, take different approaches here. Ask each to load three of your real fund statements during the proof of concept.
Mistakes five and six: documents sent by email and one login for the whole family
Mistake five: the vault exists, but documents still go by email
If advisers attach quarterly reports to emails, clients have no reason to log in. You also take on needless risk. Misaddressed emails are a familiar source of data breach notifications under laws such as the EU and UK GDPR, India's Digital Personal Data Protection Act, and the data protection laws of the UAE and Saudi Arabia. Regulators everywhere expect personal financial data to travel over a controlled channel.
The fix: make the secure vault the only way statements, tax packs, contract notes and KYC (know-your-customer) requests are delivered. Email or push notifications should carry no attachment and no financial detail. Configure the vault with:
- Two-way upload, so clients return KYC refresh documents and signed forms through the vault, not by email.
- Built-in e-signature, which removes the most common reason documents get printed and scanned.
- Retention rules by jurisdiction, since record-keeping periods differ by country and regulator.
- Clear data residency. Some clients and regulators, notably in Switzerland, the Gulf and parts of Asia, expect in-country storage or specific contractual controls. Confirm where the vault is hosted before you sign.
Red flag: a vault with no version history, no audit log of who opened what, or no client upload.
Mistake six: one login for each household
When the portal allows one login per relationship, families share passwords. That defeats multi-factor authentication and makes your audit trail meaningless. It also shuts out the people who matter more every year: adult children, a spouse who manages part of the family's affairs, an external accountant or lawyer.
The fix: an access model built around individuals. Each person has their own login, linked to the entities they may see: personal accounts, trusts, holding companies, foundations. Typical roles: the principal sees everything; a spouse sees joint and personal entities; the next generation sees selected entities in view-only mode; the accountant sees tax documents only, for a limited period. Ask vendors to demonstrate, not just describe, access limited by entity and document type, access that expires on a set date, and logging of every delegate action. Next-generation clients judge your app against their banking apps, so mobile needs the same permissions as the web portal.
Mistake seven: buying the demo instead of planning the rollout, and how to score vendors
The last mistake is about launch. Many firms treat it as an IT project. Clients get a welcome email, nobody shows them around, and advisers keep running reviews from PDF reports. Clients copy their adviser. If the adviser never opens the portal, the client won't either.
The fix: build the portal into the adviser's routine. Run review meetings from the portal screen. Activate the client's login during the onboarding meeting, not afterwards. Set an activation target for each adviser and review it monthly. The client experience depends on advisers using the portal as much as on the software.
When you shortlist vendors, score them directly against the six earlier mistakes:
| Criterion | What to require | Red flag |
|---|---|---|
| Data freshness | Time from custodian to screen for each asset class, with timestamps shown | "Real-time" claims with no detail by asset class |
| Performance consistency | One calculation engine shared with your reports | The portal calculates its own returns |
| Consolidation | Live feeds for held-away assets in your clients' main markets | Aggregation listed on the roadmap |
| Alternatives | Tracking of commitments and cash flows, with NAV dates | A single "other assets" line |
| Document vault | Upload, e-signature, audit log, a choice of hosting region | Download only, single region |
| Family access | Individual logins with entity-level and time-limited roles | One login per household |
On cost, these are indicative 2026 market ranges in USD. They vary widely by contract and region, so confirm with vendors. A white-label portal on top of your existing PMS might run a small or mid-sized wealth manager roughly $30,000 to $150,000 a year in license fees, plus $25,000 to $200,000 to implement. Consolidated reporting platforms for multi-family offices are often priced on reported assets, in the region of a few basis points, with annual minimums that can range from tens of thousands to several hundred thousand dollars. Digital front ends for private banks, built on core banking suites from vendors such as Avaloq or Temenos, or from specialists such as InvestCloud, can reach seven figures to implement. The main cost drivers are the number of custodian feeds, per-account aggregation fees, market data licenses, language support, in-country hosting and the complexity of your access rules.
Here's a decision rule. List which of mistakes one to six your firm is making. If three or more come from how the platform is built (a separate performance engine, no aggregation, no entity-level access), replace the platform. If they come from configuration and process, give yourself 90 days to fix them and re-measure the three adoption numbers before you issue an RFP.
Common questions
What is a realistic adoption target for a wealth management client portal?
Set your target against your own baseline rather than an industry figure. Measure the share of households that log in each quarter and the document pickup rate before and after your fixes. If the secure vault is the only way documents are delivered, pickup should rise quickly. If it doesn't, check the configuration before blaming clients.
Should we replace our portal or reconfigure it?
Replace it if the problems come from how it's built: a separate performance engine, no way to connect held-away accounts, or no entity-level access controls. If the problems are missing timestamps, documents still sent by email or a weak launch, fix those first. They cost far less.
Can a portal include held-away assets in every country?
Not equally. Open banking and open finance frameworks in the UK, EU, India and Brazil cover payment accounts better than investment and pension accounts, and commercial aggregators fill the gaps unevenly. For private banks and family offices, SWIFT statements from custodians and manual entry of illiquid assets remain essential. Ask vendors for coverage lists specific to your clients' main markets.
Do data protection rules restrict where a client portal can be hosted?
They can. GDPR, UK GDPR, India's DPDP Act and data protection laws in the Gulf all set conditions on transferring and processing personal data, and some regulators and clients expect in-country storage. Confirm where the vendor hosts data and which contracts cover it, and have qualified legal counsel in each relevant jurisdiction review the setup.
How should a multi-family office handle portal access for next-generation family members?
Give each family member a personal login linked only to the entities they're entitled to see, usually view-only at first. Avoid shared credentials entirely, because they break both security and audit trails. Agree the access rules with the principal in writing, and review them when family circumstances or trust structures change.
Written by the Apexlink Suite editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.