Skip to main content

Callable Debt and Covenant Violations, Explained: When Your Long-Term Loan Lands in Current Liabilities

Published 13 min readMike ThriftMike Thrift
Callable Debt and Covenant Violations, Explained: When Your Long-Term Loan Lands in Current Liabilities
On this page

Your ten-year term loan has nine years left to run. The bank has never complained, never called, never hinted it wants its money back early. Then your year-end close reveals you missed a debt-service coverage ratio by a tenth of a point — and your accountant tells you the entire loan balance now sits in current liabilities, your current ratio just collapsed, and two other loan agreements are asking questions. Nothing about the loan changed except one ratio on one date. Under ASC 470, that can be enough.

This is the balance-sheet classification trap in long-term debt: a covenant violation at the balance sheet date can make an otherwise long-term obligation callable, and callable means current — even if the lender never demands repayment and shows no sign of doing so. Here is how the rule works, the three ways debt stays long-term anyway, and how demand provisions and subjective acceleration clauses change the answer.

What "Callable" Means for Classification​

In debt agreements, "callable by the lender" and "puttable to the borrower" describe the same economics from opposite sides: the lender holds something close to a put option on the loan and can hand it back to you — demand repayment — before maturity. Some puts are exercisable at any time; others spring to life only when a specific event occurs, such as breaching a covenant.

The classification rule sits in ASC 470-10-45-10 through 45-11. Obligations that by their terms are due on demand, or will be due on demand within one year (or the operating cycle, if longer) from the balance sheet date, are current liabilities — even if you do not expect to pay them within that period. And current liabilities include long-term obligations that are or will become callable because you violated a provision of the debt agreement at the balance sheet date, or because an uncured violation will make them callable once a grace period runs out.

Note what the rule does not ask: whether the lender noticed, whether it cares, or whether it plans to call. The right to call is what matters, not its exercise.

The Covenants That Can Trigger It​

Loan covenants come in three flavors, and any of them can carry an acceleration remedy:

  • Affirmative covenants — things you must do: maintain insurance, deliver audited financial statements on time, pay taxes, keep the collateral in good repair.
  • Negative covenants — things you must not do: take on more debt, sell key assets, pay dividends above a cap, merge without consent.
  • Financial covenants — ratios and metrics you must maintain, tested quarterly or annually: minimum current ratio, maximum leverage ratio, minimum debt-service coverage, minimum net worth, days cash on hand.

For classification purposes, what matters is whether the covenant is objectively determinable — a ratio computed from defined financial statement line items — or subjective, such as maintaining "satisfactory operations" or avoiding a "material adverse change." Objective violations follow the mechanical rule below. Subjective clauses follow a probability-based rule of their own, covered later in this post.

Two agreement features multiply the damage. A cross-default clause lets other lenders declare you in default because you defaulted elsewhere, so one tripped ratio can cascade across every facility that references it. And interim measurement dates mean the test is not only at year-end: a quarterly covenant breached at March 31 raises the same classification question for March financial statements as a December breach does for annual ones.

The Core Rule: Violation at the Balance Sheet Date Means Current​

If you have violated an objectively determinable covenant as of the balance sheet date, and the violation gives the lender the right to accelerate — to make the debt due on demand or within the next year — the debt is classified as current. Full stop. The lender's silence changes nothing; the reclassification reflects the lender's rights, not its intentions.

This surprises borrowers for two reasons. First, the economics feel unchanged: same loan, same payments, same maturity date on the note. But classification answers a different question — could the lender demand the money within a year? — and after a violation, the answer is yes. Second, the whole balance moves, not just next year's installments. A $2 million note with nine years left lands in current liabilities in full, which is exactly why the current ratio craters.

Related balances travel with the debt. Unamortized discounts, premiums, and debt issue costs are reclassified to current as part of the debt's carrying amount. That reclassification does not shorten their amortization period or force an immediate write-off on its own — but you should reassess whether the circumstances (your financial condition, the odds of a waiver, the odds the lender calls) now point to a write-off or a shorter amortization life.

Three Ways the Debt Stays Long-Term Anyway​

ASC 470 provides three exceptions. Each has teeth, and each is narrower than borrowers hope.

1. A waiver that actually covers the risk​

