Audit of revenue explained: this guide covers what it means, who it applies to, the step-by-step process, documents required, fees, due dates and penalties in India — so you can stay compliant with confidence and avoid costly mistakes.
Revenue is where audit standards presume trouble. Overstating it flatters profit; shifting it between years smooths results; and receivables are the balance that shows whether the sale was real and will be collected. This article explains how an auditor tests revenue and trade receivables and what an accountant should have ready. Tidy customer ledgers help here, and our books of accounts and compliance support covers them.
This article is based on the Standards on Auditing issued by ICAI as in force on 4 October 2026; ICAI may revise standards, so check the current text on icai.org. Each standard is explained in full in our linked posts; here they are applied to one area.
SA 240 (paragraph 26) tells the auditor to presume that there are fraud risks in revenue recognition and to evaluate which revenue types or transactions give rise to them. The auditor then tests cut-off, confirms balances directly with customers under SA 505, uses alternative procedures where there is no reply, and challenges the ageing and the allowance for doubtful debts as an accounting estimate. Negative confirmations are weak evidence and cannot normally be the only procedure (SA 505, paragraph 15).
The fraud presumption in revenue
SA 240, paragraph 26, requires the auditor, when identifying and assessing the risks of material misstatement due to fraud, to proceed on the presumption that revenue recognition carries such risks, and to evaluate which types of revenue, revenue transactions or assertions give rise to them. The application material (A28) explains that the misstatement is often an overstatement through premature recognition or fictitious revenue, but can also be an understatement by shifting revenue to a later period. A29 notes the risk can be greater where performance is measured on revenue growth or where much revenue is in cash. A30 says the presumption can be rebutted, for example for a single type of simple transaction. Our posts on SA 240, part 1 and the accounting principles in AS 9 go into the detail.
Assertions for revenue and receivables
| Assertion | Revenue | Trade receivables |
|---|---|---|
| Occurrence / existence | Sale really took place and relates to the entity | The customer exists and owes the balance |
| Completeness | All sales are recorded | All amounts due are recorded |
| Cut-off | Sales are in the right period | Balance includes only year-end sales |
| Accuracy | Price, quantity and tax are right | Balance agrees with invoices and receipts |
| Valuation | Discounts, returns and incentives are reflected | Allowance for doubtful debts is adequate |
| Presentation | Revenue classified and policy disclosed | Ageing and disputed balances disclosed |
Testing revenue
The auditor examines the revenue policy against the framework and its application to different streams, then tests transactions from order to cash. A sample of recorded sales is vouched to customer orders, dispatch or delivery proof, invoices and receipts (occurrence); a sample of dispatch records is traced to invoices and the ledger (completeness). Terms are read for rights of return, acceptance conditions, bill-and-hold arrangements and side agreements. Journal entries near year end, credit notes after year end and unusual large sales are looked at with scepticism, because these are the usual routes for manipulation. Analytical procedures, such as sales by month, gross margin by product and receivable days against previous years, point to unusual patterns; see our post on SA 520.
Cut-off
For cut-off the auditor takes the last dispatches before year end and the first after, and checks that each sits in the right period according to when control passed to the customer. A review of credit notes and returns issued in the weeks after year end shows whether sales were booked early. Cut-off is where management may feel pressure to pull sales forward, so the auditor looks at the documents and not at the date on the invoice alone.
External confirmations (SA 505)
The auditor must maintain control over confirmation requests, determining what is to be confirmed, choosing the right confirming party, designing the request so that replies come straight to the auditor, and sending and following up (SA 505, paragraph 7). Requests can ask for balances, terms of agreements or the absence of side agreements (A1).
| Situation | What SA 505 requires | Paragraph |
|---|---|---|
| Management will not let the auditor send a request | Ask why, seek evidence on whether the reasons are valid, evaluate the effect on risk including fraud and do alternative procedures | 8 |
| Refusal is unreasonable or alternatives fail | Communicate with those charged with governance and consider the effect on the opinion | 9 |
| Doubts about a reply's reliability | Obtain further evidence; if unreliable, evaluate the effect on risk and on other procedures | 10, 11 |
| No reply | Perform alternative procedures for each non-response | 12 |
| A reply is essential evidence | If it is not obtained, consider the effect on the opinion; alternatives will not do | 13 |
| Reply shows a difference | Investigate each exception to see whether it indicates a misstatement | 14 |
| Negative confirmations | Not the sole procedure unless risk is low and controls were tested, items are many, small and similar, few exceptions are expected and nothing suggests recipients will ignore them | 15 |
| Overall | Evaluate whether results give relevant and reliable evidence or need further procedures | 16 |
Alternative procedures for a non-reply usually mean examining subsequent receipts, and the invoices, orders and dispatch records behind the balance. The full standard is in our post on SA 505.
Ageing and the allowance for doubtful debts
The auditor checks the ageing schedule for accuracy, for example by recomputing the buckets for a sample and agreeing the total to the ledger; the format and the required ageing in company financial statements are covered in our post on the four ageing schedules. The allowance is an accounting estimate, so the SA 540 approach applies: how management made it, the data behind it, whether the method suits the framework, and whether the result is reasonable. Evidence includes subsequent receipts, correspondence with customers, the history of write-offs, disputes and credit notes, and the financial position of large debtors. Specific provisions for individual accounts and a general provision by ageing are compared with history, and any indications of management bias are noted. Unbilled revenue and advances from customers are checked to ensure they are in the right place and not netted.
Worked example (illustrative)
Kunal Appliances Pvt Ltd, an invented distributor, reports sales of Rs 96 crore and receivables of Rs 21 crore. The auditor presumes a revenue fraud risk and focuses on the last week of March. Dispatch records show Rs 2.1 crore of dispatches on 29 and 30 March to one dealer, with credit notes of Rs 1.4 crore issued in April. Enquiry shows the dealer had asked for the goods to be held back; this is a bill-and-hold arrangement without the dealer's acceptance, and revenue is overstated. Confirmation requests go out for 30 customers covering 70 per cent of the balance. Four do not reply; for them the auditor traces subsequent receipts for two and invoices and delivery proofs for two. One reply shows a difference of an illustrative Rs 6 lakh due to a receipt in transit, resolved by the bank record. The allowance is increased for a dealer with a disputed balance of Rs 35 lakh and no payments since September.
Documents to keep ready
- Revenue policy note and contract terms for major customers.
- Sales ledger, dispatch records and invoices around year end, with credit notes issued after year end.
- Customer-wise receivables list reconciled to the ledger, with ageing.
- Customer contact details so that confirmation requests reach the right person.
- Receipts after year end by customer.
- Notes on disputes, collection efforts and the basis of the allowance.
Common lapses
- Sales recorded on invoice date without proof that control passed.
- Confirmation requests that management wants to send or intercept.
- Ageing from invoice date when terms run from delivery, or unallocated receipts left in an unapplied account.
- An allowance based on a flat percentage with no regard to specific disputes.
- Credit notes after year end ignored in the cut-off review.
Need help preparing revenue and receivables schedules?
Customer-wise reconciliations, clean ageing and a documented provisioning basis make confirmations and cut-off work much quicker. Our team can reconcile ledgers, prepare the schedules and set up the monthly follow-up routine; see our books of accounts and compliance support.
Key takeaways
- Revenue carries a presumed fraud risk (SA 240, paragraph 26), rebuttable only on the facts.
- Cut-off is tested on documents, not on invoice dates alone.
- Confirmations must be controlled by the auditor, and each non-response needs alternative procedures (SA 505, paragraphs 7 and 12).
- Negative confirmations are weak evidence (paragraph 15).
- The allowance for doubtful debts is an estimate and is tested as one.
Read next
- Audit of inventories
- Audit of trade payables, expenses, provisions and cash and bank
- SA 505, external confirmations
- Internal audit of sales and receivables
Disclaimer: Based on the Standards on Auditing, the review, assurance and related services standards, the Compendium of Standards on Internal Audit (as on 1 October 2022) and the Compendium of Forensic Accounting and Investigation Standards (as on September 2025) issued by the Institute of Chartered Accountants of India, in the versions named in the article, as consulted on 4 October 2026. ICAI revises standards from time to time; check the current text and effective dates on icai.org and the Companies Act provisions referred to. This article is general information, not legal advice; check the official text before acting.