Hotpot restaurant cash office clerk - petty cash and small expense SOP: same-day produce runs, staff meals, emergency gas top-ups - the money nobody can explain, given rules that actually stick

You are a financial controls consultant for a hotpot chain. Draft a
"Petty Cash and Small Expense SOP" for one restaurant, with the store's
cash clerk as the owner. Output an archival policy document.

Customize it to the store information I provide:
- Headcount, floor area, staff dorm or not, how gas / utilities are
  paid
- Current weekly small-expense count and amounts (I'll give real
  numbers; if I don't, write "store to self-measure one week and fill
  in")
- Existing advance habits (who fronts money often, how long repayment
  takes)

The SOP must contain these seven sections, each at executable
granularity:

1. Float sizing and custody
- Sizing rule: round up from the weekly peak of two consecutive
  weeks of small spend; tier options (e.g., 500 / 1000 / 2000) for
  me to confirm before writing in
- Single custodian: one cash box, one custodian, key never lent;
  the manager is never also the custodian
- Kept separate from the cashier's change float - the two pools
  never offset each other

2. Cash payment whitelist
Only four categories: same-day small produce top-ups (per-item limit
for me to set), urgent sanitation and cleaning supplies, emergency
gas / utility top-ups, staff advances for sudden needs (first-aid
supplies, late-night cab after closing). Everything outside the
whitelist requires approval before spending.
For each category: per-transaction limit, monthly cap, and the
process when exceeded.

3. Advances and reimbursement deadlines
- Receipts submitted same or next day; reimbursement on fixed days
  (e.g., twice weekly, Tuesday and Friday)
- Documentation, any one of three: a receipt / a phone payment
  screenshot (merchant name and time visible) / a handwritten
  signed slip (unmanned street stalls, requires a witness
  signature)
- Unreceipted spend logged separately, with monthly caps on both
  count and amount

4. IOUs and overdue handling
What happens to advances unclaimed past a week: one reminder, a
hanging-balance cap, and beyond that the manager signs a special
approval - state plainly that special approval is not forgiveness,
it is a recorded transfer of responsibility.

5. Weekly count (the clerk's core ritual)
Fixed to the last trading day after close: cash on hand plus
unreimbursed receipts must equal the float. Difference tiers
(small change confusion within a few yuan / report at tens of yuan
and up), and how overages vs. shortages are each booked.

6. Monthly filing
Receipts bound by week; monthly summary metrics (count / amount /
IOU share); retention period phrased as "per local requirements" -
do not cite a specific regulation.

7. Red lines (the only non-negotiable section)
Petty cash never advances payroll, never fronts large procurement
deposits, never funds any personal bridging. Violations are defined
as fund commingling - not a discipline issue.

Constraints:
- No "manage strictly" or "raise awareness" sentences with no
  action in them
- All limits stay in 【】 for me to fill from store reality - do
  not invent numbers for me
- Write for employees: short clauses; no preamble, no
  scope-and-purpose boilerplate
- Output one printable SOP, maximum two pages

Why it is written this way

Petty cash rots almost never because the amounts get big - it rots because the range of what cash may pay for was never written narrow. A wide range lets a thirty-yuan scallion run, a three-hundred-yuan supply box, and a three-thousand-yuan bridging loan all flow through the same opening; the clerk has neither the bandwidth to audit each one nor a basis to refuse any. A whitelist of exactly four categories, each capped, makes "no cash" the default - exceptions must go through approval, and the friction of approval itself discourages most spending that had no business being cash.

The reimbursement deadline pairing with "screenshots count as receipts" is deliberate package design. A large share of restaurant small buys happen at unmanned stalls and neighborhood shops where invoices don't exist; a documents rule that accepts only invoices gets hollowed out by reality on day one. Accepting screenshots and signed slips buys the actual bottom line - every transaction leaves a trace. The trace doesn't have to be pretty; it has to exist.

The weekly count formula - cash plus unreimbursed receipts equals float - is the key anti-confusion identity. Count cash only, and everyone holding an advance becomes off-book debt: the float always looks "short" when the receipts are simply in someone's pocket. Folding receipts into the count turns stale IOUs from "the clerk chasing people" into "a count discrepancy" that surfaces every Friday without anyone's initiative being involved.

The red lines get their own section and their own name - fund commingling - to give the policy an anchor that needs no explaining. The moment petty cash starts advancing payroll or fronting supplier deposits, it stops being a small-expense tool and becomes a second ledger; that is not sloppy execution, that is a change in what the institution is. The section exists so that the second someone asks to borrow, the clerk has a ready-made "no" that isn't personal.

Variables