The lender waives — or subsequently loses — the right to demand repayment arising from the violation, for more than one year (or operating cycle) from the balance sheet date. "Subsequently loses" covers the case where you cure the violation after year-end so the debt is no longer puttable when the statements go out.

The trap is the forward-looking test. When the lender waives this period's violation but requires you to meet the same covenant (or a stricter one) at measurement dates within the next twelve months, the debt stays noncurrent only if it is not probable you will fail again. If failing the next test is probable, the debt is current despite the waiver. In practice the bar is forgiving in one direction: as long as meeting the covenant is at least reasonably possible, noncurrent classification holds — only a probable repeat failure forces it current.

Because interim dates count, a waiver that covers only the annual test while quarterly tests loom is incomplete. When you negotiate a waiver or forbearance agreement, make sure every measurement date in the next year — quarterly and annual — is addressed in the document, and get it in writing before the financial statements are issued.

2. A grace period you will probably use successfully​

If the agreement gives you a contractual cure window and it is probable you will cure the violation inside it, the debt can stay noncurrent under ASC 470-10-45-11(b). "Probable" here means likely, not merely possible: document the contractual cure mechanism and the concrete reasons cure will happen in time — a scheduled equity injection, an asset sale under contract, a ratio that self-corrects when a seasonal receivable collects.

Without that probability assessment on paper, a grace period alone does not save the classification. And if the grace period expires unmet, the debt was callable all along.

3. Refinancing on a long-term basis​

If before the statements are issued you actually refinance — issuing long-term debt or equity — or you enter a financing agreement that lets you refinance long-term, the debt can stay noncurrent. The financing agreement must not expire within a year, must be cancelable only on objective measures, must itself be violation-free (or waived), and the lender must be financially capable of honoring it.

The sting in this exception is that subjective acceleration clauses in the refinancing agreement disqualify it. A backup revolver laced with material-adverse-change language cannot support noncurrent classification, because borrower and lender may read the clause differently and the ability to refinance is therefore not assured.

Demand Provisions vs. Subjective Acceleration Clauses​

These two features look similar — both let the lender pull maturity forward — but their classification treatment is nearly opposite.

A demand provision gives the lender the right to demand repayment at any time, for any reason or none. Typical language: "principal and interest due on demand or annually," or a term note maturing "in monthly installments or on demand, whichever is earlier." Debt with a demand provision is current, period — even if the lender has never used it, even if your finances are excellent, even if liquidation within the year is not expected. There is no probability assessment to make.

A subjective acceleration clause (SAC) lets the lender accelerate only upon conditions that are not objectively determinable — the classic example is a material-adverse-change (MAC) clause triggering if your business suffers a change the lender deems material. Unlike a demand note, the lender must assert that the condition occurred; it cannot simply demand payment without a reason. Classification follows the likelihood of acceleration at the balance sheet date, using the ASC 450 probability ladder:

  • Probable (recurring losses, liquidity problems) — classify the debt as current.
  • Reasonably possible — keep it noncurrent, but disclose the clause.
  • Remote — noncurrent, no disclosure required.

So a healthy borrower with a MAC clause and no violations reports noncurrent debt with no disclosure, while the identical borrower with a demand note reports current debt. The difference is entirely in who must justify what: a demand lender needs no justification, while a SAC lender must point to a condition — and your assessment of whether it will is what drives the accounting.

Violations After Year-End but Before Issuance​

Compliance is measured at the balance sheet date, so a violation that first occurs after year-end — a missed March ratio test, a covenant tripped by a post-year-end asset sale — generally leaves the balance sheet classification alone. The debt stays noncurrent, and the violation is handled the way subsequent events are: with disclosure of the adverse consequences if future compliance is in doubt.

But there is an important carve-out for credit-related covenants violated before the statements go out. Deloitte's accounting roadmap takes the position — confirmed through informal discussions with the SEC staff — that when a credit-related violation (a quantitative ratio, a going-concern covenant) occurs after the balance sheet date but before issuance, it should generally be treated the same as a balance-sheet-date violation: current classification unless a waiver, grace-period, or refinancing exception applies. The leading example is a loan requiring a "clean" audit opinion: if your auditor issues a going-concern emphasis after year-end, the covenant fails in the new year, yet the debt is presented as current in the year just ended — because the facts behind the opinion existed at the balance sheet date. PwC reaches a compatible place by a different road: a literal read says noncurrent, but the guidance's "unless the facts and circumstances would indicate otherwise" invites current classification when, as with a going-concern opinion, that is plainly the more appropriate presentation.

