AcademyThe Net Stable Funding Ratio asks whether your balance sheet is structurally sound over a one year horizon, not just whether you can survive the next 30 days. This post works through ASF weights, RSF factors, an illustrative calculation, and what the ratio means for FTP design and funding strategy.
Regulators are not waiting for an AI rulebook before scrutinising automated workflows in treasury and risk. If your process executes sequential actions and routes outputs without human approval at each step, SS1/23 may already apply, whether your inventory reflects it or not.
Matplotlib, Seaborn, and Plotly each suit a different moment in the treasury and risk workflow. This post shows you which to reach for using worked examples including yield curves, HQLA correlation heatmaps, and cash flow waterfalls.
Liquidity risk moves in hours, and no single team holds the full picture. Here is who runs the position, who challenges it, who signs off, and why coordination is the real control.
Liquidity risk is not one number but five distinct risks that feed each other under stress. This post breaks down funding, market, contingent, intraday and structural risk, and shows how a small problem chains into a crisis.
Every liquidity rule you report against was written after a specific bank ran out of cash. This post maps each rule, the LCR, the NSFR, run off rates, HQLA definitions, the ILAAP narrative, back to the failure that caused it, so the frameworks stop feeling arbitrary and start reading as sensible answers to real problems.
A profitable, well capitalised bank can still run out of cash in days. Here is why liquidity fails so fast, and the buffers, HQLA, FTP, LCR and NSFR your treasury and risk teams use to stop it.