A minimum liquidity covenant requires the borrower to maintain at least a specified amount of qualifying cash, cash equivalents or available committed facilities. This guide explains the mechanics, evidence, failure points and controls a UK business should understand before relying on the process.
What this means in practice
A minimum liquidity covenant requires the borrower to maintain at least a specified amount of qualifying cash, cash equivalents or available committed facilities. The business should treat this as a live transaction issue rather than a specialist label, especially when material cash or contractual deadlines are involved.
The agreement may exclude restricted cash, trapped cash, uncommitted lines or amounts unavailable to the relevant borrower group, and the test may apply daily, monthly or on specific dates. The live agreement, bank specification or scheme requirement should therefore be the starting point rather than shorthand copied from another product.
How the process works
The operating sequence should move from identification to validation, approval, external action and then confirmation. For this topic, the critical mechanics are: The agreement may exclude restricted cash, trapped cash, uncommitted lines or amounts unavailable to the relevant borrower group, and the test may apply daily, monthly or on specific dates.
Timing should be planned backwards from the required result. Notice periods, value dates, processing windows and internal approval deadlines can make a correct instruction operationally late, so the workflow needs a repair margin.
The data and evidence that matter
The minimum decision pack is eligible cash by entity, restricted balances, undrawn committed facilities, utilisation conditions, covenant floor, testing frequency and expected near-term outflows. These items connect the commercial need to the bank, lender, counterparty or accounting outcome that determines the next action.
The record should distinguish internal intention from external outcome. An approved request proves what the company intended; a bank acknowledgement, lender consent, statement entry or counterparty confirmation proves what actually happened.
Where the process can fail
A group can report large consolidated cash while the contractual liquidity test excludes balances trapped in subsidiaries or unavailable committed lines. The problem usually becomes harder and more expensive to fix as the settlement, testing, maturity or payment date gets closer.
A second weakness is status confusion. Approved, submitted, accepted, processed and settled can represent different stages, and treating them as one state can distort both accounting and liquidity.
Worked example: test the mechanics
The covenant requires £10 million of minimum liquidity. The group has £8 million of unrestricted cash, £4 million trapped in a regulated subsidiary and £3 million of a committed RCF available. If the trapped cash is excluded but the undrawn RCF qualifies, liquidity is £11 million, leaving only £1 million of headroom.
The figures are illustrative rather than universal terms. In a live case the team should replace every amount, date and threshold with current source evidence, then repeat the test before treating cash, consent or coverage as available.
Governance and control design
Maintain a covenant-specific liquidity bridge and forecast the lowest point between formal reporting dates, not only period-end cash. Management should see unresolved items before the external deadline rather than only after they become failed payments, covenant breaches or aged reconciliation entries.
Management reporting should focus on qualifying liquidity versus the contractual minimum, including lowest forecast point and restricted-cash deductions. That measure connects the technical rule to the financial exposure instead of reporting only volume.
Change management is part of the control environment. When the bank, facility, ERP or legal structure changes, this process should be retested from source data through the final bank or accounting outcome rather than assumed to survive unchanged.
Ownership should survive absence and staff turnover. The procedure for minimum liquidity covenants should state who acts, who reviews, where evidence is stored and how unresolved items are escalated when the normal owner is unavailable.
Documentation should be short enough to use under pressure. A one-page operating checklist can point staff directly to eligible cash by entity, restricted balances, undrawn committed facilities, utilisation conditions, covenant floor, testing frequency and expected near-term outflows while the full policy keeps the legal, technical or scheme background.
Reconciliation should close the loop between eligible cash by entity, restricted balances, undrawn committed facilities, utilisation conditions, covenant floor, testing frequency and expected near-term outflows and the eventual financial outcome. The team should be able to prove not only that the instruction was prepared correctly but that the external result matched the intention.
If an exception occurs, the post-event review should determine whether the root cause was data, timing, authority, system design or misunderstanding of the external rule, then assign remediation that can be tested during the next cycle.
Editorial Verdict
BanksGB's editorial view is that minimum liquidity covenants should be managed as a practical cash-and-control issue. A minimum liquidity covenant requires the borrower to maintain at least a specified amount of qualifying cash, cash equivalents or available committed facilities. The best process ties the rule to the actual amount, entity, timing and external status instead of relying on shorthand.
The final test is reproducibility. A second person should be able to explain what triggered the action, which evidence was used, who approved it, what happened outside the company and what remains outstanding. If that chain is not visible, the control around minimum liquidity covenants is weaker than it appears. For this article, the decisive record is eligible cash by entity, restricted balances, undrawn committed facilities, utilisation conditions, covenant floor, testing frequency and expected near-term outflows; the control is incomplete if those fields cannot be tied to one dated case and one accountable owner.
Sources
- Association of Corporate Treasurers, treasury resources: https://www.treasurers.org/
- Loan Market Association, documentation and market resources: https://www.lma.eu.com/