Gaming Lounge Shift Reconciliation: A Step-by-Step Guide for Owners

Why shift reconciliation matters

Every lounge owner knows the feeling: the shift ends, you count the cash, and it's Ksh 200–500 short of what you expected. Nobody stole anything obvious. There's no single incident you can point to. The money just didn't materialise.

This is what happens when sessions run without proper tracking. The problem isn't the Ksh 300 shortfall — it's that you can't explain it, which means you can't prevent it tomorrow.

A proper shift reconciliation solves this. It creates an audit trail for every session, payment, and cashout in a shift — so when the numbers don't match, you can find exactly where they diverged.

The components of a shift reconciliation

A shift reconciliation is a calculation. It has five inputs:

1. Opening float. The cash in the till at the start of the shift. This is the starting baseline. It should be counted and confirmed by both the incoming and outgoing staff member at handover.
2. Session revenue. Total income from all sessions during the shift. Each session contributes its charge — calculated automatically in PsTally based on duration and game rate.
3. Product sales / cashouts. Revenue from products sold, snacks, accessories, or other items not tied to a session. These add to the expected till amount.
4. Expenses paid out. Any cash paid out during the shift — for purchases, supplier payments, or petty cash. These reduce the expected till amount.
5. Closing float (actual). The cash physically counted in the till at shift end.

The formula: Opening float + revenue + product sales − expenses = expected closing float. Compare against actual. The difference is the discrepancy.

Step-by-step: how to run a proper shift

The most common causes of discrepancies

In order of frequency in Kenyan gaming lounges:

1. Ghost sessions — a session runs without being logged. The most common cause of unexplained cash shortfalls. See our guide on ghost sessions for details.
2. Unrecorded cashouts — a product is sold but not logged. The cash leaves the till but isn't reflected in the reconciliation.
3. M-Pesa vs cash misattribution — a payment received via M-Pesa is logged as cash, or a cash payment is logged as M-Pesa. Doesn't affect total revenue but distorts the cash count.
4. Incorrect change — staff gives more change than required for a transaction without logging it as a correction.
5. Opening float miscounted — the previous shift's closing float was miscounted or the handover was rushed. A Ksh 100 opening float error cascades through the entire shift.

How PsTally handles shift reconciliation

PsTally tracks the entire shift lifecycle automatically. When a staff member opens their shift, they enter the opening float. Throughout the shift, every session, cashout, product sale, and expense is logged. At shift close, PsTally calculates the expected closing float and compares it to the amount the staff member reports.

Discrepancies are highlighted immediately. If the actual and expected amounts don't match, the staff member must either account for the difference or record it as a discrepancy. The shift cannot be silently closed with unresolved gaps.

At close, PsTally sends the full shift report to the owner's WhatsApp automatically — total sessions, cash received, M-Pesa received, cashouts, and any discrepancy. The owner sees the shift numbers the same evening, not the next week when they check the cash drawer.

FAQ