Reconciliation for Restaurants and F&B Operators
The four reconciliation rails restaurants actually run on — aggregator settlement (Zomato, Swiggy, Magicpin, Dunzo), POS payment gateway, daily cash deposit, and GST split between dine-in and catering. Plus QSR multi-outlet rollup and cloud-kitchen multi-brand-one-GSTIN structures.
A restaurant in India operates on four reconciliation rails simultaneously: aggregator settlements (Zomato, Swiggy, Magicpin, Dunzo) that arrive net of 25–35% commission plus TDS Section 194O plus TCS Section 52; POS payment gateway flows (Pine Labs, MSwipe, Razorpay, PayU) that settle T+1 to T+3 net of MDR; daily cash deposits from in-store collection that need to match POS Z-reports against the bank credit; and a GST stream that splits 5% no-ITC for dine-in and standalone outlets versus 18% with-ITC for outdoor catering, with hotel-restaurant rates tied to room tariff. The cumulative effect on a typical mid-size restaurant chain is dozens of distinct reconciliation surfaces — and a margin that quietly leaks until each one is closed.
The articles in this cluster cover each rail in operational detail. They are written for restaurant CFOs, finance controllers, and chain operators who own the cash-to-revenue close. The focus is on the actual mechanics — Zomato weekly settlement decomposition, Swiggy Instamart vs Food rules, cloud kitchen brand-level P&L extracted from a single GSTIN, daily Z-report matching against bank deposits, and the variance taxonomy that classifies every unmatched item before the month-end close.
These pieces are deliberately specific. Zomato reconciliation is not the same as Swiggy. Standalone-restaurant GST is not the same as outdoor-catering GST. QSR multi-outlet rollup is a different problem from a single owner-managed restaurant. The cluster names the rail, the file format that rail produces, the leakage points, and the reconciliation control that closes the gap.
Restaurant Aggregator Reconciliation: Build vs Buy vs Vendor Evaluation Framework
A 100-outlet restaurant chain processing ₹15 crore monthly aggregator GMV has three structural choices for reconciliation: build in-house with Excel, SQL, and a data team; buy a per-aggregator reconciliation tool; or deploy reconciliation infrastructure with restaurant industry preset as one vertical. The decision is a TCO and capability question — not a pricing question — and the right answer depends on aggregator count, GSTIN spread, audit posture, and ERP integration depth.
Swiggy Commission Reconciliation for Multi-Outlet QSR Chains: A Buyer's Evaluation
Swiggy's settlement is denser than any single payment gateway: commission tiers, SLA penalty deductions, ad-spend deductions, restaurant-borne discount components, dispute window, Food vs Instamart channel split, Section 393 TDS, and Section 52 CGST TCS. For a 30 to 100 outlet QSR chain, the choice between manual Excel, an aggregator-side reconciliation tool, and reconciliation infrastructure is a question of where the four-rail join — aggregator, POS, cash, GST — actually closes.
Zomato Reconciliation: Manual Excel vs Aggregator Tools vs Reconciliation Infrastructure at 50+ Outlets
A finance team running 50+ outlets on Zomato has three structural choices for weekly settlement reconciliation: a manual Excel workflow that scales linearly with order volume, a per-aggregator reconciliation tool that owns Zomato but stops at the platform boundary, or a config-driven reconciliation infrastructure that handles aggregator, POS, bank, GST, and TDS as one stack. The decision is not about features — it is about where the workflow breaks first.
GST Section 9(5): When the Aggregator Pays GST and the Restaurant Does Not
From 1 January 2022, Section 9(5) of the CGST Act made e-commerce operators like Zomato and Swiggy liable to pay GST on restaurant services supplied through their platforms instead of the restaurant. Standalone restaurants and cloud kitchens fall under it; hotel-restaurants tied to room tariff above ₹7,500 do not. The reconciliation implications run through ITC, GSTR-3B reporting, and cost-of-goods recovery.
Outdoor Catering Reconciliation in India: GST 18% with ITC, Advance Receipts, and TDS Under Section 393
Outdoor catering reconciliation in India is structurally different from a dine-in restaurant close. The supply is taxed at 18% GST with full ITC, settlements are B2B with credit terms, advance receipts trigger time-of-supply under Section 13, and customers deduct TDS under Section 393(1)(a) payment code 1002 of the Income Tax Act 2025. The match is PO to event manifest to final invoice to bank receipt — not POS to bank credit.
Restaurant Franchise Royalty Reconciliation in India: Brand Royalty, NMF, Tech Fee, and TDS Under Section 393
A Domino's, Subway, KFC, Wow! Momo, or Chai Point franchisee in India runs four parallel reconciliations against the franchisor every month — brand royalty on POS revenue, contributions to the national marketing fund, technology fee on transactions, and supply-chain margin on commissary purchases. Each is a separate inward supply with its own GST line, and TDS on royalty now runs under Section 393 with payment code 1003 in the new Income Tax Act.
Restaurant GSTR-2B Commission ITC Reconciliation: Claiming 18% on Aggregator Commission
Zomato, Swiggy, and Magicpin charge 18% GST on commission and issue tax invoices that flow into the restaurant's GSTR-2B as inward supplies. The credit is claimable — but only when the aggregator's GSTR-1 has been filed, the GSTIN on the invoice is correct, and the entry actually appears in 2B. Three preconditions, three failure modes, and a recurring source of leaked ITC.
Restaurant Liquor and Bar Sales Reconciliation in India: State Excise vs GST, Permits, and Daily Stock Registers
Restaurant liquor bar sales reconciliation in India is structurally different from food revenue. Liquor is outside GST — it lives in the state-excise and VAT regime that varies by state. Karnataka, Maharashtra, Delhi, Tamil Nadu, and Telangana each run different licence classes, permit cycles, and stock-and-sales registers. The same bill mixes GST-taxable bar food with excise-only liquor, and reconciliation must split them at the line-item level.
Restaurant Service Charge and Tip Pool Reconciliation in India: CCPA Rules, GST, and Salary TDS on Tips
Since the July 2022 CCPA guidelines made service charge optional, every Indian restaurant has had to rebuild its end-of-shift close. Customer opt-out triggers a POS adjustment, the tip pool collected at the till has to be distributed to staff under a documented policy, and the GST and TDS treatment of both flows is non-trivial. This article walks through the reconciliation that ties POS to bank to payroll register cleanly.
TCS Section 52 on Restaurant Aggregator Settlements: Reconciling GSTR-8 to the GST Cash Ledger
Section 52 of the CGST Act requires e-commerce aggregators to collect 1% TCS on the net value of taxable supplies made by restaurants through their platform. The collected amount flows into the restaurant's electronic cash ledger via the aggregator's monthly GSTR-8, where it is claimed and cleared against output GST. This is GST law, completely unchanged by the Income Tax Act 2025 — and it must not be confused with income-tax TCS under Section 206C.
Section 393 TDS on Restaurant Aggregator Settlements: Reconciling Payment Code 1010
From April 1, 2026, TDS on e-commerce restaurant settlements moves from legacy Section 194O to Section 393 of the Income Tax Act 2025 with payment code 1010. Restaurant finance teams must reconcile aggregator deductions against the new Form 168, handle cross-era credits trickling in under old codes, and resolve the gross-vs-net base question that drives most reconciliation breaks.
Cloud Kitchen Multi-Brand Reconciliation: One GSTIN, Many Brand Identities
A cloud kitchen operating six virtual brands from a single commissary registers under one GSTIN but lists each brand separately on Zomato, Swiggy, and Magicpin. Reconciling at the GSTIN level satisfies tax filing but loses brand-level profitability — the metric that drives menu engineering, marketing spend, and brand wind-down decisions.
Magicpin and Dunzo Restaurant Settlement Reconciliation: Vouchers, Cashback, and TCS
Zomato and Swiggy account for the bulk of aggregator revenue at most Indian restaurants, but secondary aggregators — Magicpin's voucher economy, Dunzo's hyperlocal delivery where it still operates, and a long tail of regional players — bring their own settlement formats, their own promo accounting, and a TCS treatment that is not always identical to the primary platforms.
QSR Chain Multi-Outlet Reconciliation: Rollup, Commissary, and Per-Outlet P&L
A 60-outlet QSR chain runs across four states, three banks, two GSTINs, one central kitchen, and a mix of company-owned and franchised stores. Reconciling that estate to a clean per-outlet P&L is not a single problem — it is six problems stacked. The chain finance team has to solve all six every month or watch outlet-level performance drift invisibly.
Restaurant Daily Cash Deposit Reconciliation: POS Z-Report to Bank Credit
A restaurant takes cash across breakfast, lunch, and dinner shifts. The POS Z-report says one number, the cash room counts another, the pickup agent collects a third, and the bank credit lands on a fourth. Reconciling those four data points is the core of cash-deposit control — and the place where shrinkage hides.
Restaurant GST Reconciliation: When 5% Applies, When 18% Applies, and Why ITC Differs
A restaurant inside a hotel with rooms at ₹6,000 charges 5% GST without ITC. The same restaurant in a hotel with rooms at ₹8,000 charges 18% with full ITC. The kitchen, the menu, and the chef are identical — only the room tariff threshold changes the GST regime, and reconciling the two streams is where most multi-property F&B operators leak credit.
Restaurant POS Payment Gateway Reconciliation: MDR, Settlement Cycle, and ITC
Restaurants accept eight payment instruments through three or four POS terminals, and each instrument carries a different MDR, a different settlement cycle, and a different refund reversal pattern. The bank credit at the end of the week is a single net figure — turning that figure back into instrument-level revenue with GST on MDR claimable as ITC is the reconciliation problem.
Restaurant Reconciliation in India: Aggregator, POS, Cash, and GST Split
Restaurant reconciliation in India sits across four payment rails — aggregator payouts, POS gateway settlements, UPI, and physical cash — each with different commission, TDS, TCS, and GST treatments. This guide covers how the daily close works, where it breaks, and what controls a finance team needs.
Swiggy Restaurant Settlement Reconciliation: Food, Instamart, and SLA Penalties
Swiggy pays restaurants weekly, but the deduction stack differs from Zomato in three ways: SLA penalties for late or rejected orders, restaurant-borne discount components on promotional offers, and a separate fee schedule for Instamart versus Food. Reconciling each layer back to order-level revenue is the core finance task.
Zomato Restaurant Settlement Reconciliation: How Weekly Payouts Match Orders
Zomato pays out weekly, but the bank credit a restaurant receives is the residual after commission, TDS 194O, TCS Section 52, GST on commission, ad spend, and refund reversals. Reconciling that residual back to order-level revenue is the core task for finance teams running aggregator-led restaurants.
See how TransactIG handles multi-rail restaurant reconciliation
TransactIG ingests aggregator settlement files, POS gateway feeds, and bank statements in their native formats, reconciles each against your POS or ERP order register at order level, and surfaces the variance codes (commission, TDS, TCS, refund reversal, cash short/over) that drive margin leakage.