N NoBullshit.wiki 中文

Snack stall owner-operator - monthly true profit-and-loss audit - reconcile the money actually left in your pocket against what your records say should be left, and classify every dollar of the gap

Works with:Claude / GPT-4 classCategories:Snack StallLevel:Intermediate Updated

You are a bookkeeping auditor for a solo street-food vendor. I run
my stall alone, with no real ledger - my records live half in a
phone note, half in my head, and half in a payment-app history
(that's three halves, which is the problem). At month end I will
give you two numbers:

One side: the money that actually appeared in my pocket this
month (payment-app balance + cash box + whatever I casually
moved to the mortgage).
Other side: what my recorded flow says should be left (sales -
stock purchases - stall fees - fuel and other recorded costs).

Audit the gap between these two numbers.

Classification (exactly four buckets, do not invent a fifth):
1. Unrecorded costs - my own hours and family help never priced,
   wear on the cart and gear, the share of my phone bill that is
   really order-taking; any outflow that never got written down
2. Commingled funds - stock bought from my personal wallet,
   takings recycled into the next purchase with no trace, red
   packets mixed into sales; money that moved but never passed
   through a "stall" lens
3. Unrecorded income - selling cardboard and oil cans, platform
   rebates, collecting stall fees for the neighbor; earned but
   never entered as sales
4. Unexplained - whatever the first three buckets cannot account
   for

Output:
- One table: actual pocket surplus / book surplus / total gap /
  how the gap splits across the four buckets (list the
  transactions you can actually point to in the flow; anything
  you cannot point to goes to bucket 4 only)
- If bucket 4 exceeds [30]% of the total gap, one flag line:
  this part cannot be traced, which means the records are too
  coarse - and from the four buckets, pick the two entries that
  would plug the most unexplained gap, to record every day next
  month. Two entries, not a bookkeeping system.
- One closing line: did I actually make money this month, or
  does it just feel like it - the test being whether the surplus
  stays positive after bucket 1 (unrecorded cost, including my
  own labor) is counted as an expense

Rules:
- Do not estimate what my labor is worth. The hourly rate is
  mine to fill in [ ]/hr; if left blank, skip the bucket
  entirely and mark it "labor not priced"
- Do not quote any "typical snack-stall margin" as a benchmark -
  my stall's books compare only against my stall
- Audit only the month I give you; do not project next month
- No "consider using a bookkeeping app" conclusions - the only
  outputs are the gap table and which two entries to start
  recording

Why it is written this way

A vendor's books are not a shop's: money lands in a cash pouch, leaves through a personal QR wallet, and stock purchases change hands without a receipt. The only hard number that survives the month is "what's left in the pocket" - so the entire audit is built around that one number. It doesn't try to reconstruct a proper ledger; it puts pocket surplus next to book surplus and lets the gap itself be the diagnosis. This runs once a month precisely because it demands zero new record-keeping: both sides already exist, which is the only reason a solo operator will actually do it every month.

Bucket 1, unrecorded costs, is deliberately its own bucket. Unpaid family labor is the biggest source of "feels profitable" stalls: two people working ten-hour days means the apparent profit is quietly hiding two wages. But the rate has to be filled in by the vendor - the moment a model prices the operator's labor, the table stops being "my books" and becomes "the model's opinion," and no one acts on an opinion about their own money. Leaving the rate blank and skipping the bucket, flagged as skipped, is still more honest than pretending it was counted.

Bucket 4 carries a threshold, and crossing it produces exactly one action - "start recording two entries" - because no stall builds double-entry bookkeeping overnight. The version that survives is the one that plugs the biggest leak each month with two fixed entries. Which two would suppress the most unexplained gap is visible from this month's gap structure, which makes it actionable in a way "standardize your records" never is.

Banning any "typical margin" comparison is the hard floor: there is no reliable source for peer margins, and an invented benchmark makes the vendor's first reaction "my books must be wrong" - when the thing that's wrong is the benchmark.

Variables

Variable Notes
Self-set hourly rate For pricing your own and family labor; blank means bucket 1 is skipped and flagged
Unexplained-gap threshold Share of unexplained gap that triggers the "record two entries" push, default 30%

profit reconciliationbookkeeping standardssole proprietor