Ind AS 115 - Revenue from Contracts with Customers

Ind AS 115 provides specific guidance for the accounting of contract costs:

Costs to Obtain a Contract: An entity capitalises the incremental costs of obtaining a contract with a customer if it expects to recover those costs. Incremental costs are those costs that an entity would not have incurred if the contract had not been obtained (e.g., sales commissions). Costs that would have been incurred regardless of whether the contract was obtained (e.g., travel costs for sales meetings) are expensed as incurred, unless they are explicitly reimbursable by the customer.

Costs to Fulfil a Contract: An entity capitalises costs incurred to fulfil a contract if those costs meet all of the following criteria:

1. They relate directly to a contract or an anticipated contract.
2. They generate or enhance resources of the entity that will be used in satisfying performance obligations in the future.
3. They are expected to be recovered.
   Examples include direct labour, direct materials, and allocation of costs that relate directly to contract activities.

Amortisation: Capitalised contract costs (both to obtain and to fulfil) are amortised on a systematic basis that is consistent with the pattern of transfer of the goods or services to which the asset relates. The amortisation period should reflect the period over which the entity expects to provide the related goods or services, including anticipated contract renewals if the costs relate to activities that are part of those renewals. An impairment loss is recognised if the carrying amount of the asset exceeds the remaining amount of consideration that the entity expects to receive less the costs that relate directly to providing those goods or services and that have not been recognised as expenses.

Under Ind AS 115, a good or service is distinct if both of the following criteria are met:

1. 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. This means the good or service is capable of being distinct. For example, a customer could use a software license on its own, or integrate it with their existing hardware.
2. The entity's promise to transfer the good or service to the customer is separately identifiable from other promises in the contract. This means the good or service is distinct within the context of the contract. This criterion is not met if the entity provides a significant service of integrating the goods or services into a combined output, if the goods or services are highly interdependent or interrelated, or if one significantly modifies or customizes another. For instance, in a construction contract, individual components like bricks and cement are not distinct performance obligations because the entity is providing a combined output (a building) rather than separate components.
   Identifying distinct performance obligations is critical because the transaction price is allocated to each distinct obligation, and revenue is recognized as each distinct obligation is satisfied.

If the consideration in a contract includes a variable amount, an entity must estimate the amount it expects to be entitled to. The entity can only include variable consideration in the transaction price to the extent that it is highly probable that a significant reversal in the amount of cumulative revenue recognized will not occur.

The 5-step model is: 1) Identify the contract(s) with a customer. 2) Identify the performance obligations in the contract. 3) Determine the transaction price. 4) Allocate the transaction price to the performance obligations. 5) Recognize revenue when (or as) the entity satisfies a performance obligation.

The distinction between acting as a principal and an agent is crucial because it determines whether an entity recognizes revenue on a gross basis (as a principal) or on a net basis (as an agent). An entity is a principal if it obtains control of a promised good or service before transferring that good or service to a customer. Conversely, an entity is an agent if its performance obligation is to arrange for the provision of goods or services by another party. The primary indicator of control for a principal is the ability to direct the use of, and obtain substantially all the remaining benefits from, the good or service. Key indicators that an entity controls the specified good or service before it is transferred to the customer (and is therefore a principal) include: 1) The entity is primarily responsible for fulfilling the promise to provide the specified good or service. 2) The entity has inventory risk before the specified good or service is transferred to a customer or after transfer of customer control. 3) The entity has discretion in establishing the price for the specified good or service. 4) The entity bears the credit risk for the customer. While these indicators are helpful, the ultimate determination rests on whether the entity obtains control of the specified good or service before transferring it to the customer. If an entity is an agent, it recognizes revenue in the amount of any fee or commission to which it expects to be entitled in exchange for arranging for the specified goods or services to be provided by the other party.

Ind AS 115 provides specific guidance on accounting for contract costs. Costs incurred to obtain a contract are capitalized if they are incremental costs of obtaining a contract and the entity expects to recover them. Incremental costs are those that an entity would not have incurred if the contract had not been obtained (e.g., sales commissions). Costs that would have been incurred regardless of whether the contract was obtained (e.g., travel costs to meet a prospective customer) are expensed as incurred, unless they are explicitly reimbursable by the customer. Costs to fulfill a contract are capitalized if they meet all of the following criteria: 1) The costs relate directly to a contract or an anticipated contract. 2) The costs generate or enhance resources of the entity that will be used in satisfying performance obligations in the future. 3) The costs are expected to be recovered. Examples of such costs include direct labor, direct materials, and allocation of costs that relate directly to the contract (e.g., depreciation of equipment used to fulfill the contract). Costs that do not meet these criteria, such as general and administrative costs (unless explicitly chargeable to the customer), costs of wasted materials, or costs related to past performance, are expensed as incurred. Capitalized contract costs are amortized on a systematic basis consistent with the transfer of the goods or services to which the asset relates, and are subject to impairment testing.