The practical takeaway: do not assume a post-year-end violation is automatically a next-period problem. If it is credit-related and known before issuance, run it through the same waiver-or-current analysis as a year-end breach, and talk to your auditor early.

What Reclassification Actually Costs You​

Moving a loan from long-term to current is not a cosmetic relabeling. The knock-on effects are where the real damage lives:

  • Your current ratio collapses. Working capital and every ratio built on it deteriorate overnight, which is painful precisely when lenders, sureties, and suppliers are reading the statements.
  • Cross-defaults can cascade. Other agreements with cross-default or cross-acceleration clauses may now give their lenders call rights, forcing the same current-or-waiver analysis on every facility in the stack.
  • Going-concern scrutiny intensifies. A current-liability-heavy balance sheet can feed the substantial-doubt assessment under ASC 205-40 — and a going-concern opinion can itself trip opinion covenants, closing the loop described above.
  • New borrowing gets harder. A balance sheet showing massive near-term obligations changes every credit conversation, even when everyone in the room knows the original lender has no intention of calling.

None of this requires the lender to lift a finger. The rights embedded in the agreement do all the work.

Tracking Covenants in Your Books​

Covenant compliance is a calendar discipline backed by a chart of accounts that can show the reclassification cleanly. Keep term debt split between current and long-term accounts so the year-end move is a single entry rather than a spreadsheet exercise:

2026-01-01 open Liabilities:Notes-Payable:Current
2026-01-01 open Liabilities:Notes-Payable:Long-Term
 
2026-12-31 * "Reclassify term loan — DSCR covenant breached, callable at lender option" #covenant
  Liabilities:Notes-Payable:Long-Term  -250000.00 USD
  Liabilities:Notes-Payable:Current     250000.00 USD

The tag marks every reclassification entry so you can pull the full history of covenant-driven moves at audit time. Pair this with dated reminders for each test — every quarterly measurement date, every financial-statement delivery deadline, every waiver expiry — because the most common failure is not a bad quarter but a good quarter nobody tested until the auditors asked. If you outgrow a reminder list, a proper close checklist that ties each covenant to the report proving compliance is the next step up; either way, the discipline is the same: know every test date, run every test before the auditors do, and document the probability calls behind grace-period and forward-compliance conclusions while the evidence is fresh.

A Year-End Covenant Checklist​

Work through this before the auditors arrive, not after:

  1. Read every debt agreement, including amendments. Confirm each covenant's definition (ratios are defined terms — "EBITDA" in your loan may exclude items GAAP EBITDA includes), each measurement date, each grace period, and whether cross-default clauses link your facilities.
  2. Test every covenant at every measurement date in the period, interim dates included. The classification question is asked per reporting date, not once a year.
  3. Calendar the forward tests. If you needed a waiver this period and face the same covenant within twelve months, assess now whether repeat failure is probable — that assessment, not the waiver alone, decides classification.
  4. Negotiate waivers early and completely. Waivers for widely held or syndicated debt can take months; cover interim measurement dates in the document; get it signed before issuance.
  5. Evaluate SACs on the facts. If losses or liquidity strain make lender acceleration probable, the clause alone can force current classification even with every objective covenant met.
  6. Mind the post-year-end window. A credit-related violation before issuance — especially an audit-opinion covenant — gets the same analysis as a year-end breach.
  7. Document everything. The waiver, the grace-period cure plan, the forward-compliance assessment, the SAC probability call: each is an audit assertion that needs evidence, not just a conclusion.

The unifying lesson is that debt classification measures the lender's rights at a point in time, not your relationship with the lender over time. A friendly bank that would never call still holds a call right after a breach, and the balance sheet must say so. Test early, waive completely, and write down why — that paper trail is what stands between a missed ratio and a current liability nobody saw coming.

Source: https://beancount.io/blog/2026/10/22/callable-debt-covenant-violations-demand-provisions-waivers-sacs-asc-470-guide

Published: October 22, 2026