Zomato & Swiggy Payout Cycles: How to Audit Weekly Deductions (2026)

The Payout Calendar: When Your Delivery Money Actually Arrives

For any independent restaurant or cloud kitchen in India, cash flow is oxygen. You purchase raw vegetables and poultry from the mandi every morning in cash, pay your cooks on the 1st of the month, and pay commercial LPG cylinder vendors on delivery.

Yet food aggregators do not operate in cash: they operate on institutional settlement batches. Understanding the exact calendar mechanics of when your money lands is vital to preventing weekend working capital crunches:

• The Default Weekly Cycle: On both Zomato and Swiggy, the default settlement period is generally a week of orders. The statement is prepared after the week closes and the bank transfer follows a few days later. Your partner agreement and past statements tell you the exact cut-off and the day credits usually land.
• Bank Holiday Delays: Because payouts move through standard banking channels, public holidays and bank holidays (including second and fourth Saturdays) can push a credit back.
• The Settlement Float: Say your weekly cycle closes on Sunday night and the credit lands the following Thursday. A ₹1,200 family dinner order dispatched on Friday night then reaches your banksix days after the food was eaten, and an order from the Monday before waits ten days.

Daily Payouts vs Weekly Cycles: Eligibility & T+3 Mechanics

In late 2023, Zomato announced daily payouts for its restaurant partners. Before you plan your cash flow around a daily credit, check two details in your partner app:

1. Eligibility: As reported at the time of the announcement, the daily option was aimed at smaller restaurant partners. If your delivery volume is higher, assume you are on the weekly batch unless your partner app shows otherwise.
2. The Rolling T+3 Delay: Daily payouts do not mean same-day cash. As reported, each payout covers orders from three days earlier (T+3), so Monday's orders would arrive on Thursday.

The Anatomy of an Aggregator Deduction: Where Your Payout Shrinks

When restaurant operators say their payout was “short,” the cause is rarely a banking error. Usually the difference is a stack of line-item deductions inside the platform's weekly statement:

The 4 Most Commonly Missed Deductions to Check

If you do not audit your weekly CSV settlement report line by line, four recurring categories of deduction are easy to miss:

1. “Spillage & Packaging” Customer Refunds

When a diner reports in the app that their dal makhani leaked or their burger arrived cold, the platform may refund all or part of the order. Depending on the complaint and your partner agreement, that refund can be charged back to the restaurant and deducted from your upcoming payout. Check every refund row on your statement against your own packing records.

2. Late Rider Cancellations

During peak dinner hours or heavy monsoon rain, a rider can take longer than usual to reach you. Say your kitchen marks the food “Ready for Pickup” in 14 minutes, but no rider arrives for 45 minutes, and the hungry customer cancels.

Have your staff mark the order as prepared on the merchant tablet and keep photographic evidence. If the cancellation is then charged to your account, you have what you need to contest it.

3. In-App Sponsored Ad Spend Pre-Deductions

If your marketing manager turned on Cost-Per-Click (CPC) keyword bidding or banner visibility campaigns inside the Zomato or Swiggy merchant app, the spend is usually deducted from your payout rather than billed separately, so it shows up as a deduction on the weekly statement before the bank transfer.

4. Section 194-O TDS & Reconciliation Mismatch

Under Section 194-O of the Income Tax Act, platforms withhold 0.1% TDS on gross sales. While small, mismatches can appear between the gross sales the platform reports, the TDS credited in your Form 26AS, and the sales in your own books. If these numbers differ by even a few thousand rupees, your accountant will have to reconcile the difference at year end.

The 3-Tier Reconciliation Protocol: A 20-Minute Weekly Workflow

You do not need to spend four hours cross-checking 800 individual orders by hand. Aim for a structured, tiered workflow of about 20 minutes, run on the same morning each week, once your credit has landed:

• Tier 1 (High-Level Cycle Audit, about 3 minutes): Compare total order count and total gross sales from your POS against the top-line figures in the platform settlement summary. If both match within 1%, your orders were logged correctly.
• Tier 2 (Deduction Categorization, about 7 minutes): Check the total deductions column. Subtract your contractual commission (the rate in your agreement), 18% GST on that commission, and payment gateway fees. Any remaining negative balance represents refunds, cancellations, and ad spend.
• Tier 3 (Discrepancy Investigation, about 10 minutes): Filter your settlement spreadsheet for negative line items over ₹200. Cross-reference the specific Order IDs against your kitchen KOT records and prepare evidence for dispute.

The Dispute Window: How to File Evidence-Backed Claims

Platforms accept disputes on a settlement only for a limited period after the statement is issued; the exact window is in your partner agreement. Once it has passed, a dispute is likely to be rejected, so treat your weekly reconciliation as the deadline.

When filing a dispute ticket inside the Merchant Partner portal, avoid generic complaints like “my payout is less.” Instead, back your claim with clear, objective operational evidence:

• Specific Order ID: Always quote the exact platform transaction ID.
• Timestamped KOT: Proof that the order was received, accepted, and prepped on time.
• CCTV / Packaging Proof: Photo of the tamper-proof sealed bag showing correct item counts.
• Rider Delay Evidence: Screenshot showing that your kitchen marked the order “Food Ready” at 20:15, but the rider did not arrive at the counter until 20:55.

How Direct Dine-In Self-Ordering Keeps Settlement Delays Off Your Dining Room

Third-party aggregators play an important role in bringing in new delivery customers. For guests who are already sitting in your dining room, though, there is no reason for their orders to pass through a third-party settlement cycle.

That is where KNOMI fits:

• No Platform in the Middle: Guests scan the QR on the table and order from an illustrated KNOMI menu in their phone's browser, with no app and no login. KNOMI is not a marketplace: the bill is settled with your restaurant directly, so there is no weekly platform batch to wait for.
• 0% Commission: Nothing is deducted from your dine-in sales, and with no commission there is no GST on commission either. We share KNOMI's pricing on a short walkthrough call, once we understand your restaurant.
• Cleaner Reconciliation: Orders go straight to your kitchen display, and KNOMI integrates with the POS you already use, so dine-in orders sit in the same records you reconcile every week.