Commercial & Retail Banking

Chapter 14
Banking Analytics and Artificial Intelligence

Bachelors Program in Banking Finance and Insurance
Commercial & Retail Banking   •   Bachelor

Banking Analytics and Artificial Intelligence

Introduction and Context

Commercial and retail banks generate extensive data through account transactions, loan applications, card payments, digital interactions, branch activity, credit-bureau reports, market prices and operational systems. Banking analytics converts these data into evidence for decisions. Artificial intelligence (AI), particularly machine learning (ML), extends traditional analytics by identifying complex patterns and producing predictions or recommendations.

Analytics does not replace banking judgement. It changes how judgement is informed, documented and monitored. A responsible bank must therefore connect data science with credit policy, risk management, consumer protection, information security, model governance and human accountability.

This chapter examines the use of analytics and AI for customer insight, credit decisioning, pricing, churn prediction, fraud detection and portfolio monitoring. It also evaluates explainability, bias, data governance, generative AI, model risk and human oversight.

Learning Objectives

By the end of this chapter, students should be able to:

  1. Distinguish descriptive, diagnostic, predictive and prescriptive analytics.
  2. Explain how banks use data in customer management, lending, pricing, fraud prevention and portfolio monitoring.
  3. Interpret important ML concepts, performance measures and validation methods.
  4. Evaluate model risk, explainability, bias, privacy and data-governance requirements.
  5. Assess appropriate uses and limitations of generative AI in banking.
  6. Recommend a responsible AI operating approach that preserves human accountability.

1. The Analytics Value Chain

The banking analytics value chain links a business question to an operational decision:

Business objective → data collection → data preparation → model or analysis → validation → decision integration → monitoring → review and improvement.

A technically accurate model can still produce poor business outcomes if the data are incomplete, the target is badly defined, the model is applied outside its intended population, or staff cannot act on its output.

1.1 Types of analytics

TypeMain questionBanking example
DescriptiveWhat happened?Monthly deposit balances
DiagnosticWhy did it happen?Reasons for increased delinquency
PredictiveWhat is likely to happen?Probability that a borrower defaults
PrescriptiveWhat action is preferable?Offer retention incentive to a customer
Automated decisioningCan a rule or model execute an action?Approve a low-risk digital loan

Traditional reporting usually describes historical performance. ML is especially useful where relationships are nonlinear, interactions are numerous or data are high-dimensional. However, a more complex model is not automatically a better model. A bank must consider accuracy, stability, fairness, interpretability, cost and operational feasibility together.

2. Banking Data and Governance

Banking data may be structured, such as balances, repayment histories and transaction amounts, or unstructured, such as call transcripts, documents and customer messages. Important data-quality dimensions include accuracy, completeness, consistency, timeliness, uniqueness and validity.

A useful distinction is between:

  • Internal data: deposits, payments, loan performance, product holdings and service interactions.
  • External data: credit-bureau records, public registers, macroeconomic indicators, market data and—where lawful—alternative data.
  • Labels: observed outcomes used for learning, such as default, fraud confirmation or account closure.
  • Features: explanatory inputs used by a model, such as debt-to-income ratio or payment history.
  • Sensitive or protected attributes: characteristics that may be legally protected or ethically sensitive, such as race, disability, religion or gender.

Data governance assigns ownership and controls across the data life cycle. A governance framework should identify the purpose of data collection, lawful basis, access rights, retention period, quality controls, lineage and deletion procedures. It should also distinguish data used for customer service from data used for consequential decisions such as credit approval.

A major statistical danger is data leakage: using information that was unavailable at the moment the decision would have been made. For example, using a later repayment status to predict the original loan default produces deceptively strong results. Another danger is sample-selection bias, in which the training sample does not represent future applicants or customers.

Privacy protection requires data minimisation, purpose limitation, secure storage, access controls, encryption and controlled sharing. Banks should not assume that removing names makes data anonymous; combinations of transaction characteristics can sometimes re-identify individuals.

3. Customer Insights and Personalisation

Analytics can segment customers according to needs, behaviour, profitability or lifecycle stage. Common techniques include rule-based segmentation, clustering, propensity models and customer-lifetime-value analysis.

Customer lifetime value estimates the expected economic value of a relationship. A simplified discounted formulation is:

CLV = ∑t=1T [(Rt − Ct) × pt] / (1 + r)t − A

