Revenue recognition decides when income is recorded in the statement of profit and loss. That timing matters because profit, margins, tax planning, lender reporting, managerial incentives, and audit conclusions can all change if revenue is recorded too early or too late.
At a basic level, revenue is not recognised simply because an invoice was raised or cash was collected. Revenue is recognised when the underlying accounting conditions are met under the reporting framework the entity actually follows.
What revenue recognition means
Under AS 9 on Revenue Recognition, revenue is the gross inflow arising in the ordinary activities of an enterprise from sale of goods, rendering of services, and use by others of enterprise resources yielding interest, royalties, and dividends. The standard focuses heavily on timing, transfer of significant risks and rewards for goods, performance for services, and uncertainty around measurement or collection.
Under Ind AS 115 educational material issued by ICAI, the core principle is different in structure but similar in purpose: revenue should depict the transfer of promised goods or services to a customer in an amount that reflects the consideration the entity expects to be entitled to. In practice, Ind AS 115 is a contract-based model built around performance obligations and transfer of control.
Why the concept matters in professional work
- It affects whether current-period profit is real, deferred, or accelerated.
- It determines whether advances sit as revenue or as a contract liability until performance occurs.
- It changes how discounts, returns, variable consideration, and bundled contracts are measured.
- It often decides whether a reporting issue is a cut-off error, a measurement error, or a disclosure problem.
India framework note: which rules are you even applying?
This is the first question a CA, accountant, or finance team should settle. Revenue recognition is framework-sensitive.
| Framework | Core revenue source | Basic recognition logic |
|---|---|---|
| Accounting Standards framework | AS 9 | Sale of goods, services, interest, royalties, and dividends; focus on transfer of significant risks and rewards, performance, and uncertainty |
| Indian Accounting Standards framework | Ind AS 115 educational material | Identify contract and performance obligations, determine and allocate transaction price, recognise revenue when control transfers |
Change-sensitive note verified from first-party sources: ICAI's Accounting Standards page, last updated on March 24, 2026, states that MCA issued the Companies (Accounting Standards) Rules, 2021 for accounting periods commencing on or after April 1, 2021. ICAI also states that Ind AS became mandatory for certain companies under the notified roadmap from financial year 2016-17. The exact entity-level applicability question depends on the current MCA roadmap for that reporting entity, so the correct starting point is the entity's applicable framework rather than a generic rule of thumb. Relevant first-party pages are ICAI's Accounting Standards page and ICAI's Ind AS implementation page.
How revenue recognition works under AS 9
Sale of goods
AS 9 recognises revenue when the seller has transferred property in the goods for a price, or when significant risks and rewards of ownership have passed, provided there is no significant uncertainty about consideration.
This means an invoice alone is not enough. If the seller still retains meaningful control, has major installation obligations, or faces significant uncertainty in collection or amount, recognition may need to wait.
Rendering of services
AS 9 permits either the proportionate completion method or the completed service contract method, depending on which better relates revenue to work accomplished. That is why service contracts require close attention to the pattern of performance rather than only the billing schedule.
Interest, royalties, and dividends
- Interest is generally recognised on a time basis.
- Royalties are generally recognised on an accrual basis under the agreement.
- Dividends are recognised when the right to receive payment is established.
Uncertainty changes timing
AS 9 is explicit that when measurement or ultimate collection is uncertain, revenue recognition may need to be postponed. If the collectability issue arises after revenue was properly recognised, the standard points toward a separate provision rather than rewriting the original revenue figure.
How revenue recognition works under Ind AS 115
Ind AS 115 uses a contract-based recognition model. The article-level summary is straightforward:
- Identify the contract with the customer.
- Identify the distinct performance obligations.
- Determine the transaction price.
- Allocate that price to the performance obligations.
- Recognise revenue when, or as, each performance obligation is satisfied.
Two features create most of the practical complexity.
1. Distinct promises matter
A single contract may contain separate promises, such as equipment, installation, training, annual maintenance, and post-sale support. If those promises are distinct, revenue may need to be split and recognised on different timelines.
2. Timing depends on transfer of control
Some performance obligations are satisfied at a point in time. Others are satisfied over time. ICAI's educational material summarises the standard's focus on transfer of promised goods or services, and ICAI's July 20, 2018 clarification for real estate specifically states that Ind AS 115 does allow recognition using percentage of completion where the over-time conditions are met.
That clarification is useful beyond real estate because it shows the underlying principle: a long-duration contract does not automatically mean "recognise only on final delivery," and a progress-billing pattern does not automatically mean "recognise as billed." The accounting answer depends on the performance obligation and the standard's over-time criteria. See ICAI's real-estate clarification on Ind AS 115.
AS 9 and Ind AS 115: the practical distinction
| Question | AS 9 | Ind AS 115 |
|---|---|---|
| Main lens | Nature of transaction and timing of performance | Contract, performance obligations, and transfer of control |
| Goods | Focus on transfer of property and significant risks and rewards | Focus on when control of the promised good transfers |
| Services | Proportionate completion or completed service contract method | Recognise as each performance obligation is satisfied, at a point in time or over time |
| Bundled arrangements | Less structured compared with Ind AS 115 | Requires identification of distinct promises and allocation of transaction price |
| Variable consideration | Handled mainly through uncertainty principles | Built into transaction-price assessment and related constraints |
| Balance sheet presentation | Traditional receivable and advance logic | Contract assets, receivables, and contract liabilities become central |
Examples that resolve common confusion
Example 1: Sale of goods before physical delivery
Assumptions: A manufacturer invoices machinery on March 28. The buyer has accepted billing, title passes on March 28, the machine is identified and ready for dispatch, and delivery is delayed only because the buyer requested April dispatch. Collection is reasonably certain.
Treatment: Under AS 9, revenue may be recognised before physical delivery if the substance shows the significant conditions for sale have been met. The key question is not the truck movement alone but whether the seller has effectively completed the sale and no significant uncertainty remains.
Example 2: Annual software licence with implementation support
Assumptions: Total contract value is Rs. 12,00,000. The contract includes a one-year software licence, initial implementation, and quarterly support. Assume the reporting entity follows Ind AS and the promises are assessed as distinct.
Treatment: Revenue may need to be allocated across the licence, implementation, and support obligations rather than recognised entirely on invoice date. If support runs for twelve months, that part is commonly recognised over the support period, not upfront.
Example 3: Customer advance received before performance
Assumptions: A customer pays 40% advance on April 1 for customised goods to be delivered in June. No goods or services have transferred by April 30.
Treatment: The April receipt is not April revenue merely because cash came in. Under Ind AS 115, it would ordinarily remain a contract liability until the relevant performance obligation is satisfied. Under AS 9 as well, advance collection does not by itself justify recognition.
Example 4: Service contract billed monthly but work is uneven
Assumptions: A consulting assignment runs for four months at Rs. 4,00,000 total. Billing is Rs. 1,00,000 per month, but 60% of the substantive work is completed in month 1 and month 2, with only reporting and closure in later months.
Treatment: Billing pattern and revenue pattern may differ. Under AS 9, a method that better relates revenue to work accomplished is preferred. Under Ind AS 115, recognition follows satisfaction of the performance obligation, not invoice timing alone.
Issues that most often change the answer
- Returns, rebates, and price concessions: these affect whether the amount of revenue is reasonably determinable and whether estimates are needed.
- Installation and acceptance clauses: they can delay recognition if the seller still has a substantive obligation.
- Principal versus agent questions: AS 9 itself states that in an agency relationship, revenue is the commission amount and not the gross inflow.
- Collectability problems: expected collection is part of recognition analysis, especially under AS 9 and contract identification under Ind AS 115.
- Multiple deliverables: one signed contract can contain several accounting units.
- Contract modifications: scope and price changes can alter timing and allocation under Ind AS 115.
A compact month-end checklist
- Confirm the entity's reporting framework first: AS or Ind AS.
- Match each major revenue stream to the relevant accounting logic.
- Test cut-off around period end using dispatch, delivery, acceptance, and completion evidence.
- Review advances, unbilled revenue, deferred revenue, contract assets, and contract liabilities separately.
- Scan contracts for clauses on returns, acceptance, penalties, milestones, variable consideration, and cancellation.
- Check whether collection uncertainty existed at initial recognition or arose later.
- Ensure disclosures are consistent with the recognition basis used.
Bottom line
Revenue recognition is fundamentally about performance, control, measurement, and certainty, not simply about invoicing or cash receipt. Under AS 9, the analysis often turns on transfer of significant risks and rewards, completion of service performance, and uncertainty. Under Ind AS 115, the analysis becomes more contract-driven and granular, especially where there are multiple promises, variable consideration, or over-time performance.
For India-facing professional work, the most reliable approach is to begin with the entity's applicable framework and then read the exact revenue stream against the authoritative source. The first-party references most useful for that starting point are ICAI's AS 9 text, ICAI's Ind AS 115 educational material, and ICAI's clarification on over-time recognition in real estate under Ind AS 115.
