Swiggy Instamart FMCG Settlement Reconciliation

The FMCG controller at a national namkeen brand opens the September Swiggy Instamart settlement window for the Mumbai dark-store cluster and sees ₹1.8 crore of gross invoicing run through a single month at a single platform’s dense Mumbai network — Powai, Andheri West, Lower Parel, Bandra, Vile Parle, Mulund — settled on T+7 to T+14 cycles that vary by category. Section 52 TCS at the notified 0.5 percent rate has been withheld at roughly ₹90,000 against a net taxable value of around ₹1.794 crore. A listing fee debit of ₹4 lakh sits on the cycle, raised against the new-launch larger-pack Bhujia variant; a BTL marketing claim of ₹5 lakh has been deducted against the joint business plan for a Diwali-window in-app campaign. The residual net bank credit lands at approximately ₹1.70 crore. The audit committee will ask in November whether the BTL execution was actually delivered, whether the listing fees match the JBP, whether Section 52 TCS landed correctly in the brand’s electronic cash ledger, and whether any of the ₹1.8 crore was wrongly tagged under Section 9(5). This is Swiggy Instamart FMCG settlement at production scale for a Haldiram-grade brand, and the per-dark-store reconciliation discipline that closes it without an audit qualification is what separates a clean Q3 close from a year-end Section 73 notice.

Quick reference

Section 9(5) versus Section 52 — clearing the most common confusion

Section 9(5) of the CGST Act does NOT apply to FMCG goods sold via quick commerce. Section 9(5) covers four notified categories — passenger transport, housekeeping, restaurant (including cloud kitchens since 1 January 2022), and accommodation. FMCG quick-commerce goods follow Section 9(1) (the brand or dark-store operator is the supplier of record) with Section 52 TCS at the notified rate of 0.5% (CBIC Notification 15/2024-Central Tax, effective 10 July 2024; statutory ceiling under Section 52(1) is 1%). Verify directly: CBIC Circular 167/23/2021-GST.

The confusion arises because Swiggy as a corporate group also runs Swiggy Food — and Swiggy Food’s restaurant supplies through the platform do fall within Section 9(5) following the 1 January 2022 amendment via Notification 17/2021-CT(R). The instinct to extend that treatment to Swiggy Instamart is wrong. Instamart is the FMCG goods arm; Food is the restaurant services arm. The two run different GST regimes inside the same parent group. An Instamart FMCG supply is a Section 9(1) goods supply where the brand owner (or, where the platform’s commercial entity takes title in the dark-store wholesale model, the dark-store operator) is the supplier of record. Swiggy is the facilitator. Swiggy collects TCS at 0.5 percent under Section 52 on the net value of taxable supplies — split 0.25 percent CGST plus 0.25 percent SGST intra-state, or 0.5 percent IGST inter-state — and remits via the monthly GSTR-8 by the tenth of the following month. The brand claims the TCS credit in its electronic cash ledger via GSTR-3B against the GSTR-2A credit line.

The practical risk of getting this wrong on an Instamart FMCG cycle is immediate. A brand that misclassifies a Mumbai dark-store cluster’s monthly supply as a Section 9(5) deemed-supplier flow does not file the GSTR-1 outward supply at its own GSTIN, loses the TCS credit because no TCS would attach in a Section 9(5) flow, and faces a Section 73 or 74 notice on the under-declared output tax when the audit reconstructs the trail from Swiggy’s GSTR-8 filing. The CBIC Circular 167/23/2021-GST is the anchoring authority — read it directly rather than relying on platform commercials.

Why the Swiggy Instamart settlement file arrives per dark-store

Swiggy Instamart operates one of the densest urban dark-store networks in Indian quick commerce, with concentrations in Mumbai, Bangalore, Delhi and Pune. The brand’s typical PO cadence is per dark-store rather than at the city or zone level — each dark-store has its own ranging, its own velocity profile per SKU, and its own GRN team. The settlement file therefore lands per dark-store invoice cluster rather than as a single brand-GSTIN net. For a brand running ₹1.8 crore through a Mumbai cluster of six dark-stores, the settlement file decomposes into six cluster sub-totals, each with its own seven-bucket deduction profile.

