Ind AS 115 Revenue from Contracts with Customers: 5-Step Model, Variable Consideration & POCM Guide

1. Executive Overview & The Unified Principle of Revenue Recognition

Revenue is the single most critical top-line financial metric reported by commercial enterprises, serving as the foundational benchmark for equity valuations, credit ratings, debt covenant compliance, and corporate taxation. Under legacy Indian Generally Accepted Accounting Principles (Indian GAAP), revenue recognition was governed by a fragmented collection of standards: Accounting Standard (AS) 9 'Revenue Recognition' (which governed sales of goods and rendering of services based on the transfer of significant risks and rewards of ownership) and AS 7 'Construction Contracts' (which applied the percentage of completion method to long-term projects). This fragmented legacy model produced severe industry-specific inconsistencies, permitted early recognition of unearned revenue, and struggled to account for modern bundled commercial contracts featuring hardware, software licensing, cloud hosting, and multi-year warranties.

The notification of Indian Accounting Standard (Ind AS) 115 'Revenue from Contracts with Customers' by the Ministry of Corporate Affairs (MCA), fully converged with IFRS 15, permanently replaced legacy Ind AS 18 and Ind AS 11. Ind AS 115 establishes a single, comprehensive, principles-based revenue recognition framework applicable across all industries and commercial sectors. The core principle of Ind AS 115 mandates that an entity shall recognize 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.

This core principle is operationalized through an immutable Five-Step Revenue Model. Implementing Ind AS 115 requires financial controllers to unbundle multi-element commercial contracts into distinct performance obligations, estimate variable consideration subject to statutory constraint rules, determine Standalone Selling Prices (SSP), and distinguish between revenue recognized at a point in time versus revenue recognized over time (using input or output POCM methods). Furthermore, the standard introduces new balance sheet categories—Contract Assets (Unbilled Revenue) and Contract Liabilities (Deferred Revenue)—while demanding extensive qualitative and quantitative footnote disclosures under Schedule III. Deploying integrated financial automation platforms like assureFinancials and tax reconciliation suites like assureTax is essential for corporate finance teams to manage contract lifecycles and ensure total audit readiness.

2. Statutory Architecture: Ind AS 115 versus Legacy Standards Comparison

Corporate financial reporting teams must master the conceptual divergences between Ind AS 115 and the legacy revenue recognition framework:

Reporting Dimension	Legacy Framework (AS 9 / Ind AS 18 & 11)	Modern Standard (Ind AS 115)
Core Recognition Criterion	Transfer of significant risks and rewards of ownership to the buyer.	Transfer of Control of the promised goods or services to the customer.
Contract Evaluation Model	Transaction-level rules; guidance varied between goods, services, and construction.	A single, unified Five-Step Revenue Recognition Model applied uniformly across all contracts.
Bundled Multi-Element Contracts	Limited guidance; revenue frequently recognized on composite basis upon physical delivery.	Mandatory unbundling of distinct performance obligations, with consideration allocated based on relative Standalone Selling Prices (SSP).
Variable Consideration (Discounts/Rebates)	Recognized when uncertainty was resolved; volume discounts often recognized post-facto.	Estimated upfront using Expected Value or Most Likely Amount, subject to the strict Constraint Rule (probable that no significant reversal will occur).
Customer Loyalty Programs	Accounted for under deferred revenue or incremental cost provisions.	Accounted for as a distinct performance obligation (Material Right), deferring consideration based on relative standalone value.
Balance Sheet Terminology	"Unbilled Revenue" and "Advances from Customers" grouped under generic current assets/liabilities.	Strict classification into Contract Assets (conditional right to payment), Receivables (unconditional right), and Contract Liabilities (unearned revenue).
Warranties	Treated as a cost accrual provision under AS 29 / Ind AS 37.	Bifurcated into Assurance-Type (Ind AS 37 provision) vs Service-Type (distinct performance obligation recognized over time).

3. Deep-Dive Technical Mechanics: The 5-Step Revenue Recognition Model

