Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →
A multi-outlet QSR chain reconciling Swiggy Food and Swiggy Instamart payouts must handle commission tier complexity, SLA penalty deductions, ad-spend deductions, restaurant-borne discount components, the 7 to 14 day Partner Portal dispute window, Food vs Instamart channel split, Section 393 TDS at 1% under payment code 1010, Section 52 CGST TCS at 1%, GSTR-2B commission ITC matching, multi-GSTIN consolidation, and CARO 2020 audit evidence — across 30 to 100 outlets — and then evaluate whether manual Excel, an aggregator-side tool, or reconciliation infrastructure is the right fit.
Walk each approach through one Swiggy weekly cycle: ingest the Food and Instamart settlement files at order level, classify Food vs Instamart channel with channel-specific GST treatment (5% no-ITC for prepared meals; 12% or 18% with ITC for Instamart categories), decompose commission and 18% GST on commission, accrue Section 393 TDS at 1% with payment code 1010 mapping, compute Section 52 CGST TCS with intra-state CGST/SGST or inter-state IGST split, separate platform-borne from restaurant-borne discounts, classify SLA penalties by category, link to POS gross sales, link to bank credit narration, match commission ITC against GSTR-2B, accept TCS into cash ledger via GSTR-8A, flag Section 9(5) GST liability, surface dispute candidates inside the Partner Portal window, and roll up across outlets, GSTINs, states, and channels.
Swiggy Food and Instamart settlement-file connectors with channel-specific rules; commission tier table per outlet agreement; Section 393 TDS calculator at 1% on gross supply with payment code 1010 mapping; Section 52 CGST TCS calculator with intra-state CGST/SGST and inter-state IGST split; SLA penalty parser with category mapping; restaurant-borne vs platform-borne discount classifier; GSTR-2B commission ITC matcher; GSTR-8A cash-ledger acceptance flow; Section 9(5) GST classifier; refund-period reversal logic; multi-outlet, multi-GSTIN, multi-state rollup; dispute-window flagging.
A reconciled Swiggy weekly cycle in which every order traces from gross sale through commission, GST, Section 393 TDS, Section 52 TCS, SLA penalty, and discount components to the bank credit; commission ITC is matched to GSTR-2B per GSTIN; Section 52 cash-ledger credit is accepted via GSTR-8A; dispute candidates are flagged before the Partner Portal cut-off; multi-outlet, multi-GSTIN, multi-state rollups close inside the month; and CARO 2020 audit evidence is one query away.
A 60-outlet QSR chain operates on Swiggy Food across 4 states, with 15 outlets also listed on Swiggy Instamart for a packaged-foods sub-brand. Every Wednesday, two distinct bank credits arrive — one for Food, one for Instamart — with structurally different deduction stacks. At ₹5 crore monthly Swiggy GMV (₹4.2 crore Food, ₹0.8 crore Instamart) the chain generates roughly ₹5 lakh of Section 393 TDS receivable, ₹5 lakh of Section 52 CGST TCS cash-ledger credit, and ₹22.5 to ₹30 lakh of commission with the corresponding 18% GST input tax credit at stake every month. SLA penalties on Food typically run ₹40,000 to ₹1.2 lakh a week depending on operations discipline. Restaurant-borne discount components on running campaigns can range from 4 to 12 percent of gross order value.
This article is a buyer’s evaluation walkthrough for a finance leader at a 30 to 100 outlet QSR chain choosing between manual Excel, an aggregator-side reconciliation tool, and reconciliation infrastructure for Swiggy.
What Makes Swiggy Different
Swiggy’s settlement file carries every deduction Zomato carries, plus three Swiggy-specific layers that the reconciliation must handle natively:
SLA penalty fees — late preparation, post-acceptance cancellation, rejection, and excessive cancellation rates each trigger a deduction line. Penalty schedules range from ₹50 per order for minor breaches to higher figures for systematic violations. These do not surface on the partner dashboard summary in real time; they appear only at cycle close.
Restaurant-borne discount components — Swiggy operates platform-borne (Swiggy-funded) and restaurant-borne (jointly-funded) discount mechanics. Restaurant-borne discounts are deducted from gross sales; platform-borne discounts are not. The 194O / Section 393 TDS computation uses gross sale value net of restaurant-borne discounts only.
Food vs Instamart channel split — Swiggy Food and Swiggy Instamart issue separate settlement files with different commission structures, different GST treatments (5% no-ITC for prepared meals on Food; 12% or 18% with ITC on Instamart categories), and different SLA frameworks. Mixing the two in a single reconciliation workflow creates GSTR-1 misclassification that surfaces only at year-end audit.
The Four-Rail Framework
A Swiggy reconciliation closes when four rails join at order level:
- Aggregator — Swiggy Partner settlement file (Food and Instamart, separately).
- POS — the chain’s order management system, exporting gross sales, refunds, and cancellations.
- Cash — the bank credit narration tied to each weekly cycle.
- GST — GSTR-2B for commission ITC, GSTR-8A for Section 52 TCS, the electronic cash ledger, and GSTR-3B for output liability and utilization. See TCS Section 52 walkthrough.
A reconciliation that joins fewer than four rails leaves audit evidence gaps that surface in CARO 2020 reporting or in the next GST audit.
Walkthrough: One Swiggy Weekly Cycle, 60 Outlets
The same cycle, the same data, three approaches.
Step 1 — Settlement file ingestion across two channels
A 60-outlet weekly Swiggy file carries 50,000 to 80,000 Food order rows and 8,000 to 15,000 Instamart line items on the package side, with separate column schemas.
- Manual Excel. Two workbooks per cycle, each with multi-outlet tabs, joined manually for chain-level rollup.
- Aggregator-side tool. Two connectors with channel-aware parsing.
- Reconciliation infrastructure. Both files normalize to a common order-level model with channel as a dimension, so chain rollup is one query.
Step 2 — Commission tier and 18% GST on commission
Swiggy commission ranges from 18% to 25% for standard partners, climbing to 25% to 30% or higher for delivery-only kitchens. At ₹5 crore monthly GMV with a blended 26 percent commission, the chain pays roughly ₹1.3 crore commission with ₹23.4 lakh of 18% GST on commission as ITC. Tier rule changes mid-month — frequent in Swiggy’s commercial cadence — must propagate without breaking earlier-cycle history.
Step 3 — SLA penalty classification
A 60-outlet chain processing roughly 90,000 weekly orders typically sees 200 to 1,200 SLA penalty events per week depending on operations maturity. Each penalty must be classified by category (late prep, rejection, post-acceptance cancellation, excessive cancellation rate), posted to a distinct ledger head, and routed to the kitchen operations team for root-cause review. A financial deduction that no operational owner sees becomes a recurring leak.
Step 4 — Restaurant-borne vs platform-borne discount classification
The settlement file separates platform-borne and restaurant-borne discount lines explicitly. The 194O / Section 393 TDS computation uses gross sale value net of restaurant-borne discounts only. Booking the gross sale value without deducting the restaurant-borne discount overstates revenue; treating platform-borne discounts as restaurant-borne understates the TDS base. At a 6 percent restaurant-borne rate on ₹5 crore monthly GMV, the misclassification can move ₹30 lakh of revenue and ₹30,000 of TDS.
Step 5 — Section 393 TDS at 1% under payment code 1010
Section 393 of the Income Tax Act 2025 carries forward the e-commerce operator TDS regime from legacy Section 194O. Swiggy deducts 1% on gross supply value (net of restaurant-borne discounts and refunds) and deposits under payment code 1010. At ₹5 crore monthly GMV that is ₹5 lakh of TDS receivable per month — claimable against quarterly advance tax if posted on time. Cross-period refund reversals require posting to the original sale period when crossing a filing month. See Section 393 TDS new Income Tax Act reconciliation and TDS payment codes 1001-1092.
Step 6 — Section 52 CGST TCS at 1% to the cash ledger
Section 52 of the CGST Act is unchanged by the Income Tax Act 2025. Swiggy collects 1% TCS on net taxable supply, files monthly GSTR-8, auto-populates GSTR-8A for the chain, and credits the GST electronic cash ledger to offset output GST in GSTR-3B. At ₹5 crore monthly GMV that is approximately ₹5 lakh of cash-ledger credit, split as 0.5% CGST + 0.5% SGST for intra-state supplies or 1% IGST for inter-state. With 5 to 18 GSTINs across states, GSTR-8A acceptance is a per-GSTIN flow on the GST portal.
Step 7 — GSTR-2B commission ITC matching
The 18% GST on commission — ₹23.4 lakh monthly in this example — is ITC-eligible. The match is between the chain’s books, the Swiggy commission tax invoice, and GSTR-2B. With 5 to 18 GSTINs the match runs in parallel per GSTIN.
Step 8 — Section 9(5) GST liability classification
Restaurant supplies through e-commerce operators are taxed at the operator’s hands for specific notified categories under Section 9(5) of the CGST Act. The chain’s reconciliation must classify each supply as Section 9(5) (operator pays output GST, restaurant excludes from its own GSTR-1) or own outward supply (restaurant pays output GST in GSTR-1).
Step 9 — Dispute-window flagging
The Swiggy Partner Portal dispute window is 7 to 14 days. Variances on commission, refund reversals, or SLA penalties must be raised inside that window or the deduction stands. For 90,000 weekly orders, manual review at the variance level is not feasible.
Step 10 — Bank credit linking and multi-rail close
Two bank credits per week (Food, Instamart), each tagged to a settlement cycle in the bank narration. Linking each credit to the corresponding settlement file closes the cash rail. Cross-tagging Food’s credit to Instamart’s file breaks the chain-level rollup.
Step 11 — Multi-outlet, multi-GSTIN, multi-channel rollup and CARO 2020 evidence
60 outlets, 5 to 18 GSTINs, 2 channels, weekly cadence — roughly 50 to 100 distinct rollup cells per cycle. CARO 2020 audit evidence requires pull-on-demand for each cell against each statute (Section 393, Section 52, GSTR-1, GSTR-3B).
Approach Comparison for a 30 to 100 Outlet Chain
| Capability | Manual Excel | Aggregator-side tool | Reconciliation infrastructure |
|---|---|---|---|
| Food + Instamart channel split | Two workbooks | Channel-aware | Channel as dimension on one engine |
| SLA penalty classification | Manual ledger | Automated parser | Automated, ops routing |
| Restaurant-borne vs platform-borne | Manual classifier | Automated | Automated |
| Section 393 TDS posting (code 1010) | Manual schedule | Computed, posting manual | End-to-end |
| Section 52 TCS to cash ledger | Manual GSTR-8A | Computed, claim manual | End-to-end |
| GSTR-2B commission ITC match | Out of scope | Often out of scope | Native per GSTIN |
| Section 9(5) classifier | Separate sheet | Optional | Native rule |
| Dispute-window flagging | Reactive | Proactive | Proactive, multi-rail |
| Multi-aggregator (Zomato, ONDC) | Re-build per aggregator | Separate tool per aggregator | One engine |
| Multi-GSTIN, multi-state rollup | Quarterly pivot | Outlet level | Continuous, all dimensions |
| CARO 2020 audit evidence | Reconstructed | Partial | Continuous |
| ERP write-back | Re-keyed | Per-aggregator integration | Native |
Where Each Approach Breaks
Manual Excel holds together below 10 outlets and roughly 12,000 weekly orders. Past that, the dispute window starts slipping, SLA penalty leakage compounds, and the GSTR-3B utilization of Section 52 cash-ledger credit drifts.
Aggregator-side reconciliation tools — products in the per-aggregator reconciliation category — solve the Swiggy-specific deduction trace cleanly within the platform boundary. They break at the GST portal interface, multi-aggregator consolidation, multi-GSTIN cash-ledger management, and four-rail joins for CARO 2020 audit evidence. For a 30 to 100 outlet chain on Zomato + Swiggy + ONDC + direct-channel, stacking three or four aggregator-side tools reintroduces the integration gap the first tool was bought to remove.
Reconciliation infrastructure — a config-driven engine treating Swiggy as one of many sources — pays off at scale where multi-aggregator, multi-statute, multi-GSTIN rollup is the bottleneck. For the engine surface, see restaurant reconciliation software India and the broader payment gateway reconciliation money page. For named comparison, see vs Cointab.
Buyer-Side Evaluation: Ten-Dimension Scorecard for Swiggy
A finance leader evaluating reconciliation options for a 30 to 100 outlet Swiggy chain should score ten dimensions:
- Food and Instamart channel coverage on the same engine.
- SLA penalty parser with category mapping and ops routing.
- Restaurant-borne vs platform-borne discount classifier.
- Section 393 TDS calculator at 1% with payment code 1010.
- Section 52 CGST TCS with intra-state CGST/SGST and inter-state IGST split.
- GSTR-2B commission ITC matcher per GSTIN.
- GSTR-8A acceptance flow with cash-ledger utilization to GSTR-3B.
- Section 9(5) classifier feeding GSTR-1 staging.
- Dispute-window flagging with multi-rail variance surfacing.
- Multi-outlet, multi-GSTIN, multi-state, multi-channel rollup with CARO 2020 evidence retention.
For the broader context, see restaurant reconciliation India and the regulatory walkthrough at TCS Section 52 restaurant aggregator reconciliation. For the restaurant chain industry surface, see the Restaurant Chains industry guide.
The questions below address the buyer-side decisions most often raised by finance leaders at 30 to 100 outlet QSR chains running on Swiggy.