CovenantFlow

Commercial Lending

Commercial loan compliance, and what makes a determination defensible.

A compliance status is only worth what the evidence behind it can support. This covers how determinations are made, what has to be preserved, how exceptions are categorised, and why reproducibility matters more than correctness alone.

What is commercial loan compliance?

Loan compliance

In a covenant context, commercial loan compliance is the determination of whether a borrower satisfied the obligations in its credit agreement for a given period, together with the evidence supporting that determination.

One clarification worth making up front, because the phrase is used two ways. Regulatory compliance concerns the lender's own obligations under law and regulation, fair lending, BSA, flood insurance, disclosure requirements. Loan compliance in the sense used here concerns the borrower's obligations under the credit agreement. Both are examined, and they are different subjects with different controls.

The second half of the definition carries most of the weight. A correct determination that cannot be evidenced is, from a control perspective, close to indistinguishable from an incorrect one.

What a compliance determination consists of

A determination is not a status flag. It is a defensible statement with six components, and if any is missing the conclusion has to be argued rather than demonstrated.

  1. The definition applied. Which version of the covenant governed this period, including the defined terms, and the executed document that established it.
  2. The threshold in effect on that test date. After any step-downs, build-ups, or covenant holidays.
  3. The inputs and their provenance. Each value used, the document or system it came from, and the reporting period it belongs to, including whether the statements were internally prepared, reviewed, or audited.
  4. The calculation. Itemized, so a disagreement can be traced to a line rather than debated as a total.
  5. The resulting status. Compliant, non-compliant, or not tested, with the margin to the threshold recorded rather than discarded.
  6. The human element. Who reviewed, approved, or overrode the result, and when.

Notice that "not tested" is a valid and necessary status. A period where the borrower's financials never arrived is not compliant, and recording it as compliant is a misstatement. See covenant compliance automation for how this is captured mechanically.

Compliance certificates

The compliance certificate is the borrower's own statement of covenant compliance, signed by an officer and typically delivered with each set of financial statements. Most agreements require the supporting arithmetic, not just the conclusion.

Three functions, and the third is the one most often wasted:

  • Evidence. A signed officer certification carries weight a spreadsheet does not.
  • Forcing function. Preparing one requires the borrower to compute its own covenants, which surfaces problems on the borrower's side earlier.
  • Cross-check.When the borrower's calculation and the lender's differ, the difference is informative. It usually traces to a defined term, most often an add-back the borrower applied that the agreement caps or excludes.

Accepting the certificate without performing an independent calculation is a control weakness, and a recognisable one. It also forfeits the cross-check, which is where much of the certificate's value actually sits.

Exceptions

The four exception categories

"Exception" is a bank operational term rather than a credit agreement term, and institutions report all four categories to management and examiners.

Financial covenant exception

A test failed. The most visible category and usually the smallest by count. Requires a credit decision: waiver, amendment, cure, reservation of rights, or a risk rating action.

Reporting exception

A required deliverable is late or missing. Under most agreements this is a covenant breach in its own right. Usually the largest category by count and the most predictive of future trouble.

Document exception

A required document was never obtained at closing or has since lapsed: an insurance certificate, a UCC continuation, a lien search, a signed guaranty. Frequently discovered during file review rather than through monitoring.

Policy exception

The loan was approved outside the institution's own credit policy. Tracked separately because it originates in the lender's decision rather than the borrower's performance.

Chronic reporting exceptions deserve more attention than they usually get. A borrower whose accounting function is consistently forty days late is frequently a borrower with other problems, and the pattern is visible well before the financial covenants move.

Auditability and the examination question

The practical test is whether a determination can be reproduced or has to be reconstructed. Reproduction means retrieving the stored definition, inputs, and calculation. Reconstruction means finding the agreement, finding the statements, rebuilding the spreadsheet, and hoping the answer matches what was reported at the time.

What tends to be asked for

  • How a specific covenant determination was reached for a specific period, with supporting inputs.
  • The current exception population, and how it has moved over the review period.
  • Exception history for individual credits: what was identified, when, who was notified, what was decided, when it cleared.
  • Evidence that covenant terms in the tracking system match the executed documents, including amendments.
  • Whether reporting delinquencies are tracked and escalated, not only financial covenant breaches.

The two answers that cause problems

The first is "the analyst who did that has left". The second is "the spreadsheet has been updated since". Both are common, both are honest, and both convert a substantive question into a control finding. Designing the record so neither answer is necessary is cheaper than the alternative, and it is the same work that makes trend analysis possible.

The full evidence discussion, including record retention and versioning, is in section 19 of the complete guide to commercial loan covenant monitoring. Nothing on this page is legal or regulatory advice; examination expectations vary by regulator, institution, and portfolio.

FAQ

Frequently asked questions

What is commercial loan compliance?
In a covenant context, commercial loan compliance is the determination of whether a borrower satisfied the obligations in its credit agreement for a given period, together with the evidence supporting that determination. It covers financial covenant results, delivery of required reports, and adherence to affirmative and negative covenants. It is distinct from regulatory compliance, which concerns the lender's own obligations under law and regulation.
What is covenant compliance?
Covenant compliance is the state of a borrower having satisfied a specific covenant for a specific testing period. It is determined by applying the credit agreement's definitions to the borrower's reported financial data and comparing the result to the threshold in effect on that test date. A complete determination records the definition version applied, the inputs used, the computed value, and the resulting status.
What is a compliance certificate?
A compliance certificate is a document the borrower delivers, typically alongside each set of financial statements, in which an officer certifies the covenant calculations and states whether the borrower is in compliance. Most agreements require the certificate to show the arithmetic rather than only the conclusion, which allows the lender to compare the borrower's calculation with its own.
What evidence do examiners expect for covenant compliance?
Expectations vary by regulator and institution, but the practical standard is that a determination can be reproduced rather than reconstructed. That generally means being able to show which covenant definition was applied, the threshold in effect on that test date, the input values and where they came from, the calculation itself, the resulting status, and who reviewed or approved it. Exception history, what was identified, when, who was notified, and how it cleared, is typically reviewed alongside it.
Is a late compliance certificate a breach?
Under most credit agreements, yes. Delivery deadlines are covenants in their own right, so failing to deliver on time breaches a reporting covenant independent of whether the underlying financial results would have passed. Agreements commonly provide a notice or cure period before a reporting breach becomes an event of default, and what applies to any specific loan depends on that loan's documents.

See how CovenantFlow automates covenant monitoring

Move from loan documents and borrower reporting requirements to structured covenant intelligence, compliance workflows, and portfolio visibility.