Quick Commerce FMCG Settlement Reconciliation in India

The FMCG controller at a mid-tier brand opens the September settlement window across three quick commerce platforms and sees ₹12 crore of gross invoicing run through Blinkit, Zepto and Swiggy Instamart in a single month, settled on T+7 to T+14 cycles with seven deduction categories per platform, Section 52 TCS withheld at the 0.5 percent notified rate against a 1 percent statutory ceiling, and a residual net bank credit of around ₹11.94 crore that must reconcile cleanly to the GSTR-1 outward supply, the GSTR-8 TCS line filed by each operator, the brand’s own GSTR-2A TCS credit, and the bank statement. The audit committee will ask in November whether the Section 52 treatment is correct, whether any of the ₹12 crore was wrongly tagged under Section 9(5), and whether the TCS credit landed in the electronic cash ledger. This is quick commerce FMCG settlement India at production scale, and the 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.

This single distinction is the most-litigated GST classification in quick commerce. The temptation to read Section 9(5) as covering “anything sold through an electronic commerce operator” is strong because the structural language of the section sounds general. It is not. The notification is the law, and the notification lists only four categories of services, all of them in the consumer-services space, none of them goods.

The CBIC’s settled position, anchored in Circular 167/23/2021-GST, is that quick commerce platforms supplying FMCG goods operate under the ordinary Section 9(1) regime. The brand owner (or, in the dark-store wholesale model where the platform’s commercial entity takes title, the dark-store operator) is the supplier of record. The platform is the facilitator. The platform 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 is concrete. A brand that misclassifies its Blinkit or Zepto FMCG supply as a Section 9(5) deemed-supplier flow does not file its GSTR-1 outward supply correctly, loses the TCS credit because no TCS would be applicable in a Section 9(5) flow, and faces a Section 73 or 74 notice on the under-declared outward supply at the brand’s GSTIN when the audit reconstructs the trail from the platform’s GSTR-8 filing. The correction window through GSTR-1 and GSTR-3B amendments is limited; persistent classification errors carry into the FY annual return.

How quick commerce FMCG settlement actually flows

The settlement chain starts with a PO from the platform’s commercial entity to the brand. The PO carries the agreed item-level margin off MRP for direct-buy SKUs (or the agreed consignment price for consignment SKUs, where the model is in use), the agreed listing fees per SKU, and the joint business plan for trade marketing.

The brand dispatches against the PO to the platform’s dark-store network, raises a tax invoice at the brand’s GSTIN, and the goods are received against GRN at the dark store. The platform’s payable team validates GRN against invoice (allowing some tolerance for fill-rate and short supply), processes the invoice, applies the agreed deductions, withholds Section 52 TCS at the 0.5 percent notified rate, and credits the residual to the brand’s bank account on the platform’s settlement horizon. Blinkit typically runs a T+7 cycle for established brand vendors; Zepto runs T+10 to T+12; Swiggy Instamart runs T+14 for direct-buy. Settlement files arrive as CSV or XLS attachments to a payment advice email, or as downloadable reports on the platform’s vendor portal.

The reconciliation problem is that the seven deduction buckets carry different GST and TDS treatments, the Section 52 TCS line is buried inside the file, and the bank-credit net of all deductions does not visually match either the gross invoice or any single line on the platform’s payment advice. Without a structured ingestion pipeline that decomposes each settlement file into its seven canonical buckets, the brand’s finance team posts the entire net to a generic ECO settlement clearing account and never recovers the visibility needed for GST or year-end audit.

Worked example: mid-tier FMCG brand, ₹12 crore monthly across three platforms

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 mid-tier FMCG brand running biscuits, soaps and personal-care SKUs across general trade, modern trade and quick commerce, with the quick commerce channel contributing roughly ₹12 crore of gross monthly invoicing — split approximately ₹4.8 crore on Blinkit, ₹3.9 crore on Zepto and ₹3.3 crore on Swiggy Instamart for a representative September month. The brand’s controller closes the monthly platform reconciliation in the first week of October.

The settlement file from each platform arrives with seven deduction lines. Across the three platforms, the consolidated deduction picture for the month works approximately as follows. Item-level margin lands at around ₹54 lakh on a blended 4.5 percent off-MRP across the three platforms. Listing fee for the new-launch biscuit variant runs at ₹6.5 lakh across all three platforms combined. Banner-ad and slotting invoices total ₹9 lakh, all carrying 18 percent GST that the brand claims back as ITC against the marketing GL. Scheme reimbursement and BOGO replacement claims raised by the platforms come to ₹7 lakh — these qualify under Section 15(2)(b) as invoice-recorded discounts for the BOGO line and under Section 15(2) post-supply discount with prior agreement for the slab-discount line. Fill-rate and QC penalties for short supply during the festive window add ₹2 lakh. Return-to-vendor credit notes against expiry-near stock from the August dispatches come to ₹3.5 lakh. The brand’s joint business plan with the platforms also produces a back-margin claim of around ₹4 lakh, settled by the brand owner against the platform’s invoice.

