Bank Covenants: Avoid Technical Default

Quick View

Why It Matters

Create a covenant register from every facility agreement. Include ratios, borrowing-base tests, information undertakings, negative covenants, security, insurance and event-of-default clauses.

Definitions in the agreement control. EBITDA, net debt, tangible net worth and current ratio may differ from management metrics.

Forecast compliance before the test date. If breach is likely, engage the lender early and obtain a written waiver or amendment through the required authority.

Control Framework

Action Checklist

1. Build a facility and covenant register.
2. Assign data owners.
3. Calculate monthly even if quarterly tested.
4. Review restricted payments and new debt.
5. Forecast headroom.
6. Seek written waiver before reporting where possible.

Practical Example

Evidence to Keep

• Facility and security agreements.
• Covenant definition sheet.
• Calculation and source schedules.
• Lender certificates and correspondence.
• Waivers and amendments.
• Board and going-concern analysis.

Warning Signs

Management Decision

Report covenant headroom, not only pass or fail. Thin headroom requires action even before formal breach.

Assess accounting classification and disclosure when a breach exists at the reporting date. Obtain auditor and legal input early.

Record the decision, owner, due date and evidence expected. A verbal explanation should become an approved working, board note, contract amendment, statutory filing or reconciliation before the item is treated as closed.

Rules, forms, thresholds and procedures can change. Use the latest official source and the actual company facts rather than copying a prior-year control or another entity’s legal position.

Exception Review

Classify every exception as a timing difference, data error, missing document, legal non-compliance, control-design gap or control-operating failure. This prevents management from treating fundamentally different problems as one ageing list.

The exception file should show amount or exposure, root cause, immediate correction, preventive action, owner and board-escalation threshold. Repeated low-value issues can become material when they reveal weak systems or management override.

Close the item only after the evidence agrees across source documents, books, portal data and management reporting. A screenshot or email promise is not equivalent to a completed filing, lender waiver, signed contract or reconciled ledger.

Board Escalation

The control should operate across the full transaction population, not only the samples management expects a reviewer to inspect. For this topic, the key stages are covenant inventory, measurement, forecast, breach response. Each stage should identify the source system, preparer, reviewer, deadline and evidence retained.

A useful management review asks whether the legal document, accounting entry, bank movement, tax treatment and public filing describe the same event. Differences may be valid, but they should be reconciled through a dated working rather than explained from memory during audit or diligence.

Materiality should determine escalation, not whether the company keeps a record. Repeated small exceptions can show weak master data, unclear authority, system bypass or management override. Root cause and preventive action should therefore be documented separately from the immediate correction.

The commercial owner should remain accountable after finance or legal approval. Controls cannot work when business teams treat documentation, collection, contract obligations or vendor verification as back-office responsibilities.

Report both the current exception and its cash consequence. A technically small error can delay collection, block a financing, create tax interest or undermine investor confidence well beyond its ledger value.