Standalone Selling Prices and Revenue Allocation under Ind AS 115

Once performance obligations are identified, Ind AS 115 generally allocates the transaction price based on relative standalone selling prices at contract inception. Observable prices are preferred, but many bundles include products or services not sold separately, making estimation an important accounting judgement. For finance teams, the practical challenge is to translate that principle into a repeatable conclusion supported by evidence, rather than treating the standard as a year-end checklist. Poor allocation can shift revenue between products and periods even when total contract consideration is correct. A robust approach connects commercial substance, the Ind AS 115 decision criteria, measurement evidence and presentation consequences in one coherent file.

Use observable standalone prices when available

The technical anchor. The best evidence is the price at which the entity separately sells the promised good or service to similar customers in similar circumstances. In application, pricing databases should distinguish true standalone transactions from discounted bundles or strategic exceptions. A frequent failure mode is using list price automatically when actual standalone sales show a different pattern. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Estimate unobservable prices systematically

The accounting logic. Appropriate methods can include adjusted market assessment, expected cost plus margin or, in limited circumstances, a residual approach when the relevant conditions are satisfied. Operationally, the method should maximise observable inputs and be applied consistently to similar goods or services. The main judgement risk is choosing a residual method merely because direct estimation is difficult. Where the conclusion is sensitive to a contractual clause or estimate, the file should show the alternative outcome and why the selected treatment is more appropriate.

Allocate discounts with discipline

The decision point. A discount is normally allocated proportionately to all performance obligations unless observable evidence demonstrates that the entire discount relates to one or more specific obligations. For implementation, finance should analyse standalone pricing patterns and contractual evidence before concentrating a discount. Where errors often arise is allocating the discount to the item with the highest margin to accelerate revenue. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Allocate variable consideration where appropriate

The core requirement. Variable consideration can be allocated entirely to a specific performance obligation or distinct good or service when the terms relate specifically to that item and the allocation is consistent with the allocation objective. In a controlled close process, bonus and usage terms should be linked to the performance they are designed to reward. A common weakness is spreading a service-level bonus across unrelated hardware simply because all items are in one contract. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Control pricing updates and contract inception dates

The principle. Standalone selling prices are determined at contract inception and are not reallocated merely because prices subsequently change. For a review-ready file, systems should retain the price evidence used for each contract version. The risk to avoid is refreshing old contracts with current price lists and thereby rewriting prior allocation. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Practical illustration

Assume a company sells equipment and three years of maintenance for ₹1.1 million. Observable standalone prices are ₹1.0 million for the equipment and ₹300,000 for maintenance. The bundle discount is generally allocated on relative standalone selling prices unless evidence supports a more specific allocation, rather than simply assigning the invoice labels chosen by sales. The illustration is deliberately simplified: its purpose is to show how the accounting conclusion follows the underlying facts rather than to prescribe a single mechanical answer for every entity. Before posting an entry, the preparer should reconcile contractual terms, management's commercial intent, relevant estimates and system data to the specific accounting requirement. Where the outcome is sensitive, the file should show the key judgement and explain why the selected assumption is reasonable at the reporting date.

Documentation and control points

Professional application depends as much on process quality as technical knowledge. For this topic, a minimum control set should cover standalone-price database; estimation methodology; discount allocation review; variable-consideration mapping; and contract-inception price freeze. Ownership should be clear between the business, finance and any legal, tax, valuation, credit-risk or other specialists whose evidence is required. Source data should be dated and version-controlled; manual adjustments should show preparer, reviewer, rationale and approval. The final accounting memorandum should connect the conclusion to the general ledger or relevant subledger, presentation and disclosures. If facts or estimates change, the entity should reassess the conclusion when required and preserve an audit trail explaining the change.

Closing perspective

Revenue allocation is an evidence-based pricing exercise whose purpose is to depict the consideration attributable to each promised transfer. The most useful way to apply Ind AS 115 is to treat the requirement as a decision framework rather than a compliance slogan. When the facts, accounting criteria, measurement evidence, controls and disclosure implications are considered together, the result is more consistent across reporting periods and easier to explain to management, auditors and users of the financial statements.