
After commencement, lease accounting becomes a coordinated roll-forward of the lease liability and the right-of-use asset. The liability generally accretes interest and reduces for payments, while the right-of-use asset is depreciated and adjusted for specified remeasurements or impairment. Operationalising the requirement requires clear ownership, stable data, documented judgements and a link between the technical conclusion and the amounts presented in the financial statements. Portfolio errors often arise because liability and asset schedules are maintained separately without controlled linkage. A robust approach connects commercial substance, the Ind AS 116 decision criteria, measurement evidence and presentation consequences in one coherent file.
Accrete the liability using the effective rate
The principle. Interest on the lease liability is recognised so as to produce a periodic rate on the remaining balance, while payments reduce the liability according to the schedule. For a review-ready file, the lease subledger should separate interest and principal automatically and reconcile cash payments to contractual due dates. The risk to avoid is treating the full rental payment as lease expense after recognition of the balance-sheet model. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.
Depreciate the ROU asset systematically
The technical anchor. The right-of-use asset is depreciated over the appropriate period based on whether ownership transfers or a purchase option is reasonably certain, otherwise generally over the shorter of useful life and lease term. In application, fixed-asset and lease systems should use the same commencement date and approved term assumptions. A frequent failure mode is using lease-liability maturity as the depreciation period without checking ownership or purchase-option conclusions. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.
Recognise impairment where applicable
The accounting logic. Right-of-use assets are subject to the impairment requirements of Ind AS 36 rather than being protected from impairment by the existence of a lease liability. Operationally, CGU assessments should include ROU assets consistently with how lease cash flows are treated in recoverable-amount calculations. The main judgement risk is assuming a lease asset cannot be impaired because future payments remain payable. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.
Remeasure for specified changes
The decision point. Changes in lease term, purchase-option assessment or certain payment variables can trigger remeasurement of the lease liability with corresponding ROU asset adjustment, subject to the detailed requirements. For implementation, systems should distinguish remeasurement events from simple payment processing or lease modifications. Where errors often arise is remeasuring every index change using a new discount rate even when the standard requires the existing rate. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.
Reconcile balance-sheet and expense movements
The core requirement. Closing liability, ROU asset, depreciation, interest, payments, remeasurements and modifications should form one integrated bridge. In a controlled close process, portfolio controls should detect negative liabilities, expired leases with balances, duplicate payments and unposted remeasurements. A common weakness is allowing spreadsheet schedules and general ledger balances to drift apart. Where the conclusion is sensitive to a contractual clause or estimate, the file should show the alternative outcome and why the selected treatment is more appropriate.
Practical illustration
Consider an office lease whose rentals are linked to a consumer price index. When the cash flows change because the index changes, the lessee updates the lease liability using the applicable remeasurement mechanics and adjusts the ROU asset. That event is different from a negotiated change in leased area, which may be a lease modification requiring a different analysis. The illustration is deliberately simplified: its purpose is to show how the accounting conclusion follows the underlying facts rather than to prescribe a single mechanical answer for every entity. Before posting an entry, the preparer should reconcile contractual terms, management's commercial intent, relevant estimates and system data to the specific accounting requirement. Where the outcome is sensitive, the file should show the key judgement and explain why the selected assumption is reasonable at the reporting date.
Documentation and control points
Professional application depends as much on process quality as technical knowledge. For this topic, a minimum control set should cover subledger roll-forward; interest-principal split; ROU depreciation controls; remeasurement triggers; and ledger reconciliation. Ownership should be clear between the business, finance and any legal, tax, valuation, credit-risk or other specialists whose evidence is required. Source data should be dated and version-controlled; manual adjustments should show preparer, reviewer, rationale and approval. The final accounting memorandum should connect the conclusion to the general ledger or relevant subledger, presentation and disclosures. If facts or estimates change, the entity should reassess the conclusion when required and preserve an audit trail explaining the change.
Closing perspective
Subsequent lease accounting is reliable when every movement has a defined event type and both sides of the lease balance sheet move in a controlled way. The most useful way to apply Ind AS 116 is to treat the requirement as a decision framework rather than a compliance slogan. When the facts, accounting criteria, measurement evidence, controls and disclosure implications are considered together, the result is more consistent across reporting periods and easier to explain to management, auditors and users of the financial statements.
Continue learning on JUMOQ
Turn this guidance into practical capability
Explore focused courses, worked examples and activities related to this topic.
Explore related courses →References
- Ind AS 116, Leases — ICAI Compendium of Indian Accounting Standards 2025-2026
