Ind AS 115 Revenue Recognition Guide: 5-Step Model & Obligations

Executive Overview: The Unified Revenue Framework under Ind AS 115

Revenue from operations is the single most vital metric utilized by equity investors, commercial lenders, rating agencies, and tax authorities to evaluate corporate financial performance and business viability. Under legacy Indian accounting standards (AS 9, Revenue Recognition and AS 7, Construction Contracts), revenue recognition was fragmented across disparate industry models and anchored primarily to the legal concept of "transfer of significant risks and rewards of ownership". This legacy approach created widespread accounting divergence, enabling entities to accelerate revenue recognition prior to fulfilling genuine commercial commitments or obfuscate long-term customer contract liabilities off-balance sheet.

To establish a rigorous, harmonized global standard, the Ministry of Corporate Affairs (MCA) notified Indian Accounting Standard (Ind AS) 115, Revenue from Contracts with Customers, fully converged with international standard IFRS 15, replacing both Ind AS 18 and Ind AS 11. Ind AS 115 introduces a comprehensive, contract-based, five-step revenue recognition model that applies across virtually all commercial customer contracts (excluding leases, insurance, and financial instruments). The standard shifts the core recognition trigger from "transfer of risks and rewards" to the transfer of CONTROL of promised goods or services. Furthermore, Ind AS 115 imposes rigorous measurement criteria for variable consideration, volume rebates, significant financing components, customer options, warranties, non-refundable upfront fees, and the capitalization of incremental contract acquisition costs. Chief financial officers, statutory audit partners, and revenue controllers leveraging assureOffice and its cloud-native financial reporting platform assureFinancials must master the intricate 5-step framework, performance obligation unbundling, over-time vs. point-in-time criteria, contract assets vs. trade receivables accounting, and Ind AS 115 disclosure mandates to withstand aggressive regulatory scrutiny by the National Financial Reporting Authority (NFRA).

The Core Five-Step Model of Revenue Recognition

The substantive architecture of Ind AS 115 is organized around five sequential, non-negotiable analytical steps that every reporting entity must execute for every commercial customer contract:

Step 1: Identify the Contract with a Customer (Paragraphs 9-16)

A contract is an agreement between two or more parties that creates enforceable rights and obligations. A contract falls within the scope of Ind AS 115 ONLY when all five statutory criteria are satisfied:

