A capital expenditure covenant can limit annual or rolling investment spending even when the business has enough cash to fund the projects. 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 capital expenditure covenant can limit annual or rolling investment spending even when the business has enough cash to fund the projects. A sound process makes the trigger visible before cash is committed instead of discovering the rule only after an external party rejects or questions the transaction.
The facility may define capex differently from accounting policy, allow carry-forward or carry-back amounts, exclude acquisitions or financed equipment, and permit additional spending if leverage or another test is met. The procedure should state when the test occurs, who performs it and which uncertainty forces escalation rather than leaving judgement inside an informal email chain.
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 facility may define capex differently from accounting policy, allow carry-forward or carry-back amounts, exclude acquisitions or financed equipment, and permit additional spending if leverage or another test is met.
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
Before proceeding, treasury should assemble project spend, contractual capex definition, annual basket, prior-year carry-forward, excluded items, entity, payment timing and forecast remaining allowance. Each material value should have a source and date so an old assumption cannot quietly become current evidence.
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
Operations can approve several individually reasonable projects that collectively exceed the financing limit because no one owns the group-wide covenant basket. The problem usually becomes harder and more expensive to fix as the settlement, testing, maturity or payment date gets closer.
Another risk is assumption drift after a system, bank service or finance document changes. A process that worked last year can become wrong without an obvious failure until a high-value transaction reaches the deadline.
Worked example: test the mechanics
A facility permits £18 million of annual capex plus up to £3 million of unused prior-year allowance. Approved projects already total £17 million and a new warehouse project requires £5 million this year. Without another permission, total spend would reach £22 million against £21 million of available capacity.
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
Track committed and forecast capex against the loan definition before purchase orders are released. Any temporary exception should state the affected amount, legal entity, expiry date and remediation owner so the workaround cannot quietly become permanent.
The control owner should track committed and paid capex versus contractual allowance, including carry-forward and excluded categories. A deterioration in that indicator should trigger review while the exposure is still manageable.
For this subject, the most important challenge question is whether operations can approve several individually reasonable projects that collectively exceed the financing limit because no one owns the group-wide covenant basket. The reviewer should be able to show which evidence rules out that scenario before the transaction is released.
Ownership should survive absence and staff turnover. The procedure for capital expenditure 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 project spend, contractual capex definition, annual basket, prior-year carry-forward, excluded items, entity, payment timing and forecast remaining allowance while the full policy keeps the legal, technical or scheme background.
Controls should be proportionate without creating blind spots. Routine low-value items may move automatically, but unusual movements in committed and paid capex versus contractual allowance, including carry-forward and excluded categories should still surface for human review before a larger exposure develops.
The operating checklist should state the stop condition in plain language and point directly to project spend, contractual capex definition, annual basket, prior-year carry-forward, excluded items, entity, payment timing and forecast remaining allowance. Staff under deadline pressure need to know what blocks release, what can be repaired and who can approve an exception.
Editorial Verdict
BanksGB's editorial view is that capital expenditure covenants should be managed as a practical cash-and-control issue. A capital expenditure covenant can limit annual or rolling investment spending even when the business has enough cash to fund the projects. 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 capital expenditure covenants is weaker than it appears. For this article, the decisive record is project spend, contractual capex definition, annual basket, prior-year carry-forward, excluded items, entity, payment timing and forecast remaining allowance; 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/