Cash over and short: 4 steps to close it
The last three lessons completed the daily cycle: the till is counted at opening, handover and close, and every difference is logged "for review". What does that review involve? Often a list that grows every week until month-end files it under "minor differences".
A difference logged but never reviewed is barely better than one never logged. Here are four steps that close each shortage or overage with a decision, in one weekly WhatsApp exchange.
Why differences pile up unresolved
- Overages are treated as gains: extra riyals rarely get questioned, yet may mean a miskeyed sale or an overpaying customer. An overage is an error too.
- Shortages get netted against overages: Sunday's shortage cancels Wednesday's overage, so the week looks balanced while hiding two errors.
- Reasons are written but never closed: "supplies on a handwritten receipt" is fine, but until the expense is recorded the difference stays open.
- Nobody sees the repetition: each difference looks small; only side by side does a pattern emerge.
The four steps
1. Classify each difference from a short list
Replace free-text reasons with five fixed causes: a miscount or wrong change, an unrecorded expense paid from the till, the wrong payment method (card entered as cash or the reverse), an unrecorded cash refund, and unknown. Fixed causes make differences comparable, like the exception log from an earlier lesson.
2. Tie it to a window and a person
This is where counting three times a day pays off. A difference found at handover belongs to the morning shift; at close, to the evening shift. At opening, it falls outside any shift: a miscount, or cash that moved overnight. That is the most serious kind, sent straight to the owner. Naming a person is not an accusation; it decides who is asked first.
3. Close it with one of three decisions
Each difference leaves the review with one decision: correct it when the cause is known and recordable, such as an expense with a receipt; accept a counting error below a threshold you set in advance; or escalate anything above the threshold or without a cause. Record a missing expense with its receipt photo in a minute from your phone. Never make a salary deduction automatic: any deduction from wages falls under the Saudi Labor Law, so check with your advisor first.
4. Look for the pattern every week
Then ask one question of the whole set: do differences repeat on the same shift, weekday or payment method? A difference that keeps appearing in one place usually means a broken procedure step, not an employee's mistake. Fix the procedure, not the person.
The review as one exchange
No spreadsheet needed; one line starts the review:
Supervisor: this week's differences
System: Al-Yasmin branch, Sunday to Thursday, three open differences. Sunday close: 50 SAR short, reason: cleaning supplies on a handwritten receipt. Wednesday close: 30 SAR over, no reason. Thursday close: 70 SAR short, no reason. Send Sunday's receipt so I can record the expense.
Supervisor: [receipt photo]
System: Expense recorded, Sunday closed. The other two fell on evening shifts, each with a fault logged on the second card terminal. That usually means a card sale entered as cash or the reverse. Please check the terminal's end-of-day reports against the records.
Supervisor: Wednesday: a 30 SAR cash sale entered as card. Thursday: a 70 SAR card sale entered as cash
System: Corrected both and closed them. Nothing open this week. Shall I add a payment-method check to the daily close while the second terminal is in use?
Supervisor: yes
Three differences, two causes, and one permanent fix to the close instead of a warning to an employee.
Checklist before weekly reviews
| Item | Decide in advance |
|---|---|
| List of causes | Five fixed causes, "unknown" among them |
| Acceptance threshold | The amount below which a counting error is accepted |
| Review time | A fixed weekday and a named person who runs it |
| Opening differences | Escalated straight to the owner |
| Difference left open | Days before it escalates automatically |
A common mistake: judging the week by its net figure
The easiest review adds up the differences and reads the net. Here the net was 90 SAR short, small enough to tempt you to close the file, yet it hides an unrecorded expense and a payment-method error that happened twice. Stop at the net and you never learn the second terminal is causing differences, so they return next week. Review each difference first, then the total. More in the system over WhatsApp.
In short: never leave a difference "for review" forever. Classify it from a short list, tie it to its shift, close it by correcting, accepting or escalating, then look for patterns weekly. Treat overages like shortages, never net one against the other, and have opening differences reach you directly.