A contract modification is a change in the scope or price (or both) of a contract that is approved by the parties to the contract. Ind AS 115 requires an entity to assess whether a contract modification should be accounted for as a separate new contract, as a termination of the existing contract and creation of a new one, or as part of the existing contract.

1. Separate Contract: A modification is accounted for as a separate new contract if both of the following conditions are met: (a) the scope of the contract increases due to the addition of promised goods or services that are distinct, and (b) the price of the contract increases by an amount of consideration that reflects the entity's standalone selling prices of the additional distinct goods or services. In this case, the original contract remains unchanged, and the new contract is accounted for prospectively.

2. Termination and New Contract: If the modification does not meet the criteria for a separate contract, but the remaining goods or services are distinct from those already transferred, the modification is accounted for as a termination of the original contract and the creation of a new contract. The revenue recognized for the remaining performance obligations is adjusted prospectively from the date of modification. This means the transaction price for the remaining distinct goods or services (including the consideration from the modification) is allocated to the remaining performance obligations, and revenue is recognized based on this new allocation.

3. Part of the Existing Contract (Cumulative Catch-up): If the modification does not meet the criteria for a separate contract, and the remaining goods or services are not distinct from those already transferred (i.e., they are part of a single performance obligation that is partially satisfied), the modification is accounted for as if it were part of the original contract. This results in a 'cumulative catch-up' adjustment to revenue. The effect of the modification on the transaction price and the entity's measure of progress towards satisfying the performance obligation is recognized as an adjustment to revenue in the period of the modification. This adjustment reflects the change in the total transaction price and the revised measure of progress for the entire performance obligation from the contract inception to the modification date.

The determination of whether an entity is a principal or an agent depends on whether the entity controls a promised good or service before it is transferred to a customer. An entity is a principal if it obtains control of the good or service before transferring it to the customer. An entity is an agent if its performance obligation is to arrange for another party to provide the good or service.

Indicators of Control (for Principal determination):

• The entity is primarily responsible for fulfilling the promise to provide the specified good or service.
• The entity has inventory risk before the good or service is transferred to a customer or after transfer of control to the customer (e.g., risk of obsolescence or loss).
• The entity has discretion in establishing the price for the specified good or service.
• The entity has the ability to direct the use of, and obtain substantially all of the remaining benefits from, the good or service.

Implications:

• Principal: Recognizes revenue on a gross basis, reflecting the total consideration it expects to receive in exchange for the goods or services transferred.
• Agent: Recognizes revenue on a net basis, reflecting the amount of any fee or commission to which it expects to be entitled for arranging for the other party to provide the goods or services. This is because the agent does not control the good or service provided by the other party.

Variable consideration refers to the portion of the transaction price that is contingent on future events or conditions. Examples include discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties, and royalties. An entity estimates the amount of variable consideration using either the expected value method (sum of probability-weighted amounts) or the most likely amount method (single most likely outcome), depending on which method better predicts the amount of consideration to which the entity will be entitled.

The Constraint on Variable Consideration: Ind AS 115 requires an entity to include variable consideration in the transaction price only to the extent that it is highly probable that a significant reversal in the amount of cumulative revenue recognized will not occur when the uncertainty associated with the variable consideration is subsequently resolved. This constraint aims to prevent premature recognition of revenue that may later need to be reversed. Factors to consider when applying the constraint include the entity's experience with similar contracts, susceptibility to factors outside the entity's influence (e.g., market volatility, third-party actions), the length of time until the uncertainty is resolved, and the number and range of possible consideration amounts.

Under Ind AS 115, an entity estimates the amount of consideration to which it expects to be entitled in exchange for transferring promised goods or services to a customer. Variable consideration can arise from discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties, or other similar items. The standard requires an entity to estimate variable consideration using either the 'expected value method' (sum of probability-weighted amounts) or the 'most likely amount method' (single most likely outcome), depending on which method better predicts the amount of consideration to which the entity will be entitled. A crucial aspect is the 'constraint on variable consideration'. An entity includes variable consideration in the transaction price only to the extent that it is highly probable that a significant reversal in the amount of cumulative revenue recognized will not occur when the uncertainty associated with the variable consideration is subsequently resolved. This constraint aims to prevent premature recognition of revenue that may later need to be reversed. Factors to consider when assessing the constraint include the entity's experience with similar contracts, the length of time until the uncertainty is resolved, the number and range of possible consideration amounts, and the susceptibility of the variable consideration to factors outside the entity's influence. The estimate of variable consideration and the assessment of the constraint must be updated at each reporting period.