The Section 52 TCS line is the headline number for the audit trail. On the net taxable value of approximately ₹11.94 crore (gross of ₹12 crore less the value of return-to-vendor credit notes), Section 52 TCS deducted across the three platforms comes to roughly ₹6 lakh — the 0.5 percent notified rate applied platform-by-platform. The brand reconciles this against the three GSTR-8 filings — one per platform GSTIN — that land 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 across the three platforms — net of margin, listing fees, ad and slotting invoices, scheme reimbursements, fill-rate and QC penalties, return-to-vendor credit notes, back-margin claim and Section 52 TCS — works out to approximately ₹11.94 crore against gross invoicing of ₹12 crore. The 0.5 percent absolute headline gap is dominated by the deductions, with the Section 52 TCS at roughly ₹6 lakh recoverable through the GSTR-3B credit cycle. The board-ready net realisation per ₹100 of MRP, after all deductions but before Section 52 TCS recovery, sits around ₹95.95 for the channel — and the recovery of the TCS in the next cycle pushes the net realisation back to roughly ₹96.45.

The reconciliation discipline that produces this view is the difference between a controller who can answer the audit committee in one slide and a controller who is rebuilding the deduction trail in mid-November under audit pressure.

What the three-way Section 52 TCS tie looks like

The Section 52 TCS tie is the audit trail that closes the regulatory question. It runs across three documents on a monthly cadence.

First, the settlement file from each platform carries an explicit Section 52 TCS line — the rupee value the ECO has withheld at 0.5 percent on the net value of taxable supplies. This sits inside the seven-bucket deduction taxonomy and feeds directly into the platform’s payment advice net.

Second, the platform files GSTR-8 by the 10th of the following month, reporting TCS collected at the supplier GSTIN level. The brand can pull its TCS line from the platform’s GSTR-8 (visible to the brand through its GSTR-2A TCS credit table). The three platforms file three GSTR-8s; the brand reconciles three lines.

Third, 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 GSTR-8 line equals GSTR-2A TCS credit — is the audit-ready posture. Any variance between the three feeds back to the platform’s reconciliation manager for resolution. The most common variance source is timing — the platform files GSTR-8 on the 10th, but a late-month invoice may straddle the cut-off and appear in the wrong month’s filing. The brand’s reconciliation register must track these timing variances to avoid recording a permanent gap where only a one-month delay exists.

How the GST 2.0 rate cut-over of 22 September 2025 lands inside the cycle

The 22 September 2025 GST 2.0 rate rationalisation — CBIC Notifications 09/2025 to 16/2025 – Central Tax (Rate) — moved soaps, shampoos, toothpaste, biscuits (HSN 1905), chocolates and most metal kitchenware to the 5 percent slab from that date. For a mid-tier FMCG brand on quick commerce, this lands inside the settlement cycle in three concrete places that the reconciliation register must enforce.

First, the rate-by-date table on the brand’s invoice template must switch on 22 September 2025. Dispatches on or before 21 September 2025 carry the old rate (18 percent or 12 percent depending on the HSN); dispatches on or after 22 September carry the new 5 percent. The settlement file from the platform will reflect both rates in the same monthly cycle for any brand whose dispatch schedule straddled the cut-over.

Second, Section 52 TCS continues to be computed on the net value of taxable supplies. The 0.5 percent notified rate is unchanged. But because the net taxable value at 5 percent is lower than at 18 percent for the same gross-MRP, the absolute TCS rupee value falls — and the brand’s recovery through GSTR-3B falls in proportion. The TCS credit cycle still ties three-way (settlement file ↔ GSTR-8 ↔ GSTR-2A) but the rupee values are smaller.

Third, any post-supply credit note issued after 22 September 2025 against a pre-22 September invoice — typically the September RTV credit notes against August dispatches, or scheme reimbursements settled in October against September secondary sales — must carry the original rate of the underlying invoice. The Section 34 credit note links back to the original supply date, not the credit-note issue date. Mis-applying the new 5 percent rate to a credit note against an 18 percent invoice creates a GST liability gap that the audit will surface.

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. The reconciliation discipline that catches this before the GSTR-3B cycle close is the rate-by-date audit log on every outward supply tagged to the quick commerce channel.

How the detection and reconciliation discipline actually runs

The detection layer runs four parallel checks on every quick commerce settlement file the brand ingests.

Settlement-file ingestion and seven-bucket decomposition

