If your company signed term loans or a revolving line of credit before 2022, your lease accounting change may have quietly put your bank covenant compliance at risk. ASC 842 forces nearly every operating lease onto the balance sheet, and that new liability can inflate the leverage ratios your lender tests every quarter. The result is a technical default: a covenant breach triggered by an accounting rule change rather than any deterioration in your actual cash flow or operations.
Quick answer: ASC 842 does not change how much cash you owe, but it adds an operating lease liability to your balance sheet that can push debt-to-equity, leverage, and tangible net worth ratios out of covenant range. To protect your bank covenant compliance, calculate the pro forma impact of your right-of-use liabilities before the next testing date, then negotiate a “frozen GAAP” clause so the lease standard change cannot, by itself, cause a default.
What Did ASC 842 Actually Change on the Balance Sheet?
Under the prior standard, operating leases lived in the footnotes. You disclosed future minimum lease payments, but the obligation never appeared as a liability on the face of the balance sheet. ASC 842, issued by the Financial Accounting Standards Board in Accounting Standards Update 2016-02, ended that off-balance-sheet treatment for lessees.
The standard now requires a lessee to recognize, for nearly every lease longer than 12 months, a right-of-use (ROU) asset and a corresponding lease liability measured at the present value of the remaining lease payments. This applies to operating leases such as office space, warehouses, equipment, and vehicles, not just to capital or finance leases. The economics of the lease did not change, only the presentation did.
For private companies, ASC 842 became effective for fiscal years beginning after December 15, 2021. A calendar-year private company therefore reported under the new standard for the first time in its December 31, 2022 financial statements, and the liabilities have been carried on every balance sheet since. If your loan agreement predates that adoption, its covenant definitions were almost certainly written against the old accounting.
That timing gap is the root of the problem. A lender who underwrote your facility in 2019 or 2020 set leverage and net worth thresholds based on balance sheets that did not include capitalized operating leases. When the same balance sheet suddenly carries a multimillion-dollar lease liability, the covenant math shifts even though nothing about your ability to service the loan has changed. The covenant was calibrated to one accounting world and is now being tested in another.
Why Do Operating Lease Liabilities Distort Your Covenant Ratios?
Most credit agreements test a handful of financial covenants on a recurring basis: a maximum leverage ratio, a minimum tangible net worth, a minimum debt service coverage ratio, or a maximum debt-to-equity ratio. Each of these depends on how liabilities and equity are measured, and ASC 842 changed the inputs.
Consider a company with a five-year office lease and meaningful annual rent. Capitalizing that lease can add a large operating lease liability to the balance sheet overnight. If your covenant defines “total liabilities” or “total debt” broadly enough to capture it, your leverage ratio rises even though your sales, margins, and cash position are unchanged.
The damage compounds with tangible net worth covenants. The ROU asset is generally treated as an intangible or right-of-use asset rather than tangible property, so a tangible net worth calculation often excludes the asset side while the lease liability still reduces net worth. That asymmetry can sink a covenant that looked comfortable a year earlier. The same dynamic appears whenever an accounting standard changes the measured inputs to a ratio: as the Journal of Accountancy explained in its analysis of getting debt covenant ratios right, a standard change can put a borrower in apparent violation of a covenant even when nothing about the underlying business has shifted, and most agreements lack language addressing how such changes flow through to the covenant calculation.
There is an important nuance. ASC 842 characterizes the operating lease liability as an operating liability, not as debt. A covenant that tests “funded debt” or “interest-bearing indebtedness” using a precise definition may exclude operating lease liabilities entirely. Whether you have a problem depends entirely on the specific covenant language in your agreement, which is why a careful reading comes before any conversation with the bank.
This is also why two companies with identical leases can reach opposite conclusions. One agreement defines the tested liability narrowly and is untouched by ASC 842, while the other sweeps in every balance sheet obligation and produces an immediate breach. The standard is uniform, but its covenant consequences are entirely a function of drafting.
How Do You Measure Your Exposure Before the Bank Does?
The worst way to learn about a covenant breach is from a default notice. Get ahead of it by running a pro forma covenant analysis well before your next quarterly or annual testing date.
Start by pulling every covenant definition from your credit agreement: the exact wording of “indebtedness,” “total liabilities,” “tangible net worth,” and any GAAP reference clause. Then recompute each ratio two ways, with and without the ASC 842 operating lease liability, so you can isolate exactly how much of any change is driven by the accounting standard rather than operations. This separation is the heart of your negotiating position.
This kind of analysis sits squarely in the work our audit and assurance team performs alongside lease implementation, because the ROU asset and liability calculations also affect your audited financial statements and footnote disclosures. Getting the present value, discount rate, and lease term right is not optional, and errors there flow straight into your covenant math.
Document your findings in a short memo before you call your lender. Show the ratio before adoption, the ratio after adoption, and the precise dollar impact of the lease liability. Lenders respond far better to a prepared borrower who frames the issue as a definitional artifact than to one who simply reports a breach.
The memo also serves you internally. Boards, owners, and finance teams need to understand that a covenant flag driven by ASC 842 is a presentation issue rather than a sign of distress, and a clear before-and-after reconciliation prevents an accounting change from being mistaken for a business problem.
How Do You Negotiate Frozen GAAP and Semi-Frozen GAAP Language?
The cleanest structural fix is a “frozen GAAP” clause. This provision states that covenant calculations are based on GAAP as in effect on a fixed date, typically the closing date of the loan, so that subsequent accounting changes such as ASC 842 do not alter the covenant math. Many loan agreements signed before adoption already contained such language, which is the first thing to check.
A common middle ground is a “semi-frozen” or “negotiate in good faith” clause. Under this approach, when a GAAP change would otherwise affect a covenant, the borrower and lender agree to renegotiate the affected ratios in good faith to preserve the original economic intent, or the change is simply disregarded until they do. This keeps the financial statements fully GAAP-compliant while neutralizing the covenant distortion.
If your agreement has neither, you have several practical options to raise with your lender. You can request a formal amendment that excludes operating lease liabilities from the relevant covenant definitions, you can ask for a covenant waiver for the affected periods, or you can negotiate adjusted ratio thresholds that account for the new liability. Banks generally have little appetite to call a performing loan over an accounting-driven technical default, but they expect you to surface the issue rather than ignore it.
These conversations often coincide with refinancing, acquisitions, or new debt, where covenant structures get rewritten anyway. Our transaction advisory team helps borrowers model covenant headroom and structure lease-aware definitions into new credit agreements so the same problem does not resurface at the next financing. Building frozen GAAP protection into the document at signing is far cheaper than amending under pressure later.
Practical Steps to Stay Compliant
Treat covenant management as an ongoing process, not a one-time fix. Review every credit agreement for its GAAP reference language and flag any that test broad liability or net worth measures. Recompute covenants on a pro forma basis each quarter so the lease liability never produces a surprise at the testing date.
Keep your lender informed early and in writing. A proactive memo explaining the ASC 842 impact, paired with a request to add or confirm frozen GAAP language, preserves the relationship and reduces the chance of an adverse notice. Coordinate this with your CPA so the covenant analysis ties directly to the lease calculations in your financial statements.
Finally, build covenant awareness into your lease decisions going forward. Before signing a long-term lease, model how the new liability will move your leverage and tangible net worth ratios, because the accounting consequence is now immediate and visible to every lender who reads your statements.
Frequently Asked Questions
Does ASC 842 actually increase the amount of debt my company owes?
No. ASC 842 changes presentation, not economics. The cash you are obligated to pay under a lease is identical before and after adoption. The standard simply moves the operating lease obligation from the footnotes onto the balance sheet as a lease liability, which can affect ratios that are calculated from balance sheet figures even though your underlying cash commitments are unchanged.
Will my bank call my loan over an ASC 842 technical default?
It is unlikely that a lender will call a performing loan solely because of an accounting-driven technical default, but the risk is real and should not be ignored. A breach can give the bank the contractual right to accelerate the loan, increase pricing, or impose new conditions. The safest course is to identify the exposure early, document that the breach stems from the accounting change rather than from operations, and request frozen GAAP language or a waiver before the testing date.
What is a frozen GAAP clause and how do I get one?
A frozen GAAP clause fixes covenant calculations to GAAP as it existed on a specific date, usually the loan closing date, so later standard changes like ASC 842 do not affect the covenant math. You obtain one either by confirming it already exists in your agreement or by negotiating it into a new or amended credit agreement. Lenders frequently agree, because the clause keeps your statements GAAP-compliant while preserving the economic intent both parties originally bargained for.
Which covenants are most affected by operating lease liabilities?
Leverage ratios, debt-to-equity ratios, and tangible net worth covenants are typically the most sensitive, because the new lease liability raises measured liabilities while the right-of-use asset is often excluded from tangible net worth. Covenants that define “debt” narrowly as funded or interest-bearing indebtedness may not be affected at all, since ASC 842 classifies operating lease liabilities as operating rather than financial obligations. The only way to know is to read your specific covenant definitions and run the numbers both ways.
