United Kingdom

PRA SS1/23

Supervisory Statement SS1/23: Model risk management principles for banks

The UK banking regulator's five principles for how banks with internal capital models should find, govern, build, validate and patch every model they rely on, including AI and machine learning models.

SupervisoryRegulatory GuidanceDevelopers and deployersNot an AI-specific law
Regulator
Prudential Regulation Authority (Bank of England)
Adopted
17 May 2023
In force
17 May 2024
Sectors
Financial services
Penalties
None stated in the SS. It sets supervisory expectations; the PRA follows up through normal supervision, and the accountable Senior Manager (SMF) carries personal responsibility for the MRM framework.
Last verified
19 Oct 2026Official source

Summary

  • The PRA (part of the Bank of England) published SS1/23 on 17 May 2023; it took effect on 17 May 2024.
  • It treats model risk as a risk in its own right, like credit or market risk, and asks for a firm-wide framework with board-set model risk appetite and one named Senior Manager accountable.
  • It is built on 5 principles split into 23 numbered sub-principles: (1) model identification and risk classification, (2) governance, (3) development, implementation and use, (4) independent validation, (5) model risk mitigants.
  • It covers all models, whatever the technology, built in-house or bought from vendors, including models used for financial reporting.
  • Status (as of 2026-10-19): in effect. A light-touch update in April 2026 (LIAF01/26) only clarified paragraph 1.9. No AI-specific supplement has been issued; the PRA instead said in its October 2025 roundtables that SS1/23 is the yardstick for AI and ML.

Who it applies to

  • UK-incorporated banks, building societies and PRA-designated investment firms that hold internal model approval for regulatory capital: credit risk (IRB), market risk (Internal Model Approach) or counterparty credit risk (Internal Model Method). Para 1.2 and footnote 2.
  • Not in scope: firms without internal model permission, UK branches of third-country (non-UK) banks, credit unions, insurers and reinsurers. The PRA says out-of-scope firms may still find the principles useful.
  • A firm that newly receives internal model permission has 12 months from that grant to comply (para 1.9).
  • Vendors and consultants are not addressed directly, but footnote 3 notes they may find the SS useful because it sets the minimum bar their bank clients must meet.
  • Not extraterritorial. A non-UK company is reached only as a vendor, through the bank's own duties (Principle 2.6).

Key dates

  1. SS1/23 published alongside Policy Statement PS6/23
  2. Expectations take effect; initial self-assessment and remediation plans due before this date
  3. First of two PRA CRO roundtables on AI and ML under SS1/23 (second on 22 October)
  4. PRA publishes roundtable summary and slides on AI and ML model risk
  5. Updated SS1/23 issued via LIAF01/26, clarifying paragraph 1.9 (not a condition for internal model approval)
  6. Updated version in effect, per the PRA publication page
Full date record
Date Event
2023-05-17 SS1/23 published with PS6/23
2024-05-17 Expectations take effect; firms should have completed a first self-assessment and remediation plan before this date
2025-10-20 and 2025-10-22 PRA CRO roundtables with 21 firms on AI and ML adoption under SS1/23
2025-11-24 PRA publishes the roundtable page and slides
2026-04-16 Updated SS1/23 text dated 16 April 2026 (LIAF01/26 low impact amendments); only para 1.9 changed
2026-04-23 PRA page lists the updated version as published and effective on this date

Penalties and enforcement

  • The SS states no penalties. It sets out what the PRA expects; it is not itself a rule with fines attached.
  • In practice the PRA tests it through supervision: firms must keep a self-assessment and remediation plan and give them to the PRA on request (para 1.8).
  • Accountability is personal: the chosen SMF must have MRM written into their Statement of Responsibilities (Principle 2.2), which ties model failures to the UK Senior Managers regime.
  • April 2026 clarification: meeting SS1/23 is not a condition for getting internal model approval (para 1.9), but the expectations still apply once approval is held.

What it means for an Indian company

  • Indian banks with UK operations: check how you operate. A UK branch of an Indian bank is out of scope (third-country branch). A UK-incorporated subsidiary is in scope only if it holds internal model approval for capital. If neither applies, SS1/23 is optional good practice, though UK supervisors may still use it as a benchmark.
  • IT and analytics vendors (model builders, scorecard vendors, AI platform providers) selling to UK banks: your client must validate your model to the same standard as its own (Principle 2.6), verify your data and assumptions, and monitor your model on its own outcomes. Expect requests for development documentation detailed enough for an independent expert to replicate results (Principle 3.5), data lineage, bias testing evidence and monitoring packs.
  • Group model hubs in India (for example a captive centre building models for a UK entity): a UK subsidiary may rely on the parent's validation only if the group's standards match SS1/23 and the subsidiary checks relevance and tier on a standalone basis (Principle 2.6(c)).
  • Comparison with RBI: RBI's draft Guidance on Regulatory Principles for Model Risk Management (24 June 2026, still draft as of 2026-10-19) covers AI and ML models and picks up themes from RBI FREE-AI such as board-approved frameworks and model inventories. SS1/23 is a useful, more detailed template for what "good" looks like: model definition, tiering by materiality and complexity, SMF-style accountability, PMA governance.
  • One SS1/23-aligned MRM framework, extended with AI security and fairness controls, can serve UK, RBI and OSFI E-23 expectations together.

