ASC 205-40 requires management — not the auditor — to evaluate every annual and interim period whether there is substantial doubt about the company's ability to continue as a going concern for one year after the financial statements are issued, not one year from the balance sheet date. The evaluation is a two-step test: identify the conditions first, then consider only those management plans that are both probable of being implemented and probable of working. Uncommitted financing almost never clears that bar; approved cost reductions and closed capital usually do. The outcome drives one of three disclosure patterns, and a going concern paragraph in the audit report is survivable — the real damage comes from debt agreements that treat it as a default, and from discovering the issue in March instead of November.
Every pre-revenue biotech, most Series B software companies, and a meaningful share of hardware and climate businesses run with less than two years of cash. That is the business model, not a defect. But it collides with an accounting standard that asks a narrow, binary question once a quarter: is it probable that the company can meet its obligations as they come due for the next twelve months?
Finance teams tend to treat the going concern evaluation either as a formality the auditor handles or as an existential threat to be avoided at any cost. Both are wrong. Below is how the standard actually operates, where companies get tripped up, and how to make the assessment a routine close deliverable rather than an annual crisis.
The standard: whose job, what period, what threshold
ASU 2014-15 moved the going concern evaluation into U.S. GAAP as ASC 205-40. Before that, going concern lived only in auditing standards; management had no explicit obligation under GAAP. Now it does, and three parameters define it.
Whose job. Management performs the evaluation and owns the conclusion. The auditor performs a separate evaluation under its own standard — AS 2415 for PCAOB audits, AU-C 570 for private company audits — and reaches an independent view. The two generally land in the same place, but not always, and the auditor's look-forward period is not identical to GAAP's. Plan for both.
What period. One year from the date the financial statements are issued (for SEC filers) or available to be issued (for everyone else). For a December year-end company filing its 10-K in mid-March, the window runs to mid-March of the following year — roughly fourteen and a half months of runway measured from the balance sheet date. Teams that model "twelve months from year-end" are consistently two to three months short.
What threshold. Substantial doubt exists when it is probable that the company will be unable to meet its obligations as they come due within that window. "Probable" carries the same meaning it does in ASC 450 — likely to occur — which is a higher bar than "possible" and lower than "virtually certain." A company with nine months of cash at the issuance date, no committed financing, and no approved plan to extend runway almost always meets it.
Step one: identify the conditions before you consider the fixes
The standard is deliberately sequenced. Management first evaluates whether conditions and events, considered in the aggregate, raise substantial doubt — without regard to management's plans. Only if the answer is yes does the analysis move to whether those plans alleviate the doubt.
This ordering matters because it determines what gets disclosed. A company that skips to "we'll raise a round" and concludes there is no issue has misapplied the standard even if the round closes. If conditions raise substantial doubt and plans alleviate it, the standard still requires disclosure of the conditions and the plans. Collapsing the two steps erases a required disclosure.
What conditions look like. Recurring operating losses and negative operating cash flow are the obvious ones, but the list is longer: debt maturities or balloon payments inside the window, covenant breaches or near-breaches, a milestone-dependent tranche that may not fund, concentration in a single customer whose renewal is uncertain, a clinical readout that would end a program, loss of a key license, or pending litigation with a plausible cash outcome. The evaluation is cumulative. Nine months of cash alone may not raise doubt if a signed term loan funds next month; nine months of cash plus a covenant that trips in Q2 plus a note due in Q3 almost certainly does.
The forecast behind the conclusion. The condition analysis rests on a cash forecast through the end of the window, and auditors test that forecast rigorously. It should start from the board-approved operating plan, reconcile to actual burn for the trailing two quarters, and include a downside scenario — delayed collections, slipped revenue, trial cost overruns — with sensitivities on the two or three drivers that matter most. A forecast that assumes burn improves materially without a specific, already-executed action behind each improvement will not hold up.
Step two: which management plans actually count
Here is where most of the judgment and most of the disagreement with auditors lives. A plan can alleviate substantial doubt only if it is probable that the plan will be effectively implemented and probable that, once implemented, it will mitigate the conditions within the window. Both legs must be satisfied, and the plan generally must be approved by the appropriate level of authority before the issuance date.
Equity financing. The hardest category. An intention to raise, a banker engagement letter, or a non-binding term sheet is not probable of implementation — the counterparty controls the outcome. A signed, fully executed purchase agreement with closing conditions that are within the company's control usually is. For public companies, an at-the-market program is a judgment call: the facility exists, but whether the shares can be sold at a price and volume that solves the problem depends on market conditions outside management's control. Most auditors give partial or no credit absent demonstrated recent usage and ample float.
Debt financing. An undrawn, committed facility with no unmet conditions counts. A facility whose draw is contingent on a milestone, a minimum cash covenant, or lender discretion counts only to the extent those contingencies are themselves probable. Waivers and amendments must be obtained — not merely requested — before issuance to be considered.
Cost reductions. The most reliable lever, because it is within management's control. A reduction in force approved by the board with a defined headcount and date, a deferral of a specific program or trial, or a renegotiated vendor commitment all qualify. "We would cut costs if we needed to" does not. The plan must be specific, approved, and modeled into the forecast with realistic timing — severance and wind-down costs typically mean a RIF produces net savings only after sixty to ninety days.
Asset sales and licensing. Probable when there is a signed agreement or an active, documented process for a marketable asset. A hope to out-license a non-core program with no counterparty engaged is not.
IPO proceeds. For companies in registration, this is the recurring question. Until the offering prices and closes, the proceeds are not within management's control and are not probable. The audited financials in an initial S-1 are therefore frequently accompanied by a going concern paragraph that is resolved by the offering itself — which is why the first 10-Q after the IPO typically reports the doubt alleviated by closing proceeds.
Three outcomes, three disclosures
The evaluation lands in one of three places, each with a prescribed disclosure response.
No substantial doubt raised. No specific going concern disclosure is required, though liquidity discussion in MD&A under Item 303 continues to apply, and a company with eighteen months of cash should still be describing its runway and capital needs there.
Substantial doubt raised, alleviated by management's plans. The footnotes must disclose the principal conditions that raised the doubt, management's evaluation of their significance, and the plans that alleviated it. The phrase "substantial doubt" is not required in this case, but the conditions and plans must be described specifically enough that a reader understands what happened. Vague references to "management believes current resources are sufficient" without describing what changed will draw a comment.
Substantial doubt raised, not alleviated. The footnotes must state explicitly that there is substantial doubt about the company's ability to continue as a going concern within one year of issuance, describe the conditions, and describe management's plans even though they do not alleviate the doubt. The financial statements remain on a going concern basis — liquidation-basis accounting is a separate and much rarer determination under ASC 205-30 that applies only when liquidation is imminent.
In the third case, expect a going concern paragraph in the auditor's report, and expect SEC staff to check consistency across the footnote, risk factors, and MD&A liquidity section. A footnote that says substantial doubt exists next to an MD&A that says resources are sufficient for twelve months is an immediate comment.
The covenant problem nobody models
A going concern paragraph does not, by itself, change the company's cash position. What changes it is the loan agreement. Most venture debt and many bank facilities include an event of default triggered by a "going concern" qualification or explanatory paragraph in the audit report. Some are drafted to exclude paragraphs that arise solely from an upcoming debt maturity; many are not.
The consequence is circular: the going concern paragraph triggers a default, the default accelerates the debt, the accelerated debt now falls inside the one-year window, and the going concern conclusion that was marginal becomes certain. We have seen this sequence turn a manageable disclosure into a reclassification of the entire term loan to current and a scramble for a waiver in the week before filing.
What to do about it. Read the default provisions of every credit agreement now, before the evaluation is live. Where the trigger exists, negotiate a carve-out at the next amendment — lenders to pre-revenue companies generally understand that a going concern paragraph is a function of the business model, and most will agree to language that excludes paragraphs resulting from a scheduled maturity or from the company's stage. If a waiver will be needed, start the conversation in the quarter before the filing, not the week of. A waiver obtained after the issuance date does not help the current-period conclusion.
Running the evaluation as a quarterly control
The companies that handle going concern well treat it as a close deliverable with an owner, a template, and a calendar, not as an annual negotiation with the auditors in February.
Quarterly memo. Each interim and annual period, the controller or FP&A lead prepares a short memo: the window dates, the cash forecast through the window with sources and assumptions, the conditions identified in step one, the plans evaluated in step two with the evidence that each is probable, and the conclusion. The CFO signs it. The audit committee sees it — ideally before the auditor does, so the committee is not learning the conclusion from the engagement partner.
Evidence file. Board minutes approving cost actions, executed financing documents, lender waivers, and the forecast reconciliation. The standard looks to the state of facts at the issuance date, so the file should be refreshed in the days before filing, not frozen at quarter-end.
Early warning. Set an internal threshold — say, fifteen months of forecast cash at the next expected issuance date — below which the going concern evaluation becomes a standing agenda item and plan development begins. The single most common failure is not a wrong conclusion but a late one: management reaches the right answer with too little time left to execute a plan that would have changed it.
Disclosure controls. For SEC filers, the going concern conclusion flows into the footnote, the risk factors, the MD&A liquidity section, and potentially the auditor's critical audit matters. Someone should own the consistency check across all four.
A going concern paragraph is a disclosure about runway, not a verdict on the business. The companies that get hurt by it are the ones that treated it as unthinkable until it was unavoidable.
Questions worth asking this quarter
How many months of cash does the forecast show at the date the next set of financial statements will actually be issued — not at the balance sheet date? Which of the financing or cost actions in the plan have been approved and executed, and which are still intentions? Does any credit agreement treat a going concern paragraph as an event of default, and if so, has the carve-out conversation started? And does the liquidity narrative in the MD&A draft say the same thing the footnote says?
Most growth-stage companies will face a substantial doubt evaluation at some point, and most will come through it with a disclosure and a plan rather than a crisis. The difference is almost always preparation. If you're working through a going concern assessment, a cash forecast your auditors will accept, or a credit agreement that needs a carve-out before the next filing, we'd be glad to help.
This article is for general informational purposes and should not be relied on as accounting, tax, or legal advice for any specific transaction. Please consult with your advisors.