An audit doesn't end when fieldwork does. Between the last substantive test and the date the report goes out, two separate judgments still have to be made: whether the entity can keep operating as a going concern, and whether anything that happened after the balance sheet date needs to change the financial statements. Both carry their own standard, their own evidence requirements, and their own deadline, and both get confirmed in writing through the management representation letter before the file closes.
Most of the confusion around these three pieces comes from treating them as one topic instead of three related ones. Going concern asks a forward-looking question about the entity's future, and subsequent events asks a backward-looking question about what already happened.
The representation letter ties both answers to a signature, dated the same day as the report itself.
This guide covers what AS 2415 requires for the going concern evaluation, how AS 2801 splits subsequent events into two types with different consequences, what AS 2805 requires in the representation letter, and where nonissuer audits under AICPA standards diverge from the PCAOB rules.
Financial statements assume the entity will keep operating unless there's significant information to the contrary. AS 2415 doesn't ask the auditor to go looking for that information with procedures designed specifically for this purpose; it relies on what the audit already turns up. Analytical procedures, the subsequent events review, reading board minutes, confirming arrangements for financial support, and inquiries of legal counsel are the usual sources.
When those procedures surface conditions that, taken together, raise substantial doubt, AS 2415 lays out a specific sequence:
AS 2415 points to four categories of conditions when identifying what counts in step one:
This is where a lot of going concern analysis goes wrong: AS 2415 sets the auditor's look-forward period at a reasonable period of time, not to exceed one year beyond the date of the financial statements being audited. That clock starts at the balance sheet date.
FASB's ASC 205-40, the standard that governs management's own going concern assessment, uses a different anchor entirely: one year after the date the financial statements are issued, or are available to be issued. Since issuance typically happens weeks or months after the balance sheet date, management's look-forward period runs later, and often longer, than the auditor's own period under AS 2415.
For nonissuer audits conducted under AICPA standards, AU-C 570 closes that gap by aligning the auditor's period with management's: one year after the issuance date, matching ASC 205-40 directly. An issuer audit and a nonissuer audit of the same balance sheet date can legitimately be evaluating going concern over two different windows, which is worth knowing before comparing notes across engagement types. The same AU-C period also governs GAGAS financial audits, since the Yellow Book incorporates AICPA's GAAS by reference rather than setting its own going concern standard.
Under ASC 205-40, substantial doubt is only alleviated if both of two conditions hold:
A plan that's merely plausible doesn't clear the bar; both probability tests have to be met.
Even when doubt is alleviated, the entity still has to disclose the principal conditions that originally raised it, along with management's plans. The disclosure obligation doesn't disappear just because the auditor's ultimate conclusion did.
If substantial doubt remains after evaluating management's plans, AS 2415 requires an explanatory paragraph immediately following the opinion paragraph. The conclusion has to be expressed using the phrase "substantial doubt about its ability to continue as a going concern," or similar wording that includes both terms together. Conditional language is explicitly barred: phrasing like "if the Company continues to suffer losses, there may be substantial doubt" doesn't satisfy the standard.
AS 2801 governs events that happen between the balance sheet date and the issuance of the financial statements. The standard draws a sharp line between two categories, and getting the category wrong changes whether the financial statements get adjusted or just footnoted.
Type I events provide additional evidence about conditions that already existed at the balance sheet date. A customer whose finances were already deteriorating before year-end, who then files for bankruptcy a month later, is a Type I event: it confirms what was already true, and the financial statements get adjusted to reflect it.
Type II events arise from conditions that did not exist at the balance sheet date. A fire that destroys inventory the month after year-end is a Type II event: nothing about it was true as of the balance sheet date, so the financial statements aren't adjusted, though disclosure may still be required to keep them from being misleading.
| Type I | Type II | |
|---|---|---|
| Conditions existed at balance sheet date? | Yes | No |
| Financial statement treatment | Adjust | Disclose only, don't adjust |
| Example | Customer bankruptcy from a condition already present at year-end | Loss of inventory in a fire after year-end |
AS 2801 calls the stretch between the balance sheet date and the auditor's report the "subsequent period," and it runs through the date of the auditor's report, not through the last day of fieldwork. The standard requires the auditor to:
When a subsequent event surfaces after the auditor has already obtained sufficient evidence but before the financial statements are issued, AS 3110 gives two options:
AS 2801 covers events that happen before the auditor's report is issued. A related but distinct standard, AS 2905, covers facts that existed at the date of the report but weren't discovered until afterward, which is a different timeline with different procedures. The two remain separate standards governing separate windows of time.
AS 2805 requires the auditor to obtain written representations from management as part of every PCAOB audit. The letter isn't a substitute for audit procedures; it exists to confirm representations already given and to reduce the chance of a misunderstanding about what was actually communicated.
The standard lists specific representation topics the letter has to cover, organized around a few themes:
The letter is also tailored with additional representations specific to the entity's industry.
Because the auditor is concerned with everything through the report date, the representations have to be made as of that date, not the balance sheet date and not the date fieldwork wrapped up. If the auditor dual-dates the report, AS 2805 directs the auditor to consider whether an additional representation covering the dual-dated event is needed. The letter is signed by the members of management with overall responsibility for financial and operating matters, normally the chief executive officer and chief financial officer.
Management's refusal to provide the written representations is a scope limitation serious enough to preclude an unqualified opinion, and it's ordinarily sufficient grounds for the auditor to disclaim an opinion or withdraw entirely. The same is true if the auditor is blocked from performing a necessary procedure on a material matter, even if management has separately represented that the matter is fine. A representation is not a replacement for evidence the auditor couldn't otherwise obtain.
Each standard answers a different question, but they share evidence, timing, and the same closing signature.
| Standard | Question it answers | Key deadline |
|---|---|---|
| AS 2415 (going concern) | Can the entity keep operating? | Evaluated through the date of the auditor's report |
| AS 2801 (subsequent events) | Did anything happen since the balance sheet date that changes the statements? | Subsequent period runs through the report date |
| AS 2805 (representations) | Does management confirm what it told the auditor? | Letter dated as of the report date |
A going concern conclusion often rests partly on subsequent events evidence (a financing arrangement that closed after year-end, for instance), and the representation letter is where management puts both answers in writing. Getting any one of the three wrong tends to show up in the others.
Confirming which standard governs which question, and tracing the exact lookback period or required phrase back to the paragraph it comes from, is a research task more than a memory task, especially with two different one-year clocks running on the same engagement. Bizora's Audit Research traces answers back to the specific PCAOB or FASB paragraph behind them, with a View Steps reasoning path showing how the conclusion was reached.
Research your next going concern, subsequent events, or representation letter question in Bizora AI, with a 7-day free trial, no credit card required.
The sequence that closes a clean audit file runs in a specific order:
Each step depends on the one before it, which is why these three standards tend to get evaluated together in the final days of an engagement rather than as separate checklist items.
AS 2415 requires the auditor to evaluate whether there's substantial doubt about an entity's ability to continue as a going concern for a reasonable period, not to exceed one year beyond the date of the financial statements. If doubt remains after considering management's plans, the audit report must include an explanatory paragraph using the words "substantial doubt" and "going concern" together.
A Type I event provides additional evidence about conditions that already existed at the balance sheet date and requires adjusting the financial statements. A Type II event arises from conditions that didn't exist until after the balance sheet date and calls for disclosure only, without adjustment.
For issuer audits, AS 2415 sets it at one year beyond the date of the financial statements being audited. FASB's ASC 205-40 sets management's own period at one year after the issuance date instead, which AU-C 570 also uses for nonissuer audits, so the auditor and management aren't always looking at the same window.
AS 2805 requires representations on financial statement responsibility, completeness of records and minutes, absence of unrecorded transactions, uncorrected misstatements, fraud and related-party matters, litigation and contingencies, and subsequent events, dated as of the date of the auditor's report and signed by senior management.
It's a scope limitation serious enough to preclude an unqualified opinion. The auditor is ordinarily required to disclaim an opinion or withdraw from the engagement, and the refusal also raises questions about whether other management representations can still be relied on.
Dual dating is one of two options under AS 3110 for handling a subsequent event discovered after the auditor already has sufficient evidence but before the financial statements are issued. It limits the auditor's responsibility to the one disclosed event, as opposed to extending the report date, which extends responsibility, and the subsequent-events procedures, through the later date for everything.
No. Subsequent events under AS 2801 occur before the auditor's report is issued. Subsequently discovered facts under AS 2905 involve facts that existed at the date of the report but weren't discovered until after it was already issued, which triggers a different set of procedures entirely.
Bizora AI turns hours of manual research into seconds, with every answer backed by primary source citations. Start your 7-day free trial. No credit card required.
Start Free TrialRelated articles