What are loan covenants?
Loan covenants are promises written into a loan agreement that the borrower must keep for as long as the loan is outstanding. Affirmative covenants require the borrower to do things, such as deliver financial statements, keep insurance in force and pay taxes. Negative covenants restrict actions, such as taking on more debt, selling key assets or paying large distributions without consent.
Financial covenants are the subset that sets numeric tests on the borrower's results, like a minimum debt service coverage ratio or a maximum leverage ratio. They work as an early warning. A breach does not mean the loan has stopped paying, but it gives the bank the right to step in and talk about the problem while there is still room to fix it.
Which financial covenants do banks use most?
Most commercial loans, whether made by a community bank, a credit union business lending team or a larger lender, rely on a short list of financial covenants. Larger and syndicated deals add more tests and more detailed definitions. In every case the exact definitions matter more than the names, so the agreement should spell out how each figure is calculated, which statements it uses and how often it is tested.
- Debt service coverage ratio (DSCR): cash available for debt service divided by required principal and interest. Often set as a minimum, such as 1.20x or 1.25x.
- Leverage: usually total funded debt divided by EBITDA, or total liabilities divided by tangible net worth. Set as a maximum.
- Minimum liquidity: a floor on unrestricted cash, or cash plus available credit, held by the borrower or guarantor.
- Minimum tangible net worth: equity less intangible assets, often required to stay above a dollar amount.
- Current ratio or working capital: current assets compared with current liabilities, common on working capital lines.
- Capital expenditure or distribution limits: caps that protect cash flow from being spent elsewhere.
How do you calculate a DSCR covenant? A worked example
Example only, with made-up round numbers. Suppose the loan agreement defines cash available for debt service as EBITDA minus unfinanced capital expenditures, cash taxes and distributions, and requires a minimum DSCR of 1.20x, tested annually on the borrower's fiscal year-end statements. Debt service is defined as scheduled principal and interest on all funded debt, at the bank and elsewhere, over the same twelve months. Writing the definition out like this before doing the math is a good habit, because most covenant disputes come from definitions, not arithmetic.
The borrower's year-end figures show EBITDA of $1,200,000, unfinanced capital expenditures of $100,000, cash taxes of $50,000 and distributions of $150,000. Cash available for debt service is $1,200,000 minus $300,000, or $900,000. Scheduled principal of $500,000 plus interest of $200,000 gives debt service of $700,000. DSCR is $900,000 divided by $700,000, or about 1.29x. The borrower passes the 1.20x test.
What is covenant headroom and why track it?
Headroom is the distance between the borrower's actual result and the covenant level. A pass at 1.29x against a 1.20x minimum is very different from a pass at 2.00x. Tracking headroom, not just pass or fail, shows which borrowers are drifting toward trouble.
In the example above, debt service of $700,000 at 1.20x requires $840,000 of cash available. The borrower has $900,000, so cash flow could fall by $60,000, about 7%, before the covenant breaks. That is thin. A bank watching headroom would want interim statements, a conversation about the borrower's outlook and perhaps a look at what a modest revenue decline would do. Trending headroom over several test dates is one of the most useful signals a commercial portfolio has.
What are reporting covenants and compliance certificates?
Reporting covenants require the borrower to deliver information on a schedule. Typical items are annual financial statements within a set number of days after fiscal year end, interim statements, tax returns, borrowing base certificates for asset-based lines and personal financial statements from guarantors.
A compliance certificate is a signed statement, usually from the borrower's chief financial officer or owner, that shows the covenant calculations for the period and confirms the borrower is in compliance or describes any breach. The bank should recalculate the figures itself rather than accept the certificate at face value, since definitions in the agreement are easy to misapply. Late or missing reporting is a breach in its own right and often an early sign of trouble.
What happens when a covenant is breached?
A covenant breach is usually an event of default under the loan agreement, which gives the bank rights such as calling the loan or raising the rate. In practice, most breaches lead to a conversation rather than immediate action. The bank first works to understand the cause and whether it is temporary.
Common outcomes include a one-time waiver, often with a fee, an amendment that resets the covenant level, added collateral or guarantees, tighter reporting, or a downgrade in the risk grade. Waivers should be documented in writing with the specific breach, the period covered and any conditions. A pattern of repeated waivers on the same borrower deserves attention, because it often means the covenant no longer fits the business or the business is weakening.
How do you set up covenant monitoring?
Covenant monitoring works best as a routine with clear ownership, not a scramble at year end. In many institutions the relationship manager, credit analyst and loan operations each hold part of the process, which makes it easy for a missed certificate or a late recalculation to fall between them. Writing down who does what, and when, matters more than the tool you use. A basic setup covers the following.
- A covenant record for every loan: definition, required level, test frequency and first test date.
- A calendar of reporting due dates with reminders before and after each date.
- Recalculation of each covenant from the borrower's statements, not just the certificate.
- Headroom tracked at each test date so trends are visible.
- A log of breaches, waivers, amendments and their conditions.
- Escalation rules that connect breaches and thin headroom to risk grade review.
How should covenants be set at origination?
Monitoring is easier when covenants are set well in the first place. A covenant level should leave room for normal swings in the borrower's results while still catching a real decline. A common approach is to base the level on historical and projected results, with enough cushion that an ordinary weak quarter does not trigger a breach but a sustained drop in cash flow does. Setting a DSCR covenant at exactly the borrower's current ratio almost guarantees a breach at the first dip.
Definitions deserve the same attention as levels. Spell out whether EBITDA includes one-time items, how distributions and capital expenditures are treated, whether the test uses trailing twelve months or fiscal year figures, and whether a guarantor's cash counts toward a liquidity covenant. Make sure the definitions in the loan agreement match those used in the spread and credit memo. Differences between approved terms and signed documents are a common source of disputes later, so check them at closing.
How Aarvion helps
Aarvion Risk OS Commercial Credit tracks covenants with headroom, breaches, waivers and compliance certificates in one place. Before a loan reaches covenant tracking, approvals are routed by the bank's delegated authority matrix, and a closing check compares approved, signed and booked terms, so the covenants being monitored match what was actually approved and signed.
Covenant results feed annual review drafts and a portfolio monitor that ranks borrowers by review priority. Every AI step is checked against the bank's own rules, which can allow, hold or block it, or stop all activity, and each step is recorded.
