Ind AS 115 Five-Step Model: A Practical Revenue Recognition Map

Ind AS 115 organises revenue recognition around a five-step model that follows the transfer of promised goods or services to customers. The model moves from identifying the contract and performance obligations to determining and allocating the transaction price and then recognising revenue when or as performance obligations are satisfied. 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. The steps are sequential, and an error early in the chain can distort every later measurement. A robust approach connects commercial substance, the Ind AS 115 decision criteria, measurement evidence and presentation consequences in one coherent file.

Identify the contract with the customer

The technical anchor. An arrangement enters the model when the specified contract criteria are met, including approval, identifiable rights and payment terms, commercial substance and the relevant collectability assessment. In application, finance should consider written terms, side letters, customary practices and contract-combination requirements rather than relying on invoice setup. A frequent failure mode is starting revenue accounting from billing data without proving the contract boundary. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.

Identify distinct performance obligations

The accounting logic. Promised goods or services are assessed to determine whether they are distinct and therefore accounted for separately or combined with other promises. Operationally, contract review should identify explicit and implicit promises, integration services and dependencies between deliverables. The main judgement risk is treating every line item as a separate performance obligation or bundling everything into one without analysis. 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.

Determine the transaction price

The decision point. The expected consideration can include fixed amounts, variable consideration, financing effects, non-cash consideration and amounts payable to the customer. For implementation, estimates should reflect constraint requirements and be updated when facts change. Where errors often arise is using the contract's headline value as revenue without analysing variable or financing components. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.

Allocate to performance obligations

The core requirement. Transaction price is generally allocated based on relative standalone selling prices, with specified exceptions for discounts or variable consideration that relate entirely to particular obligations. In a controlled close process, entities should establish observable prices or estimation methods for items not sold separately. A common weakness is allocating consideration according to internal cost or invoice line amounts simply because those data are available. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.

Recognise revenue on transfer of control

The principle. Revenue is recognised when or as each performance obligation is satisfied, either over time when the criteria are met or at a point in time otherwise. For a review-ready file, the entity should connect the selected measure of progress or transfer indicator to evidence of customer control. The risk to avoid is using billing milestones as automatic evidence of performance. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.

Practical illustration

Assume a software provider sells a licence, implementation and two years of support for one bundled price. The accounting cannot start by spreading the invoice over two years. Finance must first determine the contract, identify which promises are distinct, determine and allocate the transaction price, and then recognise each allocated amount according to the pattern of control transfer. 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 contract review; performance-obligation register; transaction-price approval; standalone-selling-price governance; and revenue-to-subledger reconciliation. 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

The five-step model is most useful when each step is documented as a decision with a clear input and output feeding the next step. 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.