Subsequently Discovered Facts: Dual Dating, Reissued Reports and What to Do After Release

The auditor has no duty to keep searching after the report is dated. But facts do surface: a lender mentions a default, a customer discloses a dispute, an employee reports a misstatement. If the fact existed at the report date and might have changed the report, the auditor has to respond. This post is a decision path.

Define the terms first

• Date of the auditor's report: the date on which the auditor has obtained sufficient appropriate evidence to support the opinion.
• Report release date: the date the auditor gives the entity permission to use the report.
• Subsequently discovered fact: a fact that becomes known to the auditor after the report date and that, had it been known then, may have caused the auditor to amend the report.

Everything depends on which period the discovery falls in. The AU-C 560 standards page sets out the three periods. Here we apply them.

Path A: discovered after the report date and before release

1. Confirm the fact. Obtain enough information to know whether it is real and whether it existed at the report date.
2. Discuss with management and, where appropriate, governance. Ask how management intends to deal with it in the financial statements.
3. Decide whether the financial statements need revision.
4. If management revises the statements, perform the procedures needed on the revision, extend the subsequent events procedures to the date of the new report, and issue a new or amended report.
5. If management will not revise when the auditor believes it must, modify the opinion (qualified or adverse) and explain why.

The GAO Financial Audit Manual reaches the same sequence and notes the auditor may inquire of management whether it knows of subsequently discovered facts.

Path B: discovered after release

The steps are the same at the start: confirm, discuss, decide on revision. After that the issues are practical.

• If management revises and reissues, the auditor performs the necessary procedures, and the new report is dated or dual-dated as appropriate.
• If management does not take steps to notify people who received the statements, and the auditor believes the statements need revision, the auditor tells management and governance that the report must not be relied on, and takes action to prevent reliance. The auditor may consult its own legal counsel on this step.

Redate or dual-date

When financial statements are revised for a specific matter after the report date, the auditor picks one of two forms.

Example of dual-dating wording: "March 12, 20X2, except for Note 9, as to which the date is March 22, 20X2." The work after March 12 is limited to Note 9 and its supporting events. A redated report to March 22 forces the auditor to repeat subsequent events inquiries across the whole period through March 22.

Pick dual dating when the matter is isolated and you can show it is. Pick redating when the revisions touch several areas, or when the gap between dates is long. The choice also affects the representation letter. The GAO Financial Audit Manual says to obtain updated or additional representations as appropriate. For a dual date, cover the revised matter and the events to the later date. For a redate, update the letter to the new date for everything.

Worked example

A client's report is dated April 4. Release is planned for April 15. On April 9, the client's bank tells the CFO that the covenant waiver relied on in the debt note had a condition that was not met at year end. The facts existed at December 31.

1. The manager confirms by reading the waiver letter and the bank's email.
2. The partner meets management and the audit committee chair on April 10.
3. Management concludes the debt must be classified as current, which makes a going concern evaluation necessary.
4. The firm re-performs the going concern evaluation, reviews management's updated cash flow forecast and updates the legal letter.
5. Management revises the debt classification and the going concern note. Because the revision affects the balance sheet, the current ratio and the going concern paragraph, the firm redates the report to April 12, repeats subsequent events inquiries through April 12 and obtains a new representation letter dated April 12.
6. The file contains a memo of the whole sequence and the partner's sign-off.

If instead the revision had been one note (the covenant description) with no balance sheet change, a dual-dated report ("April 4, except for Note 7, as to which the date is April 12") would have limited the extended work to that note.

Do not release the report early

The cleanest control against these problems is not releasing the report until the representation letter is signed and the last inquiry update is done. A report released with the file incomplete invites problems that dual dating cannot fix. See the engagement completion checklist.

Documentation

For any subsequently discovered fact, the file records:

• How the fact came to the auditor's attention, with date.
• Procedures performed to confirm it.
• Discussions with management and governance, with dates.
• Legal advice sought.
• The decision to redate, dual date or modify, with reasoning.
• The revised report, the new letter and the extended subsequent events work.

See AU-C 230 audit documentation. Changes to the file after the documentation completion date have their own rules; see documentation completion date and post-release changes.

CORAA prepares ready-to-review audit files for US CPA firms; the firm keeps the client, the review and the signature. See /us.

Sources

• AICPA, AU-C Section 560, Subsequent Events and Subsequently Discovered Facts
• AICPA, AU-C Section 700, Forming an Opinion and Reporting on Financial Statements; AU-C Section 570, The Auditor's Consideration of an Entity's Ability to Continue as a Going Concern
• U.S. Government Accountability Office, Financial Audit Manual, Volume 1 (GAO-26-108577), June 2026, section 550: gao.gov

AU-C references are to AICPA Professional Standards, paraphrased here; read the standard itself before relying on a requirement. This page is guidance, not professional advice. Report an error