If you run a restaurant on Swiggy or Zomato and have ever compared your dashboard sales total against the amount that actually landed in your bank, the gap probably felt wrong. It is not a glitch. Six separate deduction layers sit between your order value and your bank credit: base commission, GST on that commission, a platform fee, payment gateway charges, TDS, and promotional deductions. The dashboard shows gross sales. Your bank receives the net after all six cuts.
The structural gap runs 25-35% of your gross order value. On a Rs 500 order, you receive roughly Rs 325-375 depending on your commission tier, city, and contract terms. That much is expected. But when a wrong commission rate gets applied, or a discount you did not consent to is auto-deducted, or your POS says delivered while the platform says cancelled, the deposit drops further below what even the net calculation should have been.
This piece breaks down where every rupee goes, why timing makes the gap look larger than it is, and what to do when the numbers genuinely do not add up.
Key Takeaways
- Six deductions (commission, GST, platform fee, gateway, TDS, promotions) separate your order value from your bank credit
- The dashboard shows gross sales; your bank receives the net after all cuts
- Errors in commission tiers, auto-applied discounts, or order status records widen the gap beyond the expected deduction
- Weekly reconciliation catches these leaks before the dispute window closes
What Gets Deducted Before Money Reaches Your Account?
Every online order passes through multiple deduction stages on the platform’s backend before the remaining amount is queued for transfer to your bank.
| Deduction layer | What it is | Typical range on a Rs 500 order |
|---|---|---|
| Base commission | Platform’s cut for listing, delivery network, and customer acquisition | Rs 80-150 (16-30%) |
| GST on commission | 18% GST charged on the commission amount | Rs 14-27 |
| Platform fee | Fixed per-order charge applied by the aggregator | Rs 5-20 |
| Payment gateway | Processing fee for digital payments | Rs 10 (approx 2%) |
| TDS | Tax deducted at source on annual payouts above Rs 5 lakh | Varies by threshold |
| Promotional deductions | Sponsored listing or marketing programme costs, if opted in | Rs 0-30 |
The base commission alone accounts for the largest chunk. Both Swiggy and Zomato charge between 16% and 30% depending on the city, the restaurant’s order volume, and the specific contract tier. Layer GST, gateway fees, and platform charges on top, and the effective deduction reaches 25-35% of the order value.
For example, consider a Mughlai restaurant in Lajpat Nagar on a 22% commission contract. On a Rs 500 biryani order, the platform deducts Rs 110 as commission, Rs 19.80 as GST on that commission, Rs 10 as gateway fee, and Rs 15 as platform fee. The restaurant receives roughly Rs 345 from the original Rs 500. That is a 31% effective deduction, nine percentage points higher than the 22% headline commission rate the owner signed up for.
Why Does the Dashboard Number Never Match the Bank Statement?
Three reasons, and only one of them is an error.
Reason 1: Gross vs net. The dashboard on your Swiggy or Zomato partner app shows gross order value, the total of what customers paid. Your bank receives the net after all deductions listed above. This gap is permanent and intentional. It is not an error.
But if you have never calculated your effective deduction rate, the difference between the dashboard figure and the bank credit feels alarming the first time you compare them.
Reason 2: Settlement timing. Payouts do not land in your account the same day as the order. Most restaurants receive weekly settlements, though Zomato introduced a daily payout option in January 2024 for partner restaurants receiving up to 100 orders per month. If your settlement cycle runs Monday to Sunday with a 2-3 day processing buffer, orders from Saturday might not reflect in your bank until Wednesday or Thursday of the following week. During that window, the dashboard shows sales you have earned but not yet received.
Reason 3: Actual settlement errors. This is where the real problem sits. A wrong commission tier applied to a batch of orders. A promotional discount the platform auto-applied to your listing without your explicit approval. An order your POS recorded as delivered but the aggregator’s system marked as cancelled. These are not structural deductions. These are errors that push your deposit below what the net calculation should have been.
The National Consumer Helpline recorded over 3,631 grievances against Swiggy and 2,828 against Zomato over a 12-month period, with deficiency in services topping the complaint list for both platforms, according to India.com. Not all of these relate to restaurant payouts, but the volume indicates how common platform-side issues are.
How Big Is the Effective Deduction at Different Commission Tiers?
The effective deduction rate (what actually gets cut from your order value) is always higher than the headline commission rate in your contract. Here is what the gap looks like across common tiers, assuming standard GST, platform fee, and gateway charges.
A restaurant owner signing up at 18% commission expects to keep 82% of order value. In practice, after GST, platform fee, and gateway charges stack on, the take-home drops to around 74%. At a 30% commission tier, the effective cut crosses 40%, leaving the restaurant with roughly 60% of the original order value.
What Types of Errors Make the Gap Worse?
The structural gap is predictable. You can calculate it once and know what to expect. The unpredictable part comes from four error types that create additional shortfalls beyond the legitimate deductions.
Status mismatches cost the most per incident. For example, if a QSR in Electronic City delivers Order #7291 at 9:34 PM and the rider hands it to the customer, but the aggregator’s backend records it as “cancelled” due to a system timeout during peak hours, the full order value goes unpaid. One status mismatch on a Rs 450 order wipes out more money than twenty Rs 20 amount variances combined.
Amount variances are the most frequent error type. Small differences of Rs 5-40 per order, usually from GST rounding, discount code mismatches, or offer adjustments that the platform applied but your POS did not register. A cloud kitchen in Malad running two brands across both platforms might accumulate 15-25 such variances per week without anyone noticing.
Missing orders surface when an order exists in your POS but never appears on the settlement sheet. These tend to cluster during high-traffic windows like Friday dinners or festival weekends, when backend systems are processing thousands of concurrent transactions.
Commission overcharges occur when the platform deducts a higher percentage than your contract states. Mid-cycle changes to fee structures, auto-enrolment in promotional programmes, or backend errors applying a different tier can all cause this.
India’s food services industry is projected to grow at 8.1% CAGR to reach Rs 7.76 lakh crore by 2028, according to the NRAI India Food Services Report 2024. With hundreds of thousands of restaurants processing aggregator orders daily at that scale, even a small error rate across the ecosystem translates to crores in aggregate settlement gaps.
What Should You Do About It?
The structural deduction gap is the cost of being on an aggregator platform. It is not fixable. What you can control is whether the errors on top of that gap go unnoticed.
Know your effective deduction rate. Pick any 10 orders from last week’s settlement report and calculate the actual percentage deducted on each. A restaurant profit margin calculator can help you work out what you are actually keeping per order. If your contract says 22% but the average effective cut is 31%, that 9-point spread is your baseline. Anything above that baseline in future weeks signals an error worth investigating.
Reconcile weekly, not monthly. Both platforms enforce dispute windows that close within specific timeframes. Waiting until month-end to discover errors from Week 1 means the window for those disputes may already be shut. Restaurants that follow a weekly reconciliation workflow recover more money because they file disputes while the payout cycle is still open.
Use your POS data as the source of truth. Your POS records every order with a timestamp, amount, and delivery status. The settlement report records the same orders from the platform’s end. When these two datasets disagree, your POS data is the basis for your dispute. Restaurants managing multiple brands through a single POS find this easier because all order data sits in one place.
At Petpooja, we process data from 1,00,000+ restaurants. The pattern we see most often is that outlets crossing 60-80 online orders a day find Rs 2,000-8,000 per month in settlement gaps once they start reconciling.
Petpooja POSS includes a built-in reconciliation report that compares your order data against Swiggy and Zomato payouts and flags mismatches with specific Order IDs. It is part of the POSS subscription at no extra cost.
Conclusion
The gap between your aggregator dashboard and your bank deposit is structural. Six deduction layers ensure the two numbers will never match. That part is expected. The part that is not expected is when errors in commission rates, order statuses, or auto-applied discounts push the deposit below the legitimate deduction amount. The only way to separate the structural gap from erroneous shortfalls is to reconcile your POS data against the settlement report every week and raise disputes with specific Order IDs while the payout cycle is still open.
Frequently Asked Questions
The dashboard shows gross order value before deductions. Your bank gets the net after commission, GST, platform fee, and gateway charges. At a typical effective deduction of 28-35%, receiving Rs 1.3-1.44 lakh from Rs 2 lakh gross is within the expected range. If the gap exceeds 35%, run your numbers through a delivery commission calculator to check whether the actual deduction matches your contract.
Most restaurants receive weekly payouts. Zomato introduced a daily option in January 2024 for restaurants with fewer than 100 monthly orders, with settlements arriving based on sales from three days prior. Swiggy’s standard cycle remains weekly. Settlement frequency affects timing, not the deduction amount.
No. TDS applies only when your total annual payouts from the platform exceed Rs 5 lakh. Below that threshold, no TDS is deducted. Above it, the platform withholds 1% on the payout amount. You can claim this credit when filing your income tax return. Use the TDS calculator to estimate your liability and track cumulative deductions quarterly.
Open your settlement report and look for line items labelled “promotional”, “sponsored”, or “visibility boost”. If you did not opt into any programme through the partner app, flag these with the platform’s restaurant support team. Use your food cost calculator data alongside to show the margin impact of unapproved deductions.
Commission rates are negotiable for restaurants with high daily order volumes (typically 50+ orders per day) or multiple outlets. Contact your aggregator account manager and negotiate based on your volume and commitment. The aggregator landscape in India has grown competitive enough that platforms offer flexibility to retain high-volume partners.
