Subsequent Events in Auditing: AU-C 560 Documentation Guide

Subsequent events in auditing under AU-C 560 carry documentation requirements that change depending on exactly when an event or fact comes to the auditor's attention. At BusAcTa Advisors, we support CPA firms with the bookkeeping and file preparation work behind audit engagements, and subsequent events documentation is one of the areas where a thin file most often surfaces in peer review, usually because the timeline of discovery never made it into the workpapers clearly.

This is general information, not a substitute for the full text of AU-C 560 or professional judgment applied to your specific engagement. Always consult the current AICPA auditing standards and your firm's quality control policies before finalizing an engagement file.

The Three Time Periods That Drive Everything Under AU-C 560

Answer first: an auditor's responsibility under AU-C 560 changes across three distinct periods, and almost every documentation requirement in the standard ties back to which period an event or fact falls into.

• Balance sheet date to report date. The auditor has an active responsibility to perform procedures specifically designed to identify subsequent events during this period. This is the period the standard refers to as "subsequent events."

• Report date to financial statement issuance. The auditor has no obligation to actively search for new information, but must respond appropriately to any fact that comes to their attention. The standard refers to facts discovered in this window, and after issuance, as "subsequently discovered facts."

• After financial statements are issued. The auditor generally has no responsibility to apply procedures to search for events occurring after issuance, but must still respond if a relevant fact becomes known.

Getting the timeline of discovery documented clearly in the file is not a formality. It is the single fact that determines which set of procedures and which documentation requirements actually apply.

Type I and Type II Events, and Why the Distinction Matters for Documentation

Subsequent events fall into two categories, and the file needs to show which one applies and why.

A customer bankruptcy driven by financial distress that existed before year-end is a Type I event requiring adjustment of the related receivable. A warehouse destroyed by a fire or tornado after year-end is a Type II event, since the loss reflects a condition that did not exist at the balance sheet date, requiring disclosure but not adjustment. The file should document the specific facts that support classifying an event as one or the other, not just the conclusion.

The classification itself is the judgment call worth documenting. A correct conclusion with no record of the reasoning behind it is still a thin file.

Documentation Required for the Active Search Period

During the period from the balance sheet date to the report date, the auditor performs specific procedures aimed at identifying subsequent events, and the file should document each one along with its results. These procedures are typically grouped into three categories: inquiring, reviewing, and reading.

• Inquiring of management and those charged with governance. About the current status of items that were accounted for using preliminary or inconclusive information, new commitments or contingencies, significant changes in capital structure, and any unusual accounting adjustments.

• Inquiring of legal counsel. Regarding litigation, claims, and assessments. Legal counsel's response is generally considered the most direct and corroborative source of evidence about the status and likely outcome of legal matters, more reliable for this purpose than management representations or board minutes alone.

• Reading minutes of meetings. Of stockholders, the board of directors, and relevant board committees held after the date of the financial statements.

• Reading the entity's latest available interim financial statements. Comparing them to the financial statements being audited.

The management representation letter is a key piece of evidence for this period and must be dated as of the date of the auditor's report, not the balance sheet date and not the date fieldwork was substantially completed. That date confirms management has informed the auditor of relevant events through the entire period of the auditor's active responsibility.

Documentation When Facts Surface After the Report Date

Why does the documentation requirement shift so sharply once the report date passes? Because the auditor's obligation shifts from actively searching to responding, and the file needs to show that shift clearly, including exactly when the fact came to the auditor's attention and what the auditor did about it.

If a fact is discovered before the financial statements are issued and would have caused the auditor to revise the report had it been known earlier, the file should document the discussion with management, the procedures performed to evaluate the new information, and the resolution. If management agrees to revise the statements, the file should show that audit procedures were performed on the revision and that the report date was updated, either by changing the report date entirely or by dual-dating the report to extend responsibility only for the specific matter that prompted the revision.

If management refuses to make a necessary revision, the file needs to document the auditor's communication with management and those charged with governance, and the steps taken if appropriate action is not forthcoming, which can include taking steps to prevent continued reliance on the original report.

Dual-Dating and What It Actually Documents

Dual-dating is a specific documentation technique worth understanding precisely, since it is easy to apply incorrectly. When an auditor's report carries two dates, the later date applies only to the specific matter referenced by that date. For every other matter in the financial statements, the auditor's responsibility ends on the earlier, primary report date.

The alternative to dual-dating is simply updating the report date entirely, which extends the auditor's responsibility for subsequent events to the new date across the board. The file should make clear which approach was used and why, since the two carry meaningfully different scopes of ongoing responsibility.

Documentation for Predecessor Auditors and Reissued Reports

AU-C 560 also covers situations where a predecessor auditor is asked to reissue a previously issued report on financial statements presented on a comparative basis. The predecessor auditor should perform specific procedures to determine whether the original report is still appropriate before reissuing it, and document that evaluation. This scenario comes up more often than firms expect, particularly when a client changes auditors and the new auditor needs the prior year's report reissued alongside the current year's.

Building Subsequent Events Documentation Into the Workflow

1. Document the date each subsequent events procedure was actually performed. Not just that inquiries were made, but when, since the timeline determines which responsibility period applies.

2. Record legal counsel responses as a distinct piece of evidence. Don't let this get absorbed into general correspondence notes where it is hard to locate later.

3. Write out the reasoning for Type I versus Type II classification. A one-line conclusion without the supporting facts is the most common gap reviewers find.

4. Confirm the representation letter date matches the report date exactly. A mismatch here is an easy, avoidable documentation deficiency.

Conclusion and Next Steps

Subsequent events documentation under AU-C 560 is built around timing. The file needs to clearly establish when an event or fact was discovered relative to the balance sheet date, the report date, and the issuance date, because that timing determines which procedures apply and which obligations follow. The classification of an event as Type I or Type II should be documented with the reasoning behind it, not just the conclusion, and any dual-dating or report-date change should clearly show the scope of extended responsibility. Firms that build these habits into the engagement itself avoid the thin-file gaps that surface most often in peer review.

If your firm needs support with the bookkeeping and file preparation work behind audit engagements, talk to BusAcTa Advisors about how a dedicated team can support your engagement workflow, we can show you how this fits alongside your firm's existing quality control process. You can also see our related guide on SSARS 21 review and compilation documentation, or learn more on our audit support services page.