Smart covenants: continuous testing instead of quarterly reports
Smart covenants: continuous testing instead of quarterly reports
A covenant is a promise a borrower makes in a loan agreement. Keep leverage below a set level. Keep cash above a set amount. Don't take on more debt without consent. Deliver financial reports by a set date.
Covenants are a lender's early warning system. Breaking one lets the lender step in, renegotiate, or demand repayment before a weakening borrower becomes a loss. But the way covenants are usually checked limits how early that warning comes.
How covenants work today
Most financial covenants are tested quarterly. After the quarter ends, the borrower prepares financial statements and a compliance certificate, signed by an officer, stating that each covenant was met. The lender reviews it, often weeks after the quarter closed.
That means:
- The data is old. A test for the quarter ending March 31 might be reviewed in May.
- The data is self-reported. The borrower calculates its own compliance.
- The checks are infrequent. A borrower can be in breach for most of a quarter before anyone knows.
What makes a covenant "smart"
A smart covenant is a covenant tested automatically against data from primary sources, as often as that data updates. Instead of waiting for a certificate, the lender's system calculates each test directly.
- Minimum liquidity is tested daily against bank feeds.
- Borrowing base is recalculated as each receivable is added or paid, using the advance rate and eligibility rules.
- Concentration limits are checked every time a new asset is funded.
- Delinquency triggers update as payments arrive or don't (see Delinquency, roll rates and vintages).
- Collateral coverage updates as prices move (see Collateral health zones).
Each test result can be fingerprinted and anchored, creating a record of compliance that can't be revised later (see Hash-then-anchor).
What "smart" doesn't mean
It doesn't mean the contract executes itself. A smart covenant is a testing method, not an automatic enforcement mechanism. When a test fails, the result goes to people who decide what to do, according to the loan agreement. Most covenant breaches end in a waiver, an amendment, or a cure, not in enforcement.
It also doesn't cover every covenant. Some can't be tested from data: "no material adverse change" is a judgment, not a calculation. Smart covenants work best for numerical tests against data with a reliable source.
Why it matters
For lenders, the gap between a problem starting and a problem being seen shrinks from months to days. That's the difference between renegotiating with a borrower who's still solvent and recovering from one who isn't.
For borrowers, continuous testing can actually reduce friction. There's less to prepare at quarter-end, fewer disputes about calculations, and early warning of a looming breach while there's still time to fix it.
For investors in the lender, it means the credit quality they're told about reflects the current state of the loans, calculated from source data, rather than last quarter's self-reported certificates.
The terms of a covenant are a legal question. Whether it's being met is a data question. Smart covenants treat it like one.