Here, Rt is expected revenue in period t, Ct is expected servicing cost, pt is the probability that the relationship remains active in period t, r is the discount rate, T is the planning horizon and A is acquisition cost. The formula assumes that expected revenue and cost can be estimated consistently and that the discount rate reflects the time value of money and relevant risk. It is an estimation tool, not an accounting value.

Banks use such analysis to identify customers who may need financial education, suitable product recommendations or service intervention. Responsible personalisation must avoid manipulation, discriminatory exclusion and excessive targeting based on vulnerable circumstances. A customer who is likely to incur overdraft fees should not simply be targeted with more expensive credit; analytics should support suitable and transparent choices.

4. Credit Decisioning and Risk Measurement

Credit analytics supports underwriting, limit setting, early-warning systems and collections. A fundamental risk quantity is expected loss:

EL = PD × LGD × EAD

where PD is probability of default, LGD is loss given default and EAD is exposure at default. PD and LGD are probabilities or proportions expressed between 0 and 1, while EAD is a monetary amount; therefore EL is a monetary amount. The simple multiplication assumes that the estimates are defined for the same exposure, time horizon and default event. More advanced systems may use discounted cash flows, time-varying exposures and scenario-weighted estimates.

For example, if PD = 0.04, LGD = 0.45 and EAD = $50,000, then:

EL = 0.04 × 0.45 × 50,000 = $900.

This is an expected average loss, not a prediction that exactly $900 will be lost on the particular account.

4.1 Classification models

A logistic model estimates the probability of a binary outcome:

p = 1 / [1 + e−(β₀ + β₁x₁ + … + βkxk)]

Here, p is the estimated probability, e is the base of natural logarithms, β₀ is the intercept, βi are coefficients and xi are features. Logistic regression is useful because its coefficients and direction of association are comparatively interpretable. The model assumes a linear relationship between predictors and the log-odds of the outcome, although transformations and interactions may be added.

Tree-based methods, random forests and gradient-boosting models can capture nonlinear effects and interactions. Neural networks may be useful for large-scale text, image or behavioural data. Their complexity increases the need for robust validation and explanation.

4.2 Evaluation and validation

A credit model should be evaluated on data not used to fit it. A time-based split is often preferable to a random split because banking environments change over time. Key measures include:

  • Discrimination: whether higher-risk cases tend to receive higher scores. A receiver operating characteristic area under the curve (ROC-AUC) is commonly used, but it does not measure calibration.
  • Calibration: whether predicted probabilities correspond to observed frequencies. If 100 accounts each have predicted PD of 5%, approximately five may default over the relevant population and horizon, subject to sampling variation.
  • Confusion-matrix measures: precision, recall and specificity, selected according to the cost of errors.
  • Stability: whether performance remains acceptable across time, products, regions and customer groups.

Threshold selection is a business and policy decision. Rejecting a risky application may reduce losses but can also exclude legitimate borrowers. Models should therefore be assessed alongside affordability, responsible-lending obligations and access-to-finance objectives.

5. Pricing and Offer Optimisation

Banks use analytics to price loans, deposits, insurance-linked products and service packages. A lending rate must cover funding cost, operating cost, expected credit loss, capital usage, liquidity considerations and a return appropriate to risk. A simplified required-rate expression is:

Required yield ≈ Funding cost + Operating cost rate + Expected-loss rate + Capital charge + Margin

This is a conceptual pricing identity rather than a universal regulatory formula. Components must be measured on comparable annualised bases and adjusted for fees, timing, collateral, prepayment and tax where relevant.

Price optimisation models estimate demand elasticity, or the percentage change in demand associated with a one-percent change in price:

Elasticity = (% change in quantity demanded) / (% change in price)

Pricing models can create unfair outcomes if they use proxy variables for protected characteristics or exploit customers with limited financial literacy. Governance should require documented price factors, fairness testing, affordability checks and clear communication.

6. Churn Prediction and Customer Retention

Churn models estimate the probability that a customer will close an account, become inactive or transfer balances. Features may include declining transaction frequency, unresolved complaints, fee increases, digital disengagement and competitor interactions where lawfully available.

The model output should be linked to an intervention decision. A retention action is justified only when its expected benefit exceeds its cost and is suitable for the customer. A simple decision rule is:

Act if pchurn × Benefit of retention > Cost of intervention

The inequality assumes that pchurn is estimated for the relevant time horizon and that benefit and cost are measured on a comparable basis. It does not justify contacting every high-risk customer: the intervention may be ineffective, intrusive or inappropriate.