3.1 Step 1: Identify the Contract with a Customer

Under paragraph 9 of Ind AS 115, a contract with a customer exists only if all five statutory criteria are satisfied:

1. The parties have approved the contract (in writing, orally, or in accordance with customary business practices) and are committed to perform their obligations;
2. The entity can identify each party's rights regarding the goods or services to be transferred;
3. The entity can identify the payment terms for the goods or services;
4. 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); and
5. It is probable that the entity will collect the consideration to which it will be entitled in exchange for the goods or services transferred (evaluating the customer's credit risk profile).

If a contract does not meet these criteria, any upfront consideration received is recognized as a liability, and cannot be recognized as revenue until the criteria are met or the contract is terminated.

3.2 Step 2: Identify Distinct Performance Obligations

Under paragraph 22, at contract inception, the entity shall assess the goods or services promised in a contract and identify as a performance obligation each promise to transfer to the customer either: (a) a good or service (or bundle of goods or services) that is distinct; or (b) a series of distinct goods or services that are substantially the same and have the same pattern of transfer.

A good or service is "distinct" if both of the following criteria are satisfied:

• 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; AND
• Distinct within the context of the contract: The entity's promise to transfer the good or service is separately identifiable from other promises in the contract. A good or service is NOT separately identifiable if:
  1. The entity provides a significant service of integrating the goods or services into a combined output (e.g., EPC construction);
  2. One or more goods or services significantly modify or customize another; or
  3. The goods or services are highly interdependent or highly interrelated.

3.3 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, excluding amounts collected on behalf of third parties (e.g., GST). Determining the transaction price requires evaluating four major components:

1. Variable Consideration: If consideration includes discounts, rebates, refunds, credits, price concessions, penalties, or performance bonuses, the entity estimates the variable amount using either: (a) The Expected Value Method (probability-weighted average); or (b) The Most Likely Amount Method (single most likely outcome).

   The Variable Consideration Constraint: Under paragraph 56, variable consideration is included 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 is subsequently resolved.

2. Significant Financing Component: If the timing of payments agreed by the parties provides the customer or entity with a significant benefit of financing (e.g., payments deferred for 2 years or advanced 2 years prior), the transaction price must be adjusted for the time value of money using a discount rate reflecting credit risk.
3. Non-Cash Consideration: Measured at fair value under Ind AS 113.
4. Consideration Payable to Customer: Volume rebates or listing fees paid to customers reduce the transaction price unless paid for a distinct good or service.

3.4 Step 4: Allocate Transaction Price to Performance Obligations

The entity must allocate the transaction price to each performance obligation identified in the contract on a relative Standalone Selling Price (SSP) basis at contract inception:

• Observable Price: The best evidence of SSP is the observable price of a good or service when the entity sells that good or service separately in similar circumstances.
• Estimation Methods (When SSP is not directly observable):
  1. Adjusted Market Assessment Approach: Evaluate the market and estimate the price that customers would be willing to pay;
  2. Expected Cost Plus a Margin Approach: Forecast expected costs of satisfying the obligation and add an appropriate commercial margin;
  3. Residual Approach: Permissible strictly if the standalone selling price is highly variable or uncertain, subtracting observable standalone selling prices of other items from total transaction price.

3.5 Step 5: Recognize Revenue as Performance Obligations are Satisfied

Revenue is recognized when (or as) the entity satisfies a performance obligation by transferring a promised good or service (i.e., when the customer obtains control of that asset):

• Performance Obligations Satisfied Over Time: An entity transfers control of a good or service over time and recognizes revenue over time if any ONE of the following three criteria is met:
  1. The customer simultaneously receives and consumes the benefits provided by the entity's performance (e.g., security services, routine payroll processing);
  2. The entity's performance creates or enhances an asset that the customer controls as the asset is created or enhanced (e.g., constructing a building on customer-owned land); OR
  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., specialized customized defense equipment).

  Methods of Measuring Progress Over Time:

  • Input Methods: Recognizing revenue based on efforts or inputs expended relative to total expected inputs (e.g., Cost-to-Cost / Percentage of Completion Method - POCM: Cumulative Revenue = (Costs Incurred to Date / Total Estimated Contract Costs) × Total Contract Price).
  • Output Methods: Recognizing revenue based on direct measurements of value transferred to date (e.g., milestones reached, units produced, surveys of performance).

