OPERATOR SOP · 2026 13 min read Updated July 2026

Restaurant Daily Close SOP (2026 India) — The 15-Minute Cash + Card + UPI Reconciliation

Most Indian restaurants close their daily books wrong. Either they don't close at all — variance compounds silently for weeks — or they do a 45-minute paper-based reconciliation that misses more than it catches. In 2026 with cash, three card acquirers, four UPI providers and two aggregators all reporting differently, the right daily close takes 15 minutes and follows a strict 5-step SOP. This is the exact playbook, including the printable tracker template you should be filling in every night before you lock the shutter.

In this SOP

  1. Why daily close matters — the compounding variance problem
  2. Step 1 — Cash drawer close (3 minutes)
  3. Step 2 — Card terminal reconciliation (3 minutes)
  4. Step 3 — UPI reconciliation (3 minutes)
  5. Step 4 — Swiggy + Zomato reconciliation (3 minutes)
  6. Step 5 — KOT vs sales audit (3 minutes)
  7. The 5-column daily close tracker template
  8. 3 common mistakes and how to avoid them
  9. FAQ

Why daily close matters — the compounding variance problem

Skip a day and the variance carries. Skip a week and you cannot tell whether Monday's ₹1,800 short was a cashier error, a comp that wasn't recorded, or someone pocketing tip money. Skip a month and your accountant will hit you with a "cash on hand doesn't tie to bank" note before GST filing. The daily close is not paperwork — it is the operational discipline that keeps a restaurant honest.

The three data streams that must reconcile: (1) what your POS says was sold, (2) what money actually landed in your accounts (cash + bank), and (3) what your kitchen produced (KOTs). Any mismatch between any two of these three is a real problem that becomes exponentially harder to fix the longer you wait.

What the 15-minute close catches that a monthly close misses

Step 1 — Cash drawer close (3 minutes)

The oldest reconciliation and the one most restaurants still get wrong.

The process

  1. Print the cash Z-report from the POS. This gives you the "expected" cash total — sum of all bills paid in cash minus refunds.
  2. Count physical cash in the drawer. Not by memory, not by "looks about right" — count by denomination on the tally sheet.
  3. Subtract opening float. Every drawer starts the day with a fixed float (typically ₹1,500-3,000 in small notes and coins). Remove that from the count.
  4. Note the variance. Physical count minus expected = variance. Positive means over, negative means short.
  5. Apply the sign-off rule.

The variance thresholds that matter

VarianceActionSign-off
0 to ±₹100Normal — record and move onCashier initials the sheet
±₹100 to ±₹200Note reason (e.g., rider tip, minor round-off)Cashier + shift lead initials
±₹200 to ±₹500Manager sign-off requiredManager verifies count
Above ±₹500Recount + KOT audit before lockingManager sign-off + written explanation

The most-common ₹200-500 variance pattern: a bill was paid partially in cash and partially in UPI (customer said "here's ₹300 cash, I'll UPI the rest"), and the cashier only recorded the cash. The UPI transaction sits unlogged in the app. Cross-check UPI in Step 3.

Cash disposal at close

  1. Move everything above the opening float for tomorrow to the safe (or make a night deposit envelope).
  2. Never leave more than the opening float in an unsecured drawer overnight.
  3. Bank the safe balance every 2-3 days — cash sitting is theft risk plus you lose the working capital.

Step 2 — Card terminal reconciliation (3 minutes)

Cards are the easiest step if you follow the SOP, and the hardest if you don't.

The process

  1. Close the batch on every card terminal. Pine Labs, Mswipe, Razorpay POS — all have a "Settle" or "End of Day" button. Press it. Print the batch total slip.
  2. Compare to POS card total. Your POS reports "₹X received via card." Sum of terminal batches should equal that number.
  3. Investigate any mismatch. Common causes: a bill was recorded as card but the customer actually paid UPI; a batch failed to close and shows zero; a refund was processed on the terminal but not recorded in POS.

The T+2 settlement watch

Standard India card settlement is T+2 for most acquirers. That means Monday's card charges land in your bank on Wednesday. Two operational rules follow:

The dispute you don't want to miss: if a card charge slip is printed but the batch settlement is short, the customer probably raised a chargeback. Card chargeback response deadlines are typically 15 days. Miss it and you lose the money automatically. Weekly reconciliation catches this while you still have time.

Step 3 — UPI reconciliation (3 minutes)

