AI implementation in banking

By · Updated · Published · Next update: when material evidence changes

AI implementation in banking needs a clear use case, suitable data and defined controls. This guide explains the decisions to review from initial scope through live operation. The bank’s responsible teams must set the requirements for the actual system.

Banking AI · 12-stage checklist · free CSV

A practical operating guide for banks and fintech companies implementing AI workflows and agents under model, vendor, security, compliance, and customer controls.

What AI in banking means in 2026

AI in banking covers both predictive models and tools that generate content or prepare actions. Fraud and anti-money laundering (AML), credit, service and operations have different control needs. The hard part is moving each use case into controlled production. Financial services AI consulting covers these decisions for banks.

Scope boundary: this guide is an operating framework, not legal, regulatory, audit, cybersecurity, model-validation, or financial advice. A bank must apply current requirements with its qualified owners and supervisors.

Published deployments

Banks leading in AI

Large disclosed bank programs include employee assistants, customer assistants and internal use cases. See the sourced comparison in banks leading in AI. Scale is not the same as value. A large deployment count does not prove a return on investment.

Compare the function, users, measurement period and source behind each claim. Access to a tool does not show active use. Interaction counts do not show cost savings. Use each case to frame a test for your bank's own workflow.

Workflow selection

AI use cases in banking, by function

Choose banking AI use cases by the work they support and the harm an error could cause. The examples below describe possible scopes, not client results.

FunctionBounded use caseEvidence before release
Fraud and AMLPrioritize alerts and prepare investigation summariesFalse positives, missed cases, reviewer decisions and escalation records
CreditDraft credit memos from approved recordsSource accuracy, missing evidence and the accountable credit decision
Customer serviceAnswer approved questions and prepare dispute responsesResolution quality, complaints, handoffs and access controls
OperationsPrepare know-your-customer (KYC) refresh files and reconciliation exceptionsCompleteness, error rate, processing time and human review
Software deliveryDraft code, tests and change documentationCode review, security tests, deployment approval and recovery plan
Agentic AI in banking

AI agents in banking

AI agents in banking prepare work that people approve: KYC refresh files, alert investigation summaries, credit memos and dispute responses. Coding agents can also support software teams.

Each customer, credit or payment action needs an owner, an audit trail and a way to reverse it. Start with one bounded workflow, a clear baseline and human approval at each high-impact step. For agent architecture and controls, see agentic AI consulting.

An agent can retrieve data, call a tool, change a record, send a message, or trigger another process. Control the action as well as the text response.

Access

Use least privilege

Separate read, draft, recommend, approve, and execute rights. Bind access to an identity, role, purpose, environment, and time.

Action

Set transaction limits

Require human approval or dual control for material, irreversible, customer-facing, financial, or regulated actions.

Attack

Test adversarial paths

Test prompt injection, poisoned retrieval, unauthorized tool calls, data leakage, secret exposure, excessive agency, and unsafe fallback.

Audit

Reconstruct each decision

Retain the version, input source, retrieved evidence, tool call, output, reviewer, override, action, time, and result where policy permits.

Change

Control model and vendor updates

Define change notice, regression tests, approval thresholds, rollback, emergency disablement, and vendor incident communication.

Outcome

Measure more than containment

Track task quality, customer effect, cost-to-serve, latency, adoption, overrides, complaints, incidents, and financial outcome.

Pilot-to-production gap

From pilot to controlled production

Move into production only when the workflow has an owner, a measured baseline and agreed release conditions. A demonstration shows an output. It does not prove that the bank can operate the complete workflow.

Register the models, vendors, data and decisions before release. Test representative cases and failures with material impact. Integrate human review, exceptions, audit evidence, incident response and a stop path. Limit the first release to named users and a defined scope.

Why banking AI pilots get stuck

Ownership

No accountable workflow owner

The innovation team runs the pilot. No business owner accepts the outcome, process change, residual risk or operating budget.

Evidence

No baseline or acceptance gate

The team measures model quality. It cannot show changes in cost, time, accuracy, customer effect, control performance or incidents.

Control

Risk joins after design

Risk teams review the system and contract too late. Model risk, compliance, legal, privacy, security and audit requirements remain unresolved.

Operations

The workflow stops at the API

