Covenant compliance certificate: proving the ratios, not just asserting them

A covenant compliance certificate is the document a borrower delivers to its lender, usually quarterly, stating that the financial covenants in the credit agreement were met for the period and showing the calculation behind each one. It is signed by an officer, and the signature converts an internal spreadsheet into a representation the lender is entitled to rely on.

The certificate is short. The attached schedule is not. Leverage, fixed charge coverage, interest coverage, minimum liquidity — each has a definition written into the credit agreement that rarely matches the equivalent line in the accounts, and the schedule exists to bridge that gap explicitly.

What a covenant compliance certificate contains

• The period covered and confirmation that the financial statements for that period are attached or already delivered.
• Each covenant, its required level, the actual level achieved, and a pass or fail.
• The calculation schedule showing every adjustment: add-backs to EBITDA, pro forma treatment of acquisitions, exclusions from indebtedness.
• A statement on whether any default or event of default has occurred and, if so, what is being done about it.
• The officer’s signature and title.

The definitions are not the accounting definitions

Consolidated EBITDA in a credit agreement is a defined term, often running to a page of permitted add-backs with caps on each. Total indebtedness may include capital leases and exclude subordinated shareholder loans. Fixed charges may be measured on a trailing twelve month basis while the balance sheet inputs are point-in-time.

This is why a covenant compliance certificate cannot be produced by exporting ratios from the accounting system. Someone has to read the definitions, apply them, and leave a schedule showing the bridge from the reported figure to the covenant figure. If the bridge is not written down, next quarter it gets re-derived differently, and the two certificates will not reconcile.

Keep the definition extracts alongside the calculation. The most expensive covenant disputes are not about whether the ratio was met — they are about which of two defensible readings of a defined term was used, twelve months after the person who chose it left.

Delivering it on time

1. Diary the delivery deadline from the credit agreement, not from the closing calendar — it is usually a fixed number of days after quarter end.
2. Draft the schedule as soon as the trial balance is stable, before the audit or review is finished.
3. Circulate the draft to the officer who will sign it, with the definitions attached, so questions surface before signature.
4. Sign and deliver in the form the agreement requires, keeping proof of delivery.
5. File the signed certificate with its schedule and the financial statements it referenced.

Because the certificate only has effect once it is signed and delivered, the signing step is worth doing properly rather than by scanned page. Ettex Signature captures the officer’s signature, timestamps it and keeps the executed certificate with the schedule it certifies, so the version delivered to the lender is the version the file holds.

When a covenant is missed

The certificate still has to be delivered. Reporting a breach on time is a materially better position than delivering late or, worst of all, certifying compliance that did not exist. Most agreements distinguish between a covenant breach — often curable by an equity cure or a waiver negotiated in advance — and a false certificate, which is a representation problem and much harder to unwind.

Where covenant testing depends on figures that are still moving, the honest route is to deliver on the deadline with the calculation shown and flag the items that may change, rather than hold the certificate back until the numbers look better.