Overview of Ind AS 115, Revenue from Contracts with Customers

Indian Accounting Standard 115, Revenue from Contracts with Customers

The objective of Ind AS 115 is to establish the principles that an entity shall apply to report useful information to users of financial statements about the nature, amount, timing and uncertainty of revenue and cash flows arising from a contract with a customer.


The Standard applies to all contracts with customers, except the lease contracts within the scope of Ind AS 116, Leases; insurance contracts within the scope of Ind AS 104, Insurance Contracts; financial instruments and other contractual rights or obligations within the scope of Ind AS 109, Financial Instruments, Ind AS 110, Consolidated Financial Statements, Ind AS 111, Joint Arrangements, Ind AS 27, Separate Financial Statements and Ind AS 28, Investments in Associates and Joint Ventures; and non-monetary exchanges between entities in the same line of business to facilitate sales to customers or potential customers.

The core principle of Ind AS 115 is that an entity recognises revenue in the way that depicts the transfer of promised goods or services to customers at an amount that reflects the consideration to which the entity expects to be entitled in exchange for those goods or services. Revenue shall be recognised by an entity in accordance with this core principle by applying the following five steps:

1. Identifying contract with a customer: This Standard defines a ‘contract’ and a ‘customer’ and specifies five mandatory criteria to be met for identification of a contract.

2. Identify performance obligations in contract: At contract inception, an entity shall assess the goods or services promised in a contract with a customer and shall identify as a performance obligation each promise to transfer to the customer either:

(a) a good or service (or a bundle of goods or services) that is distinct – in other words
— the customer can benefit from the good or service either on its own or together with other resources that are readily available to the customer; and
— the entity’s promise to transfer the good or service to the customer is separately identifiable from other goods or services in the contract; or

(b) a series of distinct goods or services that are substantially the same and that have the same pattern of transfer to the customer.

3. Determine transaction price: This Standard uses transaction price approach instead of fair value approach in Ind AS 18 while determining amount of consideration. The transaction price is the amount of consideration to which an entity expects to be entitled in exchange for transferring promised goods or services to a customer, excluding amounts collected on behalf of third parties (for example, some sales taxes). The consideration promised may include fixed amounts, variable amounts, or both. If the consideration promised in a contract includes a variable amount, an entity shall estimate the amount of consideration to which the entity will be entitled in exchange for transferring the promised goods or services to a customer. Variable consideration is included in transaction price only to the extent that it is highly probable that a significant reversal in the amount of cumulative revenue recognised will not occur when the uncertainty associated with the variable consideration is subsequently resolved, The estimate of variable consideration can be determined by using either the expected value method or the most likely amount method. The transaction price is also adjusted for the effects of the time value of money if the contract includes a significant financing component and for any consideration payable to the customer.

Sales and usage-based royalties arising from licences of intellectual property are excluded from the transaction price and are recognised only when (or as) the later of the following events occurs:

(a) the subsequent sale or usage occurs; and

(b) the performance obligation to which some or all of the salesbased or usage-based royalty has been allocated has been satisfied (or partially satisfied).

4. Allocate the transaction price to the performance obligations in the contract: An entity typically allocates the transaction price to each performance obligation on the basis of the relative stand-alone selling prices of each distinct good or service promised in the contract. If a stand-alone selling price is not observable, an entity estimates it. Sometimes, the transaction price includes a discount or a variable amount of consideration that relates entirely to a part of the contract. The requirements specify when an entity allocates the discount or variable consideration to one or more, but not all, performance obligations in the contract. Any subsequent changes in the transaction price shall be allocated to the performance obligations on the same basis as at contract inception. Amounts allocated to a satisfied performance obligation shall be recognised as revenue, or as a reduction of revenue, in the period in which the transaction price changes.

5. Recognise revenue when the entity satisfies a performance obligation: An entity recognises revenue when it satisfies a performance obligation by transferring a promised good or service to a customer (which is when the customer obtains control of that good or service). The amount of revenue recognised is the amount allocated to the satisfied performance obligation. A performance obligation may be satisfied at a point in time or over time. An entity transfers control of a good or service over time and, therefore, satisfies a performance obligation and recognises revenue over time, if one of the following criteria is met:

— The customer simultaneously receives and consumes the benefits provided by the entity’s performance as the entity performs.

— The entity’s performance creates or enhances an asset that the customer controls as the asset is created or enhanced.

— The entity’s performance does not create an asset with an alternative use to the entity and the entity has an enforceable right to payment for performance completed to date.

