Restaurant Billing Fraud: Discount Control That Stops Leakage

This guide is for restaurant owners in India who are not at the cash counter all day, or who run more than one branch, and suspect that sales and cash do not fully match. By the end you will know the five places where money leaks, the sign each one leaves in the reports, and the specific control that closes it. Most of this is about ordinary carelessness and unclear rules, not crime, and the same controls fix both.

Where restaurant billing leaks: the five usual points

1. Unbilled tables

Food is served and never entered in the system. The captain passes a verbal order to the kitchen, the guest pays cash, and the sale does not exist. It also happens innocently: an extra roti or a soft drink added at the table and forgotten at billing.

2. Items cancelled after serving

The order is entered and cooked. Just before the bill, an item is cancelled. The guest pays the full amount in cash from the first bill, and the system records the lower one.

3. Unauthorised discounts

A discount is applied without authority: to friends, to regulars in exchange for a tip, or to a bill after the guest has paid in full, with the difference taken from the drawer.

4. Bill reprint and edit

A bill is printed and paid, then changed and settled at a lower amount. Or an old bill is reprinted and handed to a new table with the same order, a risk in places with fixed thali prices, so the second sale is never recorded.

5. Cash short at close

The drawer holds less than the system says it should. Sometimes it is wrong change. Sometimes a UPI payment was entered as cash. Sometimes it is not a mistake.

A restaurant with daily sales of ₹60,000 that loses 2% this way loses ₹1,200 a day, about ₹36,000 a month. That is the figure to keep in mind when weighing the effort of the controls below.

Leak, sign in the reports, and control: the full table

Every leak leaves a trace if your restaurant POS software records the right things. This table is the core of the guide.

Discount control in a restaurant: role limits and manager PIN

Discounts are the hardest leak to see, because a discount is a legitimate action. The question is never whether discounts exist. It is who gave them, how much, and why.

Set limits by role

Decide what each role may do, and write it down before you configure anything:

• Captain: no discount. Captains take orders, they do not price them.
• Cashier: a small limit, for example up to 5%, for rounding and minor complaints.
• Manager: a higher limit, for example up to 15%, for service failures and regular guests.
• Owner: no limit.

Your numbers will differ. The principle is that the limit matches the authority of the person, and that the software enforces it, not a notice on the wall.

Manager PIN above the limit

When a bill needs more than the cashier's limit, the software should ask for a manager PIN. The manager walks over, hears the reason, and approves. That thirty-second walk is the control: it makes a larger discount a decision by two people.

Protect the PIN. Change it when a manager leaves, never write it near the counter, and do not let the manager enter it from across the room by telling the cashier the digits.

A reason on every discount

Each discount should carry a reason: staff meal, complaint about a dish, owner's guest, festival offer. Reasons turn a list of numbers into something you can question. Twelve "complaint" discounts in a week from one cashier is either a kitchen problem or a cashier problem, and you want to know which.

Service charge is a separate matter

Service charge is voluntary for the guest, so a cashier must be able to remove it from a bill on request. Do not treat that as a discount in your review, but do look at how often it is removed and by whom.

Cancelled items, void reasons and the cancelled-item report

Cancellations are normal. Guests change their minds and captains tap the wrong item. The control is not to block them but to make each one visible in two places.

The first place is the kitchen. A cancelled item should print a CANCELLED ticket at the counter that received the original. If the cook has not started, the dish is stopped. If the dish has already gone out, the cook will say so, loudly. A cancellation that the kitchen never hears about is the one to worry about. Our guide to KOT printing and kitchen order tickets explains these tickets.

The second place is the report. Review the cancelled and void report weekly, and read it like this:

1. Sort by user. Who cancels most, relative to the bills they handle?
2. Look at the gap between order time and cancel time. Two minutes is a correction. Forty minutes is a question.
3. Look at the items. High-value dishes and drinks cancelled late deserve a second look.
4. Read the reasons. "Guest changed mind" forty minutes after a dosa was ordered does not hold up.
5. Ask about three or four entries a week, calmly, in front of the manager. The asking matters more than the answers.