Obligations

Principle and sub-principle numbers are from section 4 of the April 2026 SS text; paragraph numbers are from sections 1 and 3.

Showing 30 of 30
IDObligationReferenceApplies toControls
PRASS123-01Run a self-assessment of the MRM framework against the principles, keep a remediation plan, update both at least annually, share findings with the board and be ready to give them to the PRA on requestParas 1.6 to 1.8Deployer
PRASS123-02If newly granted internal model permission, meet the expectations within 12 months of the grantPara 1.9Deployer
PRASS123-03Give the audit committee a report on MRM effectiveness for financial reporting models at least annually, in time to inform the external auditor's planningParas 3.7 to 3.8Deployer
PRASS123-04Adopt the PRA model definition to set MRM scope; consider applying MRM to complex, material rule-based methods; keep documented controls over non-model quantitative methodsPrinciple 1.1Both
PRASS123-05Keep a complete, firm-wide model inventory covering models in use, in development and decommissioned, recording purpose and use, operating boundaries, assumptions and limitations, validation findings and governance detailsPrinciple 1.2Deployer
PRASS123-06Give every model a firm-wide risk tier based on materiality (size and purpose) and complexity; for advanced techniques, factor in unstructured data, interpretability, explainability, transparency and potential biasPrinciple 1.3(a) to (c)Both
PRASS123-07Periodically validate the tiering approach itself, and independently reassess each model's tier at every validation and revalidationPrinciple 1.3(d) to (e)Deployer
PRASS123-08Board sets up a firm-wide MRM framework and a model risk appetite with measures for framework effectiveness, model approval, usage limits and exceptions, performance thresholds, and use of mitigants and expert judgementPrinciple 2.1(a) to (c)Deployer
PRASS123-09Board receives regular model risk reports against appetite and challenges the outputs, limits and fallback plans of the most material modelsPrinciple 2.1(d) to (e)Deployer
PRASS123-10Name the SMF(s) with overall responsibility for MRM, update their Statement of Responsibilities, and give them the resources, systems and authority to actPrinciple 2.2; para 3.6Deployer
PRASS123-11Keep board-approved MRM policies covering at least model definition, tiering, development standards, data quality, validation, performance monitoring, mitigants and model approval and change; review them as technology changesPrinciple 2.3(a) to (c)Deployer
PRASS123-12Add bespoke standards for material and complex model types and data-intensive models, including clear data quality rolesPrinciple 2.3(d)Both
PRASS123-13Document owners, users, developers and validators for every model, with the skills, independence and seniority each role needsPrinciple 2.4Deployer
PRASS123-14Internal audit periodically tests the whole MRM framework, validator independence and compliance, and reports to the boardPrinciple 2.5Deployer
PRASS123-15For vendor models, confirm they are validated to internal standards, verify vendor data and assumptions, validate your own use and monitor performance using your own outcomes; the board stays responsiblePrinciple 2.6(a) to (b)Deployer
PRASS123-16A subsidiary reusing a parent group's validation must show group standards meet SS1/23, check data relevance locally and set the tier on a standalone basisPrinciple 2.6(c)Deployer
PRASS123-17Give every model a clear purpose and design objectives, a conceptually sound technique, benchmarks against alternatives, and clear communication of limits and sensitivitiesPrinciple 3.1Developer
PRASS123-18Show development data is suitable, representative, free of inappropriate bias and privacy compliant; document and validate proxies and adjustments; record alternative and unstructured data in the inventoryPrinciple 3.2Developer
PRASS123-19Test models during development (backward-looking, forward-looking, sensitivity and challenger tests), hand over a monitoring pack, and retest after material changes, including cumulative changes in self-updating modelsPrinciple 3.3Developer
PRASS123-20Justify, record and validate expert-judgement model adjustments; treat recurring adjustments as a sign the model may need redesignPrinciple 3.4Both
PRASS123-21Keep development documentation detailed enough for an independent expert to understand and replicate the model, including enough detail on vendor models to validate their usePrinciple 3.5Developer
PRASS123-22Run models only on tested systems under quality and change control, and reassess system suitability periodicallyPrinciple 3.6Both
PRASS123-23Keep a validation function independent of developers and owners (separate reporting lines for internal model firms) with the standing to challenge and access to the boardPrinciple 4.1Deployer
PRASS123-24Independently review every model (inputs, calculations, outputs, conceptual soundness, data, judgements, extra testing), with depth set by tierPrinciple 4.2Deployer
PRASS123-25Verify that model inputs, code and integration, and output reports work as intended and are accurate and auditablePrinciple 4.3Deployer
PRASS123-26Monitor performance against thresholds on a tier-based schedule using benchmarking, sensitivity tests, override analysis and parallel outcomes analysis; have monitoring reports independently reviewedPrinciple 4.4Deployer
PRASS123-27Revalidate models periodically, at a frequency matching their tierPrinciple 4.5Deployer
PRASS123-28Run a firm-wide process for post-model adjustments (overlays and overrides): approval for material ones, results shown with and without them, independent review, documentation and triggers for removal or redevelopmentPrinciple 5.1Deployer
PRASS123-29Restrict or prohibit model use when serious deficiencies or performance breaches appear, and track the issue and remediation in the inventoryPrinciple 5.2Deployer
PRASS123-30For material models, define allowed exceptions (temporary, with PMAs, approved) and a maximum performance tolerance, and escalate exceptions promptly to owners, users, validators and senior managementPrinciple 5.3Deployer

