The principle
Loan covenants may require actions, restrict actions, or set financial tests. Examples include delivering financial reports, maintaining insurance, limiting additional debt, or meeting a defined coverage ratio. The agreement specifies the calculation, testing dates, permitted exceptions, and consequences of noncompliance.
Put it into practice
Build a covenant calendar and calculate headroom using actual results and the forecast. If a ratio is tested quarterly, an annual forecast alone may miss a problem. Review planned dividends, acquisitions, shareholder repayments, asset sales, and new financing against the restrictions before committing to those actions.
What people often miss
A missed report can matter even when payments are current. Do not assume a lender will automatically waive a breach or that an informal conversation changes the contract. Ask about notice, cure periods, waiver processes, and potential fees. For complex terms, have advisers review the definitions and make responsibility for ongoing monitoring explicit inside the business.
Turn clauses into a working dashboard
A covenant becomes easier to manage when it has an owner, a date and evidence. BDC distinguishes requirements to do something, restrictions on actions and numerical financial tests. Start a register using the agreement's actual clause numbers. Include the defined terms and exceptions, because a friendly summary can accidentally remove the conditions that make a requirement important.
For each item, write the test date separately from the delivery deadline. A ratio might be measured at quarter end while the certificate is due later. Insurance may need to remain in force continuously. Consent for a transaction may be required before the business commits to it. One annual reminder is unlikely to capture those different operating rhythms.
| Illustrative register field | What to record |
|---|---|
| Obligation | Exact clause and definitions |
| Timing | Measurement date, notice date and delivery deadline |
| Evidence | Calculation, certificate, statement or policy |
| Owner | Named preparer and reviewer |
| Forecast | Expected result and headroom |
| Exception | Written consent, waiver or amendment, if any |
Worked example: headroom before expansion
Assume a fictional agreement requires defined debt service coverage of at least 1.30 times. The business forecasts $260,000 of the permitted earnings measure and $180,000 of annual debt service. Coverage is approximately 1.44 times. The required earnings at that payment level are $234,000, leaving $26,000 of earnings headroom under this invented test.
Management then proposes equipment financing that adds $24,000 of annual payments. If earnings have not yet increased, debt service rises to $204,000 and coverage falls to approximately 1.27 times. Meeting 1.30 times would now require $265,200 of defined earnings, $5,200 more than the current forecast. Even a project with attractive long-term returns can create a near-term covenant issue. The agreement also needs a separate check for restrictions on additional debt.
Distinguish a forecast problem from an actual breach
In that example, a forecast below the threshold is an early warning. Whether an actual breach exists depends on the signed requirement, the testing period, the results and any valid amendment or waiver. Label internal reports clearly: actual tested result, forecast, possible shortfall and unresolved interpretation are different states. Do not certify compliance from a spreadsheet that still contains unconfirmed adjustments.
Build a short decision note before a material transaction. State the transaction, the relevant clauses, its effect on the calculations and the approval needed. This lets the owner, accountant and lender discuss the same scenario. If there is a potential problem, preserve the correspondence and ask what formal process applies. An expectation of flexibility is not a substitute for the required written action.
- Do acquisitions, dividends, owner repayments or new leases need consent?
- Are tests based on one period, a trailing period or specified reporting dates?
- Which accounting policies and adjustments must remain consistent?
- What notice, cure or waiver provisions actually appear in the agreement?
- Who checks covenant effects before signing a new commercial commitment?
- Can the evidence be reproduced when the lender requests it?
Make monitoring part of the monthly close
Reserve a small section of the monthly financial review for borrowing obligations. Update forecasts, confirm upcoming reporting dates and keep versions of calculations with the source statements. A second person should review the assumptions before a certificate is signed. These are practical workflow suggestions; they do not determine the legal effect of a clause. U.S. and Canadian loan documentation can differ, so any disputed interpretation or consequence requires review of the applicable agreement and law.
A covenant calculation is not a borrowing approval
A financial test answers one contractual question under a defined formula. It does not establish that a new loan will be offered, that a transaction is permitted or that the business has enough cash on every payment date. Check the numerical test, any restriction requiring prior consent, and the operating cash forecast separately.
Under the fictional 1.30× test above, $260,000 of permitted earnings supports $200,000 of annual debt service in that simplified calculation. Existing debt service of $180,000 leaves $20,000 of annual payment headroom. It does not mean the business can borrow another $20,000 of principal. Principal depends on interest, amortization, fees and other terms. New equipment payments of $24,000 annually would exceed that illustrative headroom by $4,000.
Source: BDC: Loan covenants
Keep measurement dates separate from delivery dates
If a fictional agreement measures a ratio at September 30 and requires a certificate 45 days later, the later delivery date does not move the measurement date. A strong October does not automatically repair the September result. Record the reporting period, accounting definitions, preparer, reviewer and source statements beside the calculation.
Ask which obligations apply continuously, which are tested on specified dates, and which arise only when the business proposes an action. U.S. and Canadian contracts can use similar ratio names with different definitions and consequences. Use the signed agreement for the actual test; a calculator or glossary is only a preparation tool.
Your next-step checklist
- Exact covenant wording and definitions
- Complete testing and reporting calendar
- Base-case and downside headroom
- Consent, notice, waiver, and cure provisions
Crack this combination.
Can a reporting failure matter even when loan payments are current?
Keys track learning on this device and, when signed in, in your Saved files library. Every dossier stays open.
Sources & further reading
This file draws on the following references. Product availability and requirements must be confirmed with the provider.
BDC: Loan covenantsLevr: reviewing a debt term sheet