Three operational realities flow from the per-dark-store structure. First, listing fees can differ across dark-stores even within the same city, because each dark-store category manager carries discretion over end-cap visibility and shelf placement. A reconciliation that aggregates to brand-GSTIN cannot detect a dark-store-level mis-pricing on a particular listing-fee debit. Second, fill-rate penalties are dark-store-specific — a stock-out in Powai does not penalise dispatches to Andheri West. Aggregating fill-rate penalties hides the dark-store-level conversation about delivery reliability. Third, BTL marketing campaigns are typically dark-store-cluster targeted — a Diwali campaign in the Mumbai cluster does not run in Pune, and the BTL claim must reconcile against the cluster it ran in. The per-dark-store discipline is therefore not optional; aggregating to GSTIN destroys the visibility needed to challenge each line.

The cadence of settlement varies by category and by dark-store turnover velocity. Fast-moving categories — namkeen, biscuits, soaps, shampoos — settle on the shorter end (T+7 to T+10) because consumer-purchase velocity is high and the platform’s payable team closes the cycle in line with sell-through. Slower-moving categories — premium chocolates, larger-pack edible oils — settle on the longer end (T+10 to T+14). Brands running multi-category SKUs through the same dark-store see different settlement horizons for different SKU clusters within the same monthly invoice cycle.

Worked example: Haldiram Snacks Aloo Bhujia, Mumbai Instamart cluster, monthly ₹1.8 crore cycle

Illustrative — public disclosures do not reveal internal scheme amounts; the figures here are representative of the operating pattern, not actual brand data. Cross-verify against your own DMS export or trade-spend GL before action.

Consider a national namkeen brand of Haldiram scale shipping Aloo Bhujia and a sister SKU range through Swiggy Instamart’s Mumbai dark-store cluster — Powai, Andheri West, Lower Parel, Bandra, Vile Parle, Mulund — across a representative September month. Gross invoicing for the month at the Mumbai cluster totals roughly ₹1.8 crore at the brand’s Mumbai GSTIN, against approximately 145 invoices across the six dark-stores and around 22 SKUs at the Aloo Bhujia and sister-namkeen ranging. The brand’s controller closes the Mumbai cluster’s monthly Instamart reconciliation in the first week of October.

The settlement file from Swiggy Instamart arrives per dark-store invoice cluster. Across the six Mumbai dark-stores, the consolidated deduction picture for the month works approximately as follows.

Item-level margin lands at around ₹14 lakh on a blended margin off MRP across the cluster, varying dark-store by dark-store on the agreed ranging-margin schedule. Listing fee for the new-launch larger-pack Bhujia variant runs at ₹4 lakh across the six Mumbai dark-stores combined, debited per dark-store per cycle. The BTL marketing claim — a Diwali-window in-app banner and push-notification campaign agreed in the September JBP — runs at ₹5 lakh against the cluster, carrying 18 percent GST that the brand claims back as ITC against the marketing GL (recoverable ITC of roughly ₹76,000 sitting on the BTL invoice). Scheme reimbursement and BOGO replacement claims raised by Instamart against an October festive scheme on the smaller-pack Bhujia come to ₹1.5 lakh — qualifying under Section 15(2) as post-supply discounts where the prior agreement and recipient ITC reversal conditions are met per the scheme master. Fill-rate and dark-store-specific QC penalties on the Diwali demand-spike supply come to ₹50,000 across two dark-stores. Return-to-vendor credit notes against close-to-expiry stock from the July dispatches come to ₹40,000.

The Section 52 TCS line is the headline number for the audit trail. On the net taxable value of approximately ₹1.794 crore (gross of ₹1.8 crore less the value of return-to-vendor credit notes and the BTL-invoice value which is separately invoiced), Section 52 TCS deducted by Swiggy across the six dark-stores comes to roughly ₹90,000 — the 0.5 percent notified rate applied dark-store by dark-store. The brand reconciles this against the Swiggy GSTR-8 filing that lands in the following month’s GSTR-2A TCS credit table. The TCS credit lands in the brand’s electronic cash ledger on the next GSTR-3B cycle.

