Across revenue recognition, cut-off, confirmation, credit note and receivables provisioning testing, the exceptions that actually turn up on real engagements fall into a short, recurring list: dispatch and invoice dates that disagree at the year end, sales with no matching dispatch evidence, credit notes clustered just after year end, non-responding or disputed debtor confirmations, provisions that have not moved from a prior-year percentage, and related-party or export transactions missing their specific supporting document. Knowing this list in advance speeds up both testing design and the response once an exception is actually found, because the right next step for each type is largely the same every time it recurs.
Why a reference list helps
Revenue testing generates a lot of individual findings, and treating each one as a fresh problem wastes time that should go into judging whether the finding actually matters. Most exceptions are a known shape with a known first response. This article collects them from across the revenue and receivables cluster into one table, organised the way they actually surface in a working paper review, so a reviewer or a first-year article can recognise the pattern quickly and go straight to what the finding needs rather than starting from nothing.
The catalogue
| Exception | Why it happens | What to do |
|---|---|---|
| Dispatch date and invoice date fall in different periods at year end | Billing is batched weekly or invoices are raised a day or two after a weekend dispatch, as a routine operational lag rather than anything deliberate | Recompute recognition based on the dispatch date, not the invoice date; adjust the period if material and check whether the related inventory treatment also needs correcting |
| A recorded sale has no matching dispatch or delivery evidence | Could be a genuine service sale with no physical dispatch, a bill-and-hold arrangement, or a fictitious or premature sale | Establish which of the three it is from the contract terms first; only once a bill-and-hold or service basis is confirmed should the absence of dispatch evidence stop being a concern |
| A dispatch has no matching sales invoice | An invoicing step was missed, goods were sent on approval or consignment and not yet actually sold, or revenue is understated | Check the nature of the dispatch against any consignment or approval terms; if none apply, this is a completeness gap in revenue |
| Credit notes cluster in the weeks after year end against invoices dated just before it | Genuine quality rejections and scheme adjustments do happen near a period close, but the same pattern is also how overstated year-end revenue gets quietly reversed | Analyse the whole credit note population by date gap and stated reason before looking at individual items; investigate any concentration against a small number of customers |
| A debtor confirmation is not returned despite two requests | Customer accounts staff frequently do not prioritise confirmation letters, independent of whether the balance is actually correct | Move to alternative procedures: trace subsequent cash receipts to the specific invoices making up the balance, and vouch invoice-level detail where receipts are insufficient |
| A debtor confirmation comes back disputing the balance | A genuine timing difference, a billing error, or a substantive commercial dispute over goods, pricing or quality | Reconcile the difference item by item and document the resolution; a cluster of disputes around one product line or branch deserves escalation beyond the individual items |
| The provision for doubtful debts uses the same percentages as last year with no fresh calculation | Rolling forward a prior-year rate is faster than recomputing it, and in a stable business it can look close enough not to question | Ask for the underlying historical loss-rate calculation; recompute the provision on the current year-end ageing independently rather than accepting the client's total |
| A related-party relationship surfaces that was not on management's disclosed list | The statutory definition of related party is broader than what gets volunteered, and the omission is not always deliberate | Follow the relationship through to its sales and balances, test pricing against comparable third-party transactions, and check the disclosure note is updated to match |
| An export sale has no FIRC and no extension of the realisation period on file | Realisation can genuinely be delayed by an overseas buyer dispute, but the same gap is also how a non-genuine export sale would present | Chase the realisation status directly with whoever manages the client's export documentation; treat a long-outstanding, unexplained balance as a receivables risk in its own right |
| A journal entry posts directly to the sales ledger with no invoice or dispatch reference | Bypasses the normal invoicing workflow, sometimes for a legitimate adjustment, sometimes because the entry was never meant to go through the normal controls | Obtain the specific reason and supporting approval for every such entry; treat the absence of either as a finding regardless of amount |
How these exceptions relate to each other
These are not nine unrelated findings. A dispatch-invoice date mismatch at year end and a post-year-end credit note cluster are often two symptoms of the same underlying revenue-timing pressure. A non-responding debtor confirmation and an unmoved provision percentage often sit on the same stale balance, neither one examined closely enough to catch the other. Working through the catalogue by exception type, rather than by sampled transaction, makes these connections visible in a way that testing transaction-by-transaction tends to miss.
- Recognition and cut-off exceptions (date mismatches, missing dispatch evidence) tend to concentrate in the same window around the year end and should be looked at together
- Credit note clustering and recognition exceptions are frequently the two ends of the same overstatement
- Confirmation exceptions and provisioning exceptions both ultimately concern whether a balance is real and collectible, and should inform each other rather than being closed off separately
- Related-party and export exceptions both tend to involve a missing document rather than a missing transaction, and the first response in both cases is to chase the specific document rather than assume the transaction itself is wrong
An exception that looks individually immaterial but belongs to a recognisable category above is still worth logging in full, because the category, not the individual item, is usually where the real risk sits. A dozen immaterial items in the same category can be a material finding in aggregate.
How we think about this
Every exception in this catalogue is, at its root, a mismatch between two things that should agree: two dates, a dispatch and an invoice, a stated percentage and a recomputed one, a disclosed list and an independently built one. Finding the mismatch is a matching exercise that software should run across the whole population and flag every time, consistently. Deciding what a specific mismatch means for a specific client is, and should stay, a judgement the auditor makes.
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-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-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-offDebtors confirmation procedure: balance confirmation in practicePositive versus negative confirmation, selection criteria, handling non-responses and disputes, and the alternative procedures that cover the gap when confirmations fail.
- Revenue, receivables & cut-offMatching dispatch, invoice and ledger for revenue testingThe sales-side mirror of the purchase three-way match: what breaks it in practice, and why the unmatched population should be sized by value, not count.
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.