Revenue recognition means deciding how much revenue belongs in an accounting period and recording it in the accounts. Receiving payment or issuing an invoice does not settle that question. First check which accounting rules apply, what the business has delivered, and how much it is entitled to receive.
This guide compares AS 9 with Ind AS 115 for Indian financial reporting. It is not a guide to GST time of supply or taxable-income computation; those require a separate analysis.
Two frameworks, one practical question: when is revenue earned?
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 in ICAI's compendium, revenue follows the transfer of promised goods or services to the customer. The amount reflects what the business expects to be entitled to receive. The standard starts with the customer contract and asks which promises have been fulfilled and whether control has passed.
Which set of accounting rules applies?
Check the accounting-framework note in the financial statements and confirm that it is still correct for the period. A business cannot choose AS for one transaction and Ind AS for another simply because one gives an earlier revenue date.
| Framework | Core revenue source | What drives the revenue date? |
|---|---|---|
| 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 | Identify contract and performance obligations, determine and allocate transaction price, recognise revenue when control transfers |
ICAI's Accounting Standards page links the Companies (Accounting Standards) Rules, 2021, applicable for accounting periods beginning on or after 1 April 2021. Its Ind AS implementation page explains the separate roadmap. This comparison assumes that the entity has already established its applicable framework.
Check the transaction scope too. AS 9 excludes construction contracts, hire-purchase and leases, government grants and insurance-contract revenue. Ind AS 115 covers customer contracts, subject to its own exclusions, including leases, insurance contracts and specified financial-instrument rights. Do not apply AS 9's interest-and-dividend section to an Ind AS entity by analogy. See AS 9 paragraph 2 and Ind AS 115 paragraphs 5–8.
How revenue recognition works under AS 9
Sale of goods
AS 9 paragraphs 10–11 require the relevant transfer of property or significant risks and rewards, no retained effective control normally associated with ownership, and no significant uncertainty over consideration. Ultimate collection must also be reasonably expected at performance.
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 uses the method that best matches revenue to the work done. Under proportionate completion, revenue is recorded as the work progresses. Under the completed service contract method, it is recorded when the service is completed or substantially completed. The contract and the importance of any remaining work determine the method; monthly billing alone does not.
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 five steps. A performance obligation is a promise to transfer a distinct good or service, a distinct bundle, or a qualifying series of distinct goods or services. It is the part of the contract for which revenue is assessed.
- 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.
Before applying those steps, check paragraph 9: approval and commitment, identifiable rights and payment terms, commercial substance and probable collection. A signed order alone does not settle every recognition condition.
Separate promises can have different revenue dates
One contract can promise equipment, installation and future support. These may need different revenue dates. To decide whether a promise is distinct, check both whether the customer can benefit from it on its own or with readily available resources, and whether it is separately identifiable from the other promises in the contract.
When can revenue be recorded as work progresses?
Under paragraph 35, over-time recognition requires at least one of these conditions:
- The customer receives and consumes the benefits as the entity performs.
- The work creates or improves an asset that the customer controls as work progresses.
- The asset has no alternative use to the entity, and the entity has an enforceable right to payment for work completed to date.
If none applies, assess point-in-time control transfer under paragraph 38. A long contract or monthly invoices do not, by themselves, justify recording revenue over time. ICAI's real-estate clarification explains why percentage-of-completion recognition is possible, but is not automatic.
Compare the accounting decisions
| 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 |
Four examples at the reporting date
The following examples use fictional contracts and exclude tax. Each conclusion depends on the stated assumptions.
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. Assume the significant risks and rewards have passed, no ownership-like control is retained, no substantive installation or acceptance condition remains, and delivery is expected.
Treatment: These assumptions support March recognition under AS 9 paragraph 11 and illustration A.1. If the machine is still being manufactured, the conclusion changes. An Ind AS entity must separately meet paragraphs B79–B82; the AS 9 conclusion cannot simply be carried across.
Example 2: ₹12 lakh received does not all become April revenue
Assumptions: An Ind AS entity receives ₹12,00,000 on 1 April for equipment, installation and twelve months of stand-ready support. The contract meets paragraph 9. All three promises are assessed as distinct: the equipment is usable with readily available alternative installation services, and this installation does not significantly modify or integrate it. Control of the equipment transfers and installation is completed on 1 April. Support is supplied evenly from April to March. There is no variable consideration or financing adjustment, and no evidence that the discount belongs only to one promise.
| Promise | Stand-alone price | Allocated price |
|---|---|---|
| Equipment | ₹10,00,000 | ₹8,00,000 |
| Installation | ₹1,25,000 | ₹1,00,000 |
| Twelve months of support | ₹3,75,000 | ₹3,00,000 |
| Total | ₹15,00,000 | ₹12,00,000 |
The three separate selling prices total ₹15 lakh, but the customer pays ₹12 lakh for the package. Allocate 80% of each separate price: ₹12 lakh ÷ ₹15 lakh = 80%. This follows paragraphs 73–80.
Equipment and installation are completed in April, so their allocated revenue is ₹8 lakh + ₹1 lakh. One month’s support adds ₹3 lakh ÷ 12 = ₹25,000. Total April revenue is ₹9,25,000.
The remaining ₹2,75,000 is a contract liability: the business has been paid but still owes eleven months of support. The check is ₹9,25,000 revenue + ₹2,75,000 remaining liability = ₹12,00,000 received.
This example is not a rule that every installation is distinct or every service is straight-line. Change either assumption and redo the allocation or timing analysis. A software licence would also require its own right-to-use versus right-to-access assessment; a one-year licence term alone does not establish a twelve-month revenue pattern.
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. By the end of month 2, cumulative measured progress is 60%. Assume the progress measure faithfully represents performance, consideration is determinable and collection is reasonably expected. For the Ind AS case, assume the customer receives and consumes the service benefits as the entity performs, satisfying paragraph 35(a). For the AS case, assume proportionate completion properly reflects the work accomplished and no decisive final act requires deferral.
Treatment: Cumulative revenue at the end of month 2 is ₹4,00,000 × 60% = ₹2,40,000, against cumulative billing of ₹2,00,000. The extra ₹40,000 of revenue has not yet been billed. Check the payment rights before classifying it in the balance sheet. Under Ind AS 115, a receivable is an unconditional right to payment; only time must pass before it becomes due. A right that still depends on another condition may be a contract asset. If a substantive final deliverable prevents the assumed recognition pattern, do not book 60% merely because that much effort has been spent.
Contract terms that can 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.
Before closing the month
- 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.
Keep the working behind the entry
For each material contract, keep the accounting rules used, contract terms, evidence of delivery or work done, price calculation and closing reconciliation together. A reviewer should be able to see why this amount belongs in this period.
Primary references: AS 9, paragraphs 2, 6–14 and illustrations; Ind AS 115 in ICAI's 2025–26 compendium, particularly paragraphs 5–9, 22–38, 39–45, 73–86 and 105–109. The compendium text includes the amendments identified in its notification note through 13 August 2025.
