Commercial terms
Lessor, agreement, invoice, tenure, payment frequency, timing, broken periods, deposits and options.
The operating question
Ind AS records depend on decisions and evidence outside the accounting schedule.
Lease identification, commencement, payment structure, discount-rate policy, modifications and end-term options require controlled inputs. For equipment portfolios, those inputs also need to remain connected to receipt and asset reality.
Is the source lease population complete?
Who approves commencement, IBR and other policy inputs?
How do payments and modifications flow into the record?
Can finance reconcile contract and asset-level information?
Connected workflow
An India-first lease accounting support workflow
- 01
Collect
Capture the agreement, invoice, rental structure, dates, options, deposits and asset references.
- 02
Evidence
Connect receipt, GRN, acceptance, serial number, location and supporting documents.
- 03
Approve inputs
Finance confirms policy decisions and calculation inputs.
- 04
Maintain records
Generate and retain configured liability, ROU, payment and expense records.
- 05
Review changes
Control payments, reconciliations, modifications, period actions and end-term events.
Connected records
What stays connected
Accounting inputs
Commencement, approved discount rate, useful-life inputs and customer policy decisions.
Indian invoice data
Billing entity, GSTIN, billing and delivery states, CGST, SGST or IGST fields as supplied and reviewed.
Periodic schedules
Lease liability, interest, principal reduction, ROU depreciation, payment and expense records.
Asset evidence
Serial or ERP number, GRN, location, custody, condition, movement and verification.
Control evidence
Approvals, calculation versions, exceptions, reconciliations, source documents and review history.
Illustrative example
Quarterly rentals with first and last broken periods
An Indian equipment arrangement may include quarterly rental dates, first and last broken periods, a refundable deposit and a final balloon or buyout term. ServiceTiket retains the inputs and configured schedules; finance approves the treatment.
The illustration intentionally contains no tax conclusion or numerical accounting result.
FrequencyQuarterly
Partial periodsFirst and last broken
EvidenceInvoice, GRN, asset ID
ReviewFinance-approved policy
Business value
What the organisation gains
India-specific clarity
Use the vocabulary and source data Indian finance and operations teams already manage.
Operational connection
Keep lease-accounting support tied to asset receipt, placement, movement and verification.
Controlled review
Make policy inputs, changes, approvals and reconciliation evidence visible.
Scope and responsibility
What the platform supports—and what people decide
ServiceTiket maintains configured records, schedules, approvals and evidence. The organisation and its advisers remain responsible for accounting policy, treatment, review and compliance.
Ind AS 116 is the primary accounting context for the India offering. IFRS 16 or ASC 842 requirements are assessed separately where group reporting requires them.
Calculations, reports, integrations and controls are confirmed during discovery and testing before they are included in an implementation scope.
Continue exploring LeaseOps
A useful first conversation
Map one real asset from contract to field reality
Bring an anonymised lease schedule, asset register, or workflow. We will map where the records separate and what a controlled process could look like.
Request an Ind AS workflow review