Churn models can suffer from label ambiguity. A customer may appear inactive because of seasonality, migration to another channel or temporary financial difficulty. Analysts should define churn precisely and test performance by product and customer segment.

7. Fraud Detection and Portfolio Monitoring

Fraud detection combines rules, anomaly detection, supervised learning, network analysis and investigator judgement. Useful signals may include unusual device information, impossible travel, abnormal transaction timing, rapid changes in beneficiaries and links between accounts. Fraud is adversarial: criminals adapt when controls become known. Consequently, model monitoring must include emerging patterns and investigator feedback.

False positives can inconvenience legitimate customers, delay payments and damage trust. False negatives create direct losses and may expose the bank to regulatory or reputational harm. Thresholds should reflect transaction value, customer vulnerability, payment urgency and the possibility of rapid human review.

Portfolio monitoring aggregates account-level signals to identify concentration and deterioration. Important indicators include delinquency rates, roll rates, migration between risk grades, utilisation, sector concentration, geographic exposure and vintage performance. Early-warning systems should distinguish genuine deterioration from temporary volatility and should trigger documented escalation procedures.

8. Generative AI in Banking

Generative AI systems produce text, code, summaries, images or other content from prompts. Potential applications include summarising customer interactions, drafting internal reports, searching policy documents through retrieval systems, assisting software development and supporting employee training.

Generative AI is unsuitable for unsupervised final decisions on credit, fraud blocking or customer rights. Risks include hallucinated statements, outdated information, confidential-data exposure, prompt injection, copyright concerns, inconsistent outputs and automation bias. A retrieval-augmented system may reduce unsupported answers by grounding responses in approved documents, but retrieval does not guarantee correctness.

Controls should include approved use cases, restricted data inputs, logging, output verification, access management, red-teaming, vendor due diligence and a clear prohibition on treating generated text as authoritative without review. Generative AI may assist a credit analyst in summarising documents, but the analyst and institution remain responsible for the decision.

9. Explainability, Fairness and Responsible AI

Explainability concerns the ability to communicate how a system reached or supported an outcome. Interpretability generally refers to a model being understandable in itself; post-hoc explanation provides an approximation of the factors influencing a particular output. Explanations should be accurate, understandable and relevant to the decision. A feature-importance chart is not automatically a causal explanation.

Fairness has no single universal definition. Possible assessments include:

  • Group performance: compare error rates, calibration or approval rates across groups.
  • Individual fairness: similar individuals should receive similar treatment, subject to a meaningful similarity definition.
  • Outcome analysis: investigate whether differences reflect legitimate risk factors, historical disadvantage, data problems or prohibited discrimination.

Fairness criteria can conflict, especially when groups have different base rates. Therefore, banks must combine quantitative testing with legal analysis, domain expertise and affected-stakeholder review. Removing a protected attribute does not necessarily remove discrimination because proxy variables may remain.

A responsible AI framework commonly includes:

  1. Clear purpose and necessity assessment.
  2. Lawful, relevant and high-quality data.
  3. Pre-deployment validation and impact assessment.
  4. Documented model limitations and intended use.
  5. Human review and appeal mechanisms.
  6. Continuous performance, drift and fairness monitoring.
  7. Incident reporting, remediation and retirement procedures.

10. Model Risk and Governance

Model risk is the risk of adverse consequences from incorrect models, inappropriate use or errors in implementation. Sources include poor data, unsuitable assumptions, coding errors, unstable relationships, weak validation, data leakage, model drift and misuse by staff.

A sound model-governance lifecycle includes model inventory, risk classification, development standards, independent validation, approval, implementation testing, monitoring, change control and retirement. Documentation should cover purpose, population, variables, data sources, methodology, performance, limitations, overrides and approval history.

Model monitoring should examine both outcomes and inputs. Population stability, missingness, distribution shifts, calibration deterioration and changes in approval rates can signal drift. A model may remain statistically accurate while becoming unsuitable because customer behaviour, regulation or product design has changed.

Human oversight must be substantive. A reviewer needs authority, time, competence and access to relevant evidence. Merely requiring a person to click “approve” is not meaningful oversight. Override rates should be monitored because excessive overrides may indicate model weakness, poor workflow design or inappropriate incentives.

11. Applied Case: Illustrative Retail Lending Scenario

Background

