12.5 Subsequent Events & Subsequently Discovered Facts (AU-C 560)

12.5 Subsequent Events & Subsequently Discovered Facts (AU-C 560)

Core Principle: An audit does not end on the final day of the client's fiscal year. Under AU-C 560 (Subsequent Events and Subsequently Discovered Facts), the auditor must evaluate events and transactions occurring between the balance sheet date and the date of the auditor's report, and respond appropriately to facts discovered after the financial statements have been released to the public.

---

1. The Audit Timeline & Chronological Spheres of Responsibility

The auditor's responsibilities are divided into three distinct chronological phases:

                                    THE SUBSEQUENT AUDIT TIMELINE

  Balance Sheet Date           Auditor's Report Date         Financial Statement Issuance Date
    (e.g., Dec 31)                (e.g., Feb 15)                      (e.g., Mar 2)
          |                             |                                   |
          +=============================+===================================+------------------------>
          | <--- ACTIVE REVIEW PERIOD -> | <-- PASSIVE SUBSEQUENT PERIOD --> | <-- POST-ISSUANCE ---->
          | - Active responsibility to  | - No active inquiries required.   | - Subsequently        |
          |   perform subsequent        | - If an event becomes known,      |   discovered facts    |
          |   event procedures.         |   audit team must take action.    |   existing at report  |
          | - Type I & Type II events.  | - Dual dating vs. extending date. |   date require action |

The Three Spheres of Responsibility