The parties have approved the contract and are committed to performing their obligations;
The entity can identify each party's rights regarding the goods or services to be transferred;
The entity can identify the payment terms for the goods or services;
The contract has commercial substance (the risk, timing, or amount of the entity's future cash flows is expected to change as a result of the contract); and
It is probable that the entity will collect the consideration to which it will be entitled in exchange for the goods or services transferred to the customer.

Step 2: Identify the Performance Obligations in the Contract (Paragraphs 22-30)

A performance obligation is a promise in a contract with a customer to transfer to the customer either: (a) a good or service that is distinct; or (b) a series of distinct goods or services that are substantially the same and have the same pattern of transfer.

The "Distinct" Criteria: A good or service is distinct if:
1. The customer can benefit from the good or service either on its own or together with other resources readily available (capable of being distinct); AND
2. The entity's promise to transfer the good or service is separately identifiable from other promises in the contract (distinct within the context of the contract).
Bundled vs. Unbundled Services: In software contracts, selling software licenses alongside custom integration and ongoing technical support requires evaluating whether the integration service significantly modifies the software (bundled single obligation) or represents standard installation (three distinct performance obligations!).

Step 3: Determine the Transaction Price (Paragraphs 47-72)

The transaction price is the amount of consideration to which an entity expects to be entitled in exchange for transferring promised goods or services, excluding amounts collected on behalf of third parties (e.g., GST). Determining transaction price requires evaluating four complex elements:

Variable Consideration: Discounts, rebates, refunds, credits, price concessions, incentives, or performance bonuses. Estimated using either the "Expected Value" method or the "Most Likely Amount" method. The Constraint Rule (Paragraph 56): Variable consideration is included 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 is resolved!
Significant Financing Component: If the timing of payments agreed provides the customer or entity with a significant benefit of financing (e.g., customer pays 2 years in advance or 2 years after delivery), the consideration must be discounted to present value using an imputed discount rate.
Non-Cash Consideration: Measured at fair value at contract inception.
Consideration Payable to a Customer: Cash or credits paid to a customer (e.g., slotting fees, cooperative advertising allowances) are accounted for as a reduction of the transaction price, unless paid in exchange for a distinct good or service.

Step 4: Allocate the Transaction Price to Performance Obligations (Paragraphs 73-86)

The objective is to allocate the transaction price to each performance obligation in an amount that depicts the consideration to which the entity expects to be entitled. Allocation must be made in proportion to their relative Stand-Alone Selling Prices (SSP) determined at contract inception.

Observable Price: The price at which the entity sells the good or service separately in similar circumstances.
Estimated Price: If an SSP is not directly observable, the entity must estimate it using: (i) Adjusted market assessment approach; (ii) Expected cost plus a margin approach; or (iii) Residual approach (permitted only in narrow circumstances).

Step 5: Recognize Revenue When (or as) the Entity Satisfies a Performance Obligation (Paragraphs 31-45)

Revenue is recognized when the customer obtains control of the promised asset (ability to direct the use of and obtain substantially all remaining benefits). The standard establishes two recognition mechanisms:

Over Time (Paragraph 35): Revenue is recognized over time if ANY ONE of the following three criteria is met:
- (a) The customer simultaneously receives and consumes the benefits provided by the entity's performance as the entity performs (e.g., daily security services, routine cleaning);
- (b) The entity's performance creates or enhances an asset that the customer controls as the asset is created or enhanced (e.g., building an asset on customer-owned land); OR
- (c) 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 throughout the contract term!
Point in Time (Paragraph 38): If none of the three over-time criteria are met, revenue is recognized at the point in time when control transfers (evaluated by indicators: physical possession, legal title, present right to payment, significant risks and rewards, customer acceptance).

Enterprise revenue accounting modules in assureFinancials automate multi-element contract allocations and track percentage-of-completion progress measures in real time.

Contract Assets, Contract Liabilities, and Contract Cost Capitalization

Ind AS 116 completely overhauled balance sheet nomenclature and asset-liability presentations for customer contracts:

1. Contract Asset vs. Trade Receivable (Paragraphs 105-108)

Contract Asset: An entity's right to consideration in exchange for goods or services that the entity has transferred to a customer when that right is conditioned on something other than the passage of time (e.g., entity's future performance of another milestone obligation). Contract assets are subject to the Expected Credit Loss (ECL) impairment model under Ind AS 109.
Trade Receivable: An entity's right to consideration that is unconditional (only the passage of time is required before payment of that consideration is due). An invoice raised upon milestone certification is a trade receivable.
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 (previously referred to as "Unearned Revenue" or "Customer Advances").

2. Accounting for Contract Costs (Paragraphs 91-104)

Ind AS 115 establishes specific rules for capitalizing costs associated with customer contracts:

Incremental Costs of Obtaining a Contract (Paragraph 91): Costs that the entity incurs to obtain a contract with a customer that it would not have incurred if the contract had not been obtained (e.g., sales commissions paid to employees upon successful deal signing). These costs MUST be capitalized as an intangible asset and amortized on a systematic basis consistent with the transfer of goods/services! (Practical expedient: Expensed immediately if amortization period is 1 year or less).
Costs to Fulfill a Contract (Paragraph 95): Costs incurred in fulfilling a contract (e.g., pre-contract engineering setup, mobilization costs) are capitalized if: (a) they relate directly to a contract; (b) they generate or enhance resources that will be used in satisfying future obligations; and (c) they are expected to be recovered.

Practical Case Studies and Numerical Illustrations

The following eight comprehensive real-world case studies illustrate complex scenarios encountered by corporate revenue controllers, software vendors, EPC contractors, and statutory auditors under Ind AS 115.

Case Study 1: Bundled Software Contract: License, Implementation, and Annual Maintenance (AMCs)