The pilot omits identity, permissions, source systems, queues, human review, exceptions, monitoring, support and recovery.

Compare the pilot with the baseline before expanding its users or permissions. Record a decision to scale, revise or stop. Keep a named owner after launch.

Risk ownership

Governance, model risk and regulation

Banking AI governance assigns who may approve, change and stop a system. Model risk covers the possible harm from model outputs or their use.

Choose controls for the system's intended use, customer impact, data and jurisdiction. Record who validates the evidence and who accepts residual risk. A vendor's evaluation does not replace the bank's own acceptance decision.

The Federal Reserve's SR 26-2 guidance replaced SR 11-7 on April 17, 2026. It takes a risk-based approach to model risk management.

The guidance's scope note excludes generative and agentic AI models. Bank risk management and governance practices still determine controls for those systems. Do not treat the exclusion as permission to release without review.

12-stage implementation checklist

Banking AI implementation checklist

Each stage should produce a decision and evidence that its owner can review. Use the table as a working record throughout the system's life.

StageRequired decisionMinimum evidence
1. MandateName the workflow and executive objective.Current process, baseline, users, volume, cost, quality, risk, target, and stop conditions.
2. Intended useDefine what the AI system will and will not do.Affected decisions, customer impact, materiality, jurisdictions, users, and accountable owners.
3. InventoryRegister every model, vendor, component, and dependency.Versions, data sources, third parties, business owner, control owner, status, and change path.
4. Data and accessSet the minimum data and tool access.Rights, lineage, classification, security, privacy, retention, secrets, permissions, and logs.
5. Build or buySelect an architecture and delivery model.Requirements, due diligence, contract rights, concentration, change notice, continuity, and exit.
6. ControlsAssign decision rights and human oversight.Reviewer, approval, override, escalation, separation of duties, audit trail, and prohibited actions.
7. EvaluationSet thresholds before release.Representative cases, high-impact failures, quality, bias where relevant, security, latency, and cost.
8. IntegrationConnect the system to the real workflow.Interfaces, permissions, exceptions, fallback, incident process, customer contact, and support.
9. PilotApprove a bounded production release.Named users, limited scope, monitoring, issue log, adoption data, and scale or stop gate.
10. MonitorOperate within defined thresholds.Performance, drift, incidents, complaints, overrides, vendor changes, and outcome analysis.
11. ScaleExpand only from verified evidence.Benefit record, residual risk, control performance, capacity, training, funding, and approval.
12. ExitRetire or replace without losing control.Continuity, data return or deletion, customer effect, evidence archive, lessons, and next owner.

Download the banking AI implementation checklist to assign owners and record decisions.

Vendor diligence

Evaluate the complete third-party relationship.

The model is one dependency. Hosting, retrieval, monitoring, support, data processors, tools, integrators, and contract terms also affect the bank.

  1. Workflow fit: intended users, actions, data, languages, channels, volume, latency, exception rate, and customer effect.
  2. Technical fit: architecture, interfaces, identity, logging, model options, data location, portability, observability, and failure behavior.
  3. Risk evidence: security, privacy, validation access, model information, subcontractors, business continuity, incidents, and independent reports.
  4. Operating rights: use of bank data, training rights, change notice, audit, service levels, support, remediation, termination, deletion, and transition.
  5. Concentration and exit: critical dependencies, replacement time, retained knowledge, export formats, fallback, and orderly termination.

Paul Okhrem's AI due-diligence framework provides reusable decision records for this work. The AI governance checklist helps assign controls and their owners.

Success measures

Measure business value and control performance together.

Measure groupExamplesDecision it supports
BusinessCycle time, cost-to-serve, throughput, revenue, loss, customer retentionDid the workflow improve the intended outcome?
Task qualityAccuracy, completeness, consistency, exception rate, false positive and false negative costIs the system fit for its intended use?
CustomerResolution, complaints, wait time, access, fairness measures where relevantDid service improve without unacceptable harm?
ControlOverrides, unauthorized actions, incidents, response time, audit gaps, vendor changesAre controls operating at the required level?
AdoptionEligible users, active use, abandonment, workarounds, training, support demandHas the operating workflow actually changed?
EconomicsModel, infrastructure, integration, review, support, control, rework, and exit costIs the full operating case still positive?
Current primary sources

