Most month-end errors aren't wrong amounts. They are right amounts in the wrong month.
Cut-off procedures check that revenue, costs, receipts and payments near the period end are recorded in the period they belong to. Test transactions a few days either side of month end: match sales to delivery dates, purchases to goods received, and accruals to the service period. Fix errors with journals and look for the process that let them through.
A sale invoiced on the 1st for goods delivered on the 30th belongs in the earlier month. A supplier invoice dated next month for a service used this month needs an accrual. Small cut-off errors move profit between months; at year end they move it between years, which is exactly what auditors test.
| Area | Test | Evidence |
|---|---|---|
| Sales | Invoices in the last and first few days: is the delivery or service date in the same period? | Delivery notes, timesheets, contract milestones |
| Purchases | Goods received near month end: is there an invoice or an accrual? | Goods received notes, GRNI report |
| Services | Services used but not yet invoiced | Contracts, usage reports, emails |
| Inventory | Goods shipped and received around the count date | Despatch and receiving logs |
| Cash | Receipts and payments on the last day | Bank statement, remittances |
Export invoices dated in the first five days of the new month and the last five days of the closing month, with the delivery date. Then flag mismatches:
=IF(EOMONTH(InvoiceDate,0)<>EOMONTH(DeliveryDate,0),"CHECK","OK")
Every CHECK is either a genuine cut-off error or a legitimate case, such as advance billing, that you can document.
Post a journal to correct each error, then ask why it happened. If sales invoices are always raised late, move invoicing to the day of delivery. If receipts are booked late, set a receiving deadline before the close. Each fix makes next month's cut-off test shorter.
Cut-off ties into the accruals routine, the GRNI review and your close calendar.
At year end, extend the testing window, include inventory movements around the stock count, and review credit notes issued after year end for returns that relate to the old year. Keep the cut-off workings with the year-end file: auditors will usually perform their own cut-off tests and ask to see yours.
Cut-off testing is the same in both countries. Revenue timing follows IFRS 15 in the UK (or FRS 102 for many private companies) and ASC 606 in the US; both look at when control of goods or services passes to the customer.
Reviews every balance sheet reconciliation with an on-device AI and 20 review tests, flags vague and wrong-account reconciling items, and builds a risk-ranked review queue. Runs in your browser on your own computer: nothing is uploaded.
12 questions on how strong your close controls are. Free to use online.
The Month-End Close & Controls System tests the trial balance against the sum of reconciled balances, keeps every open item on one exception dashboard and blocks sign-off while exceptions remain open. Excel, no macros, one-time price.
A transaction recorded in the wrong accounting period, such as a sale invoiced in the next month for goods delivered in this one.
A few working days is usual. Extend it if your business invoices in batches or has slow receiving.
Someone in the finance team who didn't raise the invoices or book the receipts, with results reviewed by the controller as part of the close sign-off.
Yes. They misstate each month's results, and at year end they misstate the annual accounts.
Last updated 21 October 2026. General guidance for finance teams; check it against your own policies, systems and local rules.