Facts: CloudMatrix Enterprise Software Ltd. enters into a 3-year enterprise software contract with a corporate bank on 1st April 2025. Total contract consideration is ₹1,20,00,000. The contract comprises: (a) Enterprise ERP Software License (perpetual); (b) Standard implementation and data migration service; and (c) Post-implementation technical support (AMC) for 3 years. The implementation service is routine and could be performed by independent third-party IT vendors. Stand-alone selling prices (SSP) if sold separately are: License = ₹70,00,000; Implementation = ₹30,00,000; 3-Year AMC = ₹40,00,000 (Total standalone value = ₹1,40,00,000). The bank receives the license and implementation is completed on 30th September 2025.

Step-by-Step Allocation & Revenue Schedule:

Step 1 & 2: Performance Obligations: Because the implementation is routine and does not significantly customize or modify the software code, the license, implementation, and AMC are all distinct performance obligations (3 separate obligations).
Step 3: Transaction Price: Total fixed consideration = ₹1,20,00,000.
Step 4: Relative Stand-Alone Selling Price Allocation:
- Total Stand-Alone Price = ₹70L + ₹30L + ₹40L = ₹1,40,00,000.
- Discount = ₹1,40,00,000 - ₹1,20,00,000 = ₹20,00,000 (Allocated proportionately).
- License Allocation: (₹70L / ₹140L) × ₹1,20,00,000 = ₹60,00,000 (50%).
- Implementation Allocation: (₹30L / ₹140L) × ₹1,20,00,000 = ₹25,71,429 (21.43%).
- 3-Year AMC Allocation: (₹40L / ₹140L) × ₹1,20,00,000 = ₹34,28,571 (28.57%).
Step 5: Revenue Recognition Timing:
- License: Point-in-time on 1st April 2025 (control of software key transferred) = ₹60,00,000 recognized immediately.
- Implementation: Over-time between April and September 2025 = ₹25,71,429 recognized across Q1 and Q2.
- AMC: Over-time straight-line over 36 months starting 1st October 2025 (₹34,28,571 / 36 = ₹95,238 per month). In FY 2025-26 (6 months of AMC), revenue recognized = ₹5,71,428.
- Total FY 2025-26 Revenue Recognized = ₹60L + ₹25.71L + ₹5.71L = ₹91,42,857. The remaining ₹28,57,143 sits as Contract Liability on the Balance Sheet. assureFinancials automatically runs this allocation engine.

Case Study 2: Variable Consideration with Estimation Constraint (Volume Rebates)

Facts: Apex Consumer Goods Ltd. enters into a contract to supply specialty packaging boxes to a retail conglomerate on 1st April 2025. Standard price is ₹100 per box. Contract term: If the customer purchases more than 1,00,000 boxes during FY 2025-26, the price per box for all purchases during the year is retrospectively reduced to ₹80 per box. In Q1 (April to June 2025), the customer purchases 30,000 boxes. Based on historical ordering patterns and market demand, Apex estimates that it is highly probable that the customer's annual purchases will exceed 1,00,000 boxes.

Accounting Mechanics under Paragraphs 53-56:

Identifying Variable Consideration: The retrospective price reduction is variable consideration.
Applying the Constraint Rule: Because it is highly probable that the 1,00,000 threshold will be exceeded, recognizing revenue at ₹100 per box would lead to a significant revenue reversal at year-end. Therefore, Apex must constrain the transaction price to ₹80 per box from Day 1!
Q1 Invoicing vs. Revenue Accounting:
- Invoiced Amount (billed at contract baseline): 30,000 boxes × ₹100 = ₹30,00,000.
- Revenue Recognized in P&L: 30,00,000 / 100 = 30,000 boxes × ₹80 = ₹24,00,000!
- Refund Liability (Contract Liability): ₹30,00,000 - ₹24,00,000 = ₹6,00,000 recorded on the Balance Sheet under Other Current Liabilities.
Audit Protection: If Apex had recognized ₹30 Lakhs, statutory auditors would issue an audit adjustment under Ind AS 115. Setting up automated rebate constraints in assureFinancials eliminates audit friction.

Case Study 3: Long-Term EPC Construction Contract: Over-Time Recognition via Input Method

Facts: Bharat Infra Projects Ltd. entered into a fixed-price contract of ₹50,00,00,000 on 1st April 2025 to construct a railway bridge on land owned by the State Government. Contract duration: 2 years. Total estimated contract costs are ₹40,00,00,000. During Year 1 (FY 2025-26), Bharat incurred actual contract costs of ₹16,00,00,000. Customer was billed ₹15,00,00,000 based on physical milestone inspections, of which ₹12,00,00,000 was collected in cash.