• Performance Obligations Satisfied at a Point in Time: If an obligation is not satisfied over time, it is satisfied at a point in time. Indicators of transfer of control include: (a) entity has present right to payment; (b) customer has legal title; (c) entity has transferred physical possession; (d) customer has significant risks and rewards of ownership; and (e) customer has accepted the asset.

3.6 Contract Assets vs Contract Liabilities vs Receivables

Ind AS 115 establishes precise balance sheet demarcation:

• Receivable: An entity's right to consideration that is unconditional (only the passage of time is required before payment is due).
• Contract Asset (Unbilled Revenue): An entity's right to consideration in exchange for goods or services transferred to the customer, but the right is conditional on something other than the passage of time (e.g., future satisfaction of another performance obligation in a milestone contract).
• Contract Liability (Deferred Revenue): An entity's obligation to transfer goods or services to a customer for which the entity has received consideration (or an advance payment is due) from the customer.

4. Practical Examples, Case Studies & Numerical Illustrations

The following real-world case studies illustrate the exact mathematical allocations, POCM models, and balance sheet transitions under Ind AS 115.

Case Study 1: Enterprise Software Multi-Element Bundling (License + Implementation + AMC)

Context & Contract Terms: On April 1, 2024, CloudEnterprise Ltd enters into a composite software contract with a corporate banking client for a bundled price of ₹1,00,00,000. The contract comprises three components:

• Component 1: Term Software License for 3 years (delivered electronically on April 1, 2024). Standalone Selling Price (SSP) = ₹60,00,000.
• Component 2: Customization & Implementation Services (delivered over 6 months, completed September 30, 2024). SSP = ₹40,00,000.
• Component 3: Annual Maintenance & Support (AMC) for 3 years (April 1, 2024 to March 31, 2027). SSP = ₹20,00,000.
• Total Standalone Selling Prices = ₹60L + ₹40L + ₹20L = ₹1,20,00,000. Contract Bundled Price = ₹1,00,00,000 (Discount: ₹20,00,000 / 16.67%).

Step-by-Step Allocation & Revenue Profile:

1. Relative Standalone Selling Price Allocation:
   • Software License: (₹60L / ₹120L) × ₹1,00,00,000 = ₹50,00,000 (50%)
   • Implementation Services: (₹40L / ₹120L) × ₹1,00,00,000 = ₹33,33,333 (33.33%)
   • 3-Year AMC: (₹20L / ₹120L) × ₹1,00,00,000 = ₹16,66,667 (16.67%)
2. Distinct Test Analysis:
   • If the software requires significant customization without which it cannot function, the license and implementation are NOT distinct in the context of the contract and must be combined.
   • Assuming the bank can use the software out-of-the-box and implementation is standard, they are separate distinct obligations.
3. Revenue Recognition for FY 2024-25 (Year 1):
   • Software License: Point-in-time transfer on April 1, 2024 = ₹50,00,000 recognized immediately.
   • Implementation: Over-time recognition completed on September 30, 2024 = ₹33,33,333 recognized in full.
   • AMC: Recognized straight-line over 36 months. Year 1 (12 months) = (12 / 36) × ₹16,66,667 = ₹5,55,556 recognized. Unearned AMC of ₹11,11,111 is classified as Contract Liability.
   • Total Year 1 Revenue Recognized = ₹50,00,000 + ₹33,33,333 + ₹5,55,556 = ₹88,88,889. Managing bundled contract allocations via assureFinancials guarantees automated Schedule III revenue schedules.

