What generative AI can and cannot do in banking

How to study this topic

Generative AI can draft, summarise, search and explain controlled knowledge, but it cannot become an ungoverned decision-maker for credit, compliance, reporting or customer treatment. Read this as a banking control chapter, not as a technology marketing chapter. The useful question is whether the bank can trust, explain, control and monitor the result in banking GenAI governance.

The topic should stay close to banking evidence, policy ownership, customer outcome, regulatory expectation, data quality, operational process and audit trail. If the explanation drifts into generic AI language, it loses the reason this card exists.

A strong learner should be able to explain the model role, the evidence, the control owner, the human review point and the wrong-outcome risk to a business analyst, compliance analyst, credit-risk manager, developer, tester, auditor and senior risk owner.

Plain language meaning

In plain language, what generative ai can and cannot do in banking is about turning messy banking evidence into a controlled banking answer. The bank must separate observed fact, interpretation, model output and business action.

The model may classify, retrieve, summarise, estimate or rank, but the bank decides whether to approve, refer, investigate, escalate, communicate, provision, report or remediate.

Confidence in wording is not confidence in source quality, model design, policy authority or control effectiveness. Banking AI needs proof, not just fluent output.

Where it sits in the bank

This topic normally touches risk, compliance, product, operations, legal, data, model governance, technology and internal audit. Ownership must be explicit for source, policy, model, output and action.

The relevant population includes the banking cases described by the topic, including clean cases and edge cases: missing evidence, vulnerable customers, unusual products, disputed outcomes, local regulatory differences and manual overrides.

The same AI output can be low risk in internal learning and high risk when it affects a customer, control conclusion, finance number, regulatory response or audit file. Purpose matters.

Evidence and source material

Relevant evidence includes internal policy, approved procedures, regulatory text, control standards, audit findings, case notes, model documentation, risk appetite statements, source citations, approval records, and usage logs. These sources are not equal; official records, user-entered values, derived values, draft documents and approved policy need different trust treatment.

Timing matters because credit outcomes, policy versions, model versions, approval thresholds and customer status change. A correct answer for one date can be wrong for another date.

Evidence must be traceable to source, owner, version, date, access permission, transformation, retrieval path and limitation.

Data quality and control checks

Controls should include approved use-case register, human review, source grounding, prompt logging, data leakage prevention, hallucination checks, access control, legal review boundary, and incident escalation. These controls stop weak evidence from being treated as strong evidence and stop model output moving faster than governance.

Quality means authority, completeness, business meaning, lineage, label quality, fairness, privacy, security, citation quality, output review and customer impact.

When evidence fails, the response should be known: block, limit, refer, escalate, fallback, sample, remediate or retire the use.

How AI and ML can be adopted

Useful adoption includes summarising policy, drafting first-pass explanations, comparing procedures, finding relevant controls, and preparing analyst notes. These are support uses first; they improve search, classification, prioritisation, explanation, drafting and monitoring.

A bank should move from internal research assistance to controlled decision support and then to restricted automation only where validation, monitoring, accountability and fallback are mature.

The model role should be named with a verb: search, summarise, classify, estimate, recommend, refer, block, approve, escalate, report or communicate. Each verb has a different risk level.

Decision boundary and human judgement

The model may support judgement, but it should not erase judgement. The user must know whether the output is guidance, evidence, a draft, a score, a ranking, a referral trigger, a monitoring signal or a proposed communication.

Human review is useful only when the reviewer sees source evidence, reason codes, citations, limitations, model version, prompt context, retrieved documents and the policy rule being applied.

Overrides and corrections should be captured because they may reveal source gaps, policy ambiguity, retrieval weakness, model limitation or training needs.

Customer, compliance and conduct impact

The direct wrong outcome is a confident but unsupported answer being treated as bank policy, regulatory advice, customer communication or operational instruction. That is why the bank should not judge AI only by speed, test-set accuracy or user satisfaction.

A wrong model or unsupported GenAI answer can affect approval, decline, referral, complaint handling, compliance review, audit response, customer communication, collections, provisioning, capital, controls testing or regulatory reporting.

