Testing a sale with a right of return means testing that the entity recognised revenue only for the consideration it expects to be entitled to keep — total consideration less the amount expected to be refunded — recognised a refund liability for the amount expected to be returned, and recognised a separate asset, with a corresponding adjustment to cost of sales, for its right to recover the goods expected to come back. All three components move together and should be tested together, not as a single net revenue adjustment.
Why three balances, not one
It is common to see an entity reduce revenue by an estimated returns percentage and stop there, treating the adjustment as a single net figure. Ind AS 115 requires the refund obligation to be recognised gross as a liability, and the returned goods the entity expects to recover to be recognised as a separate asset measured at the former carrying amount of the inventory, less any expected costs to recover it and any expected reduction in value. Testing only the net revenue figure misses whether the liability and the asset are each individually right.
The testing sequence
- 01Identify the population of sales with a contractual or customary right of returnA contractual return right is explicit in the sale terms; a customary right arises from the entity's established business practice of accepting returns even without a contractual obligation to do so, and both are in scope.
- 02Obtain the entity's estimate of the expected return rate and its basisThe estimate should be built from the entity's own return history, segmented by product line or channel where return behaviour genuinely differs, rather than a single blended rate applied across dissimilar products.
- 03Test the historical return rate against actual returns processed after the reporting dateCompare the prior year's estimated return rate to what was actually returned in the following months — a persistent gap between estimate and outcome, in one direction, signals the estimation approach itself needs revisiting, not just this year's number.
- 04Recompute the revenue recognised net of the estimated refund obligationGross sales for the period, less the refund liability computed at the estimated return rate applied to the gross transaction price, equals the revenue that should be recognised.
- 05Recompute the refund liability balance separatelyThis should be carried as a liability, not netted against trade receivables or against revenue in the balance sheet, and recomputed at each reporting date as the estimate is updated.
- 06Recompute the asset for the right to recover returned goodsMeasured at the former carrying amount of the inventory expected to be returned, adjusted for the expected cost of recovering it and any expected decline in the value of the returned goods, and tested the same way inventory is tested for net realisable value.
- 07Test actual returns received during the year against the opening refund liabilityA return processed in the period should reduce the refund liability and the right-of-recovery asset that were set up for it, not be run through revenue or cost of sales again as if it were a fresh transaction.
| Balance | Measurement | Evidence |
|---|---|---|
| Revenue recognised | Gross consideration less expected refunds | Return rate estimate applied to the gross transaction price |
| Refund liability | Expected refund amount, gross | Historical return rate against actual subsequent returns |
| Asset for right to recover goods | Former inventory carrying amount, less recovery cost and value decline | Inventory valuation testing applied to the expected returns |
A return rate estimate that has not moved in several years despite a visible shift in the product mix, the sales channel, or a known quality issue on a specific product line is a red flag worth testing on its own, independent of whether the aggregate historical rate still looks reasonable.
How we think about this
Recomputing the three balances from a given return rate is arithmetic, and should tie exactly. Whether the return rate itself is a reasonable estimate of what will actually come back is a forecasting judgement, tested against the entity's own track record, and it is the part of this working paper that actually carries audit risk.
This is practical guidance written for audit teams, not an authoritative statement of any standard or statute. Standards, forms and timelines change. Check the current text issued by the ICAI and the relevant authority before relying on anything here in an audit file.
Related resources
- Revenue, receivables & cut-offAuditing sales returns and credit notesWhy post-year-end credit notes are a classic overstatement signal, how to match them to the original invoice, and the GST reporting implications auditors should check.
- Revenue, receivables & cut-offAuditing Ind AS 115 — testing the five-step revenue recognition modelInd AS 115 doesn't ask when revenue is earned — it asks when control of a distinct good or service transfers, and each of the five steps changes that answer.
- Revenue, receivables & cut-offRevenue recognition testing in a statutory auditThe transfer-of-control test that governs when a sale is recognised, the misstatement patterns that recur in practice, and what evidence ties a recognised sale to an underlying document.
- Revenue, receivables & cut-offHow to test variable consideration in a revenue contract under Ind AS 115Variable consideration is estimated using one of two specified methods and then constrained. Skipping the constraint step is the most common way this estimate ends up too high.
Free tools, no signup
Each one reads a file entirely in your browser — or, for two of them, just answers a few questions — and nothing is ever uploaded.
- Purchase register checkDuplicate payments, round-sum amounts, weekend-dated invoices, incomplete records.
- GSTR-2B reconcilerMatches your purchase register against GSTR-2B — missing invoices either side, amount mismatches.
- Bank reconciliation checkerMatches your cash book against a bank statement — what's outstanding on each side.
- Fixed asset register checkDuplicate asset codes, missing location or useful life, negative net book value.
- Payroll red-flag scannerBank accounts shared across employees, and records missing an ID, PAN or salary.
- CARO applicability checkerAnswer a few questions about the company and see which CARO 2020 clauses likely apply.
- MSME payment delay checkerMSME-flagged invoices paid — or still unpaid — beyond the 45-day Section 22 limit.
- Related-party transaction screenerTransactions above a threshold you set with no approval reference, grouped by counterparty.
- Depreciation useful life checkerCompares a useful life in use against the Schedule II, Part C indicative figure.
- Materiality calculatorOverall and performance materiality against PBT, revenue, assets or equity, with reasoning shown.
- Sample size calculatorStatistical sample size for a test of controls or a substantive test of detail.