
Identifying performance obligations is the step that converts a commercial bundle into accounting units of account. A promised good or service is distinct when the customer can benefit from it on its own or with readily available resources and the promise is separately identifiable within the context of the contract. A professional application therefore needs more than the right journal entry: it needs a controlled decision path from contractual facts and management assumptions to measurement and disclosure. Over-separating or over-combining promises can significantly change the timing and pattern of revenue. A robust approach connects commercial substance, the Ind AS 115 decision criteria, measurement evidence and presentation consequences in one coherent file.
Inventory all promises
The decision point. The analysis includes explicit contractual promises and, where relevant, implied promises arising from customary business practices, published policies or specific statements. For implementation, finance should review sales materials, implementation commitments and customer expectations as well as the legal contract. Where errors often arise is ignoring a material promise because it has no separate invoice line. 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.
Assess capability of being distinct
The core requirement. A customer can benefit from a good or service on its own or together with other resources that are readily available to the customer. In a controlled close process, the analysis should consider whether the item is regularly sold separately and whether another supplier or customer resource can make it useful. A common weakness is concluding an item is not distinct simply because the customer purchased it in a bundle. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.
Assess distinctness in the context of the contract
The principle. Even capable goods or services are combined when the entity provides a significant integration service, one item significantly modifies another, or the promises are highly interdependent or interrelated. For a review-ready file, complex implementation and construction arrangements need a contract-level integration assessment. The risk to avoid is splitting inputs to one combined output into multiple obligations and accelerating revenue. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.
Treat series of services consistently
The technical anchor. A series of distinct goods or services can form one performance obligation when each item would be satisfied over time and the same method would measure progress toward complete satisfaction. In application, recurring services should be tested for the series guidance rather than treated as hundreds of separate daily obligations. A frequent failure mode is creating unnecessary accounting units that all have the same transfer pattern. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.
Document material rights and options
The accounting logic. Customer options for additional goods or services can create a separate performance obligation when they provide a material right the customer would not receive without entering the contract. Operationally, renewal discounts, loyalty points and incremental purchase rights should be compared with standalone pricing. The main judgement risk is treating every future purchase option as either revenue immediately or as a material right without pricing analysis. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.
Practical illustration
Assume an equipment supplier promises a specialised machine and an installation service that significantly modifies the machine so it can operate in the customer's production line. Although installation is a service the supplier can describe separately, the significant integration and modification may mean the machine and installation form one combined performance obligation rather than two. 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 promise inventory; distinctness decision tree; integration assessment; series evaluation; and material-right review. 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
Performance obligations should mirror what the customer is really receiving, not the way the seller happens to structure its price list. 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.
Continue learning on JUMOQ
Turn this guidance into practical capability
Explore focused courses, worked examples and activities related to this topic.
Explore related courses →References
- Ind AS 115, Revenue from Contracts with Customers — ICAI Compendium of Indian Accounting Standards 2025-2026
