Sales cut-off testing checks that each sale is recorded in the period in which the transfer of control or risk actually happened, not the period in which it was invoiced or posted to the ledger. Because dispatch date, invoice date and ledger posting date can each differ by days from one another, the test has to pick a defined window either side of the year end, pull every transaction in that window, and trace each one to independent dispatch evidence — the gate register and the e-way bill — rather than relying on the dates the accounting system itself reports.
Why three dates can disagree
In a well-run business the dispatch date, the invoice date and the ledger posting date are the same day. In most mid-market Tally clients they are not, for ordinary operational reasons that have nothing to do with fraud: goods are dispatched on a Saturday when the accounts team is not working and the invoice is raised the following Monday; invoices are batched and entered into Tally once a week; a transporter's lorry receipt is dated a day after the goods actually left the gate because of how the transport desk processes paperwork.
| Date | What it records | Why it can lag or lead |
|---|---|---|
| Dispatch or delivery date | When physical control of the goods changed hands | Usually the correct recognition date, but is the one least likely to be in the accounting system at all unless pulled from the gate register or e-way bill |
| Invoice date | When the accounting document was generated | Can be deliberately backdated or forward-dated, or simply delayed because billing is batched |
| Ledger posting date | When the transaction was entered into Tally | Often several days after the invoice date because of batch entry, and is not evidence of either dispatch or invoicing |
Designing the cut-off sample
A cut-off test is only as good as the window it covers and the independence of the evidence it relies on. Four decisions set up the test.
- 01Fix the window symmetrically around the year endA common approach is the last five to ten working days before the year end and the first five to ten after, adjusted for the client's actual volume pattern. A client with a monthly billing cycle needs a wider window than one that bills daily.
- 02Pull the population from more than one sourceTake the sales register entries dated in the window, but also pull the gate outward register and the e-way bill portal data for the same window independently. A dispatch with no corresponding sales entry, or a sales entry with no corresponding dispatch, is the actual finding — and neither shows up if you only look at the sales register.
- 03Trace each sampled item to dispatch evidence first, invoice secondReverse the usual order. Starting from the invoice and looking for support invites confirmation bias toward the date already recorded. Starting from an independent dispatch record and asking which period it falls in is the test that actually catches cut-off error.
- 04Treat invoices raised after year end for pre-year-end dispatch as inventory risk tooIf goods left the gate before the year end but were invoiced after, the goods may have already been excluded from the physical inventory count. Check that the item was not also omitted from the closing stock sheet — a cut-off error can produce two misstatements, not one.
Corroborating evidence: e-way bill and gate register
The e-way bill is generated under GST rules for the movement of goods above a prescribed value and carries a system-generated timestamp that the client cannot adjust after the fact in the way an internally created delivery challan can be backdated. It is one of the better independent cut-off checks available on an Indian client, because its date is verifiable against the GST portal rather than resting entirely on the client's own paper trail.
- E-way bill generation date and vehicle number, cross-checked against the invoice it corresponds to
- Gate outward register, maintained at the factory or warehouse, showing vehicle entry and exit times independent of the accounts department
- Transporter's lorry receipt or proof of delivery, where available, for the far end of the journey
- For e-commerce or direct-to-consumer dispatch, the courier manifest and tracking status as of the year-end date
Common practice, not a requirement
Pulling the e-way bill data as a separate extract and reconciling it to the sales register by invoice number, rather than asking the client to manually identify which e-way bills relate to year-end dispatches, removes an opportunity for the exact population at risk to be filtered before it reaches you.
Common cut-off manipulation patterns
Deliberate cut-off manipulation, where it occurs, tends to follow a small number of recognisable shapes rather than being inventive.
- Invoices dated before year end for goods that physically left the gate after year end, to pull revenue into the current period
- The sales register left open past the year end, with transactions from the first days of the new period backdated into the closing month
- Dispatch made before year end but deliberately not invoiced until a scheme or price revision takes effect in the new year, understating current-period revenue for reasons unrelated to cut-off but producing the same symptom
- A customer return accepted in principle before year end but the credit note raised weeks later, leaving an overstated receivable and overstated revenue sitting in the closing balances
A sales ledger that remains open for data entry after the year end but before the audit begins is itself a control weakness worth documenting, independent of whether any specific transaction in it turns out to be misstated.
How we think about this
Reconciling a sales register entry to an e-way bill and a gate register entry by invoice number and date is exactly the kind of matching that should run across the whole window automatically, flagging every exception rather than the handful a sample happens to catch. Deciding whether a dispatch-before-invoice gap reflects ordinary batching or deliberate cut-off manipulation is a judgement that depends on the client's normal pattern, and that stays with the auditor.
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-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.
- 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-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.