The residual bank receipt for the Mumbai cluster — net of margin, listing fees, BTL marketing claim, scheme reimbursements, fill-rate penalties, RTV credit notes and Section 52 TCS — works out to approximately ₹1.70 crore against gross invoicing of ₹1.8 crore. Of the roughly ₹10 lakh apparent gap, around ₹4 lakh is the contestable listing fee that needs JBP audit, ₹5 lakh is the BTL claim that needs execution-evidence audit, and the remainder is Section 52 TCS recoverable through the GSTR-3B credit cycle plus the ordinary fill-rate, scheme and RTV lines. The board-ready net realisation per ₹100 of MRP through the Mumbai Instamart cluster, after all deductions but before Section 52 TCS recovery, sits around ₹94.4 — and the recovery of the TCS in the next cycle pushes the net realisation back to roughly ₹94.9.

The reconciliation discipline that produces this view — per dark-store, per deduction bucket, per Section 52 TCS line — is the difference between a controller who can answer the audit committee in two slides and a controller who is rebuilding the dark-store-level trail in mid-November under audit pressure.

Detection: per-dark-store reconciliation, Instamart settlement file ingestion, BTL claim audit

The detection layer for a Swiggy Instamart FMCG cycle runs three parallel disciplines. None of them works if the reconciliation aggregates to the brand-GSTIN level rather than per dark-store.

Per-dark-store reconciliation as the base discipline

The Mumbai cluster decomposes into Powai, Andheri West, Lower Parel, Bandra, Vile Parle and Mulund — six dark-stores with six different deduction profiles. Each dark-store’s invoice cluster lands separately in the settlement file with its own gross, its own seven-bucket deductions and its own net. The reconciliation matches each dark-store’s settlement cluster back to the brand’s SAP or Oracle invoice ledger at the dark-store-GSTIN-tagged line level. Listing fees, fill-rate penalties and scheme reimbursements are reconciled per dark-store. The variance pack handed to the modern-trade controller breaks down per dark-store rather than as an Instamart aggregate. The same discipline applies to the Bangalore, Delhi and Pune dense clusters where the brand runs material volume; smaller cities aggregate at the city-cluster level but the dense-network cities reconcile per dark-store.

Instamart settlement file ingestion with seven-bucket decomposition

The Instamart settlement file format places fill-rate penalties in an annexure rather than the main settlement, places BTL claim invoices separately from product-sales settlement (the BTL invoice arrives as a distinct 18 percent GST invoice from Swiggy’s media commercial entity), and aggregates listing fees per dark-store per cycle. The ingestion parser decomposes every settlement file into the seven canonical buckets — item-level margin, listing fee per dark-store per SKU, BTL marketing claim (with separate ITC claim on the 18 percent GST line), scheme reimbursement classified by Section 15(2) treatment, fill-rate and QC penalties per dark-store, return-to-vendor credit notes, and Section 52 TCS at the 0.5 percent notified rate. Each bucket lands in its own GL ledger line. The Section 52 TCS line is matched to the Swiggy GSTR-8 line at the brand’s GSTIN and to the GSTR-2A TCS credit line.

BTL claim audit against JBP and execution evidence

The BTL marketing claim audit is the highest-value layer of the discipline because the contestable amount is concentrated. A ₹5 lakh BTL claim on a Mumbai cluster cycle is around 2.8 percent of the gross invoice value — material at scale and recoverable in full if the audit holds. The audit runs in three steps. First, the brand’s modern-trade and quick-commerce team reconciles each BTL claim against the JBP plan — campaign code, dark-store group, dates of execution, contracted media value, agreed deliverables (banner placement, push-notification slot, dark-store shelf prominence). Second, the brand requests campaign execution evidence — banner screenshots dated within the campaign window, push-notification analytics per dark-store cluster, dark-store shelf photos for the shelf-prominence element of the agreement. Third, the BTL invoice carries 18 percent GST that the brand claims back as ITC against the marketing GL, separately from the product-sales settlement. Mis-tagging the BTL deduction as a generic Instamart settlement loss destroys both the marketing-GL visibility and the recoverable 18 percent GST ITC — roughly ₹76,000 on a ₹5 lakh BTL claim. The discipline of routing the BTL invoice to the marketing GL with its own ITC line is the recovery mechanism.

