Ind AS 115 - Revenue from Contracts with Customers: A Comprehensive Guide for CA Final Students

Ind AS 115, 'Revenue from Contracts with Customers', establishes a comprehensive framework for revenue recognition, moving from a transaction-based approach to a contract-based approach. It provides a single, principle-based model applicable to all contracts with customers, ensuring consistent and comparable revenue reporting across industries and jurisdictions. This standard is critical for CA Final students, forming a significant part of Paper 1: Financial Reporting.

In India, Ind AS 115 is mandatory for companies adopting Ind AS and has significantly changed how revenue is recognised, especially for entities with complex arrangements involving multiple deliverables, variable consideration, and long-term contracts.

Quick Answer for Featured Snippets:
Ind AS 115's core principle is to recognise revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to be entitled in exchange for those goods or services, following a mandatory 5-step model.

Introduction to Ind AS 115: The Core Principle

Before Ind AS 115, revenue recognition was governed by Ind AS 18 (Revenue) and Ind AS 11 (Construction Contracts), which were largely rule-based and often led to inconsistent application, especially for complex arrangements involving multiple deliverables, variable consideration, and long-term contracts. Ind AS 115, converged with IFRS 15, addresses these complexities by providing a robust, principle-based framework.

Why Ind AS 115?

• Replaced Multiple Standards: Supersedes Ind AS 18 (Revenue) and Ind AS 11 (Construction Contracts), providing a single, comprehensive model.
• Principle-Based Approach: Shifts from a rule-based approach to a principle-based one, requiring significant judgment.
• Addresses Complexities: Provides detailed guidance for complex revenue recognition issues like bundled products, variable consideration, contract modifications, and licensing.
• Enhanced Comparability: Aims to improve comparability of revenue across industries, entities, and capital markets globally.
• Increased Disclosures: Mandates extensive disclosures to provide users with more informative insights into revenue streams.

Core Principle: The core principle of Ind AS 115 is that an entity shall recognise 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.

The Five-Step Model for Revenue Recognition

Ind AS 115 requires an entity to apply the following five steps to determine when to recognise revenue and at what amount:

• Step 1: Identify the contract(s) with a customer.
• Step 2: Identify the performance obligations in the contract.
• Step 3: Determine the transaction price.
• Step 4: Allocate the transaction price to the performance obligations.
• Step 5: Recognise revenue when (or as) the entity satisfies a performance obligation.

CA Exam Tip: Memorising and understanding the logical flow of these five steps is fundamental for solving any Ind AS 115 problem. Always structure your answers around these steps.

Step 1: Identify the Contract(s) with a Customer

A contract is an agreement between two or more parties that creates enforceable rights and obligations. For Ind AS 115, a contract with a customer must meet specific criteria to be accounted for.

Criteria for a Contract (all must be met):

• Approval: The parties have approved the contract (in writing, orally, or in accordance with customary business practices) and are committed to performing their respective obligations.
• Rights: The entity can identify each party's rights regarding the goods or services to be transferred.
• Payment Terms: The entity can identify the payment terms for the goods or services to be transferred.
• Commercial Substance: The contract has commercial substance (i.e., the risk, timing, or amount of the entity's future cash flows is expected to change as a result of the contract).
• Collectibility: It is probable that the entity will collect the consideration to which it will be entitled in exchange for the goods or services that will be transferred to the customer. ('Probable' means more likely than not, i.e., >50% chance).

Contract Combinations:
An entity combines two or more contracts and accounts for them as a single contract if they are entered into at or near the same time with the same customer (or related parties of the customer) and one or more of the following criteria are met:

1. The contracts are negotiated as a single package with a single commercial objective.
2. The amount of consideration in one contract depends on the price or performance of the other contract.
3. The goods or services promised in the contracts are a single performance obligation.

Contract Modifications:
A contract modification exists when the parties to a contract approve a change that either changes the scope or price (or both) of a contract. It can be accounted for as:

1. A separate contract: If the scope increases due to additional distinct goods/services, and the price increases by an amount that reflects the standalone selling price of the additional distinct goods/services.
2. Termination of old and creation of new contract: If the remaining goods/services are distinct from those transferred before the modification, and the price is adjusted for the standalone selling price of the remaining distinct goods/services.
3. Part of the existing contract: If the remaining goods/services are not distinct, or the price adjustment does not reflect the standalone selling price of additional distinct goods/services. This results in a cumulative catch-up adjustment to revenue.

Step 2: Identify the Performance Obligations in the Contract

A performance obligation is a promise in a contract with a customer 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.

Criteria for a Distinct Good or Service:

• Capable of being distinct: 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 not highly integrated with other goods or services in the contract).
• Distinct within the context of the contract: 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 entity is not providing a significant service of integrating the good or service with other goods or services into a combined output.

Examples of Not Distinct (i.e., bundled):

• Goods or services that are inputs to a combined output.
• Goods or services that significantly modify or customise other goods or services in the contract.
• Goods or services that are highly interdependent or interrelated with other goods or services in the contract.