If an entity does not satisfy a performance obligation over time, the performance obligation is satisfied at a point in time. For performance obligations satisfied over time, an entity recognises revenue over time by selecting an appropriate method (output methods and input methods) for measuring the entity’s progress towards complete satisfaction of that performance obligation.

Treatment of Contract Costs

Ind AS 115 specifies the following requirements for contract costs:

1. Incremental costs of obtaining a contract: Those costs that an entity incurs to obtain a contract with a customer that it would not have incurred if the contract had not been obtained. An entity shall recognise these costs as an asset if the entity expects to recover those costs. Costs to obtain a contract that would have been incurred regardless of whether the contract was obtained shall be recognised as an expense when incurred, unless those costs are explicitly chargeable to the customer regardless of whether the contract is obtained.

2. Costs to fulfil a contract: If costs incurred in fulfilling a contract are not within scope of another Standard, entity shall recognise an asset from the costs incurred to fulfil a contract only if some specified criteria are met. If costs incurred in fulfilling a contract are within scope of another Standard, entity shall account for those costs in accordance with those other Standards.

Contract costs recognised as an asset shall be amortised on a systematic basis that is consistent with the transfer to the customer of the goods or services to which the asset relates.

An impairment loss shall be recognised in profit or loss to the extent that the carrying amount of contract costs recognised as an asset exceeds the remaining amount of consideration that the entity expects to receive in exchange for the goods or services to which the asset relates after deducting the costs that relate directly to providing those goods or services and that have not been recognised as expenses.


When either party to a contract has performed, an entity shall present the contract in the balance sheet as a contract asset or a contract liability, depending on the relationship between the entity’s performance and the customer’s payment. An entity shall present any unconditional rights to consideration separately as a receivable.

Sale with a right of return

To account for the transfer of products with a right of return (and for some services that are provided subject to a refund), an entity shall recognise all of the following:

  • revenue for the transferred products in the amount of consideration to which the entity expects to be entitled (therefore, revenue would not be recognised for the products expected to be returned);
  • a refund liability; and
  • an asset (and corresponding adjustment to cost of sales) for its right to recover products from customers on settling the refund liability.


If customer has the option to purchase warranty separately, the warranty is a distinct service because the entity promises to provide the service to the customer in addition to the product that has the functionality described in the contract. In that case, entity shall account for the promised warranty as a performance obligation and allocate a portion of the transaction price to that performance obligation. If the warranty cannot be purchased separately, an entity shall account for the warranty in accordance with Ind AS 37 Provisions, Contingent Liabilities and Contingent Liabilities.

Principal versus agent considerations

When another party is involved in providing goods or services to a customer, the entity shall determine whether the nature of its promise is a performance obligation to provide the specified goods or services itself (i.e. the entity is a principal) or to arrange for those goods or services to be provided by the other party (i.e. the entity is an agent). An entity determines whether it is a principal or an agent for each specified good or service promised to the customer. Indicators that an entity controls the specified good or service before it is transferred to the customer (and is therefore a principal include, but are not limited to, the following:

(a) the entity is primarily responsible for fulfilling the promise to provide the specified good or service

(b) the entity has inventory risk before the specified good or service has been transferred to a customer or after transfer of control to the customer (for example, if the customer has a right of return)

(c) the entity has discretion in establishing the price for the specified good or service.


To disclose sufficient information to enable users of financial statements to understand the nature, amount, timing and uncertainty of revenue and cash flows arising from contracts with customers, an entity shall disclose qualitative and quantitative information about all of the following:

(a) its contracts with customers;

(b) the significant judgements, and changes in the judgements, made in applying this Standard to those contracts; and

(c) any assets recognised from the costs to obtain or fulfil a contract with a customer.

Service concession arrangements

Appendix D of Ind AS 115 gives guidance on the accounting by operators for public-to-private service concession arrangements. This Appendix applies to both (a) infrastructure that the operator constructs or acquires from a third party for the purpose of the service arrangement; and (b) existing infrastructure to which the grantor gives the operator access for the purpose of the service arrangement. Infrastructure within the scope of this Appendix shall not be recognised as property, plant and equipment of the operator because the contractual service arrangement does not convey the right to control the use of the public service infrastructure to the operator.


An entity may transition to Ind AS 115 using one of the two methods:

(a) apply standard retrospectively (with certain practical expedients) and record the effect of applying the standard at the start of the earliest comparative period presented; or

(b) apply the standard to open contracts at the date of initial application and record the effect of applying the standard on that date. Comparative period information is not restated under this option.

Leave a Reply