Ind AS 116
The primary accounting context for ServiceTiket’s India-first commercial motion.
The operating question
A three-standard logo list does not explain the required system behaviour.
The useful discovery questions concern books, entities, policies, calculations, journals, disclosures, controls and the events that must be processed differently. These must be documented before the product is described as supporting a specific implementation.
Which entities report under which standard?
Are parallel books required for the same lease population?
Which policy elections and exemptions have been approved?
What journals, disclosures and controls must the system produce?
Connected workflow
Start with the reporting requirement, then configure the records
- 01
Map entities
Identify legal entities, reporting groups, currencies, calendars and source systems.
- 02
Confirm standards
Document Ind AS 116, IFRS 16 or ASC 842 obligations with qualified reviewers.
- 03
Define policies
Record elections, discount-rate methods, materiality and event treatment.
- 04
Test scenarios
Validate initial, periodic, modification and end-term calculations and controls.
- 05
Approve outputs
Reconcile reports, journals, disclosures and audit evidence.
Connected records
What stays connected
IFRS 16
Relevant where an organisation reports under IFRS or submits information to an IFRS-reporting group.
ASC 842
Relevant where an organisation or group reports under US GAAP.
Parallel reporting
May require separate books, calculations, classifications, journals or disclosures for the same contracts.
Policy ownership
Belongs to the reporting organisation and its qualified finance and audit advisers.
System validation
Requires documented test cases, reconciled outputs, controlled changes and clearly stated exclusions.
Illustrative example
An Indian subsidiary in an international group
The Indian entity may maintain Ind AS reporting while the parent requests a group-reporting package under another standard. Discovery must establish whether one approved output, a reconciliation or parallel books are required.
The example describes a discovery scenario, not a statement that every multinational requires parallel accounting.
Local contextInd AS 116
Group contextIFRS or US GAAP
Design questionReconciliation or parallel book
ApprovalGroup finance policy
Practical comparison
Use each standard in its proper context
This table is deliberately high level. Detailed differences and accounting conclusions require qualified review.
| Context | Primary use | System discovery focus | ServiceTiket message |
|---|---|---|---|
| Ind AS 116 | Indian entities applying Ind AS | India-specific policies, entity structure, schedules, journals and disclosures | Primary India accounting-support context |
| IFRS 16 | Entities or groups reporting under IFRS | Group policy, local-to-group reporting, currency, calendar and consolidation needs | Assessed where international group reporting requires it |
| ASC 842 | Entities or groups reporting under US GAAP | Classification, expense pattern, books, journals and disclosure requirements | Assessed only for an explicit US GAAP requirement |
Business value
What the organisation gains
Accurate scoping
Avoid promising three standards when the customer needs one carefully implemented reporting model.
Fewer surprises
Surface entity, currency, calendar, journal and disclosure differences before configuration.
Defensible claims
Describe only the standards and system behaviours that have passed documented validation.
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.
Map your reporting requirements