Short answer: count the till unannounced, so the count measures the till and not the preparation; reconcile the bank and compare deliveries with invoices every week; and each month review three things: cancelled or reversed documents, entries dated into a closed period, and changes to master data such as prices and supplier bank details. Write down what you checked each time.
Key takeaways
- A surprise count works because it removes warning: arrive unannounced, secure the drawer, record the system figure, then count.
- Count in the custodian's presence and have both parties sign the result — never count alone.
- Daily: till counted and banked intact. Weekly: bank reconciled, deliveries versus invoices, refunds and voids reviewed.
- Monthly: review cancelled or reversed documents, anything dated into a closed period, and changes to master data such as prices and bank details.
- Master data changes deserve as much attention as transactions — one price change affects every future sale.
- Write down what you checked and what you found; a review with no record cannot show a pattern over time.
Controls that exist only as rules decay quietly. The routine that keeps them honest is a short, regular review — daily for cash, weekly for the money trail, monthly for the things that change underneath everything else. None of it takes long once it is a habit; the difficulty is entirely in doing it on a schedule rather than when something already feels wrong.
The surprise cash count is the part most often done wrong. A count announced in advance measures how well someone can prepare for a count. Only an unannounced one measures the till.
Running a surprise count
- Arrive unannounced. No warning, no pattern. Rotate which float or drawer you count.
- Stop transactions on that drawer for the duration.
- Record the expected figure first — the system's recorded takings for the shift, plus the opening float — before any cash is counted.
- Count in the custodian's presence. Never count someone's float alone: it protects them as much as it protects the business.
- Compare and record. Write down the difference, whatever it is, including zero.
- Both sign the count sheet.
Step 3 matters because a count taken after seeing the expected number tends to arrive at that number. Step 4 matters because a count conducted without the custodian present is not evidence of anything either party can rely on.
"The first Monday of the month" is a scheduled count wearing a surprise count's clothes. Vary day, time and target — that unpredictability is the entire mechanism.
The weekly and monthly rhythm
| Frequency | Check | Who |
|---|---|---|
| Daily | Till counted against recorded takings, banked intact | Cashier, witnessed by supervisor |
| Weekly | Bank reconciled | Someone who did not handle the money |
| Weekly | Deliveries without invoices, invoices without deliveries | Sales or finance |
| Weekly | Refunds, voids and discounts by cashier | Supervisor or owner |
| Monthly | Cancelled and reversed documents | Owner |
| Monthly | Entries dated into a closed period | Owner |
| Monthly | Master data changes: prices, terms, supplier bank details | Owner |
| Quarterly | Stock count on high-value lines; vendor list review | Rotated |
The weekly items are the ones that catch problems early enough to fix cheaply. The monthly items are the ones that catch problems at all.
The three things to look at monthly
Cancelled and reversed documents. Every accounting system lets you cancel, void or reverse a document, and the ability is necessary — mistakes happen. What is worth reviewing is the pattern: how many, by whom, and for what reason. A cluster on one person's entries, or on one customer's account, is the signal. The volume is usually small enough to scan in minutes.
Entries dated into a closed period. Once a month is reviewed and closed, a new entry dated into it changes a number you already reported. Sometimes that is legitimate and deliberate. It should never be routine, and it should never happen without the owner knowing. If a correction is genuinely needed, the clean options (reopen the period, or post a correcting entry in the current one) are covered in common month-end closing mistakes.
Master data changes. Selling prices, customer credit terms, supplier bank accounts, product costs. One edit here outweighs most individual transactions, because it applies to everything that comes after it. Check what changed, who changed it, and whether it was requested by someone entitled to request it.
A review with no record cannot show a trend. One line per review — date, what was checked, what was found, what was done — turns a series of one-off looks into evidence of a pattern. It is also the only way to answer "when did we last check this?" honestly.
Who does the review
Independence matters more than seniority. The rule is simply that the reviewer did not handle the money or the goods being reviewed. In a very small business that usually puts the bank reconciliation review, surprise counts and master data checks with the owner personally — these are the compensating controls that stand in for separation of duties you do not have the headcount to arrange.
Two Reyuko features support this routine directly.
The activity log. Reyuko records sign-in activity per user — successful sign-in, failed sign-in, unlock, auto-lock and sign-out — in an activity log page under Settings, visible to the owner-level role. That answers "who was signed in, and when", which is the context a review of unusual entries needs.
Period locking. Once an accounting period is closed in Reyuko, the posting engine itself refuses entries dated into it — the refusal comes from the core, not from a warning dialog someone can dismiss. That turns "entries dated into a closed period" from something you hunt for into something that needs a deliberate reopening to happen at all.
Reyuko also has a notification bell on the home screen carrying reminders and alerts — calendar reminders, stock and expiry alerts, and receivable ageing — which is useful for the routines that are easy to forget. Before relying on any of this to detect a specific thing, check what it does and does not record, using the test in verifying a feature before you rely on it.
Build the review calendar
- Put the daily till count and weekly bank reconciliation in the calendar with named owners.
- Schedule three or four surprise counts a year at irregular intervals, and rotate the target.
- Add the monthly three: cancelled documents, closed-period entries, master data changes.
- Keep a one-line log of every review: date, scope, finding, action.
- Review the log itself each quarter — the patterns live there, not in any single check.
Reviews tell you what happened. The last two lessons are about limiting what can happen: designing an access matrix, then letting the software enforce it.
Reyuko