Skip to content

FRM Exam Part II · Stress Testing Banks

Enterprise-Wide and Integrated Stress Testing for Banks

Updated 11 October 2026 · Fact-checked

Enterprise-wide (integrated) stress testing runs one coherent scenario across credit, market, liquidity and operational risk, then combines the impacts on earnings, losses and capital. It must capture risk interactions and feedback effects. To solve questions, sum impacts consistently, add interaction and second-round effects, and compare the result with capital.

Understand Enterprise-Wide and Integrated Stress Testing

A bank does not suffer one risk at a time. A severe recession raises loan defaults, cuts trading values, drains funding and increases operational failures, all together. Enterprise-wide stress testing applies a single, consistent scenario to every risk type and business line, then measures the combined effect on the bank's capital and liquidity.

The old approach was silo testing: the credit team, market risk team and treasury each ran their own scenario with their own assumptions. Results were then added up or simply reported side by side. This misses the fact that the same shock drives all of them, and that they reinforce each other.

Integrated stress testing fixes this in two ways. First, it uses common macro-financial scenario variables (GDP, unemployment, rates, spreads, equity prices, FX) for all models. Second, it models risk interactions and feedback effects. Examples: losses reduce capital, which triggers rating downgrades and higher funding costs, which hit net interest income and force asset sales at fire-sale prices, which cause further market losses. These are second-round effects. Feedback can also run through the wider economy: bank deleveraging cuts credit supply, which deepens the recession and raises defaults again.

Aggregation matters because simple addition is not neutral. Adding standalone losses at a high confidence level assumes perfect dependence and can overstate the total. But in a stress, correlations rise and diversification benefits shrink, so assuming normal-time diversification understates it. In a single-scenario stress, the usual practice is to add the impacts, since the scenario already fixes the state of the world, rather than apply diversification credit.

The output is projected pre-provision net revenue, losses, risk-weighted assets and capital ratios over the horizon, plus liquidity metrics. Management compares these with minimum requirements and buffers, and uses the result for capital planning, limits and contingency plans.

Key formulas to remember

Post-stress capital
Stressed capital = Starting capital + Pre-provision net revenue − Credit losses − Market losses − Operational losses − Other adjustments (taxes, dividends)
Include every risk's impact in the same scenario and same horizon.
Stressed capital ratio
Stressed ratio = Stressed capital ÷ Stressed risk-weighted assets
RWA usually changes under stress (migration, higher risk weights), so do not hold the denominator fixed unless told.
Total integrated impact
Total impact = Σ standalone impacts + interaction (second-round) effects
Interaction effects can be negative for capital, such as fire-sale losses or higher funding costs. Hedges may offset some impacts.
Capital buffer headroom
Headroom = Stressed ratio − Required minimum plus buffers
A negative figure means a shortfall that needs action.

How to solve Enterprise-Wide and Integrated Stress Testing questions

Use this method for numerical and conceptual questions on integrated stress tests.

  1. 1Identify the scenario and horizon, and confirm every risk uses the same one.
  2. 2List each risk's standalone impact: credit, market, liquidity (funding cost or fire-sale loss) and operational.
  3. 3Check the signs: losses reduce capital, revenue adds to it, and note any taxes or dividends.
  4. 4Add the second-round or feedback effects the question gives, such as higher funding spreads, asset-sale losses or RWA growth.
  5. 5Compute stressed capital, and stressed RWA if it changes.
  6. 6Divide to get the ratio and compare it with the minimum plus buffers to find headroom or shortfall.
  7. 7For conceptual questions, name the weakness (silo, static balance sheet, ignored feedback) and the improvement (common scenario, dynamic modelling, interactions).

Quickest way: Add, adjust, then divide

When to use it: Use when an MCQ gives several loss figures and asks for a capital ratio or shortfall.

  1. Write starting capital, then subtract all losses and add net revenue in one line.
  2. Add any feedback loss given in the question as one more deduction.
  3. Update RWA only if the question changes it.
  4. Divide and compare with the requirement.
  5. For concept options, pick the answer that uses a common scenario and includes interactions; reject simple standalone sums or diversification credit.