1. Active Review Period (Balance Sheet Date to Auditor's Report Date): The auditor has an affirmative responsibility to design and execute specific procedures to identify subsequent events that require adjustment or disclosure.
2. Passive Post-Report Period (Auditor's Report Date to Financial Statement Issuance Date): The auditor has no obligation to perform ongoing inquiries or review procedures. However, if a subsequent event comes to the auditor's attention before the financial statements are issued, the auditor must investigate and determine whether adjustments or disclosures are required.
3. Post-Issuance Period (After Financial Statement Issuance Date): The auditor has released the report. If the auditor becomes aware of facts that existed at the date of the auditor's report that would have affected the report had they been known, the auditor must initiate formal remediation procedures.

---

2. Type I Subsequent Events: Recognized Events (Adjustment Required)

Type I subsequent events represent events or transactions that provide additional evidence with respect to conditions that existed on or before the balance sheet date.

+-------------------------------------------------------------------------------------------------------+
|                               TYPE I RECOGNIZED SUBSEQUENT EVENTS                                     |
|                                                                                                       |
|   CRITERION: Condition existed on or before the balance sheet date.                                   |
|   ACCOUNTING TREATMENT: ADJUSTMENT to the financial statements (Balance Sheet & Income Statement)    |
|                         plus footnote disclosure where necessary.                                     |
+-------------------------------------------------------------------------------------------------------+

Classic Type I Scenarios

• Customer Bankruptcy: A major customer files for Chapter 7 bankruptcy in January. The bankruptcy resulted from a gradual deterioration in financial condition that began prior to December 31. This provides definitive evidence that the customer's receivable balance was uncollectible at year-end, requiring an adjustment to increase the Allowance for Credit Losses (bad debt expense) at December 31.
• Settlement of Pre-Existing Litigation: In February, the client settles a patent infringement lawsuit for $3,500,000. At December 31, the company had accrued an estimated loss of $1,500,000. Because the litigation existed at year-end, the settlement confirms the true liability, requiring an adjustment to increase accrued litigation liabilities by $2,000,000 at December 31.
• Disposal of Obsolete Inventory Below Cost: In January, finished goods inventory held at December 31 is sold at a massive discount below its recorded book value. This confirms that the net realizable value (NRV) impairment existed at year-end, requiring an adjustment to write down inventory at December 31.
• Renegotiation of Long-Term Purchase Price: Resolution of purchase price contingencies for an acquisition completed prior to year-end.

---

3. Type II Subsequent Events: Unrecognized Events (Disclosure Only)

Type II subsequent events represent events or transactions that provide evidence with respect to conditions that did not exist at the balance sheet date, but arose subsequent to that date.

+-------------------------------------------------------------------------------------------------------+
|                              TYPE II UNRECOGNIZED SUBSEQUENT EVENTS                                   |
|                                                                                                       |
|   CRITERION: Condition arose AFTER the balance sheet date.                                            |
|   ACCOUNTING TREATMENT: DISCLOSURE ONLY in financial statement notes.                                  |
|                         NO adjustment to balance sheet or income statement accounts!                  |
+-------------------------------------------------------------------------------------------------------+

Classic Type II Scenarios

• Natural Disaster / Casualty Loss: On January 18, a client's main distribution center and inventory are destroyed by a fire or hurricane. Because the fire occurred after December 31, the condition did not exist at year-end. No balance sheet adjustment is permitted. The event must be disclosed in the footnotes, detailing the estimated uninsured loss.
• Issuance of Capital Stock or Bonds: The client issues $100,000,000 in debentures or preferred stock in January. Requires footnote disclosure only.
• Significant Business Acquisition or Combination: The company executes a definitive merger agreement to acquire a competitor in February. Requires footnote disclosure and possibly pro forma financial information.
• Sudden Decline in Asset Value: A severe market crash or geopolitical embargo occurs in January, causing a dramatic collapse in marketable securities or foreign exchange values. Disclosure only.
• Loss of Major Facility or Customer from Subsequent Event: An uninsured fire at a key customer's factory in January leads to contract cancellation. Disclosure only.

Summary Comparison Matrix

---

4. Auditor's Active Review Procedures During the Subsequent Period

Through the date of the auditor's report, the auditor must perform active audit procedures specifically designed to uncover subsequent events:

1. Read Interim Financial Statements: Inspect the client's latest available monthly or quarterly interim financial statements (e.g., January financial statements) and compare them with the year-end balances.
2. Inquire of Management & Those Charged with Governance (TCWG): Make targeted inquiries regarding:
   • Whether any substantial contingent liabilities or commitments have been incurred.
   • Whether significant changes in capital stock, long-term debt, or working capital have occurred.
   • Whether any unusual accounting adjustments have been made since year-end.
   • The current status of items accounted for based on tentative or preliminary data.
3. Read Available Minutes: Read minutes of meetings of stockholders, the board of directors, and executive committees held after the balance sheet date.
4. Inquire of External Legal Counsel: Review responses to legal inquiry letters and confirm that no new material legal actions have arisen.
5. Obtain Written Management Representations: Obtain the signed management representation letter, which must be dated as of the date of the auditor's report.

---

5. Dual Dating vs. Extending the Report Date

When a subsequent event occurs after the date of the auditor's report but before the financial statements are issued, management must disclose the event (if Type II) or adjust the statements (if Type I). The auditor is faced with a critical reporting choice:

                               REPORT DATING OPTIONS FOR SUBSEQUENT EVENTS
                                                    |
        +-------------------------------------------+-------------------------------------------+
        |                                                                                       |
     OPTION 1: DUAL DATING                                                   OPTION 2: EXTENDING THE REPORT DATE
- Format: "February 15, 2026, except for Note 16,                          - Format: Single date: "March 2, 2026"
  as to which the date is March 2, 2026"                                   - Post-dated responsibility EXTENDS across ALL accounts
- Post-dated responsibility is RESTRICTED                                    and operations through March 2.
  strictly to the matter disclosed in Note 16.                             - Auditor MUST perform full subsequent review procedures
- Auditor has NO responsibility for other events                             through March 2 (inquiries, minutes, rep letter update).
  occurring between Feb 15 and Mar 2.                                      

Exam Trap: Dual dating limits the auditor's post-report responsibility strictly to the referenced footnote. If the auditor instead changes the overall report date to the later date (March 2), the auditor's active audit responsibility is automatically extended across all financial statement accounts through March 2, requiring updated subsequent review procedures across the entire entity.

---

6. Subsequently Discovered Facts After Financial Statement Release

Subsequently discovered facts refer to facts that become known to the auditor after the financial statements have been released, which existed at the date of the auditor's report and would have caused the auditor to modify the report had they been known.

+-------------------------------------------------------------------------------------------------------+
|                                 SUBSEQUENTLY DISCOVERED FACTS WORKFLOW                                |
|                                                                                                       |
|   Auditor learns of fact existing at report date  --> Discuss immediately with Management & TCWG     |
|                                                                                                       |
|   MANAGEMENT AGREES TO COOPERATE                  MANAGEMENT REFUSES TO COOPERATE                     |
|   - Revise financial statements.                  - Execute formal "Disassociation" protocol:         |
|   - Issue updated report (dual-dated/extended).     1. Notify Management & TCWG not to rely on report.|
|   - Notify all users relying on statements.         2. Notify regulatory agencies (SEC).              |
|                                                     3. Notify persons known to be relying on report.  |
+-------------------------------------------------------------------------------------------------------+

The Remediation Protocol When Management Refuses

If management refuses to revise the financial statements or notify users, AU-C 560 requires the auditor to take immediate action to prevent continued reliance on the audit report:

1. Notify Management & TCWG: Formally notify the board of directors that the auditor's report must no longer be associated with the financial statements.
2. Notify Regulatory Agencies: Notify regulatory bodies having jurisdiction over the entity (for example, the SEC for an issuer) that the auditor's report should no longer be relied upon.
3. Notify Relying Parties: If practicable, notify each person known to the auditor to be relying on the financial statements that the auditor's report must not be relied upon. (For public entities, this is accomplished through an immediate public announcement or regulatory filing).