Going Concern Events after the Reporting Period

Why this question matters

The best analysis separates three questions: what happened economically, which Ind AS boundary applies, and what evidence supports the resulting measurement and presentation. Going Concern Events after the Reporting Period deserves separate analysis. The practical requirement is to show why severe post-period deterioration can change the basis of preparation even when the triggering event occurs later. 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.

The governing logic

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, going concern events after the reporting period 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.

A practical application sequence

A practical sequence keeps the analysis ordered and prevents a late disclosure review from uncovering a recognition error:

1. Frame the question. reassess going concern, covenants and liquidity using all relevant post-period information. Link it explicitly to going concern events after the reporting period.
2. Build the evidence base. establish the authorisation date and maintain an event log through that date. Trace it to the reported outcome for going concern events after the reporting period.
3. Apply the accounting test. trace each event to the condition it evidences and determine when that condition existed. Record its effect on recognition, measurement or disclosure for going concern events after the reporting period.
4. Quantify and reconcile. update recognised amounts and related disclosures for adjusting events. Give the conclusion on going concern events after the reporting period a date and an accountable owner.

Worked illustration

Suppose management brings this issue to the audit committee: A lender withdraws committed funding after year end and the entity has no realistic alternative financing. The matter involves a carrying amount, transaction value or exposure of approximately ₹690 crore. The committee should expect finance to estimate and disclose material financial effects of non-adjusting events where practicable before it reassess going concern, covenants and liquidity using all relevant post-period information. That order is important because the objective is to show why severe post-period deterioration can change the basis of preparation even when the triggering event occurs later, not merely to agree a number after the ledger has closed.

For going concern events after the reporting period, the principal risk is ignoring customer failure after year end that confirms an existing credit problem. The file should therefore include updated cash-flow and covenant forecasts. It should also distinguish assumptions from observed facts and explain the effect of each material judgement. A concise sensitivity or alternative-outcome analysis may be more informative than a long generic policy note.

Judgement traps

Two recurring shortcuts deserve explicit challenge:

• 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 going concern events after the reporting period, 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 going concern events after the reporting period, the working paper should show why the entity’s facts do or do not create this risk.

Evidence, presentation and disclosure

A defensible file would normally contain:

• Updated cash-flow and covenant forecasts, specifically cross-referenced to the conclusion on going concern events after the reporting period and the affected financial-statement line items.
• Authorisation evidence identifying the approving body and date, specifically cross-referenced to the conclusion on going concern events after the reporting period and the affected financial-statement line items.
• Board minutes, legal updates and significant-contract reports after year end, specifically cross-referenced to the conclusion on going concern events after the reporting period and the affected financial-statement line items.

The presentation and disclosure review should be performed at the same time as the accounting analysis. Ind AS 10 often interacts with Ind AS 37, Ind AS 109 and Ind AS 1. The memorandum should allocate each issue to the correct standard, reconcile note amounts to the ledger and explain material judgement in entity-specific language. For going concern events after the reporting period, the paper should show where each material assumption is used.

Practical takeaway

This is an area where a short technical memo, supported by reconciled data, can prevent a long audit debate. Going Concern Events after the Reporting Period is best handled as a governed decision rather than a year-end adjustment. The entity should know who owns the conclusion, which data refreshes it and what evidence would trigger reassessment. That approach improves both compliance and the usefulness of the reported information. It also prepares learners to evaluate more complex Ind AS 10 cases in which several principles interact.