Going Concern under Ind AS 1: From Forecast to Defensible Disclosure

Why the answer affects more than one line item

Good reporting in this area requires more than quoting a principle. The entity must show how the principle was applied to its own facts and how the conclusion will be updated. The practical task in Going Concern under Ind AS 1: From Forecast to Defensible Disclosure is to translate liquidity forecasts, covenant evidence and mitigating actions into a robust basis-of-preparation conclusion and entity-specific disclosure. A weak conclusion may survive the first calculation but fail when a reviewer asks about scope, timing or consistency. The purpose of Ind AS 1 is to present general-purpose financial statements that are comparable across periods and understandable to users without obscuring material information.

Technical foundation

A sound paper separates scope, recognition, measurement and presentation. The scope of Ind AS 1 covers the complete set of financial statements, their structure, minimum presentation requirements and the overarching principles that govern fair presentation. Its operating logic is straightforward even when the facts are not: Management must combine recognition and measurement results from other Ind AS standards into a coherent primary-statement and notes architecture, applying consistency, materiality, aggregation and comparative information principles. Applied to going concern: from forecast to defensible disclosure, this means the team must identify the triggering event, the relevant rights or obligations, and the information available at the reporting date before selecting a measurement method. Disclosure is the final part of the accounting, not an afterthought.

Implementation sequence

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

1. Frame the question. map each material balance and movement to the appropriate primary statement, line item and note. Record its effect on recognition, measurement or disclosure for going concern: from forecast to defensible disclosure.
2. Build the evidence base. challenge classifications, subtotals, aggregation and offsetting against the substance of the underlying transactions. Give the conclusion on going concern: from forecast to defensible disclosure a date and an accountable owner.
3. Apply the accounting test. refresh going-concern, judgement and estimation-uncertainty assessments using information available through authorisation. Retain the source supporting going concern: from forecast to defensible disclosure.
4. Quantify and reconcile. complete a presentation and disclosure review that reconciles every note to the general ledger and primary statements. Link it explicitly to going concern: from forecast to defensible disclosure.

Case-based explanation

At the reporting date, assume the following: An infrastructure company faces a major repayment within nine months and depends on refinancing not yet completed. The matter involves a carrying amount, transaction value or exposure of approximately ₹73 crore. A disciplined response begins when the team will define the reporting perimeter, reporting period and complete statement set before drafting individual notes; it continues when the team will map each material balance and movement to the appropriate primary statement, line item and note. Together, those steps show whether the entity can translate liquidity forecasts, covenant evidence and mitigating actions into a robust basis-of-preparation conclusion and entity-specific disclosure using evidence available at the relevant date.

The going concern: from forecast to defensible disclosure review should challenge allowing note totals, cash-flow movements and equity movements to drift out of reconciliation. Evidence in the form of a signed financial-statement mapping from trial balance to primary statements and notes 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.

Risk of misstatement

Reviewers should be alert to two patterns:

• Allowing note totals, cash-flow movements and equity movements to drift out of reconciliation. The risk increases when different teams own the contract, model, journal and note disclosure. For going concern: from forecast to defensible disclosure, the working paper should show why the entity’s facts do or do not create this risk.
• Treating prescribed line items as a fixed chart rather than a minimum that still requires entity-specific disaggregation. This usually happens when the ledger label is accepted without tracing the underlying terms and timing. For going concern: from forecast to defensible disclosure, the working paper should show why the entity’s facts do or do not create this risk.

A defensible evidence pack

Good governance converts a judgement into a controlled accounting outcome. Useful evidence includes:

• Documented materiality thresholds and qualitative override criteria, specifically cross-referenced to the conclusion on going concern: from forecast to defensible disclosure and the affected financial-statement line items.
• Board-approved going-concern forecasts, sensitivities and financing evidence, specifically cross-referenced to the conclusion on going concern: from forecast to defensible disclosure and the affected financial-statement line items.
• A disclosure checklist with preparer and reviewer sign-off, specifically cross-referenced to the conclusion on going concern: from forecast to defensible disclosure and the affected financial-statement line items.

Ind AS 1 should not be applied in isolation where the fact pattern also touches Ind AS 33, Ind AS 34 and Ind AS 7. The close checklist should assign an owner to each interface, require reviewer sign-off and retain the source data used in sensitivities. For going concern: from forecast to defensible disclosure, clear disclosure should explain how the entity applied that evidence.

Key learning

For practitioners, the objective is not merely to avoid an adjustment. It is to produce information that tells users what changed, why it changed and how uncertainty was handled. The essential point is that the entity must translate liquidity forecasts, covenant evidence and mitigating actions into a robust basis-of-preparation conclusion and entity-specific disclosure. Once that distinction is documented, the calculation, journal, reconciliation and note can follow the same logic. Practitioners should revisit the conclusion when contractual terms, operating facts or material assumptions change. A deeper study of Ind AS 1 helps connect this individual issue with the standard’s wider recognition, measurement and disclosure architecture.