Seven ways your POS is leaking cash — and how to plug the holes

If you ask an owner where their cash leaks are, they'll usually point at the back door. The reality is messier. Most loss in a restaurant doesn't happen as one bold theft. It happens as a slow drip, weeks at a time, hidden in transactions that all look ordinary on the report. The good news: every drip leaves a fingerprint in your POS — you just have to know where to look.

Here are the seven leaks we see most often when we're called in to audit a struggling operation, and the specific reports or behaviors that surface each one.

1. What is the void-and-rering trick?

A guest pays cash. The server rings the order, takes the cash, then voids the ticket once the guest leaves and pockets the difference. The product still left the kitchen, but no sale shows in the POS. To find it, pull a void report grouped by employee and by daypart — the staff member ringing 4× the median voids on a Friday night isn't unlucky.

2. How does modifier abuse work?

On most cloud POS platforms, a server can ring a $14 burger as 'Burger – No Bun – No Fries – Add Avocado' and end up at $9. Sometimes that's a real preference. Often it's a discount being handed to a friend. Pull the modifier-frequency report by employee. If one server's 'No Bun' rate is double the rest of the floor, you have a conversation to have.

3. How do open-tab walkouts get hidden?

A guest finishes their meal, the bartender 'forgets' to close the tab, and at end of shift the manager force-closes a stack of tabs without the matching credit transactions. POS data won't always flag this — the tab gets closed eventually — but the credit-card batch totals will. If the tip-out and the batch don't reconcile within a couple percent, something is being absorbed.

4. What is cash-rounding skim?

Hospitality rounding sounds harmless. A $13.84 ticket gets paid with a $20, the staff returns six bucks, pockets sixteen cents. Multiply that by 200 transactions a shift and a year. Solve it by training staff that exact change is the rule and by enforcing it with a cash-discrepancy report — not by mistrusting your team.

5. How do comps get abused?

Comps are a real management tool — but they're also where the slipperiest leakage hides. We've seen operators where 9% of nightly sales were comped 'for guest recovery,' but only 30% of those guests were ever called back to verify. Run a manager-comp report. Anything above 1.5–2% of sales without documented reasons deserves a conversation.

6. How does buddy-punching show up on the POS?

Buddy-punching — one server clocking in another — is the oldest labor leak there is. It looks like nothing on the POS. It only shows up when you compare clock-ins to actual ticket activity. If a server is on the clock for two hours and rings zero tickets, they were either smoking, slammed, or not there.

Biometric clock-in (face or fingerprint) on the POS terminal eliminates this almost overnight. Most cloud POS platforms have it built in. If yours doesn't, it's a cheap third-party add-on and one of the highest-ROI changes a small restaurant can make.

7. What is discount stacking — and why is it allowed by default?

Loyalty + happy hour + employee discount on the same ticket can take a $48 check down to $12. Most POS platforms can prevent stacking, but the rules are off by default and the menu builder has to turn them on. Audit your loyalty redemption report for tickets where multiple discounts are applied. If the report has a 'discount type' column, sort by it and look for combos that shouldn't be possible.

Most owners feel uneasy about this. We get it — it can feel like surveillance. The frame that works is opposite: your team can't be trusted with anything if the system makes it impossible to be honest. Reports aren't traps. They're a way to keep good staff from being suspected, and to make the bad behavior visible enough that it stops on its own.