Vegetable stall checkout - the closing-time till checklist: cash, QR takings, tabs and tomorrow's float - four jobs, ten minutes

You are a closing-routine checklist designer for a vegetable stall. Generate my
closing-time till checklist. Premise: the stall takes cash and QR payments, plus tabs;
by close I've been standing all day and want to go home - so the checklist must be
doable in ten minutes, every line one concrete action.

Four fixed blocks (order locked: count the visible money first, reconcile the invisible
money second):

Block one: cash box count
- Sort and count by denomination (give me a recording format: denomination x count =
  subtotal)
- Total it, compare against today's rough cash tally
- Large notes pulled and set apart (for the bank or to take home); the box keeps only
  tomorrow's float - a FIXED amount, written at the top of this checklist (if I set
  two hundred, it's two hundred every day, topped up at close)
- The float's denomination mix matters: stock it by what today's change-giving
  actually demanded (give me one line: "read today's change record, buy tomorrow's
  small notes accordingly")

Block two: QR takings reconciliation
- Open the payment platform's daily statement; check two things: total amount and
  transaction count
- A count mismatch (my tally vs the statement) is more common than an amount mismatch
  - a missing transaction usually means a customer typed the amount and walked off
  without pressing pay; scrolling the statement by timestamp right now finds it
- Give a three-step search order for any mismatch (refunds first, then two
  adjacent-timestamp entries, then my own missed records)

Block three: tabs
- Today's new tabs go into the book tonight (paper or tool), never carried overnight
- Glance at the tab total while there: any red rows, anything a week stale with no
  movement - if so, one casual mention tomorrow. No chasing; just let the customer
  know the ledger exists

Block four: close the day
- Cash total + QR takings + new tabs = today's takings; write it in ONE fixed place
  (notebook or tool) - tomorrow's buying trip needs this number
- Box locked and put away; checklist ticked and filed (one page per week; by month-end
  the pages chain into the month's underlying ledger)

Format:
- Each item = checkbox + one line of action, concrete down to "look at what, write
  what"
- Three blanks at the top of the checklist: float amount / tab-nudge age / ledger
  location - filled in once, followed forever
- Fifteen items total, maximum - nobody closing a stall reads a second page

Constraints:
- No "install a POS", no "use reconciliation software" - this is a paper checklist
  equipped with one notebook and one pen
- Do not prescribe a float amount - each stall sets its own; a hardcoded number gets
  ignored, a blank gets filled in
- Every item must be a "skip this and something breaks" item; delete the padding

Why it is written this way

The daily close's natural enemy is "tomorrow" - not laziness, exhaustion. So the whole checklist optimizes for exactly one goal: ten minutes, done. The four blocks run "visible money first, invisible money second" on purpose: counting cash is physical labour and gets done while any energy remains; reconciliation and tab-keeping, the thinking work, comes after, because the more tired you are, the more the front-loaded mechanical part protects you.

The fixed float is the checklist's most valuable single line. Without a fixed level, the box holds a random amount every day and "today's cash income" is never computable; with one, income = closing cash - float, a single subtraction, no double counting needed. Stocking tomorrow's small notes "by today's change-giving" is learned practice: the morning crowd pays cash, tens and twenties leave as change most, so tomorrow's float should mirror today's change record - a rule that updates itself daily and beats any fixed denomination table.

"Transaction count mismatches more often than amount" earns its place on the list because it is counter-intuitive experience: amount differences catch the eye, but the high-frequency reality is a missing entry - a customer who typed the sum and left without pressing confirm. Making "check the count" a formal step with a three-step search order keeps reconciliation from stalling the first time a difference appears. And the ban on "get a system" carries the same reasoning as every stall entry: paper, pen, ten minutes - the entire set of preconditions for this checklist to actually run at close of trade, every day.

Variables