Loan-to-value covenants for business property: asset values can move the covenant without new borrowing

A loan-to-value covenant compares secured debt with the value of specified collateral, making the borrower's compliance sensitive to both debt balance and valuation changes. 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 loan-to-value covenant compares secured debt with the value of specified collateral, making the borrower's compliance sensitive to both debt balance and valuation changes. Treasury should turn the idea into a repeatable operating rule because the practical consequence normally appears in liquidity, compliance or control.

The facility defines eligible collateral, valuation methodology, frequency, valuers, debt deductions and cure rights such as repayment or additional security. Current transaction facts matter because a small change in entity, date, notional or service setup can change the result.

How the process works

The operating sequence should move from identification to validation, approval, external action and confirmation. For this topic, the critical mechanics are: The facility defines eligible collateral, valuation methodology, frequency, valuers, debt deductions and cure rights such as repayment or additional security.

Timing should be planned backwards from the required result. Notice periods, value dates, processing windows and internal approval deadlines can make a correct action operationally late, so the workflow needs a repair margin.

The data and evidence that matter

The working file should contain secured debt, property or asset value, valuation date, valuer, eligible collateral, covenant threshold, cure amount and any additional security. Keeping those fields together lets another reviewer reproduce the decision without relying on memory.

The record should distinguish internal intention from external outcome. An approved request proves what the company wanted to do; a bank acknowledgement, lender confirmation, statement entry or reconciled transaction proves what actually happened.

Where the process can fail

A company can make every scheduled loan payment and still breach LTV because the collateral value falls faster than principal amortises. The problem normally becomes harder and more expensive to fix as the payment, settlement, test date or financing deadline approaches.

Repeated emergency workarounds are evidence that the design is weak. If the same override appears every month, management should repair the process instead of normalising the exception.

Worked example: test the mechanics

A property is valued at £20 million with £12 million of secured debt, producing 60% LTV. A new valuation of £16 million raises LTV to 75% without any new borrowing. If the covenant maximum is 70%, the company needs to consider the contractual cure mechanics.

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 hedge coverage as available.

Governance and control design

Model valuation sensitivity before formal revaluations and calculate the repayment or additional collateral needed at warning thresholds. The evidence should sit beside the transaction so later review can distinguish an approved exception from a missed control.

Useful oversight includes current LTV, stressed LTV and cure amount required at each covenant threshold. This turns the policy into an operating discipline with a measurable escalation point.

A post-event review should identify whether an exception came from data, timing, authority, system design or misunderstanding of the external rule, then assign remediation that can be tested in the next cycle.

Ownership should survive absence and staff turnover. The procedure for loan-to-value covenants for business property should state who acts, who reviews, where evidence is stored and how unresolved items are escalated.

Documentation should be short enough to use under pressure. A one-page operating checklist can point staff directly to secured debt, property or asset value, valuation date, valuer, eligible collateral, covenant threshold, cure amount and any additional security while the fuller policy keeps the legal, technical or product background.

The business should set an escalation trigger around current LTV, stressed LTV and cure amount required at each covenant threshold. Reporting becomes useful only when a threshold leads to a named decision, owner and deadline rather than another number in a monthly pack.

Repeated overrides should not be normalised. If the same workaround appears month after month, the issue is no longer exceptional; it is evidence that the timetable, data model, authority design or bank setup needs to change.

The next scheduled review should revisit current LTV, stressed LTV and cure amount required at each covenant threshold and confirm that no new transaction, user, balance or market movement has changed the conclusion. Any exception that remains open should carry a dated action and named owner.