Imagine you are closing the books on a tough fiscal year. Cash runway is tight, a loan covenant just tripped, and your auditor schedules an extra meeting titled "Going concern discussion." That meeting is not a courtesy — it is the trigger for one of the most consequential disclosures in U.S. GAAP. Under ASC 205-40, management (not the auditor) is required to evaluate whether substantial doubt exists about the entity's ability to continue as a going concern within one year after the financial statements are issued. Get the evaluation and disclosure right, and you can still receive an unmodified audit opinion even when conditions look ugly. Get it wrong, and you risk an emphasis-of-matter paragraph that can ripple through covenants, customer contracts, and equity raises.
This guide walks through what ASC 205-40 actually requires, how management's two-step assessment works, what mitigating plans qualify, what the disclosures should look like in each scenario, and how the standard intersects with the auditor's responsibilities under AU-C 570 and PCAOB AS 2415.
Why ASC 205-40 Exists
Before the FASB issued ASU 2014-15 (codified as ASC 205-40, effective for annual periods ending after December 15, 2016), going concern was an auditor-driven concept. U.S. GAAP did not explicitly require management to perform or document its own evaluation. The standard was inconsistent across jurisdictions and time horizons. Some auditors looked out twelve months from the balance sheet date, others from the financial statement issuance date, and disclosures varied widely.
ASC 205-40 closed that gap. It put the responsibility squarely on management, anchored the assessment to a one-year look-forward window measured from the issuance date, and prescribed specific disclosures depending on whether the doubt is alleviated. Today, every reporting entity preparing financial statements under U.S. GAAP — public, private, nonprofit — must perform this evaluation each annual and interim period.
Step 1: Identify Conditions That Raise Substantial Doubt
The evaluation starts with management asking a deceptively simple question: in the next twelve months from the issuance date, is it probable that we will be unable to meet our obligations as they come due?
"Probable" is the same threshold used elsewhere in U.S. GAAP — meaning likely to occur, a higher bar than "reasonably possible" but lower than "virtually certain." The assessment must be based only on information that is known or reasonably knowable at the issuance date.
Conditions and events to evaluate
ASC 205-40 directs management to consider the entity's current financial condition, obligations due, funds needed to maintain operations, and broader risk factors. In practice, the checklist usually includes:
- Recurring operating losses or working capital deficits
- Negative cash flow from operations
- Debt obligations coming due within the assessment window with no committed source of refinancing
- Loan covenant violations — actual or projected — that could trigger acceleration
- Loss of a key customer, supplier, franchise, or license
- Pending litigation, regulatory action, or adverse judgments
- Labor disputes, strikes, or loss of essential personnel
- Catastrophic uninsured events (natural disasters, cyber attacks, product recalls)
- Inability to pay dividends or maintain compliance with stock exchange listing standards
Any single item is not necessarily fatal. It is the aggregate picture — combined with the cash flow forecast — that drives the conclusion.
The one-year look-forward window
The window is measured from the date the financial statements are issued or available to be issued, not from the balance sheet date. For a calendar-year company that issues March 31, 2026 financial statements, the assessment period runs through March 31, 2027. That extra quarter or two can be the difference between "no doubt" and "substantial doubt." It also means the window keeps moving as you prepare and reissue interim statements.
Step 2: Evaluate Management's Mitigating Plans
If the initial assessment surfaces substantial doubt, management does not stop there. The next step is to evaluate whether management's plans to address those conditions will alleviate the doubt.
ASC 205-40 only permits a plan to be counted in this evaluation if both of the following are probable:
- The plan will be effectively implemented within the assessment period.
- The plan, once implemented, will mitigate the conditions or events that raise substantial doubt.
Aspiration is not a plan. A board resolution to "explore strategic alternatives" is not a plan. To be credited under ASC 205-40, the plan must be specific, supported by evidence, and within management's authority — or with strong evidence of third-party commitment (a signed term sheet, an executed loan commitment, a board-approved budget already in motion).
Typical mitigating plans
- Debt refinancing or extension — usually evidenced by a signed commitment letter or completed transaction
- New equity issuance — backed by underwriter commitments, executed subscription agreements, or a controlling shareholder's binding guarantee
- Asset sales — supported by purchase agreements, broker letters of intent, or active market evidence
- Cost reduction programs — supported by board-approved plans, signed severance schedules, and historical execution track record
- Covenant waivers or amendments — evidenced by an executed waiver letter from the lender, ideally with a long enough term to cover the assessment window
- Parent company or related-party support — supported by a legally enforceable support letter (a "comfort letter" alone usually is not enough)
The phrase "probable of being effectively implemented" is the hinge. Auditors will push hard for written, executed evidence. A plan that depends on a transaction that has not yet closed — even one that "everyone expects to close" — is rarely sufficient on its own.
Disclosure Requirements: Two Distinct Outcomes
Once the two-step assessment is complete, you land in one of three places, each with different disclosure requirements.
Outcome A: No substantial doubt exists
If conditions and events do not raise substantial doubt, no specific ASC 205-40 disclosure is required. (You may still need to disclose risk factors elsewhere — for example, in SEC filings or in liquidity discussions.)
Outcome B: Substantial doubt is alleviated by management's plans
Here you must disclose, in the financial statement footnotes, information that lets a reader understand all three of the following:
- The principal conditions or events that raised substantial doubt (described as they existed before considering management's plans)
- Management's evaluation of the significance of those conditions in relation to the entity's ability to meet its obligations
- Management's plans that alleviated the substantial doubt
You do not include the magic phrase "substantial doubt about the entity's ability to continue as a going concern." That language is reserved for Outcome C.
Outcome C: Substantial doubt is not alleviated
This is the scenario every CFO wants to avoid. You disclose everything required under Outcome B, plus an explicit statement that "there is substantial doubt about the entity's ability to continue as a going concern within one year after the date that the financial statements are issued." You also disclose management's plans that are intended to mitigate the conditions — even though those plans have not alleviated the doubt.
The wording matters. ASC 205-40 specifies the language, and auditors will not accept softer or conditional substitutes such as "may have" or "could potentially have" substantial doubt.
Example Disclosures
Outcome B (substantial doubt alleviated) — abridged example:
During the year, the Company breached the fixed-charge coverage ratio under its senior credit facility as a result of a one-time inventory write-down. Absent remedial action, the breach would have permitted the lender to accelerate amounts due. On February 1, 2026, the Company executed a new $50 million term loan with Bank X, the proceeds of which were used to repay the prior facility in full. The new agreement contains revised covenants that the Company expects to comply with throughout the assessment period. Based on the executed refinancing, management has concluded that the substantial doubt that previously existed has been alleviated.
Outcome C (substantial doubt not alleviated) — abridged example:
The Company has incurred recurring operating losses, has a working capital deficit of Y million of debt maturing within twelve months for which no committed refinancing exists. These conditions raise substantial doubt about the Company's ability to continue as a going concern within one year after the date that these financial statements are issued. Management's plans include the pursuit of additional equity financing and asset divestitures. However, these plans are not within the Company's sole control and are not yet supported by definitive agreements. Accordingly, those plans have not alleviated the substantial doubt.
How This Coordinates With the Auditor
ASC 205-40 governs management. The auditor's responsibility is governed by AU-C 570 (for nonissuers, under AICPA Statements on Auditing Standards) and PCAOB AS 2415 (for issuers). The auditor performs an independent evaluation and tests management's conclusion.
The auditor's report outcomes line up like this:
- No substantial doubt, adequate disclosure — unmodified opinion, no going concern paragraph.
- Substantial doubt alleviated, adequate disclosure — unmodified opinion. The auditor may include an emphasis-of-matter paragraph drawing attention to the conditions and management's plans, but it is not required.
- Substantial doubt not alleviated, adequate disclosure — unmodified opinion with a required emphasis-of-matter paragraph that uses the phrase "substantial doubt about the entity's ability to continue as a going concern." The phrase must be unconditional — AU-C 570 explicitly prohibits softening language.
- Disclosure inadequate or omitted — qualified or adverse opinion, regardless of which outcome applies.
The often-overlooked nuance is that an unmodified opinion is achievable in Outcome C. Substantial doubt that the auditor agrees has been adequately disclosed does not automatically produce a qualified or adverse opinion — only inadequate disclosure does.
Practical Tips to Stay Out of Trouble
Start the evaluation early. ASC 205-40 requires assessment every annual and interim period. Build the evaluation into your close calendar. Do not let it become a last-week-before-issuance fire drill.
Document the assessment in writing. Auditors will ask for management's memo. A well-organized memo lists conditions considered, cites supporting forecasts and evidence, walks through the two-step analysis, and concludes clearly. Memos drafted after the auditor raises an issue are weaker than memos prepared as part of the original close.
Use a robust cash-flow forecast. Most going concern conclusions rise or fall on the forecast. A weekly or monthly cash flow projection that ties to the financial statements, includes sensitivity scenarios, and reflects all committed obligations gives the auditor something to test. A back-of-the-envelope schedule does not.
Treat lender communications as audit evidence. If a covenant breach is a possibility, get the waiver in writing and dated before issuance. A verbal "the bank is fine with it" will not survive audit review. The longer the waiver period, the better — twelve months ahead of issuance is the gold standard.
Avoid double-counting plans. A single source of capital cannot be used to support multiple mitigating plans. If the new term loan is what saves you from the maturity wall, it cannot also be what funds the expansion plan.
Watch for subsequent events. Conditions and events arising between the balance sheet date and the issuance date are part of the assessment. A line of credit drawn down after year-end, a customer loss in February, a covenant amendment signed in March — all need to be considered.
The Bookkeeping Connection
A going concern evaluation is only as credible as the underlying records. Auditors and lenders will trace your cash flow forecast back to the general ledger, the bank reconciliations, the debt schedules, and the obligations register. If those records are messy, inconsistent, or impossible to audit, even a defensible business outlook can land in Outcome C simply because the evidence is not there. Clean, version-controlled financial records make every step of the ASC 205-40 process — drafting the memo, supporting the forecast, evidencing mitigating plans — dramatically faster and more defensible.
Keep Your Books Audit-Ready Every Quarter
Going concern assessments are one of many places where clean, auditable financial records pay for themselves. Beancount.io provides plain-text, version-controlled accounting that gives auditors, lenders, and management complete transparency into every transaction — no black boxes, no vendor lock-in, and a full Git history of every change. Get started for free and see why developers, controllers, and finance professionals are choosing plain-text accounting to keep their books permanently audit-ready.