Common mistakes in Enterprise-Wide and Integrated Stress Testing

  • Applying diversification benefits between risk types inside a single stress scenario.

    Economic capital aggregation uses correlations, and students carry that habit over.

    Fix: In a scenario-based test the shock is already joint. Add the impacts; do not reduce them by a diversification factor unless the question says so.

  • Ignoring second-round effects.

    Students stop after the first-round losses.

    Fix: Always ask what the capital loss triggers: funding costs, downgrades, asset sales, credit supply cuts.

  • Holding RWA constant.

    It is simpler, and the question may not stress it.

    Fix: Check whether the scenario implies rating migration or higher exposures. If so, update the denominator.

  • Treating liquidity and solvency as separate tests.

    They are covered in different chapters.

    Fix: Remember they interact: capital losses cause funding runs, and fire sales cause capital losses.

  • Using inconsistent scenarios across business lines.

    Each team picks its own assumptions.

    Fix: Insist on common macro variables and horizon; inconsistency is a named weakness of silo testing.

Worked examples

Example 1

A bank starts with CET1 capital of USD 50 billion and RWA of USD 500 billion. Under a stress scenario over the horizon: pre-provision net revenue is USD 12 billion, credit losses are USD 20 billion, trading losses are USD 6 billion, operational losses are USD 3 billion. Taxes and dividends reduce capital by USD 2 billion. RWA rises to USD 520 billion. What is the stressed CET1 ratio?

Show the solution
  1. Stressed capital = 50 + 12 − 20 − 6 − 3 − 2.
  2. 50 + 12 = 62; 62 − 20 = 42; 42 − 6 = 36; 36 − 3 = 33; 33 − 2 = 31.
  3. Stressed ratio = 31 ÷ 520 = 0.0596.

Answer: About 5.96%. The starting ratio of 10% falls by roughly four points.

Example 2

Using the bank above, the capital loss triggers a funding spread increase that reduces net interest income by a further USD 1.5 billion, and forced asset sales add USD 2.5 billion of losses. RWA falls to USD 500 billion after the sales. The regulatory minimum plus buffers is 7%. What is the shortfall in capital terms?

Show the solution
  1. Second-round effects total 1.5 + 2.5 = USD 4 billion.
  2. Stressed capital = 31 − 4 = USD 27 billion.
  3. Stressed ratio = 27 ÷ 500 = 5.4%.
  4. Required capital at 7% = 0.07 × 500 = USD 35 billion.
  5. Shortfall = 35 − 27 = USD 8 billion.

Answer: The ratio is 5.4%, and the shortfall against 7% is USD 8 billion. Feedback effects worsened the result despite lower RWA, showing why ignoring second-round effects understates risk.

Exam tips

  • Questions often ask which feature makes a test truly integrated: look for a common scenario plus interactions and feedback.
  • Read whether the balance sheet is static or dynamic; dynamic tests allow management actions and RWA changes.
  • Watch the sign on each item and whether taxes and dividends are included.
  • Be ready to name the reasons aggregation is hard: different horizons, models and risk metrics across risks.
  • If an option says to simply sum standalone VaR figures, check whether the question is about scenario impacts or a risk measure.

Practice questions from Stress Testing Banks

Enterprise-Wide and Integrated Stress Testing: frequently asked questions

What is the difference between enterprise-wide and silo stress testing?

Silo testing runs separate scenarios for each risk type with their own assumptions. Enterprise-wide testing uses one consistent scenario across all risks and business lines and combines the results on capital and liquidity. It also captures interactions between risks.

How do you aggregate stress test results across risk types?

Apply a common scenario, estimate each risk's impact, then add the impacts to the capital calculation. Add interaction and second-round effects on top. Do not take diversification credit unless the method explicitly models it.

What are second-round or feedback effects in stress testing?

They are the further impacts caused by the first-round losses. Examples are higher funding costs after capital falls, fire-sale losses, and reduced lending that worsens the economy and raises defaults. They can make total losses larger than the sum of first-round impacts.

Why is it hard to integrate stress tests?

Risk types use different models, time horizons and metrics. Data may sit in separate systems, and feedback loops are hard to estimate. Governance is also needed to keep scenarios consistent.