Reconciling Payouts: How to Check If Zomato Actually Paid You for All 100 Orders Last Week
MenuHelper Editorial
Senior Business & Food-Tech Analyst
Reconciling Swiggy and Zomato payouts is the financial task that almost every Indian cloud kitchen and restaurant owner knows they should be doing — and almost nobody actually does. They wait for the weekly settlement to arrive in their bank account, glance at the total, confirm it's "roughly what it should be," and move on. That's not reconciliation. That's wishful accounting. And it's costing Indian restaurant operators thousands — sometimes lakhs — in undetected payment gaps every month.
Most experts get this wrong. They focus entirely on commission rates and margin calculations — which are important — but ignore the downstream question of whether the platform actually executed the payout correctly on every single order. The ugly truth is that platforms process millions of transactions and their systems, like all systems, make errors. Automatic refund deductions applied to the wrong orders. Orders included in the count but excluded from the payout calculation. Settlement amounts rounded down by fractions that accumulate into meaningful sums at volume. None of this is necessarily malicious. All of it is your problem to identify.
So here is the complete reconciliation process — step by step, with real numbers — for checking whether Zomato or Swiggy actually paid you for every order you fulfilled last week.
Why Platform Payouts Are Wrong More Often Than You Think
Before the process, the context. Let's look at what the platforms don't tell you: their settlement systems are automated, and automation means errors occur at a predictable rate. The question is not whether payout errors happen — they do. The question is whether you have a system to catch them.
The most common sources of payout discrepancies, in order of frequency, are:
Automated Refund Deductions Without Notification
A customer reports a missing item or food quality issue. The platform processes an automatic partial or full refund. The deduction appears in your settlement — often without a specific notification linking it to the original order. At 200+ orders per day, these can accumulate without being individually identified.
Cancelled Orders Included in Order Count but Not Payout
Orders that are cancelled after acceptance — by the customer, the platform, or due to a delivery partner issue — appear in your order count but attract zero payout. If your kitchen has already prepared the food for a cancelled order, you've incurred the cost with no revenue. The order count and payout count should match exactly for completed orders.
Promotional Discount Deductions Applied Incorrectly
If you're participating in a platform promotion, your share of the discount is deducted from your payout on qualifying orders. Sometimes this deduction is applied at the wrong rate, on the wrong orders, or on orders that shouldn't have qualified for the promotion at all. The deduction appears in aggregate in most settlement summaries, making individual errors invisible without order-level review.
Settlement Period Boundary Errors
Orders placed near midnight on settlement period boundaries — Sunday evening orders, for instance — can sometimes be allocated to the wrong settlement week. This doesn't cause permanent loss, but it creates temporary discrepancies that look like missing payments until you identify the timing issue.
TDS Deducted on Cancelled Orders (Not Reversed)
As discussed in the Section 194-O context, TDS should be reversed on cancelled orders. When it isn't, your gross sales figure in Form 26AS is inflated, and your settlement shows a TDS deduction on revenue you never actually received. This is both a payout discrepancy and a tax issue requiring correction at the platform end.
The Per-Order Economics You Need to Know Before You Reconcile
Reconciling Zomato and Swiggy payouts requires knowing exactly what you should have received for each completed order. You can't identify a discrepancy if you don't know the expected number. Here is the complete calculation on a standard ₹550 order — this is your baseline.
| Line Item | Calculation | Amount | Your Expected Payout |
|---|---|---|---|
| Gross Order Value (Customer Pays) | Menu price | ₹550.00 | ₹550.00 |
| Platform Commission (25%) | ₹550 × 25% | – ₹137.50 | ₹412.50 |
| GST on Commission (18%) | ₹137.50 × 18% | – ₹24.75 | ₹387.75 |
| Fixed Platform Fee | Per-order flat | – ₹5.00 | ₹382.75 |
| TDS — Section 194-O (1%) | ₹550 × 1% | – ₹5.50 | ₹377.25 |
| Expected Net Payout Per Order | Before refunds/promos | ₹377.25 | ₹377.25 |
| Promotional Discount Share (if applicable) | Depends on promo terms | Variable | Reduces payout |
| Refund Deduction (if applicable) | Per complaint | Variable | Reduces payout |
| ⚠️ At 100 orders/week at ₹550 average: Expected gross payout = ₹37,725 (before COGS). If your bank receipt is ₹35,000, you have a ₹2,725 discrepancy that needs a line-by-line explanation — not a shrug. | |||
The expected net payout per order — ₹377.25 on a ₹550 order at standard rates — is your reconciliation baseline. Multiply it by your order count for the week. Compare the product to the settlement amount received. Any gap larger than what refund deductions and promotional co-funding can account for is a discrepancy that requires investigation.
📊 Calculate your expected payout per order instantly.
Check your own margins using our Swiggy & Zomato Profit Calculator — enter your commission rate, GST, platform fee, and menu price to get the exact per-order payout you should be receiving.
The Step-by-Step Reconciliation Process
Here is the exact process. It takes about 30–45 minutes per platform per week if you're doing it for the first time. Once you've built the habit and a simple spreadsheet template, it drops to 15 minutes. The data you need is available in both platforms' partner portals right now.
Download Your Order-Level Report
Log into your Swiggy or Zomato partner portal. Navigate to Reports or Payouts. Download the order-level data for the settlement period you want to reconcile — not the summary, but the full line-by-line order report with individual order IDs, order values, and payout amounts. This is the raw data you'll work from. If the portal only shows aggregate summaries, contact partner support and request order-level data explicitly.
Cross-Reference Order Count Against Your Kitchen Records
Count the completed orders in the platform report. Compare that number against your kitchen order log, POS system, or physical KOT (Kitchen Order Ticket) count for the same period. These numbers should match exactly. If the platform shows 97 completed orders and your kitchen logged 100, you have 3 orders that were received and fulfilled but may not have been included in the payout calculation. Identify the specific order IDs that are missing.
Verify the Gross Sales Figure
Sum the individual order values from the order-level report. This should equal the gross sales figure shown in your settlement statement. If the sum of individual orders doesn't match the aggregate gross sales on the statement, there is a calculation error somewhere in the platform's settlement processing. This is rare but it does occur — and it's the kind of discrepancy that only surfaces through order-level reconciliation, not summary-level review.
Audit Every Deduction Line Individually
Your settlement statement will show deductions in categories: commission, GST on commission, platform fee, TDS, refunds, promotional deductions. For each category, verify that the amount shown is mathematically consistent with your order data. Commission should be commission rate × gross sales. GST on commission should be 18% of the commission total. TDS should be 1% of gross sales. Any category that doesn't match the formula deserves a formal query to partner support.
Isolate and Investigate Refund Deductions
Refund deductions are the most common source of unexplained gaps. For every refund deduction in your settlement, you should be able to identify the corresponding order ID, the complaint type, and the refund amount. If a refund appears for an order you have no complaint record for, or if the refund amount exceeds what the platform's own policy allows for the complaint category, that's a dispute. Document it and raise it formally within the 30-day dispute window.
Reconcile Against Bank Statement and Raise Disputes
After verifying all deductions, the net settlement figure should match the bank credit received. If it doesn't — even by a few hundred rupees — investigate. Log every discrepancy with the order ID, expected amount, received amount, and the date you identified it. Raise disputes through the platform portal for each item individually. Keep all correspondence in writing. If portal disputes go unresolved beyond the stated response time, escalate via email to partner support with full documentation.
Building a Simple Weekly Reconciliation Spreadsheet
You don't need accounting software to do this. A simple spreadsheet with six columns handles the entire process. Here is the template structure:
Weekly Reconciliation Template — Column Structure
The "Expected Payout" column is calculated using the formula from the table earlier in this article — gross order value minus commission, minus GST on commission, minus fixed platform fee, minus TDS. Any row where Variance is non-zero and cannot be explained by a documented refund or promotional deduction is a dispute item. Flag it, record it, and raise it before the 30-day dispute window closes.
The 2026 Hidden Fee Update: Why Reconciliation Is Harder This Year
Reconciling Swiggy and Zomato payouts was already time-consuming in previous years. In 2026, four structural changes have made it materially more complex — and made undetected discrepancies more likely for operators who aren't reviewing their settlements systematically.
Update 1 — Automated Refund Processing Has Accelerated. Both platforms moved to more automated refund handling in 2025, meaning customer-reported complaints now trigger automatic deductions faster than before — sometimes within hours of the complaint being filed. The deduction appears in your settlement before you've had any opportunity to contest it. The dispute window still exists, but the default is now "deduct first, dispute later" rather than "review before deducting." This fundamentally changes your reconciliation burden: you now need to proactively identify disputed refunds rather than waiting to receive a notification.
Update 2 — Promotional Deductions Are More Complex to Audit. With both platforms expanding their promotional ecosystems in 2025–2026 — more campaigns, more co-funding structures, more subscription-tier obligations — the promotional deduction section of settlement statements has become significantly more granular. Multiple deduction types now appear under the promotional category, each with different calculation bases. What was previously a single line item is now sometimes four or five. Reconciling each against the specific campaign terms requires access to the campaign documentation, which is not always readily available in the portal.
Update 3 — Settlement Timelines Have Extended for Some Partners. As noted in previous posts in this series, the stated 7-business-day settlement cycle has stretched to 10–14 days for a segment of partners. This makes it harder to identify missing payments within the dispute window, because by the time you notice a payment hasn't arrived, you may already be near the 30-day dispute deadline. The practical response: set a calendar reminder to check every settlement exactly 10 business days after the period end, not when the payment arrives.
Update 4 — Dual-Platform Order Data Is Not Consolidated Anywhere. If you're listed on both Swiggy and Zomato, you are running two separate reconciliation processes with two separate data formats, two separate dispute portals, and two separate settlement timelines. There is no consolidated reporting tool available from either platform that combines both. Third-party aggregator management tools exist for this, but they add cost. For most cloud kitchen operators, the practical solution remains two separate spreadsheets — one per platform, reconciled weekly, ideally on the same day.
The Dispute Window: How Long You Have and What to Do
Both platforms operate formal dispute windows — the period within which you can raise a payout discrepancy claim. Miss the window and the claim is generally not entertained, regardless of how clear the error is. Know these deadlines and treat them as hard limits.
Dispute Window Reference
When you raise a dispute, include: the specific order ID, the settlement period, the expected amount, the actual amount received, and a clear description of the discrepancy. The more specific your documentation, the faster the resolution. Vague disputes — "I think I was underpaid last week" — get deprioritised. Specific disputes with order IDs and calculations attached get resolved.
Thirty Minutes a Week That Pays for Itself
Most cloud kitchen operators in India are doing no formal payout reconciliation at all. They're trusting platforms — businesses with their own interests, running automated systems that make errors — to have paid them correctly. Some of those operators are leaving ₹5,000 to ₹20,000 per month in disputed payments unclaimed, month after month, because the 30-day window passed before they noticed.
The process described here takes 30 minutes per platform per week once you've built the spreadsheet template. At 200 orders per week on one platform at ₹550 average order value, your expected weekly gross payout is approximately ₹75,450. A 1% discrepancy in that settlement is ₹754. Not life-changing. But a 1% discrepancy every week for 52 weeks is ₹39,208 per year. That's money that is either being recovered by operators who reconcile, or being absorbed as an unidentified cost by operators who don't.
Reconcile. Weekly. For every platform. Before the dispute window closes. It is the single most underutilised financial control available to Indian restaurant operators — and the one with the most direct, measurable return.
💡 Know exactly what your settlement should be — before it arrives.
Check your own margins using our Swiggy & Zomato Profit Calculator — calculate your exact expected payout per order so you have a baseline to reconcile against every settlement week.