Why a stock or cash gap needs evidence
A busy service does not show whether every sale, receipt and stock movement was recorded. Compare the same time period and location before treating a cash or ingredient difference as a loss.
Staff-linked orders, recorded waste, stock counts and a daily cash-up give a manager a starting point for review. A discrepancy alone does not identify a dishonest employee or establish theft.
Five possible loss patterns to investigate
Use these examples as checks, not as evidence that a particular member of staff has done something wrong:
- Unrecorded sales — a customer pays cash, the order is never entered, the money goes straight to a pocket.
- "Friends and family" freebies — drinks and plates given away without a sale, draining stock you paid for.
- Over-pouring and short-pouring at the bar — spirits served generously to favoured customers, or watered down with the difference sold off-book.
- Voided and discounted orders — a bill is settled in cash, then voided in the system so it looks like it never happened.
- Stock walking out the back — meat, cooking oil, gas, and bulk supplies leaving with staff at the end of a shift.
Step 1: Make every sale belong to someone
Give each staff member their own access so recorded orders, voids, discounts and payments can be reviewed with their timestamps. These records help a manager ask specific questions; they do not guarantee that theft will stop.
For example, review who recorded a KES 200 bill, who changed it and when. Compare the bill with the payment and stock records before drawing a conclusion.
Step 2: Tie stock to sales, every single day
For an illustrative check, suppose you open with 48 sodas, record 30 sold, and have no receipts, transfers or waste. Expected closing stock is 18. If the count is 12, investigate the six-unit difference: a missing sale, breakage, an unrecorded transfer or a counting error could explain it. The difference is not proof of theft.
Configured recipes provide theoretical ingredient use from recorded sales. Compare that expected balance with a physical count, allowing for receipts, transfers, recorded waste and timing. Useful results depend on correct portions, units and records; the software does not measure the actual ingredients served.
Step 3: Reconcile cash and M-Pesa daily
Compare recorded cash sales with the drawer after allowing for opening float and documented payouts. Compare recorded M-Pesa tenders with verified completed payments. Keep card, credit, refunds and split tenders separate rather than expecting cash plus M-Pesa to equal every sale.
For an integrated STK prompt, check the payment result against the bill; an unconfirmed prompt is not a completed payment. Investigate differences while the shift's records are available, without assuming the cause is theft.
Step 4: Watch voids, discounts and comps
Review recorded voids, discounts and complimentary items alongside their reasons, timestamps, staff roles and underlying bills. A high count can reflect legitimate corrections or a different job, not necessarily misuse. Confirm the relevant permissions and approval workflow in a demo, then investigate exceptions with the manager.
Key takeaways
- Use individual staff access so recorded activity can be reviewed with its context.
- Compare expected stock with a physical count, including receipts, transfers, recorded use, waste and timing.
- Reconcile cash and M-Pesa daily so shortfalls surface the same evening, not months later.
- Review voids and discounts with reasons and bill records; a difference or unusual count is not proof of theft.
How DineHQ helps you investigate stock and cash differences
- Every order, void, discount and cash payment is logged against the staff member who processed it, with a timestamp.
- Configured recipes link recorded sales to theoretical ingredient use for comparison with stock counts and recorded movements.
- Integrated M-Pesa payment results can be reviewed against the associated bill alongside other tender records.
- Check staff access, relevant reports, your device and the proposed annual plan in a demonstration of your own workflow.
Annual plans
