Ind AS 1, Presentation of Financial Statements sits at the core of how Indian companies communicate financial position and performance. The Companies (Ind AS) Second Amendment Rules, 2025 refine this foundation by tightening when an entity truly has the right at the reporting date to defer settlement, defining what counts as “settlement” for classification purposes, and adding targeted covenant-risk disclosures when non-current classification depends on meeting covenants within the next 12 months.
The amendments draw a clear line in the sand firmly separating what qualifies as current versus non-current, leaving no room for subjective interpretation. A temporary Indian carve-out applies in financial year (FY) 2025-26 allowing a post balance-sheet waiver to avoid current classification (with disclosure). From FY 2026-27 this relief goes and India fully converges with IAS 1 on breaches at period-end where only the rights on the reporting date speak, and everything else is noise.
WHY THE AMENDMENTS MATTER
Under the old wording, preparers often asked: Does a covenant tested after year-end affect classification? Can we rely on a lender’s waiver after the reporting date? What if we intend to settle early? Different interpretations led to inconsistency. The amendments address these by anchoring classification solely to enforceable rights at period-end, regardless of intentions or subsequent actions.
Pre vs. Post Amendment Criteria
| Pre-amendments criteria |
Pre-amendments criteria |
| An entity shall classify a liability as current when:
(a)
It expects to settle the liability in its normal operating cycle, |
An entity shall classify a liability as
current when:
(a)
It expects to settle the liability in its normal operating cycle, |
(b)
It holds the liability primarily for the purpose of trading,(c)
The liability is due to be settled within twelve months
after the reporting period, or |
(b)
It holds the liability primarily for the purpose of trading,(c)
The liability is due to be settled within twelve months
after the reporting period, or |
(d)
It does not have an unconditional right to defer settlement of the liability for at least twelve months after the reporting period. Terms of a liability that could, at the option of the counterparty, result in its settlement by the issue of
equity instruments do not affect its classification. |
(d)
It does not have the right at the end of the reporting period to defer settlement of the liability for at least twelve months after the reporting period. |
| An entity shall classify all other liabilities as non-current. |
An entity shall classify all other liabilities as non-current. |
When an entity presents current and non-current assets, and current and non-current liabilities, as separate classifications in its statement of financial position, it shall not classify deferred
tax assets (liabilities)
as current assets (liabilities). |
When an entity presents current and non-current assets, and current and non-current liabilities, as separate classifications in its statement of financial position, it shall not classify deferred tax assets (liabilities) as current assets (liabilities). |
Overview of Key Requirements (Pre vs. Post Amendment Criteria)
| Area |
Pre-Amendment |
Post-Amendment |
| Paragraph 69(d) – Core definition |
Liability classified current if due within 12 months or if no clear right to defer; wording left room for differing interpretations. |
Clarified: liability is current if the entity does not have the right, at the reporting date, to defer settlement for ≥12 months. Anchors classification
to enforceable rights existing at period-end. |
| Covenants (paragraph 72A–72B) |
No explicit guidance on how covenants affect classification. |
New paragraphs added: covenants linked to period-end measures affect period-end classification (even if tested later); covenants tested only after reporting date do not. |
| Rollover rights (paragraph 73) |
Silent; practice varied. |
Explicit: liability is non-current only if an unconditional rollover right exists at period-end. |
| Breach at period-end (paragraph 74) |
No clear requirement; diversity in practice. |
Two-step change:
– FY 2025-26 transitional carve-out: waiver after year-end but before approval can avoid current classification (with Ind AS 107 disclosure).
From FY 2026-27: carve-out removed. If breach exists at period-end, liability is current, regardless of waiver. Only a grace period in place at period-end preserves non-current. |
| Grace period (paragraph 75) |
Not expressly codified. |
Non-current if, by reporting date, lender provides a grace period extending ≥12 months. |
| Intent / early settlement (paragraph 75A) |
Often debated; some looked to management intent. |
Clarified: classification is unaffected by management’s intention or by actual settlement after year-end. |
| Definition of “settlement” (paragraph 76A–76B) |
No definition. |
Settlement defined: transfer of cash/other resources or own equity instruments (with an exception for equity components classified under Ind AS 32). |
| Events after reporting (paragraph 76) |
Listed as non-adjusting events (refinancing, waivers, grace, settlement). |
Temporarily deleted in 2025 text; reinstated from 2026. |
Right to defer settlement
Earlier position (pre-amendment):
Under the pre-amended Ind AS 1, a liability could be classified as non-current only if the entity had an unconditional right to defer its settlement for at least twelve months after the reporting date. In practice, however, most loan agreements contain debt covenants that must be complied with either continuously (e.g., no change in control, no material adverse event) or at frequent intervals (e.g., quarterly or half-yearly debt-equity or current ratio tests). Although borrowers generally expected to comply, these conditions were not entirely within their control. This created uncertainty as to whether such loans met the strict “unconditional right” test. Different interpretations emerged in practice, leading to diversity in reporting and making it difficult for users to compare financial statements.
New position (post-amendment):
Post amendment, the standard no longer refers to an “unconditional right”; instead, it simply requires a right to defer settlement. This means that even a conditional right can support non-current classification of a financial liability or borrowing, provided it is substantive and exists at the reporting date.
A new paragraph also makes clear that, the right to defer settlement may be subject to compliance with covenants in the loan agreement. Only covenants requiring compliance on or before the reporting date are relevant for classification, even if the actual testing takes place after year-end.
Covenants that apply only after the reporting date (i.e., future covenants) do not affect classification. Instead, future covenants must be explained through disclosures in the notes, along with details of the related liabilities.
EXPECTED DEFERRALS AND INTENTIONS TO SETTLE EARLY
The amendments clarify that for a loan liability to be classified as non-current, the entity must hold a right to defer settlement for at least twelve months after the reporting date. Whether the entity actually intends to exercise that right is irrelevant.
The earlier reference to management’s expectations has been deleted, and a new paragraph makes this principle explicit: classification is unaffected by the likelihood of early settlement. Accordingly, if a loan meets the criteria for non-current classification, it remains non-current even if management intends or expects to repay within twelve months, or even if the entity actually repays the loan between the reporting date and the date the financial statements are approved for issue.
In such cases, the entity may need to disclose the timing of settlement in the notes to ensure users understand the impact on liquidity.
The amended standard also clarified that the “expected to be settled in the normal operating cycle” criterion for current classification is intended only for items such as trade payables and operating accruals that are part of working capital. This test does not apply to loans and similar financial liabilities.
IMPACT OF BREACHES TO DEBT COVENANTS – IND AS 1
The final amendments to Ind AS 1 retain a temporary carve-out for FY 2025-26 (periods beginning on or after 1 April 2025):
Material vs. minor breaches: Only a breach of a material covenant of a long-term loan triggers current classification. Breaches of minor provisions do not require reclassification.
Post-reporting date waivers: If there is a breach of a material covenant on or before the reporting date, the loan would normally be current.
However, under Ind AS 1 (FY 2025-26 only), if the lender provides a waiver after the reporting date but before approval of the financial statements, the loan may still be shown as non-current. Such waivers are treated as adjusting events.
From FY 2026-27 (periods beginning on or after 1 April 2026):
Both carve-outs are removed, and Ind AS 1 will be fully converged with IAS 1. That means, no distinction between material and minor breaches, i.e., any breach is relevant and waivers obtained only after the reporting date no longer cure the breach for classification. A liability is current if the breach exists at year-end, unless a grace period extending ≥12 months was already agreed at that date.
This transition means that entities preparing financial statements for FY 2025-26 can still apply the carve-out, but from FY 2026-27 onward, classification will strictly follow the principle that rights must exist at the reporting date.
To make the amendments easier to understand, here are some practical situations that show how classification works under revised Ind AS 1. In each case, the entity has a 31 March year end and a loan of ₹1,000 crores repayable on 31 March 2029.
Scenario 1 – Future covenant tests
The loan agreement requires compliance with debt covenants at the end of each quarter, i.e., 30 June, 30 September, 31 December, and 31 March 2025. The entity has complied with all covenants till 31 March 2025 and expects to comply going forward, but it is not fully within the entity’s control.
Analysis:
At the reporting date, the entity has the right to defer settlement for at least twelve months. Future covenant tests do not affect classification. Since there has been no breach up to 31 March 2025, the loan is classified as
non-current. The same conclusion would apply even if there were uncertainty about future compliance as the classification depends only on the position at the reporting date.
Impact across years:
There is no difference between FY 2025-26 and FY 2026-27 . Since no breach exists at the reporting date, the loan is non-current under both
Scenario 2 – Waiver before year-end
Same facts as Scenario 1 except that the entity anticipated in February 2025 that it might breach its covenant as at 31 March 2025. On 15 March 2025, it entered into an agreement with the lender under which the 31 March covenant test was waived. As a result, no breach on
31 March 2025 would give the lender the right to demand repayment, although future covenant breaches at later test dates could still trigger repayment.
Analysis:
Since the 31 March covenant was waived before the reporting date, there is no non-compliance at year-end. The entity therefore has the right to defer settlement for at least twelve months. Under the amended Ind AS 1, future covenant tests do not affect classification at the reporting date. The loan is classified as non-current.
Impact across years:
Because the waiver was obtained before the reporting date, the position is same under FY 2025-26 and FY 2026-27. Since no breach exists at the reporting date, the loan is non-current under both
Scenario 3 – Breach waived on reporting date
Same facts as Scenario 1 except that in this case, the entity did not comply with the covenant as at 31 March 2025, which gave the lender the right to demand immediate repayment. However, on the same date, the lender agreed to waive the non-compliance and confirmed it would not demand repayment for the breach at 31 March 2025. Future breaches at later covenant test dates could still trigger repayment.
Analysis:
Because the waiver was granted on the reporting date itself, the entity retained the right to defer settlement for at least twelve months. Under the amended Ind AS 1, future covenant tests do not affect classification at the reporting date. Accordingly, the loan is classified as non-current.
Scenario 4 – Short grace period
Same facts as Scenario 1 except that in this case, the entity did not comply with the covenant as at 31 March 2025, giving the lender the right to demand immediate repayment. On the same date, the lender agreed not to demand repayment until 30 April 2025. The lender also stated that if the entity complied with the covenant on 30 April 2025, it would not demand repayment for the 31 March breach. However, the lender retained the right to demand repayment for non-compliance with later scheduled covenant tests.
Analysis:
By agreeing not to act on the 31 March breach, the lender has effectively waived the non-compliance at the reporting date, but introduced an additional covenant test on 30 April 2025. Under the amended Ind AS 1, future covenant tests do not affect classification at the reporting date. Therefore, the entity is considered to have the right to defer settlement for at least twelve months after 31 March 2025. The loan is classified as non-current.
Impact across years:
The scenarios 1 to 4 above, use a 31 March 2025 year-end purely for illustration. The principles, however, apply equally to later periods — whether the reporting date is 31 March 2026 (first year of applying the FY 2025-26 amendments) or 31 March 2027 (first year after the FY 2026-27 convergence). For Scenarios 1 to 4, the outcome is unchanged across both years. Because any waiver (where relevant) exists at the reporting date, the entity clearly has the right to defer settlement for at least twelve months. The loan is therefore non-current under both FY 2025-26 and FY 2026-27 rules.
Scenario 5 – Breach waived after reporting date
Same facts as Scenario 1 except that in this case, the entity did not comply with the covenant as at 31 March 2025, giving the lender the right to demand immediate repayment. On the same date, the lender agreed not to demand repayment for one month (until 30 April 2025). At that point, the lender would reassess the entity’s covenant compliance and decide whether to continue the loan. The lender also retained rights for future covenant breaches at later scheduled dates.
Analysis:
Here, the lender has not waived the breach. Instead, it has only provided a short grace period of one month. Even if the entity complies on 30 April, the lender could still rely on the original 31 March breach to demand repayment. Therefore, the entity does not have a substantive right to defer settlement for at least twelve months. The loan must be classified as current.
Impact across years: The conclusion is the same under both FY 2025-26 and FY 2026-27 rules — a short grace period does not provide the right to defer settlement for twelve months. The loan remains current in both years
Scenario 6 – Intention to repay early
Same facts as Scenario 1, except the entity did not comply with the covenant as at 31 March 2025, giving the lender the right to demand immediate repayment. On 30 April 2025, the lender agreed to waive the non-compliance and confirmed it would not demand repayment for the 31 March breach. The lender still retained rights over future covenant breaches at later scheduled test dates.
Analysis:
At 31 March 2025, the entity did not have the right to defer settlement for at least twelve months — the waiver only came later.
Under IAS 1, such a waiver after the reporting date is a non-adjusting event, so the liability is current.
Under Ind AS 1 for FY 2025-26 (year ending 31 March 2026), India’s carve-out allows a waiver obtained after the reporting date but before approval of the financial statements to be treated as if it existed at year-end. The loan can therefore be shown as non-current.
From FY 2026-27 (year ending 31 March 2027), this carve-out is removed. The same facts will result in the loan being current.
Impact across years:
FY 2025-26: Loan is non-current (carve-out applies).
FY 2026-27: Loan is current (carve-out removed, aligned with IAS 1).
The above examples demonstrate how the amended Ind AS 1 brings clarity to the classification of liabilities as current or non-current. Under the pre-revised standard, treatment of future covenants was not explicitly addressed, which meant entities could arrive at different interpretations in practice. With the new guidance, the principle is clear: classification hinges on the rights that exist at the reporting date, not on expectations or post-date events.
The authors believe that it is therefore essential for entities to revisit past positions and ensure their policies and classifications are aligned with the amended requirements, particularly as the Indian carve-out on covenant breaches will be removed from FY 2026-27 onwards.
Example – Expected Early Settlement of Loan
As at 31 March 2025, an entity has a loan repayable in five years from the reporting date. The entity is planning to prepay this loan within the next three months. The financial statements of the entity for the year ended 31 March 2025 will be approved for issue on 31 May 2025.
In this case, the entity has a right to defer settlement for at least twelve months after the reporting date. The intention to prepay the loan does not affect classification. Hence, the liability is classified as non-current.
Will it make a difference if the entity has prepaid the loan before the financial statements were approved for issue?
The standard is clear that classification is based on the right of the entity at the reporting date. Hence, the loan will still be classified as non-current. However, the entity will be required to disclose the subsequent repayment as a non-adjusting event.
Will the position change if the entity has notified the bank of its intentions but has not entered into an irrevocable commitment to repay the loan within 12 months?
As stated above, the classification is based on the right of the entity at the reporting date. Hence, the loan will still be classified as non-current. However, the entity should make appropriate disclosures regarding its intention to prepay the loan.
What if the entity has entered into a binding agreement with the bank for early settlement before the reporting date and the said agreement is irrevocable?
In this case, the entity no longer has the right to defer settlement for at least twelve months at the reporting date. Accordingly, the loan is classified as current.
SETTLEMENT OF A LIABILITY BY ISSUE OF EQUITY INSTRUMENTS
Before the amendments, Ind AS 1 required that if a liability could be settled at the option of the counterparty by issuing equity instruments, this feature did not affect classification. For example, a convertible instrument repayable in cash after more than twelve months — but which the holder could choose to convert into equity at any time — was classified as non-current, since the cash maturity date was beyond twelve months.
The revised Ind AS 1 removes this clause. Now, settlement through the issue of equity instruments is also treated as settlement for the purpose of classifying a liability as current or non-current. The only exception is when the conversion option itself meets the definition of an equity instrument under Ind AS 32 Financial Instruments: Presentation.
Practical impact:
Many companies have issued convertible instruments that are redeemable only after a fixed period but allow the holder to convert them into a variable number of shares at any time. Prior to amendments, these were shown as non-current. After the amendment, they must be treated as current liabilities, because the counterparty can demand settlement immediately through equity.
Example– Classification of Optionally Convertible Redeemable Preference Shares (OCRPS)
An entity issues OCRPS redeemable after 10 years (either mandatorily or if there is no qualified IPO by the end of year 10). The holder, however, can require conversion into equity shares at any time after issuance. Consider the following conversion formulas:
Scenario 1: OCRPS are convertible into a variable number of shares based on the fair value of equity shares at the conversion date.
Scenario 2: OCRPS are convertible into a fixed number of shares upfront, but with down-round protection (number of shares changes if new shares are issued at a lower price).
Scenario 3: OCRPS are convertible into a fixed number of shares upfront, with no down-round protection or other clauses that change the conversion ratio.
Response:
Earlier position (pre-amendment):
Before the amendments, Ind AS 1 stated that if a liability could, at the option of the counterparty, be settled through the issue of equity instruments, this feature did not affect its classification. In practice, this meant that the holder’s right to demand early conversion into equity was ignored when deciding current versus non-current classification. As a result, in all three OCRPS scenarios discussed, the liability could reasonably have been shown as non-current in the balance sheet for years 1 to 9.
Amended position (post-amendment):
Following the amendments, the option to convert into equity can be ignored only if it qualifies as equity under Ind AS 32. If the conversion feature fails the equity test, it must be considered in classification. Accordingly, the following treatment will apply in the balance sheet for years 1 to 9:
Scenario 1: The OCRPS are convertible into a variable number of shares, determined based on the fair value of the equity shares at the conversion date. Under Ind AS 32, such a conversion feature is classified as a liability, not equity. Because the holder can demand conversion (and therefore settlement) at any time, the entire instrument must be classified as a current liability in years 1 to 9.
Scenario 2: The OCRPS are convertible into a fixed number of shares upfront, but the terms include a down-round protection clause, which can change the number of shares to be issued if new shares are issued at a lower price. Because the host instrument is a financial liability, this conversion option fails the “fixed-for-fixed” test and therefore does not qualify as equity under Ind AS 32. Instead, it is treated as an embedded derivative liability.
Under Ind AS 109, the issuer may measure the whole instrument at fair value through profit or loss (FVTPL) or separate the host liability (at amortised cost) and the embedded derivative (at FVTPL). Regardless of the measurement approach, the conversion feature is not equity. Accordingly, the entire OCRPS must be classified as a current liability in years 1 to 9.
Scenario 3: The OCRPS are convertible into a fixed number of shares upfront, with no down-round protection or other clauses that could change the number of shares to be issued. In this case, the conversion option qualifies as equity under Ind AS 32. The host instrument, however, remains a financial liability. Because the conversion option is treated as equity, it is ignored for classification purposes, and the OCRPS liability is classified as non-current in the balance sheet for years 1 to 9.
In year 10, once redemption falls due within twelve months, the liability becomes current in all scenarios, under both the pre-amended and post-amendment standards. Year 10 treatment:
This example highlights how the amendment fundamentally changes practice: only conversion options that meet the strict “equity” definition under Ind AS 32 are ignored. All others bring the liability into current classification, even if legal maturity is much longer.
NEW DISCLOSURE REQUIREMENTS
The amendments introduce detailed disclosure obligations when a liability from a loan agreement is classified as non-current, but the right to defer settlement depends on compliance with covenants falling due within the next twelve months. Disclosures required include:
(i) Information about the covenants:
(a) The nature of the covenants,
(b) When the entity must comply with them, and
(c) The carrying amount of the related liabilities.
(ii) If facts and circumstances suggests that the entity may face challenges in meeting such covenants, those circumstances must be disclosed. For example- indicate potential difficulty in compliance:
(a) The entity has already taken actions during or after the reporting period to avoid or mitigate a potential breach,
(b) The entity would not have complied with the covenants, if compliance had been assessed based on its circumstances at the reporting date
The authors believe that these disclosure requirements are entirely new for most entities. In the past, such disclosures were not made, both because there was no explicit requirement and because many companies considered covenant-related information to be confidential. With the amendments now in place, entities will have no choice but to comply. For instance, an entity with several loan arrangements and each with multiple covenants, may find itself required to disclose a long list of covenant details. In our view, the first set of disclosures (covering the nature of covenants, timing of compliance, and carrying amounts) will be necessary in all cases where:
(a) a loan liability is classified as non-current, and
(b) there are one or more covenants that require compliance within the next twelve months.
This requirement applies irrespective of whether management expects any difficulty in compliance.
With regard to the second disclosure, entities are expected to assess not only whether they have complied with covenants up to the reporting date, but also whether future difficulties may arise based on information available at that date. If such challenges are foreseen, they must be disclosed in the financial statements.
This requirement can be sensitive. Disclosure of potential difficulties may cause lenders, creditors, and other stakeholders to become more cautious, which in turn could accelerate the very risks being highlighted and reduce the chances of managing them successfully. To balance this, entities may also wish to explain how they plan to mitigate potential breaches. However, such disclosures should be factual, verifiable, and carefully worded to avoid inadvertently providing prospective financial information.
The amendments to Ind AS 1 apply retrospectively. For FY 2025-26 (periods beginning on or after 1 April 2025), companies must adopt the new rules including the temporary carve-out on covenant breaches and restate comparatives. From FY 2026-27 (periods beginning on or after 1 April 2026), this carve-out is removed, and Ind AS 1 is fully aligned with IAS 1. At that point, classification will depend only on rights that exist at the reporting date, and waivers obtained later will no longer change the outcome.
The amendments to Ind AS 1 mark a turning point in liability classification. FY 2025-26 is the clarity year: rights at the reporting date take centre stage, covenants and settlement are defined, and new disclosures improve transparency with a temporary waiver relief for breaches.
FY 2026-27 is the convergence year: the waiver relief ends, events after reporting return as disclosures, and India stands fully aligned with IAS 1. The authors believe that for preparers, the message is simple: focus on the rights that exist at the reporting date, review covenant terms carefully, and be ready to explain them clearly in the notes.