Bubble tea month-end close checklist for the cash office - bank, in-transit payouts, stored-value liability, float, and receipts: five lines, each with its chase-this-first move

You are the cash office clerk for a bubble tea
chain. Give me a month-end close checklist usable
for one store or a few, organized as five lines,
ticked item by item on close day.

Every item carries three fields: what to match
(what each of the two figures is), the pass line
(how close is close enough), and chase-this-first
(the first move when it does not balance - not a
full investigation).

Line 1 - bank:
- Platform payout deposits matched line by line
  to bank statement: settlement statement
  amounts vs bank credits
- QR-code settlement deposits vs POS
  mobile-payment flow
- If off, check first: the cross-month in-transit
  list - payouts initiated at month-end landing
  next month, carried as in-transit only with
  pending-settlement detail behind them; a
  difference with no detail behind it is
  reported as a difference, not parked

Line 2 - platform in-transit:
- Orders from the final [N] days of the month
  settle next month; this month's in-transit
  equals the platform backend's pending
  settlement detail summed item by item - never
  last month's in-transit number, never an
  estimate

Line 3 - stored-value liability:
- Opening balance + sales and top-ups −
  redemptions − refunds = closing balance;
  all four exported from the system and
  reconciled
- A month where redemptions exceed sales is not
  automatically wrong - old cards running down
  - but the reason goes in the notes; never
  pass it silently
- Stored-value cash is a liability, not
  revenue: its own line on the close sheet,
  never folded into sales

Line 4 - float and change:
- Each store's counted float vs the ledger
  base; over/short logged with amount and store
- If off, check first: unresolved end-of-shift
  variances from this month - most month-end
  differences are one unclosed shift rolling
  forward

Line 5 - receipts:
- Purchases, rent and utilities, platform
  service fees filed by store and month;
  missing items listed as a gap sheet
- Platform service-fee invoices checked per
  platform: invoiced amount vs total fees
  deducted - the gap becomes next month's
  first errand

Output format:
- One A4 page, five sections, checkboxes on
  every item
- One "line verdict" row per section: balanced /
  variance amount / cause located
- After close day, one exception report:
  amounts, investigation status, items needing
  the manager's or owner's decision

Constraints:
- The checklist ends at reconciliation and
  escalation - no tax filings, no journal
  entries; that is the outside accountant's
  territory, and crossing it tangles both books
- "Chase-this-first" gives exactly one move, not
  an investigation tutorial - close day affords
  one step per item; a dead end goes to the
  exception report, not an all-night dig
- In-transit amounts must be backed by itemized
  detail; the words "estimated in transit" do
  not appear on the close sheet

Why it is written this way

One chase-this-first move per line, instead of a full investigation guide, reflects close day's real constraint: five lines in one day means one step per item. The correct handling of a dead end is escalation, not digging until dawn - the checklist shields the clerk from self-imposed all-nighters, and the exception report is the exit built for exactly that step.

In-transit must be backed by itemized detail because in-transit is the most comfortable dumpster in a close: any difference can be dropped in with "it'll clear next month," and the ease of dropping it in equals the pain of the reconciliation that never converges. Itemized detail forces in-transit to become checkable fact, which closes the dumpster.

Stored-value liability gets its own line with "liability, not revenue" spelled out because it is the single most common conceptual error in this trade's cash offices: the day the card-sale money arrives, no revenue has happened; months that mix it into sales show growth that was borrowed, and it surfaces only when the cards come due for redemption. Redemption-exceeding-sales months get noted rather than silently passed for the same reason - old cards running down is healthy, but it has to be health that someone saw, not a number that got skipped.

The boundary stops at reconciliation and escalation - no filings, no entries - because that is the division between this checklist and the accountant's work. The moment a clerk starts adjusting books against differences directly, the outside ledger drifts further from store reality, each book edits itself, and the differences multiply instead of resolve.

Variables