Each platform’s file format is parsed independently. Blinkit’s settlement file separates margin, listing fee and TCS into clearly named columns; Zepto’s file aggregates margin and listing fee in a single deduction column unless the brand has negotiated the split; Instamart’s file places fill-rate penalties in an annexure rather than the main settlement. The parser per platform decomposes every gross invoice into the seven canonical buckets — item-level margin, listing fee, ad and slotting invoices, scheme reimbursement, fill-rate and QC penalties, return-to-vendor credit notes, and Section 52 TCS — regardless of how the platform’s file presents the data. Each bucket lands in its own GL ledger line, not as a generic ECO settlement net.

Section 52 TCS audit and the three-way tie

Every Section 52 TCS line on the settlement file is matched to the platform’s GSTR-8 GSTIN-by-GSTIN line and to the brand’s GSTR-2A TCS credit line. Variances are aged 0-30, 31-60, 61-90 and 90-plus days from the settlement date. Permanent variances over 60 days trigger a manual review with the platform’s reconciliation manager. The three-way tie closes the audit trail on the regulatory side.

GSTR-1 outward-supply tagging with TCS-collector reference

Every outward supply through a quick commerce platform is tagged in GSTR-1 with the TCS-collector GSTIN reference. This allows the brand’s GSTR-1 outward supply to be cross-validated against the platform’s GSTR-8 inward report. The aggregate of the brand’s quick commerce GSTR-1 outward supply at each platform GSTIN should match the platform’s GSTR-8 inward supply at the brand’s GSTIN — the GST authority reconciles this directly, so the brand should pre-reconcile it before each GSTR-1 cycle close.

Bank-receipt reconciliation against platform payment advice

The net bank receipt from each platform — net of all seven deduction buckets plus Section 52 TCS — is matched to the platform’s payment advice. Multiple invoices typically settle in a single bank transfer, so the matcher decomposes the bank receipt back to the platform’s payment advice cluster and then back to the individual invoices that comprise the cluster. Bank-receipt timing should sit within the T+7 to T+14 horizon; receipts past T+14 indicate a settlement dispute that needs platform-level escalation.

Where the leakage shows up in a typical three-platform monthly close

Three areas absorb the most quick commerce FMCG leakage in mid-tier brands, and each surfaces only when the reconciliation discipline is in place.

First, unrecovered listing fees and slotting-fee debits. When the platform’s payable team debits a listing fee or slotting fee against a previous cycle’s settlement but the brand’s finance team treats it as a generic ECO deduction, the visibility on what was actually charged for which SKU is lost. The brand cannot challenge mis-priced listing fees because it never decomposed them. A two-platform sample at a mid-tier brand often shows 6 to 12 percent of listing-fee debits exceed the joint-business-plan agreement — recoverable, but only with the decomposition.

Second, mis-tagged ad-spend deductions. When a banner-ad or slotting-fee invoice (at 18 percent GST) is netted against product-sales settlement and the GST 18 percent ITC is never claimed, the brand pays twice — once economically for the ad spend, once for the lost ITC. The reconciliation discipline that routes ad-spend invoices to the marketing GL with their own ITC line recovers this loss.

Third, Section 9(5) versus Section 52 treatment errors. As discussed in detail above, a brand that mis-classifies its FMCG quick commerce supply under Section 9(5) loses its TCS credit and faces a downstream Section 73 notice when the audit reconstructs the trail from the platform’s GSTR-8. Catching this in pre-filing reconciliation — not in audit defence — is the discipline that closes the regulatory exposure cleanly.

The audit-ready posture is achieved when the brand can walk into the November statutory audit with a per-platform monthly reconciliation pack: gross invoice, seven-bucket deduction decomposition with named-line breaks, net bank receipt tied to platform payment advice, Section 52 TCS three-way tie (settlement file ↔ GSTR-8 ↔ GSTR-2A), GSTR-1 outward-supply tagging audit trail, ad-spend invoice register with ITC posture, scheme reimbursement ageing buckets, GST 2.0 rate-by-date audit log, and a leakage summary. Reference the CBIC GST portal directly for the Section 52 Notification 15/2024-CT, Circular 167/23/2021-GST and the September 2025 GST 2.0 rate notifications when challenged.

Continue reading

The trade-promotion accrual layer behind the scheme reimbursement deduction is covered in trade promotion accrual vs payout reconciliation for Indian FMCG. The Section 15(2) treatment of the BOGO replacement line is worked end-to-end in BOGO scheme accounting under CGST Section 15(2) for FMCG. For the cross-cluster bridge into the merchant-fees universe — where Section 52 TCS treatment on direct-buy versus consignment versus marketplace flows is contrasted across the D2C operating model — 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.