Fast food restaurant cashier - shift-close reconciliation checklist - cash is one block out of four; vouchers, platforms, refunds, and the float are where over/short is born

You are a cashiering-process consultant for a fast food
restaurant. Build a shift-close reconciliation checklist.
The reader is the cashier ending their shift, handing
to the next shift or the manager. My store: [payment
methods, whether we take delivery and group-buy
vouchers, float amount, shift structure].

Four fixed blocks:

1. Cash:
- Count the drawer against the system's expected
  cash; record over/short to the cent
- Count the float, matching the store standard,
  signed by two people
- When over/short is non-zero, the check order:
  the large-change tickets first (bills paid with
  hundreds), then parked tickets never settled -
  only after both may the record read "cause
  unknown"
2. Electronic payments:
- Each payment method's daily total against the
  system statement
- Discrepancy check order: network-delayed captures
  -> duplicate scans -> refunds not synced - and
  for each, state how it's checked
3. Vouchers and platforms (where over/short breeds):
- Voucher and group-buy redemption counts against
  the platform backend
- Platform order counts against the store's kitchen
  tickets - a one-order gap is one missed sale or
  one wrong refund
- Every refund of the day recorded line by line:
  time, amount, reason, who - any unrecorded
  refund gets flagged red on the checklist itself
4. Paperwork and handover:
- Refund, void, and comp slips clipped and handed
  over
- Over/short and anomalies written into the shift
  log - verbal-only handover is not acceptable

Every item must carry a "first check on mismatch"
action; only after checking and still failing to
explain may the entry read "cause unknown".

Output format:
- Table: block / item / pass standard (which two
  numbers match which) / first check on mismatch
- Close sign-off line: outgoing cashier, incoming
  cashier, time, over/short amount - four fields
- A one-page print layout that tapes inside the
  register station

Constraints:
- No payment-platform names or fee rates - platform
  actions written generically; specifics follow
  this store's dashboards
- No specific amounts or count thresholds - [per
  store policy]
- No liability language ("the cashier shall bear...")
  - the checklist governs checking actions only

Why it is written this way

Cash being just one block of four reflects where the money actually leaks now: at most fast food stores cash is the minority of transactions, and the structural sources of over/short have moved to vouchers and platforms - redemption counts that don't match the backend, platform orders that don't match kitchen tickets. Catch those tonight or untangle them from tomorrow's settlement. Most reconciliation checklists still stop at counting the drawer; the four-block structure is the dividing line from generic templates.

The core discipline is the repositioning of "cause unknown". A high share of unknowns in the close record isn't a money problem - it's an unenforced checking procedure: without a prescribed order, people naturally start with the hardest check and give up. Lock the order (large-change tickets first, then parked tickets, only then "unknown") and unknown turns from default into earned conclusion - and its share falls on its own.

The order itself is deliberate: large-change mistakes are the most common, hence first; parked tickets second. That's sorted by hit probability times checking cost. Get the order wrong and the checklist becomes an unpaid audit that finds nothing.

Refund lines live in the vouchers-and-platforms block, not paperwork, because refunds are the shared channel of both error and fraud. Line-by-line records aren't distrust - they're what lets a careful cashier prove themselves clean every night. The four sign-off fields (out, in, time, amount) exist for the same reason: reconciliation ends with a signed sheet, not with "looks right".

Variables