Skip to content

Industry · Financial services

AI agents for banks and insurers

Onboarding files, claims and credit dossiers run on documents and rules. That's the work AI agents can take on first, as long as they're connected to your core systems and stay inside your controls. That connection is the part Infosistema does.

At a glance

  • Infosistema connects AI agents to the core banking, policy and claims systems, data and security controls of banks, insurers and credit providers.
  • Typical first processes are customer onboarding and KYC, claims intake, credit dossiers, and back-office reconciliation.
  • Every engagement starts with a three-week analysis sprint that ends in a decision, process by process, and no agent starts with full autonomy.
  • The agents come from Vesster or from Google's Gemini Enterprise Agent Platform; Infosistema integrates them and works under ISO/IEC 27001 and ISO 9001 certified practices.
  • Infosistema has built and maintained systems for Santander Totta, Banco Invest and other banks and insurers; its 30 banking and insurance clients include CGD, BPI, Bankinter, Ageas, Liberty Seguros and Médis.

Talk to us

Where do AI agents fit in banking and insurance?

In processes with high volume and clear rules, where people spend the day collecting documents and re-keying data into a second system. Five of them come up in almost every bank or insurer we talk to.

Customer onboarding and KYC

The agent collects the documents a file needs, checks them against official sources, flags what's missing or inconsistent and hands a complete dossier to the analyst.

  • Stays with people: the acceptance decision and every case the agent flags.
  • Systems: onboarding front end, document repository, KYC and AML tools, official registries through bizAPIs.

Claims intake and triage

The agent reads the first notice of loss and its attachments, opens the claim with the right data, checks cover against the policy and routes the case by complexity.

  • Stays with people: cover decisions, settlement and any claim the agent flags as unusual.
  • Systems: policy administration, claims system, inbox and document repository.

Credit dossiers for companies

The agent assembles the dossier for a business credit request: company status, tax and Social Security position, annual accounts (IES) and beneficial owners, each with proof of source.

  • Stays with people: the credit analysis and the decision. Creditworthiness assessment of individuals is a high-risk use under the EU AI Act, and we treat it that way.
  • Systems: credit workflow, core banking, bizAPIs for official Portuguese data.

Back-office reconciliation and exceptions

The agent matches records between systems (payments, premiums, commissions), clears the routine differences and prepares the rest for a person with the evidence attached.

  • Stays with people: write-offs, adjustments and anything above the agreed threshold.
  • Systems: core banking or policy system, ERP, payment hub (for example aplonHUB).

Complaints and customer requests

The agent classifies incoming requests, drafts the reply from the customer's record and the applicable rules, and tracks the regulatory deadline.

  • Stays with people: sending replies on regulated matters and every complaint that needs a judgment call.
  • Systems: CRM, ticketing, document and knowledge repositories.

What makes agents hard to run in financial services?

Regulation, old systems and the cost of a wrong action. An agent in a bank touches accounts and personal data, so every action has to be logged and contained.

  • EU AI Act. Credit scoring of individuals and risk pricing in life and health insurance are high-risk uses. Most back-office agents are not, but each process is classified before we build.
  • DORA and outsourcing rules. Agents and the services behind them are part of your ICT risk perimeter: register, exit plan, incident reporting.
  • GDPR and banking secrecy. Agents get the minimum data the task needs, and the model's location is a design decision.
  • Core systems without modern APIs. Much of the work sits in systems built decades ago. Connecting to them safely is integration work, and it's most of the project.

How does Infosistema start?

With a three-week analysis sprint on a defined scope, for example retail onboarding or motor claims.

  1. Week 1: map the processes and systems in scope and short-list up to five candidates.
  2. Week 2: score each process for impact and for readiness (consequence of an error, volume, structure, data), and analyse it step by step with a baseline measurement.
  3. Week 3: estimate build and monthly operation for each agent, and recommend one of four outcomes: agent, agent with conditions, classic automation, or not yet.

Small agents on pains your teams already know can start in supervised mode from week 2. After that, an agent moves up four levels of autonomy (shadow, supervised, guided, autonomous), and only when its numbers against the baseline justify the step. One that takes part in a credit decision can stay supervised for good.

Which Infosistema products and partners help?

  • bizAPIs: official Portuguese business data (Tax Authority, Social Security, registries, IES, RCBE) as APIs, for KYC, credit and compliance agents. Zero data retention.
  • Vesster: governed enterprise agents for regulated processes, with an audit trail on every decision; deployable in your VPC, on-premises or air-gapped.
  • aplonAPI and aplonHUB: open banking and payments infrastructure from ACI Worldwide, delivered by Infosistema.
  • Google CoE: Gemini Enterprise Agent Platform, Vertex AI and BigQuery, when your bank runs on Google Cloud.

What has Infosistema built for banks and insurers?

Systems that run in production, many of them for decades. Agents are the newer part; the integration knowledge comes from this work:

Clients in the sector include Santander, Caixa Geral de Depósitos, BPI, Bankinter, Barclays, EuroBic, Crédito Agrícola, Ageas, Liberty Seguros, Médis and Ocidental. The full list, by sector, is on the clients page.

Frequently asked questions

Can AI agents be used in a regulated bank or insurer?

Yes, in most back-office and operations processes, with controls. Each process is classified under the EU AI Act before anything is built, the agent gets the minimum access it needs, and every action is logged. High-risk uses such as credit scoring of individuals keep a person deciding.

Which banking processes should get an AI agent first?

Processes with high volume, many documents and stable rules: onboarding and KYC, company credit dossiers, reconciliation and request handling. The analysis sprint confirms this for your case and also tells you where classic automation is cheaper.

Does the data leave our perimeter?

Only if you decide it can. Agents can run in your VPC, on-premises or air-gapped, with models chosen by data sensitivity. Official data from bizAPIs is not retained by bizAPIs.

How does this fit with DORA?

The agents, their platform and Infosistema as a provider enter your ICT third-party register like any other service. Each agent has a named owner, documentation, an audit trail and an agreed way to switch it off.

What does it cost to run an agent?

Operation is estimated in the analysis sprint, before any decision to build: monthly operation and maintenance, model consumption with a monthly cap, and infrastructure. The monthly report shows the cost per completed task.

Do you replace our core banking or policy system?

No. Agents work on top of the systems you have, through their APIs or through a service layer we add where no API exists.

Let's put AI to work in your bank or insurer

Tell us which process you'd like to look at first, and we'll reply within 1 business day.

Talk to us