Case Study 2: Long-Term EPC Construction Contract under Cost-to-Cost POCM

Context & Facts: InfraBuild Ltd undertakes a fixed-price construction contract to build an industrial port terminal for ₹150 Crore. Total estimated contract costs are ₹120 Crore (Expected Profit: ₹30 Crore). The project satisfies the over-time criteria under paragraph 35(b) (asset created on customer land).

Year 1 Operational Financials:

• Actual contract costs incurred in Year 1: ₹36,00,00,000
• Total estimated contract costs remain unchanged at ₹120,00,00,000
• Progressive milestone bills raised on customer during Year 1: ₹30,00,00,000
• Cash collected from customer in Year 1: ₹25,00,00,000

POCM Mathematical Execution & Balance Sheet Presentation:

1. Percentage of Completion (Input Method):
   Progress % = Cumulative Costs Incurred / Total Estimated Costs = ₹36 Cr / ₹120 Cr = 30.00%
2. Cumulative Revenue Earned:
   Revenue = 30% × Total Contract Price = 30% × ₹150,00,00,000 = ₹45,00,00,000
3. Cost of Sales Recognized in P&L: ₹36,00,00,000; Operating Profit = ₹9,00,00,000.
4. Contract Asset vs Receivable Determination:
   • Cumulative Revenue Recognized: ₹45,00,00,000
   • Less: Progressive Milestone Billings Raised: (₹30,00,00,000)
   • Contract Asset (Unbilled Revenue): ₹15,00,00,000 (Classified under Current Assets).
   • Trade Receivables = Total Billed (₹30 Cr) − Cash Collected (₹25 Cr) = ₹5,00,00,000.
5. Tracking input cost metrics in assureFinancials prevents unbilled revenue distortions during audit reviews.

Case Study 3: Variable Consideration with Volume Rebate & Statutory Constraint

Context & Facts: ChemCorp Ltd contracts to sell specialty chemical drums to a distributor for ₹10,000 per drum. The contract specifies: if the distributor purchases more than 1,000 drums in the financial year, the price per drum for ALL drums purchased during the year is retrospectively reduced to ₹8,50,0? No, ₹8,500 per drum (a retrospective rebate of ₹1,500 per drum).

Quarterly Progression & Constraint Application:

• Q1 (Sales: 200 drums): ChemCorp historical experience indicates the distributor will not exceed 1,000 drums. High probability of no rebate. ChemCorp recognizes revenue at ₹10,000 per drum = 200 × ₹10,000 = ₹20,00,000.
• Q2 (Sales: 350 drums, Cumulative: 550 drums): Distributor expands retail network; management determines it is now highly probable that cumulative purchases will exceed 1,000 drums by year-end.
• Application of Constraint & Cumulative Catch-Up:
  • Transaction price is revised to ₹8,500 per drum for all 550 drums.
  • Cumulative Revenue required at end of Q2 = 550 × ₹8,500 = ₹46,75,000.
  • Less: Revenue recognized in Q1 = (₹20,00,000).
  • Q2 Revenue Recognized = ₹46,75,000 − ₹20,00,000 = ₹26,75,000.
  • The difference of ₹8,25,000 (550 × ₹1,500) is credited to a Refund Liability, matching invoices in GSTR-1. Reconciling volume rebate liabilities in assureTax prevents GST return mismatches.

Case Study 4: Extended Warranty Accounting (Assurance-Type vs Service-Type)

Context & Facts: AutoDrive Ltd sells an electric SUV for ₹20,00,000 on May 1, 2024. The sale includes: (a) A mandatory 2-year manufacturer warranty guaranteeing freedom from manufacturing defects (Assurance-Type); and (b) An optional 3-year extended roadside maintenance warranty from Year 3 to Year 5 (Service-Type). The standalone price of the extended warranty is ₹1,00,000.

Accounting Segregation under Paragraph B28–B33:

1. Assurance-Type Warranty (Years 1 & 2): Does not represent a separate performance obligation. It is accounted for as a warranty expense provision under Ind AS 37 based on historical claims data.
2. Service-Type Warranty (Years 3 to 5): Represents a distinct performance obligation because it provides a service beyond assuring product quality.
3. Transaction price of ₹20,00,000 is unbundled: ₹19,00,000 recognized immediately upon vehicle delivery on May 1, 2024.
4. The remaining ₹1,00,000 is recognized as a Contract Liability (Deferred Revenue) and amortized straight-line over Years 3, 4, and 5 as the maintenance service is rendered. Warranty unbundling schedules are maintained in assureFinancials.

Case Study 5: Significant Financing Component in Long-Term Deferred Payment

Context & Facts: MegaMachinery Ltd sells an automated industrial packaging line to a client on April 1, 2024. The cash selling price is ₹80,00,000. Under the contract, the client is permitted to pay ₹1,00,00,000 in a single lump sum after 2 years on March 31, 2026. The market borrowing rate for the client is 11.80% per annum.

De-Linking Financing from Revenue under Paragraph 60:

• The contract contains a significant financing component (2-year payment deferral).
• Present Value of ₹1,00,00,000 deferred for 2 years @ 11.80% = ₹1,00,00,000 / (1.1180)^2 = ₹80,00,000.
• Revenue Recognized on April 1, 2024: ₹80,00,000 (Strictly the cash selling price).
• The differential ₹20,00,000 is Finance Income recognized over the 2-year credit period using the effective interest method:
  • FY 2024-25 Finance Income = 11.80% × ₹80,00,000 = ₹9,44,000
  • FY 2025-26 Finance Income = 11.80% × ₹89,44,000 = ₹10,56,000
• Treating the full ₹1 Crore as revenue upon delivery violates Ind AS 115 and triggers audit restatements. Financing schedules are automated in assureFinancials.

Case Study 6: Customer Loyalty Points Program (Material Right Deferral)

Context & Facts: Lifestyle Retail operates a loyalty card program. Customers earn 1 loyalty point for every ₹100 spent. Each point is redeemable for ₹5 on future purchases. In October 2024, customers spend ₹1,00,00,000, earning 1,00,000 points. Historical redemption data indicates that 80% of points will be redeemed (80,000 points expected redemption).

Allocation & Deferral under Paragraph B39–B40:

• Estimated Standalone Selling Price of Points = 80,000 expected points × ₹5 = ₹4,00,000.
• Total Standalone Values = Retail Goods (₹1,00,00,000) + Points (₹4,00,000) = ₹1,04,00,000.
• Allocation of ₹1,00,00,000 Revenue:
  • Revenue Allocated to Goods = (₹100L / ₹104L) × ₹1,00,00,000 = ₹96,15,385 recognized immediately.
  • Revenue Allocated to Points (Contract Liability) = (₹4L / ₹104L) × ₹1,00,00,000 = ₹3,84,615 deferred.
• When points are subsequently redeemed in future months, the ₹3,84,615 is released to P&L in proportion to points redeemed. Loyalty program accounting is managed via assurePractice.

Case Study 7: Principal versus Agent Assessment for Digital Marketplace

Context & Facts: MarketBazaar Ltd operates an e-commerce platform. Merchant 'X' lists a laptop for ₹50,000. A customer buys the laptop on the platform for ₹50,000. MarketBazaar remits ₹46,000 to Merchant X and retains a ₹4,000 platform commission. MarketBazaar never takes inventory title or pricing discretion.

Gross versus Net Evaluation under Paragraph B34–B38:

1. Control Test: MarketBazaar does NOT obtain control of the laptop before it is transferred to the customer. Merchant X is primarily responsible for product fulfillment and warranty.
2. Therefore, MarketBazaar is an Agent, not a Principal.
3. Revenue Presentation: MarketBazaar must report revenue on a NET basis = ₹4,00,0? No, ₹4,000 (Commission only). Reporting gross sales of ₹50,000 violates Ind AS 115, artificially inflating company turnover. Financial disclosures are verified in assureFinancials.

