
Non-adjusting Events under Ind AS 10: When Disclosure Is Enough
The practical reporting issue
The practical risk in this area is rarely a calculation error alone. Classification, timing, evidence and disclosure can each change the reported story. Non-adjusting Events under Ind AS 10: When Disclosure Is Enough deserves separate analysis. The practical requirement is to explain how later conditions remain outside year-end measurement but may need nature and financial-effect disclosure. Reliable ledger data may still be insufficient evidence for the accounting classification. Ind AS 10 addresses favourable and unfavourable events arising between the reporting date and the date the financial statements are authorised for issue. The finance team should use that scope as a boundary and apply the detailed mechanics consistently rather than allowing contractual labels or system defaults to decide the answer.
Drawing the right boundary
The correct answer begins with boundaries. Ind AS 10 applies to favourable and unfavourable events arising between the reporting date and the date the financial statements are authorised for issue. Adjusting events provide evidence of conditions existing at the reporting date; non-adjusting events reflect later conditions but may require disclosure when material, while going concern can override the normal basis of preparation. In practice, non-adjusting events: when disclosure is enough can be distorted when teams mix a rule from a connected standard, use a later event as hindsight, or let an operational system define the accounting unit. A short scope conclusion and a dated fact pattern prevent those errors and give reviewers a stable basis for challenging the estimate or classification.
From contract or data to accounting outcome
The following workflow is suitable for a period-end memorandum, model review or transaction approval:
- Frame the question. update recognised amounts and related disclosures for adjusting events. Give the conclusion on non-adjusting events: when disclosure is enough a date and an accountable owner.
- Build the evidence base. estimate and disclose material financial effects of non-adjusting events where practicable. Retain the source supporting non-adjusting events: when disclosure is enough.
- Apply the accounting test. reassess going concern, covenants and liquidity using all relevant post-period information. Link it explicitly to non-adjusting events: when disclosure is enough.
- Quantify and reconcile. establish the authorisation date and maintain an event log through that date. Trace it to the reported outcome for non-adjusting events: when disclosure is enough.
Worked application
At the reporting date, assume the following: A factory is destroyed by a fire caused by an event occurring three weeks after year end. The matter involves a carrying amount, transaction value or exposure of approximately ₹616 crore. A disciplined response begins when the team will establish the authorisation date and maintain an event log through that date; it continues when the team will trace each event to the condition it evidences and determine when that condition existed. Together, those steps show whether the entity can explain how later conditions remain outside year-end measurement but may need nature and financial-effect disclosure using evidence available at the relevant date.
The non-adjusting events: when disclosure is enough review should challenge closing the subsequent-events review before financial statements are authorised. Evidence in the form of board minutes, legal updates and significant-contract reports after year end should be reconciled to source systems and approved assumptions. The conclusion should identify the owner, the date of approval and the event that would require reassessment. This makes the accounting sustainable beyond the current close.
Common shortcuts and why they fail
A technically sound conclusion should demonstrate that these shortcuts were avoided:
- Recognising dividends declared after the reporting period as a year-end liability. The error can affect both the amount and the period in which it is recognised, so a disclosure-only fix is rarely sufficient. For non-adjusting events: when disclosure is enough, the working paper should show why the entity’s facts do or do not create this risk.
- Ignoring customer failure after year end that confirms an existing credit problem. A reviewer will normally challenge consistency with similar transactions and with evidence used elsewhere in the financial statements. For non-adjusting events: when disclosure is enough, the working paper should show why the entity’s facts do or do not create this risk.
Presentation, disclosure and related standards
The evidence pack should be proportionate to materiality but complete enough for another reviewer to reproduce the conclusion:
- A documented adjusting-versus-non-adjusting conclusion for each material event, specifically cross-referenced to the conclusion on non-adjusting events: when disclosure is enough and the affected financial-statement line items.
- Updated cash-flow and covenant forecasts, specifically cross-referenced to the conclusion on non-adjusting events: when disclosure is enough and the affected financial-statement line items.
- Authorisation evidence identifying the approving body and date, specifically cross-referenced to the conclusion on non-adjusting events: when disclosure is enough and the affected financial-statement line items.
Connected-standard analysis is also necessary. Relevant interfaces include Ind AS 36, Ind AS 37 and Ind AS 109. The team should document whether these standards change recognition, measurement, tax, impairment, cash-flow classification or disclosure. For non-adjusting events: when disclosure is enough, the final tie-out should align management reporting, the primary statements and the notes.
Closing insight
The durable lesson is to preserve the chain from facts to conclusion. For non-adjusting events: when disclosure is enough, that chain consists of the relevant business facts, the Ind AS 10 criterion, the measurement or classification method, the supporting evidence and the resulting presentation. Teams that build those elements together are less likely to rely on hindsight or generic disclosure. The topic is also a useful entry point into the broader Ind AS 10 course pathway because it shows how one principle moves from transaction analysis to an audit-ready financial-statement conclusion.
Continue learning on JUMOQ
Turn this guidance into practical capability
Explore focused courses, worked examples and activities related to this topic.
Explore related courses →References
- Ind AS 10, Events after the Reporting Period — ICAI Compendium of Indian Accounting Standards 2025–2026
- JUMOQ learning pathway — Indian Accounting Standards
