How to Prepare a Credible ILAAP Submission That Reflects Genuine Liquidity Risk Thinking
This guide sets out how to produce an ILAAP that demonstrates real liquidity risk understanding rather than template compliance. Readers will finish with a clearer view of what supervisors actually test, where submissions typically fall short, and how to build a document the board can defend.
An ILAAP is read as evidence of how a firm actually thinks about liquidity, not as a disclosure exercise. Supervisors can tell within a few pages whether the document reflects a live risk conversation among the executive and board, or whether treasury has pulled last year's file forward and asked risk to tidy the edges. The difference shows up in the specificity of assumptions, the honesty of the stress narrative, and the coherence between what the firm says it will do and what its contingency playbooks actually permit.
Key Executive Takeaways
- A credible ILAAP demonstrates that the board and executive genuinely understand the firm's liquidity vulnerabilities, not just that the LCR and NSFR are above threshold.
- The weakest submissions pass the numerical tests but fail to show linkage between business model, stress assumptions, early warning indicators, and contingency actions.
- Supervisors reward firms that identify their own weaknesses and explain the remediation path, not firms that present an artificially clean picture.
Start with the business model, not the metrics
The single most common failure is leading with regulatory ratios. Open instead with a precise description of how the firm generates, uses, and loses liquidity: which deposit cohorts are sticky and why, where funding concentrations sit, which intraday flows matter, and what the firm would struggle to replace in a stressed market. If the ILAAP cannot be read as a liquidity-eye view of the business, it will not persuade.
This matters because every assumption downstream, behavioural maturity, outflow rates under stress, collateral haircuts, HQLA monetisation timing, has to be defensible against that business description. Supervisors probe for inconsistency. A retail bank claiming 2% stressed outflows on a concentrated digital deposit book will be challenged, and rightly.
Make the stress testing argue with itself
Weak ILAAPs run idiosyncratic, market-wide, and combined scenarios that all produce survivable outcomes with comfortable buffers. That is a signal the scenarios are not biting. Good stress testing includes at least one scenario the firm barely survives, or does not survive without management actions whose feasibility is explicitly tested.
Name the reverse stress point. Identify the combination of outflows, market closures, and franchise damage that would exhaust the liquidity buffer, and state how far from that point the firm sits today. This is uncomfortable to write and far more credible than a document in which every scenario ends well.
Tie early warning indicators to actions, not dashboards
Most ILAAPs list EWIs. Few show that breaching an EWI triggers a specific decision at a specific forum within a specific timeframe. Map each indicator to the contingency funding plan action it would prompt, the governance body that would authorise that action, and the realistic execution window. Where the action depends on counterparty behaviour, central bank facility access, or asset saleability, say so and evidence it.
Test the plan. A CFP that has never been walked through with the operational teams who would execute it, treasury, collateral management, operations, communications, is not a plan. Supervisors increasingly ask for evidence of dry runs.
Address intraday honestly
Intraday liquidity is where many ILAAPs become generic. Describe peak usage, the buffer held against it, the monitoring cadence, and what happens if a key correspondent or CSD disruption occurs mid-session. If the firm relies on uncommitted intraday credit, say so and explain the mitigation.
Show the board actually engaged
The board attestation carries weight only if the paper trail supports it. Minutes should show challenge on assumptions, not approval of a treasury presentation. If the risk committee queried the deposit stickiness assumption and treasury revised it, document that. If the board set the liquidity risk appetite tighter than management proposed, show the reasoning. Supervisors read minutes alongside the ILAAP.
What good looks like
A strong ILAAP is shorter than most firms produce, specific where templates invite generality, and honest about the two or three liquidity risks that genuinely keep the CFO awake. It identifies gaps the firm is already remediating and gives a timeline. It reads as if written by people who would still believe it under cross-examination.
Next step
Before the next submission cycle, commission an internal read of last year's ILAAP against this question: if a supervisor asked us to defend any single assumption in the document, could we? Where the answer is no, that is where the work starts.
Frequently Asked Questions
How long should an ILAAP be?
Long enough to be complete, short enough to be read. Most run too long because they repeat regulatory text. Strip anything the supervisor already knows and expand on firm-specific judgement.
Should we disclose known weaknesses?
Yes. Supervisors find them anyway. A firm that identifies its own gaps and shows a credible remediation plan is in a materially stronger position than one that is caught presenting an incomplete picture.
How often should assumptions be refreshed?
Behavioural assumptions should be reviewed at least annually and whenever the deposit mix, product set, or market conditions shift materially. Document the review even where assumptions are unchanged.
Who should own the ILAAP internally?
Treasury typically drafts, risk challenges, finance validates numbers, and the CFO owns the submission with board approval. The weakness to avoid is treasury owning it end to end with risk providing only a sign-off.
What triggers supervisory follow-up most often?
Inconsistency between the ILAAP, the recovery plan, the risk appetite statement, and board minutes. Align these documents before submission.
Frequently asked questions
How long should an ILAAP be?
Long enough to be complete, short enough to be read. Most run too long because they repeat regulatory text. Strip anything the supervisor already knows and expand on firm-specific judgement.
Should we disclose known weaknesses?
Yes. Supervisors find them anyway. A firm that identifies its own gaps and shows a credible remediation plan is in a materially stronger position than one that is caught presenting an incomplete picture.
How often should assumptions be refreshed?
Behavioural assumptions should be reviewed at least annually and whenever the deposit mix, product set, or market conditions shift materially. Document the review even where assumptions are unchanged.
Who should own the ILAAP internally?
Treasury typically drafts, risk challenges, finance validates numbers, and the CFO owns the submission with board approval. The weakness to avoid is treasury owning it end to end with risk providing only a sign-off.
What triggers supervisory follow-up most often?
Inconsistency between the ILAAP, the recovery plan, the risk appetite statement, and board minutes. Align these documents before submission.
Related guides
How to Build a Credible ICAAP Narrative That Withstands Supervisory Scrutiny
This guide explains how to construct an ICAAP document that reads as a genuine articulation of risk, capital adequacy and board ownership rather than a compliance artefact. After reading, you will know what supervisors actually test for, where most narratives fall apart, and how to sequence the work so the story holds together under challenge.
How to Prepare for a Regulator Meeting When Rules Are Open to Interpretation
A practical guide for senior leaders preparing to meet a regulator on matters where the published rules leave genuine room for judgement. Covers how to build a defensible interpretation, sequence the conversation, and demonstrate the quality of your reasoning, not just your conclusion.
What Regulators Look For in a Submission: A Practical Guide
This guide explains what regulators actually assess when reviewing a formal submission, from authorisation applications to Section 166 responses and thematic returns. After reading it, you will know how to structure a submission that reflects genuine control, sound judgement and credible governance.
How to Structure a Section 166 Skilled Person Review Response
This guide sets out how senior leaders in regulated firms should structure their response to a Section 166 skilled person review, from the moment the requirement notice arrives to the remediation phase. It covers governance, evidence, stakeholder handling, and the judgement calls that determine whether the firm emerges credibly or damaged.
How to Prepare a Regulatory Filing With Stakeholder Risk Assessment
A practical guide for senior leaders on integrating stakeholder risk assessment into a regulatory filing so it reads as evidence of genuine control, not compliance theatre. After reading, you will know how to sequence the work, what to include, and where filings typically fall short under supervisory review.
Where internal confidence may exceed external evidence
Polar Insight helps leadership teams test critical assumptions against stakeholder, market, regulatory, and operational reality before risk compounds.
Explore Stakeholder Proximity