Bank Covenants and Debt Compliance: How CFOs Avoid Technical Default
Convert facility agreements into a live covenant calendar before an avoidable technical default.
Companies often focus on interest and repayment and overlook the rest of the facility agreement. A delayed stock statement, expired insurance, unreported litigation or unauthorised related-party loan can trigger default even when every instalment is paid.
Covenant ratios use agreement definitions, not necessarily management KPI definitions.
Reporting, insurance, security, information and negative covenants also create default risk.
A quarter-end certificate is too late to discover a breach.
Discuss a forecast breach before the test date and document lender consent clearly.
1. The operating framework
| Covenant type | Example | Control |
|---|---|---|
| Financial | DSCR, leverage, current ratio, net worth or EBITDA. | Definition sheet, monthly forecast and certificate tie-out. |
| Information | Monthly/quarterly statements, budgets, audited accounts and compliance certificates. | Due-date calendar and submission acknowledgement. |
| Positive | Maintain insurance, security perfection, licences and accounts. | Renewal tracker and document repository. |
| Negative | Limits on new debt, guarantees, dividends, asset sale or related-party transactions. | Pre-transaction covenant clearance. |
| Event-based | Litigation, management change, default elsewhere or material adverse event. | Legal/secretarial notification process. |
| Security | Charge creation, valuation, stock statements and collateral coverage. | ROC/CERSAI/lender reconciliation and periodic valuation. |
2. CFO playbook
- Abstract every facility into a covenant register with exact definitions and test dates.
- Model ratios monthly using lender definitions and downside scenarios.
- Reconcile stock/debtor statements submitted to banks with books and CARO evidence.
- Route material contracts, new debt, guarantees, dividends and asset disposals through covenant clearance.
- Track reporting acknowledgements; “emailed to relationship manager” may not satisfy notice clauses.
- Escalate a forecast breach early and seek written waiver/amendment before the relevant date where possible.
- Assess accounting disclosure, current/non-current classification and cross-default consequences with auditors.
3. Practical example
Management reports EBITDA of â‚ą12 crore, but the facility excludes one-time income and adds lease adjustments differently. Covenant EBITDA is â‚ą9 crore, causing leverage to exceed the limit. The covenant model must start from the contract definition, not the investor deck.
4. Common failure points
- Using the same ratio formula across all lenders.
- Testing only on certificate date.
- Ignoring non-financial undertakings.
- Assuming a relationship manager’s verbal comfort is a waiver.
- Not assessing cross-default across facilities.
5. Evidence folder
- Facility abstract
- Definition and ratio workbook
- Monthly forecast
- Submission/acknowledgement log
- Security and insurance tracker
- Pre-transaction clearance
- Waiver/amendment and disclosure file
6. Finin2min takeaway
Design the evidence before the transaction.
Reliable compliance is the result of clear ownership, timely action, reconciled records and a documented escalation route—not a last-minute filing exercise.