Auditing sales returns and credit notes means matching every credit note to the invoice it relates to, checking the gap between the two dates, and testing whether credit notes issued shortly after the year end actually relate to sales recognised just before it — which, if so, points to revenue that should not have been recognised in the year under audit. The population also needs separate attention for GST, because a credit note changes the supplier's output tax liability and has to be reported within the return timelines that apply, independent of how it is treated in the books.
Why this is a classic red flag
A sale recognised just before the year end and reversed by a credit note just after it is the single most recognisable shape of revenue-overstatement risk in a receivables-heavy business. It can be entirely innocent — a genuine quality rejection discovered after delivery, or a scheme adjustment agreed with a dealer — or it can be the mechanism by which a sale was pulled into the current year knowing it would unwind. The test cannot distinguish intent from the ledger alone; it can only surface the pattern so that intent gets examined.
A concentration of credit notes in the first two to four weeks of the new financial year, disproportionate to the rest of the year's run rate, is worth investigating as a population before looking at any individual item, because the pattern itself is the finding.
Matching credit notes to the original invoice
A credit note register that merely lists amount and customer, without a clear link to the invoice being credited, cannot be properly tested. The first step is establishing that link for every credit note in the sample, not assuming it from the customer name and a roughly similar amount.
- 01Confirm the credit note references the specific invoice numberMany Tally setups allow a credit note to be entered as a standalone voucher with no reference field populated. Where the reference is missing, obtain it from the physical document or the customer correspondence rather than guessing from amount and date proximity.
- 02Compute the gap between invoice date and credit note dateA short gap, measured in days, around a period end is the pattern to flag. A credit note six months after the original sale, for an unrelated reason such as a long-running dispute, is a different risk entirely and should not be lumped into the same analysis.
- 03Read the stated reasonRate difference, quality rejection, quantity shortage, scheme or discount adjustment, and sales return each carry a different evidentiary trail. A credit note with no stated reason at all, or a generic one such as "adjustment", is itself a finding worth noting.
- 04Trace quantity-based returns to actual physical receipt back into stockA credit note for a sales return should correspond to the goods actually coming back. Where the quantity returned has no matching inward entry in the stores or inward gate register, the credit note may be adjusting a billing dispute rather than reflecting a true return, which has different accounting and GST consequences.
GST reporting implications
A credit note reduces the supplier's taxable value and output tax for the original supply, and has to be reported in the GST returns, which also affects the corresponding entry the customer sees reflected for their input credit. Credit notes issued near a year end therefore sit at the intersection of the financial reporting cut-off question and a separate GST compliance timeline, and the two need to be checked together rather than assuming that correct GST filing proves correct accounting cut-off, or the reverse.
- Confirm the credit note has actually been reported in the GST returns for the relevant period, not just raised internally in Tally
- Check that the tax adjustment on the credit note matches the tax originally charged on the invoice it relates to
- Where the credit note relates to a return of goods, confirm the stock movement is reflected consistently between the financial books and whatever is reported for GST purposes
- Flag any credit note raised well after the statutory time limit for adjusting output tax for that supply, since a credit note that misses the GST timeline still needs to be accounted for correctly even though the tax treatment is affected
Regulatory requirement
GST law prescribes time limits within which a credit note must be issued and reported for the supplier to adjust output tax liability against it. These timelines have been subject to amendment; confirm the limit applicable to the period under audit before concluding on any specific credit note.
Testing approach
Treat the credit note register as its own population for analysis, separate from but linked to the sales register, and run the following before selecting individual items for detailed testing.
| Analysis | What it reveals |
|---|---|
| Credit notes by month across the year, by value and count | Whether the post-year-end weeks are genuinely anomalous against the client's own pattern |
| Credit notes grouped by customer | Concentration in a small number of dealers or distributors, consistent with a channel-stuffing pattern |
| Credit notes grouped by stated reason | Whether a disproportionate share carry vague or missing reasons |
| Credit note value as a percentage of the related invoice | Full reversals are a different risk signal from small rate corrections and should be reviewed separately |
How we think about this
Matching every credit note to its invoice, computing the date gap, and ranking the population by concentration and reason are exactly the kind of exhaustive, repeatable checks that software should run across every credit note raised in the year, not a sample of them. Whether a cluster of post-year-end credit notes reflects genuine returns or engineered revenue is a judgement that needs the auditor looking at the underlying facts.
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-offSales cut-off testing: dispatch, invoice and ledger datesWhy dispatch, invoice and ledger dates disagree at year end, how to sample either side of the cut-off, and the evidence that settles which date governs.
- 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-offCommon exceptions in revenue and receivables testingA reference catalogue of the exceptions that recur most often across revenue and receivables testing, why each happens, and what to do about it.
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.