Permitted security in loan agreements: track liens before a local pledge breaches the facility

A negative pledge usually restricts new security, while permitted-security provisions carve out liens or pledges that the borrower may create without separate lender consent. This guide explains the mechanics, evidence, risks and controls a UK business should understand before relying on the process.

What this means in practice

A negative pledge usually restricts new security, while permitted-security provisions carve out liens or pledges that the borrower may create without separate lender consent. Treasury should translate that concept into an operating decision because the practical consequence usually appears in liquidity, settlement or lender consent.

Permissions may cover existing disclosed security, ordinary-course liens, cash collateral, asset-finance security, acquisition security or capped baskets, each with its own conditions. Treasury should base the decision on the live agreement, bank specification or scheme report rather than on a prior transaction that may have used different terms.

How the process works

The operating sequence should start with the trigger, move through validation and approval, and end only when the external result is confirmed. For this topic, the critical mechanics are: Permissions may cover existing disclosed security, ordinary-course liens, cash collateral, asset-finance security, acquisition security or capped baskets, each with its own conditions.

Planning should work backwards from the required result rather than from the internal submission date. A correct instruction can still fail operationally if the company misses a notice period, scheme window, bank cut-off or response deadline.

The data and evidence that matter

Before the business acts, the working file should contain the secured obligation, asset charged, legal entity granting security, secured amount, relevant permitted-security limb, basket usage and any release date. These fields define the real transaction and make it possible to see whether a deadline, approval or external condition is still open.

The record should also distinguish instruction from outcome. An internally approved request proves intent; it does not prove that the bank, lender or counterparty accepted, processed or settled it. The final status should therefore come from an external acknowledgement, reconciled account entry or formal consent. The exposure specific to this process is visible in aggregate secured exposure against each contractual security basket, split by entity and permission, so that measure should be reviewed before the next external deadline rather than after reconciliation.

Where the process can fail

A subsidiary can grant what looks like a small local bank pledge and unknowingly consume a group-wide basket or breach a restriction that applies to all obligors. The exposure usually becomes more expensive to fix as the company gets closer to payment, settlement, testing or maturity.

Deadline pressure often exposes weak design. If staff repeatedly need urgent overrides to make normal payments or funding events work, management should redesign the timetable instead of treating emergency intervention as standard practice.

Worked example: test the mechanics

A facility allows £5 million of general permitted security. Treasury has already logged £3.7 million. A local company proposes a £1.8 million secured equipment line. If the full exposure counts, the group would reach £5.5 million and needs another permission or lender consent.

The figures are illustrative, not universal terms. In a live case the company should replace every amount, date and threshold with the current bank, scheme or contractual evidence, then rerun the decision before cash is committed.

Governance and control design

Maintain a central security register and require finance-document review before any group company signs a pledge, account charge or secured local facility. Any approved exception should state the amount, affected entity, expiry date and person responsible for returning the process to normal.

Useful oversight is built around aggregate secured exposure against each contractual security basket, split by entity and permission. This turns the policy into a measurable operating discipline rather than a document reviewed only during audit.

Contingency planning should be proportional to value and time sensitivity. Treasury should know the alternate approver, funding route, bank contact or manual fallback before a live deadline exposes the weakness.

Ownership should also survive absence and staff turnover. The procedure should say who acts, who reviews, where evidence is stored and what happens if the normal owner cannot complete the step. For permitted security in loan agreements, undocumented expert knowledge is itself an operational dependency. The practical stop condition is linked to this risk: A subsidiary can grant what looks like a small local bank pledge and unknowingly consume a group-wide basket or breach a restriction that applies to all obligors. That scenario should be explicitly ruled out or escalated before the item is released.

The team should also define an escalation threshold around aggregate secured exposure against each contractual security basket, split by entity and permission. A measure without a decision rule becomes descriptive reporting; a measure tied to an owner, deadline and action can prevent an exception from ageing into a cash or compliance problem.

Management should challenge repeated exceptions rather than normalise them. If the same override 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.

For permitted security in loan agreements, the review should end with a dated decision and a named owner for the next action; unresolved items should never disappear simply because the reporting period has closed.