Banks, brokers and pensions in one model
Wealth products are judged on whether the whole picture is right. That picture is assembled from banks, brokers and pension providers, which are usually reached through different connectivity providers.
The problem
A wealth product that shows a client only part of their assets is not a wealth product. So the connectivity requirement is unusually wide: current accounts and savings from retail banks, holdings and transactions from brokerage platforms, and pension pots from providers whose interfaces look nothing like either.
Each is usually served by a different connectivity provider, so teams add one provider per asset class. Each addition brings its own consent flow, its own account identifiers and its own idea of what a position is.
The expensive part arrives later. When a provider is replaced, or when a client’s account starts being served by a different one, the identifiers change. Unless something upstream of the application keeps track, the same account appears twice, history breaks, and reconciliation becomes a project rather than a property of the system.
What VEREA does
One canonical account model across banking, brokerage and pension connections, with identity that survives a provider change.
- One canonical account, balance, position and security model across banking, brokerage and pension connections.
- A capability graph that answers whether a specific institution can deliver holdings, not only balances, through a given provider.
- Canonical account identity, so the same underlying account keeps one identifier when the provider behind it changes.
- Routing across providers by capability and observed behaviour rather than by whichever integration came first.
- Provenance on material fields, so a valuation can be traced back to the connection and the moment it was read.
What stays with you
VEREA is infrastructure. The parts of the problem that are your product, your policy or your regulatory responsibility remain yours.
- The end-user experience, including how you present consent and how you handle re-authentication prompts.
- Portfolio logic, performance calculation, tax treatment and anything else that is your product rather than your plumbing.
- Your provider contracts and credentials, and the commercial relationship with each provider.
Other solutions
Start with a connectivity audit
We look at the institutions and countries that matter to you against more than one provider, and write up the provider dependence, the failure handling and the operational duplication we find.