Conduct control asks what happens to the person, obligation, report or control affected by the answer. If the output creates pressure, exclusion, delay, weak disclosure or unfair treatment, it is a real banking risk.

Validation and monitoring

Validation should review concept, data, methodology, source quality, prompt design, retrieval quality, limitations, output behaviour and approved use.

Monitoring should look for drift, bad citations, outdated sources, repeated corrections, unfair outcomes, high override rates, weak explanations, user misuse, data leakage and missing audit trail.

When performance deteriorates, the response may be recalibration, retrieval tuning, source cleanup, stricter guardrails, retraining, manual review, restricted use, incident escalation or retirement.

Diagram walkthrough

The diagram follows five control steps: Bank knowledge, GenAI support, Control boundary, Human review, and Approved use. Read it left to right as a controlled banking flow from evidence or question through AI support and into accountable use.

Each box is a control point. A bank should be able to name the owner, source, rule, limitation and retained evidence at every step.

Bank-ready checklist

Before production use, check purpose, source authority, population, date, output role, customer impact, compliance impact and reproducibility.

Then check access control, validation, monitoring, override governance, audit evidence, fallback rules, incident response and business ownership.

If those controls are weak, the model may still produce an answer, but the bank should not treat the answer as trusted banking evidence.

Source anchors for accurate study

Basel credit-risk principles frame credit risk around a suitable credit-risk environment, sound credit granting, administration, measurement, monitoring and adequate controls.

The Basel Framework uses probability of default, loss given default and exposure at default as core credit-risk components for internal ratings based credit-risk measurement.

IFRS 9 is effective for annual periods beginning on or after 1 January 2018 and includes expected credit loss impairment requirements for financial instruments.

CECL under US GAAP estimates expected credit losses over the contractual life using historical experience, current conditions, and reasonable and supportable forecasts.

NIST AI RMF is a voluntary framework for managing risks to individuals, organisations and society from AI systems across design, development, use and evaluation.

US banking model-risk guidance expects model purpose, input quality, assumptions, limitations, validation, monitoring, governance, controls and effective challenge to be proportionate to model materiality.

Federal Reserve SR 26-2, dated 17 April 2026, supersedes SR 11-7 and SR 21-8 and attaches revised interagency guidance on model risk management for banking organisations.

The 2026 revised model-risk guidance states that generative AI and agentic AI are not within that guidance scope, while traditional statistical, quantitative and non-generative/non-agentic AI models are covered.

The EU AI Act treats AI systems used to evaluate the creditworthiness of natural persons or establish a credit score as high-risk; Union-law fraud-detection uses and prudential capital-requirement uses are carved out.

Banking practice note: definition ownership

For what generative ai can and cannot do in banking, definition ownership decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from internal policy through approved use-case register and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

AI adoption should make weak evidence easier to see, inconsistent treatment easier to challenge, outdated documents easier to detect and operational exceptions easier to route. It must not hide uncertainty behind confident language.

A good implementation records source, owner, version, date, transformation, retrieval path, model version, prompt context, user action, limitation, review decision and monitoring result.

Banking practice note: source authority

For what generative ai can and cannot do in banking, source authority decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from approved procedures through human review and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: effective-date control

For what generative ai can and cannot do in banking, effective-date control decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from regulatory text through source grounding and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: population design

For what generative ai can and cannot do in banking, population design decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from control standards through prompt logging and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: policy alignment

For what generative ai can and cannot do in banking, policy alignment decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from audit findings through data leakage prevention and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: model purpose

For what generative ai can and cannot do in banking, model purpose decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from case notes through hallucination checks and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: approved use

For what generative ai can and cannot do in banking, approved use decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from model documentation through access control and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: human review

For what generative ai can and cannot do in banking, human review decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from risk appetite statements through legal review boundary and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: output limitation

For what generative ai can and cannot do in banking, output limitation decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from source citations through incident escalation and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: fairness and conduct

For what generative ai can and cannot do in banking, fairness and conduct decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from approval records through approved use-case register and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: customer harm

For what generative ai can and cannot do in banking, customer harm decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from usage logs through human review and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: regulatory evidence

