Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
Swiggy's weekly restaurant settlement carries the same 194O and Section 52 deductions as Zomato but adds SLA penalties and restaurant-borne discount lines that vary order by order — and Swiggy Food and Swiggy Instamart use entirely separate payout files that must not be reconciled in the same workflow.
Ingest the Swiggy Partner settlement file at order level, classify each order by Food or Instamart channel, separate platform-borne from restaurant-borne discounts, post commission and 18% GST on commission with ITC, accrue 194O TDS and Section 52 TCS as receivables, expense SLA penalties as a distinct ledger head, and surface dispute candidates within the 7 to 14 day Partner Portal window.
Swiggy Food and Instamart settlement file connectors with channel-specific rules; commission tier table per restaurant agreement; SLA penalty parser with category mapping; restaurant-borne vs platform-borne discount classifier; 194O 1% on gross taxable supply; Section 52 1% TCS with intra-state and inter-state split; weekly dispute-window flag.
A reconciled Swiggy weekly payout with each order traced to gross revenue, commission, GST, TDS, TCS, SLA, and discount components, with disputes auto-flagged before the Partner Portal cut-off and tax credits posted in time for monthly GSTR-3B and quarterly TDS reconciliation.
A restaurant chain runs 6 outlets on both Swiggy Food and Swiggy Instamart in Mumbai. Every Wednesday, two separate bank credits arrive — one for the Food channel, one for Instamart — and the deduction stack on each is structurally different. The Food payout carries SLA penalties for late preparation; the Instamart payout carries inventory adjustments and a 12% or 18% GST treatment instead of the 5% restaurant rate. This article is for finance teams running multi-channel restaurants with Swiggy as a primary or secondary aggregator.
What Swiggy Settlement Reconciliation Involves
Swiggy restaurant settlement reconciliation is the process of matching the Swiggy Partner settlement file, the restaurant’s POS or order management data, and the bank credit narration for each weekly cycle. The reconciliation produces an order-level trace that ties gross revenue to net cash, with each deduction posted to its own ledger head. Swiggy’s deduction stack is denser than a typical payment gateway because it combines tax deductions (194O, Section 52), commission, GST on commission, restaurant-borne discounts, and SLA penalties in a single file.
The complication that distinguishes Swiggy from Zomato is the SLA penalty layer. When a restaurant rejects an order, prepares it late, or cancels after acceptance, Swiggy debits a penalty fee against future settlement. These penalties are not always visible in real time on the Partner dashboard summary — they surface only at cycle close in the settlement file, often days after the underlying event.
How the Swiggy Weekly Settlement Differs From Zomato
SLA Penalties and Rejection Fees
Swiggy maintains a service-level framework with explicit penalties for breach. Late preparation beyond the committed prep time, post-acceptance cancellations, or repeated rejections trigger fee deductions that appear as a distinct line in the settlement. These fees range from ₹50 per order for minor breaches to higher figures for systematic violations. Reconciliation must classify each penalty by category and feed it back to the kitchen operations team for root-cause review — a financial deduction that no operational owner sees becomes a recurring leak.
Restaurant-Borne vs Platform-Borne Discounts
Swiggy runs two discount mechanics. Platform-borne discounts (Swiggy One free delivery, Swiggy-funded coupon offers) do not affect the restaurant payout. Restaurant-borne discounts (campaigns where the restaurant agreed to fund part of the offer) are deducted from gross sales. The settlement file separates these lines explicitly. Booking the gross sale value without deducting the restaurant-borne discount overstates revenue; deducting platform-borne discounts also overstates the deduction. The 194O TDS computation must use the gross sale value net of restaurant-borne discounts only.
Food vs Instamart Channel Separation
Swiggy Food and Swiggy Instamart issue separate settlement files with different commission structures, GST treatments, and SLA frameworks. Food carries the 5% no-ITC GST regime for prepared meals; Instamart carries 12% or 18% GST with ITC depending on product category. Mixing the two in a single reconciliation workflow creates GSTR-1 misclassification that surfaces only at year-end audit.
Swiggy Weekly Settlement Deduction Reference
| Deduction Head | Typical Range | Tax Treatment |
|---|---|---|
| Platform commission | 18% to 30% of gross | Expense; 18% GST on commission is ITC-eligible |
| TDS Section 194O | 1% of gross taxable supply | Receivable; appears in Form 26AS |
| TCS Section 52 | 1% (CGST+SGST or IGST) | GST credit via GSTR-2A |
| SLA penalty fees | ₹50 per order and above | Operating expense; distinct ledger head |
| Restaurant-borne discount | Campaign-specific | Marketing expense; reduces gross revenue base |
| Refund or cancellation reversal | Order-specific | Reverses revenue and output tax in original period |
India Compliance Angle: Dispute Window and 194O Timing
The Swiggy Partner Portal enforces a 7 to 14 day dispute window for settlement entries. A penalty or commission variance not raised within this window becomes permanent. For a chain with 200 orders per day per outlet across 6 outlets, that is roughly 8,400 orders per week — manual review at this volume is impossible without an order-level reconciliation pipeline that flags variances by category and severity. The 194O TDS deduction shows in Form 26AS by the 15th of the next month under the deductor PAN of Bundl Technologies Private Limited (Swiggy’s parent). Restaurants that miss reconciling the 194O credit in the same quarter cannot adjust against advance tax instalments and must wait for income tax return filing, locking up working capital for 6 to 12 months.
Finance teams running payment gateway reconciliation workflows can extend the same matching engine to Swiggy aggregator payouts, where the deduction stack is denser than card or UPI settlement. Reconciliation software India ingests both Swiggy Food and Instamart files, applies channel-specific rules, and produces dispute-ready variance lists before the Partner Portal cut-off. The Income Tax Department publishes the Section 194O framework and Form 26AS access where restaurants verify TDS credit each month. For pillar context, see restaurant reconciliation India.
For the restaurant chain industry surface, see the Restaurant Chains industry guide. For the buying-intent surface covering this rail, see the restaurant reconciliation software for India overview, and for a head-to-head against the aggregator-side reconciliation tool category, see TransactIG vs Cointab.
The questions below address the Swiggy-specific reconciliation issues most often raised by Indian restaurant finance teams.