Illustrative Bank is a mid-sized retail bank seeking faster decisions on unsecured personal loans. Existing underwriting relies on a scorecard, manual document checks and fixed policy rules. Processing is slow, and applicants with thin credit files receive inconsistent treatment.

Problem

Management proposes a gradient-boosting model using application data, repayment history, account cash-flow information and selected digital-behaviour variables. The bank must improve decision speed without creating unlawful discrimination or uncontrolled credit growth.

Analysis

The analytics team first defines the outcome as 90-day serious delinquency within twelve months of origination. It excludes variables unavailable at application time and removes post-origination information. Data are split chronologically: earlier loans are used for development and later loans for testing. Performance is assessed by discrimination, calibration, approval rate, delinquency, profitability and subgroup outcomes.

The team finds strong overall performance but poorer calibration for thin-file customers. It also discovers that a digital-behaviour variable is correlated with neighbourhood and age, creating a potential proxy concern. The variable is removed pending further evidence. The bank separately tests whether cash-flow data improve affordability assessment and whether customers have given appropriate permission for its use.

Approach and solution

The bank adopts a controlled champion–challenger process. The existing scorecard remains the champion while the new model operates in a monitored pilot. Applications near the decision threshold receive human review. Customers receive an understandable explanation of principal adverse factors and have a correction and appeal route.

An independent validation team reviews data lineage, leakage controls, calibration, fairness analysis, implementation code and stress performance. Limits are placed on approval rates and risk grades. Monthly monitoring examines drift, overrides, complaints, delinquency and subgroup outcomes.

Outcome

The pilot reduces average decision time and improves consistency, but it does not automatically approve every application with a high predicted probability of repayment. The bank retains affordability rules, fraud controls and human review. After monitoring confirms stable performance, the model is expanded gradually, with a formal review after material economic change.

Learning points

The case demonstrates that successful banking AI is not merely a modelling exercise. It requires a clearly defined target, time-appropriate data, independent validation, fairness assessment, explainable communication, controlled deployment and continuing accountability.

12. Professional Practice and Best Practices

Banking professionals working with analytics should:

  • Begin with a decision and customer outcome, not with a fashionable algorithm.
  • Establish data ownership, lineage, quality checks and lawful use before modelling.
  • Separate development, validation and operational approval responsibilities.
  • Use time-based and out-of-sample testing where appropriate.
  • Evaluate calibration, stability, costs and fairness—not only accuracy.
  • Document assumptions, exclusions, limitations and intended use.
  • Provide meaningful explanations and accessible appeal processes.
  • Monitor models after deployment and define escalation thresholds.
  • Protect confidential information in vendors, APIs and generative-AI tools.
  • Retain human accountability for consequential decisions.

Contemporary Developments

Current banking practice is moving toward real-time decisioning, open-banking data, graph analytics, privacy-enhancing techniques, cloud platforms and foundation models. These developments can improve inclusion and service quality, but they also increase dependency on data ecosystems, third-party providers and complex infrastructure. Regulatory expectations increasingly emphasise risk-based AI governance, transparency, resilience, consumer protection and demonstrable accountability. The central professional challenge is to obtain useful automation without treating statistical prediction as moral or managerial judgement.

Chapter Summary

Banking analytics transforms data into evidence for customer insight, lending, pricing, retention, fraud control and portfolio supervision. Descriptive and diagnostic analytics explain past events, while predictive and prescriptive analytics support decisions. ML can identify nonlinear patterns, but model complexity creates validation, explanation and governance demands.

Credit analytics uses concepts such as PD, LGD, EAD and expected loss. Model evaluation must consider discrimination, calibration, stability and the consequences of errors. Pricing and churn systems must link predictions to suitable, economically justified actions. Fraud and portfolio models require continuous monitoring because behaviour and threats change.

Responsible AI requires lawful and high-quality data, privacy protection, fairness assessment, explainability, independent validation, human oversight and lifecycle monitoring. Generative AI may assist employees but should not be treated as an autonomous authority in consequential banking decisions. Effective governance integrates technology with professional judgement, customer rights and institutional accountability.

Key Terms

Artificial intelligence: Systems that perform tasks associated with human intelligence, such as prediction, classification or language generation.

Analytics: Systematic use of data, statistical methods and models to support understanding and decisions.

Calibration: Agreement between predicted probabilities and observed event frequencies.

Churn: Customer cessation of a relationship or defined activity.

Data leakage: Use of information unavailable at the time of the intended prediction.

Data governance: Policies, roles and controls for managing data quality, access, use and protection.