UPI is where the 2026 daily close gets messy. Most restaurants have 3-4 UPI apps active — PhonePe QR, GPay QR, Paytm, BharatPe soundbox — each with its own dashboard, each settling on its own schedule.

The process

  1. Open each UPI merchant app. Note today's total for each provider.
  2. Compare to POS UPI total. Your POS records "UPI ₹X" per bill. Sum across all bills = expected UPI total across all providers combined.
  3. Reconcile provider-by-provider. If your POS says ₹18,500 UPI total and providers say ₹11,200 PhonePe + ₹4,800 GPay + ₹2,500 BharatPe = ₹18,500, you're clean. Off by ₹500 or more — investigate.

The T+1 settlement watch and the ₹0.05 MDR reality

UPI settles T+1 for most restaurants — money you collect Monday hits your current account Tuesday. MDR (merchant discount rate) on person-to-merchant UPI is effectively 0% for transactions under ₹2,000 (which is the vast majority of restaurant bills). Above ₹2,000, MDR is a nominal 0.5-1% on RuPay and interchange debit cards, but is typically absorbed by the merchant provider on standard PhonePe/GPay QR flows. In practice you lose about ₹0.05-₹0.10 per ₹500 UPI order — small enough to ignore for daily reconciliation but track quarterly.

The UPI cashback trap

Customer opens PhonePe, pays ₹500 to your QR, and PhonePe shows them "₹5 cashback earned!" Your merchant app receives ₹495, not ₹500. This is not a fee — it is PhonePe applying a promo split to the payment. If you record ₹500 on the bill but only ₹495 landed, that ₹5 is a variance. On 100 UPI transactions/day this becomes ₹500 daily "loss" that is really just a data discrepancy.

The fix: instruct staff to record the amount your merchant app confirms, not the amount the customer said they paid. Or accept the variance and account for it as "cashback pass-through" at month-end.

Step 4 — Swiggy + Zomato reconciliation (3 minutes)

Aggregator orders are recorded live in your POS/Ordering Suite. Your job at close is to make sure the count matches what the platforms show.

The process

  1. Open Swiggy Partner and Zomato Partner apps. Note today's order count and gross order value.
  2. Compare to POS aggregator report. Your POS/Ordering Suite has a "Channel Revenue" or "Order Source" report. Sum by platform.
  3. Log any missing orders. A Swiggy order that shows in Swiggy Partner but not in your POS = an integration failure. Log it, file with Swiggy support next morning.

The T+7 settlement schedule

Both Swiggy and Zomato settle weekly (T+7). Your Monday-Sunday orders get paid the following week, net of:

Weekly reconciliation SOP: every Monday morning, download last week's settlement statement from both partner apps. Match line-by-line against your POS-recorded aggregator orders. Any missing order or wrong commission = raise a dispute within the 7-day window. Missed disputes = money written off.

The Cash on Delivery trap

Some Swiggy and Zomato orders are still fulfilled with Cash on Delivery. The rider collects cash at the door. That cash goes into your drawer. But the platform records the order as pre-paid on their app. If your cashier doesn't record COD orders in the "cash" tally, your cash drawer will run a ₹500-2,000 daily surplus you cannot explain. Fix: add a COD tick-box on your bill entry or ask riders to submit cash to cashier with the order slip stapled.

Step 5 — KOT vs sales audit (3 minutes)

The forensic step. Every KOT sent to the kitchen should have a matching bill. If it doesn't, something happened that wasn't accounted for.

The process

  1. Print the KOT summary from your POS. Should show KOTs printed today: count and total value.
  2. Compare to bills raised. Bills-raised total value should equal KOT total value minus voids.
  3. Investigate any variance above ₹300. Common causes:
    • KOT printed for a customer who walked out (dine-and-dash) — record as loss
    • KOT printed but bill was voided without record
    • KOT modified (item added/removed) after the initial print, and the second print didn't update the count
    • Staff meal recorded as a KOT — needs a separate "internal" tag so it doesn't count as unbilled sale
