SUNANDO ROY – On Banking, Finance and Society

 

A credible Contingency Funding Plan (CFP) is no longer a “good‑to‑have” regulatory artefact; it is the operational blueprint that determines whether a bank can navigate a fast‑moving liquidity event without entering resolution. This technical paper develops a practitioner‑oriented framework for embedding the High‑Quality Liquid Asset (HQLA) buffer as the first, and most immediately testable, line of defence within a modern CFP. It focuses on the distinction between regulatory eligibility and real‑world usability, and sets out expectations for banks and supervisors seeking to close that gap.

1. Rethinking the Contingency Funding Plan

1.1 From narrative to operational promise

At its core, a CFP is an institutional promise about behaviour under stress: if a funding shock occurs, the bank will detect it early, mobilise pre‑defined funding sources in a disciplined sequence, communicate coherently, and continuously reassess its position. This is fundamentally different from a descriptive document that restates liquidity policies and regulatory ratios.

A modern CFP should therefore:

• Define clearly the types of stress it covers (idiosyncratic, market‑wide, combined) and the severity assumptions for each.
• Specify quantitative and qualitative triggers that move the bank through clearly labelled stages of stress.
• Link each stage to a time‑bound set of actions across treasury, risk, finance, legal, operations, communications, and the C‑suite.
• Allocate decision rights explicitly, including escalation paths and conditions for Board involvement.
• Be demonstrably executable through simulations, war‑games, and desk‑level drills.

The first and most time‑critical test of this “operational promise” is the bank’s ability to answer a simple question under pressure: How much liquidity can you mobilise today, within hours, without relying on optimistic assumptions?

1.2 Positioning the HQLA buffer in the CFP architecture

The HQLA buffer is the primary liquidity firewall and should be treated as such in the CFP architecture. This has two implications:

1. The CFP’s early stages must be designed around the rapid verification and deployment of HQLA, not around more complex or slower measures such as asset sales or liability management exercises.
2. The definition of the buffer used for crisis decision‑making must be narrower and more conservative than the definition used for regulatory reporting.

In other words, the CFP should be built around “usable HQLA under stress,” not headline LCR‑compliant HQLA.

2. Early‑Warning and the Trigger Framework

2.1 Designing meaningful early‑warning indicators

Early‑warning indicators (EWIs) translate the abstract concept of “emerging stress” into objective, trackable signals. For CFP purposes, they must be:

• Quantitative where possible (for example, LCR trajectory, NSFR movements, intraday net cash flows, wholesale roll‑over ratios, deposit outflow rates, spreads on unsecured funding, market liquidity of key bonds).
• Calibrated with “traffic‑light” thresholds that align to CFP stages (e.g., Heightened Awareness, Contingency Activation, Crisis).
• Supplemented with qualitative indicators (rumours, social‑media narratives, rating‑watch announcements, sector‑wide events) that can accelerate escalation.

The critical feature is timeliness. Daily snapshots are inadequate in the kind of intraday runs observed in recent crises. Intraday monitoring of selected indicators, particularly for large deposits and wholesale funding, must be part of the regular surveillance infrastructure.

2.2 From triggers to time‑bound actions

Each trigger band should be linked to specific actions and time standards. Illustratively:

• Heightened Awareness (e.g., LCR trending down but above internal buffer): intensify monitoring, restrict non‑essential balance‑sheet growth, and run an updated HQLA verification within 24 hours.
• Contingency Activation (e.g., LCR approaching internal floor, pronounced market signals): full HQLA forensic within a fixed time (e.g., 60–90 minutes), pre‑positioning of additional collateral, preparatory contact with key repo counterparties and, where appropriate, central bank.
• Crisis (e.g., imminent or actual breach of regulatory or internal thresholds, severe outflows): immediate execution of the pre‑defined funding playbook, formal crisis governance activation, and full communication protocols.

This structure only works if the HQLA block is truly actionable in the time frames implied by the triggers.

3. Usable HQLA: From Regulatory Eligibility to Time‑to‑Cash

3.1 Regulatory HQLA versus operational HQLA

Regulatory definitions under the Liquidity Coverage Ratio recognise different levels of HQLA with specified haircuts and caps. For operational planning, however, three additional dimensions are critical:

• Time‑to‑cash: how long it actually takes to monetise a given asset under stress, considering settlement cycles, cut‑off times, and operational bottlenecks.
• Legal and accounting constraints: whether the asset can be sold, pledged, or repo‑ed without triggering adverse legal or accounting consequences.
• Market depth and stress behaviour: how price and market‑making capacity are likely to evolve under severe but plausible stress.

