AS 9 deals with the bases for recognising revenue in the statement of profit and loss. Revenue recognition is one of the most fundamental questions in accounting — *when* should a sale be recorded as revenue? — because recording it too early overstates performance and too late understates it. AS 9 sets out the timing for the main categories of revenue: sale of goods, rendering of services, and revenue from interest, royalties, and dividends.
Objective and scope
The standard is concerned with the recognition of revenue arising in the course of the ordinary activities of the enterprise from the sale of goods, the rendering of services, and the use by others of enterprise resources yielding interest, royalties, and dividends. Revenue is the gross inflow of cash, receivables, or other consideration arising in the course of ordinary activities from these sources. It is measured by the charges made to customers or clients for goods supplied and services rendered, and by the charges and rewards arising from the use of resources by others. Importantly, revenue is the gross inflow on the enterprise's own account — amounts collected on behalf of third parties (such as certain taxes collected for the government) are not revenue.
AS 9 does not deal with several specific revenue situations covered by other standards, including construction contracts (AS 7), revenue of insurance companies, government grants and similar subsidies (AS 12), and revaluation of fixed assets. These exclusions exist because those areas have their own treatment.
The two key conditions
Underlying AS 9 are two recurring conditions for recognising revenue. Revenue is recognised when the performance required has been achieved, *and* when it is reasonable to expect ultimate collection (no significant uncertainty exists regarding the amount of consideration that will be derived). Where, at the time of raising a claim, it is unreasonable to expect ultimate collection, revenue recognition is postponed. These two ideas — performance, and reasonable certainty of collection — run through all the categories below.
Sale of goods
In a transaction involving the sale of goods, performance is regarded as being achieved when the seller has transferred to the buyer the property in the goods for a price, or all significant risks and rewards of ownership have been transferred to the buyer and the seller retains no effective control over the goods to a degree usually associated with ownership. At that point, provided there is no significant uncertainty regarding collection, revenue from the sale is recognised. In most straightforward sales, this occurs on delivery. The emphasis on transfer of significant risks and rewards (and loss of effective control) is what determines timing — for example, goods sold on approval are not recognised as revenue until the buyer accepts them or the approval period lapses.
Rendering of services
Revenue from service transactions is usually recognised as the service is performed. AS 9 permits two methods:
Proportionate completion method — revenue is recognised proportionately by reference to the performance of each act, as the service is performed. This suits services performed over time through a number of acts.
Completed service contract method — revenue is recognised only when the rendering of services under the contract is completed or substantially completed. This suits services where performance consists of a single act, or where the proportion of completion cannot be reliably measured.
As with goods, recognition is subject to no significant uncertainty over collection.
Interest, royalties, and dividends
Revenue arising from the use by others of enterprise resources is recognised when no significant uncertainty as to measurability or collectability exists, on the following bases:
Interest — on a time proportion basis, taking into account the amount outstanding and the rate applicable. Interest accrues with the passage of time.
Royalties — on an accrual basis in accordance with the terms of the relevant agreement.
Dividends — when the owner's right to receive payment is established (for shareholders, this is generally when the dividend is declared/approved).
Disclosure
An enterprise should disclose the circumstances in which revenue recognition has been postponed pending the resolution of significant uncertainties. This alerts users to revenue that has been earned in the sense of performance but not yet recognised because collection is uncertain.
A brief illustration
A company delivers goods worth ₹5 lakh to a customer on 28 March, transferring the significant risks and rewards of ownership, with payment due in April and no doubt about the customer's ability to pay. Under AS 9, revenue of ₹5 lakh is recognised in March — performance is complete and collection is reasonably certain — even though the cash arrives in April (this is the accrual basis in action). Contrast this with goods sent on a sale-or-return basis where the customer has not yet accepted them: no revenue is recognised until acceptance, because the significant risks and rewards have not yet passed.
How AS 9 compares with Ind AS 115
This is one of the most important framework differences for any business. AS 9 is a relatively short, principles-based standard focused on the *timing* of recognition for a few revenue categories. Under the Ind AS framework, revenue is governed by Ind AS 115, Revenue from Contracts with Customers, which is far more comprehensive and applies a single five-step model to all contracts with customers: (1) identify the contract, (2) identify the separate performance obligations, (3) determine the transaction price, (4) allocate the transaction price to the performance obligations, and (5) recognise revenue as each performance obligation is satisfied (either over time or at a point in time). Ind AS 115 deals in much greater depth with matters AS 9 barely addresses — multiple-element arrangements, variable consideration, significant financing components, principal-versus-agent questions, and extensive disclosures. So while AS 9 asks "has performance occurred and is collection reasonably certain?", Ind AS 115 imposes a structured five-step analysis on every customer contract. The practical results can differ significantly for complex arrangements (such as bundled goods and services or contracts with discounts and variable pricing), even if simple cash sales are recognised similarly under both.
Common pitfalls
Frequent issues include recognising revenue before the significant risks and rewards of ownership have passed; recognising revenue despite significant uncertainty over collection (rather than postponing it); recognising amounts collected on behalf of third parties as the enterprise's own revenue; and, for services, applying the completed-contract method where proportionate completion would better reflect performance.
Why this is cleaner on a unified system
Revenue recognition is more reliable when sales, dispatch, billing, collections, and the ledger all sit in one connected system, so that the point at which goods are delivered or services performed — and the status of collection — is captured in a single source of truth. When revenue flows directly from the underlying transaction data into the accounts, applying the recognition criteria consistently and tracking postponed revenue is far simpler than reconciling sales records against accounting entries held in separate tools.
This article is a detailed educational summary of AS 9 in plain language. It is not a substitute for the full text of the standard. Accounting standards are amended from time to time; always verify the current, authoritative text of AS 9 as issued by the ICAI before relying on it, and consult a qualified chartered accountant for application to your specific circumstances.