The Internal Liquidity Adequacy Assessment Process has a reputation for being a large document that appears once a year and causes a scramble. It does not have to be that way. At its heart the ILAAP is a claim, backed by evidence, that your firm understands its liquidity risks and holds enough resources against them.
What the regulator is actually reading
The PRA is looking for a joined up story. Your risk appetite sets the limits. Your stress testing shows what happens when the world moves against you. Your buffer and your contingency funding plan show what you would do about it. If those pieces contradict each other, the document falls apart no matter how long it is.
A weekly note on treasury, liquidity and practical Python. No spam, unsubscribe any time.
Make the numbers tie out
The most common weakness is not a missing section. It is that the survival horizon in the stress testing does not match the buffer the treasury desk actually holds, or the early warning indicators never trigger the actions the plan describes. Tie the numbers together first, then write the narrative around them.
A good test. Pick one severe scenario and trace it from the trigger, through the buffer that absorbs it, to the specific management action. If you cannot follow that thread in five minutes, the reader cannot either.
Treat it as a living process
The firms that find the ILAAP painless are the ones that treat it as a process rather than a document. The limits, the stress scenarios and the indicators live in the day job. The annual submission is then a summary of something real, not a one off construction.
That shift, from document to process, is the whole game.
Get the next one in your inbox
A weekly note on treasury, liquidity and practical Python. No spam, unsubscribe any time.
Practitioner notes on treasury, liquidity, regulatory reporting and practical Python.