Why this step catches theft: a cashier who wants to skim will not just take cash from the drawer (that's caught in Step 1). They'll void a bill after the customer paid in cash and pocket the cash. The bill is voided so it doesn't show up in expected cash. The KOT was already sent to the kitchen, so a dish was made. KOT count vs bills raised is the only place this shows up.

The 5-column daily close tracker template

Print or fill this in a shared sheet. Same 5 columns every day. After 30 days, patterns become obvious.

DAILY CLOSE — [Restaurant name] — Date: __/__/2026 Shift: [ ] Lunch [ ] Dinner [ ] Both Manager on duty: ______________ +---------------+----------+----------+----------+-----------+ | Channel | Expected | Actual | Variance | Notes | +---------------+----------+----------+----------+-----------+ | Cash | ₹ | ₹ | ₹ | | | Card | ₹ | ₹ | ₹ | | | UPI | ₹ | ₹ | ₹ | | | Swiggy | ₹ | ₹ | ₹ | | | Zomato | ₹ | ₹ | ₹ | | +---------------+----------+----------+----------+-----------+ | TOTAL | ₹ | ₹ | ₹ | | +---------------+----------+----------+----------+-----------+ KOTs printed today: _____ Bills raised: _____ Voids: _____ Unmatched KOTs (needs explanation): _____ Cash moved to safe: ₹______ Float retained: ₹______ Cashier signature: ________________ Manager signature: ________________

Any variance line >₹200 gets a note in the Notes column. Any variance line >₹500 gets a manager signature. The tracker becomes the audit trail — 90 days of these tell you exactly which channel, which shift, and which staff member is running clean vs sloppy.

3 common mistakes and how to avoid them

Mistake 1 — Leaving cash overnight

The single most common mistake. Owner is tired, cashier is tired, everyone locks up and goes home with ₹15,000-40,000 sitting in the drawer. When there's a break-in, when there's an employee theft, when there's a fire — that money is gone. Fix: safe on premises, or better, a night-deposit bank arrangement. Cash-in-drawer overnight should be capped at ₹2,000 (float only).

Mistake 2 — Ignoring UPI cashback discrepancies

The ₹5 here, ₹8 there. Individually trivial. On 3,000 UPI transactions/month that's ₹15,000-24,000 in unexplained "loss" — which is not really loss but looks like loss and hides the actual problems. Fix: either record the merchant-app-confirmed amount (not the customer's paid amount) on every bill, or accept the pattern and pre-book a "cashback pass-through" monthly reserve.

Mistake 3 — Forgetting to record Swiggy Cash on Delivery

Rider brings ₹500 cash for a COD order. Goes straight into the drawer. Cashier does not record it as an aggregator-sourced cash payment. At close, drawer is ₹500 over. Investigate why → 20 minutes lost → happens again tomorrow. Fix: a dedicated "aggregator COD" line on the tracker, or a separate cash pouch that COD riders drop into (opened at close, counted, matched to Swiggy/Zomato COD order lists).

Get the Z-report that auto-flags variance above ₹200

Online eMenu Desktop POS end-of-shift Z-report groups cash + card + UPI + aggregator + KOT audit in one screen. ₹4,999/year yearly license, no monthly fee.

Take the product tour

Frequently Asked Questions

How long should a restaurant daily close take?

15 minutes if you have a POS with settlement reports and a standard SOP. If it takes 45+ minutes, the process is broken.

What variance in cash drawer is acceptable?

Under ₹100 normal. ₹100-200 needs a note. Above ₹200 needs manager sign-off. Above ₹500 needs a written explanation and a KOT audit.

When does UPI settlement hit my bank?

T+1 for most providers. MDR is effectively 0% under ₹2,000. Above ₹2,000 is 0.5-1% but usually absorbed.

When do card settlements arrive?

T+2 standard for Pine Labs, Mswipe, Razorpay. T+1 for premium plans. Reconcile weekly against bank credits, not just daily against terminal reports.

When do Swiggy and Zomato pay?

T+7 weekly settlement, net of commission + 1% TDS + restaurant-funded discounts. Dispute deadline is typically 7 days.

What is a KOT-vs-sales audit?

Every KOT should produce a bill. Any KOT without a bill is either voided, unbilled, or a walkout. Catches most fraud.

Top 3 mistakes?

Leaving cash overnight. Ignoring UPI cashback discrepancies. Forgetting to record Swiggy COD orders as cash-in-drawer.

Does Online eMenu Desktop POS support daily close?

Yes — Z-report groups all channels + KOT audit + variance flag on one screen at ₹4,999/year.

O

Online eMenu Editorial Team

INWIZARDS SOFTWARE TECHNOLOGIES L.L.C · Dubai · Engineering in Indore · Published 2026-07-22