Summary : For financial years beginning on or after 1 April 2026, amended Ind AS 1 paragraphs on liabilities with covenants require a reporting-date analysis of the entity’s right to defer settlement for at least twelve months. A covenant that must be complied with on or before the reporting date affects that right even if testing or certification occurs later. A covenant required only after the reporting date does not affect classification at that date, but it may trigger targeted disclosures when facts indicate the entity could have difficulty complying. If a loan is payable on demand because of a breach at year-end, a lender waiver obtained only after the reporting date generally does not create a non-current right at year-end; it is a non-adjusting event requiring disclosure when material. This practical guide focuses on FY 2026-27 covenant calendars, legal agreements, waiver timing, grace periods, disclosure data and audit evidence. It separates contractual classification from management intent and avoids treating refinancing plans or informal lender comfort as a substitute for an enforceable right.
- FY 2026-27 Is the Operative Period for the Covenant Amendments
- Build a Covenant Calendar from Executed Contracts
- Map the Exact Compliance Date
- Separate Period-End from Future Covenants
- A Breach Can Remove the Right to Defer Settlement
- Waiver Timing Determines Whether It Changes Classification
- Waiver in Place by the Reporting Date
- Waiver Obtained After Year-End
- Grace Periods and Cure Rights
- Future Covenant Disclosures Are Designed to Show Risk
- Classification Must Align with Other Financial-Statement Judgments
- Audit File for a Defensible Conclusion
- Frequently Asked Questions
- When do the amended Ind AS 1 covenant paragraphs apply?
- Does a covenant tested after year-end affect classification?
- Can management intent make a breached loan non-current?
- What if the lender waives the breach after 31 March?
- Can a grace period support non-current classification?
- Do future covenants affect year-end classification?
- What carrying amount is disclosed for future-covenant risk?
- Does current classification mean the entity is not a going concern?
- Key Takeaways
FY 2026-27 Is the Operative Period for the Covenant Amendments
The notified amendments to Ind AS 1 apply the revised covenant paragraphs retrospectively for annual reporting periods beginning on or after 1 April 2026. An entity with a 31 March year-end therefore applies them in its FY 2026-27 financial statements, together with comparative and transition analysis required by Ind AS 8. The amendments refine classification; they do not change the underlying loan agreement or cure a breach.
The central question is whether, at the reporting date, the entity has a substantive right to defer settlement of the liability for at least twelve months after that date. Management’s intention to repay, refinance or negotiate is not the deciding factor. The right must arise from the contractual arrangement and must exist at the reporting date.
| Covenant fact | Classification effect at 31 March | Evidence |
|---|---|---|
| Compliance required on or before reporting date | Affects the right to defer, even if tested later | Executed agreement, calculation and certificate |
| Compliance required only after reporting date | Does not affect classification at reporting date | Covenant calendar and next test terms |
| Breach makes loan payable on demand at year-end | Liability is current unless a qualifying right already exists | Default clause and lender correspondence |
| Waiver received only after reporting date | Generally does not create a year-end right | Dated waiver and event disclosure analysis |
| Grace period granted by reporting date for at least 12 months | May support non-current classification if enforceable | Executed waiver or amendment effective at year-end |
Build a Covenant Calendar from Executed Contracts
Map the Exact Compliance Date
The finance team should extract every covenant from executed facility agreements, amendments, side letters and waivers. The calendar should identify the measurement period, compliance date, testing date, certificate date, consequence of failure, cure period and cross-default provisions. A covenant based on the year-end ratio affects classification when compliance is required at year-end, even if the lender receives the certificate weeks later. Administrative testing after year-end does not move the substantive compliance date.
Separate Period-End from Future Covenants
Some agreements require a ratio at each quarter-end; others require a condition at a future drawdown or a date after year-end. Only covenants with which the entity must comply on or before the reporting date affect the right to defer at that date. Future covenants still matter to liquidity, going concern and disclosure, but they do not automatically make the liability current. The contract analysis should quote the clause and explain the conclusion rather than relying on a generic covenant label.
A Breach Can Remove the Right to Defer Settlement
When a breach occurring on or before the reporting date makes a loan payable on demand, the entity no longer has an unconditional or substantive right at that date to defer settlement for at least twelve months. The liability is classified as current, even if the lender has not demanded payment and management expects a waiver. An established commercial relationship or oral assurance does not replace the legal position unless it creates an enforceable right under the agreement and applicable law.
Cross-default clauses require a facility-wide and group-wide review. A breach in one borrowing may accelerate another liability or trigger a right of cancellation. The covenant register should therefore be reconciled to the complete debt population, lender confirmations and legal assessments. Finance should not classify each loan in isolation when contractual links exist.
Waiver Timing Determines Whether It Changes Classification
Waiver in Place by the Reporting Date
If, by the reporting date, the lender has agreed not to demand repayment for at least twelve months after that date, the entity may have the necessary right to classify the liability as non-current, subject to the exact enforceable terms. The waiver should identify the facility, breached clause, effective date, duration and conditions. A letter that merely says the lender will consider the matter is not equivalent to a binding waiver.
Waiver Obtained After Year-End
A waiver obtained after the reporting date but before the financial statements are approved ordinarily confirms a new agreement after year-end; it does not create the missing right at the reporting date. The liability remains current. The waiver, refinancing or correction of the breach is generally a non-adjusting event disclosed under Ind AS 10 when material. The note should not describe the post-year-end waiver in a way that obscures the required current classification.
Grace Periods and Cure Rights
A grace period can affect classification only if the entity already has an enforceable right at the reporting date to cure the breach and the period extends for at least twelve months after that date, as required by Ind AS 1. Cure provisions often have shorter durations or conditions. Legal review should confirm whether the lender can still demand payment during the period and when the right becomes effective.
Future Covenant Disclosures Are Designed to Show Risk
When a liability is classified as non-current because covenants are required only after the reporting date, the entity discloses information in the notes that enables users to understand the risk that the liability could become repayable within twelve months. The information includes the nature of the covenants, when compliance is required, the carrying amount of related liabilities and facts and circumstances indicating that the entity may have difficulty complying.
A boilerplate statement that covenants exist is inadequate when forecasts show limited headroom. The disclosure process should link contractual thresholds to approved forecasts, sensitivities and the carrying amount of affected facilities. Management should explain facts without asserting future compliance as certain. Materiality is assessed in the context of liquidity and solvency as well as the absolute carrying amount.
| Disclosure field | Data owner | Reconciliation |
|---|---|---|
| Nature and timing of covenants | Treasury / legal | Executed facility agreement |
| Carrying amount of related liabilities | Financial reporting | General ledger and balance-sheet line |
| Headroom and difficulty indicators | FP&A / management | Approved forecast and sensitivity model |
| Post-reporting-date waiver or refinancing | Treasury / company secretary | Signed document and Ind AS 10 assessment |
Classification Must Align with Other Financial-Statement Judgments
Current classification does not itself prove that the entity is not a going concern, and non-current classification does not prove that liquidity risk is remote. Ind AS 1 going-concern assessment, Ind AS 7 cash-flow information, Ind AS 107 liquidity-risk disclosures and Ind AS 10 events after the reporting period must be prepared from the same debt facts. Forecasts used for covenant difficulty disclosures should be consistent with board-approved budgets and going-concern models or the differences explained.
A breach can also affect finance costs, modification accounting under Ind AS 109, fees, security enforcement, cross-defaults, management remuneration, dividend capacity and regulatory reporting. The covenant workpaper should list these downstream effects and assign owners. A late waiver may resolve immediate commercial risk without changing the year-end classification, so the accounting entry, disclosure and narrative must be coordinated.
Audit File for a Defensible Conclusion
- Prepare a complete debt and covenant register reconciled to the general ledger and lender confirmations.
- Retain executed agreements, amendments and waivers rather than unsigned drafts or email summaries.
- Document the compliance date separately from the testing and certificate dates.
- Calculate every reporting-date covenant with source-data references and independent review.
- Obtain legal analysis for payable-on-demand, cure, grace-period and cross-default clauses where judgment exists.
- Reconcile future-covenant disclosures to carrying amounts, forecasts and approved sensitivities.
- Record Ind AS 10, going-concern, liquidity-risk and Ind AS 109 consequences in the same issue file.
Frequently Asked Questions
When do the amended Ind AS 1 covenant paragraphs apply?
They apply retrospectively for annual reporting periods beginning on or after 1 April 2026, making FY 2026-27 the first operative year for a March year-end entity.
Does a covenant tested after year-end affect classification?
Yes, if the contract requires compliance on or before the reporting date. A later administrative test does not change the compliance date.
Can management intent make a breached loan non-current?
No. Classification depends on the right existing at the reporting date, not management’s intention or expectation.
What if the lender waives the breach after 31 March?
A post-year-end waiver generally does not create a right at 31 March. The liability remains current, while the waiver may require material non-adjusting-event disclosure.
Can a grace period support non-current classification?
Only if an enforceable right existed at the reporting date and the qualifying period extends for at least twelve months after that date.
Do future covenants affect year-end classification?
Covenants required only after the reporting date do not affect classification at that date, but targeted disclosures may be required.
What carrying amount is disclosed for future-covenant risk?
The carrying amount of the liabilities to which the covenants relate should be disclosed and reconciled to the financial statements.
Does current classification mean the entity is not a going concern?
Not automatically. Going concern is a separate assessment using all relevant facts, financing actions and forecasts.
Key Takeaways
- Classification turns on the right to defer settlement that exists at the reporting date.
- A covenant required by year-end affects classification even when testing occurs later.
- A waiver obtained only after year-end generally does not repair the year-end classification.
- Future covenants can require disclosure of terms, timing, carrying amounts and difficulty indicators.
- Debt classification, going concern, liquidity risk and subsequent-event reporting must use consistent facts.
*****
Disclaimer: This article is a general financial-reporting guide to the covenant-related amendments to Ind AS 1 for annual periods beginning on or after 1 April 2026 and is based on official material checked on 6 November 2026. It is not an accounting opinion, audit conclusion, legal opinion, lender waiver, covenant certificate, solvency assessment, going-concern conclusion, tax advice or substitute for the complete notified text of Ind AS 1, Ind AS 8, Ind AS 10, Ind AS 107, Ind AS 109, Schedule III, loan agreements, amendments and applicable law. Classification depends on the exact executed contract, compliance date, consequences of breach, enforceability of cure or grace rights, timing and wording of any waiver, cross-default terms and facts at the reporting date. A lender’s commercial intention, oral comfort or post-reporting-date action may not establish a right existing at year-end. Future-covenant disclosures require materiality and forecast judgments that cannot be resolved through a generic example. Entities should obtain the complete debt documents, reconcile liabilities, involve treasury and legal teams, and seek advice from their statutory auditor, chartered accountant and qualified legal counsel before approving classification, entries, disclosures or communications. They should also check later MCA notifications and ICAI material immediately before finalising financial statements. TaxGuru accepts no responsibility or liability for any misclassification, audit modification, covenant consequence, lender action, regulatory issue, restatement, going-concern impact or loss arising from reliance on this article, incomplete documents, later amendments or differences between the general discussion and an entity’s actual arrangements.
