Generative AI in Banking: From Experiment to Core Infrastructure
This post is a written companion to a presentation I gave at a 2025 conference on Generative AI applied to banking. Downoad the presentation in PDF and PowerPoint.
The talk — “Generative AI in Banking”, a fifteen-slide, in-depth analysis prepared for technology directors of European banks — walked through where the economic value sits, which use cases are already live in EU institutions, how to architect for it, and what the EU AI Act demands of every deployment. This article covers the same ground in long form; if you attended the session, consider this the extended version of the deck.
The economic case: a productivity opportunity the size of a business line
- Customer operations — chat and voice assistants, agent support, call summarisation
- Marketing and sales — personalised offers, content generation, next-best-action
- Software engineering — code generation, testing, documentation, legacy migration
- R&D — research synthesis, product design, knowledge discovery
Europe is not waiting: generative AI is the current wave
- ~90% of significant euro area banks already use AI technologies (ECB, 2025 data). Fraud and cybercrime detection leads (used by more than half), followed by marketing (~50%), chatbots (40%) and credit scoring (30%).
- ~40% of EU banks already use general-purpose AI, led by customer support and internal-process optimisation (EBA RAQ, autumn 2024).
- 55% of surveyed banks use general-purpose or agentic AI in consumer-facing processes (EBA sample, 2025).
Three domains already deliver measurable value
1. Customer operations — the first production beachhead.
Volumes are high, text-heavy, and quality is measurable. Generative AI assistants resolve customer queries and answer employees’ questions on internal policies; models transcribe and summarise contact-centre audio and draft next-best responses for operators. Resolution rate, handle time and customer satisfaction give a clean before/after read — rare for AI projects. And because routine queries sit outside regulated decision-making, early deployments rarely trigger high-risk obligations.
2. Software engineering — your own developers are the fastest payback.
Banks use general-purpose AI to generate code from natural language, detect errors, support testing, convert between languages and migrate legacy systems — a structural problem in European core banking estates. Coding assistants can run against internal repositories under the bank’s own access controls, so no customer data leaves the perimeter. It also compounds: faster delivery accelerates every other AI initiative on the roadmap. For context, significant euro area banks invested over in digital technologies including AI in 2025 (~1.3% of tangible assets, ECB).
Risk and legal teams are text factories. Observed uses include monitoring legal and regulatory change, summarising court rulings, assessing contractual clauses, drafting regulatory reports and preparing audits. One boundary matters: drafting and summarising is low-risk assistance; deciding is not. Under the EU AI Act, AI used to evaluate creditworthiness or set credit scores is (Annex III), carrying conformity, data-governance, human-oversight and logging duties.
Architecture: one governed gateway, many models
Regulation has a calendar — plan backwards from 2026
- Aug 2024 — in force; governance structures set up. Start your use-case inventory.
- Feb 2025 — prohibitions on manipulative practices apply, plus the AI-literacy duty for staff.
- Aug 2025 — obligations for general-purpose AI models apply.
- Aug 2026 — high-risk obligations apply, covering creditworthiness assessment and credit scoring: data governance, human oversight, logging, conformity.
- Aug 2027 — extended deadlines for AI embedded in regulated products conclude the phase-in.
| Risk (as observed by the EBA) | Control (built into the platform) |
|---|---|
| Hallucinations and inaccurate output | Ground every answer via RAG over verified sources; block free-form generation in customer flows; human review for consequential replies |
| Input-data quality, governance and consent | Curated, versioned, quality-checked corpora; GDPR consent and purpose limitation enforced at the data layer |
| Reliance on third parties | Model routing as insurance: at least two qualified models per critical flow; DORA register, exit plans, portability tests |
| Opaque logic | Log prompts, sources and outputs; generate customer-facing reason statements from the same record |
The roadmap: foundation, scale, industrialise
- Foundation (months 0–6) — gateway MVP with routing, guardrails and logging; a full use-case inventory classified by AI Act risk tier; the first domain live (developer coding assistants, with a measured baseline).
- Scale (months 6–18) — three use cases in production across service, engineering and document work; a RAG platform with curated corpora; a second qualified model per critical flow.
- Industrialise (months 18–24) — high-risk conformity proven before August 2026; model validation, monitoring and retraining as routine; unit economics tracked (cost per resolved contact, per delivered feature).
What to do on Monday
- Stand up the GenAI gateway. Routing, guardrails, RAG and logging as shared infrastructure — not rebuilt per use case.
- Pick three measurable use cases. Start where the EBA sees production today: customer support, coding, document work.
- Classify before you build. AI Act risk tiering in the intake process; high-risk conformity ready before August 2026.