Revenue Recognition & Contract Asset Calculations:

Over-Time Assessment (Paragraph 35(b)): The bridge is constructed on customer-owned land; hence, the asset is enhanced under customer control as construction proceeds. Over-time recognition is mandatory.
Measuring Progress (Input Method - Cost-to-Cost): Progress Percentage = Cumulative Costs Incurred / Total Estimated Costs = ₹16,00,00,000 / ₹40,00,00,000 = 40.0%.
Revenue Recognized in Year 1: Revenue = Total Contract Value × Progress % = ₹50,00,00,000 × 40.0% = ₹20,00,00,000. Contract Cost (P&L) = ₹16,00,00,000. Gross Profit Recognized in Year 1 = ₹20 Cr - ₹16 Cr = ₹4,00,00,000.
Contract Asset vs. Trade Receivable Classification:
- Cumulative Revenue Earned = ₹20,00,00,000
- Less Cumulative Invoiced Amount = ₹15,00,00,000
- Contract Asset (Unbilled Revenue) = ₹5,00,00,000 (Right to payment conditional on next milestone).
- Trade Receivables = Invoiced (₹15 Cr) - Cash Collected (₹12 Cr) = ₹3,00,00,000 (Unconditional right).

Case Study 4: Capitalization of Sales Commissions as Contract Acquisition Costs (Paragraph 91)

Facts: Synergy Telecom Ltd. signed a 3-year enterprise cloud networking contract with a multinational corporation for ₹3,60,00,000. Under the company's sales incentive policy, Synergy paid an upfront cash commission of ₹18,00,000 to the senior sales director specifically for securing this 3-year deal. In addition, Synergy incurred ₹4,00,00,00 / 100 = ₹4,00,000 in travel expenses for pitching the proposal (which were incurred regardless of whether the deal was won or lost).

Contract Cost Accounting Analysis:

Sales Commission (Incremental Cost of Obtaining Contract): Under Paragraph 91, the ₹18,00,000 commission would not have been incurred if the contract had not been obtained. It is an incremental cost. Synergy MUST CAPITALIZE the ₹18,00,000 as an asset (Contract Acquisition Costs)!
- Amortization: Amortized on a systematic basis over the 36-month contract term (₹18,00,000 / 36 = ₹50,000 per month / ₹6,00,000 per year).
Proposal Travel Costs (₹4,00,000): Under Paragraph 93, costs incurred regardless of whether the contract is obtained must be expensed immediately in P&L as administrative expenses. Capitalizing proposal travel costs is illegal under Ind AS 115!

Case Study 5: Significant Financing Component in Customer Advance Payments

Facts: HeavyEng Machines Ltd. signs a contract on 1st April 2025 to manufacture and deliver a customized industrial turbine to a power utility on 31st March 2027 (2 years later). The utility pays an upfront advance of ₹10,00,00,000 on 1st April 2025. If the utility had paid on the delivery date 2 years later, the contract price would have been ₹11,66,40,000, reflecting HeavyEng's incremental borrowing rate of 8% p.a.

Accounting for Significant Financing Component (Paragraph 60):

Recognizing the Financing Element: Because the advance payment is received 2 years prior to delivery, the contract contains a significant financing component where the customer is providing financing to the supplier.
Year 1 Accounting (FY 2025-26):
- 1st April 2025: Cash A/c Dr. ₹10,00,00,000; To Contract Liability Cr. ₹10,00,00,000.
- 31st March 2026: Interest Expense (P&L at 8%) = ₹10,00,00,000 × 8% = ₹80,00,000. Accreted Contract Liability = ₹10,80,00,000.
Year 2 Accounting (FY 2026-27 - Delivery Date):
- Interest Accretion: ₹10,80,00,000 × 8% = ₹86,40,000. Contract Liability reaches ₹11,66,40,000.
- Revenue Recognition on Delivery: Contract Liability A/c Dr. ₹11,66,40,000; To Revenue from Operations Cr. ₹11,66,40,000. Total revenue recognized reflects the true economic value delivered!

