CORAA
University · Substantive testing

Year-End Cut-Off Tester.

Paste sales or purchase entries with the date recorded in the books and the date goods were delivered or received. Enter the year-end date. The tool finds entries booked in one year but delivered in the other, and entries sitting close to year end. These are the ones to vouch first.

Transactions and year end

Paste from Excel or CSV. Dates can be dd/mm/yyyy, dd-mm-yyyy or yyyy-mm-dd. Columns are found by header names; if a name is not recognised the default position above is used.

Revenue is recognised when control passes under your reporting framework, which may not be the delivery date for every contract. Use the date that fits the terms, and check the current standards.

Cut-off results
Entries read6
Recorded in the year, delivered after year end0 items, 0.00
Recorded after year end, delivered in the year0 items, 0.00
Other entries within the window0 items, 0.00
Entries with no delivery or receipt date1
Rows with an unreadable recorded date0
ReferenceRecordedDelivered / receivedAmountFlags
S-88302020-03-31-1,75,000.00No delivery or receipt date given

Cut-off errors move profit between years.

An entry booked a day early or a day late shifts revenue or cost from one year into the next. The risk is highest in the last and first few days around year end, and in large entries. Vouch the flagged items to the dispatch note, goods receipt or other proof of when control passed, then follow through to credit notes and returns in the new year.

Revenue recognition testerInvoice sequence gap finder

How the tests work

Each entry has a recorded date and a delivery or receipt date. If the entry is recorded on or before year end but the goods moved after it, the entry may be early. If it is recorded after year end but the goods moved on or before it, the entry may be late.

Entries whose recorded or delivery date falls within the window you set around year end are also flagged, so you can look at the busiest days even where the two dates agree.

Amounts are totalled for each group. Entries without a delivery or receipt date can be flagged for follow-up.

Worked example — a sale booked a few days early

A sale of 4,80,000 is booked on 29 March and the goods leave on 2 April. Year end is 31 March.

Inputs
Recorded date29/03/2026
Delivery date02/04/2026
Year end31/03/2026
Output
FlagRecorded in the year, delivered after year end
Possible overstatement4,80,000
Whether the sale belongs in this year depends on when control passed under the contract. The flag tells you where to look.

Common mistakes

Using the invoice date as the delivery date
They can differ. Take the delivery date from the dispatch note or goods receipt.
Testing only sales
Run purchases, expenses and credit notes too. Cut-off can be wrong on the cost side.
Choosing too narrow a window
Transit time and shipping terms can move the risk window. Widen it when goods travel far.

Frequently asked questions

What columns does the pasted data need?+
A header row, then reference, description, recorded date, delivery or receipt date and amount.
Does it decide where revenue belongs?+
No. That depends on the contract terms and the reporting framework. The tool finds entries to vouch.
Is my data uploaded?+
No. Everything is processed in your browser.

Authoritative sources

ICAI — SA 500, Audit Evidence — Substantive procedures and evidence. Check the current text.
Always confirm against the latest version of the source. Regulations evolve and amendments are common.
Related calculators
Revenue recognition tester →Inventory count variance analyser →Invoice sequence gap finder →
Share this tool
Last reviewed: 2026-10-17 · For informational purposes only — not professional advice.