How the Section 52 three-way tie closes on a Swiggy Instamart cycle

The Section 52 TCS audit trail is the regulatory anchor for the Instamart reconciliation. It runs across three documents on a monthly cadence.

The settlement file from Swiggy Instamart carries an explicit Section 52 TCS line per dark-store cluster — the rupee value Swiggy has withheld at the 0.5 percent notified rate on the net value of taxable supplies dark-store by dark-store. For the Haldiram-scale Mumbai cluster example, the line aggregates to roughly ₹90,000 across the six dark-stores in the cycle. This sits inside the seven-bucket deduction taxonomy and feeds the platform’s payment advice net.

Swiggy as the ECO files GSTR-8 by the 10th of the following month, reporting TCS collected at the supplier GSTIN level. The brand can extract its TCS line from Swiggy’s GSTR-8 (visible through the brand’s GSTR-2A TCS credit table). The aggregate of the Mumbai cluster’s TCS line on the settlement file should equal the GSTR-8 line at the brand’s Mumbai GSTIN for the cycle’s reporting month, allowing for the late-month timing variance discussed below.

The GSTR-2A TCS credit table at the brand’s GSTIN shows the same TCS rupee value as available to claim in the electronic cash ledger via the next GSTR-3B. The brand claims, the cash ledger increases, and the TCS is now usable against future GST liability.

The three-way tie — settlement file TCS line equals Swiggy GSTR-8 line equals brand GSTR-2A TCS credit — is the audit-ready posture. Variance handling runs by category. Timing variances — a late-September invoice straddling the 10th of October cut-off and appearing in October’s GSTR-8 instead of September’s — are recorded as one-month timing items and aged out the next cycle. Rupee-value variances feed back to Swiggy’s reconciliation manager for resolution; persistent variance over 60 days triggers a manual review and a written escalation through the JBP commercial channel. The reconciliation register that tracks these per dark-store is the discipline that closes the regulatory exposure cleanly.

How the 22 September 2025 GST 2.0 cut-over lands on a Mumbai Instamart cluster

The 22 September 2025 GST 2.0 rate rationalisation — CBIC Notifications 09/2025 to 16/2025 – Central Tax (Rate) — moved biscuits (HSN 1905), chocolates, soaps, shampoos, toothpaste and most metal kitchenware to the 5 percent slab from that date. Namkeen and savoury snack HSN under heading 2106 must be re-tested cycle by cycle against the brand’s HSN master because the slab moves were category-specific and some namkeen segments saw rate changes that others did not.

For the Haldiram-scale Mumbai cluster cycle that straddled 22 September 2025, the rate-by-date table on the brand’s invoice template had to switch on that date. Dispatches on or before 21 September 2025 to the Mumbai dark-stores carry the pre-cut-over rate per the brand’s HSN master; dispatches on or after 22 September carry the new 5 percent for the affected HSN list. The settlement file from Instamart for September will reflect both rates in the same monthly cycle, and Section 52 TCS at 0.5 percent is computed on the net taxable value at the date-appropriate rate.

Any post-supply credit note issued in October against a pre-22 September invoice must carry the original rate, not the new 5 percent. The Section 34 credit-note linkage goes back to the original supply date. Mis-applying the new 5 percent rate on a credit note against an 18 percent or 12 percent invoice creates a GST liability gap that the audit will surface — and on a per-dark-store decomposed cycle, the breakdown of where the rate mismatch occurred is visible by dark-store cluster.

