How restaurants lose money to staff theft

And how permissions, void tracking and cash-up reports can stop small losses becoming a daily habit.

A till can balance perfectly and still be losing you money. That is the uncomfortable part. A staff member who knows the routine may not need to grab notes from the drawer. A cancelled sale, an unrecorded drink, a generous “manager” discount or a refund sent to the wrong card can hide inside an ordinary shift. Most losses do not arrive as one dramatic event. They arrive in small amounts, mixed in with genuine mistakes and rushed service.

Ten pounds here. A bottle there. A meal given away after closing. Each one is easy to dismiss. Repeated over weeks, the numbers stop being small. The answer is not to treat every employee as a suspect. That wrecks morale and still leaves gaps in the system. The answer is to make sensitive actions clear, attributable and reviewable. A good point of sale setup does exactly that.

Where the money goes

The problem is wider than the cash drawer

Theft often looks like a normal till action

Restaurant owners tend to picture theft as cash being taken from the drawer. That happens, but it is only the obvious version. Modern restaurant theft often uses a perfectly legitimate function for the wrong reason.

A server takes cash for a round, then voids the transaction and keeps the money. A cashier rings a £32 order as £22 and pockets the difference. A supervisor uses a staff discount for friends. A refund is processed after the guest has left, but the money goes to a different card. A takeaway order is prepared, handed over and never entered into the till at all.

Stock can leave through the same gaps. Drinks are served without being rung in. Premium ingredients are recorded as wastage. Complimentary meals become a quiet perk for friends. Loyalty points are added to a staff-controlled account, then redeemed later. Tips intended for the team may be removed before the pot is counted.

These acts vary in seriousness, but they share one feature: the transaction trail is weak, shared or easy to alter. The dishonest action is hard to separate from an innocent mistake.

If everyone uses the same login, the audit trail does not identify anyone. It records the device, not the decision. The wider fraud picture backs up the need for basic controls. The Association of Certified Fraud Examiners classifies theft or misuse of an employer’s cash, stock and other resources as asset misappropriation. In its 2024 global study of occupational fraud cases, this was the most common category. The figures are not restaurant-specific, so they should not be treated as a forecast for your business. They do show that everyday assets are a common target when controls are weak. That is why the first job is not to install more cameras or write a harsher policy. It is to remove ambiguity from the till.

Permissions — Control one

Personal logins make every action accountable

A shared four-digit code feels convenient during a rush. It is also a gift to anyone who wants to hide. When six people can use the same manager login, a suspicious refund tells you almost nothing.

Give every user their own account. The code should be private, quick to enter and removed as soon as that person leaves. Do not keep former employees active “just in case”, and do not write the manager PIN beside the till. Those sound like basic points because they are. They are also where many systems fail in real restaurants.

Then match access to the job. A new server may need to open tables, add items, split bills and take payment. They probably do not need to change prices, issue post-payment refunds or delete transactions. A shift supervisor may need to approve a void or comp. Only the owner or general manager may need access to payroll exports, system settings and historical reports.

Use approval for the risky moments

Permissions should not make staff hunt for a manager every time somebody changes chips to salad. Put approval around actions that remove money or erase evidence:

• Refunding a completed payment, especially without the original card or receipt.
• Voiding an item after it has been sent to the kitchen or bar.
• Applying a large discount, a complimentary item or an open-price adjustment.
• Reopening a closed bill, deleting an order or changing its payment type.
• Opening the cash drawer without a sale.

A useful rule is to let staff correct ordinary mistakes while requiring approval for actions that change the financial outcome. Set sensible thresholds. A manager should not be dragged over to approve a 50p correction, but a £40 refund should not pass under a trainee’s login.

Do not build a bottleneck. If the control is so awkward that staff borrow a supervisor’s PIN to keep the queue moving, the permission exists only on paper.

Role-based access protects honest staff too. When each person can perform only the tasks they are trained and authorised to do, they are less likely to be blamed for somebody else’s transaction. Accountability works both ways.

Voids and refunds — Control two

A void is not suspicious until the pattern is

Voids are part of restaurant life. A guest changes their mind, a server taps the wrong item, the kitchen runs out of sea bass or a duplicate order reaches the bar. Blocking voids altogether would turn minor mistakes into arguments.

The better approach is to keep the function and capture the context. Every void should record who made it, when it happened, which table or order it affected, what was removed, its value and why. If approval was needed, the report should show who authorised it. The same principle applies to refunds, discounts, complimentary items and reopened bills.

Use a short list of clear reason codes: customer changed mind, item unavailable, duplicate entry, kitchen error, service recovery, manager comp. Avoid a catch-all “other” button unless it requires a note. If half the team selects “mistake” for everything, you have collected a label rather than an explanation.

Look for combinations, not isolated numbers

One high void count does not prove theft. The bartender on the busiest station may make more corrections simply because they handle twice as many orders. A new starter may have several genuine errors in their first week. The useful question is whether the activity makes sense beside the rest of the shift.

