Blinkit (Zomato) FMCG Settlement Reconciliation

The FMCG controller at a Rajasthan-headquartered namkeen brand opens the September Blinkit settlement window and sees ₹35 lakh of gross dark-store invoicing settled on a T+7 cycle, with the seven-bucket deduction taxonomy — item-level margin, listing-fee debits, BOGO scheme reimbursement, fill-rate penalties, RTV credit notes, ad and slotting invoices, and Section 52 TCS at the 0.5 percent notified rate against a 1 percent statutory ceiling. Net bank credit lands at roughly ₹32.83 lakh. The audit committee will ask in November whether the Section 52 treatment is correct, whether any of the ₹35 lakh was wrongly tagged under Section 9(5), and whether the ₹17,500 of TCS credit landed in the electronic cash ledger. This is Blinkit FMCG settlement reconciliation at the per-SKU, per-dark-store level — the 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 Blinkit 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 temptation to read Section 9(5) as covering anything sold through an electronic commerce operator is strong, but the notification is narrow. It lists only four categories of services — all consumer-services, none goods. CBIC Circular 167/23/2021-GST is the settled position: Blinkit’s FMCG flow operates under the ordinary Section 9(1) regime, the brand or dark-store operator is supplier of record, Blinkit is the facilitator, and the platform collects TCS at 0.5 percent under Section 52, remits via monthly GSTR-8 by the tenth of the following month, and the brand claims the TCS credit in the electronic cash ledger via GSTR-3B against the GSTR-2A credit line.

The practical risk of getting this wrong on Blinkit is concrete. A brand that misclassifies its Blinkit 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 when the audit reconstructs the trail from Blinkit’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 Blinkit’s dark-store FMCG settlement actually flows

Blinkit’s operating model is dark-store-based 10-minute delivery, with inventory forward-positioned at dark stores in each metro and tier-1 catchment. The settlement chain starts with a purchase order from Blinkit’s commercial entity to the FMCG brand, carrying the agreed item-level margin off MRP, listing fees per SKU per pack size, and the joint business plan for trade marketing — particularly the BOGO and slab-discount cadence that drives festive volume.

The brand dispatches against the PO from its CFA depot to the Blinkit dark-store network, raises a tax invoice at the brand’s GSTIN, and the goods are received against goods-received-note (GRN) at the dark store. Blinkit’s payable team validates GRN against invoice, processes the invoice, applies the agreed deductions, withholds Section 52 TCS at the 0.5 percent notified rate, and credits the residual on the T+7 horizon. Settlement files arrive as CSV or XLS attachments to a payment advice email or as downloadable reports on the Blinkit vendor portal.

What makes the Blinkit cycle distinct from a modern-trade DMart or Reliance Smart cycle is the dark-store granularity. The same SKU — Bhujia 200g — is dispatched across multiple Blinkit dark stores in the city, each with its own GRN cycle, consumption pattern and ageing risk. Reconciliation runs not just per platform but per SKU per dark store. A brand that consolidates all Blinkit invoicing into a single platform-level receivable line loses visibility on which dark store carried near-expiry stock that triggered an RTV credit note, and which hosted the BOGO that drove the scheme reimbursement claim.

Worked example: Bikaji Bhujia 200g — ₹35 lakh monthly Blinkit dark-store invoice

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 Bikaji Foods International — Rajasthan-headquartered namkeen and sweets manufacturer, PLISFPI beneficiary #7 — running its core Bhujia 200g pack across Blinkit’s dark-store network in Delhi NCR, Mumbai, Bengaluru and Hyderabad. The September monthly invoice cycle on Blinkit lands at a representative ₹35 lakh of gross invoicing for the Bhujia 200g SKU across roughly 240 dark stores, blended at the agreed Blinkit margin off MRP. The controller closes the cycle in the first week of October.

The Blinkit settlement file decomposes the ₹35 lakh as follows. Item-level margin at approximately ₹1.75 lakh on the agreed 5 percent off-MRP blend. Listing-fee debit for the SKU’s premium-shelf placement at ₹50,000 for the cycle. Banner-ad and slotting invoices for the festive promotion total ₹40,000, carrying 18 percent GST that Bikaji claims back as ITC against marketing GL — kept separate from the product-sales line. BOGO scheme reimbursement against the festive Buy-One-Get-One campaign on Bhujia 200g, where Bikaji funded the free-of-charge replacement pack across the network, totals ₹2 lakh; Section 15(2) treatment is the post-supply discount with prior agreement and ITC reversal by Blinkit on the discount amount. Fill-rate and QC penalties for under-supply during Diwali peak add ₹15,000. Return-to-vendor credit notes against near-expiry stock from August dispatches at the Mumbai dark store come to ₹12,500.

The Section 52 TCS line is the regulatory headline. On the net taxable value of approximately ₹35 lakh, Blinkit withholds TCS at the notified 0.5 percent rate of ₹17,500 — split 0.25 percent CGST + 0.25 percent SGST for intra-state dark-store movement or 0.5 percent IGST for the inter-state legs. The TCS lands in Blinkit’s GSTR-8 filing for September and shows in Bikaji’s October GSTR-2A as a credit line, available via the next GSTR-3B cycle.

Net bank receipt: gross ₹35 lakh, less margin ₹1.75 lakh, less listing fee ₹50,000, less BOGO reimbursement ₹2 lakh, less fill-rate penalty ₹15,000, less RTV credit note ₹12,500, less Section 52 TCS ₹17,500. The ad invoice of ₹40,000 settles separately as a credit invoice — not netted against product-sales. The net product-settlement bank receipt on the T+7 cycle is approximately ₹32.83 lakh. The ₹17,500 TCS is recovered through GSTR-3B, pushing effective net realisation back to roughly ₹32.85 lakh. Per ₹100 of gross-MRP invoiced through Blinkit, after all deductions but before TCS recovery, net realisation sits around ₹93.80; after TCS recovery it rises to approximately ₹93.85.

