To build ILAAP stress scenarios that regulators will accept, you need scenarios that are severe but plausible, directly tied to your institution’s specific risk profile, and supported by clear methodology and documented assumptions. Regulators are not looking for worst-case fiction; they want evidence that your bank has genuinely thought through how liquidity could deteriorate under realistic adverse conditions. This article walks through what regulators look for, which scenario types you need, how to calibrate severity, and the mistakes that most often lead to a failed review.
What do regulators actually look for in ILAAP stress scenarios?
Regulators look for ILAAP stress scenarios that are credible, institution-specific, forward-looking, and connected to real business decisions. They want to see that your stress testing framework reflects a genuine understanding of your liquidity vulnerabilities, not a compliance checkbox exercise built around generic assumptions. The quality of your narrative and methodology matters as much as the numbers themselves.
When supervisors review an ILAAP submission, they typically assess several dimensions. First, they check whether scenarios are tailored to your actual balance sheet composition, funding structure, and business model. A retail bank with heavy reliance on overnight deposits faces different liquidity risks than a wholesale-funded institution, and your scenarios need to reflect that difference explicitly.
Second, regulators look for internal consistency. The assumptions you apply to deposit outflows, asset liquidity, and contingent liabilities need to hold together logically. If you assume a moderate market stress but simultaneously assume no impact on secured funding markets, that inconsistency will attract scrutiny.
Third, supervisors want to see that stress results actually feed into decision-making. An ILAAP that produces stress outputs but shows no connection to your liquidity buffer sizing, funding strategy, or contingency planning will be viewed as a documentation exercise rather than a genuine risk management tool.
What are the main types of stress scenarios required in an ILAAP?
ILAAP stress testing frameworks typically require three core scenario types: an idiosyncratic stress scenario affecting only your institution, a market-wide stress scenario affecting the broader financial system, and a combined scenario that applies both simultaneously. This is standard supervisory expectation — the ECB’s ILAAP Guide, for instance, calls for scenarios covering institution-specific vulnerabilities, market-wide disruption, and severe downturns — and most regulators expect all three angles to be present and independently calibrated, even where the exact three-category structure is not spelled out verbatim in every jurisdiction’s guidance. It is worth noting that a precise tripartite taxonomy of this kind appears more explicitly in stress testing guidance such as EBA GL/2018/04, and supervisors across jurisdictions have broadly converged on the same expectation in practice.
Idiosyncratic stress scenarios
An idiosyncratic scenario models a stress event specific to your bank, such as a reputational shock, a credit rating downgrade, or an operational failure. The focus is on how confidence-sensitive funding sources would react if counterparties or depositors became concerned about your institution specifically. This type of scenario tests the resilience of your funding base when you cannot rely on market conditions being supportive.
System-wide stress scenarios
A market-wide scenario models broader financial system stress, such as a sudden drying up of wholesale funding markets, a sharp rise in interest rates, or a macroeconomic downturn that affects asset values across the sector. Here the question is whether your liquidity position remains adequate even when external funding sources are constrained for the whole market, not just for you.
Combined stress scenarios
The combined scenario is typically the most demanding, and regulators treat it as the primary test of your liquidity resilience. It stacks idiosyncratic and market-wide stresses simultaneously, reflecting the reality that institution-specific problems rarely occur in benign market conditions. Your liquidity buffer needs to be sized to survive this combined scenario over a defined survival horizon, usually a minimum of 30 days but often extended further for internal management purposes.
How severe should ILAAP stress scenarios be to satisfy regulators?
ILAAP stress scenarios should be severe enough to represent a genuine threat to your liquidity position, but not so extreme that they become implausible. Regulators generally expect scenarios to reflect conditions that are unlikely but realistic, often described as low-probability, high-impact events. The benchmark is not the absolute worst case imaginable, but a stress level your institution could plausibly face given historical precedents and current vulnerabilities.
Calibrating severity requires anchoring your assumptions to observable reference points. Past episodes of banking stress, such as periods of deposit outflows, funding market disruption, or rating-triggered collateral calls, provide useful benchmarks. Your assumptions on deposit run-off rates, secured funding haircuts, and drawdown rates on committed credit lines should be comparable to what institutions with similar profiles actually experienced during historical stress periods.
Regulators also look at the survival horizon. A 30-day survival horizon is a regulatory minimum in many jurisdictions, but supervisors increasingly expect banks to demonstrate resilience over longer periods, particularly for more moderate stress scenarios. Showing that your liquidity buffer can sustain you through a 90-day or longer stress event under a moderate scenario adds credibility to your overall framework.
One practical consideration: if your stress scenarios consistently produce comfortable results with large buffers to spare, regulators may question whether the severity is adequate. Scenarios that never come close to testing your limits suggest the calibration is too conservative to be useful. A well-designed stress framework should produce results that genuinely inform decisions about buffer sizing and funding strategy.
How does scenario design connect to a bank’s specific risk profile?
Scenario design connects to your risk profile by identifying the specific funding vulnerabilities, behavioral assumptions, and balance sheet characteristics that make your institution unique, and then building scenarios that directly stress those weak points. A scenario that does not reflect your actual liquidity risk drivers will not satisfy regulators and will not help you manage risk effectively.
Start by mapping your funding structure. What proportion of your funding comes from retail deposits, wholesale counterparties, secured markets, or central bank facilities? Each of these sources behaves differently under stress, and your scenario assumptions need to reflect those behavioral differences. Retail deposits from a large, diversified customer base tend to be more stable than short-term wholesale funding, but a reputational shock can change that quickly for a retail-focused bank.
Next, identify your contingent liquidity risks. Off-balance-sheet commitments, collateral upgrade triggers, margin calls, and intraday liquidity obligations can all generate sudden cash outflows that are easy to underestimate in a benign environment. Your scenarios should explicitly model these contingent claims under stress conditions.
Asset-side liquidity also needs to match your actual portfolio. If you hold assets that are liquid under normal conditions but become illiquid under stress, your scenario assumptions about asset monetization should reflect that deterioration. Applying standard HQLA haircuts to assets that may not actually be sellable under your specific stress scenario will overstate your available liquidity.
Dynamic balance sheet modeling helps here significantly. Rather than applying static assumptions to a fixed balance sheet, a dynamic model allows you to reflect how new business volumes, maturing positions, and behavioral changes interact with your liquidity position as the stress scenario evolves over time. This produces a more realistic picture of how your liquidity gap develops and where the critical pressure points emerge.
What common mistakes cause ILAAP stress tests to fail regulatory review?
The most common mistakes that cause ILAAP stress tests to fail regulatory review are generic scenario assumptions that do not reflect the institution’s actual risk profile, insufficient severity in stress calibration, weak linkage between stress results and management decisions, and poor documentation of methodology and assumptions. Each of these signals to regulators that the stress testing process is not genuinely embedded in how the bank manages liquidity risk.
Using industry-standard or template-based assumptions without customizing them to your balance sheet is a frequent problem. Regulators can identify when deposit run-off rates, secured funding haircuts, or contingent outflow assumptions have been copied from guidance documents without adjustment. Your assumptions need to be justified by reference to your own funding structure, counterparty relationships, and historical behavior.
Another common failure is treating the three scenario types as variations of the same stress rather than genuinely distinct analyses. Regulators expect each scenario to reflect a different stress narrative with its own internally consistent set of assumptions. If your idiosyncratic and combined scenarios produce nearly identical results, that suggests the scenarios have not been designed to stress different aspects of your liquidity risk profile.
Weak management action assumptions also attract criticism. Many institutions include optimistic assumptions about asset sales, new funding lines, or central bank access without adequately testing whether those actions would actually be available under stress conditions. Regulators want to see conservative assumptions about management actions, with clear evidence that your liquidity buffer is sufficient even if some planned actions prove unavailable.
Finally, poor model governance and audit trail documentation create problems during review. Regulators need to trace how assumptions were set, who approved them, and how they connect to stress results. Without clear configuration lineage and data traceability from source inputs through to final outputs, it becomes difficult to demonstrate the integrity of your stress testing process. Platforms that provide this traceability built into the workflow, rather than as a separate documentation exercise, make a meaningful difference when it comes to regulatory review. Our ICAAP/ILAAP solution is built around exactly this kind of embedded governance, giving you a clear audit trail across scenario design, model configuration, and stress results without needing a separate environment to manage it.
Frequently Asked Questions
How do we get started if our current ILAAP stress scenarios are mostly template-based and have never been challenged by regulators?
Start with a funding structure audit: map every material funding source, its behavioral characteristics under stress, and how it has actually performed during past market disruptions specific to your institution. Use that mapping to identify where your current template assumptions diverge most from your real risk profile, and prioritize those gaps first. You do not need to rebuild everything at once — a phased approach that addresses your highest-risk assumption areas first, with clear documentation of the rationale for each change, will demonstrate to regulators that you are moving in the right direction and that the process is genuinely owned by risk management rather than compliance.
What is the right survival horizon to use for each scenario type, and can we use different horizons for different scenarios?
Yes, using different survival horizons across scenario types is not only acceptable but encouraged by most supervisory frameworks, including ECB SREP guidelines. The combined scenario typically anchors to the regulatory minimum of 30 days, but internal management practice should extend the moderate idiosyncratic scenario to 90 days or beyond to demonstrate medium-term resilience. The key is to document the rationale for each horizon explicitly and ensure your liquidity buffer sizing is driven by the most binding scenario-horizon combination, not just the shortest one.
How conservative should our management action assumptions be, and which actions are regulators most skeptical about?
Regulators are most skeptical about three categories of management actions: asset sales that assume full market depth under stress conditions, access to new unsecured wholesale funding lines during an idiosyncratic event, and central bank facility drawdowns that have not been operationally tested. A sound approach is to apply a feasibility haircut to each planned action — asking whether this action would realistically be executable within the survival horizon under the specific stress narrative — and to size your primary liquidity buffer as if the most uncertain actions are unavailable. Any management action that relies on market conditions being cooperative during a stress event should be treated with particular caution.
How do we handle assets that appear liquid on paper but may not be sellable under our specific stress scenario?
The key is to distinguish between regulatory HQLA classification and your institution’s actual monetization capacity under the specific stress narrative you are modeling. An asset may qualify as Level 1 HQLA under LCR rules but still face significant liquidity constraints if your stress scenario involves a broad market dislocation or if your institution is simultaneously perceived as distressed. For each material asset category, document the conditions under which it can realistically be monetized, apply scenario-specific haircuts that reflect those conditions, and cross-check your assumptions against what institutions with similar portfolios actually achieved during comparable historical stress episodes.
What does 'internal consistency' mean in practice, and how do we check for it across our scenario assumptions?
Internal consistency means that every assumption within a scenario must be plausible given the same underlying stress narrative — if you model a severe market-wide stress, your assumptions about secured funding haircuts, interbank market access, asset prices, and deposit behavior all need to reflect that same environment simultaneously. A practical consistency check is to write a brief narrative description of each scenario as if it were a real event unfolding in sequence, then test whether each individual assumption makes sense within that narrative. Inconsistencies typically surface when assumptions are set independently by different teams without a shared scenario narrative anchoring them, so a cross-functional scenario review session before finalization is one of the most effective ways to catch these problems early.
How should we document our scenario methodology to satisfy regulators without creating an unmanageable documentation burden?
Effective regulatory documentation does not need to be voluminous — it needs to be traceable, logical, and clearly connected to your institution’s actual risk profile. At a minimum, document the stress narrative and its rationale, the source and justification for each material assumption, who reviewed and approved the assumptions, and how stress results feed into specific management decisions such as buffer sizing or contingency plan triggers. The most efficient approach is to embed this documentation directly into your stress testing workflow rather than maintaining it as a separate exercise, so that the audit trail is a natural output of the process rather than something reconstructed after the fact.
How often should ILAAP stress scenarios be updated, and what events should trigger an out-of-cycle review?
Most supervisory frameworks expect ILAAP stress scenarios to be reviewed at least annually as part of the full ILAAP cycle, but several events should trigger an out-of-cycle reassessment: a material change in your funding structure or business model, a significant shift in your credit rating or market perception, a major market stress event that provides new reference data for calibration, or a regulatory finding that questions your current scenario design. Treating scenario updates as a purely calendar-driven exercise is a common mistake — your scenarios should evolve in response to changes in your actual risk profile, and documenting what triggered each update strengthens your case with regulators that the framework is genuinely forward-looking.
Related Articles
- CRR3 and the Standardized Approach: How Revised Risk Weights Are Reshaping RWA in 2026
- When should banks upgrade regulatory reporting systems?
- How do you incorporate forward-looking scenarios in stress tests?
- What are sensitivity analysis and its role in risk management?
- What data sources are needed for comprehensive stress testing?
This content was generated with the help of AI and it may contain mistakes