Case Study 6: Warranties: Assurance-Type vs. Service-Type Warranties (Paragraph B28)

Facts: Precision Electronics Ltd. manufactures specialized surgical monitoring equipment priced at ₹25,00,000 per unit. Each machine comes with: (a) A mandatory 1-year warranty assuring that the product complies with agreed manufacturing specifications; and (b) An optional 2-year extended repair and preventative maintenance contract for an additional fee of ₹3,00,000. A hospital purchases the equipment along with the 2-year extended warranty on 1st April 2025 for ₹28,00,000.

Bifurcation and Accounting Protocol:

Assurance-Type Warranty (1-Year Mandatory): Under Paragraph B28, a warranty that provides the customer with assurance that the product complies with agreed specifications is an assurance-type warranty. It does NOT represent a separate performance obligation. It is accounted for as a cost provision under Ind AS 37 (Provisions), matching against equipment revenue.
Service-Type Warranty (2-Year Extended): Under Paragraph B29, because the customer has the option to purchase the extended warranty separately, it provides a distinct service. It represents a separate performance obligation!
Allocation: The ₹3,00,00,00 / 100 = ₹3,00,000 consideration is allocated to the service warranty and deferred as a Contract Liability. It is recognized as revenue over-time on a straight-line basis over Years 2 and 3 (₹1,50,000 per year). Equipment revenue of ₹25,00,000 is recognized immediately on delivery.

Case Study 7: Non-Refundable Upfront Initiation / Joining Fees

Facts: FitnessClub Chain Ltd. charges an upfront non-refundable "Joining & Registration Fee" of ₹12,000 plus an ongoing monthly subscription fee of ₹2,000 per month. Joining involves creating a member profile and issuing a digital RFID key card (activity cost ₹500). Average member tenure before cancellation is 24 months.

Accounting Treatment under Paragraph B49:

Assessing Distinct Service: Does setting up the member profile and issuing an RFID card transfer a distinct service to the member? Under Paragraph B49, setup activities do NOT transfer a promised good or service to the customer; they are administrative tasks.
Deferral and Amortization: The non-refundable upfront fee of ₹12,000 is an advance payment for future fitness services! It must be recognized as a Contract Liability and amortized over the estimated customer relationship period (24 months) at ₹500 per month.
Monthly P&L Recognition: Total monthly revenue recognized per member = ₹2,000 (monthly fee) + ₹500 (amortized upfront fee) = ₹2,500 per month. Recognizing the entire ₹12,000 on Day 1 is an audit violation!

Case Study 8: Principal vs. Agent Assessment (Gross vs. Net Revenue Presentation)

Facts: TravelLink Portal Ltd. operates an online flight booking website. When a traveler books an Indigo flight ticket for ₹10,000 through the portal, TravelLink charges the traveler ₹10,000. TravelLink remits ₹9,400 to Indigo and retains ₹600 as its booking commission. TravelLink does not purchase the airline seat inventory in advance and bears zero inventory risk if seats remain unsold.

Control Evaluation under Paragraphs B34-B38:

The Control Principle: An entity is a Principal if it controls the specified good or service before it is transferred to the customer (recognizing revenue on a gross basis). An entity is an Agent if its obligation is to arrange for the provision of goods/services by another party (recognizing revenue on a net basis).
Evaluating Indicators of Control:
- Primary Responsibility: The airline (Indigo) is primarily responsible for performing the flight service.
- Inventory Risk: TravelLink bears NO inventory risk before or after ticket issuance.
- Pricing Discretion: Base ticket pricing is established by the airline.
Verdict: TravelLink is an Agent. Reporting ₹10,000 as Gross Revenue in P&L would massively inflate turnover and deceive investors! TravelLink must report Net Revenue of ₹600 in its Statement of Profit and Loss. Finance teams use assureFinancials to automate principal vs agent classifications.

10-Step Audit Verification Matrix for Ind AS 115 Compliance

Statutory audit teams and revenue accounting controllers must execute a structured verification protocol to certify Ind AS 115 revenue integrity. The following 10-step matrix outlines the audit program:

Step	Audit Dimension	Verification Protocol & Substantive Testing	Compliance Deliverable
1	Contract Identification & Enforceability	Audit signed customer agreements. Verify commercial substance, collectability thresholds, and formal written approval under Paragraph 9.	Contract Scope Verification Memo
2	Performance Obligation Unbundling	Decompose multi-element contracts into distinct goods/services. Test whether promises are separately identifiable under Paragraph 27.	Performance Obligation Schedule
3	Transaction Price & Rebate Constraints	Audit variable consideration models (volume rebates, discounts, penalties). Verify application of the "highly probable" constraint test.	Variable Consideration Workpaper
4	Significant Financing Component Check	Review customer advances and deferred payment terms exceeding 12 months. Ensure imputed interest is bifurcated from revenue.	Financing Component Calculation Sheet
5	Stand-Alone Selling Price Allocation	Audit relative stand-alone selling price (SSP) allocation methodologies. Verify observable price lists and cost-plus models under Step 4.	SSP Allocation Matrix Dossier
6	Over-Time vs. Point-in-Time Testing	Scrutinize Paragraph 35 criteria: simultaneous consumption, asset enhancement, or no alternative use with enforceable right to payment.	Revenue Timing Determination Note
7	Input Method & Cost Progress Audit	For over-time contracts, verify cumulative cost-to-cost progress percentages, accrued contract costs, and test for uninstalled materials.	POC Progress Certification File
8	Contract Assets & Liabilities True-Up	Reconcile contract assets (unbilled revenue) and contract liabilities (advances) against general ledgers and test for ECL impairment.	Contract Balance Reconciliation Sheet
9	Sales Commission Capitalization Check	Audit incremental contract acquisition costs. Verify capitalization of sales commissions and test amortization schedules under Paragraph 91.	Contract Cost Amortization Ledger
10	Comprehensive Footnote Disclosures	Verify mandatory disclosures under Paragraphs 110-129: disaggregation of revenue, transaction price allocated to remaining obligations.	Ind AS 115 Disclosure Note Docket

Mandatory Disclosure Architecture under Paragraphs 110 to 129

Ind AS 115 enforces unprecedented levels of financial footnote disclosure:

Disaggregation of Revenue (Paragraph 114): Revenue disaggregated into categories that depict how nature, amount, timing, and uncertainty of revenue and cash flows are affected by economic factors: (a) primary geographical markets; (b) major product/service lines; (c) contract duration (short-term vs long-term); and (d) timing of transfer (point-in-time vs over-time).
Contract Balances (Paragraph 116): Opening and closing balances of contract assets, contract liabilities, and receivables; revenue recognized in the period that was included in opening contract liabilities; and explanation of significant changes in contract balances.
Transaction Price Allocated to Remaining Performance Obligations (Order Book - Paragraph 120): Disclosure of aggregate amount of transaction price allocated to unsatisfied performance obligations as of reporting date, with quantitative time bands showing when the entity expects to recognize that revenue (<1 yr, 1-2 yrs, >2 yrs).

By preparing financial statements through assureFinancials, corporate finance leaders automate revenue disaggregation tables, manage multi-year contract asset schedules, and ensure flawless compliance with NFRA accounting mandates.

Frequently Asked Questions (FAQs) for Corporate Practitioners

Below are 16 detailed, practitioner-grade answers to the most common technical and practical questions regarding Ind AS 115:

Q1: Can an entity recognize revenue upon raising an invoice if goods have not been delivered?

Answer: Generally, no. Under Ind AS 115, revenue is recognized upon the transfer of control of the goods, not upon invoice issuance. Invoicing prior to delivery without satisfying the strict "bill-and-hold" criteria (Paragraph B81) represents an unlawful premature revenue acceleration.

Q2: What are the mandatory conditions for recognizing revenue under a "Bill-and-Hold" arrangement?

Answer: Under Paragraph B81, four cumulative criteria must be met: (1) The reason for bill-and-hold must be substantive (requested by customer); (2) The product must be identified separately as belonging to the customer; (3) The product must be ready for physical transfer; and (4) The entity cannot have the ability to use the product or direct it to another customer.

Q3: What is the practical expedient for incremental contract acquisition costs?