Brands that did not pre-configure the rate-by-date table on 22 September 2025 are now correcting the September and October GSTR-1 cycles in the December amendment window. Reference the CBIC GST portal for the Section 9(5) notification list, Circular 167/23/2021-GST on the deemed-supplier scope, Notification 15/2024-CT on the Section 52 0.5 percent rate, and Notifications 09 to 16 of 2025-CTR on the 22 September rate rationalisation.

Where the leakage shows up in a typical Mumbai Instamart cluster close

Three layers absorb the most contestable leakage in a Swiggy Instamart Mumbai cluster monthly close, and each surfaces only when the per-dark-store decomposition is in place.

First, unrecovered listing fees. A ₹4 lakh listing-fee debit on a ₹1.8 crore Mumbai cluster cycle is around 2.2 percent of the gross. When the per-dark-store JBP audit reconciles the listing fee against the agreed schedule per dark-store, mis-priced fees at specific dark-stores typically surface — a category manager applying a higher fee than the JBP standard at one dark-store, an aggregate fee billed against a SKU not actually listed at that dark-store, a fee debited on a discontinued SKU still showing in the master. A two-dark-store sample at a mid-tier brand often shows 6 to 12 percent of dark-store listing fees exceed the JBP standard — recoverable, but only with the decomposition.

Second, mis-tagged BTL deductions and the recoverable ITC. A ₹5 lakh BTL claim on a Mumbai cluster cycle carries roughly ₹76,000 of recoverable GST ITC sitting on the 18 percent invoice. When the BTL claim is netted against product-sales settlement and the invoice is not routed separately to the marketing GL, the ITC is never claimed. The brand pays twice — once economically for the campaign, once for the lost ITC. The discipline of routing the BTL invoice to the marketing GL with its own ITC line recovers this loss in full.

Third, the Section 9(5) versus Section 52 classification error. A brand that misclassifies its Mumbai Instamart cluster supply under Section 9(5) — pulling it into the wrong cell of the GSTR-1 outward supply report or, worse, not reporting it at the brand’s GSTIN at all — loses the Section 52 TCS credit and faces a Section 73 or 74 notice when the audit reconstructs the trail from Swiggy’s GSTR-8 filing. Catching this in pre-filing reconciliation — not in audit defence — is the discipline that closes the regulatory exposure cleanly.

The audit-ready posture at quarter-end is achieved when the brand can walk into the November statutory audit with a per-dark-store Instamart monthly reconciliation pack: gross invoice per dark-store, seven-bucket deduction decomposition with named-dark-store breaks, BTL claim audit against JBP and execution evidence, net bank receipt tied to Swiggy’s payment advice cluster, Section 52 TCS three-way tie (settlement file ↔ Swiggy GSTR-8 ↔ brand GSTR-2A), GSTR-1 outward-supply tagging audit trail, BTL invoice register with 18 percent ITC posture, scheme reimbursement ageing buckets, GST 2.0 rate-by-date audit log for the 22 September 2025 cut-over per HSN, and a leakage summary surfacing unrecovered listing fees, mis-tagged BTL deductions, and any Section 9(5) versus Section 52 treatment error before it reaches the GSTR-3B cycle close.

Continue reading

The cross-platform comparative view of Swiggy Instamart alongside Blinkit and Zepto — including the consolidated three-platform reconciliation discipline at the brand-aggregate level — is covered in quick commerce FMCG settlement reconciliation, the cornerstone of the quick commerce sub-theme. The Blinkit-specific dark-store reconciliation pattern is contrasted in Blinkit FMCG settlement reconciliation. For the cross-cluster bridge into the merchant-fees universe — where Section 52 TCS treatment, direct-buy vs consignment commercial models, and ad-spend deduction taxonomy are contrasted across D2C marketplace flows — see quick commerce platform reconciliation across direct-buy, consignment and ad-spend and the merchant-fees cluster hub. The full FMCG reconciliation surface — TPM, modern trade, general trade distributor pyramid, quick commerce, Section 15(2) trade-discount valuation, PLISFPI claim filing — is mapped on the FMCG reconciliation cluster hub.