Use banking guidance that matches the system and date.

  1. Federal Reserve SR 26-2, Revised Guidance on Model Risk ManagementIssued April 17, 2026. It supersedes SR 11-7 and emphasizes a risk-based approach tailored to a banking organization's model risk profile, size, complexity, and use.
  2. Federal Reserve supervisory guidance on model risk managementCovers development and use, validation and monitoring, governance and controls, and vendor or third-party products. The guidance states that generative and agentic AI are outside its model scope, while bank governance should still determine appropriate controls.
  3. OCC Bulletin 2023-17, Third-Party RelationshipsInteragency guidance for planning, due diligence and selection, contract negotiation, ongoing monitoring, and termination across the third-party lifecycle.
  4. NIST AI Risk Management FrameworkVoluntary cross-sector framework for trustworthiness considerations across AI design, development, use, and evaluation.

Freshness note: older banking articles often cite SR 11-7 as current. The Federal Reserve states that SR 26-2 superseded SR 11-7 on April 17, 2026.

FAQ

Banking AI implementation questions.

How should a bank implement AI?

Start with one bank workflow, a named owner and a measured baseline. Define the intended use and risk level. Register the system and vendors, then set data and access controls. Test routine and high-impact cases, including human review and exceptions. Run a limited production pilot and track results and incidents. Scale only when the evidence supports it.

How do you secure AI agents in banking?

Give each agent the minimum data and tool access needed for its task. Separate read and write permissions. Require approval for high-impact actions. Validate inputs and outputs, restrict tools, protect secrets, log decisions and actions, test prompt and data attacks, monitor abnormal behavior, and provide a tested stop and recovery path.

How should a bank evaluate an agentic AI vendor?

Evaluate workflow fit, intended use, architecture, data rights, security, model and subcontractor dependencies, evaluation access, audit logs, human controls, change notice, monitoring, incident support, financial condition, concentration risk, continuity, contract rights, and exit. Test the vendor in the bank's own representative cases before production.

Why do banking AI pilots fail to scale?

Common causes are an unowned workflow, no baseline, unclear intended use, inaccessible data, late risk involvement, weak integration, vendor dependence, no representative evaluation, missing exception handling, low user adoption, and no scale or stop gate. A successful demo does not prove safe or valuable production operation.

How should a bank measure AI implementation success?

Measure business outcome, task quality, failure impact, customer effect, control performance, adoption, latency, operating cost, incidents, overrides, complaints, and model or vendor change. Compare results with the pre-implementation baseline and record an explicit scale, revise, or stop decision.

Paul Okhrem, AI transformation consultant and fractional Chief AI Officer, in Prague

Who compiled this banking AI guide

Compiled by Paul Okhrem, AI transformation consultant and fractional Chief AI Officer. Co-Founder and CEO of Elogic Commerce; Managing Partner at Uvik Software since June 2017. Paul compiles this research as part of his fractional CAIO work advising CEOs and boards on AI and agentic AI decisions.

This checklist is free to reuse under CC BY 4.0 with attribution.

Change log

  • : Reviewed service scope, decision guidance and supporting resources for the October release.
  • : Reviewed service scope, source evidence, links and buyer answers for the October release.
  • : Clarified dense passages while preserving source limits and commercial terms.
  • : Clarified the banking implementation guide’s scope, responsible owners and link to the advisory service.

Send a private brief to Paul Okhrem

Paul Okhrem, AI transformation consultant and fractional Chief AI Officer, in Prague

Tell Paul what you need to decide, who owns the decision and when you need to act. Review his background and published terms.

What happens next

Paul replies within two business days. If the work fits, you agree the scope, availability and terms before it starts.

An NDA, conflicts review and secure sharing process can be agreed before a detailed briefing.

Do not include passwords, customer or patient records, or confidential deal documents. An NDA and secure sharing process can be agreed before a detailed briefing.
Project details (optional)
Budget (optional)

Your brief is stored privately and read by Paul. Do not include passwords, customer records or confidential deal documents. The enquiry includes the page path, referring hostname and safe campaign labels when available. It excludes full referring URLs and search terms. Privacy and retention details.

Paul replies from paul@paul-okhrem.com within two business days.