Ind AS 116 Lease Accounting

The Problem

For a mid-market company operating 50 or more lease agreements — office premises, warehouses, vehicles, and equipment — the manual Ind AS 116 accounting cycle typically consumes three to five working days every quarter. A finance team must open each PDF lease agreement, transcribe commencement dates, lease terms, payment schedules, and renewal clauses into a spreadsheet model, then build or update a present-value amortisation table for every right-of-use (ROU) asset and corresponding lease liability. With agreements ranging from a straightforward equipment hire to a multi-component warehouse arrangement with embedded racking, the transcription step alone introduces material keying errors before any accounting judgement is applied.

Ind AS 116, Leases, which replaced the earlier Ind AS 17 for reporting periods beginning on or after 1 April 2019, requires lessees to recognise a ROU asset and a lease liability for virtually all leases, measured at the present value of future lease payments discounted at the incremental borrowing rate (IBR) or the rate implicit in the lease. The standard's paragraphs 19, 26, 42, and 44 introduce judgement points — renewal option assessment, IBR selection, index-linked re-measurement, and lease-modification classification — that cannot be handled by a static spreadsheet without a documented, auditable rationale for each.

At scale, the failure modes multiply. A renewal agreement filed as a modification rather than a separate new lease (Ind AS 116 paragraph 44) misstates the opening balance of both the ROU asset and the liability. An undocumented IBR means the present-value calculation cannot be independently verified by an auditor. Index-linked rent clauses left at the original rate produce an understated liability the moment the Consumer Price Index resets. Mid-market controllers running these schedules in Excel across 50–500 lease records report restatement risk at every annual close.

The Cadel Ind AS 116 Lease Accounting workflow processes lease agreements — including lessor information and property documents — extracts the relevant contractual terms, applies the standard's recognition and measurement rules, and produces a complete, audit-ready ROU asset and lease liability schedule without manual data entry.

Why It Matters: Context

Ind AS 116 is India's adoption of IFRS 16 and is mandatory for all companies reporting under Indian Accounting Standards. The Institute of Chartered Accountants of India (ICAI) has issued educational material clarifying that the standard applies to all leases except short-term leases (term of 12 months or less at commencement, per paragraph 5(a)) and leases of low-value assets (paragraph 5(b)), provided the lessee elects those exemptions on a lease-by-lease or class basis. The initial measurement of the lease liability under paragraph 26 requires discounting future payments at the rate implicit in the lease or, where that rate cannot be readily determined, the lessee's IBR — a rate that must be documented and supportable at the commencement date. The ROU asset is then measured at cost, comprising the initial lease liability, any initial direct costs, prepayments, and restoration obligations per paragraph 24.

For mid-market companies with no dedicated lease-accounting system, the practical challenge is that each of these inputs lives in a different place: the payment schedule is in the lease agreement PDF, the IBR is in a treasury memo or a prior borrowing record, and the index-rate adjustment is triggered by an external RBI or Labour Bureau notification that finance teams must monitor independently. When a single portfolio contains a mixture of property leases (e.g., Gupta Logistics Hub, Nair Business Park Unit D3), equipment leases (e.g., Kumar Office Solutions equipment), and renewal agreements (e.g., Sunrise Plaza Renewal), the number of interdependent schedules that must stay synchronised across quarters grows faster than any spreadsheet-based process can reliably handle.

The consequences of non-compliance or computational error are direct and quantifiable. An auditor conducting procedures under SA 500 Audit Evidence and SA 540 Auditing Accounting Estimates who finds that the IBR was not documented, that a renewal was classified as a modification rather than a new lease, or that index-linked payments were not re-measured will raise an audit qualification or require a prior-period restatement. Under Schedule III of the Companies Act 2013, ROU assets and lease liabilities must be disclosed separately in the balance sheet; an error in the underlying schedule therefore flows directly into a statutory disclosure error.

What This Workflow Automates