Audit log, bill settlement and the day-end report

Audit log

An audit log records sensitive actions with the user and time: discounts, voids, price changes and settings changes. Its value is partly detection and mostly deterrence. Staff who know that a price change at 10:45 PM carries their name do not make one casually.

Price and settings changes deserve attention. A menu price lowered for an hour and raised again, or a discount limit quietly increased, will not show in a sales report. It will show in the log.

Two-step billing

The bill-edit leak lives in the gap between printing a bill and recording payment. Close it with two rules. The table stays occupied after the bill is printed, so every unpaid bill is visible on the floor screen. And the final invoice number is assigned only when the bill is settled, in sequence, so there are no numbered invoices floating around unpaid. The post on table management covers the table side of this.

Day-end report

At close, print the day-end report and compare it with reality:

• Cash in the report against cash counted in the drawer, ideally counted by someone other than the cashier.
• UPI and card totals against the bank and the card machine.
• Total discounts and total cancellations for the day against a normal day.
• No table left in running or billed status.

Sign the printed report and file it. The full routine is in our post on the day-end report and cash closing.

How Dhandhaan handles this

Dhandhaan is the restaurant POS software built by JK Tech Hub in Rajkot. These are the controls it provides:

• Roles: owner or admin, manager, cashier and captain. Captains can be limited to certain floors and log in with their own username and PIN.
• Discounts: percentage or fixed, with a reason. Permission is set per role with a maximum limit, and above the limit a manager PIN is needed.
• Service charge: an on or off setting per branch, and the cashier can remove it from a bill.
• Kitchen tickets: cancelled items print a CANCELLED ticket at the kitchen printer.
• Two-step billing: "Print Bill" gives a provisional bill and the table stays occupied. "Settle" takes payment, assigns the final invoice number and frees the table. Invoice numbers are sequential per branch.
• Audit log: every discount, void, price change and settings change is recorded.
• Reports: discount report, cancelled and void report, captain-wise and cashier-wise reports, payment mode split, and a day-end report printed at close, in Excel and PDF.
• Owner access: a web admin panel that works in a phone browser, with combined and branch-wise reports for multi-branch accounts.

What it does not do: Dhandhaan has no inventory, stock or recipe management at present, so it cannot compare raw material used with dishes billed. That check, if you want it, stays manual. The price is ₹12,999 a year for a single branch and ₹23,999 a year for multi-branch, with no charge per bill.

What we learned building these controls for a multi-branch restaurant in Gujarat

JK Tech Hub built Dhandhaan for a multi-branch South Indian and fast food restaurant business in Gujarat that was moving off a hosted POS. With several branches, the owner cannot stand at every counter, so the controls had to work without the owner present.

Two design decisions came out of that. The table stays occupied until the bill is settled, even though freeing it at print would be one tap faster. And the audit log covers settings and price changes as well as discounts and voids, because a changed limit is as important as a discount given under it.

We also kept the controls out of the way of routine work. The PIN prompt appears only above the role's limit, so a small discount within a cashier's limit does not need the manager and does not hold up a counter with a queue.

What this means for your business

Start with three actions this week. Give every person their own login and stop sharing passwords. Set discount limits by role with a manager PIN above them. Print and sign the day-end report every night.

Then add the weekly half hour on the discount and cancelled-item reports. Tell the team that you read them. Most leakage stops at that point, without a single confrontation, because the opportunity was the cause.

Related reading and next step

• Dhandhaan restaurant POS software: features and price
• Restaurant day-end report and cash closing
• Restaurant table management: merge and split tables
• KOT printing and kitchen order ticket setup
• Restaurant POS software in Rajkot

To see role limits, the manager PIN and the audit log on a live system, ask for a demo or a quote through the contact page or on WhatsApp at +91 7265004040.