Revenue Cutoff
Test whether the sale was actually earned in the period it was recorded.
- General ledger alone
- Key analysis in Revenue & receivables
How the result is read
Compare the date control passed to the customer against the date the sale was booked, across a window straddling period end. Delivery is the usual evidence of that transfer, not the rule — ex-works it passes at collection, bill-and-hold with no shipment, services as work is performed — so the terms are read before the dates are compared. The test runs both ways: booked before control passed overstates this year, delivered this year and invoiced after understates it.
The worksheet, on the demo engagement
Revenue Cutoff, as the application draws it for Harrow Precision Engineering Ltd, the fictional demo engagement — one row per revenue invoice in the window.
- Window
- Dec 22 to Jan 8
- Mismatches
- 2
- Premature rev
- 2,800
Result grid4 rows
| invoice_id | invoice_date | delivery_date | gap_days | amount | booked |
|---|---|---|---|---|---|
| INV-77120 | 2024-12-30 | 2025-01-06 | +7 | 1,840 | FY25 |
| INV-77131 | 2024-12-31 | 2025-01-04 | +4 | 960 | FY25 |
| INV-77140 | 2024-12-28 | 2024-12-28 | 0 | 540 | FY25 |
| INV-77155 | 2024-12-29 | 2024-12-22 | 7 | 1,200 | FY25 |
In the application
Revenue Cutoff is filed under Revenue & receivables, index letter C. "Run all analyses" runs it with every other analysis the ledger can answer. The worksheet states the population it tested on its face — or "Not applicable" with the reason when a column it depends on is empty — and the Excel workbook the engagement exports files it under C, beside an index of the source files with their SHA-256 fingerprints.
Read it with
Run your next audit file test without the Excel crash.
One free engagement to evaluate, valid 60 days. The ledger never leaves the machine.
- 20 minutes
- Runs on a fictional engagement
- No client data required