ASC 205-40: When You Have to Disclose Going Concern Doubt

Management evaluates whether conditions and events, considered together, raise substantial doubt about the company's ability to meet its obligations as they come due within the look-forward period the standard defines, based on information available at the time the financials are issued or available to be issued. This isn't a one-time assessment made only when a crisis is obvious; it's a required evaluation every single reporting period, even in a period where the company feels perfectly healthy, because the standard requires the analysis to happen regardless of the expected conclusion.

If the initial evaluation raises substantial doubt, management then considers whether its plans to address the conditions will actually mitigate that doubt, but only plans that have been approved and are probable of being effectively implemented count, not aspirational ones. A verbal intention to raise a funding round doesn't count as mitigation; a signed term sheet with committed capital, or an executed cost reduction plan already underway, is the kind of specific, probable action the standard is actually asking about.

Consider a company whose cash runs out inside the look-forward window and whose lead investor has said only that they're interested in a new round. That conversation is encouraging, but it isn't an approved plan that is probable of being implemented, so it can't be counted as mitigation. Now suppose the same company has signed a term sheet with committed capital and a board-approved schedule for drawing it. That is the kind of specific, documented action the standard looks for. When you assess a plan, ask whether it is approved, whether it is within management's control, and whether you could show the evidence to an auditor today.

If you're already tracking your burn multiple as part of routine reporting¹, a going concern evaluation is really just an extension of that same discipline applied formally, over the standard's specific look-forward window, with the analysis documented rather than kept as an internal read on runway. Companies that already run disciplined cash forecasting tend to find the going concern test far less stressful than companies encountering the formal analysis for the first time under audit pressure.

There's an important distinction the standard draws between doubt that exists but is alleviated by probable, effective mitigating plans, which still requires disclosure of the conditions and the plans that alleviate them, and doubt that remains even after considering those plans, which requires a stronger disclosure indicating the doubt isn't fully resolved. Getting this distinction right matters a great deal to a reader, a lender, or an investor, since the two disclosures signal very different levels of risk even though both start from the same underlying doubt.

Build a written memo each period showing the specific conditions considered, the cash flow projections and assumptions behind the look-forward analysis, and the specific mitigating plans evaluated along with why they were or weren't considered probable. An auditor testing this area will want to see the reasoning, not just management's bottom-line conclusion that doubt does or doesn't exist, and a documented analysis from a period when things looked fine is exactly what makes a harder period's analysis credible later, since it shows a consistent, applied methodology rather than a one-off exercise.

A useful memo each period includes these elements:

• The specific conditions and events considered together, including any that raised doubt about the company's ability to meet its obligations.
• The cash flow projections and assumptions behind the look-forward analysis, so a reviewer can follow how you reached your numbers.
• Each mitigating plan you evaluated, with your reasoning for why it was or wasn't probable of being effectively implemented.
• Evidence that the plans were approved, such as a signed term sheet with committed capital or an executed cost reduction already underway.
• Your conclusion, written up every period, including periods when the company looks perfectly healthy.

If your own cash flow analysis is trending toward a substantial doubt conclusion, tell your board proactively rather than letting them learn about it for the first time when the auditor raises it during fieldwork. A board that's already aware of the trend and has weighed in on the mitigating plan is in a much stronger position than one blindsided by a disclosure they never saw coming, and that early conversation is often exactly what turns an aspirational plan into the kind of approved, probable plan the standard actually requires. Waiting for the auditor to force the conversation almost always produces a worse outcome for everyone involved.