Summary: Covenant testing is the periodic check that a borrower still meets the financial and reporting terms of its credit agreement. Each period the borrower delivers financials and a compliance certificate; the lender recalculates every covenant ratio under that agreement’s definitions and compares it with the threshold in force. This post walks through the steps, the places manual tracking breaks, and what examiners expect to see, and points to how the work is automated on the MightyBot platform.
What a credit agreement sets up
A credit agreement carries three kinds of covenants that matter for testing.
Financial covenants set numeric limits: a minimum debt service coverage ratio, a maximum leverage ratio, a minimum liquidity or fixed charge coverage. Each one comes with its own definitions. “EBITDA” in one agreement permits add-backs that another agreement excludes. “Debt” may or may not include leases, subordinated notes or letters of credit. The definitions, not the ratio names, decide the result.
Reporting covenants say what the borrower must deliver and when: annual audited statements within 120 days of year end, quarterly management accounts within 45 days, a compliance certificate with each delivery, and often a budget or borrowing base.
Structural terms change the test over time. Thresholds step down as a loan seasons, amendments reset them, waivers suspend them for a period, and cure rights let a sponsor inject equity to fix a miss. A test is only correct if it uses the terms in force for that period.
The test, step by step
1. Receive the package. The borrower sends statements and a compliance certificate. On a large book they arrive as PDFs, scans and spreadsheets in each borrower’s own layout, and a late package looks the same in a tracker as one nobody has opened.
2. Extract the inputs. Revenue, EBITDA components, interest, scheduled principal, cash, debt balances, and whatever custom items the agreement defines. Each figure should keep a pointer to the page it came from.
3. Apply the agreement’s definitions. Adjusted EBITDA under this agreement, total debt under this agreement, trailing twelve months built from the periods this agreement specifies.
4. Calculate the ratios and compare them with the thresholds in force. Pass or fail is the minimum. Headroom, the cushion between actual and threshold, and the trend across periods are what let a lender act before a breach.
5. Check the certificate. The borrower’s own calculation should agree with the lender’s. Differences usually come from definitions and are worth resolving before the next period.
6. Record the test. Inputs, result, headroom, the policy version that applied, who reviewed it, and any waiver or amendment, with timestamps.
Where manual tracking breaks
Every step above has a failure mode when it runs on spreadsheets and a calendar. Definitions live in formulas that each analyst maintains, so one formula never fits the portfolio. Step-downs and amendments get missed. Statements sit in inboxes. Headroom is rarely tracked, so the first sign of trouble is the breach itself. And the record of a test is a file version and an email thread.
The result is that testing runs on the analyst’s calendar rather than the borrower’s. A ratio that slipped in March gets read in June.
What examiners expect
Bank examiners look at the process as well as the result. The OCC’s Commercial Loans handbook directs examiners to consider a bank’s systems for “monitoring compliance with loan covenants,” its practices for “receiving and analyzing timely financial data,” and how it checks “the ongoing accuracy and reliability of borrower certifications.”
The OCC’s Rating Credit Risk handbook explains why covenants matter to the rating: effective covenants give the bank “an opportunity to trigger protective action” when a borrower’s condition “falls below prescribed standards,” and it tells examiners to “be alert for covenants that have been waived or renegotiated.” The July 2026 Lending and Loan Portfolio Risk Management booklet lists “loan covenant testing” among loan administration functions and counts “Covenant breaches (even if waived)” as financial exceptions a bank should track. The FDIC’s examination manual lists “Adherence to loan covenants” among the factors a loan review analyzes.
For a private credit fund the investment committee and LPs ask the same questions in different words: show each test, the inputs behind it, who reviewed it, and what happened after a waiver.
How the automated version works
On the MightyBot platform each agreement’s covenants are written as plain-English policies that carry its definitions, thresholds, step-downs, cure periods and reporting dates. When a package arrives, agents classify the documents, extract the inputs with a pointer to the page each came from, calculate every ratio, measure headroom and compare the trend. A breach, a shrinking cushion or a missed reporting date raises an alert with the covenant, the value, the threshold and the source documents attached.
Teams usually start in audit mode, where agents run the tests and analysts decide, then let clean cases run straight through as results hold up. The full checklist of what to look for is on the covenant monitoring use-case page, and a comparison of tools is in best covenant monitoring software.
Covenant testing depends on how the loan was boarded. BoardReady sets up each reporting requirement and covenant test from the loan agreement when a CRE loan closes, and MaturityWatch resizes the loan as a refinance as maturity approaches.