The problem
Many finance companies run liquidity on spreadsheets. Extracts come from the core system at month end, are pasted into a workbook, adjusted by hand and summarised for ALCO. The workbook works until the person who built it is on leave, or until an auditor asks why a deposit bucket moved between two versions of the same pack.
The CBSL liquidity risk management direction for finance companies raises the standard. It asks for a documented framework, regular and forward-looking reporting to the board, BIRMC and ALCO, stress testing, a contingency funding plan, limits with a defined escalation path, and independent assessment of the whole. Each of those needs data that can be traced and a record of who decided what.
Banks face the same questions at greater scale, with more products, more currencies and closer supervisory review of the models behind the numbers. Global systems answer those questions but are built and priced for large banks. Noēsis Liquidity is built for finance companies first, then banks, and is priced for finance companies and mid-sized banks.
What the direction asks, and what the product does
The direction requires a liquidity risk management strategy, policy and procedures, a governance structure, and a process to identify, measure, monitor and report, control and mitigate liquidity risk. The table sets out how Noēsis Liquidity relates to each element.
| Element of the direction | Noēsis Liquidity | Role | Stays with your institution |
|---|---|---|---|
| Framework | |||
| Strategy | Holds the board-approved risk appetite as versioned parameters, so reports always show which appetite they were measured against | Supports | Writing and approving the strategy |
| Policy and procedures | Holds approved limits, thresholds and assumptions with version, date and approver; keeps the history of every change | Supports | Writing and approving the policy |
| Governance | Routes figures and reports through Draft, Verified, Reviewed and Approved, with role-based access and a record of each sign-off | Supports | Committee membership, terms of reference, BIRMC and board approvals |
| Process: identify, measure, monitor and report | |||
| Identification and measurement | Builds contractual and behavioural maturity ladders from core-system extracts; calculates the statutory liquid-asset requirement and your internal ratios | Does | Approving behavioural assumptions |
| Monitoring | Tracks early-warning indicators and positions against board-approved limits after each end-of-day extract | Does | Setting the indicators and their thresholds |
| Reporting | Produces ALCO packs, BIRMC and board reports, and draft regulatory returns from verified figures | Does | Reviewing, approving and submitting returns |
| Stress testing | Runs named, versioned scenarios quarterly or more often, as the direction requires | Does | Approving scenarios and acting on results |
| Contingency funding plan | Links plan triggers to scenarios and indicators; keeps the invocation and escalation log; reports to senior management, BIRMC and the board | Supports | The plan document itself and its board approval |
| Intraday positions | Tests positions against day-to-day and intraday limits at each extract you load, end of day or intraday, and records every breach | Does | Setting intraday limits and providing intraday extracts |
| Control and mitigation | |||
| Control and escalation | Records each breach, the escalation through senior management, BIRMC and the board, and the corrective action agreed | Supports | Deciding the corrective action |
| Independent assessment | Gives internal audit and risk a full audit trail from report back to source extract | Supports | The assessment itself |
The product does not write your strategy or policy. It holds what your board approved, tests positions against it, and records what happened when a limit was breached.
Stress testing
Each scenario has a name, an owner, a version and an approval date. A run records the extract it used, the scenario version and the assumptions applied, so it can be reproduced months later.
Scenarios can combine institution-specific and market-wide stress: deposit run-off by product and depositor type, lower renewal of maturing fixed deposits, slower collections on the lease and loan book, withdrawal of bank lines, and haircuts on liquid assets. Results show the survival horizon and the funding gap by time band, as a range where assumptions are uncertain. The direction asks for stress tests quarterly or more frequently as necessary, with results feeding strategy, policy and the contingency funding plan. The product supports runs at any frequency your policy sets.
Survival horizon under stress: 34 to 48 days, base case 41
The range comes from the uncertain assumptions: deposit run-off between 12% and 18% a month, and renewal of maturing deposits between 70% and 85%.
Early-warning indicators
You choose the indicators and their thresholds; your board approves the limits. Typical indicators include deposit concentration, the renewal rate on maturing deposits, the cost of new funding against the market, undrawn bank lines, and the liquid-asset buffer against the requirement. Each is shown against its threshold with its trend. A crossed threshold opens a record that follows the escalation path in your policy and links to any contingency funding plan trigger.
Early-warning indicators against policy limits
The indicators are rule-based. They apply the thresholds you set and do not use machine learning.
Board and regulatory reporting
ALCO, BIRMC and board packs are built from figures that have reached at least Verified status, and the pack shows the status of every figure. A director can follow any number back to the ladder, the extract and the source record.
The product prepares draft returns from verified figures for your review and submission. It also produces the key liquidity indicators the direction expects in published financial statements, and the material on the framework for the annual report or website.
For banks
Licensed banks are measured against the Basel III liquidity coverage ratio (LCR) and net stable funding ratio (NSFR), as applied by CBSL, alongside the statutory liquid-asset requirement. For bank clients, LCR and NSFR are built on the same maturity data, reconciliation, review states and audit trail. They are agreed as part of a bank's pilot scope.
Data and implementation
Noēsis Liquidity works from extracts your core system already produces: the loan and lease book, deposits, borrowings, investments and the general ledger trial balance. We map your extract fields to the product's data model once, and the mapping is versioned like everything else.
Each load is reconciled to the general ledger before anything is built on it. Breaks above the tolerance your finance team sets are shown, not hidden, and must be cleared or explained before figures move to Verified. During the pilot the product runs in parallel with your current process, so your team can compare outputs line by line before relying on them.
Your team stays in control of assumptions, scenarios and approvals. We handle configuration, mapping and reconciliation set-up.
The pilot
We are taking three to five pilot institutions for three months, with no fee for the pilot. You provide end-of-day extracts, a named sponsor and time with ALCO. We deliver your maturity ladder, liquid-asset and internal ratios, an agreed set of stress scenarios and indicators, and a draft ALCO pack, all run in parallel with your current process. At the end we propose commercial terms. If you do not continue, your data is returned or deleted.
Three-month pilot, run in parallel with your current process, with no fee for the pilot.
Request a briefingFrequently asked questions
How do you reconcile your ladder to our general ledger?
Every extract is reconciled to the trial balance before use, at the tolerance your finance team sets. Breaks are listed by account and must be cleared or explained before figures can move to Verified.
Who owns the stress scenarios and behavioural assumptions?
You do. We can propose a starting set based on common practice, but each scenario and assumption is approved by your institution, versioned, and dated. Reports always show which version they used.
How are the models governed?
Each model shows its assumptions, version and date. Changes are logged with the approver. We do not claim accuracy for any model until it has been back-tested on your data.
Does the product decide whether a limit breach needs action?
No. It records the breach and follows the escalation path in your policy. Senior management, BIRMC and the board decide the corrective action, and the product records that decision.
Does it support our contingency funding plan?
Yes. It links plan triggers to scenarios and indicators, keeps the invocation and escalation log, and reports to senior management, BIRMC and the board. The plan itself remains your document, approved by your board.
Can we file returns directly from the system?
The product prepares draft returns from verified figures for your review and submission. Submission stays with you.
Do you monitor intraday liquidity?
Yes. The product tests positions against your limits at every extract you load. Most finance companies work from end-of-day extracts; where your core system provides intraday extracts, positions are monitored intraday as well.
Is it for banks as well?
Yes. For banks it adds LCR and NSFR, agreed as part of the pilot scope. Regulatory capital ratios are covered by Noēsis Capital.
See Noēsis Liquidity on your own data
Three-month pilots, run in parallel with your current process, with no fee for the pilot.