After the audit report: trace late-discovered existing facts
A discovery after an audit report can concern facts that already existed when the report was dated. The later discovery date does not make the underlying fact new. The research task is to separate when the condition existed, when information reached the auditor, when reliability was established, and what actions became observable.
This guide concerns PCAOB issuer audits and AS 2905 as displayed on October 25, 2026. The fictional financial statements have already been issued before the discovery. It does not prescribe securities-filing forms or deadlines, and it does not replace analysis of separate registration-statement or other engagement responsibilities.
Identify the trigger without assuming a permanent reaudit
AS 2905 .01–.05 distinguishes the absence of a general continuing inquiry after the report date from the response when relevant new information comes to the auditor’s attention. Information of sufficient nature and source requires assessing its reliability and whether the facts existed at the report date.
That is not a promise that the auditor continually searches every subsequent business development. It is also not permission to disregard credible later information about the reported statements. The trigger depends on the actual information, its source and potential effect.
The standard’s discussion is about facts existing at the auditor’s report date, not merely at the financial year-end. Keep those dates separate. If the statements have not yet been issued, AS 2905’s footnote directs attention to subsequent-events guidance instead. The main example avoids that different procedural window.
Work a dated discovery case
Assume a fictional issuer’s financial year ends December 31, 2025. Its audit report is dated March 1, 2026, and the financial statements are issued March 5. On April 20, the auditor receives credible information suggesting that a December sale of 20 was fabricated. All monetary amounts are thousands.
At that moment, 20 is the amount of the suspected sale, not a publicly verified correction. Assume the issue would have warranted investigation during the audit. On April 25, the hypothetical investigation establishes reliability, confirms that no sale occurred and that the false record existed before March 1.
| Date | Event | Evidence state |
|---|---|---|
| December 2025 | Purported sale of 20 recorded | Underlying condition, later investigated |
| December 31 | Financial reporting date | Affected period identified |
| March 1 | Auditor’s report dated | Relevant report-date condition |
| March 5 | Statements issued | Already-issued case established |
| April 20 | Credible information received | Investigation trigger, not completed correction |
| April 25 | Facts substantiated | Reliability and existence supported |
| Later action date | Disclosure or revision | Separate status requiring evidence |
The investigation should distinguish nonexistent revenue from other possible issues, such as a valid sale with poor collection prospects. Those mechanisms have different financial effects. A customer dispute alone does not prove fabrication.
Even if revenue and receivables are overstated by 20 under the substantiated assumptions, profit is not necessarily overstated by 20. Associated costs, taxes and other entries need separate analysis. Do not turn the suspected sales amount into a complete earnings correction before the facts and accounting effects are determined.
Evaluate whether report-related action follows
Assume, for the teaching case, that the nature and effect are such that the report would have been affected if the information had been known and properly considered, and that people currently relying or likely to rely on the statements would attach importance to it. These are explicit assumptions, not consequences of the number 20 alone.
AS 2905 .05–.07 describes the relevant conditions, appropriate disclosure routes and the auditor’s need to satisfy itself that the client made the disclosures. The route depends on circumstances, including whether effects can be determined promptly and whether subsequent statements are imminent without delaying disclosure.
If the effects can be determined promptly, the standard discusses revised statements and report as soon as practicable. If a prolonged investigation is necessary and revision appears required, the discussion includes notification about reliance while revised information is being developed. Do not invent a fixed number of days from this general description.
For a hypothetical completed path, assume the issuer discloses the matter April 28 and issues revised statements and the related report May 10. Those dates are invented events, not regulatory deadlines. Record the actual wording and scope of each notice rather than treating the first announcement as the completed revision.
Keep actions and accounting status separate
A board decision to investigate is not a published correction. A public warning about reliance is not itself a revised balance sheet. A later amended filing is not proof that every originally suspected amount survived the investigation.
Use separate columns for suspected amount, substantiated finding, estimated statement effect, final correction and report status. Add dates and sources to each. If investigation reduces the identified sale problem from 20 to 12, the research record should preserve the original allegation and the final finding without presenting both as current errors.
Likewise, revised statements might affect several periods or several accounts. Match the revised figures and report to the specific statements covered. A headline saying “restatement” is insufficient to identify every changed period.
Do not infer that the auditor took no action simply because private discussions are absent from the public record. Board communications, investigative records and legal advice may remain confidential. A public analyst can track observable actions and identify gaps without asserting undisclosed inaction.
A new-event boundary
Now consider an unrelated factory fire occurring on April 20, after issuance. Assume it is entirely new and reveals no preexisting report-date condition. Its seriousness alone does not make it the existing-facts situation in the main case.
The fire may have financial-reporting or other disclosure consequences under applicable rules, but those require their own analysis. It is not evidence that the March 1 report was based on the same condition. The calendar sequence and causal facts matter more than the headline’s severity.
A rumor presents another boundary. An anonymous claim without substantiation does not make the alleged 20 a verified error. Evaluate what the source actually provides, whether corroboration is possible and whether the information meets the investigation trigger. Do not skip directly from receiving a rumor to announcing an auditor withdrawal.
What if cooperation or disclosure fails?
AS 2905 .08–.09 discusses refusal to make appropriate disclosure, communications and steps intended to prevent future reliance, with circumstances and legal considerations affecting the actions.
The source distinguishes a satisfactory investigation establishing reliable facts from circumstances in which lack of cooperation prevents such an investigation. A disclosure about unresolved information should not be rewritten as proof of the specific alleged amount or someone’s motive.
For research, retain the exact attributed statement: what the auditor said, what management said, what was investigated and what remains unresolved. Do not average conflicting accounts into a fictional compromise figure. Nor should an analyst present the standard’s general steps as evidence that a particular auditor completed them privately.
Execute the public timeline
| Question | Evidence object | Research conclusion |
|---|---|---|
| What statements are involved? | Period, original report and issuance record | Relevant reporting population |
| When did the condition exist? | Transaction or investigative finding | Existing versus genuinely new fact |
| When was information received? | Dated attributed disclosure | Trigger timing if publicly established |
| Is it reliable? | Corroborated finding versus allegation | Evidence state, not guessed certainty |
| What effects were determined? | Revised notes and reconciliation | Revenue, assets, profit and tax separated |
| What action occurred? | Notice, revised statements and report | Each action’s actual date and scope |
| What is unavailable? | Missing private records | No claim to know undisclosed procedures |
When dates conflict, distinguish document signing, public filing, dissemination and effective report dates. They may all be real while referring to different events. Preserve both dates until their meanings are resolved.
Update the matrix as findings are substantiated, estimated effects change, revised statements appear or a prior notice is corrected. The final memo should explain the underlying fact, discovery and disposition without turning a later discovery into a new event or an allegation into an established correction.
Distinguish the report date from the balance-sheet date
Suppose a separate guarantee arises February 15, after December year-end but before the March 1 report, and is discovered in April. It can be an existing fact at the report date without being a December transaction. The relevant accounting could concern subsequent-event disclosure rather than inserting a December payable.
The example illustrates why the matrix needs both dates. Determine the applicable reporting treatment and whether the report would have been affected; do not assume every report-date fact requires the same prior-period journal entry.
FAQ
Does discovering a fact in April mean it arose in April?
No. Its underlying existence date must be established separately.
Is a suspected sale of 20 automatically a profit correction of 20?
No. Reliability and the full accounting effects require investigation.