Series of Distinct Goods or Services:
A series of distinct goods or services is treated as a single performance obligation if:

1. Each distinct good or service in the series that the entity promises to transfer would meet the criteria for being a performance obligation satisfied over time.
2. The same method would be used to measure the entity's progress towards complete satisfaction of the performance obligation to transfer each distinct good or service in the series to the customer.

CA Exam Tip: Identifying distinct performance obligations is crucial. Often, contracts include bundled goods/services. Students must analyse if each component can be used independently or if they are highly integrated.

Step 3: Determine the Transaction Price

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 (e.g., GST).

Components of Transaction Price:

• Fixed Consideration: A straightforward, fixed amount.
• Variable Consideration: Amounts that vary due to discounts, rebates, refunds, credits, price concessions, incentives, performance bonuses, penalties, or other similar items. It is estimated using either the 'expected value' method (probability-weighted average) or the 'most likely amount' method (single most probable outcome), depending on which method better predicts the amount of consideration.
• 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 recognised will not occur when the uncertainty associated with the variable consideration is subsequently resolved. This is a critical anti-abuse mechanism.
• Significant Financing Component: If the contract includes a significant financing component, the transaction price is adjusted for the time value of money. This typically applies when payment is received significantly before or after the transfer of goods/services. The adjustment is made using a discount rate that would be reflected in a separate financing transaction between the entity and its customer.
• Non-cash Consideration: Measured at fair value. If fair value cannot be reliably estimated, then by reference to the standalone selling price of the goods or services promised in exchange for the non-cash consideration.
• Consideration Payable to a Customer: This reduces the transaction price and, therefore, the revenue recognised. It can be cash or other items (e.g., vouchers, credits).

Formula for Transaction Price:

$$\text{Transaction Price} = \text{Fixed Consideration} + \text{Variable Consideration (subject to constraint)} + \text{Fair Value of Non-cash Consideration} - \text{Consideration Payable to Customer} \pm \text{Adjustment for Significant Financing Component}$$

CA Exam Tip: Variable consideration and the constraint are frequent areas of examination. Students must be able to apply the 'highly probable' threshold and choose the appropriate estimation method.

Step 4: Allocate the Transaction Price to the Performance Obligations

If a contract has multiple performance obligations, the entity allocates the transaction price to each distinct performance obligation in an amount that depicts the amount of consideration to which the entity expects to be entitled in exchange for transferring the promised goods or services.

Allocation Basis:

• Standalone Selling Price (SSP): The best evidence of SSP is an observable price when the entity sells that good or service separately to a customer. If not directly observable, it must be estimated.

Estimating SSP (when not directly observable):

• Adjusted market assessment approach: Evaluate market prices for similar goods/services and adjust for entity-specific factors.
• Expected cost plus a margin approach: Forecast expected costs of satisfying a performance obligation and add an appropriate margin.
• Residual approach: Used only if SSP is highly variable or uncertain. The entity may estimate the SSP of a good or service by subtracting the sum of the observable SSPs of other goods or services promised in the contract from the total transaction price. (Use with caution and only when other methods are not feasible).

Allocation of Discounts:
A discount exists if the sum of the standalone selling prices of the distinct goods or services in the contract exceeds the promised consideration. Discounts are allocated proportionately to all performance obligations unless there is observable evidence that the discount relates entirely to one or more, but not all, performance obligations.

Allocation of Variable Consideration:
Variable consideration is allocated to all performance obligations unless it relates specifically to one or more, but not all, performance obligations.

CA Exam Tip: The residual approach for SSP estimation is an exception, not the norm. Understand when it can be applied. Proportional allocation of discounts is the default.

Step 5: Recognise Revenue When (or As) the Entity Satisfies a Performance Obligation

Revenue is recognised when (or as) a performance obligation is satisfied by transferring a promised good or service to a customer. A good or service is transferred when the customer obtains control of that good or service.

Performance Obligations Satisfied 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:

1. Customer simultaneously receives and consumes the benefits as the entity performs (e.g., routine cleaning services, internet access).
2. The entity's performance creates or enhances an asset (e.g., work in progress) that the customer controls as the asset is created or enhanced (e.g., building on customer's land).
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 (e.g., highly customised product, specific service contract where entity can't redirect the asset).

Measurement of Progress:
For performance obligations satisfied over time, revenue is recognised based on the entity's progress towards complete satisfaction of that performance obligation. Methods include:

• Output methods: Measure value of goods/services transferred (e.g., surveys of work performed, appraisals of results achieved, milestones reached, units produced/delivered).
• Input methods: Measure entity's efforts or inputs to satisfy a performance obligation (e.g., costs incurred, resources consumed, labour hours expended, machine hours used). Input methods require careful adjustment for any inefficiencies.

Performance Obligations Satisfied At a Point in Time

If a performance obligation is not satisfied over time, it is satisfied at a point in time. To determine the point in time at which the customer obtains control, the entity considers indicators of the transfer of control, including, but not limited to:

1. The entity has a present right to payment for the asset.
2. The customer has legal title to the asset.
3. The customer has physical possession of the asset.
4. The customer has the significant risks and rewards of ownership of the asset.
5. The customer has accepted the asset.

CA Exam Tip: Distinguishing between 'over time' and 'point in time' revenue recognition is fundamental. The three criteria for 'over time' recognition are crucial. For 'point in time', remember the indicators of control.

Specific Application Guidance & Complex Scenarios

Ind AS 115 provides detailed guidance for various complex situations, which are frequently tested in CA Final examinations.

Variable Consideration and the Constraint

• Expected Value Method: Used when there are many possible outcomes (e.g., volume discounts, rebates). It's the sum of probability-weighted amounts.
• Most Likely Amount Method: Used when there are only two possible outcomes (e.g., bonus/penalty for meeting a deadline). It's the single most probable amount.
• Constraint: Revenue from variable consideration is recognised only to the extent that it is 'highly probable' that a significant reversal in the amount of cumulative revenue recognised will not occur. Factors to consider: susceptibility to factors outside entity's influence, length of time until uncertainty is resolved, entity's experience with similar contracts, broad range of possible consideration amounts.

Significant Financing Component

• A financing component exists if the timing of payments provides a significant benefit to either the customer or the entity.
• Adjust the transaction price by discounting future payments to their present value using an appropriate discount rate (rate that would be used in a separate financing transaction).
• The difference between the discounted amount and the nominal amount is recognised as interest revenue or interest expense.
• Practical expedient: No adjustment if the period between transfer of goods/services and payment is one year or less.

Non-cash Consideration

• Revenue is measured at the fair value of the non-cash consideration.
• If fair value cannot be reliably estimated, measure by reference to the standalone selling price of the goods or services promised in exchange for the non-cash consideration.

Consideration Payable to a Customer

• This reduces the transaction price and thus the revenue recognised.
• It is accounted for as a reduction of revenue unless it is in exchange for a distinct good or service that the customer transfers to the entity (in which case it's a purchase from the customer).

Principal vs. Agent Considerations

• Principal: Controls a good or service before it is transferred to the customer. Recognises revenue on a gross basis (total consideration).
• Agent: Arranges for another entity to provide the good or service. Recognises revenue on a net basis (commission or fee).
• Indicators of Control (for Principal):
  • Primary responsibility for fulfilling the promise.
  • Inventory risk (before or after customer acceptance).
  • Discretion in establishing prices.
  • Ability to direct the use of the good/service.

Licensing of Intellectual Property (IP)

• Right to Use (Functional IP): Revenue recognised at a point in time. Customer obtains control of the IP at the point the license is granted (e.g., software license for a specific version).
• Right to Access (Symbolic IP): Revenue recognised over time. The entity's activities during the license period significantly affect the IP, and the customer is exposed to changes in the IP (e.g., brand name, logo, continuously updated software).
• Factors to consider: Entity's ongoing activities, customer's ability to direct the use of the IP, entity's ability to change the IP.

Repurchase Agreements

• Sale with a Right of Return: Customer has right to return goods. Entity recognises revenue for goods not expected to be returned, a refund liability, and a right to recover goods (asset).
• Repurchase Options:
  • Forward or Call Option: Entity has right/obligation to repurchase. Accounted for as a lease (if customer has right to use asset) or a financing arrangement (if repurchase price > original selling price).
  • Put Option: Customer has right to require entity to repurchase. Accounted for as a lease, a financing arrangement, or a sale with right of return, depending on the repurchase price and customer's economic incentive.

Consignment Arrangements

• Goods delivered to a dealer (consignee) but legal title and risks/rewards remain with the entity (consignor).
• Revenue is recognised by the consignor only when the consignee sells the goods to an end customer.

Warranties

• Assurance-type Warranty: Provides assurance that the product complies with agreed-upon specifications. Accounted for under Ind AS 37 (Provisions, Contingent Liabilities and Contingent Assets) as a provision.
• Service-type Warranty: Provides a service in addition to the assurance-type warranty. This is a separate performance obligation, and a portion of the transaction price is allocated to it and recognised over the warranty period.

Contract Costs

• Incremental costs of obtaining a contract: Costs that an entity would not have incurred if the contract had not been obtained (e.g., sales commissions). Capitalise if expected to be recovered.
• Costs to fulfil a contract: Costs that relate directly to a contract, generate or enhance resources, and are expected to be recovered (e.g., direct labour, direct materials, allocation of overheads). Capitalise if they meet these criteria.
• Amortisation: Capitalised contract costs are amortised on a systematic basis consistent with the transfer of the related goods or services to the customer.

Contract Modifications

• Separate Contract: If the modification adds distinct goods/services and the price reflects their standalone selling price. Revenue recognised for new contract separately.
• Termination of Old & Creation of New: If remaining goods/services are distinct and the price reflects their standalone selling price. Revenue recognised prospectively from modification date.
• Part of Existing Contract: If remaining goods/services are not distinct or price does not reflect SSP. Cumulative catch-up adjustment to revenue recognised to date.

Presentation and Disclosure Requirements

Ind AS 115 requires specific presentation in the balance sheet and extensive disclosures in the notes to the financial statements to provide users with comprehensive information about revenue from contracts with customers.

Contract Assets, Contract Liabilities, and Receivables

• Contract Asset: An entity's right to consideration in exchange for goods or services that the entity has transferred to a customer. This right is conditional on something other than the passage of time (e.g., future performance). Presented as an asset.
• Contract Liability: An entity's obligation to transfer goods or services to a customer for which the entity has received consideration (or an amount of consideration is due) from the customer. Presented as a liability.
• Receivable: An entity's right to consideration that is unconditional (i.e., only the passage of time is required before payment is due). Presented as a financial asset.

Disclosure Requirements

• Disaggregation of Revenue: Disclose revenue disaggregated into categories that depict how the nature, amount, timing, and uncertainty of revenue and cash flows are affected by economic factors (e.g., by type of good/service, geographical region, customer type).
• Contract Balances: Opening and closing balances of contract assets, contract liabilities, and receivables, and significant changes in these balances (e.g., revenue recognised from contract liabilities, impairment losses).
• Performance Obligations: Information about remaining performance obligations, including the aggregate amount of the transaction price allocated to unsatisfied (or partially unsatisfied) performance obligations, and when the entity expects to recognise that amount as revenue.
• Significant Judgments: Explain the judgments made in applying the 5-step model, especially regarding identifying performance obligations, determining transaction price (including variable consideration and the constraint), and determining when performance obligations are satisfied.
• Contract Costs: Opening and closing balances of capitalised contract costs, amount of amortisation, and impairment losses.

Comparison with AS 9 (Revenue Recognition)

Ind AS 115 replaced AS 9 (Revenue Recognition) and AS 7 (Construction Contracts). The transition brought significant changes, particularly for entities with complex revenue arrangements.

Key Insight: AS 9 was largely rule-based and focused on the transfer of risks and rewards. Ind AS 115 is principle-based, contract-centric, and focuses on the transfer of control.

Key Differences:

• Basis: AS 9 was transaction-based; Ind AS 115 is contract-based.
• Core Principle: AS 9 focused on transfer of risks and rewards; Ind AS 115 focuses on transfer of control.
• Multiple Deliverables: AS 9 had limited guidance; Ind AS 115 provides a robust 5-step model for identifying and allocating revenue to distinct performance obligations.
• Variable Consideration: AS 9 had limited guidance; Ind AS 115 provides detailed guidance including estimation methods and the 'constraint'.
• Contract Costs: AS 9 had no specific guidance; Ind AS 115 specifies capitalisation and amortisation criteria for incremental costs of obtaining a contract and costs to fulfil a contract.
• Licensing: AS 9 had limited specific guidance; Ind AS 115 distinguishes between 'right to use' and 'right to access' IP.
• Presentation: AS 9 did not have 'contract assets'/'contract liabilities'; Ind AS 115 introduces these concepts.
• Disclosures: Ind AS 115 requires significantly more extensive and granular disclosures.

Illustrative Journal Entries

Understanding the accounting entries is crucial for practical application of Ind AS 115. Here are some common scenarios:

Scenario 1: Customer pays upfront for a 12-month service contract (₹1,20,000) starting immediately.

• On receipt of cash:
  Bank A/c Dr. ₹1,20,000
  \quad To Contract Liability A/c ₹1,20,000
  (Being cash received for future service)
• At end of each month (for 12 months):
  Contract Liability A/c Dr. ₹10,000
  \quad To Revenue A/c ₹10,000
  (Being revenue recognised for service provided during the month)

Scenario 2: Entity transfers goods to customer, but payment is due in 60 days.

• On transfer of goods:
  Trade Receivables A/c Dr. ₹X
  \quad To Revenue A/c ₹X
  (Being revenue recognised for goods transferred, payment due in 60 days)

Scenario 3: Entity incurs ₹5,000 in sales commission (incremental cost) to obtain a 3-year contract, expected to be recovered.

• On incurring commission:
  Contract Cost Asset A/c Dr. ₹5,000
  \quad To Bank A/c ₹5,000
  (Being capitalisation of incremental cost of obtaining a contract)
• At end of each year (for 3 years, assuming straight-line amortisation):
  Amortisation Expense A/c Dr. ₹1,667
  \quad To Contract Cost Asset A/c ₹1,667
  (Being amortisation of contract cost asset)

Scenario 4: Entity provides service over 3 months. Bills customer monthly. Revenue recognised based on progress (e.g., 30% complete at end of Month 1).

• At end of Month 1:
  Contract Asset A/c Dr. ₹X (Revenue recognised but not yet billed)
  \quad To Revenue A/c ₹X
  (Being revenue recognised based on progress towards satisfaction of performance obligation)
• When customer is billed (e.g., at end of Month 1 for ₹Y):
  Trade Receivables A/c Dr. ₹Y
  \quad To Contract Asset A/c ₹Y
  (Being billing to customer for services provided)

Practice Questions

Test your understanding with these exam-style questions. Model answers are provided for self-assessment. These are designed to simulate CA Final written answer requirements (full-blown descriptive and numerical problems, not MCQs).

Short Form Questions (Conceptual & Numerical)

Q1. Explain the core principle of Ind AS 115 and briefly outline the five-step model for revenue recognition.

Model Answer:
The core principle of Ind AS 115 is that an entity shall recognise 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.

The five-step model is:

1. Identify the contract(s) with a customer: Determine if an enforceable agreement exists.
2. Identify the performance obligations in the contract: Identify distinct promises to transfer goods/services.
3. Determine the transaction price: Calculate the amount of consideration expected, considering variable consideration, financing components, etc.
4. Allocate the transaction price to the performance obligations: Distribute the transaction price based on standalone selling prices.
5. Recognise revenue when (or as) the entity satisfies a performance obligation: Determine if control is transferred over time or at a point in time.

Q2. Distinguish between an 'assurance-type warranty' and a 'service-type warranty' under Ind AS 115, and explain their accounting treatment.

Model Answer:
Assurance-type Warranty: This is a warranty that provides assurance to the customer that the product will function as specified for a period. It is not a distinct service but part of the original product quality. Accounting treatment: Accounted for under Ind AS 37 (Provisions, Contingent Liabilities and Contingent Assets) as a provision for expected warranty costs.

Service-type Warranty: This is a warranty that provides a service to the customer in addition to the assurance that the product will function as specified. It is a distinct service that the customer could purchase separately. Accounting treatment: It is identified as a separate performance obligation. A portion of the transaction price is allocated to this performance obligation and recognised as revenue over the warranty period as the service is provided.

Q3. What is the 'constraint on variable consideration' under Ind AS 115? Provide an example of when it would be applied.

Model Answer:
The 'constraint on variable consideration' 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 recognised will not occur when the uncertainty associated with the variable consideration is subsequently resolved. This prevents premature recognition of revenue that may later need to be reversed.

Example: A construction company enters into a contract to build a bridge for ₹100 crore, with a bonus of ₹10 crore if completed within 2 years. At the end of Year 1, the company estimates a 70% chance of completing on time. However, the project involves new technology, and there's a significant risk of delays due to unforeseen technical challenges. Even though the 'most likely outcome' might suggest the bonus, due to the high uncertainty and susceptibility to external factors, the company might conclude it's not 'highly probable' that a significant reversal won't occur. Therefore, the ₹10 crore bonus would be constrained and not included in the transaction price until the uncertainty is resolved (e.g., near completion with high confidence).

Q4. Explain the difference between a 'contract asset' and a 'receivable' under Ind AS 115, and how they are presented in the financial statements.

Model Answer:
Contract Asset: Represents an entity's right to consideration in exchange for goods or services that the entity has transferred to a customer. This right is conditional on something other than the passage of time (e.g., future performance by the entity, or the achievement of a milestone). It is presented as an asset in the balance sheet.

Receivable: Represents an entity's right to consideration that is unconditional. Only the passage of time is required before payment is due. It is presented as a financial asset (e.g., Trade Receivables) in the balance sheet.

Key Difference: The conditionality of the right to consideration. A contract asset becomes a receivable when the right to consideration becomes unconditional.

Case Studies (Comprehensive Scenarios with Full Solutions)

Case Study 1: Application of 5-Step Model with Multiple Performance Obligations and Variable Consideration

Tech Solutions Ltd. (TSL) enters into a contract with a customer to sell a software license, provide installation services, and offer 2 years of technical support. The contract price is ₹10,00,000. TSL sells the software license for ₹6,00,000, installation services for ₹2,00,000, and 1 year of technical support for ₹1,50,000 on a standalone basis. The installation service is complex and significantly customises the software. The contract includes a performance bonus of ₹50,000 if the software achieves certain uptime targets in the first 6 months. TSL estimates an 80% probability of achieving the bonus, but there's high uncertainty due to customer's IT infrastructure. TSL's financial year ends on 31st March.

Requirements:
(a) Identify the performance obligations.
(b) Determine the transaction price.
(c) Allocate the transaction price to the performance obligations.
(d) Explain when and how revenue should be recognised for each performance obligation.

Model Solution:

(a) Step 1: Identify the Contract(s) with a Customer
A contract exists as per Ind AS 115 criteria.

(b) Step 2: Identify the Performance Obligations in the Contract

• Software License: This is a distinct good as the customer can benefit from it on its own.
• Installation Services: These services significantly customise the software, making it highly integrated with the software. Therefore, the installation services are not distinct from the software license. They are bundled together.
• Technical Support (2 years): This is a distinct service as the customer can benefit from it on its own or with other readily available resources. TSL sells 1-year support separately, so 2 years of support is a distinct performance obligation.

Thus, there are two distinct performance obligations:

1. Software License (including installation services)
2. Technical Support (2 years)

(c) Step 3: Determine the Transaction Price

• Fixed consideration: ₹10,00,000
• Variable consideration (performance bonus): ₹50,000

TSL estimates an 80% probability of achieving the bonus. However, due to high uncertainty related to the customer's IT infrastructure, it is not highly probable that a significant reversal of revenue will not occur. Therefore, the variable consideration of ₹50,000 is constrained and excluded from the transaction price initially.

Transaction Price = ₹10,00,000

(d) Step 4: Allocate the Transaction Price to the Performance Obligations
Standalone Selling Prices (SSPs):

• Software License: ₹6,00,000
• Installation Services: ₹2,00,000
• 1-year Technical Support: ₹1,50,000
  • Therefore, 2-year Technical Support SSP = ₹1,50,000 x 2 = ₹3,00,000

Combined SSP for Software License + Installation = ₹6,00,000 + ₹2,00,000 = ₹8,00,000
Total SSP of distinct performance obligations = ₹8,00,000 (Software+Installation) + ₹3,00,000 (2-year Support) = ₹11,00,000

Transaction Price = ₹10,00,000
Total SSP = ₹11,00,000
There is a discount of ₹1,00,000 (₹11,00,000 - ₹10,00,000).

Allocate transaction price based on relative SSPs:

• Software License (including installation): (₹8,00,000 / ₹11,00,000) * ₹10,00,000 = ₹7,27,273
• Technical Support (2 years): (₹3,00,000 / ₹11,00,000) * ₹10,00,000 = ₹2,72,727

(e) Step 5: Recognise Revenue When (or As) the Entity Satisfies a Performance Obligation

• Software License (including installation): Control of the software and the customised installation is transferred to the customer at a point in time (e.g., when the software is installed and accepted). Revenue of ₹7,27,273 is recognised at that point.
• Technical Support (2 years): This is a service provided over time, and the customer simultaneously receives and consumes the benefits. Revenue of ₹2,72,727 is recognised over the 2-year service period (₹1,36,363.50 per year, assuming straight-line recognition).

Summary:

• Revenue for Software + Installation: ₹7,27,273 (recognised at point of transfer).
• Revenue for Technical Support: ₹1,36,363.50 per year for 2 years (recognised over time).
• Performance bonus: Recognised only when the uncertainty is resolved and it is 'highly probable' that a significant reversal will not occur.

Case Study 2: Contract Costs and Significant Financing Component

BuildCo Ltd. enters into a contract on 1st April 2024 to construct a specialised machine for a customer for ₹50,00,000. The machine will be delivered on 31st March 2026. The customer pays ₹10,00,000 upfront on 1st April 2024 and the remaining ₹40,00,000 on delivery. BuildCo incurs ₹2,00,000 in sales commissions to obtain this contract. These costs are incremental and expected to be recovered. BuildCo's incremental borrowing rate is 10% per annum. The machine is built on BuildCo's premises and does not have an alternative use, but BuildCo has an enforceable right to payment for work completed. BuildCo uses an input method (costs incurred) to measure progress. Costs incurred in 2024-25: ₹15,00,000; in 2025-26: ₹20,00,000. Total expected cost: ₹35,00,000.

Requirements:
(a) Account for the incremental contract costs.
(b) Determine if a significant financing component exists and adjust the transaction price.
(c) Calculate revenue to be recognised for 2024-25 and 2025-26.
(d) Pass relevant journal entries for 2024-25.

Model Solution:

(a) Incremental Contract Costs (Sales Commissions)
The ₹2,00,000 sales commission is an incremental cost of obtaining the contract and is expected to be recovered. Therefore, it should be capitalised as a contract cost asset and amortised over the expected period of benefit, which is the contract term (2 years).
Annual amortisation = ₹2,00,000 / 2 years = ₹1,00,000 per year.

(b) Significant Financing Component

• Payment terms: ₹10,00,000 upfront (1.4.2024), ₹40,00,000 on delivery (31.3.2026).
• The upfront payment provides a significant financing benefit to BuildCo, and the deferred payment provides a significant financing benefit to the customer. Since the period between payment and transfer of goods/services is more than one year, a significant financing component exists.
• Discount rate = 10% per annum.

Present Value of future payment:
PV of ₹40,00,000 due on 31.3.2026 (2 years from 1.4.2024) = ₹40,00,000 / (1 + 0.10)^2 = ₹40,00,000 / 1.21 = ₹33,05,785

Adjusted Transaction Price (Revenue amount):
= Upfront payment + PV of future payment
= ₹10,00,000 + ₹33,05,785 = ₹43,05,785

Difference between nominal and adjusted transaction price is the financing component:
Nominal Transaction Price = ₹10,00,000 + ₹40,00,000 = ₹50,00,000
Financing Component = ₹50,00,000 - ₹43,05,785 = ₹6,94,215

(c) Revenue to be Recognised

• Performance Obligation: Construction of the specialised machine. This is a single performance obligation satisfied over time because the machine has no alternative use to BuildCo, and BuildCo has an enforceable right to payment for performance completed to date.
• Measure of Progress: Input method (costs incurred).
• Total expected costs = ₹35,00,000.
• Adjusted Transaction Price (Revenue) = ₹43,05,785.

Year 2024-25:

• Costs incurred = ₹15,00,000
• Percentage completion = ₹15,00,000 / ₹35,00,000 = 42.86%
• Revenue recognised = 42.86% * ₹43,05,785 = ₹18,45,337

Year 2025-26:

• Costs incurred = ₹20,00,000
• Cumulative costs = ₹15,00,000 + ₹20,00,000 = ₹35,00,000
• Cumulative percentage completion = ₹35,00,000 / ₹35,00,000 = 100%
• Cumulative revenue = 100% * ₹43,05,785 = ₹43,05,785
• Revenue recognised in 2025-26 = ₹43,05,785 - ₹18,45,337 = ₹24,60,448

Interest Expense/Revenue (Financing Component):
The upfront payment of ₹10,00,000 is a contract liability. BuildCo earns interest on this liability.

• 2024-25: Interest expense on upfront payment = ₹10,00,000 * 10% = ₹1,00,000
• 2025-26: Interest expense on upfront payment = (₹10,00,000 + ₹1,00,000) * 10% = ₹1,10,000

The deferred payment of ₹40,00,000 (nominal) has a PV of ₹33,05,785. BuildCo will recognise interest revenue on this 'receivable' portion.

• 2024-25: Interest revenue = ₹33,05,785 * 10% = ₹3,30,578.50
• 2025-26: Interest revenue = (₹33,05,785 + ₹3,30,578.50) * 10% = ₹3,63,636.35

(d) Journal Entries for 2024-25

1. To record capitalisation of contract costs (1.4.2024):
   Contract Cost Asset A/c Dr. ₹2,00,000
   \quad To Bank A/c ₹2,00,000
   (Being capitalisation of incremental costs to obtain contract)

2. To record receipt of upfront payment (1.4.2024):
   Bank A/c Dr. ₹10,00,000
   \quad To Contract Liability A/c ₹10,00,000
   (Being receipt of upfront payment from customer)

3. To recognise revenue for 2024-25 (31.3.2025):
   Contract Asset A/c Dr. ₹18,45,337
   \quad To Revenue A/c ₹18,45,337
   (Being revenue recognised for machine construction based on progress)

4. To recognise interest expense on contract liability (31.3.2025):
   Interest Expense A/c Dr. ₹1,00,000
   \quad To Contract Liability A/c ₹1,00,000
   (Being recognition of interest on upfront payment)

5. To recognise interest revenue on contract asset (31.3.2025):
   Contract Asset A/c Dr. ₹3,30,578.50
   \quad To Interest Revenue A/c ₹3,30,578.50
   (Being recognition of interest revenue on deferred consideration)

6. To amortise contract cost asset for 2024-25 (31.3.2025):
   Amortisation Expense (Contract Costs) A/c Dr. ₹1,00,000
   \quad To Contract Cost Asset A/c ₹1,00,000
   (Being amortisation of contract cost asset)

Case Study 3: Principal vs. Agent Determination

TravelEase Ltd. operates an online platform where customers can book flights and hotels. TravelEase offers two types of services: (A) Direct booking of flights where TravelEase acts as a reseller, buying tickets in bulk from airlines and selling them to customers at a markup. TravelEase sets the price, handles customer service, and bears inventory risk. (B) Hotel bookings where TravelEase lists hotels and facilitates bookings. The hotel sets the price, handles all customer service, and bears the risk of cancellations. TravelEase receives a 10% commission from the hotel on each booking.

Requirements:
(a) For each service (A and B), determine whether TravelEase acts as a principal or an agent.
(b) Explain the revenue recognition implications for each service.
(c) Provide illustrative journal entries for a ₹10,000 flight booking (Service A) and a ₹5,000 hotel booking (Service B).

Model Solution:

(a) Principal vs. Agent Determination:

• Service A (Direct Flight Booking): TravelEase acts as a Principal.

  • Indicators: TravelEase controls the flight tickets before transferring them to the customer. This is evidenced by:
    • Inventory risk: TravelEase buys tickets in bulk and bears the risk if they are not sold.
    • Pricing discretion: TravelEase sets the selling price to the customer.
    • Primary responsibility: TravelEase handles customer service related to the booking.

• Service B (Hotel Bookings): TravelEase acts as an Agent.

  • Indicators: TravelEase does not control the hotel rooms. It facilitates the booking between the customer and the hotel. This is evidenced by:
    • No inventory risk: TravelEase does not own or bear risk for the hotel rooms.
    • No pricing discretion: The hotel sets the price.
    • No primary responsibility: The hotel is responsible for providing the accommodation and handling customer service/cancellations.

(b) Revenue Recognition Implications:

• Service A (Principal): TravelEase will recognise revenue on a gross basis. This means the full amount of consideration received from the customer for the flight ticket will be recognised as revenue. The cost of the ticket purchased from the airline will be recognised as cost of sales.

• Service B (Agent): TravelEase will recognise revenue on a net basis. This means only the commission earned from the hotel will be recognised as revenue, not the full amount paid by the customer to the hotel.

(c) Illustrative Journal Entries:

Service A: ₹10,000 Flight Booking (TravelEase as Principal)
Assume TravelEase bought the ticket from the airline for ₹9,000.

1. On purchase of ticket from airline:
   Inventory (Flight Tickets) A/c Dr. ₹9,000
   \quad To Bank/Payables A/c ₹9,000
   (Being purchase of flight ticket)

2. On sale of ticket to customer:
   Bank/Receivables A/c Dr. ₹10,000
   \quad To Revenue A/c ₹10,000
   (Being revenue recognised for flight ticket sold)

3. On transfer of ticket (cost of sales):
   Cost of Sales A/c Dr. ₹9,000
   \quad To Inventory (Flight Tickets) A/c ₹9,000
   (Being cost of flight ticket sold)

Service B: ₹5,000 Hotel Booking (TravelEase as Agent)
TravelEase earns a 10% commission, so ₹500.

1. On customer booking and payment (assuming TravelEase collects payment on behalf of hotel):
   Bank A/c Dr. ₹5,000
   \quad To Payable to Hotel A/c ₹4,500
   \quad To Revenue A/c (Commission) ₹500
   (Being receipt of payment from customer, recognising commission and liability to hotel)

2. On remitting payment to hotel (if applicable):
   Payable to Hotel A/c Dr. ₹4,500
   \quad To Bank A/c ₹4,500
   (Being remittance of net payment to hotel)

---

Common Mistakes & CA Exam Tips

• Not applying the 5-step model systematically: Always structure your answer around the five steps, even if some steps are straightforward.
• Incorrectly identifying distinct performance obligations: Students often fail to analyse if goods/services are highly integrated or capable of being distinct.
• Ignoring the constraint on variable consideration: This is a critical point. Don't just take the expected value; assess 'highly probable' first.
• Failing to adjust for significant financing components: Especially when payment terms are long, remember to discount.
• Confusing Principal vs. Agent: Carefully evaluate the indicators of control, particularly inventory risk and pricing discretion.
• Incorrectly accounting for contract costs: Remember capitalisation criteria and amortisation.
• Misclassifying Contract Assets vs. Receivables: Understand the conditionality aspect.
• Insufficient Disclosures: In theory questions, remember to list relevant disclosure requirements.
• Practice Tip: Solve past ICAI RTPs/MTPs and mock tests on Kartavvya for topic-wise MCQs + analytics on weak areas like 'variable consideration constraint' or 'principal vs. agent determination'.

Key Takeaways

• Ind AS 115 is a principle-based, contract-centric standard focusing on the transfer of control.
• Master the 5-step model – it's the backbone of all revenue recognition under Ind AS 115.
• Pay close attention to variable consideration and its constraint, significant financing components, and principal vs. agent determinations, as these are common areas of complexity.
• Understand the accounting for contract costs (incremental and fulfilment).
• Differentiate between contract assets, contract liabilities, and receivables for correct presentation.
• Be prepared for extensive disclosure requirements.

Frequently Asked Questions (FAQs)

Q: What is the core principle of Ind AS 115?
A: The core principle is to recognise revenue to depict the transfer of promised goods or services to customers in an amount that reflects the consideration the entity expects to be entitled in exchange for those goods or services.

Q: What are the five steps of revenue recognition under Ind AS 115?
A: The five steps are: 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) Recognise revenue when (or as) the entity satisfies a performance obligation.

Q: When is variable consideration included in the transaction price under Ind AS 115?
A: Variable consideration is included 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.

Q: What is the main difference between Ind AS 115 and the old AS 9?
A: Ind AS 115 is a principle-based, contract-centric standard focusing on the transfer of control, whereas AS 9 was largely rule-based and focused on the transfer of risks and rewards.

Q: How do you determine if a performance obligation is satisfied 'over time' or 'at a point in time'?
A: A performance obligation is satisfied 'over time' if any of three specific criteria are met (customer simultaneously receives/consumes benefits, customer controls asset as created/enhanced, or entity has no alternative use for asset and enforceable right to payment). If none of these are met, it's satisfied 'at a point in time', determined by indicators of control like physical possession, legal title, and risks/rewards.

References & Further Reading

• Ind AS 115 – Revenue from Contracts with Customers (ICAI)
• ICAI Study Material for CA Final Paper 1: Financial Reporting
• Guidance Notes and Educational Material issued by ICAI on Ind AS 115
• Ind AS 37 – Provisions, Contingent Liabilities and Contingent Assets

Last Updated: July 2026 | Prepared by Kartavvya CA Expert Team (aligned with latest ICAI syllabus & Ind-AS)

Ready to master this topic?
Practice hundreds of MCQs, past-year questions, and get personalized weak-area analytics with adaptive study plans on Kartavvya – your AI-powered CA prep companion. [Start Free Trial / Join Now]