A compliance certificate is a short statement, delivered with each set of financial statements the loan agreement requires, in which an officer of the borrower certifies that the company is meeting its covenants and that no default exists. It attaches the covenant calculations, usually coverage and leverage ratios, worked from the financial statements using the loan agreement's own definitions. The signer is typically the CFO or, in a smaller company, the owner acting as an officer. Because the certificate is a representation to the lender, a material error in it can itself be an event of default.
- What it is
- A signed statement of covenant compliance, with the calculations attached
- Who signs
- A responsible officer: usually the CFO, or the owner in a smaller company
- When
- With each quarterly or annual set of financial statements the agreement requires
- What it attaches
- Covenant calculations, EBITDA reconciliation and any required schedules
- The risk
- A materially wrong certificate is a misrepresentation, and a default in its own right
What the certificate says
The certificate itself is usually a one- or two-page form attached as an exhibit to the credit agreement. The borrower fills it in each period; it does not draft a new one. Most forms contain the same core statements, in the same order:
- That the signer is a named officer of the borrower and is signing in that capacity.
- That the attached financial statements fairly present the company's financial condition for the period, subject to normal year-end adjustments where they are interim figures.
- That the signer has reviewed the loan agreement and the company's affairs for the period, and that no default or event of default exists, or, if one does, what it is and what the company is doing about it.
- That the attached calculations of each financial covenant are true and correct, and show compliance.
- Any updates the agreement requires: new subsidiaries, new locations holding collateral, changes to insurance, material litigation.
The form is agreed at closing, which is the time to read it. Some lenders slip in additional certifications, such as confirming every representation in the agreement is still true, that turn a routine report into a much broader statement.
Who signs, and in what capacity
Credit agreements define a "responsible officer" or "financial officer" who may sign: typically the chief financial officer, treasurer or controller, and sometimes the chief executive or president. In a company with no CFO, the owner signs as president. The lender wants a senior person who knows the numbers and can be held to them.
Well-drafted forms say the officer signs "solely in his or her capacity as an officer, and not individually". That wording matters. It makes clear the certificate is the company's statement, and the officer is not taking on personal liability by signing it. Borrowers should ask for it if it is missing. That said, an owner who is also a personal guarantor is already on the hook for the loan, and where a guarantee is limited, the limit commonly falls away for fraud or intentional misrepresentation. A certificate the signer knew was false is not protected by the capacity language.
Sign it as though the lender will check it, because at some point it will: at renewal, in a field exam, or when something goes wrong.
The calculations and supporting schedules
The heart of the certificate is the covenant schedule: each financial covenant, the calculation, the required level, and the result. The critical rule is that every figure follows the credit agreement's definitions, not generally accepted accounting principles or the company's internal reports. Covenant EBITDA adds back what the agreement allows and nothing else. Funded debt counts what the agreement counts. Fixed charges include the items the definition lists, which may include distributions, cash taxes and unfinanced capital expenditures.
| Schedule | What it shows | What lenders look for |
|---|---|---|
| EBITDA reconciliation | Net income to covenant EBITDA, one line per add-back | Each add-back permitted by the definition, and within any cap |
| Coverage calculation | Cash flow available against debt service or fixed charges for the test period | The right test period, usually trailing twelve months, and the right payments |
| Leverage calculation | Funded debt against covenant EBITDA | All debt counted, including finance leases and seller notes if defined as debt |
| Liquidity or net worth | Cash, availability, or tangible net worth at period-end | Intangibles and related-party receivables excluded where the definition says so |
| Capital expenditures and distributions | Amounts spent against the agreement's baskets | Nothing above the permitted amounts |
| Headroom | The margin between the result and the required level | Not required, but a trend of shrinking headroom is noticed |
The schedules should tie to the financial statements delivered with them, line for line. An underwriter who cannot trace the EBITDA in the certificate back to the income statement will ask, and the questions are the start of a closer look. A company that can show its covenant headroom quarter by quarter, and explain a change before the lender asks, is treated very differently from one that sends a bare page of ratios.
Asset-based lines also require a borrowing base certificate, often monthly or more frequently. That is a separate document with its own rules, and it calls for its own care; see how to prepare one.
Why an error can itself be a default
Loan agreements make it an event of default if any representation or certificate delivered to the lender was materially incorrect when made. The compliance certificate is such a certificate. So an error in it creates a problem separate from, and sometimes worse than, the covenant it concerns.
The cases that come up in practice:
- An error that hid a breach. The company used an add-back the definition did not allow, reported compliance, and was in fact in breach. The lender now has two defaults: the covenant breach, and the false certificate. The second often has no cure period and undermines the lender's trust in every figure the company has sent.
- An error that did not change the result. A misclassified expense that left the ratio still passing. Technically this may still be a misstatement, though most agreements require it to be material. Correcting it promptly and in writing is almost always the right answer.
- A certificate delivered late or not at all. A breach of the reporting covenant rather than a misrepresentation. Usually curable within the agreement's cure period, but a lender that does not receive certificates on time tends to assume the worst.
- A certificate saying no default exists when one does. For example, a new equipment loan taken without the lender's consent in breach of the negative covenants. The certificate turns an unnoticed breach into a signed false statement.
The protection is the same in each case: build the calculation from the agreement's definitions, have a second person check it, keep the workpapers, and report problems in the certificate rather than around it. A certificate that discloses a breach and describes the plan is honest; it is also the start of the conversation that leads to a waiver or amendment. See what to do when you breach a covenant.
Setting up the process at closing
The simplest time to get the compliance certificate right is before the first one is due. At closing, build a covenant model that follows the agreement's definitions exactly, and test it against the most recent historical period so you know where the company sits. Agree with the lender how any ambiguous terms will be read, such as which one-time costs qualify as add-backs, and put the answer in writing. Set a calendar for delivery that allows for your accountant's schedule, especially for annual statements that must be reviewed or audited; see reviewed vs audited financials.
Transparent's lender package includes a financing model that calculates each proposed covenant on the company's historical and projected figures, so the borrower sees its headroom under each lender's definitions before choosing a term sheet, and has a working model to produce the certificates from after closing. See what goes in the package.
Common questions
- How often is a compliance certificate due?
- Whenever the loan agreement requires financial statements with covenant tests, most often quarterly and annually. Smaller loans may require only an annual certificate. The agreement sets the deadline after each period ends.
- Who signs the compliance certificate?
- A responsible officer as defined in the loan agreement, usually the CFO or controller, or the owner as president in a smaller company.
- Am I personally liable for what I sign?
- Well-drafted certificates are signed in the officer's capacity, not individually. But an owner who has personally guaranteed the loan is already liable for it, and knowingly false statements are not protected.
- What if the certificate shows we missed a covenant?
- Report it accurately. A certificate that discloses the breach and a plan starts the conversation about a waiver or amendment. A certificate that hides it creates a second, more serious default.
- Do SBA loans require compliance certificates?
- SBA loans usually require periodic financial statements, and some lenders add covenants with certificates. Many smaller SBA loans have no financial covenants to certify. The loan authorization and note set the requirements.