Introduction
Financial statements are intended to present the financial position of an enterprise as at a specific reporting date. Nevertheless, the process of preparing, reviewing and approving those financial statements inevitably extends beyond the balance sheet date. During this intervening period, management may become aware of significant developments affecting customers, suppliers, legal disputes, investments, borrowings or even the entity’s own operations. Such developments often trigger an immediate and practical question:
Should the financial statements already prepared as at the balance sheet date be revised to reflect these developments, or should they merely be disclosed to users?
Although the question appears simple, the answer is often far from straightforward.
In practice, finance professionals frequently adopt one of two extreme approaches. The first is to conclude that every material event occurring after the balance sheet date should be incorporated into the financial statements because users deserve the most up-to-date information available. The second is to take the opposite view, that once the reporting period has ended, subsequent developments belong exclusively to the next accounting period and should never affect the reported figures. However, neither of these approach reflects the accounting principles embodied in Accounting Standard (AS) 4.
1. Understanding the Concept of AS 4
AS 4 does not require management to focus merely on when an event occurred. Rather, it requires management to evaluate what the event signifies. The critical consideration is whether the subsequent event provides additional evidence of conditions that already existed at the balance sheet date, or whether it represents an entirely new condition that arose after the reporting date. This distinction determines whether recognised amounts must be adjusted or whether disclosure alone is sufficient.
1.1. Examples of events arising after the balance sheet date
The following are some of the examples of events occurring after the balance sheet date.
(a) A major customer is declared insolvent shortly after the reporting date.
(b) Litigation pending at year-end is settled before the financial statements are approved.
(c) A manufacturing facility is destroyed by fire after year-end.
(d) Significant fluctuations occur in the market value of investments after the reporting date.
(e) Dividends are declared after the balance sheet date but before the financial statements are approved.
(f) A bank withdraws financing facilities after year-end because of covenant breaches that existed before the reporting date.
Each of these events occurs after the balance sheet date. Yet the accounting consequences are not identical. Some require adjustment to recognised assets or liabilities, whereas others merely require disclosure. The determining factor is not the date of occurrence, but the relationship between the event and the conditions existing at the reporting date.
2. Relevant Provisions of AS 4
The Standard defines the events occurring after balance sheet date as such favourable or unfavourable events that occur between:
(a) the balance sheet date; and
(b) the date on which the financial statements are approved by the Board of Directors (or the corresponding approving authority in the case of other entities).
The significance of this definition is often underestimated. Many finance professionals assume that events occurring after the reporting date are irrelevant because they fall outside the accounting period. AS 4 rejects this assumption. Instead, it expressly requires management to utilise information available up to the date the financial statements are approved, provided that such information assists in faithfully representing the financial position at the reporting date.
The Standard classifies subsequent events into two categories.
2.1. Events providing additional evidence of conditions existing at the balance sheet date
These events do not create new economic circumstances. Instead, they improve management’s understanding of conditions that were already present on the reporting date but whose consequences became clearer only afterwards.
Since the event merely confirms the position existing at year-end, recognised assets and liabilities should be adjusted to reflect the improved information.
Typical examples include:
(a) settlement of litigation confirming an obligation existing at year-end;
(b) insolvency of a debtor confirming financial difficulties existing before year-end;
(c) discovery of fraud, indicating that financial information at year-end was inaccurate;
(d) confirmation of inventory damage that had already occurred before year-end.
The underlying principle is simple. The subsequent event itself is not the reason for the adjustment. Rather, the event serves as additional evidence enabling management to estimate more accurately the financial position that already existed at the reporting date.
2.2. Events indicative of conditions arising after the balance sheet date
The second category consists of events representing entirely new economic circumstances arising after the reporting date. These events do not provide evidence regarding conditions existing at year-end.
Consequently, recognised assets and liabilities should generally remain unchanged. However, where such events are sufficiently significant to influence users’ decisions, appropriate disclosure should accompany the financial statements.
Examples commonly include:
(a) destruction of assets by fire after year-end;
(b) acquisition or disposal of a major business;
(c) commencement of significant litigation arising after year-end;
(d) major borrowings undertaken after year-end;
(e) ordinary post-year-end fluctuations in investment prices.
Although these events may substantially affect the enterprise’s future financial position, they do not alter the financial position existing on the balance sheet date. Accordingly, recognising them within the current year’s financial statements would compromise faithful representation.
Click Here To Read The Full Story
The post How to Account for Subsequent Events Under AS 4 appeared first on Taxmann Blog.