5. 10-Step Practitioner Audit Verification Program for Ind AS 115 Compliance

Corporate financial controllers, statutory auditors, and internal audit teams should execute this 10-step audit verification protocol:

Step #	Audit Verification Domain	Key Verification Actions & Evidentiary Records	Standard Reference
Step 1	Contract Enforceability Audit	Inspect executed customer agreements. Verify approval, identifiable payment terms, commercial substance, and customer creditworthiness.	Ind AS 115.9–16
Step 2	Performance Obligation Unbundling	Scrutinize multi-element contracts. Verify whether promises (licenses, hardware, maintenance, training) are distinct standalone and in-context.	Ind AS 115.22–30
Step 3	Transaction Price & Financing Terms	Audit variable consideration, prompt payment discounts, performance penalties, and significant financing terms (> 12 months).	Ind AS 115.47–65
Step 4	Variable Consideration Constraint Testing	Verify whether variable revenue estimates satisfy the high-probability constraint rule. Audit historical reversal patterns.	Ind AS 115.56–58
Step 5	Standalone Selling Price (SSP) Allocation	Review SSP benchmarking documentation (observable prices, cost-plus margins). Verify proportional allocation of contractual discounts.	Ind AS 115.73–86
Step 6	Over-Time Criteria Verification	Audit contracts claiming over-time recognition. Verify enforceable right to payment for performance to date and absence of alternative use.	Ind AS 115.35–37
Step 7	POCM Input / Cost-to-Cost Calculations	Audit total estimated contract costs, engineering progress reports, and actual costs incurred to date. Verify arithmetic progress percentages.	Ind AS 115.39–45
Step 8	Contract Asset & Liability Reconciliation	Reconcile unbilled revenue (Contract Assets) and unearned customer advances (Contract Liabilities) against milestone billing logs.	Ind AS 115.105–109
Step 9	Principal vs Agent Assessment	For platforms, consignment sales, and drop-shipping, verify whether the entity controls the goods before transfer. Confirm gross vs net presentation.	Ind AS 115.B34–B38
Step 10	Schedule III & Note Disclosures	Verify disaggregation of revenue (by market, timing, contract duration), remaining performance obligations (order backlog), and asset movements.	Ind AS 115.110–129

6. Elevating Revenue Accounting with the AssureOffice Suite

Managing multi-element contract allocations, tracking complex POCM construction schedules, and automating Ind AS 115 financial statement disclosures requires integrated enterprise software:

• assureFinancials: The premier financial accounting and consolidation suite. Houses an automated Ind AS 115 Revenue Engine that tracks contract obligations, applies relative Standalone Selling Price allocation algorithms, models variable consideration constraints, calculates POCM cost-to-cost progress percentages, and formats Schedule III revenue disaggregation footnotes with complete audit trails.
• assureTax: Reconciles Ind AS 115 revenue with Income Computation and Disclosure Standards (ICDS IV - Revenue Recognition) for Tax Audit Form 3CD (Clause 13), tracking timing differences for deferred tax under Ind AS 12.
• assurePractice: Empowers chartered accountancy firms and statutory audit teams to manage client contract review checklists, store executed commercial master agreements, and review revenue recognition technical memorandums.
• assureNotice: Organizes corporate accounting records, manages financial statement review inquiries from statutory auditors and NFRA, and maintains evidentiary compliance archives.

7. Comprehensive Practitioner FAQs on Ind AS 115 Revenue Recognition

Q1: Does Ind AS 115 apply to all contracts entered into by a company?

Ind AS 115 applies to all contracts with customers, EXCEPT: lease contracts (Ind AS 116), insurance contracts (Ind AS 104), financial instruments and contractual rights/obligations (Ind AS 109), and non-monetary exchanges between entities in the same line of business to facilitate sales.

Q2: Can revenue be recognized under Ind AS 115 if collectability of consideration is doubtful?

