Here you can read:
Multi-entity groups face a hidden risk in bank loan covenant compliance: numbers that look safe at entity level can breach at group level due to consolidation rules, currency translation, cash trapped in subsidiaries, and negotiated EBITDA definitions. Many debt covenants issued in recent years contain weaker terms than their predecessors, and earnings add-backs now reduce headline leverage by 15–30% in some transactions, according to analysis by the Financial Stability Board. This article explains how treasury teams map debt covenant inputs to their data sources, maintain a test calendar across facilities, forecast covenant headroom forward, and catch breaches before certificate deadlines arrive.
What are financial covenants and why do lenders test them?
Financial covenants are undertakings by the borrower in a loan agreement, usually expressed as ratios the company must meet at specified test dates. Common examples include interest coverage, leverage ratios such as corporate debt management metrics like debt to EBITDA, and occasionally current ratios or net worth tests. Third-party lenders commonly specify debt-to-EBITDA, debt-to-equity, and interest cover covenants in commercial agreements.
Covenant compliance is evidenced by a certificate delivered with the financial statements, typically signed by two directors. Investment-grade loan templates often require quarterly testing, and the certificate deadline usually falls 45 to 60 days after quarter-end. Breaching a debt covenant is a default event under most credit agreements, which makes the whole group's process material, not just the borrowing entity's. Treasurers should direct the compliance process and ensure performance against financial covenants is properly forecast throughout the year.
Where covenant numbers drift in a multi-entity group
Why do covenant calculations in multi-entity groups produce different results from entity-level accounts? Five main areas create gaps between what treasury sees and what the covenant test measures.
| Where the number drifts | Why in a multi-entity group | What to settle |
|---|---|---|
| Group perimeter | Loan agreements may exclude certain entities or restrict which cash counts | Which entities are in the test; whether the covenant group matches the accounting group |
| Cash in net debt | Definitions vary; negotiations cover caps, offshore restrictions, and whether non-loan-party cash counts | Which cash counts, where it sits, and any caps or restrictions |
| Currency | Debt translated at spot rates can rise against EBITDA translated at average rates; currency moves alone can cause breaches | One rate convention for both sides of the ratio |
| Intragroup balances | Intragroup loans eliminate on consolidation, but FX differences on them may not | Whether intragroup debt is excluded and how FX on it is treated |
| EBITDA | EBITDA isn't an IFRS concept; it's negotiated item by item with add-backs for restructuring, synergies, run-rate adjustments | Permitted add-backs, caps, and pro forma adjustments for M&A |
Group perimeter issues arise because loan agreements may define the test group differently from your statutory reporting group. A cash position may show £50 million, but if £15 million sits outside the guarantor group and the agreement caps recognised cash, the covenant net debt is higher. Furthermore, intragroup balances require careful handling. While intragroup loans eliminate on consolidation, the foreign exchange differences on them may not, creating unexpected volatility. Similarly, cash in net debt must be scrutinised to ensure only eligible, non-restricted cash is netted against debt figures.
Currency translation creates risk because debt translated at closing spot rates can rise relative to EBITDA translated at average rates. Some agreements include exchange rate equalisation provisions to prevent this mismatch, but borrowers must negotiate them explicitly.
EBITDA is a constructed figure where every element gets negotiated. Common add-backs include restructuring costs, transaction expenses, synergies, and run-rate adjustments. Recent market practice shows caps on add-backs typically ranging from 10 to 25 per cent of EBITDA, though some transactions push wider. Understanding how EBITDA is calculated is critical for covenant management.
Mapping each debt covenant input to the data that feeds it
How do you connect each element of a covenant calculation to the systems and owners who maintain it? A structured mapping ensures nothing falls through gaps between treasury, group finance, and entity controllers.
| Covenant input | Where it lives in a group | Owner | Typical refresh |
|---|---|---|---|
| Debt | Entity ledgers, bank statements, facility agreements, lease schedules | Treasury | Monthly, with quarterly bank confirmations |
| Cash | Bank portals, daily treasury reports; excludes restricted/trapped balances per covenant definition | Treasury | Daily position; covenant-definition cash reconciled monthly |
| EBITDA | Consolidation system; operating profit adjusted for negotiated add-backs | Group finance / FP&A | Monthly with detailed build-up for audit |
| Interest | Loan amortisation schedules, derivative registers, interest accrual models | Treasury | Monthly, reconciled to entity ledgers |
| FX rates | Specified rate source in credit agreement | Treasury or group finance | Locked at each test date per contract |
Debt comprises loan and bond balances, and lease liabilities if the covenant definition brings them into scope. Cash includes bank balances by entity, but the covenant definition determines which accounts count and whether any caps or restrictions apply. Modern treasury management platforms can help consolidate facility terms and cash positions in real time.
The covenant calendar: test dates, certificates and cross-defaults
What should a covenant calendar track beyond test dates? Quarterly covenant compliance testing is standard, but the calendar needs granularity to manage springing covenants, cure windows, and cross-default implications.
Key calendar elements for each facility:
- Test dates: last day of each financial quarter
- Certificate deadline: typically 45 or 60 days after quarter-end
- Springing trigger: if applicable, the threshold (e.g. revolver drawn over 35 to 40% of commitments at quarter-end)
- Equity cure capacity: remaining cure rights, for example, two in any four quarters and five over the loan life
- Owner and backup: primary responsible person and backup per facility
- Cross-default threshold: materiality levels that trigger other facilities
Test dates are usually the last day of each financial quarter. Some covenants are springing, meaning they only get tested when a revolving credit facility is drawn above a threshold, often 35 to 40 per cent of commitments. Cross-default provisions mean a breach in one facility can trigger default across others, typically with materiality thresholds.
Equity cure rights allow shareholders to inject capital that is added to EBITDA for covenant purposes, giving the borrower a second chance. Cures usually come with caps, which are commonly two quarters in any four and five over the loan life under standard loan market practices.
Calculating covenant headroom forward
How much covenant headroom does a firm actually have? Let’s look at hypothetical Example Export Group PLC:
Example Export Group PLC: Covenant Headroom Analysis
| Metric | Current position | Covenant breach point | Headroom available | Practical meaning |
|---|---|---|---|---|
| Leverage covenant limit | 3.0x | 4.0x | 1.0x | The firm is currently operating 1.0x below the maximum lender threshold. |
| EBITDA downside risk | £100 million | £75 million | 25 per cent or £25 million | Earnings can decline by a quarter before the current debt load triggers a default. |
| Additional debt capacity | £300 million | £400 million | £100 million | The firm can borrow an additional £100 million before breaching the covenant, assuming earnings stay flat. |
Lenders set covenant levels with deliberate headroom against a base case. In direct lending, cushions of 25 to 40 per cent appear common at closing, though corporate investment-grade borrowers may see different figures. Covenants should leave room for moderate performance weakening without forcing immediate amendment discussions.
Treasurers should forecast covenant headroom forward as part of regular cashflow management. Covenants that may constrain a company's plans should be reflected explicitly in financial forecasts. Integrating covenant headroom projections into a firm’s 13-week cash flow forecast ensures short-term liquidity planning accounts for covenant constraints.
Forecast headroom using the contract definition of each ratio, including any caps on EBITDA add-backs that expire during the forecast period. Stress-test for foreign exchange moves, because a 10 per cent depreciation can eliminate headroom even if operating performance is stable.
When a covenant test fails
What happens if a covenant is breached? The consequences hit immediately, and responses depend on timing and the lender's willingness to provide relief.
A breach at or before the reporting date that makes the loan repayable on demand requires current classification under IAS 1 Presentation of Financial Statements, even if the lender agrees after year-end not to demand payment. A waiver or grace period must be in place by the reporting date. A waiver is a complete surrender of the lender's rights to demand repayment for that specific breach. A grace period must extend at least 12 months beyond the reporting date to support non-current classification.
Equity cure rights, where available, allow shareholders to inject cash or subordinated instruments that are added to EBITDA for the failed test, effectively reversing the breach. Early engagement with lenders is critical because amendments take time to document and execute.
Capital expenditure usually drops sharply after covenant violations, net debt issuance falls, and lenders frequently raise interest rates and reduce credit availability. Borrowers rarely switch lenders following a violation, which suggests renegotiation within the existing banking group is the norm.
A covenant tracking check for your next test date
What should one verify before each test date?
- Pull the full definitions from your credit agreement: group perimeter, EBITDA build-up, net debt, accounting basis, and rate convention
- Confirm the consolidation perimeter matches the covenant group definition
- Reconcile cash by entity against the covenant definition, flagging restricted balances and trapped offshore cash
- Check EBITDA add-back caps and ensure supporting documentation is ready for lender review
- Update your test calendar with all facilities: test dates, certificate deadlines, responsible owner, and backup contact
- Forecast headroom forward for the next four quarters, with base case, FX sensitivity, and downside scenarios
- Decide early whether a waiver, amendment, or cure is needed, because any relief must be in place before year-end
Modern treasury platforms centralise debt portfolios across every entity and bank, automate amortisation schedules, track covenant compliance, and connect debt positions to cash forecasting in real time. The architecture is designed to proactively surface covenant risks and optimise liquidity using advanced models. While the vision is to provide highly intelligent insights, the human stays in control at all times.