Revenue is recognized over time if one of the following criteria is met: 1) The customer simultaneously receives and consumes the benefits provided by the entity's performance. 2) The entity's performance creates or enhances an asset that the customer controls. 3) 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.

Ind AS 115 provides specific guidance for licensing of intellectual property (IP), distinguishing between a 'right to access' and a 'right to use' IP, which significantly impacts the timing of revenue recognition.

Right to Use IP:

• This grants the customer the right to use the entity's IP as it exists at the point in time at which the license is granted. The entity's activities do not significantly affect the IP to which the customer has rights. The customer can direct the use of, and obtain substantially all of the remaining benefits from, the IP at that point in time.
• Revenue Recognition: Revenue is recognized at a point in time (when the license is granted and control of the right to use is transferred). Examples include licenses for software, movies, or music where the IP is static and the customer can use it immediately.

Right to Access IP:

• This grants the customer the right to access the entity's IP as it exists throughout the license period. The entity's ongoing activities are expected to significantly affect the IP to which the customer has rights. The customer simultaneously receives and consumes the benefits from the entity's performance as the entity performs.
• Revenue Recognition: Revenue is recognized over time (over the license period). Examples include brand licenses, franchise agreements, or subscriptions to online databases where the licensor continuously updates or maintains the IP, and the customer benefits from these ongoing activities throughout the license term.

Identifying distinct performance obligations is the second step in the five-step model of Ind AS 115 and is critical for determining when and how revenue is recognized. A good or service is distinct if both of the following criteria are met: 1) 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 (i.e., the good or service is 'capable of being distinct'). This means the good or service could be sold separately or has a standalone utility for the customer. 2) The entity's promise to transfer the good or service to the customer is separately identifiable from other promises in the contract (i.e., the good or service is 'distinct within the context of the contract'). This criterion is not met if the entity provides a significant service of integrating the good or service with other goods or services promised in the contract into a bundle that represents the combined output for which the customer has contracted. For example, if a software license, installation, and customization are sold together, the installation and customization might not be separately identifiable if they significantly modify the software to create a combined product. Factors indicating that two or more promises are not separately identifiable include: the entity provides a significant service of integrating the goods or services into a combined item; the goods or services are highly interdependent or highly interrelated; or one good or service significantly modifies or customizes another. Each distinct performance obligation is accounted for separately, and revenue is recognized as each distinct performance obligation is satisfied.

Ind AS 115 establishes a five-step model for revenue recognition to ensure that revenue is recognized in a manner that depicts 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. The five steps are:

1. Identify the contract(s) with a customer: A contract exists if it has commercial substance, the parties are committed, rights and payment terms are identifiable, and collection is probable.
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 distinct goods or services that are substantially the same and have the same pattern of transfer) to the customer.
3. Determine the transaction price: This is the amount of consideration an entity expects to be entitled to in exchange for transferring promised goods or services, excluding amounts collected on behalf of third parties.
4. Allocate the transaction price to the performance obligations: If a contract has multiple performance obligations, the transaction price is allocated to each distinct performance obligation based on its relative standalone selling price.
5. Recognize revenue when (or as) the entity satisfies a performance obligation: Revenue is recognized when control of the promised good or service is transferred to the customer, which can be at a point in time or over time.
   This model is crucial as it provides a robust framework for addressing complex revenue arrangements, enhancing comparability across entities and industries, and improving the quality of financial reporting.

A contract modification changes the scope or price (or both) of an existing enforceable contract. Ind AS 115 provides three approaches for accounting for contract modifications:

1. As a separate contract: This applies if the modification adds distinct goods or services, and the price of the added goods or services reflects their standalone selling price. In this case, the existing contract remains unchanged, and the modification is accounted for prospectively as a new, separate contract.

2. As a termination of the existing contract and creation of a new contract (prospective adjustment): This applies if the modification does not add distinct goods or services, but the remaining goods or services are distinct from those already transferred. The revenue and costs for the remaining performance obligations are accounted for prospectively from the date of modification, effectively treating the original contract as terminated and a new one created for the remaining part.

3. As part of the existing contract (cumulative catch-up adjustment): This applies if the modification does not add distinct goods or services, and the remaining goods or services are not distinct from those already transferred. In this scenario, the modification is accounted for as if it were part of the original contract from inception. This requires a cumulative catch-up adjustment to revenue and costs recognized to date, reflecting the change in the transaction price and/or scope as if it had always been part of the contract. This approach is common when a modification changes the transaction price for partially satisfied performance obligations that are recognized over time.