Ind AS 115 — Revenue from Contracts with Customers

Ind AS 115 is the single, comprehensive standard for recognising revenue from contracts with customers under Ind AS. It replaced the older, more fragmented revenue guidance with one principle-based five-step model that applies to virtually all customer contracts — goods, services, and construction alike. For any business, revenue is the headline number, and Ind AS 115 is among the most important and most far-reaching of the Ind AS standards.

Objective and the core principle

The objective is to establish the principles that an entity applies to report useful information about the nature, amount, timing, and uncertainty of revenue and cash flows arising from a contract with a customer. The core principle is that an entity recognises revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. Everything in the standard flows from that principle, operationalised through the five steps.

The five-step model

Step 1 — Identify the contract with the customer. A contract is an agreement creating enforceable rights and obligations. It is within scope only when criteria are met: the parties have approved it and are committed to perform, each party's rights and the payment terms can be identified, the contract has commercial substance, and it is probable the entity will collect the consideration it is entitled to.

Step 2 — Identify the performance obligations in the contract. A performance obligation is a promise to transfer a distinct good or service (or a series of substantially the same distinct goods or services). A good or service is distinct if the customer can benefit from it on its own or with readily available resources, and it is separately identifiable from other promises in the contract. A single contract may contain several performance obligations (for example, a piece of equipment plus installation plus a maintenance service), each of which is accounted for separately.

Step 3 — Determine the transaction price. The transaction price is the amount of consideration the entity expects to be entitled to in exchange for transferring the promised goods or services. It includes the effects of variable consideration (discounts, rebates, refunds, performance bonuses, penalties — estimated and constrained so that a significant revenue reversal is not probable), any significant financing component (where the timing of payments gives the customer or entity a financing benefit, the price is adjusted for the time value of money), non-cash consideration, and consideration payable to the customer.

Step 4 — Allocate the transaction price to the performance obligations. The transaction price is allocated to each performance obligation in proportion to the stand-alone selling prices of the distinct goods or services. Where a stand-alone selling price is not directly observable, it is estimated. Discounts are generally allocated proportionately across performance obligations (with exceptions where a discount relates to specific obligations).

Step 5 — Recognise revenue when (or as) the entity satisfies a performance obligation. Revenue is recognised when control of the good or service transfers to the customer. This happens either over time or at a point in time. A performance obligation is satisfied over time if one of three criteria is met (the customer simultaneously receives and consumes the benefits as the entity performs; the entity's performance creates or enhances an asset the customer controls; or the entity's performance does not create an asset with alternative use and the entity has an enforceable right to payment for performance completed to date). If none is met, control transfers at a point in time, and revenue is recognised at that point. For over-time recognition, progress is measured using output or input methods.

Contract costs and presentation

Ind AS 115 also addresses certain contract costs — the incremental costs of obtaining a contract (such as sales commissions) are capitalised if expected to be recovered, and costs to fulfil a contract are capitalised where they meet specified criteria, then amortised consistently with the transfer of the goods or services. Contracts are presented on the balance sheet as contract assets or contract liabilities depending on the relationship between performance and payment (for example, a contract liability arises where the customer pays in advance of performance).

Disclosure

Disclosures are extensive — disaggregation of revenue into categories depicting how the nature, amount, timing, and uncertainty of revenue and cash flows are affected by economic factors; information about contract balances; information about performance obligations (including when they are typically satisfied and significant payment terms); and the significant judgements made in applying the standard.

A full worked example

Let's apply the five-step model to a real contract. A software company signs a ₹12,00,000 deal with a customer for: (a) a perpetual software licence, (b) one year of technical support, and (c) a one-off installation service. Sold separately, the standalone prices would be licence ₹9,00,000, support ₹3,00,000, installation ₹1,50,000 — totalling ₹13,50,000. The customer pays ₹12,00,000, a bundled discount.

Steps 1–2 — Identify the contract and the performance obligations. There is one contract with three distinct performance obligations: the licence, the support, and the installation. Each is capable of being distinct and is separately identifiable.

Step 3 — Determine the transaction price. ₹12,00,000.

Step 4 — Allocate the price to each obligation in proportion to standalone selling prices. The ₹1,50,000 discount is spread across all three.

Obligation	Standalone price (₹)	% of total	Allocated price (₹)
Software licence	9,00,000	66.7%	8,00,000
Technical support	3,00,000	22.2%	2,66,667
Installation	1,50,000	11.1%	1,33,333
Total	13,50,000	100%	12,00,000

Step 5 — Recognise revenue as each obligation is satisfied. The timing differs by obligation:

Obligation	When control transfers	Revenue recognition
Licence (₹8,00,000)	At a point in time (on delivery)	Recognised immediately
Installation (₹1,33,333)	At a point in time (on completion)	Recognised when installed
Support (₹2,66,667)	Over time (12 months)	₹22,222 per month over the year

The journal entry on day one, assuming the licence is delivered and installation completed, with the full ₹12,00,000 received in cash:

Account	Debit (₹)	Credit (₹)
Bank	12,00,000
Revenue — licence		8,00,000
Revenue — installation		1,33,333
Contract liability (deferred support revenue)		2,66,667

The crucial insight the five-step model forces out: even though the customer paid ₹12,00,000 up front, the company cannot book it all as revenue on day one. Only ₹9,33,333 is earned immediately; the ₹2,66,667 of support sits as a contract liability and is released to revenue at ₹22,222 a month as the service is delivered. Getting this allocation wrong — recognising bundled revenue too early — is the most common Ind AS 115 error, and the one auditors look for first.

How Ind AS 115 compares with AS 9 and AS 7

This is a major framework difference. Under the AS framework, revenue is governed by the short, principle-based AS 9 (timing of recognition for sale of goods, services, and interest/royalties/dividends), and construction contracts by AS 7 (percentage of completion). Ind AS 115 replaces both with a single five-step model covering all customer contracts. The practical consequences are significant for complex arrangements: bundled goods and services must be unbundled into separate performance obligations with the price allocated by stand-alone selling price; variable consideration must be estimated and constrained; significant financing components must be separated out; and the over-time/point-in-time analysis replaces both the AS 9 risks-and-rewards test and the AS 7 percentage-of-completion method. Simple cash sales are recognised similarly under both frameworks, but multi-element, variable, or long-term contracts can be recognised quite differently.

Common pitfalls

Frequent issues include failing to identify all distinct performance obligations in a bundled contract; not estimating and constraining variable consideration appropriately; overlooking a significant financing component in extended payment terms; allocating the transaction price other than by stand-alone selling prices; and recognising revenue over time without meeting one of the three criteria (or vice versa).

Why this is cleaner on a unified system

Applying the five-step model reliably depends on capturing contract terms, performance milestones, billing, and collections in a connected way — far easier when sales, delivery, billing, and the ledger sit in one system. When the data needed to identify performance obligations, allocate the transaction price, and recognise revenue as control transfers comes from a single source of truth, applying Ind AS 115 consistently and producing its detailed disclosures is more manageable than reconciling contract records against accounting entries held in separate tools.

This article is a detailed educational summary of Ind AS 115 in plain language. It is not a substitute for the full text of the standard. Accounting standards are amended from time to time; always verify the current, authoritative text of Ind AS 115 as notified under the Companies Act before relying on it, and consult a qualified chartered accountant for application to your specific circumstances.