Patterns worth reviewing include:

• Voids after food or drinks have already been prepared.
• Refunds clustered near closing time or processed long after the original sale.
• Discounts repeatedly applied to cash transactions, friends or the same customer account.
• One employee’s void rate rising well above colleagues doing similar work.
• No-sale drawer openings followed by cash shortages.
• Large tips attached to discounted or refunded bills.
• Reopened bills whose payment method changes from card to cash.

Compare rates as well as totals. Twenty voids from 500 transactions tell a different story from twenty voids from 80. Compare similar roles, sections and service periods. Lunch counter service should not be judged against a packed Saturday night on the bar.

Most importantly, review the underlying receipt before speaking to anyone. A report is a prompt to ask a question. It is not proof of intent.

Cash-up reports — Control three

A proper cash-up turns a hunch into a trail

“The till is a bit short” is not enough information to manage anything. A useful cash-up tells you what the system expected, what was counted, the difference, who counted it and what happened next.

Start each drawer with a recorded float. Where practical, assign the drawer to one person or a small team for the shift. If twelve people dip into the same till, responsibility disappears. Record paid-outs, petty cash and float movements at the time they happen, not from memory at midnight.

At close, count the drawer away from the sales total if your system supports a blind count. The person counting enters the physical amount before seeing what the till expects. That removes the temptation to make the count “fit”. A second person should verify material differences, and both names should appear on the record.

The report should reconcile:

• opening float and cash sales;
• cash refunds, paid-outs and declared tips;
• cash added to or removed from the drawer;
• expected closing cash against the physical count;
• card totals against the payment provider or terminal batch;
• delivery-platform and online-order payments against their settlement reports.

Small differences still need a reason

A £3 shortage may be a wrong coin, a rushed change calculation or a genuine mistake. Recording it is not an accusation. The point is to see whether the same person, till or shift keeps producing the same kind of difference.

Review both shortages and overages. An overage can mean a sale was under-rung, a cash payment was entered incorrectly or change was shorted. A drawer that is always exactly right can also deserve a look if other reports show unusual voids or unrecorded stock movement. Cash-up only tells one part of the story.

Do not ask “Who stole £20?” Ask “Which transactions explain the £20 difference?”

That wording matters. It keeps the review factual and stops a routine discrepancy from becoming a public accusation. In a busy restaurant, process errors are common. Good records help you tell an error from a pattern.

The review routine

Ten focused minutes beats a folder nobody opens

A restaurant can collect immaculate audit data and still lose money if reports are reviewed only after a bad month. Keep the routine short enough to survive a busy week.

Every day: clear the exceptions

The closing manager should review cash variances, large refunds, unusual discounts, post-kitchen voids, reopened bills and no-sale drawer openings. Each exception needs either a sensible explanation or a follow-up. Add a note while the shift is fresh. “Customer sent steak back; approved by Sam” is useful. “Sorted” is not.

Do not flood the report with routine noise. Set thresholds that match the business, and refine them when too many harmless transactions appear. The purpose is to make odd activity stand out, not to produce a hundred-page daily dump.

Every week: compare people, shifts and locations

Look at rates per transaction or per sales value. Compare staff doing similar jobs. Watch for repeated use of the same reason code, refunds without an original receipt, discounts immediately before cash payment and cash variances on the same rota combinations.

If you run several sites, compare locations cautiously. A late-night bar and a daytime café will not have the same refund or void profile. The useful comparison is against a venue’s own normal pattern, then against genuinely similar sites.

Every month: test the controls themselves

Review user accounts and permission groups. Remove leavers. Check whether supervisors are sharing codes. Confirm that only authorised people can export reports, alter tax settings, change prices or delete records. Choose a small sample of refunds and trace each one back to the original sale and approval.

Tie sales data to stock as well. If the bar sells 80 measures of a spirit but stock movement suggests 110 have gone, till permissions alone will not explain the gap. Check portion control, wastage, transfers, complimentary drinks and deliveries before assuming theft. The same applies in the kitchen: recipe quantities and stock counts are imperfect, but repeated unexplained differences deserve attention.

Keep the review owned. Put one manager’s name against the daily check and one senior person against the weekly review. “Management will review it” usually means nobody does.

Handling concerns fairly

When something does not add up

POS records are evidence, not a verdict

A suspicious pattern needs a calm investigation. Do not challenge somebody on the restaurant floor, announce a culprit in the management chat or jump straight from a till report to dismissal.

First, preserve the records. Export the relevant transaction history, receipts, approvals, clock-in data and cash-up notes. Keep any relevant CCTV in line with your retention policy. Record what the report showed, when it was noticed and who handled the review. Do not edit the source records to “tidy them up”.

