Restaurants are not normal businesses when it comes to payroll.
A corporate office pays mostly salaried employees, everyone arrives at similar times, leaves are uniform. A restaurant has a head chef on a fixed monthly salary, dishwashers on daily wages, waiters earning a base plus tips, delivery boys paid per shift, and agency housekeeping on a contractor’s invoice. All in the same month. All with different rules.
Most payroll problems in Indian restaurants don’t happen because owners are careless. They happen because the system being used, a paper register, a WhatsApp group, a rough Excel sheet cannot handle the complexity that restaurant payroll actually has. This guide is about what that complexity looks like and how to deal with it.
Why Restaurant Payroll Is Different
Let’s go through the actual problems, not the generic ones.
One team, five wage structures
A 40-cover restaurant might have: head chef on ₹45,000/month, three cooks on ₹18,000, four waiters at ₹12,000 plus service charge, two dishwashers at ₹450/day, and a cleaning agency billing ₹8,000/month. That’s five different structures with different PF applicability, different ESI thresholds, and different overtime logic. And they all need to run in the same payroll cycle.
Shifts that don’t fit a normal calendar
Lunch shift starts at 10 AM. Dinner shift starts at 4 PM. Kitchen team bridges both. Someone covers a colleague’s Saturday. The head waiter stays until 1 AM because a table of 14 came in at 10:30. Every one of these variations shift allowance, overtime, late-night premium affects what that person gets paid. Tracking it from a supervisor’s verbal report is where the errors enter.
Daily wage workers need daily records
A dishwasher on daily wages who worked 19 days in July doesn’t get a flat monthly salary. They get 19 ÷ 26 × monthly equivalent. Which means you need to know it was specifically 19 days not ‘around 20’ and which days those were, because if Sunday was one of them, Sunday might be double pay.
Minimum wage isn’t optional
Restaurant workers are covered by state minimum wage notifications often under a separate schedule for hotels and restaurants, not the general commercial rate. Delhi unskilled: ₹18,066/month as of April 2026. Karnataka Zone I: ₹15,489/month. Paying below this because someone agreed to it is still non-compliant. See where your state sits: Minimum Wage by State in India.
Service charge is a wage, not a gift
The 5–10% service charge that gets added to restaurant bills and distributed to staff? That’s part of wages. It’s taxable. Most restaurants treat it informally, which is fine in practice until there’s an audit. Pure cash tips from customers are harder to classify but service charge is not ambiguous.
PF and ESI What Applies to Whom
Get the thresholds wrong and you either owe back payments or you’re over-deducting. Both are avoidable.
PF (Provident Fund)
- Kicks in at: 20 or more employees. Once registered, you can’t deregister even if the number of employees drops.
- Rate: 12% from employee, 12% from employer (8.33% EPS capped at ₹1,250/mo, 3.67% EPF). Plus 0.5% admin charge.
- Base: Basic salary up to ₹15,000/month. Employees earning more can be enrolled on actual basic voluntarily.
- Restaurant reality: crossing 20 employees is a moment many restaurant owners don’t plan for. Suddenly the employer PF cost is 13–14% on top of every wage. Budget for this before your 20th hire, not after.
ESI (Employees’ State Insurance)
- Kicks in at: 10 or more employees (most states).
- Rate: 3.25% employer + 0.75% employee, on gross wages.
- Threshold: Only for employees earning ≤ ₹21,000/month gross.
- Restaurant reality: kitchen helpers, dishwashers, junior cooks, and delivery staff are almost universally under ₹21,000. ESI covers them for medical treatment, maternity, and sickness benefit benefits that restaurant workers actually use. Enrolling them properly matters beyond just compliance.
Who Gets What Payroll Rules by Staff Role
| Staff Role | Wage Type | PF Applicable? | ESI Applicable? | Key Payroll Point |
|---|---|---|---|---|
| Head Chef / Executive Chef | Monthly fixed | Yes (on capped ₹15K if basic > ₹15K) | Usually No (gross > ₹21K) | Verify 50% basic rule Labour Code 2025 |
| Sous Chef / Cook | Monthly or daily | Yes | Yes if gross ≤₹21K | LOP deductions common attendance must be linked to payroll |
| Waiter / Server | Monthly + tips | Yes if enrolled | Yes if gross ≤₹21K | Service charge is taxable wages handle it clearly |
| Delivery Executive | Daily or per-delivery | Classify carefully | Yes if gross ≤₹21K | GPS attendance per shift verify each working day |
| Dishwasher / Helper | Daily wages | Yes | Yes almost always | Accurate roster per day = accurate payroll |
| Housekeeping / Cleaning | Contract or daily | Contractor’s obligation | Contractor’s obligation | Get monthly PF/ESI proof from agency before paying invoice |
| Cashier / Billing | Monthly | Yes | Yes if gross ≤₹21K | Night shift allowance if late shifts apply |
| Manager / Supervisor | Monthly | Yes | Usually No (gross > ₹21K) | Shops Act OT applies job title doesn’t exempt them |
Shifts and Overtime Where the Money Gets Lost
Here’s a scenario that plays out in restaurants across India every month.
The supervisor tells HR: ‘Ranjan stayed late three times this month.’ HR asks: how many hours? The supervisor says: ‘Maybe two hours each time?’ HR enters six hours of OT. Payslip goes out. Ranjan thinks it was more like eight hours total across four nights. He doesn’t say anything but he’s keeping count.
That gap between what was worked and what was recorded is where trust erodes and disputes start. Under the Shops and Establishments Act that applies to most Indian restaurants, overtime is double the ordinary rate. That’s not a guideline. It’s the law. And it only calculates correctly if you know exact check-out times, per employee, per day.
What you actually need to track OT correctly:
- Exact check-out time, not an estimate. A check-out at 11:23 PM against a 10:00 PM shift end is 83 minutes of OT. ‘Left around 11’ is not a payroll record.
- Which shift they were on. OT is measured against the scheduled shift end, not against 8 hours. A B-shift employee finishing at 11 PM instead of 10 PM worked 1 hour OT not 3.
- The right rate. Most states: 2× ordinary rate. Verify your state’s Shops Act.
The OT calculation framework changed in January 2026 for factory workers. Full breakdown, including the Supreme Court ruling and how it applies by industry type, is in the Overtime Calculation Guide for India (2026). For restaurants, the Waggex shift management module flags overtime automatically when a check-out goes past the shift’s threshold no supervisor report needed, no estimate, just the timestamp.
Daily Wage Calculation The Formula and the Denominator Fight
The math is simple. The argument is usually about which number to put in the denominator.
Daily rate = Monthly equivalent ÷ Working days in the month
Monthly pay = Daily rate × Days actually worked
Example: dishwasher on ₹14,000/month equivalent. Worked 19 days in July.
Daily rate = ₹14,000 ÷ 26 = ₹538.46
Monthly pay = ₹538.46 × 19 = ₹10,230.77
The denominator 26 or 30 depends on whether your kitchen runs a 5-day or 6-day week, and what your company policy is. Either is defensible. The problem is inconsistency. If you used 26 in June and 30 in July for the same employee, the July payslip is going to look wrong to them even if your arithmetic is right. Pick one number and stick to it.
On weekly offs: a daily wage worker who works on their designated weekly off is entitled to double pay for that day or a comp-off within the month. Public holidays are generally paid the restaurant might be closed but the worker still gets paid. Track actual days worked per person, not just days present.
What This Actually Looks Like Andheri Cloud Kitchen
18 staff. Four virtual food brands out of one kitchen in Andheri, Mumbai. Shifts starting between 9 and 11 AM, running until midnight. Two delivery boys on payroll.
Before: the kitchen manager sent a WhatsApp summary at month end. ‘Santosh worked about 24 days, Priya took 3 days off, Ravi stayed late on busy nights.’ Owner calculated salaries from this. Two or three employees got underpaid most months. They didn’t complain. Two of them quit within six months.
After: app-based check-in and check-out at the kitchen. Delivery boys GPS-verified from their phones. LOP calculated automatically. OT flagged when someone’s check-out crossed shift threshold. Payslips generated for all 18 at month end without manual assembly.
The thing the owner noticed most: salary disputes stopped. When someone questioned their pay, there was an actual record to look at. The conversation changed from ‘I think you worked around…’ to ‘here’s every day, here’s every check-out time.’
Where Waggex Fits In
Restaurant payroll needs two things most generic HR tools don’t deliver: shift-aware attendance that connects directly to payroll, and the ability to handle fixed monthly salaries, daily wages, and contract staff in the same system.
On the attendance side: kitchen staff check in via web or app at the restaurant. Delivery executives use GPS-verified check-in from their phones verified server-side, so fake GPS apps don’t work. Both flow into the same dashboard. When someone’s check-out goes past their configured shift end, OT is flagged automatically. No supervisor relay, no estimate.
On the leave side: when a cook applies for leave and it’s approved in Leave Management, the attendance record updates and LOP calculates without anyone entering it manually before payroll day. Approved leave is already there.
Payroll itself PF, ESI, TDS, Professional Tax all calculate from verified attendance data. PF ECR file and ESI challan generate from the same run. Reminder Management sends alerts before the 7th (TDS) and 15th (PF and ESI) every month, so no deposit gets missed because the first of the month got busy with a big event.
Free plan for up to 10 employees full features, no card required. Paid plans: ₹699/month (10 emp) → ₹1,499/month (25 emp) → ₹2,499/month (50 emp) → ₹3,999/month (100 emp).
The Monthly Payroll Checklist
Before the 1st Verify These
| Statutory Deadlines Every Month
|
Five Mistakes Restaurants Make Every Month
- Tracking check-in but not check-out. Check-in confirms someone arrived. Check-out tells you how many hours they worked. Without it, overtime is invisible and daily wage calculation is a guess.
- Paying agency invoices without verifying PF/ESI compliance. If the agency’s cleaners aren’t enrolled and a labour inspector comes in, the liability lands on you as principal employer. Request proof of deposit monthly, before the invoice is cleared.
- Assuming minimum wage doesn’t apply because someone accepted a lower offer. It’s a statutory floor. The worker’s agreement doesn’t override it. If your dishwasher is on ₹7,000/month and your state minimum is ₹13,000, you’re non-compliant regardless of what they signed.
- Basic salary below 50% of CTC. Since November 2025, basic pay must be at least 50% of total remuneration under the Labour Code. Salary structures built to minimise PF liability by keeping basic low are now non-compliant. See the full breakdown: How to Create a Salary Structure in India.
Reconstructing payroll from memory. ‘Ranjan worked about 24 days’ is not in a payroll record. When a salary dispute comes up in a 20-person restaurant, one always needs a verified record, not an unverified estimation from weeks ago
To Wrap Up
Restaurant payroll goes wrong in very predictable ways. Overtime that was tracked from a supervisor’s memory. Daily wage workers whose count was ‘roughly’ 22 days. Agency staff whose PF nobody checked. These aren’t careless mistakes, they’re what happens when the system being used can’t actually capture what’s happening in a kitchen that runs 14 hours a day.
The fix is a connected system: attendance captured accurately at shift level, leaving no gap between what happened and what goes into payroll. If your current process involves assembling salary data from WhatsApp, a physical register, and someone’s recollection the night before payday, that’s where the compliance gap is living.