Summary The Internal Liquidity Adequacy Assessment Process (ILAAP) too often becomes an annual defence of the current liquidity position rather than a live framework governing funding and contingency. This article sets out how to design ILAAP governance that ties liquidity risk appetite to concrete limits, funding decisions and a credible contingency funding plan.
The core question ILAAP answers a simple question with hard implications: given the bank's business model, funding profile, deposit franchise and market access, how much liquidity does it need to hold, in what quality, and how does it fund itself under stress? Regulatory ratios (LCR, NSFR) are the floor; ILAAP is the bank's own view.
Liquidity risk appetite Liquidity appetite should be expressed in metrics the business can operate against: survival horizons under defined stresses, minimum buffers by currency, encumbrance limits, wholesale funding concentration limits, and single-counterparty limits. Statements the business cannot breach are decorative. Statements the business can breach — but does not, because the framework guides behaviour — are functional.
Stress testing Effective liquidity stress testing goes beyond regulator-defined scenarios. It includes idiosyncratic stresses (rating downgrade, litigation shock, cyber event affecting payment operations), market-wide stresses, and combined scenarios that recognise these can coincide. Survival horizons should be reported alongside the assumptions that produce them, not as headline numbers alone.
Contingency funding plan A contingency funding plan is only credible if it is testable. That means named funding sources with documented capacity, tested activation procedures, clear governance triggers, and a maintenance cycle that keeps assumptions current. A plan that has never been walked through in a simulation exercise is a document, not a plan.
Governance rhythm ALCO owns balance sheet execution within appetite. The CRO office owns framework, appetite challenge, and independent stress testing. The board risk committee approves appetite and monitors adherence. Escalation from ALCO to the board risk committee follows defined triggers, not discretion.
CRO and board implications Boards should see liquidity through three lenses: current position against appetite, forward-looking stress outcomes, and the health of the contingency funding plan. When any of the three is weak, that is the story to tell — not an averaged headline.
Practical implementation Documented liquidity risk appetite with cascaded limits; stress testing suite covering idiosyncratic, market-wide and combined scenarios; contingency funding plan with tested activation and annual simulation; ALCO reporting that separates position, forward view and contingency; board-level review at defined intervals.
Limitations Liquidity behaviour under severe stress is not fully predictable. Assumptions about deposit stickiness, market access and haircut behaviour should be explicit and revisited as evidence evolves; the framework should not project false precision.
Related reading See [Banking Risk](/expertise/banking-risk), [Financial Risk (Market and Liquidity)](/expertise/market-liquidity) and [Enterprise Risk](/expertise/enterprise-risk).
Frequently asked questions
What should risk leaders know about the core question?
ILAAP answers a simple question with hard implications: given the bank's business model, funding profile, deposit franchise and market access, how much liquidity does it need to hold, in what quality, and how does it fund itself under stress? Regulatory ratios (LCR, NSFR) are the floor; ILAAP is the bank's own view.
What should risk leaders know about liquidity risk appetite?
Liquidity appetite should be expressed in metrics the business can operate against: survival horizons under defined stresses, minimum buffers by currency, encumbrance limits, wholesale funding concentration limits, and single-counterparty limits. Statements the business cannot breach are decorative. Statements the business can breach — but does not, because the framework guides behaviour — are functional.
What should risk leaders know about stress testing?
Effective liquidity stress testing goes beyond regulator-defined scenarios. It includes idiosyncratic stresses (rating downgrade, litigation shock, cyber event affecting payment operations), market-wide stresses, and combined scenarios that recognise these can coincide. Survival horizons should be reported alongside the assumptions that produce them, not as headline numbers alone.
What should risk leaders know about contingency funding plan?
A contingency funding plan is only credible if it is testable. That means named funding sources with documented capacity, tested activation procedures, clear governance triggers, and a maintenance cycle that keeps assumptions current. A plan that has never been walked through in a simulation exercise is a document, not a plan.
What should risk leaders know about governance rhythm?
ALCO owns balance sheet execution within appetite. The CRO office owns framework, appetite challenge, and independent stress testing. The board risk committee approves appetite and monitors adherence. Escalation from ALCO to the board risk committee follows defined triggers, not discretion.