The cut-off exceptions that actually turn up in Indian statutory audits, once a team traces the transactions flagged within a window of the period end, tend to cluster into a short list of recognisable patterns: round-sum invoices dated right at the period end that don't match any purchase order line item, credit notes issued in the first week of the following month that reverse a chunk of the prior period's late sales, and a visible concentration of invoicing in the last two or three days of the month that doesn't match the dispatch capacity the client actually has. None of these are found by the selection step itself — the window just makes sure the transaction is in the list to be traced. The exception only surfaces once someone pulls the underlying document.
Pattern 1: round-sum invoices dated March 31
An invoice for exactly ₹10,00,000 or ₹25,00,000, dated the last day of the financial year, with no corresponding purchase order or with a PO for a materially different amount, is a recurring red flag. It often turns out to be a provisional or estimated billing raised to hit a revenue number, reversed or heavily adjusted in April. Tracing it to a dispatch document frequently shows either no dispatch at all as of year end, or a dispatch for a different quantity than invoiced.
Pattern 2: credit notes clustered in the first week of April
A spike in credit notes issued in the first five to seven working days of the new financial year, especially ones referencing invoices dated in the last week of March, is one of the more reliable indicators of cut-off trouble. The pattern suggests invoices were raised to close out the period and then walked back once the goods, or the customer's acceptance, didn't actually materialise in time. This is worth pulling as its own population, separate from the forward-looking cut-off window, because it catches the mirror image of the same problem from the other side of the boundary.
Pattern 3: invoicing concentrated in the last three days of the month
Not every burst is a problem — some businesses genuinely dispatch in a rush at month end for operational reasons. But a burst that is disproportionate to the client's normal dispatch capacity (forty invoices raised on the 29th through 31st against a warehouse that typically processes six to eight dispatches a day) deserves a closer look at whether the goods behind those invoices actually left before midnight on the 31st, or whether the invoice date was simply backdated to the period the client wanted the revenue in.
- Sales to related parties or group entities invoiced at period end with unusually fast documentation turnaround compared to third-party sales
- E-way bills generated a day or more after the invoice date for transactions that are supposed to involve same-day dispatch
- Invoices against sales orders that were themselves only created in the last week of the period, suggesting last-minute deal creation rather than delivery of pre-existing orders
- Export invoices dated before the shipping bill or bill of lading date, where the physical export genuinely happened in the following period
| Pattern | What clears it | What confirms a genuine exception |
|---|---|---|
| Round-sum year-end invoice | Matching PO, dispatch note dated before period end | No PO match, dispatch dated after period end or absent |
| Post-year-end credit note cluster | Credit note relates to an unrelated return/discount reason | Credit note reverses a specific late-March invoice in full or near-full |
| Last-3-days invoicing burst | Dispatch records show capacity genuinely scaled up that week | Dispatch dates for the burst fall mostly after period end |
None of these patterns, on their own, prove a cut-off error. A legitimate business reason can explain any single round-sum invoice or credit note. The point of flagging the pattern is to make sure the transaction gets traced, not to treat the pattern itself as a finding.
Common practice, not a requirement
Firms that keep a running list of which exception patterns showed up at a given client in prior years tend to spot a repeat faster. If last year's cut-off error was a round-sum invoice with no matching PO, that's a reasonable thing to specifically check for again this year, on top of the general window-based trace.
Every one of these patterns was found by a person looking at the document behind a flagged invoice — a dispatch note, an e-way bill, a shipping bill, a credit note register. The window-based selection that put the transaction on the list in the first place is a sorting step, not a conclusion. Lekhya's revenue and cut-off testing produces the list of transactions within the configured window of the period end, across the full population; it does not read the dispatch note, does not compare dates automatically, and does not flag a round-sum invoice as suspicious on its own. That judgement, pattern recognition included, stays with the audit team doing the trace.
How we think about this
A tool that narrows a population well still leaves the interesting work — recognising that this particular round-sum invoice looks like last year's exception — to the people doing the audit. That is by design, not a gap to be engineered away.
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-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.
- Revenue, receivables & cut-offThe year-end sale that was really next year's revenueInvoiced on the 31st. Dispatched on the 3rd. The sale was real. The year it belonged to was not the one the client had booked it in.
- Revenue, receivables & cut-offThe e-way bill date that gave away a cut-off problem the sales register didn't showThe invoice was dated the last day of the financial year. The e-way bill tied to the same consignment was generated four days later — meaning the goods could not have left the warehouse when the sale was booked.
- Revenue, receivables & cut-offRevenue cut-off testing across the full population, not a sample around the year endThe hard part of cut-off testing was never the tracing. It was deciding which invoices to pull in the first place.
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.