Next, test other explanations. Was the till assigned correctly? Did a supervisor approve transactions under somebody else’s login? Was the card terminal offline? Did staff use a workaround during a system problem? Were refunds delayed because the manager was unavailable? Check evidence that may clear the employee as carefully as evidence that may implicate them.

Acas advises employers to plan workplace investigations, identify the evidence needed and keep the process full and fair. Where possible, different people should handle the investigation, the disciplinary decision and any appeal. If formal action follows, use your disciplinary policy, provide the allegation and evidence, let the employee respond, and give the right to be accompanied where it applies. Take employment advice for a serious case rather than improvising.

Monitoring must be open and proportionate

Transaction logs identify workers and can be personal data. The Information Commissioner’s Office says employers should be clear about the purpose, use the least intrusive method, identify a lawful basis, tell workers what monitoring takes place and keep only relevant information. That points towards transparent till auditing, not secret surveillance.

Explain during onboarding that logins are personal, sensitive actions are recorded and exception reports are reviewed. Put the rules in writing. Staff should know what data is collected, why it is collected, who can see it and how long it is kept. If you use CCTV or other monitoring, check the data-protection requirements that apply to your setup.

Do not casually dock wages

Restaurant operators should also be careful about recovering alleged shortages from pay. UK law restricts wage deductions, and the Employment Rights Act gives extra protection for cash shortages and stock deficiencies in retail employment. Whether a restaurant worker and a proposed deduction fall within the detailed rules depends on the facts and the contract. Do not treat a short drawer as automatic permission to deduct money. Check the written terms and take proper advice.

Prevention

Controls cannot carry the whole culture

Most prevention is ordinary, consistent management

A locked-down till will not fix poor supervision, confusing rules or a workplace where managers make exceptions for favourites. Software makes activity visible. Managers still have to set the standard.

Start with a plain policy. Define what counts as misuse: taking cash, giving away food or drink without authority, abusing discounts, adding loyalty credit to a personal account, changing tips, falsifying wastage and using another person’s login. Explain the approval process for genuine comps, staff meals and customer recovery. If the rules are fuzzy, enforcement will be inconsistent.

Train people on the reason for the controls. “Because we do not trust you” is a terrible message. “This protects the business and stops you being blamed for someone else’s transaction” is both true and easier to support. Managers must follow the same rules as everyone else. An owner who borrows a cashier’s login teaches the whole team that the audit trail does not matter.

Separate tasks where you can. The person approving a large refund should not be the only person reconciling it. The person counting the drawer should not silently write off their own unexplained variance. The employee receiving a high-value stock delivery should not be the sole person checking the invoice and adjusting the stock record. In a small venue, perfect separation may be impossible, but a second review can still remove easy opportunities.

Give people a safe route to speak up

Colleagues often spot behaviour before a report does: drinks leaving the bar without tickets, repeated “family discounts”, cash sales being cancelled, or one supervisor demanding everyone use the same PIN. Give staff a private route to raise a concern, and tell them how it will be handled.

The ACFE’s 2024 study found tips were the most common way occupational fraud cases in its sample were detected, and more than half of those tips came from employees. Again, that is a broad international fraud study, not a restaurant benchmark. The practical lesson still holds: people need a route to tell you what the numbers cannot.

Respond carefully. A concern is information to check, not permission to punish. Protect confidentiality as far as you reasonably can, avoid gossip and never reward managers for finding a culprit. Reward them for resolving discrepancies, following the process and tightening a weak control.

Good controls change the question from “Who do we trust?” to “Can we explain what happened?”

Practical checklist

Put it into practice

Make unusual transactions explain themselves

The strongest loss-prevention setup is not the one with the most restrictions. It is the one that leaves a clear answer to four questions: what changed, who changed it, why they changed it and who reviewed it.

• Give every employee a personal login; ban shared accounts.
• Remove access immediately when someone leaves or changes role.
• Limit refunds, deletions, price edits and large discounts by role.
• Require manager approval above sensible value thresholds.
• Record a clear reason for every void, refund and comp.
• Keep the original transaction linked to each refund.
• Record no-sale drawer openings and cash movements.
• Use blind cash counts where the system allows them.
• Reconcile cash, cards and online payments every day.
• Review rates and patterns, not just raw totals.
• Compare POS sales with stock use and recorded wastage.
• Keep a written, fair process for investigating concerns.

The goal is a calmer business, not a suspicious one

Most restaurant employees are trying to get through a demanding service and do a good job. Controls should reflect that. They should catch mistakes early, make training needs obvious and protect staff from vague blame. When deliberate abuse does happen, the same controls give management a reliable trail.

Start with the three basics: personal permissions, a readable void and refund log, and a cash-up report that is actually reviewed. Add stock checks, approval thresholds and a weekly trend review once the routine is working. There is no need to launch everything on a Monday morning and bury the team in new rules.

A restaurant will never remove every mistake or dishonest act. It can remove the easy hiding places. When every sensitive action has a name, a reason and a review, small losses are much less likely to become part of the nightly routine.