Use least privilege
Separate read, draft, recommend, approve, and execute rights. Bind access to an identity, role, purpose, environment, and time.
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.
A practical operating guide for banks and fintech companies implementing AI workflows and agents under model, vendor, security, compliance, and customer controls.
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.
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.
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.
| Function | Bounded use case | Evidence before release |
|---|---|---|
| Fraud and AML | Prioritize alerts and prepare investigation summaries | False positives, missed cases, reviewer decisions and escalation records |
| Credit | Draft credit memos from approved records | Source accuracy, missing evidence and the accountable credit decision |
| Customer service | Answer approved questions and prepare dispute responses | Resolution quality, complaints, handoffs and access controls |
| Operations | Prepare know-your-customer (KYC) refresh files and reconciliation exceptions | Completeness, error rate, processing time and human review |
| Software delivery | Draft code, tests and change documentation | Code review, security tests, deployment approval and recovery plan |
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.
Separate read, draft, recommend, approve, and execute rights. Bind access to an identity, role, purpose, environment, and time.
Require human approval or dual control for material, irreversible, customer-facing, financial, or regulated actions.
Test prompt injection, poisoned retrieval, unauthorized tool calls, data leakage, secret exposure, excessive agency, and unsafe fallback.
Retain the version, input source, retrieved evidence, tool call, output, reviewer, override, action, time, and result where policy permits.
Define change notice, regression tests, approval thresholds, rollback, emergency disablement, and vendor incident communication.
Track task quality, customer effect, cost-to-serve, latency, adoption, overrides, complaints, incidents, and financial outcome.
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.
The innovation team runs the pilot. No business owner accepts the outcome, process change, residual risk or operating budget.
The team measures model quality. It cannot show changes in cost, time, accuracy, customer effect, control performance or incidents.
Risk teams review the system and contract too late. Model risk, compliance, legal, privacy, security and audit requirements remain unresolved.
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.
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.
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.
| Stage | Required decision | Minimum evidence |
|---|---|---|
| 1. Mandate | Name the workflow and executive objective. | Current process, baseline, users, volume, cost, quality, risk, target, and stop conditions. |
| 2. Intended use | Define what the AI system will and will not do. | Affected decisions, customer impact, materiality, jurisdictions, users, and accountable owners. |
| 3. Inventory | Register every model, vendor, component, and dependency. | Versions, data sources, third parties, business owner, control owner, status, and change path. |
| 4. Data and access | Set the minimum data and tool access. | Rights, lineage, classification, security, privacy, retention, secrets, permissions, and logs. |
| 5. Build or buy | Select an architecture and delivery model. | Requirements, due diligence, contract rights, concentration, change notice, continuity, and exit. |
| 6. Controls | Assign decision rights and human oversight. | Reviewer, approval, override, escalation, separation of duties, audit trail, and prohibited actions. |
| 7. Evaluation | Set thresholds before release. | Representative cases, high-impact failures, quality, bias where relevant, security, latency, and cost. |
| 8. Integration | Connect the system to the real workflow. | Interfaces, permissions, exceptions, fallback, incident process, customer contact, and support. |
| 9. Pilot | Approve a bounded production release. | Named users, limited scope, monitoring, issue log, adoption data, and scale or stop gate. |
| 10. Monitor | Operate within defined thresholds. | Performance, drift, incidents, complaints, overrides, vendor changes, and outcome analysis. |
| 11. Scale | Expand only from verified evidence. | Benefit record, residual risk, control performance, capacity, training, funding, and approval. |
| 12. Exit | Retire 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.
The model is one dependency. Hosting, retrieval, monitoring, support, data processors, tools, integrators, and contract terms also affect the bank.
Paul Okhrem's AI due-diligence framework provides reusable decision records for this work. The AI governance checklist helps assign controls and their owners.
| Measure group | Examples | Decision it supports |
|---|---|---|
| Business | Cycle time, cost-to-serve, throughput, revenue, loss, customer retention | Did the workflow improve the intended outcome? |
| Task quality | Accuracy, completeness, consistency, exception rate, false positive and false negative cost | Is the system fit for its intended use? |
| Customer | Resolution, complaints, wait time, access, fairness measures where relevant | Did service improve without unacceptable harm? |
| Control | Overrides, unauthorized actions, incidents, response time, audit gaps, vendor changes | Are controls operating at the required level? |
| Adoption | Eligible users, active use, abandonment, workarounds, training, support demand | Has the operating workflow actually changed? |
| Economics | Model, infrastructure, integration, review, support, control, rework, and exit cost | Is the full operating case still positive? |
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.
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.
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.
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.
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.
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.

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