Debt covenants are often treated as a treasury responsibility. For a financial controller, however, they are also a financial-reporting, close-management and internal-control issue. A missed calculation, an incomplete definition of adjusted EBITDA or a late lender certificate can create consequences well beyond a financing relationship: a covenant breach may affect debt classification, liquidity disclosures, going-concern assessments, audit procedures and management decisions.
The control objective is straightforward: know which obligations apply, calculate them from controlled data, identify potential breaches early, communicate with lenders through authorized channels and preserve evidence supporting the accounting conclusion at each reporting date.
1. Start with a complete covenant inventory
Maintain a central register for every credit agreement, revolving facility, term loan, private placement and other financing arrangement containing financial or non-financial covenants. Capture the lender, borrower/legal entity, facility amount, maturity, reporting dates, test frequency, thresholds, cure rights, grace periods, reporting deadlines and the responsible finance owner.
Do not rely solely on a summary prepared when the facility was signed. Read the executed agreement, amendments, side letters and subsequent waivers. Definitions can differ between facilities. For example, “EBITDA” used in a leverage covenant may include or exclude specific add-backs, acquisition costs, restructuring charges or synergies. Those contractual definitions are not automatically the same as the EBITDA measure in management reporting.
2. Translate legal wording into controlled calculations
For each covenant, prepare a calculation specification that identifies the contractual formula, source accounts, permitted adjustments, testing period, currency, entity or group perimeter, and rounding convention. Have Treasury and Legal confirm the interpretation of ambiguous terms; Finance should not silently resolve legal uncertainty through a spreadsheet assumption.
Common measures include leverage ratios, interest coverage, fixed-charge coverage, minimum liquidity, tangible net worth and capital expenditure limits. Document whether the agreement tests a point-in-time balance, a trailing twelve-month measure, a quarterly result or a forward-looking condition.
3. Reconcile every input to the accounting records
Build the calculation from controlled source data. Reconcile relevant revenue, operating profit, interest, debt, cash, lease liabilities and permitted adjustments to the trial balance, consolidation package or other authoritative records. Maintain a bridge for every non-GAAP or contract-specific adjustment.
For a US group reporting under US GAAP, a leverage calculation may begin with consolidated results but still require agreement-specific adjustments and exclusions. A Canadian subsidiary reporting under ASPE may feed a parent’s US GAAP covenant package; the controller should document any conversion or mapping adjustments rather than assume that local statutory figures can be inserted unchanged.
Where the agreement defines a calculation using a particular accounting framework or requires consistency with prior periods, follow that contractual language. Involve technical accounting when a new standard, acquisition, discontinued operation, impairment, lease change or accounting-policy change could affect the measure.
4. Establish an independent review and evidence trail
The preparer should not approve their own covenant calculation. Assign an appropriately experienced reviewer who can challenge the source data, adjustments, formula, agreement interpretation and comparison with the contractual threshold. The review should be evidenced with dated sign-off and comments showing what was checked—not just an unexplained tick mark.
Retain the executed agreement, amendments, source reports, reconciliations, calculation workbook, review evidence, lender submissions and correspondence in a controlled repository. Restrict access to sensitive financing documents and protect calculation files from untracked changes.
5. Monitor headroom between formal test dates
A covenant that is tested quarterly can deteriorate well before quarter-end. Establish a monthly or more frequent monitoring cadence for facilities with limited headroom, volatile earnings, seasonal working capital or significant foreign-exchange exposure. Forecast the covenant using the latest actuals and a range of scenarios, including downside cases for revenue, margins, interest rates, collections and capital expenditure.
Show both the contractual threshold and the remaining headroom. A forecast breach is not necessarily an actual breach, but it is a trigger for escalation and action planning. Do not wait for the formal certificate date to tell leadership that a covenant is at risk.
6. Control lender certificates and communications
Use a submission calendar with named owners, internal review deadlines and evidence of delivery. Reconcile the certificate to the approved calculation and obtain the required management authorization before submission. Keep a copy of the final version and the lender’s acknowledgement.
Only designated personnel should communicate covenant positions, request waivers or agree amendments. Oral assurances, informal emails or a lender’s indication that it does not currently intend to accelerate a loan should not be treated as equivalent to a legally effective waiver. Obtain and assess the actual executed documentation.
7. Assess debt classification under the applicable framework
A covenant breach can change whether long-term debt is presented as current or non-current. The answer is framework-specific; do not apply one jurisdiction’s waiver or timing rules to another set of financial statements.
US GAAP
Under US GAAP, ASC 470-10 addresses the balance-sheet classification of debt, including obligations that become callable because of covenant violations. The analysis considers the contractual right of the creditor to demand repayment, the timing and nature of the violation, applicable grace periods and whether a qualifying waiver or cure exists. Certain credit-related covenant violations occurring after the balance-sheet date but before the financial statements are issued or available to be issued can also affect the analysis. A waiver must meet the applicable requirements; a general expression of lender support is not enough. Consult the current FASB Accounting Standards Codification and the executed debt agreement for the specific facts.
IFRS Accounting Standards
IAS 1 requires an entity to have a substantive right at the reporting date to defer settlement for at least twelve months to classify a liability as non-current. Under the IAS 1 amendments on non-current liabilities with covenants, covenants with which the entity must comply on or before the reporting date affect whether that right exists—even if compliance is assessed after that date. Covenants that must be met only after the reporting date do not affect classification at that date, but disclosures are required to help users understand the risk of the liability becoming repayable within twelve months. The amendments apply for annual reporting periods beginning on or after January 1, 2024.
Canadian ASPE
For entities applying Canadian Accounting Standards for Private Enterprises, Section 1510 addresses current liabilities and long-term debt. Section 1510.14 addresses measurable covenant violations and the circumstances in which long-term debt is classified as current, including specified written waiver or grace-period conditions. Do not substitute the IFRS future-covenant disclosure model or the US GAAP analysis for the ASPE requirements. Confirm the current Handbook wording and the precise facts with the entity’s accounting adviser.
8. Coordinate disclosure, audit and liquidity assessments
When a breach has occurred or is reasonably likely, coordinate the accounting conclusion with Treasury, Legal, senior management and the external auditor early. Evaluate the effects on current liabilities, liquidity, available borrowing capacity, refinancing plans, going-concern assessments and subsequent-event analysis as applicable.
For SEC registrants, the SEC Division of Corporation Finance’s Financial Reporting Manual notes that MD&A liquidity and capital-resources discussion may need to address debt instruments and related covenants, particularly where the registrant is or is reasonably likely to be in breach, or covenants affect its ability to obtain additional financing. The disclosure should explain material liquidity trends and uncertainties rather than merely repeat cash-flow statement amounts.
9. Embed the controls in the close and ERP process
Make covenant monitoring a formal close activity, with a calendar task, assigned preparer and reviewer, required evidence and escalation thresholds. Where SAP S/4HANA or another ERP is used, define controlled data extracts for the relevant general-ledger balances and consolidation data. Keep contractual adjustments and lender-specific calculations in a governed calculation layer with version control; do not rely on undocumented manual spreadsheet changes.
Access to debt schedules, covenant workbooks and lender submissions should be role-based. Changes to source mappings, formulas and assumptions should be logged and approved. A dashboard can display headroom and forecast trends, but it does not replace the underlying reconciliation, review or accounting analysis.
Controller’s implementation checklist
| Control | Evidence to retain | Suggested frequency |
|---|---|---|
| Complete agreement and covenant register | Executed agreements, amendments and owner list | At inception; quarterly update |
| Approved covenant calculation methodology | Formula specification and interpretation sign-off | At inception and on amendment |
| Reconciliation of calculation inputs | Trial-balance bridge and adjustment support | Each test date |
| Independent review | Dated reviewer sign-off and challenge evidence | Each calculation |
| Headroom and downside monitoring | Forecast, sensitivity analysis and escalation log | Monthly; more often if at risk |
| Lender certificate approval | Approved final certificate and delivery receipt | Each contractual deadline |
| Breach, waiver and classification assessment | Legal correspondence, waiver and technical memo | When triggered; each reporting date |
| Disclosure and audit coordination | Disclosure checklist and auditor communication | Each reporting period |
Conclusion
Effective covenant management is not simply a ratio calculation performed before a lender deadline. It is a connected control process spanning contract interpretation, accounting data, forecasting, independent review, lender communication and financial-statement presentation. Controllers who establish clear ownership and monitor headroom throughout the year are better positioned to identify problems early and support a defensible reporting conclusion.
Authoritative and technical references
- US GAAP: ASC 470-10 debt classification and covenant violations (Deloitte technical guide). Refer to the current FASB Codification for authoritative requirements.
- IFRS Foundation: IASB amendments on non-current liabilities with covenants.
- IFRS Foundation: IAS 1 Presentation of Financial Statements.
- CPABC: Balance-sheet classification of callable debt obligations under ASPE.
- MNP: ASPE financial statement presentation and disclosure checklist (includes Sections 1510 and 3856).
- SEC Division of Corporation Finance: Financial Reporting Manual, Topic 9—MD&A.
Disclaimer: This article is for general informational and educational purposes only. It is not accounting, legal, tax or investment advice. Apply the current authoritative standards, contractual terms and professional judgment to the entity’s facts.