The reconciliation discipline that produces this view per SKU per dark store per cycle is the difference between a controller answering the audit committee in one slide and one reconstructing the deduction trail in mid-November under audit pressure.

What the per-SKU Blinkit reconciliation discipline actually runs

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

Per-SKU dispatched-vs-invoiced reconciliation

The brand’s CFA dispatch register at the SKU and pack-size level (Bhujia 200g, Soan Papdi 250g, Aloo Bhujia 150g) is reconciled against the Blinkit GRN-confirmed quantity at each dark store. Variances — short-supply, GRN-rejected quantity, in-transit shrinkage — are tagged before invoice cut, so the invoice raised aligns to the GRN-confirmed quantity rather than dispatched. This stops downstream fill-rate penalties from compounding.

Settlement-file ingestion and seven-bucket decomposition

The Blinkit file is parsed into the seven canonical buckets — item-level margin, listing-fee debit, ad and slotting invoices (kept separate with 18 percent GST claimed as ITC), BOGO and scheme reimbursement classified by Section 15(2) treatment, fill-rate and QC penalties, return-to-vendor credit notes, and Section 52 TCS. Each bucket lands in its own GL line, not as a generic ECO settlement net. Blinkit’s file separates margin, listing fee and TCS into clearly named columns, which makes parsing cleaner than Zepto’s or Instamart’s formats.

BOGO scheme verification against the TPM accrual

Every BOGO reimbursement claim raised by Blinkit is verified against the brand’s trade-promotion-management accrual register. The scheme master holds the campaign window, per-SKU BOGO ratio, target dark-store coverage and the agreed Section 15(2) treatment. A Blinkit claim that exceeds the accrual triggers a scheme-master review. The accrual-versus-payout discipline is covered in depth in the trade promotion accrual vs payout reconciliation for Indian FMCG cornerstone.

Section 52 TCS three-way tie

Every Section 52 TCS line on the Blinkit settlement file is matched to Blinkit’s GSTR-8 GSTIN-by-GSTIN line and to the brand’s GSTR-2A credit line. Variances are aged 0-30, 31-60, 61-90 and 90-plus days from settlement date. Permanent variances over 60 days trigger a manual review with Blinkit’s reconciliation manager. The three-way tie closes the audit trail on the regulatory side; GSTR-8 cut-off timing variances are tracked separately so they are not recorded as permanent gaps.

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

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. For Bikaji, the core Bhujia and Soan Papdi SKUs continued at their pre-existing rate; for a Parle or Mondelez brand running biscuits or chocolates on Blinkit, the rate cut-over lands inside the September settlement file in three places.

First, the rate-by-date table on the brand’s invoice template must switch on 22 September 2025 — dispatches on or before 21 September carry the old rate, on or after 22 September carry the new 5 percent. Second, Section 52 TCS continues to be computed on net taxable value at the unchanged 0.5 percent notified rate; the absolute TCS rupee value falls at the same gross-MRP, and GSTR-3B recovery falls in proportion. Third, any post-supply credit note issued after 22 September 2025 against a pre-22 September invoice — typically RTV credit notes against August dispatches — must carry the original rate of the underlying invoice. The Section 34 credit note links back to the original supply date, not the issue date.

Where the leakage shows up in a typical Blinkit monthly close

Three areas absorb the most Blinkit leakage in mid-tier FMCG brands.

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

Second, mis-tagged ad-spend deductions. When a Blinkit banner-ad or slotting invoice (at 18 percent GST) is netted against product-sales and the 18 percent ITC is never claimed, the brand pays twice — once for the ad spend, once for the lost ITC. Routing ad-spend invoices to the marketing GL with their own ITC line recovers this. Blinkit’s file format keeps ad and product-sales distinct, cleaner than Zepto’s bundled format — but only if the parser respects the distinction.

Third, BOGO scheme reimbursement gaps. When the TPM accrual is not maintained at the campaign-SKU-dark-store level, the Blinkit BOGO claim cannot be verified line by line. Either the brand over-pays a claim that exceeded campaign scope, or under-recovers a claim the accrual register would have validated. A campaign accrual maintained at the right granularity, reconciled monthly against the Blinkit BOGO line, closes this gap.

Audit-ready posture is achieved when the brand walks into the November statutory audit with a per-platform monthly reconciliation pack: gross invoice per dark store per SKU, seven-bucket deduction decomposition, net bank receipt tied to the Blinkit payment advice on the T+7 horizon, Section 52 TCS three-way tie (settlement file ↔ GSTR-8 ↔ GSTR-2A), GSTR-1 tagging audit trail, BOGO register validated against TPM accrual, ad-spend invoice register with ITC posture, and a leakage summary. Reference the CBIC GST portal directly for Notification 15/2024-CT, Circular 167/23/2021-GST and the September 2025 GST 2.0 notifications when challenged.

Continue reading

The cross-platform view across Blinkit, Zepto and Instamart is covered in quick commerce FMCG settlement reconciliation in India — the canonical reference for the T+7 to T+14 cycle, Section 52 TCS and the seven-bucket deduction taxonomy across all three platforms. The Section 15(2) treatment of the BOGO replacement line — central to the Bikaji Bhujia worked example above — is taken 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.