How management identifies substantial doubt, evaluates mitigating plans, and discloses going-concern uncertainty under ASC 205-40.
Going concern questions test whether management can evaluate financial distress and disclose uncertainty without changing the measurement basis prematurely. Under U.S. GAAP, the core issue is whether conditions and events raise substantial doubt about the entity’s ability to meet obligations as they become due within the required evaluation period.
For FAR, keep three questions separate:
ASC 205-40 makes going-concern evaluation a management responsibility, not merely an auditor concern. Management must evaluate known and reasonably knowable conditions and events for each annual and interim reporting period.
| Requirement | FAR meaning |
|---|---|
| Evaluation period | One year after the date the financial statements are issued or available to be issued. |
| Evaluation evidence | Financial results, liquidity, debt maturities, covenant compliance, market access, litigation, and operating conditions. |
| Management plans | Plans are considered only if probable of implementation and probable of alleviating substantial doubt. |
| Disclosure conclusion | Disclosure differs depending on whether substantial doubt is raised and whether it is alleviated. |
The look-forward period is a common exam trap. It is not simply one year from the balance sheet date. Under U.S. GAAP, the going-concern evaluation looks forward one year from issuance or availability for issuance.
Management repeats this evaluation for interim and annual financial statements. A prior-period conclusion does not control the current period because liquidity, covenant status, customer concentration, refinancing evidence, and operating forecasts can change quickly.
Substantial doubt exists when conditions and events, considered in the aggregate, raise significant uncertainty about the entity’s ability to meet obligations as they come due during the evaluation period.
| Indicator | Why it matters |
|---|---|
| Recurring operating losses | Losses can consume liquidity and reduce access to financing. |
| Negative operating cash flows | The entity may not generate enough cash to meet near-term obligations. |
| Maturing debt with no refinancing | Debt due within the evaluation period can create severe liquidity pressure. |
| Covenant violations | A default or acceleration clause can make debt immediately due. |
| Loss of major customers or suppliers | Operating viability may depend on concentrated relationships. |
| Adverse litigation or regulatory action | Potential payments, injunctions, or restrictions can threaten solvency. |
| Inability to access capital markets | Weak financing access limits management’s ability to bridge cash shortfalls. |
No single indicator automatically controls the conclusion. Management evaluates the full set of facts, including timing, magnitude, and whether obligations can be met as they come due.
flowchart TB
A["Evaluate known conditions and events"] --> B{"Do they raise substantial doubt?"}
B -->|No| C["No substantial-doubt disclosure required by ASC 205-40"]
B -->|Yes| D["Evaluate management plans"]
D --> E{"Plans probable of implementation and mitigation?"}
E -->|Yes| F["Disclose conditions and plans that alleviate doubt"]
E -->|No| G["Disclose substantial doubt not alleviated"]
F --> H["Update assessment each reporting period"]
G --> H
C --> H
The key logic is sequential. First identify whether substantial doubt is raised before considering management’s plans. Then evaluate whether those plans are strong enough to alleviate the doubt.
Management plans matter only when they are credible under the standard. A vague intention to “raise capital” or “cut costs” does not carry the same weight as signed financing agreements, executed cost reductions, committed asset sales, or approved restructuring actions.
| Plan type | Evidence that strengthens the plan | Common weakness |
|---|---|---|
| Debt refinancing | Executed agreement, lender commitment, or advanced negotiations with realistic terms | General expectation that lenders will cooperate |
| Equity raise | Filed offering, signed investment agreement, or credible investor commitment | Unsupported assumption that new investors will appear |
| Asset sale | Purchase agreement, active market, board approval, and realistic closing timeline | Asset is illiquid or sale price is speculative |
| Cost reduction | Approved plan, supplier renegotiations, workforce actions, or lease exits | Savings are vague or depend on future events outside management control |
| Operational turnaround | Signed customer contracts, production changes, or verified backlog | Optimistic sales forecast without evidence |
To alleviate substantial doubt, plans must be probable of being effectively implemented and probable of mitigating the adverse conditions during the evaluation period. Both parts matter.
The disclosure answer depends on whether substantial doubt exists after management evaluates its plans.
| Evaluation conclusion | Required disclosure focus |
|---|---|
| No substantial doubt is raised | ASC 205-40 substantial-doubt disclosure is generally not required, although other material uncertainties may still require disclosure elsewhere. |
| Substantial doubt is raised but alleviated by management’s plans | Disclose the principal conditions or events that raised doubt and management’s plans that alleviated it. |
| Substantial doubt is raised and not alleviated | State that substantial doubt exists, describe the conditions or events, and describe management’s plans even if they are not expected to fully mitigate the doubt. |
When substantial doubt is not alleviated, the disclosure must be direct. The note should not hide the conclusion behind vague liquidity language.
Substantial doubt does not automatically mean liquidation-basis accounting. Going-concern disclosure addresses uncertainty about the entity’s ability to continue operating. Liquidation-basis accounting is a different measurement basis and applies only when liquidation is imminent under the relevant guidance.
| Fact pattern | Reporting implication |
|---|---|
| Substantial doubt exists, but management is still pursuing operating plans | Continue using the going-concern basis and provide ASC 205-40 disclosures. |
| Substantial doubt is alleviated by probable mitigating plans | Continue using the going-concern basis and disclose the conditions and plans. |
| Substantial doubt is not alleviated | Continue using the going-concern basis unless liquidation is imminent; disclose that substantial doubt exists. |
| Liquidation is imminent | Consider liquidation-basis accounting rather than merely adding a going-concern note. |
The exam trap is jumping from severe financial distress directly to liquidation accounting. Unless the facts indicate liquidation is imminent, the FAR answer usually centers on substantial-doubt disclosure, not automatic remeasurement of all assets and liabilities.
Assume a company has recurring losses, negative operating cash flows, and a $15 million term loan due eight months after the financial statements will be issued. Existing cash and forecasted operations will not cover the maturity. These conditions raise substantial doubt.
Management then evaluates a refinancing plan:
In both cases, substantial doubt was raised before plans were considered. The disclosure outcome changes based on whether the plans are probable of implementation and mitigation.
Going-concern conclusions should be supported by evidence, not just narrative. A strong file connects the forecast, obligations, assumptions, plans, and disclosure conclusion.
| Documentation area | Evidence to retain |
|---|---|
| Cash-flow forecast | Monthly cash inflows, outflows, debt payments, covenant calculations, and sensitivity cases. |
| Debt and covenant analysis | Maturity schedules, waiver status, acceleration clauses, and refinancing evidence. |
| Management plans | Board approvals, signed agreements, term sheets, purchase agreements, or executed cost actions. |
| Stress testing | Downside cases showing whether obligations can still be met. |
| Disclosure conclusion | Written analysis explaining whether substantial doubt is raised, alleviated, or not alleviated. |
FAR may not ask for documentation mechanics directly, but simulations often include exhibits that function like documentation. Use them to decide whether management’s plans are concrete or speculative.
Going-concern analysis overlaps with subsequent events because management considers information through the issuance or available-for-issuance date. A refinancing agreement, covenant waiver, major customer loss, or litigation settlement after year-end can affect the going-concern conclusion if it is known before issuance.
Do not treat the balance sheet date as the cutoff for going-concern evidence. The required evaluation period and subsequent-event review both make dates central to the answer.
| Trap | Correct approach |
|---|---|
| Using one year from the balance sheet date | Use one year from the date financial statements are issued or available to be issued. |
| Considering management plans before identifying substantial doubt | First determine whether conditions and events raise substantial doubt, then evaluate plans. |
| Accepting vague plans as mitigating | Plans must be probable of implementation and probable of mitigating the conditions. |
| Omitting disclosure when doubt is alleviated | If substantial doubt was raised but alleviated, disclose the conditions and management’s plans. |
| Treating going concern as only an auditor issue | Management performs the ASC 205-40 evaluation and prepares the disclosures. |
| Ignoring post-year-end evidence before issuance | Subsequent information can change the going-concern conclusion. |