IAS 10 and Ind AS 10 explained for 2026: adjusting vs non-adjusting events, dividends, going concern, and disclosures that protect your audit opinion.
IAS 10- Events After the Reporting Period
IAS 10 — mirrored in India by Ind AS 10 and broadly aligned with AS 4 under the legacy GAAP framework — governs how you treat events occurring between the balance sheet date and the date your financial statements are authorised for issue. For most Indian companies closing their books on 31 March 2026, that window runs from 1 April 2026 through to the board meeting at which accounts are approved, typically in May or June 2026. Get the classification wrong and you risk a qualified audit opinion, an NFRA thematic-review comment, or a SEBI observation letter. Get it right and your accounts are defensible, your disclosures are complete, and your audit committee sign-off is clean.
The Two Categories That Drive Every Decision
IAS 10 / Ind AS 10 draws a single, decisive line through all subsequent events:
- Adjusting events provide evidence of conditions that existed at the end of the reporting period. You adjust the recognised amounts in the financial statements.
- Non-adjusting events are indicative of conditions that arose after the reporting period. You do not change any number in the financial statements, but you disclose if material.
The critical word is evidence. The condition — a debtor's financial difficulty, a legal obligation, an inventory write-down requirement — must have existed at the balance-sheet date. The post-period event merely confirms or quantifies what was already there.
This distinction sounds clean in theory, but it breaks down in practice because accountants conflate the event (which happened after year-end) with the condition (which existed at year-end). Apply one question every time: "Was this condition already present on 31 March 2026, and does this post-period event simply provide better evidence of it?" If yes, adjust. If no, disclose.
Adjusting Events: When You Must Reopen the Numbers
The following are classic adjusting events, with the reasoning you need to document:
Debtor Insolvency Confirmed After Year-End
A customer announces insolvency in April 2026, but a review of payment history shows financial distress was present — bounced cheques, 180-day overdue balances — well before 31 March 2026. The condition (credit impairment) existed at the reporting date. The post-period announcement provides the confirming evidence. Write off the receivable or increase your expected credit loss (ECL) provision accordingly.
Settlement of a Court Case
A lawsuit pending at 31 March 2026 is settled post-period. If the settlement confirms that a present obligation existed at year-end, it is adjusting. The key test: was there a present obligation at the reporting date? If the claim was entirely contingent on an act that occurred after year-end, it is non-adjusting.
Inventory Sold Below Carrying Value
If inventory is sold in the post-period window at a price below its carrying amount, this is evidence that net realisable value (NRV) was already below cost on 31 March 2026. IAS 2 / Ind AS 2 requires inventory at the lower of cost and NRV; the post-period sale price provides the NRV confirmation.
Fraud or Error Discovered
Discovery of a deliberate overstatement of revenue, or a material accounting error that rendered the financial statements incorrect at the reporting date, is always adjusting — regardless of when the discovery is made.
Finalisation of Performance Bonuses or Variable Pay
If an obligation to pay performance bonuses or profit-sharing existed at year-end but the quantum was uncertain, and the final amount is determined post-period, that figure adjusts the year-end financial statements.
Non-Adjusting Events: Disclose, Do Not Adjust
These relate to conditions that genuinely arose after the reporting period. You do not change a single number in the financial statements, but material non-adjusting events require a note.
Common examples:
- A significant fall in market value of listed investments between 31 March 2026 and the authorisation date
- Announcement of a business combination, acquisition or demerger after year-end
- Destruction of significant assets by fire, flood or earthquake after the reporting date
- Commencement of major litigation arising entirely out of a post-period act
- Issue of equity shares, debentures or drawdown of a term loan after year-end
- Announcement of a major restructuring plan
The market-value decline deserves emphasis. If your company holds quoted equity investments classified as FVTOCI or FVTPL under Ind AS 109, a 35% fall in value between 1 April and 20 May 2026 does not restate the 31 March 2026 balance sheet figure. Market prices fluctuate for reasons entirely disconnected from year-end conditions. It is a non-adjusting event — disclose the estimated financial effect if material, but do not re-measure.
Worked Example: Classifying Five Post-Period Events for FY 2025-26
Assume Rajputana Textiles Limited, a listed company, closes its accounts on 31 March 2026 and its board meets on 28 May 2026 to approve the financial statements. In the intervening period, five events occur:
| # | Event | Classification | Treatment |
|---|---|---|---|
| 1 | Trade debtor (outstanding: Rs. 38 lakh) files for insolvency on 14 April 2026. The debtor was 210 days overdue at 31 March 2026 with three dishonoured cheques. | Adjusting | Recognise bad debt expense of Rs. 38 lakh; write off the receivable in FY 2025-26 P&L |
| 2 | Finished-goods warehouse (carrying value Rs. 1.2 crore) destroyed by fire on 3 May 2026. Insurance claim lodged but not yet admitted. | Non-adjusting | Disclose nature, Rs. 1.2 crore impact, and insurance recovery status in the notes |
| 3 | Raw material inventory (cost: Rs. 55 lakh) sold in distress on 20 April 2026 for Rs. 39 lakh. The supply-side price pressure began in February 2026. | Adjusting | Write down inventory by Rs. 16 lakh to NRV in FY 2025-26 accounts |
| 4 | Merger announcement with an unrelated entity on 10 May 2026. No restructuring existed at year-end. | Non-adjusting | Disclose the nature and, where determinable, the financial effect |
| 5 | Income-tax demand of Rs. 9.2 lakh (AY 2024-25) received 22 April 2026; the company had provided only Rs. 4 lakh at 31 March 2026 for this specific dispute. | Adjusting (partial) | Increase provision by Rs. 5.2 lakh to align with the confirmed demand |
Net impact on FY 2025-26 profit or loss from adjusting entries: Rs. 38L (debtor) + Rs. 16L (inventory NRV) + Rs. 5.2L (tax provision top-up) = Rs. 59.2 lakh additional pre-tax charge.
The two non-adjusting events (fire, merger) require careful, quantified note disclosure — but they leave every number on the face of the financial statements unchanged.
Dividends Declared After Year-End: The Rule Companies Keep Getting Wrong
This is the most widely misapplied rule in Ind AS 10. Para 12 of the standard states:
> "If an entity declares dividends to holders of equity instruments after the reporting period, the entity shall not recognise those dividends as a liability at the end of the reporting period."
Most Indian boards recommend a final dividend at their May board meeting — that is, after 31 March. The dividend flows from a decision taken after the reporting date, so no present obligation existed at year-end. It is a non-adjusting event. The only required treatment is a note disclosure.
Worked example: Rajputana Textiles' board recommends a final dividend of Rs. 4 per share on 80 lakh equity shares at its 28 May 2026 meeting — a total outflow of Rs. 3.2 crore. This amount has no place on the 31 March 2026 balance sheet. It will be recognised as a liability only in FY 2026-27, after shareholders ratify it at the AGM. In the FY 2025-26 financial statements, it appears in a note: "Subsequent to the reporting date, the Board of Directors recommended a final dividend of Rs. 4 per equity share, aggregating Rs. 3.2 crore, subject to shareholder approval. No liability has been recognised in these financial statements."
The legacy AS 4 hangover: Under the old AS 4, proposed dividends were recorded as provisions — a balance sheet liability — pending shareholder approval. Ind AS 10 reverses this entirely. Many companies that transitioned to Ind AS before 2019 never scrubbed this out of their closing templates. If a "provision for proposed dividend" still sits under current liabilities at 31 March, it is wrong. The auditor should flag it; the audit committee should demand it be corrected.
Going Concern: The One Non-Adjusting Circumstance That Rewrites Everything
IAS 10 / Ind AS 10 contains one overriding rule that differs fundamentally from all others. If, after the reporting period, management determines that it intends to liquidate the entity or cease trading, the financial statements must not be prepared on a going concern basis — even if that decision was taken entirely after 31 March 2026.
This is the only situation where a post-period development does not just call for a note. It changes the entire basis of preparation. Assets must be remeasured at liquidation or realisable values, long-term classifications collapse into current, and the auditor's report must reflect the changed basis.
Practical triggers to watch for during the post-period window:
- A principal bank formally calling in a term loan or cash credit facility and refusing renewal
- An NCLT order admitting a winding-up petition filed by a major creditor
- A regulatory licence revocation — SEBI cancelling a broker's Certificate of Registration, or RBI cancelling an NBFC's Certificate of Registration — that makes the entity's primary business legally impermissible
- A promoter-group board resolution to liquidate a holding company
If any of these arise between 1 April and the board's approval date, management must reassess the basis of preparation before signing the accounts. The audit committee cannot approve Ind AS financial statements on a going concern basis if that assumption is demonstrably untenable at the authorisation date.
What Your Disclosures Must Actually Say
For material non-adjusting events, Ind AS 10 paragraphs 21–22 require:
- The nature of the event — a specific, factual description
- An estimate of its financial effect, or, if not practicable, a statement that an estimate cannot be made
- The date the financial statements were authorised for issue and by whom (e.g., "authorised by the Board of Directors on 28 May 2026")
- Whether the entity's owners or others have the power to amend the financial statements after issue
What a weak disclosure looks like: > "Subsequent to year-end, certain developments may have an impact on the company's financial position."
This tells the reader nothing. NFRA's published inspection findings have cited language almost identical to this as a disclosure deficiency.
What a strong disclosure looks like: > "Subsequent to 31 March 2026, the company's Bhiwandi warehouse, containing finished goods with a carrying value of Rs. 1.2 crore, was destroyed by fire on 3 May 2026. An insurance claim of Rs. 1.1 crore has been lodged with the insurer; the claim has not yet been admitted. The estimated net exposure, after anticipated insurance recovery, is approximately Rs. 10 lakh. No adjustment has been made in these financial statements as the event arose after the reporting date and does not provide evidence of conditions existing at 31 March 2026."
The second version is defensible before NFRA, SEBI, and in litigation. The first is not.
Ind AS 10 vs IAS 10: Key Differences for Indian Reporters
For entities applying Ind AS (listed companies and large unlisted companies above the prescribed net worth / turnover thresholds), Ind AS 10 is substantively converged with IAS 10. There are no significant carve-outs.
For entities still on AS 4 (smaller unlisted companies, LLPs and partnership firms below the Ind AS threshold), the differences matter:
| Area | AS 4 | Ind AS 10 / IAS 10 |
|---|---|---|
| Proposed dividends | Recognised as a provision (balance-sheet liability) at year-end | Not recognised; disclosed in notes only |
| Going concern override | Broadly similar principle | Identical override rule |
| Disclosure of authorisation date | Recommended | Mandatory |
| Adjusting / non-adjusting framework | Not formally articulated | The core classification architecture |
SEBI LODR Regulation 33 requires listed entities to submit audited standalone and consolidated financial results within 60 days of the financial year-end — that is, by 29 May 2026 for FY 2025-26. This compresses your post-period window severely. The subsequent-events review cannot be an afterthought bolted on after the audit is otherwise complete; it must be built into the audit committee agenda as a standing item.
A Step-by-Step Review Process for the Post-Period Window
Integrate this into your standard year-end close timeline for FY 2025-26:
- 1–15 April 2026: The finance team circulates a formal subsequent-events questionnaire to business heads, legal counsel, the company secretary, and HR (for bonus disputes). Questions cover: new litigation, customer defaults, regulatory orders, asset damage, significant contracts won or lost, financing changes, promoter transactions.
- 16–30 April 2026: The CFO and accounting team classify each flagged item as adjusting or non-adjusting using the single condition test. Borderline items are escalated to the statutory auditor for input before positions are finalised.
- First week of May 2026: Adjusting events are posted to the books. Draft note disclosures for material non-adjusting events are prepared and reviewed by legal counsel where litigation or regulatory orders are involved.
- Audit committee meeting (typically mid-May 2026): The CFO presents a formal subsequent-events memo — one page per material event, with classification rationale, financial effect, and proposed disclosure language. The audit committee chair and independent directors review and sign off. This memo is appended to the audit committee minutes. It is your primary documentary defence in any future NFRA, SEBI, or income-tax inquiry.
- Board meeting (by 28 May 2026 for listed entities): The board approves the financial statements. The authorisation date is recorded in the notes to the accounts. Any event materialising between the audit committee meeting and the board meeting is assessed for materiality at this stage.
- Post-approval monitoring: If a significant event occurs after board approval but before the financial statements are filed or published to the stock exchange, assess with your statutory auditor whether re-authorisation is required. Note: events after the authorisation date fall outside IAS 10's scope, but SEBI's continuous disclosure obligations under Regulation 30 (LODR) may require separate intimation to stock exchanges.
Common Mistakes and How to Avoid Them
Mistake 1 — Adjusting for post-period market value declines Post-period falls in quoted equity prices are non-adjusting. Do not re-mark your FVTPL or FVTOCI portfolio to the authorisation-date price. Fix: Lock portfolio valuation at 31 March 2026 prices. Disclose any material post-period movement in the notes.
Mistake 2 — Recognising proposed dividends as a balance-sheet liability Still common among companies that migrated from old GAAP to Ind AS and never updated their closing-entry templates. Fix: Remove any "provision for proposed dividend" from the 31 March 2026 balance sheet. Place it in a subsequent-events note instead.
Mistake 3 — Treating all post-period tax demands as non-adjusting A demand notice received in April 2026 for AY 2024-25 may be adjusting if it confirms a liability that existed at 31 March 2026 and for which insufficient provision was made. Fix: Trace the demand to the underlying assessment year and the state of provision at that reporting date. Adjust if under-provided.
Mistake 4 — Boilerplate nil-events statements without process Signing off "no subsequent events require adjustment or disclosure" without a documented review process is a compliance risk, particularly under NFRA oversight. Fix: The subsequent-events questionnaire must be formally distributed and signed off by responsible officers. A nil-events statement is only credible when supported by a documented process.
Mistake 5 — Ignoring the going concern test during the window Particularly relevant for companies in stressed sectors — real estate developers, MFIs, companies with concentrated bank lending — where a lender's post-period action can fundamentally alter the going concern assumption. Fix: Build an explicit going concern checklist into every subsequent-events review. Ask specifically whether any financing event, regulatory action, or legal development post-31 March 2026 calls the going concern assumption into question before the accounts are signed.
Key Takeaways
- Apply the single condition test without exception: "Did this condition exist at 31 March 2026?" Yes → adjust. No → disclose if material.
- Dividends recommended after year-end are not a balance-sheet liability under Ind AS 10. The old AS 4 habit of booking a "provision for proposed dividend" is incorrect for Ind AS reporters and must be cleaned up.
- Going concern is the only non-adjusting circumstance that changes the entire basis of preparation, not merely the notes. If management decides post-period to liquidate, the accounts must be recast on a non-going-concern basis.
- Disclosure quality is not optional. A specific, quantified, event-by-event narrative is the standard. Vague or generic language invites NFRA comments and undermines investor confidence.
- The authorisation date — when the board formally approves the financial statements — is both a mandatory disclosure item and the legal cut-off for the IAS 10 subsequent-events review.
- SEBI LODR Regulation 33 imposes a 60-day deadline from year-end for listed entities. Your subsequent-events review must be built into the audit committee agenda, not squeezed in after it.
- Documentary discipline is your defence. The subsequent-events memo presented to and approved by the audit committee — with each event classified, quantified, and disclosed — is your first reference point in any NFRA inspection, SEBI inquiry, or income-tax scrutiny.





