Ind AS 115 Revenue Recognition: Practical Guide for CFOs

Introduction: Why Ind AS 115 Matters for CFOs

Ind AS 115 — Revenue from Contracts with Customers — replaced a range of legacy guidance to create a single, principle‑based model for revenue recognition. For companies operating in India, accurate application of Ind AS 115 is critical not only for compliant financial reporting but also for communicating predictable and comparable results to investors, lenders, and other stakeholders.

CFOs, controllers, and finance leaders must align commercial terms, ERP controls, and accounting judgments with the five‑step model to avoid restatements, unexpected tax consequences, or misaligned performance metrics. This guide explains the objective, scope, five-step model, practical implications, and implementation challenges of Ind AS 115 along with a simple illustration relevant to Indian companies.

What Is the Objective of Ind AS 115?

The objective of Ind AS 115 is to establish principles for reporting useful information about the nature, amount, timing and uncertainty of revenue and cash flows arising from contracts with customers.

In simple terms, the standard requires entities to recognise revenue in a manner that reflects the transfer of promised goods or services to customers in an amount that represents the consideration to which the entity expects to be entitled. This approach ensures that financial statements provide meaningful insights into a company’s revenue generation and performance.

Scope of Ind AS 115

Ind AS 115 applies to most contracts with customers across industries, including contracts for sale of goods, services, construction activities, and licensing arrangements.

However, certain contracts are outside its scope. These include:

• Lease contracts accounted for under Ind AS 116
• Insurance contracts
• Financial instruments and contractual rights covered under other standards
• Certain non‑monetary exchanges between entities in the same line of business

For most Indian companies preparing financial statements under Indian Accounting Standards, Ind AS 115 is the primary framework governing revenue recognition.

Five-Step Revenue Recognition Model

Ind AS 115 introduces a five‑step model for recognising revenue:

Step 1 – Identify the contract with the customer A contract exists when parties approve the agreement, rights and payment terms are identifiable, and collection is probable.

Step 2 – Identify performance obligations Performance obligations are distinct goods or services promised to the customer.

Step 3 – Determine the transaction price The transaction price is the amount of consideration the entity expects to receive, including estimates of variable consideration such as discounts, rebates, penalties, or bonuses.

Step 4 – Allocate the transaction price The transaction price is allocated to each performance obligation based on their relative standalone selling prices.

Step 5 – Recognise revenue when the obligation is satisfied Revenue is recognised either at a point in time or over time depending on when control of the goods or services transfers to the customer.

These principles create a consistent framework for revenue recognition across industries.

Practical Implications for CFOs and Finance Teams

For CFOs and finance teams in India, Ind AS 115 affects several operational and financial reporting areas.

Contract structures may need to be revisited, particularly where goods and services are bundled together. Revenue may need to be split across multiple performance obligations rather than recognised upfront.

ERP and billing systems may require changes to track performance obligations, allocate transaction prices, and automate revenue recognition.

Financial planning and analysis may also be impacted because the timing of revenue recognition may differ from billing schedules or cash collections.

In addition, companies must ensure strong documentation and internal controls to support judgments made under the standard.

Common Challenges in Ind AS 115 Implementation

Many companies face practical challenges when implementing Ind AS 115.

Identifying distinct performance obligations can be complex, especially in bundled contracts involving multiple deliverables.

Estimating variable consideration requires judgment and careful application of constraints to prevent over‑recognition of revenue.

Determining standalone selling prices can also be challenging when observable market prices are not available.

Another common issue is accounting for contract modifications or change orders, particularly in long‑term construction or service arrangements.

Finally, companies often struggle with data availability and system limitations, making the implementation process more resource‑intensive than expected.

Illustration: Revenue Allocation Under Ind AS 115

Consider an equipment manufacturer that sells machinery along with two years of maintenance services.

The contract price is INR 1,000,000. The standalone selling price of the equipment is INR 800,000 and maintenance services are valued at INR 200,000.

Under Ind AS 115, the company identifies two performance obligations: delivery of equipment and maintenance services.

The transaction price of INR 1,000,000 is allocated based on relative standalone selling prices. Accordingly, INR 800,000 is allocated to equipment and INR 200,000 to maintenance.

Revenue for the equipment is recognised when control transfers to the customer, typically upon delivery and installation.

Revenue for maintenance services is recognised over time during the two‑year service period.

Disclosure Requirements Under Ind AS 115

Ind AS 115 requires detailed disclosures that help users understand the nature and timing of revenue.

Companies must disclose disaggregated revenue information, contract balances such as receivables and contract liabilities, and details about performance obligations.

They must also explain significant judgments used in determining transaction prices and allocating revenue to performance obligations.

Information about remaining performance obligations and expected timing of revenue recognition must also be disclosed where relevant.

How Nexdigm Can Help

Implementing Ind AS 115 often requires a combination of technical accounting expertise, process redesign, and system improvements.

Nexdigm’s CFO Services team supports companies through Ind AS implementation by reviewing customer contracts, identifying performance obligations, designing revenue recognition policies, and assisting with accounting documentation.

We also help organizations enhance internal controls, align financial reporting processes, and prepare robust disclosures that meet regulatory expectations.

Our approach combines deep technical knowledge with practical business insights to help companies achieve effective Ind AS compliance.