For what generative ai can and cannot do in banking, regulatory evidence decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from internal policy through source grounding and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: privacy and confidentiality

For what generative ai can and cannot do in banking, privacy and confidentiality decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from approved procedures through prompt logging and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: access control

For what generative ai can and cannot do in banking, access control decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from regulatory text through data leakage prevention and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: audit trail

For what generative ai can and cannot do in banking, audit trail decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from control standards through hallucination checks and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: change control

For what generative ai can and cannot do in banking, change control decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from audit findings through access control and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: monitoring thresholds

For what generative ai can and cannot do in banking, monitoring thresholds decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from case notes through legal review boundary and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: feedback loops

For what generative ai can and cannot do in banking, feedback loops decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from model documentation through incident escalation and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: exception routing

For what generative ai can and cannot do in banking, exception routing decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from risk appetite statements through approved use-case register and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: incident response

For what generative ai can and cannot do in banking, incident response decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from source citations through human review and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: committee reporting

For what generative ai can and cannot do in banking, committee reporting decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from approval records through source grounding and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: third-party dependency

For what generative ai can and cannot do in banking, third-party dependency decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from usage logs through prompt logging and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: training and user behaviour

For what generative ai can and cannot do in banking, training and user behaviour decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from internal policy through data leakage prevention and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: fallback operation

For what generative ai can and cannot do in banking, fallback operation decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from approved procedures through hallucination checks and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: retirement and redevelopment

For what generative ai can and cannot do in banking, retirement and redevelopment decides whether the bank can trust the evidence, explain the result and defend the action. A model can produce a fluent answer or a precise score quickly, but a bank still has to prove why that output is suitable for banking GenAI governance.

Trace one example from regulatory text through access control and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: definition ownership

Trace one example from control standards through legal review boundary and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: source authority

Trace one example from audit findings through incident escalation and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: effective-date control

Trace one example from case notes through approved use-case register and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: population design

Trace one example from model documentation through human review and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: policy alignment

Trace one example from risk appetite statements through source grounding and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: model purpose

Trace one example from source citations through prompt logging and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: approved use

Trace one example from approval records through data leakage prevention and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: human review

Trace one example from usage logs through hallucination checks and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: output limitation

Trace one example from internal policy through access control and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: fairness and conduct

Trace one example from approved procedures through legal review boundary and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: customer harm

Trace one example from regulatory text through incident escalation and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: regulatory evidence

Trace one example from control standards through approved use-case register and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: privacy and confidentiality

Trace one example from audit findings through human review and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: access control

Trace one example from case notes through source grounding and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: audit trail

Trace one example from model documentation through prompt logging and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: change control

Trace one example from risk appetite statements through data leakage prevention and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: monitoring thresholds

Trace one example from source citations through hallucination checks and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: feedback loops

Trace one example from approval records through access control and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: exception routing

Trace one example from usage logs through legal review boundary and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: incident response

Trace one example from internal policy through incident escalation and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: committee reporting

Trace one example from approved procedures through approved use-case register and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: third-party dependency

Trace one example from regulatory text through human review and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: training and user behaviour

Trace one example from control standards through source grounding and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: fallback operation

Trace one example from audit findings through prompt logging and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: retirement and redevelopment

Trace one example from case notes through data leakage prevention and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: definition ownership

Trace one example from model documentation through hallucination checks and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: source authority

Trace one example from risk appetite statements through access control and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: effective-date control

Trace one example from source citations through legal review boundary and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: population design

Trace one example from approval records through incident escalation and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: policy alignment

Trace one example from usage logs through approved use-case register and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: model purpose

Trace one example from internal policy through human review and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: approved use

Trace one example from approved procedures through source grounding and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: human review

Trace one example from regulatory text through prompt logging and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Banking practice note: output limitation

Trace one example from control standards through data leakage prevention and into the business use. If the team cannot trace that path without guesswork, the implementation is not mature enough for serious banking use.

Primary sources for further study

• NIST AI 600-1: Generative AI Profile
• NIST AI RMF: Measure playbook and data provenance