Evidence an auditor will ask for

  • The latest annual self-assessment against SS1/23, remediation plan and board minutes showing they were presented.
  • The SMF Statement of Responsibilities naming MRM.
  • Board-approved model risk appetite statement with its measures and the latest report against it.
  • MRM policy and procedures, with version history and date of last review.
  • Model inventory extract (including decommissioned and in-development models) with tier, owner, validation dates and open findings.
  • Tiering methodology, plus evidence that AI and ML models were rated using explainability, bias and data complexity factors.
  • Development documentation and validation reports for a sample of high-tier models, including vendor models.
  • Monitoring packs, threshold breaches and actions taken.
  • PMA register with approvals, independent review and results shown with and without PMAs.
  • Exceptions log and escalation records.
  • Internal audit reports on MRM; the annual audit committee report on financial reporting models.

Common mistakes

  • Assuming SS1/23 covers only capital models. Once a firm is in scope, it covers all models used for business decisions, including AI and ML scoring models, marketing models and financial reporting models.
  • Writing a tiering policy that puts AI and ML at medium complexity or higher, then logging them as low in the inventory. The PRA called out this exact gap in its 2025 roundtable.
  • Monitoring dynamic AI models on a six-monthly cycle; the PRA said that may be too slow and suggested fallback models and, in extremis, kill switches.
  • Treating SHAP or LIME outputs as proof of explainability. The PRA's slides warned these tools can mislead when input features are correlated.
  • Relying on a vendor's own validation without checking it against internal standards or monitoring on the bank's own outcomes.
  • Letting overlays (PMAs) pile up year after year instead of fixing the model.
  • Assuming a UK branch of an Indian bank must comply; branches of third-country banks are out of scope.

Glossary

  • PRA: Prudential Regulation Authority, the part of the Bank of England that supervises banks, building societies and insurers for safety and soundness.
  • Supervisory Statement (SS): a PRA document setting out what it expects firms to do; it guides supervision rather than creating fines by itself.
  • Model risk: the chance of loss or harm from a model being wrong or being used for the wrong job.
  • IRB (Internal Ratings Based): an approach where a bank uses its own approved models to calculate capital for credit risk.
  • SMF (Senior Management Function): a named senior role under the UK Senior Managers regime, with personal accountability.
  • Model tiering: ranking models by how much damage they could do (materiality) and how hard they are to get right (complexity).
  • Validation: an independent check that a model is sound and fit for its intended use.
  • Post-model adjustment (PMA): an overlay, override or manual tweak applied to a model's output because the model misses some risk.
  • Operating boundaries: the range of data a model was built on; using it outside that range adds risk.
  • Dynamic model: a model that recalibrates or changes its parameters by itself as new data arrives, which includes many machine learning models.
  • Challenger model: an alternative model used to compare against and test the main one.

Key takeaways

  • SS1/23 is the UK's model risk rulebook for banks with internal capital models; in effect since 17 May 2024 and still current after a minor April 2026 clarification.
  • It is technology neutral, so predictive AI and ML models are covered as ordinary models, with AI traits (opacity, bias, unstructured data, self-updating) pushing them into higher tiers.
  • 30 obligations across 5 principles and 23 sub-principles, plus self-assessment and audit committee reporting duties.
  • The PRA's 2025 AI roundtable gave practical signals: align tiering with inventory, monitor dynamic models more often, be sceptical of explainability tools, plan fallbacks and kill switches.
  • Indian banks' UK branches are out of scope; Indian vendors are reached through their UK bank clients' vendor validation duties.

Official sources

This is general information, not legal advice. Last verified 19 Oct 2026 against the official source. Laws change; confirm the current position with qualified counsel before acting.

Check your readiness

See where your controls stand today with our free compliance gap assessment.

Start the gap assessment

Talk to us about AI Governance

We map PRA SS1/23 and the other rules that reach you onto one control set, and build the evidence your auditors and customers will ask for.

Explore AI Governance