No. Under paragraph 9(e), a contract exists only if it is probable that the entity will collect the consideration to which it is entitled. If collectability is not probable at inception, no revenue can be recognized; any cash received is recognized as a liability.

Q3: What is the primary difference between a Contract Asset and a Trade Receivable?

A Receivable is an unconditional right to consideration (only the passage of time is required before payment is due). A Contract Asset is a right to consideration in exchange for goods or services transferred, but the right is conditional on something other than the passage of time (e.g., completing future milestones).

Q4: How should trade discounts and volume rebates be treated under Ind AS 115?

Trade discounts and volume rebates are classified as variable consideration. They must be estimated upfront using the expected value or most likely amount method, and deducted from the transaction price, subject to the constraint rule.

Q5: What is the "Variable Consideration Constraint"?

Under paragraph 56, variable consideration is included in the transaction price ONLY to the extent that it is highly probable that a significant reversal in cumulative revenue recognized will not occur when the uncertainty is resolved.

Q6: Can an entity recognize revenue over time if the contract does not contain an enforceable right to payment?

No. Under paragraph 35(c), if the asset has no alternative use, the entity MUST have an enforceable right to payment for performance completed to date (covering costs plus a reasonable profit margin) throughout the contract duration. If no enforceable right exists, revenue is recognized at a point in time.

Q7: How are mobilization advances received from customers presented in the Balance Sheet?

Mobilization advances received before satisfying performance obligations are presented as Contract Liabilities (Deferred Revenue) under Current Liabilities, until performance is rendered.

Q8: Are customer loyalty reward points treated as marketing expenses or revenue reductions?

Loyalty points provide the customer with a "Material Right". Under paragraph B39, consideration must be allocated to the points based on their relative standalone selling price, deferring revenue as a contract liability until points are redeemed or expire.

Q9: How are contract modification amendments accounted for under Ind AS 115?

Under paragraph 20, contract modifications are accounted for as a separate contract IF distinct goods/services are added at standalone prices. Otherwise, they are accounted for as a prospective termination and creation of a new contract, or via a cumulative catch-up adjustment to existing revenue.

Q10: When must an entity recognize a Significant Financing Component?

Under paragraph 60, if the agreed payment schedule provides either party with a significant financing benefit (payments delayed or advanced by more than 12 months), the transaction price must be adjusted for the time value of money, recognizing interest income or expense.

Q11: Can the Percentage of Completion Method (POCM) be used under Ind AS 115?

Yes. The Cost-to-Cost method is recognized as an Input Method under paragraph B18 for measuring progress towards complete satisfaction of a performance obligation satisfied over time.

Q12: How are pre-contract tender and bidding costs accounted for?

Costs incurred in bidding for a contract (e.g., travel, legal tender prep) are expensed immediately as incurred, unless they are explicitly chargeable to the customer regardless of whether the contract is obtained.

Q13: What costs can be capitalized as "Costs to Fulfill a Contract"?

Under paragraph 95, costs directly related to a contract (direct labor, direct materials, allocated overheads) that generate or enhance resources utilized in satisfying performance obligations in the future and are expected to be recovered are capitalized as contract fulfillment assets and amortized.

Q14: How does Ind AS 115 treat sales with a right of return?

Revenue is recognized only for goods expected not to be returned, estimated using the variable consideration constraint. An entity recognizes a Refund Liability for cash received for expected returns, and an Asset for the right to recover returned inventory.

Q15: What are the required disclosures under Ind AS 115?

Entities must disclose: disaggregation of revenue into primary categories, opening/closing contract asset and liability balances, transaction price allocated to remaining unsatisfied obligations (order backlog), and significant accounting judgments.

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

assureFinancials automatically unbundles multi-element contracts, allocates consideration based on Standalone Selling Prices, models variable consideration constraint thresholds, tracks POCM cost-to-cost progress percentages, and formats Schedule III revenue disaggregation footnotes with zero manual spreadsheet errors.