Audit objective
Verify that revenue is recognised in accordance with the five-step model under IND AS 115, in the correct period (cut-off is usually the highest-risk assertion), at the correct amount (variable consideration, discounts, rebates, returns), and is presented and disclosed correctly including contract assets, contract liabilities, and disaggregation. Revenue is a presumed fraud risk area under SA 240 regardless of the entity's specific risk profile, so the audit response must go beyond standard substantive procedures.
Relevant framework
- IND AS 115 · Revenue from Contracts with Customers · five-step model, contract assets/liabilities, disclosure
- AS 9 · Revenue Recognition for non-IND AS entities (sale of goods, services, interest/royalty/dividend)
- IND AS 109 · Financial Instruments · trade receivables measurement, expected credit loss on revenue-related receivables
- IND AS 21 / AS 11 · Foreign Exchange · export revenue recognition and restatement
- IND AS 37 · Provisions · warranty obligations linked to revenue contracts
- IND AS 116 · Leases · lessor accounting where revenue includes lease income
- Section 129 · True and fair view requirement
- Schedule III Div I & II · Revenue from operations disaggregated into sale of products, sale of services, other operating revenue
- Contract assets and contract liabilities (advances from customers) presented separately under current liabilities / other assets
- Disclosure of revenue recognised from performance obligations satisfied in previous periods
- 3(xi)(a) · Whether any fraud by the Company or on the Company has been noticed or reported during the year, nature and amount
- 3(xi)(b) · Whether any report under Section 143(12) has been filed with the Central Government
- 3(xi)(c) · Whether auditor has considered whistle-blower complaints received during the year
- SA 240 · Auditor's Responsibilities Relating to Fraud · revenue is a presumed fraud risk
- SA 315 · Identifying and Assessing Risks of Material Misstatement
- SA 330 · Auditor's Responses to Assessed Risks · including unpredictability element
- SA 500 · Audit Evidence
- SA 505 · External Confirmations · customer balance confirmations
- SA 520 · Analytical Procedures · revenue trend, gross margin analysis
- SA 530 · Audit Sampling
- SA 550 · Related Parties · related party sales require specific scrutiny
- SA 600 · Group audit considerations for multi-location revenue
- Section 145 · Method of accounting, mercantile system mandatory for business income computation
- ICDS IV · Revenue Recognition · prescribes recognition for sale of goods, services (percentage completion or straight line), interest, royalties, dividends for tax computation, may differ from IND AS 115 book treatment
- Section 43CB · Computation of income from construction/service contracts on percentage completion method for tax, regardless of IND AS 115 treatment
- Section 12 · Time of supply for goods · earliest of invoice date, removal/delivery date, or payment date
- Section 13 · Time of supply for services · earliest of invoice date (if within prescribed period) or payment date
- Section 15 · Value of supply · transaction value including discounts allowed before/at supply, excluding post-supply discounts unless conditions met
- Section 31 · Tax invoice requirements
- Section 34 · Credit notes for sales returns and post-supply discounts, time limit for issuance
- GSTR-1 vs books cross-tally · revenue per books should reconcile to taxable value declared in GSTR-1, after adjusting for GST-exempt income, export without payment of tax, and timing differences
- Guidance Note on Accounting for Revenue from Contracts with Customers (IND AS 115) · ICAI
- Guidance Note on Audit of Revenue · ICAI AASB
IND AS 115 · five-step model
Every revenue contract should be walked through these five steps. Most audit findings on revenue trace back to a failure at one of these steps, particularly Step 5 (timing of recognition vs cut-off) and Step 4 (allocation where multiple performance obligations exist).
Identify the contract
Enforceable rights and obligations exist; commercial substance; collection probable. Watch for side letters and verbal modifications not reflected in the written contract.
Identify performance obligations
Distinct goods/services within the contract. Bundled contracts (goods + installation + AMC) often have multiple obligations requiring separate recognition.
Determine transaction price
Fixed and variable consideration, discounts, rebates, penalties, significant financing components. Variable consideration estimated using expected value or most likely amount, constrained to avoid significant reversal.
Allocate transaction price
Allocated to each performance obligation based on standalone selling price. Common error: allocating 100% to the primary deliverable and ignoring embedded service obligations (extended warranty, free maintenance).
Recognise revenue
At a point in time or over time, based on transfer of control. Over-time recognition (construction, SaaS, long-term services) requires a measure of progress; point-in-time requires identifying the exact transfer-of-control event.
Presumed fraud risk
SA 240 requires the auditor to presume a risk of material misstatement due to fraud related to revenue recognition, even where no specific risk indicators are identified. This is not optional and not rebuttable without documented justification.
What "responding to the presumption" looks like in the file
Vary the nature, timing, or extent of procedures from prior years, e.g. select a different period for cut-off testing, test different locations
Test journal entries and adjustments made to revenue accounts, particularly manual entries near period-end and from unusual users
Review revenue-related estimates (variable consideration, returns provision, percentage completion) for management bias
Evaluate the business rationale of significant transactions outside the normal course of business, especially near period-end
If, after performing these procedures, the auditor concludes the presumption does not apply (rare), the conclusion and basis must be documented per SA 230. Simply not addressing it is a documentation deficiency.
Risk areas by assertion
Risks below are mapped to financial statement assertions per SA 315. For revenue, occurrence and cut-off are typically the dominant risks, the opposite emphasis from a liability area like Trade Payables.
Occurrence Dominant
- Fictitious sales to non-existent or related-party shell customers
- Sales recorded without corresponding dispatch / delivery / service performance
- Channel stuffing: goods pushed to distributors near year-end with implicit right of return
- Bill-and-hold arrangements without meeting IND AS 115 criteria
Completeness
- Revenue earned but not invoiced (unbilled revenue / contract assets) not recognised
- Service revenue under long-term contracts not recognised on percentage of completion
- Rental, royalty, or licensing income omitted
- Scrap sales, by-product sales not captured
Valuation / Accuracy
- Variable consideration (rebates, volume discounts, price protection) not estimated or estimate biased
- Returns provision understated, especially for distributor-heavy models
- Multiple performance obligations not separately valued (bundled contracts)
- Foreign currency sales not recorded at correct exchange rate
- Significant financing component in long-credit-period contracts not adjusted
Rights & Obligations
- Consignment sales recognised as outright sales before transfer of control
- Related party sales not identified or priced at non-arm's-length terms
- Revenue recognised on goods still subject to buy-back arrangements
Cut-off Dominant
- Sales recorded before transfer of control to inflate period revenue
- Invoices dated in the current period for goods dispatched after year-end
- Year-end sales reversed or heavily returned in the subsequent period
- Last-day-of-period dispatches without supporting transport documentation
Presentation & Disclosure
- Revenue disaggregation (products / services / geography) not disclosed per IND AS 115
- Contract assets and contract liabilities not separately presented
- Performance obligations satisfied in previous periods not disclosed
- Related party revenue not separately disclosed
- Significant judgements in applying IND AS 115 not disclosed (timing of recognition, transaction price determination)
Documents to request
Hand this to the client at the start of the engagement. Items 11-13 are the ones most often missing and most often material.
- Sales register / revenue ledger for the year, with invoice-wise detail
- Sample of customer contracts / purchase orders, especially multi-element arrangements
- Pricing master and discount/rebate policy
- Credit note register issued during the year and subsequent period
- Sales returns register with reasons
- Dispatch / delivery challan register, transporter LR copies for sample
- Customer-wise ageing of trade receivables
- Customer confirmation responses (per SA 505)
- Revenue recognition policy document, including treatment of multiple performance obligations
- Contract asset / unbilled revenue working with computation basis
- Contract liability / advance from customer working, with movement schedule
- Percentage-of-completion working for long-term contracts, with budgeted vs actual cost
- Variable consideration estimation working (rebates, volume discounts, price protection accruals)
- Related party master and related party sales register
- GSTR-1 filed for the year, with reconciliation to books revenue
- Foreign currency sales listing with invoice and realisation rates
- Journal voucher listing for manual entries to revenue accounts during the year and post year-end
- Board minutes discussing significant or unusual sales transactions
- Whistle-blower complaint register, if any, relevant to sales/revenue
- Warranty provision working and historical claims experience
Fieldwork procedures
Procedures are grouped by assertion. Per the SA 240 presumption above, cut-off testing should be performed with an unpredictable element, vary the period sampled or the locations covered from prior year.
- Vouch a sample of revenue entries to underlying contract, dispatch documentation (LR / e-way bill), and customer acknowledgment
- Send confirmation requests to a sample of customers, prioritising large balances, related parties, and customers with unusual activity near year-end
- For consignment / distributor arrangements, verify revenue is recognised only on transfer of control, not on dispatch to consignee
- Review significant sales transactions near period-end for business rationale and unusual terms (extended credit, right of return, buy-back)
- Test journal entries posted to revenue accounts, focusing on manual entries, round amounts, period-end timing, and unusual users
- Reconcile dispatch register / e-way bills to sales register; investigate dispatches without corresponding invoices
- For service contracts, verify unbilled revenue / contract asset is recognised for services performed but not yet invoiced
- For long-term contracts, recompute percentage of completion using budgeted vs actual cost; verify revenue recognised matches
- Perform analytical procedures: gross margin trend by product line, revenue per unit trends, compare to industry and prior periods
- Reconcile GSTR-1 outward supplies to books revenue; investigate reconciling items
- Recompute variable consideration (rebates, volume discounts) based on contractual terms and actual volumes; compare to amount recognised
- Review returns provision: compare historical return rates to current provision, assess for management bias
- For bundled contracts, verify transaction price allocated to each performance obligation based on standalone selling price
- Verify foreign currency sales recorded at transaction-date rate; verify realisation gain/loss
- For long-credit-period contracts, assess whether a significant financing component exists and is separated per IND AS 115
- Identify related party sales from the related party master; verify pricing against arm's-length benchmarks
- For sale-and-buyback or sale-with-repurchase-option arrangements, assess whether transfer of control actually occurred
- Verify consignment stock at customer locations is not included in the Company's revenue until sold to end customer
- Select a sample of invoices around year-end (both sides) and trace to dispatch documentation; verify revenue recognised in the correct period based on transfer of control
- Vary the cut-off testing window and locations from the prior year per the SA 240 unpredictability requirement
- Review subsequent-period sales returns and credit notes; assess whether they relate to pre-year-end sales requiring adjustment
- For e-commerce / online sales, verify cut-off based on delivery confirmation rather than order date
- Verify revenue disaggregation disclosure (by product/service line, geography, timing of recognition) matches internal management reporting
- Verify contract assets and contract liabilities are separately presented and the movement schedule reconciles
- Verify disclosure of revenue recognised in the current period that was included in the contract liability balance at the start of the period
- Verify related party revenue is separately disclosed per AS 18 / IND AS 24
- Verify significant judgements applied (timing of recognition, transaction price estimation methods) are disclosed in accounting policies
Common findings and red flags
The most common observations encountered in Revenue fieldwork. Each line is a working-paper trigger.
Sample conclusion language
Use these as starting drafts. Adapt to engagement-specific facts and your firm's house style. All language is illustrative.
"Based on our procedures, which included testing of revenue recognition under the five-step model of IND AS 115, cut-off testing performed with an unpredictable element as required under SA 240, recomputation of variable consideration and percentage-of-completion estimates, confirmation of balances from a sample of customers, and reconciliation of revenue to GSTR-1, the revenue recognised for the year ended 31 Mar XXXX is recorded completely, accurately, and in the correct period in accordance with IND AS 115 and presented in accordance with Schedule III to the Companies Act, 2013. No material misstatement was noted."
"During our cut-off testing, we identified sales aggregating to Rs. XX lakhs invoiced on or before 31 Mar XXXX where the corresponding dispatch documentation indicates goods were despatched on or after 01 Apr XXXX. Management has [adjusted / not adjusted] the revenue recognised for these transactions to the subsequent period. [State materiality assessment and impact on opinion if unadjusted.]"
"We noted that the Company's estimate of variable consideration relating to volume rebates does not incorporate the actual sales volumes achieved by key distributors as at the reporting date, resulting in a potential understatement of the rebate liability of approximately Rs. XX lakhs. We have recommended that management revise the estimation methodology to incorporate actual volume data available at the time of finalisation. [Assess materiality for opinion impact.]"
"In response to the presumed risk of fraud in revenue recognition under SA 240, we performed cut-off testing covering [period / locations], varied from the approach adopted in the prior year, tested journal entries posted to revenue accounts for unusual characteristics, and reviewed significant transactions occurring near the period end for business rationale. No instances of fraud were identified. This documentation is retained as evidence of our response to the presumption."
Linked AuditAIKit tools
Audit Sampling Engine
Select customer confirmation samples and cut-off testing samples with documented, reproducible selection.
Live · SA 240Journal Entry Testing
Score revenue-account journal entries for round amounts, period-end timing, weekend postings, and unusual users.
Live · GST ReconciliationGSTR-2B Reconciliation
While built for purchases, the same matching engine can be adapted for GSTR-1 vs books revenue cross-tally workflows.
PlannedRevenue Cut-off Analyzer
Dispatch register vs sales register matching, subsequent-period returns analysis, percentage-of-completion recomputation.
Sources & references
Every reference in this playbook traces to an official source. Open the link to verify the exact wording in force as at the last review date.
| Reference | Source | Link |
|---|---|---|
| Companies Act, 2013 · Sec 129, Sch III | MCA | mca.gov.in |
| IND AS 115 / 109 / 21 / 37 / 116 | ICAI / MCA notification | icai.org |
| CARO 2020 Order · 25 Feb 2020 | MCA | mca.gov.in |
| SA 240, 315, 330, 500, 505, 520, 530, 550, 600 | ICAI AASB | icai.org |
| Guidance Note on Accounting for Revenue (IND AS 115) | ICAI | icai.org |
| Guidance Note on Audit of Revenue | ICAI AASB | icai.org |
| Income Tax Act · Sec 145, 43CB; ICDS IV | Income Tax Dept | incometax.gov.in |
| CGST Act · Sec 12, 13, 15, 31, 34 | CBIC | cbic.gov.in |