The CFP should therefore re‑express the HQLA buffer not as a single aggregated figure but as a time‑to‑cash ladder that overlays the regulatory levels.

3.2 Time‑to‑cash laddering

A practical operational taxonomy is:

• T+0 (Intraday): central‑bank reserves and securities already pre‑positioned at central‑bank or secured‑funding facilities, with legal documentation and eligibility pre‑cleared.
• T+1 (Next‑day): assets that can be monetised through repo or outright sale by the next business day, assuming realistic cut‑offs and a stressed (but functioning) market.
• T+2 and beyond: assets whose settlement or mobilisation lag makes them irrelevant for the first 24–48 hours of a severe run but still important for sustained stress scenarios.

Mapping the entire HQLA portfolio into these buckets reveals how much “firepower” truly exists in the decisive early hours of a crisis.

3.3 Typical structural weaknesses

When this lens is applied, recurring structural weaknesses often emerge:

• “Accounting traps”: Held‑to‑maturity (HTM) securities counted in internal HQLA figures despite the fact that their sale would taint the portfolio and trigger significant mark‑to‑market recognition, potentially undermining capital and confidence.
• Collateral fragmentation and double‑counting: treasury, derivatives, and repo functions keeping separate collateral inventories, leading to the same security being assumed available in multiple places.
• Eligibility mismatches: securities treated as “liquid” under internal and LCR views that are not eligible at key central‑bank facilities or with priority repo counterparties.
• Stale encumbrance and valuation data: reliance on month‑end or week‑end snapshots to infer available buffers during an intraday event.

An honest CFP needs to recognise these weaknesses and design controls that eliminate them before stress, not during it.

4. Pre‑Positioning: Converting Potential into Usable Capacity

4.1 Concept and rationale

Pre‑positioning means placing eligible collateral in the right legal and operational location ahead of time so that it can be drawn on quickly under stress. This has three main components:

• Lodging securities in central‑bank or secured‑funding facilities with all documentation, eligibility checks and legal opinions completed ex‑ante.
• Arranging tri‑party or custodian structures that support rapid allocation and substitution with minimal operational friction.
• Ensuring intraday access: aligning settlement cut‑offs, internal processing capabilities, and central‑bank facility windows.

Without pre‑positioning, securities held in ordinary custody accounts may require T+2 settlement to be transformed into cash or central‑bank balances, which is incompatible with a fast‑moving run.

4.2 Legal title and encumbrance

Pre‑positioned collateral must be clean in both law and fact. That requires:

• A comprehensive legal review to confirm there are no undisclosed liens, flawed pledges, or enforceability concerns.
• A consolidated encumbrance map showing, for each asset, all existing pledges, rehypothecation rights, and usage in payment‑system or clearing‑system arrangements.
• Controls that prevent the same security from being pledged for multiple purposes in a way that would compromise its availability at the moment of need.

The CFP should assume that any asset with ambiguous title or documentation is not part of the usable firewall.

4.3 Operational capacity and testing

Pre‑positioning is only as good as the bank’s ability to actually use the facilities in which collateral has been placed. The CFP must therefore:

• Identify, by role, who has authority to draw on each facility and under what conditions.
• Set out the operational steps needed (system entries, confirmations, margining) and target timelines.
• Require periodic “non‑crisis” draws or simulations to test that the end‑to‑end process works as expected, including during off‑peak hours or on non‑standard days.

These rehearsals should feed into continuous improvement of procedures, staffing plans, and system support.

5. Department‑Level Role in HQLA Mobilisation

A robust CFP translates the HQLA concept into concrete expectations for each key function.

5.1 Treasury and Asset–Liability Management

Treasury/ALM should be responsible for:

• Maintaining and running the intraday HQLA/time‑to‑cash and encumbrance dashboard.
• Proposing the sequence of monetisation across T+0, T+1 and T+2+ buckets, taking into account costs, signalling effects, and regulatory constraints.
• Coordinating with collateral management and operations to ensure that proposed transactions are operationally feasible within the desired time frames.

5.2 Collateral Management

Collateral management’s role includes:

• Maintaining the consolidated collateral inventory and encumbrance map.
• Managing recalls and substitutions from tri‑party and bilateral arrangements when assets must be redirected to higher‑priority uses.
• Ensuring that pre‑positioning levels at central‑bank and key counterparties remain within strategic targets and are regularly reviewed.

In a stress event, this function must be able to operate at extended hours and in close coordination with operations and treasury.

5.3 Risk Management

Risk management should:

• Independently validate the construction of the HQLA/time‑to‑cash ladder and the underlying assumptions (haircuts, eligibility, market depth).
• Integrate the operational HQLA view into liquidity stress‑testing, ILAAP, and risk appetite formulation.
• Provide challenge and independent reporting to the Board and senior management on whether the usable firewall is sufficient under various stress scenarios.

Risk functions also play an important role in “lessons‑learned” exercises after drills and real events.

5.4 Finance and Accounting

Finance must ensure that:

• Accounting classifications and potential reclassification consequences are fully understood and reflected in the definition of usable HQLA.
• Any planned use of HTM or similar portfolios in stress scenarios is supported by pre‑agreed accounting and disclosure strategies, or else excluded from the immediate firewall.
• Capital and P&L impacts of large‑scale HQLA monetisation are transparently modelled and communicated to senior management and the Board.

This prevents the bank from discovering only during a crisis that its “liquid” assets cannot be used without creating a second‑order capital or disclosure problem.

5.5 Legal and Compliance

Legal and compliance functions should:

• Maintain up‑to‑date documentation for central‑bank facilities, repo master agreements, and custody arrangements.
• Identify rating‑trigger, automatic‑termination, or cross‑default clauses that may be activated in a severe stress event, affecting the availability of funding.
• Advise on the legal boundaries between confidential supervisory communication and market disclosure when liquidity facilities are used at scale.

These roles become particularly important when pre‑positioned collateral and emergency funding lines are used for the first time in anger.

6. Supervisory Perspective and Expectations

6.1 Focus on execution capability

Supervisors are increasingly concerned with whether banks can execute their CFPs, not merely whether the documents exist. From a supervisory lens, the following aspects are central:

• Realism of usable HQLA: whether the bank distinguishes between regulatory and operational HQLA, treats HTM and encumbrance issues conservatively, and maintains a credible time‑to‑cash ladder.
• Governance and decision rights: clarity on who can deploy which parts of the firewall, under what triggers, and with what reporting to the Board and supervisor.
• Integration with ILAAP and stress testing: consistency between the CFP’s assumptions and those used in internal and regulatory liquidity assessments.
• Evidence of drilling: documented simulations and exercises that test HQLA mobilisation and broader CFP execution, including identified weaknesses and corrective actions.

During on‑site inspections or thematic reviews, supervisors are likely to test these elements through data requests, scenario discussions, and “table‑top” crisis exercises.

6.2 Supervisory engagement in a live event

In a real stress situation, supervisors will expect:

• Prompt, senior‑level notification when trigger events or threshold breaches occur.
• Rapid delivery of a verified usable‑HQLA figure and its evolution over recent days.
• Clear articulation of planned use of central‑bank and market‑based facilities, including pre‑positioning status and contingency options.
• Transparent communication of governance arrangements, including Board involvement and internal challenge.

Banks that can display a disciplined, pre‑planned HQLA mobilisation and CFP execution are likely to enjoy greater supervisory confidence and more constructive engagement. Conversely, discovery under stress that reported HQLA is materially overstated or slow to mobilise will severely damage credibility and may accelerate intrusive intervention.

7. Illustration: Internal Liquidity Firewall Table

An example of a concise internal table to be embedded in the CFP is below.

Dimension	Target state under CFP
HQLA definition	Segmented by regulatory level and time‑to‑cash (T+0/T+1/T+2+)
Data and reporting	Intraday HQLA and encumbrance dashboard in stress
Accounting constraints	HTM and restricted assets excluded from immediate firewall
Eligibility management	Facility‑ and counterparty‑specific eligibility map maintained
Pre‑positioning	Minimum share of Level‑1 pre‑lodged at central‑bank facilities
Operational drills	At least annual test of HQLA mobilisation and facility usage
Governance	Pre‑defined authority for deploying each time‑to‑cash bucket

This type of table makes the expectations of the CFP operational and auditable.

In restrospect

Embedding a robust, usable HQLA firewall at the centre of the CFP is both a risk‑management imperative and a supervisory expectation. The key shift is from seeing HQLA as a static stock that supports a regulatory ratio to seeing it as a dynamic, time‑sensitive resource that must be verified, mobilised, and governed under real‑world constraints. Banks that make this shift—through clear trigger frameworks, detailed time‑to‑cash analysis, disciplined pre‑positioning, and rigorous departmental playbooks—are materially better placed to navigate the next liquidity shock without resorting to last‑minute improvisation.

 

For more information : Visit : https://sunandoroy.org/liquidity-management-in-financial-sector/