
Revenue recognition begins with enforceable rights and obligations, not with an invoice or cash receipt. A contract enters the Ind AS 115 model only when the specified criteria are satisfied, and multiple contracts may need to be combined when their economics are linked. In practice, the accounting works best when commercial facts are separated from the technical assessment and every significant judgement can be traced to source evidence. Getting the contract boundary wrong can move revenue between periods and distort contract assets, liabilities and receivables. A robust approach connects commercial substance, the Ind AS 115 decision criteria, measurement evidence and presentation consequences in one coherent file.
Confirm approval and commitment
The accounting logic. The parties must have approved the arrangement and be committed to perform their respective obligations, taking account of enforceability under applicable law and customary business practices. Operationally, finance should verify executed terms, authority levels and any cancellation rights that undermine enforceability. The main judgement risk is recognising revenue from a proposal or unsigned order that has not created enforceable obligations. Evidence should be retained at the same level of detail as the accounting conclusion, with assumptions version-controlled and exceptions explicitly approved.
Identify rights and payment terms
The decision point. The entity must be able to identify each party's rights regarding goods or services and the payment terms for those goods or services. For implementation, contract abstraction should capture amendments, rebates, milestone provisions and side agreements. Where errors often arise is using a master agreement while ignoring transaction-specific terms that actually determine rights and consideration. The accounting result should reconcile to the underlying contract, valuation or subledger rather than rely on a standalone spreadsheet conclusion.
Assess commercial substance and collectability
The core requirement. The arrangement should change the entity's future cash-flow risk, timing or amount, and the entity should assess whether collection of consideration to which it expects to be entitled is probable within the contract criteria. In a controlled close process, credit assessment should focus on the amount expected in exchange for transferred goods or services rather than mechanically on the stated contract price. A common weakness is equating a customer's weak credit with a variable-price concession without analysing the commercial facts. The working paper should identify the relevant facts, source data, judgement and conclusion so that an independent reviewer can reproduce the decision.
Combine related contracts where required
The principle. Contracts entered into at or near the same time with the same customer or related parties are combined when specified package, pricing or performance-obligation criteria are met. For a review-ready file, sales and finance systems should identify linked negotiations and cross-contract pricing dependencies. The risk to avoid is splitting one negotiated commercial package into multiple contracts to alter timing of revenue. 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.
Handle arrangements that fail the criteria
The technical anchor. Consideration received before a contract qualifies is generally recorded as a liability until the standard's conditions for revenue recognition are met. In application, finance should monitor failed-criteria arrangements and reassess them when facts change. A frequent failure mode is treating non-refundable cash as automatic revenue solely because repayment is unlikely. A concise review note should state the trigger, the rule applied, the evidence considered and the financial-statement consequence.
Practical illustration
Assume a services company receives an upfront payment before both parties sign the final statement of work and the customer can withdraw without substantive penalty. Cash has been received, but finance still needs to assess whether an enforceable contract exists. Until the contract criteria are met or another specified condition applies, the payment does not become revenue merely because it is non-refundable in practice. 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 executed-contract completeness; side-letter capture; credit review; contract-combination screen; and failed-criteria monitoring. 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 contract assessment is the gateway to Ind AS 115; discipline here prevents later revenue calculations from being built on an invalid accounting unit. 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