Explainability: Ability to communicate how a model or system supports an outcome.

Expected loss: Estimated average loss, commonly PD × LGD × EAD.

Feature: Input variable supplied to an analytical model.

Generative AI: AI that produces new content such as text, code or summaries.

Human oversight: Meaningful human responsibility, review and intervention over an AI-supported process.

Machine learning: Methods that learn patterns from data for prediction or decision support.

Model drift: Deterioration or change in model behaviour as data or relationships evolve.

Model risk: Risk of adverse consequences from model error, misuse or inappropriate implementation.

Probability of default: Estimated probability that a borrower defaults over a specified horizon.

Proxy variable: A variable that indirectly represents a sensitive characteristic.

Sensitivity: Proportion of actual positive cases correctly identified.

Specificity: Proportion of actual negative cases correctly identified.

Validation: Independent assessment of whether a model is suitable, accurate and properly implemented.

Review Questions

Short Answer Questions

  1. Distinguish descriptive, predictive and prescriptive analytics.
  2. Define data leakage and explain why it is dangerous in credit modelling.
  3. What do PD, LGD and EAD represent?
  4. Why is calibration different from discrimination?
  5. State three risks associated with generative AI in banking.

Long Answer Questions

  1. Explain the banking analytics value chain and identify controls required at each stage.
  2. Discuss how a bank should evaluate a credit model before deployment.
  3. Explain why removing protected attributes may not eliminate discriminatory outcomes.
  4. Analyse the benefits and limitations of AI-based fraud detection.
  5. Describe a complete model-governance lifecycle for a retail bank.

Analytical / Application Questions

  1. A loan has PD = 0.03, LGD = 0.50 and EAD = $20,000. Calculate expected loss and explain what the result means.
  2. A churn model predicts a 20% probability of churn. Retaining a customer is worth $400 and an intervention costs $50. Using the simplified decision rule in this chapter, should the bank intervene? State the limitation of this calculation.
  3. Design a governance plan for a generative-AI tool that summarises customer-service calls, including privacy, accuracy, access, human review and monitoring controls.

Multiple Choice Questions with Answers

Question 1

Which type of analytics asks what is likely to happen?

A. Descriptive analytics

B. Diagnostic analytics

C. Predictive analytics

D. Prescriptive analytics

Correct Answer: C. Predictive analytics

Question 2

If PD is 0.04, LGD is 0.45 and EAD is $50,000, what is expected loss?

A. $90

B. $900

C. $4,500

D. $22,500

Correct Answer: B. $900

Question 3

What is data leakage in model development?

A. Encrypting data before storage

B. Using information unavailable at decision time

C. Deleting duplicate records

D. Splitting data by business unit

Correct Answer: B. Using information unavailable at decision time

Question 4

Which measure assesses whether predicted probabilities match observed frequencies?

A. Calibration

B. Specificity

C. Precision

D. Discrimination only

Correct Answer: A. Calibration

Question 5

Why can removing a protected attribute fail to eliminate discrimination?

A. Models cannot use numerical variables

B. Proxy variables may remain

C. All models become perfectly fair

D. Protected attributes are always required

Correct Answer: B. Proxy variables may remain

Question 6

Which is an appropriate use of generative AI in a controlled banking environment?

A. Making unsupervised final credit decisions

B. Blocking all suspicious payments without review

C. Summarising approved internal documents for staff

D. Replacing model validation

Correct Answer: C. Summarising approved internal documents for staff

Question 7

What is the main purpose of independent model validation?

A. To increase marketing expenditure

B. To assess suitability, performance and implementation independently

C. To guarantee that defaults never occur

D. To remove the need for monitoring

Correct Answer: B. To assess suitability, performance and implementation independently

Question 8

A fraud system that flags many legitimate transactions has a high rate of which problem?

A. False positives

B. False negatives

C. Data anonymisation

D. Calibration

Correct Answer: A. False positives

Question 9

Which principle requires collecting only data relevant to a stated purpose?

A. Data minimisation

B. Model drift

C. Overfitting

D. Adversarial adaptation

Correct Answer: A. Data minimisation

Question 10

Meaningful human oversight requires that reviewers have authority, competence and what additional feature?

A. No access to model evidence

B. Time and ability to intervene

C. A requirement to accept every output

D. Permission to ignore customer appeals

Correct Answer: B. Time and ability to intervene

Commercial & Retail Banking
Chapter 14 of 15