Consistent semantics, and a source for every field
A lending decision is only as defensible as the data it was made on. Connectivity that changes shape between institutions turns that into a standing risk.
The problem
Lending teams do not want more data. They want data that means the same thing every time. The difficulty in cash-flow underwriting is rarely reaching an institution at all; it is that the same concept arrives in different forms. Balances are reported against different definitions. Some providers enrich transaction descriptions; others pass them through as the bank sent them. History depth varies by institution and can vary by provider and by account.
An application that absorbs those differences ends up encoding provider behaviour into credit logic, which is exactly where it should never live. The normalisation work gets written once per provider, drifts, and is rarely documented well enough to explain a decision months later.
The second problem is evidential. When a decision is reviewed, the question is not only what the balance was but where that figure came from and when it was read. If provenance was never captured at the point of ingestion, it cannot be reconstructed afterwards.
What VEREA does
One transaction, balance and liability model across institutions, with provenance recorded per field for review and audit.
- A canonical transaction, balance and liability model that does not change shape when the institution or the provider does.
- Normalised connection states, so an expired consent or a required re-authentication is one condition rather than several provider-specific ones.
- Provenance per material field, recording the provider, institution, connection, timestamp and source record behind it.
- Observability on data freshness and history depth, so you know what a decision was actually based on.
- Routing that takes required capability into account, so a connection that cannot deliver transaction history is known before it is offered.
What stays with you
VEREA is infrastructure. The parts of the problem that are your product, your policy or your regulatory responsibility remain yours.
- Affordability models, risk policy, scoring and every credit decision. VEREA does not score, decide or advise.
- How you obtain and present consent to the applicant, and what you tell them about the data you use.
- Retention and processing of the data once it reaches you, under your own legal basis.
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.