Loan Covenants | How Banks Keep Watching Risk After the Money Is Lent

A covenant is an early-warning contract

At its best, a covenant turns a risk assumption into an observable condition.

If the bank approved a loan because the business had moderate leverage, a leverage covenant can require the borrower to stay below a defined level. If the bank relied on stable cash flow, a debt-service covenant can require a minimum coverage ratio. If collateral matters, reporting covenants can require updated valuations or borrowing-base certificates.

underwriting assumption → covenant → observed evidence → early review if the assumption weakens.

Covenants do not guarantee repayment

A borrower can comply with every covenant and still fail suddenly. A covenant can also be badly designed, measured too infrequently or based on accounting numbers that lag reality.

Covenants therefore improve visibility and control. They do not remove uncertainty.

Financial covenants measure the shape of the balance sheet and cash flow

• Leverage ratio: limits debt relative to earnings, equity or another agreed base.
• Debt-service coverage: requires sufficient cash generation relative to debt payments.
• Interest coverage: tests whether earnings or cash flow can cover interest expense.
• Minimum net worth: requires a capital cushion to remain in the borrower.
• Loan-to-value: keeps debt below an agreed proportion of collateral value.
• Liquidity ratio: requires specified liquid resources relative to short-term obligations.

The exact definitions matter enormously. “EBITDA,” “debt,” “cash,” “net worth” and “value” can be defined differently in different contracts.

Non-financial covenants protect behaviours and information

Not every credit risk can be reduced to a ratio.

• provide financial statements on time;
• maintain insurance;
• pay taxes;
• preserve licences and permits;
• avoid disposing of important assets without consent;
• limit additional borrowing;
• restrict dividends or distributions under defined conditions;
• notify the bank of litigation or default;
• maintain collateral and security registrations;
• allow inspections or audits where agreed.

These covenants keep the bank connected to the operating facts supporting the loan.

Information covenants can be more important than restrictive covenants

A bank cannot manage risk it cannot see. Timely accounts, management reports, borrowing-base certificates and compliance certificates give the lender a recurring evidence stream.

The information itself does not prevent deterioration. It shortens the time between deterioration and recognition.

That time advantage can matter greatly. The earlier a problem is visible, the more options may remain.

Why covenant headroom matters

Suppose a borrower must keep leverage below 4.0 times and currently sits at 2.8 times. The 1.2-turn gap is covenant headroom.

If leverage rises to 3.9 times, the borrower remains technically compliant but has little room for another earnings decline or debt increase. The bank should therefore monitor trend and headroom, not only binary pass/fail status.

A covenant often becomes most useful before it is breached.

A breach is a state change, not automatically a collapse

When a covenant is breached, the contract can give the bank rights such as demanding information, restricting further drawings, changing pricing, requiring remediation, obtaining additional security or declaring an event of default depending on the agreement.

In practice, a bank may waive the breach, amend the covenant or negotiate a cure if the underlying borrower remains viable.

The important point is that the breach creates a formal review point before ordinary payment default necessarily occurs.

Waivers should preserve information, not erase history

If a covenant breach is waived, the bank should still record what happened and why the waiver was granted. Otherwise repeated waivers can hide a deteriorating credit.

A waiver means the bank chooses not to exercise certain rights for that breach under agreed terms. It does not mean the breach never occurred.

Covenant-lite lending changes the control model

Some loan markets use fewer maintenance covenants, especially for stronger borrowers or competitive leveraged transactions. That gives borrowers more operating freedom and reduces early contractual intervention points.

The bank then relies more heavily on payment performance, information rights, collateral, market signals and later default triggers.

Fewer covenants are not automatically reckless. They change where the monitoring and control burden sits.

Too many covenants can also damage a good loan

Overly restrictive covenants can prevent a business from making sensible investments, taking normal operational decisions or responding quickly to market changes.

Good covenant design therefore protects the bank’s core assumptions without attempting to manage every detail of the borrower’s business.

The contract should create useful signals, not permanent interference.

Covenants connect loan structure to portfolio monitoring

One covenant breach matters at borrower level. A sudden rise in breaches across an entire sector can reveal a broader economic shock.

The bank can therefore aggregate covenant data to see emerging portfolio stress before defaults arrive.

This is another example of banking turning individual claims into system-level evidence.

Financial statements arrive slowly; transaction data can move faster

Traditional covenants may be tested quarterly or annually. Modern banking can also observe account flows, card receipts, payroll activity or other consented operational data more frequently.

This can create earlier warning signals, but it also increases data-governance and privacy responsibilities. More data is useful only if the bank knows what it means and uses it lawfully.

The covenant should correspond to a real risk

A covenant earns its place when the bank can explain which risk it controls.

Risk	Possible covenant response
Leverage rises too far	Maximum debt-to-earnings or debt-to-equity ratio
Cash flow weakens	Minimum debt-service or interest coverage
Collateral value falls	Maximum loan-to-value or borrowing-base test
Value leaks to owners	Restrictions on dividends or distributions
New debt subordinates the bank	Limits on additional borrowing or security
Bank loses visibility	Reporting and information undertakings

A covenant copied mechanically from another transaction can create noise rather than control.

A worked miniature

A company borrows S$10 million with a covenant requiring debt-service coverage above 1.5 times. At approval it sits at 2.2 times.

Six months later coverage falls to 1.6 times because margins weaken. No payment has been missed. The covenant has not been breached. But headroom is almost gone.

The bank can now investigate before default: Is the margin decline temporary? Does management need to reduce dividends? Is additional borrowing planned? Should the bank tighten monitoring or restructure?

The covenant created value because it made deterioration visible while choices still existed.

Covenants are part of relationship banking

A well-designed covenant gives the borrower and bank a shared vocabulary for risk. It defines the corridor both parties agreed was acceptable at origination.

When the borrower approaches the boundary, the conversation can begin before the relationship becomes adversarial.

Four misconceptions to remove

Misconception	Better model
“A covenant breach means the loan has defaulted permanently.”	A breach creates contractual rights and review; waiver, cure or amendment may be possible.
“Covenants guarantee the bank sees trouble early.”	They work only if definitions, testing frequency and information remain meaningful.
“More covenants always make a loan safer.”	Excessive restrictions can damage the borrower and create noise.
“Monitoring ends after approval.”	Credit risk continues to change for the entire life of the loan.

A mastery test

1. What underwriting assumption does a covenant make observable?
2. Why does covenant headroom matter before breach?
3. What is the difference between a breach and a payment default?
4. Why should waivers remain in the credit history?
5. How can covenant data reveal portfolio-wide stress?

If those answers connect, covenants become more than legal clauses. They become a monitoring system embedded in the loan contract.

---