Answer: Under Paragraph 94, an entity may expense the incremental costs of obtaining a contract (e.g., sales commissions) immediately in P&L if the amortization period of the asset that would have been recognized is one year or less.

Q4: How are customer loyalty points accounted for under Ind AS 115?

Answer: Customer loyalty points grant the customer a material right. Under Paragraph B40, loyalty points represent a separate performance obligation. A portion of the transaction price must be allocated to the points based on their relative stand-alone selling price and deferred as a contract liability until points are redeemed or expire.

Q5: Does Ind AS 115 apply to lease contracts or insurance contracts?

Answer: No. Paragraph 5 explicitly excludes lease contracts (governed by Ind AS 116), insurance contracts (governed by Ind AS 104), and financial instruments (governed by Ind AS 109) from the scope of Ind AS 115.

Q6: When does an entity have an "enforceable right to payment" for over-time recognition?

Answer: An enforceable right to payment under Paragraph 35(c) exists if, in the event of contract termination by the customer for reasons other than the entity's failure to perform, the entity is legally entitled to compensation that approximates the sales value of performance completed to date (including cost plus a reasonable profit margin).

Q7: How should uninstalled materials be treated in calculating progress under the Input Method?

Answer: Under Paragraph B19, if a contractor incurs significant costs for materials delivered to a site that have not yet been installed or customized (e.g., standard elevators or steel delivered to site), the cost of those uninstalled materials must be excluded from the progress percentage, recognizing revenue strictly equal to the cost of those materials (zero profit margin) to prevent revenue distortion!

Q8: What is the difference between a Contract Asset and an Unbilled Receivable?

Answer: A contract asset is a right to consideration conditional on something other than the passage of time (e.g., future milestone completion). An unbilled receivable is an unconditional right to consideration where only the clerical passage of time is required before generating the invoice.

Q9: How is consideration payable to a customer presented in the financial statements?

Answer: Under Paragraph 70, consideration payable to a customer (such as slotting fees or listing allowances) must be accounted for as a reduction of revenue, unless the payment is in exchange for a distinct good or service received from the customer.

Q10: Can an entity use the Residual Approach to allocate transaction prices?

Answer: The residual approach is permitted under Paragraph 79(c) ONLY if: (a) the entity sells the same good/service to different customers for a broad range of amounts (highly variable); or (b) the entity has not yet established a price for that good/service and it has not previously been sold on a standalone basis (uncertain).

Q11: How does Ind AS 115 treat non-refundable upfront membership fees?

Answer: Upfront joining or initiation fees do not transfer a distinct service. They are treated as advance payments for future services, recognized as contract liabilities, and amortized over the estimated customer relationship period.

Q12: How are liquidated damages for construction delays accounted for?

Answer: Liquidated damages represent negative variable consideration. Under Paragraph 51, the expected penalty must be estimated and deducted from the transaction price from the moment delay becomes probable, directly reducing recognized revenue.

Q13: Does an exchange of similar goods between oil companies to facilitate distribution create revenue?

Answer: Under Paragraph 5(d), non-monetary exchanges between entities in the same line of business to facilitate sales to customers (e.g., an exchange of oil between two petrochemical firms to fulfill local demand) do NOT generate revenue under Ind AS 115.

Q14: How are contract modifications accounted for under Ind AS 115?

Answer: A contract modification is accounted for: (a) As a separate contract if it adds distinct goods at stand-alone prices; (b) Prospectively if remaining goods are distinct; or (c) On a cumulative catch-up basis as part of the original contract if remaining goods are not distinct.

Q15: What is the practical expedient for disclosing remaining performance obligations?

Answer: Under Paragraph 121, an entity need not disclose the transaction price allocated to remaining obligations if: (a) the performance obligation is part of a contract that has an original expected duration of one year or less; or (b) revenue is recognized using the "right to invoice" expedient.

Q16: How does assureFinancials automate Ind AS 115 revenue accounting?

Answer: assureFinancials delivers a specialized enterprise revenue automation suite: it unbundles multi-element contracts, allocates transaction prices using relative SSP algorithms, manages variable consideration constraint models, computes percentage-of-completion progress schedules, automates contract asset/liability ledgers, and generates ready-to-publish Ind AS 115 disaggregated disclosure notes.