What is the cut-off assertion?
ISA 315.A190(a)(iv) defines cut-off as the assertion that transactions and events have been recorded in the correct accounting period. Unlike most other assertions, cut-off has a narrow scope — it focuses exclusively on the boundary between two reporting periods and whether transactions sit on the correct side of that line.
Despite its narrow scope, a cut-off error has a wide impact. Every cut-off misstatement affects two periods simultaneously: if revenue is recorded one day too early, the current period is overstated and the next period is understated by the same amount. This dual-period effect means that cut-off errors, unlike accuracy or classification errors, always self-correct in the following period — but the current period's financial statements are still materially misstated.
ISA 240.A50 specifically flags improper revenue recognition near the period end as a fraud indicator. Management under pressure to meet targets has a clear incentive to pull revenue forward or push expenses back across the reporting date. The evidence that resolves cut-off is almost always date-based: delivery dates, shipping dates, acceptance certificates, and goods-received notes rather than amounts or descriptions.
Key Points
- Tests the right period, not the right amount. Cut-off accepts that the transaction is real and correctly valued — it only asks whether it belongs in this period or the next.
- Revenue cut-off is the highest risk area. ISA 240.A50 identifies period-end revenue recognition as a specific fraud indicator that auditors must address.
- Testing focuses on the last and first two weeks. The standard window covers the final days of the current period and the opening days of the subsequent period.
- Errors always misstate two periods. A cut-off error overstates one period and understates the adjacent one by the same amount.
Why it matters in practice
The AFM has found that audit teams commonly test revenue cut-off using invoice dates rather than delivery dates. Under IFRS 15.38, revenue is recognised when control transfers to the customer — which is typically the delivery date, not the invoice date. An entity that invoices on 30 December for goods shipped on 3 January has recorded revenue in the wrong period, but teams relying on invoice dates will not detect this. Effective cut-off testing requires the auditor to identify the date on which the performance obligation was satisfied and compare that to the recording date.
Purchase cut-off on accruals is another area teams routinely skip. If goods were received before the reporting date but the invoice arrives in January, a purchase accrual should exist at year end. Teams that test only recorded transactions miss the completeness dimension of purchase cut-off entirely. The auditor needs to examine goods-received notes and delivery records around the period end and verify that corresponding accruals exist for items not yet invoiced.
Key standard references
- ISA 315.A190(a)(iv): Cut-off assertion for classes of transactions — transactions and events recorded in the correct accounting period.
- ISA 240.A50: Improper revenue recognition near the period end as a fraud risk indicator.
- IFRS 15.38: Revenue recognised when (or as) the entity satisfies a performance obligation by transferring control.
Related terms
Related reading
Frequently asked questions
What does a cut-off error do to the financial statements?
A cut-off error always creates a misstatement in two periods simultaneously: one overstated, one understated. A revenue transaction recorded one day too early overstates the current period's profit and understates the next period's.
What window do auditors typically test for cut-off?
The standard window is the last two weeks of the current period and the first two weeks of the subsequent period, though the width depends on transaction volume and industry. ISA 240.A50 specifically flags improper revenue recognition near the period end as a fraud indicator.
How is cut-off different from occurrence?
Occurrence asks whether the transaction happened at all. Cut-off accepts that it happened and asks whether it is in the right period. A fictitious sale fails occurrence. A genuine sale recorded on 30 December when delivery was 3 January fails cut-off. Both use delivery documentation but ask different questions of it.