Liquidity Monitoring Agent
Monitors LCR, NSFR and the liquidity buffer and recommends funding actions.
- Industry
- Banking
- Department
- Finance
- Team
- Planning and Compliance
- Kind
- Decision-maker
- Approver
- Treasurer
- Code
- FIN-11
It monitors the bank's liquidity: the stock of high-quality liquid assets, the liquidity coverage ratio and net stable funding ratio, deposit outflows, maturing wholesale funding and the 30-day stressed outflow forecast. When a ratio approaches its internal limit it recommends actions such as repo of eligible bonds, term funding or slowing lending, for the treasurer and ALCO.
How it works
7 steps, and a person signs off before step 7.
- 01Looks it up
Finds the record the request is about in the risk data warehouse: HQLA holdings, deposit balances by type, wholesale funding maturities and the stressed outflow assumptions..
- 02Reads the request
Works out what is being asked and what a complete answer needs.
- 03Checks the facts
Checks figures, dates and rules against the source records, not from memory.
- 04Forecasts, when it decides
Projects what each option will cost or return before it recommends one.
- 05Works it through
Prepares the draft, match, recommendation or reply, with its sources.
- 06Asks a person
Hands the work to Treasurer with its reasoning before anything goes out.
- 07Acts
Once approved, it acts in the risk data warehouse: it publishes the liquidity position and recommendations to ALCO's liquidity report. and records what was done.
What it works with
Your knowledge, your systems, your people.
Knows
The liquidity risk framework: LCR and NSFR methodology under Basel, internal limits and early-warning indicators, the HQLA buffer and its composition, the contingency funding plan, and central-bank facilities.
Reads from
the risk data warehouse: HQLA holdings, deposit balances by type, wholesale funding maturities and the stressed outflow assumptions.
Acts in
the risk data warehouse: it publishes the liquidity position and recommendations to ALCO's liquidity report.
Hands back
An object with as_of, lcr_percent, nsfr_percent, hqla_usd, days (a list with date, lcr_percent, net_outflows_usd and headroom_usd), early_warnings (a list) and recommended_actions (a list with action, amount_usd and effect).
Asks a person when
Any forecast day breaches an internal limit, an early-warning indicator fires, or it recommends repo, term funding, a central-bank facility or lending restrictions.
Settings
Your limits, set by your managers.
| Setting | Default | What it controls |
|---|---|---|
| LCR internal limit (%) | 120 | The bank's own floor, above the 100 percent regulatory minimum. |
| NSFR internal limit (%) | 110 | The bank's own floor. |
| Early warning above the limit (points) | 10 | Within this of a limit is an early warning. |
| Deposit outflow alert in a day (%) | 2 | A larger fall in retail deposits is an early-warning indicator. |
| Forecast horizon (days) | 90 | The window forecast. |
Limits are settings, not code: a manager changes them without a developer.
Rules it always follows
- Compute LCR and NSFR by the Basel methodology; flag any day within 10 points of 120 or 110 percent.
- A one-day retail deposit fall above 2 percent is an early-warning indicator for the contingency funding plan.
- Forecast 90 days ahead including every known maturity.
- Recommend actions in the contingency funding plan's order; never execute a trade or drawdown.
- A breach of a regulatory minimum is reported to the Chief Risk Officer and the regulator at once.
See the Liquidity Monitoring Agent agent on your own work.
We’ll run it on a sample of your work and show you what your approver would see.