1. Document ingestion: The workflow accepts uploaded PDFs classified as Lease Agreement, Lessor, or Property documents and routes each file to the appropriate extraction model without manual sorting.
2. Key-term extraction: From each lease agreement, the workflow extracts commencement date, lease term, payment amounts and frequency, renewal option clauses, variable/index-linked payment terms, asset description, and any stated implicit interest rate.
3. Exemption eligibility check: The workflow computes the remaining lease term from the extracted commencement and expiry dates, compares the asset description against a configurable low-value threshold, and either applies the short-term or low-value exemption under Ind AS 116 paragraph 5 or proceeds to full recognition — recording the determination and its rationale.
4. Renewal and modification classification: The workflow scans document titles and extracted terms for renewal indicators or scope-change language; where paragraph 44 criteria are met (new right-of-use asset at a stand-alone price), it classifies the event as a new lease and opens a fresh ROU asset and liability schedule dated from the modification effective date rather than treating it as a modification of the original.
5. Component separation: Where a single agreement contains multiple distinct lease components (e.g., warehouse space plus integrated racking), the workflow identifies each component from the asset description, allocates consideration on a relative stand-alone price basis, or records the practical expedient election under Ind AS 116 paragraph 15, and produces a separate amortisation schedule per component.
6. IBR validation and present-value calculation: If no implicit rate is stated in the agreement, the workflow surfaces an IBR input field pre-populated with the lessee's most recently recorded borrowing rate, blocks finalisation until a rate is confirmed, records the chosen rate and justification in the audit trail, and then computes the present value of future lease payments to produce the opening lease liability balance under paragraph 26.
7. ROU asset and liability schedule generation: The workflow outputs a full amortisation table showing the opening ROU asset cost, periodic depreciation, interest expense on the lease liability, cash payment allocation, and closing balances — together with a re-measurement trigger record for any index-linked payment component requiring update when the reference index changes per paragraph 42.

All seven steps execute within seconds of document upload, producing deterministic, field-level outputs that every controller or auditor can trace back to the source clause in the lease agreement.

Edge Cases We Simulate

The workflow ships with a battery of synthetic test scenarios that exercise every failure mode we have seen in real-world data. Each scenario produces a deterministic outcome that an auditor or controller can verify in seconds.

Sample Documents

Download or inspect the seeded sample files used to demonstrate this workflow:

Sample Results

In the demo dataset, the workflow processed four lease agreement files covering a mix of agreement types: an equipment lease (Kumar Office Solutions), a logistics hub property lease (Gupta Logistics Hub), a renewal agreement (Sunrise Plaza Renewal), and a multi-unit commercial lease (Nair Business Park Unit D3). All four documents were correctly classified as Lease Agreement type at ingestion. The reconciliation layer identified four source-to-target pairings across the document set, confirming cross-referencing between lease agreements and supporting lessor or property documents. Extraction covered contractual fields including commencement dates, payment schedules, lease terms, renewal clauses, and asset descriptions, providing the input set required for ROU asset recognition and liability discounting under Ind AS 116 paragraphs 24 and 26.

A notable exception caught during processing involved the Sunrise Plaza Renewal document: the workflow detected the word Renewal in the document title and identified scope-expansion language in the extracted terms, triggering classification as a new lease under Ind AS 116 paragraph 44 rather than a modification of the original agreement. This prevented the common error of carrying forward an understated opening liability balance from the original lease commencement date. Similarly, the Nair Business Park Unit D3 agreement was flagged for potential multiple lease component separation after the asset description referenced integrated warehouse racking alongside the unit space, prompting the preparer to confirm whether to allocate consideration by component or elect the practical expedient under paragraph 15.

Why Automation Wins Here

By replacing manual PDF transcription and spreadsheet modelling with structured extraction and rule-based classification, the Cadel Ind AS 116 Lease Accounting workflow reduces what typically takes a mid-market finance team three to five days per quarter to a process completable in minutes per lease agreement. The six deterministic validation checks — exemption eligibility, renewal classification, component separation, IBR documentation, index-linked re-measurement triggers, and present-value computation — eliminate the four most common sources of restatement risk in Ind AS 116 portfolios: misclassified renewals, undocumented IBRs, unadjusted index-linked payments, and missing component schedules. Error rates in manual Ind AS 116 schedules across mid-market portfolios of 50–200 leases have been documented by ICAI educational guidance as a leading cause of audit qualification on lease disclosures; automated extraction addresses the root cause at the data-entry stage rather than at review.

Every output produced by the workflow — the extracted term sheet, the exemption determination, the IBR record with its justification, the component allocation, and the full amortisation schedule — is stored as a versioned artifact with a direct link back to the source document clause. The controller or auditor can attach this artifact directly to the Ind AS 116 workpaper in the audit file, satisfying the documentation requirements under SA 230 Audit Documentation and supporting the Schedule III balance sheet disclosures without any further manual compilation.

Frequently Asked Questions