TPM Debit Note Reversal for Rejected Distributor Claims in FMCG

A national FMCG brand running a Q1 noodles trade scheme across 800 distributors closes the May 2026 cycle with 12,400 distributor claims submitted on the TPM portal. After validation, 1,847 claims — roughly 15 percent — fail one or more scheme rules. The aggregate value of rejected claims is approximately ₹2.6 crore. Of that, ₹1.1 crore had already been paid out in April via Section 15(2) qualifying credit notes (the brand was running a fast-cycle credit-note workflow that month and several claims slipped through validation), ₹0.4 crore had been settled in cash with Section 393(1) Sl. 18 TDS deducted, and ₹1.1 crore was still under validation when the rejection landed and had never been settled. The brand’s controller now has three distinct reversal flows to execute — accrual-only reversal for ₹1.1 crore, debit-note plus accrual reversal for ₹1.1 crore, and TDS-correction plus accrual reversal for ₹0.4 crore — and the GSTR-1 filing for May closes in 18 days. This is TPM debit note reversal rejected distributor claims FMCG at production scale, and the discipline that separates a clean filing from a Section 73 notice risk is the per-claim reversal taxonomy.

Quick reference

What rejected-claim reversal actually looks like in Indian FMCG

The reversal flow begins on the TPM portal validation step. The distributor submits a claim against a published scheme — a slab discount on Maggi noodles secondary sales, a BOGO consumer-pack offer on Maggi cup noodles, a growth-over-base rebate on the broader Nestle India culinary portfolio. The portal validates the submission against the scheme master: was the secondary-sales certificate within the scheme period; do the retailer codes referenced match the DMS master; is the POS photographic evidence geo-tagged and within the activation window; did the distributor cross the slab threshold the claim asserts; is this a duplicate of a claim already paid in a prior cycle. Failures generate a rejection reason code on the portal and route the claim into the rejected-claim register. The rejection reason determines the downstream flow. A missing POS photo for a BTL claim is often recoverable — the field sales team can chase the distributor’s local team for the evidence and resubmit within the scheme’s resubmission window. A retailer code mismatch may be a data hygiene problem that resolves with a DMS master update. A claim outside the validity window is terminal — no resubmission possible, the rejection is final. A scheme-rule failure on slab threshold is also typically terminal unless the distributor produces additional evidence of secondary sales (a secondary-sales reconciliation note from the super-stockist or CFA pyramid often closes the gap). A duplicate submission is investigated for which of the two claims is the live entitlement. For terminal rejections, the brand executes the reversal. The first question the reversal engine asks of each rejected claim is: what is the current settlement state. There are four states, each with a different reversal flow. State 1 — Never settled. The claim was submitted, was under validation, and was rejected before any payout was issued. The brand has the trade-spend accrual on the books from Day 0 of the original secondary sale, but no credit note, no cash payout, no TDS deduction has happened. The reversal is a simple accrual journal — debit trade-spend liability, credit trade-spend P&L — in the rejection month. No GST instrument is required because there was no prior GST footprint. The distributor is notified of the rejection with the reason code; the GL liability shrinks; the field team manages the channel relationship. Most rejections in mature TPM operations sit in this state because the validation cycle is designed to catch issues before any payout. State 2 — Settled via Section 15(2) qualifying credit note. This is the case that requires the Section 34 debit note. The brand had issued a credit note in a prior cycle that reduced the dispatch invoice taxable value (and consequently the GST liability) under Section 15(2). When the underlying scheme entitlement is now invalid, the value reduction has to be unwound — the original invoice value gets restored, the original GST liability gets restored, and the distributor is the counterparty. The Section 34 debit note is the GST instrument. The debit note must reference the original credit note, must carry the rate of the original underlying invoice (not the rate at debit-note issue), and must be declared in GSTR-1 Table 9B of the issue month with the corresponding liability uptick in GSTR-3B of the same month. State 3 — Settled via cash with Section 393(1) Sl. 18 TDS. Where the original payout was structured as a commission settlement rather than a value-reducing credit note, the brand deducted TDS at 5% (legacy 194H, codes 1015 / 1016 in the new TRACES taxonomy) and reported it in the quarterly TDS return. The reversal recovers the gross commission from the distributor — typically netted against the next dispatch invoice — and triggers a TDS return correction for the affected quarter so the deductee distributor’s Form 26AS no longer carries the inflated credit. No GST debit note is required on this leg because the original cash commission was not a value-reducing credit note. State 4 — Settled via net-off against next dispatch invoice with no Section 34 instrument. Some brands net the claim amount directly off the next dispatch invoice (issuing a financial credit note that does not carry GST) when the scheme is non-qualifying under Section 15(2). The reversal is the inverse — a financial debit note that adds the amount back to the next dispatch. No GSTR-1 adjustment is required because no value reduction was booked under Section 15(2). The per-claim reversal classification — the four-state taxonomy — is the engine that drives both the accuracy of the reversal and the audit pack at year-end.

The Section 34 CGST overlay — when a debit note is mandatory

Section 34 of the CGST Act, 2017, governs the issue and treatment of credit and debit notes. The substance of the provision is that where the taxable value or the tax charged in a tax invoice is found to be less than the taxable value or the tax payable on the supply (typically discovered through a return of goods, an increase in the rate or value, or — for TPM reversal — the unwinding of a previously claimed post-supply discount), the supplier shall issue a debit note. The debit note must contain particulars prescribed in the rules (issue date, number, original invoice reference, supplier and recipient GSTIN, taxable value, tax charged, rate) and must be declared in the GSTR-1 of the month in which the debit note is issued. Two operational points flow from the statute and matter for TPM. First, the debit note is declared in the month of issue, not the month of original supply. This is the cleanest path through the GSTR-1 architecture — the brand does not amend the original supply month’s GSTR-1, it adds a fresh debit note line to the current month’s Table 9B. The recipient distributor’s GSTR-2B picks up the debit note in the same month, and they must mirror the adjustment in their GSTR-3B. Second, the Section 34 declaration window closes by 30 November following the financial year of the original supply (or before annual return filing, whichever is earlier). For TPM reversals discovered after that window — for instance, a Q4 FY 2024-25 scheme claim where the rejection lands in January 2026 — the debit-note route is closed and the brand must treat the recovery through a financial debit note that does not adjust GST, with the GST cost staying inside the trade-spend P&L. A subsidiary point worth flagging: the debit note must carry the rate of the original underlying invoice. If the original Maggi noodles dispatch was raised in August 2025 at 18% GST and the rejection-driven debit note is issued in December 2025 — after the 22 September 2025 GST 2.0 transition under Notifications 09 to 16/2025-CTR — the debit note carries 18% (the rate at the time of the original supply), not 5% (the post-22-September rate). The brand’s TPM engine must keep a rate-effective-date lookup per HSN per supply date so that debit notes issued after the rate change resolve to the right historical rate. This is the same straddle pattern that surfaces in retro credit notes at quarter-end, and the discipline applies symmetrically on the debit side.

A worked example — Nestle India Maggi noodles Q1 FY 2026-27 scheme rejection

A leading packaged-foods FMCG brand operates a national Q1 FY 2026-27 scheme on its instant-noodles flagship — slab discount (4 to 8 percent) on secondary sales above distributor volume tiers, BOGO consumer pack for the first 30 days of the cycle, and a BTL retailer activation reimbursement for in-store visibility shelves. The scheme runs 1 April to 30 June 2026. Claim submission window opens 1 May and closes 31 July. The brand’s TPM portal collects 12,400 claims across 800 distributors by the close of the window, aggregating ₹17.4 crore in gross claim value. Illustrative — figures are representative of the operating pattern in this category, not actual brand data. Cross-verify against your own DMS, TPM portal, and GL trade-spend account before action. Validation runs from 1 August to 31 August 2026. Outcomes: 10,553 claims (₹14.8 crore) pass and move to settlement; 1,847 claims (₹2.6 crore) fail validation across four reason codes.

Common reconciliation breakages

Five breakages drive the bulk of TPM debit-note reversal errors at year-end.

• Issuing a debit note without referencing the original credit note. The Section 34 debit note must carry the original credit-note number — without it, the rejection is impossible to defend at a Section 65 audit. The TPM engine’s credit-note generator must capture the original invoice references at issue time so that the reverse-mapping is mechanical when the rejection lands months later. Brands that lose this linkage end up issuing standalone debit notes that the GST department questions on Section 34 compliance.
• Carrying the issue-month rate on the debit note instead of the original invoice rate. Post-22-September 2025 GST 2.0 transition, this is the single most consequential mechanical error. A debit note issued in November 2025 for an August 2025 invoice on biscuits or chocolates must carry 18% (the pre-transition rate), not 5% — even though new dispatches in November are at 5%. The TPM engine’s rate-effective-date lookup must resolve to the supply date, not the issue date.
• Reversing the accrual but not issuing the Section 34 debit note when a credit note was issued in a prior cycle. This is the most damaging breakage from a GST risk perspective — the brand’s books show the trade-spend liability reduced, but the GST liability never gets restored. At the next Section 65 audit, the inspector identifies the credit notes still showing value reduction without matching debit-note reversal, and the department issues a Section 73/74 notice on the unpaid GST plus interest. Cleaning this up retroactively is costly and brand-damaging.
• Failing to align the TDS return correction when a cash-commission claim is reversed. The deductee distributor’s Form 26AS continues to show a TDS credit against income that no longer exists. Distributors discover the inflation only at year-end when filing their ITR, and the resulting dispute strains the channel relationship. The fix is a quarterly TDS return correction in the rejection quarter — a routine TRACES workflow — but it must be triggered automatically when the reversal engine flags a Bucket C state.
• Treating the debit note as a current-period supply rather than a Section 34 instrument. Some operations teams generate debit notes in the regular sales-invoice series and report them in Table 4 of GSTR-1 (B2B supplies) instead of Table 9B (credit and debit notes). The portal does not reject this, but it distorts the supply turnover and breaks the auditor’s ability to trace the reversal back to the original credit note. Maintain a separate debit-note series with clear referencing to the original credit-note number.

How a reconciliation platform handles this

A purpose-built reconciliation platform automates the four-state taxonomy: every claim carries a settlement-state flag from origination, every credit note issued on a Section 15(2) qualifying scheme carries the linkage back to the original invoices, every rejected claim is routed to the right reversal flow with the correct GST instrument generated against the original supply-date rate, and the GSTR-1 Table 9B export plus the TDS return correction trigger fire automatically in the rejection month. The dispute log captures reason codes with evidence references so the field sales team has a single source of truth when re-engaging distributors. The trade-spend GL liability cross-foots cleanly to the open-claim register plus the stale-claim provision, the GST liability stays aligned with the actual scheme entitlement universe, and the channel relationship preserves the audit trail that builds trust through the rejection cycle. For Indian FMCG brands closing a year with thousands of claims across hundreds of distributors, the structured discipline is the difference between a clean year-end close and a Section 73 notice waiting to land.

Cross-cluster bridges and where to read next

For brands also handling retro credit notes at quarter-end, the debit-note reversal is the mirror operation — the same scheme master, the same Section 34 architecture, opposite direction of the GST adjustment. The slab discount distributor claim recovery article covers the validation logic that produces the rejection signals upstream. For the channel-economics layer, the general trade distributor pyramid and DMS distributor management system reconciliation articles walk the secondary-sales feed that drives the accrual base in the first place. On the regulatory side, distributor commission TDS under Section 393(1) Sl. 18 covers the Bucket C reversal mechanics in depth. The FMCG reconciliation software India commercial pillar anchors the broader category. The five FAQs below address the operational questions Indian FMCG controllers ask most often when implementing structured TPM debit-note reversal discipline.

Terra Insight Reconciliation Infrastructure

Content authored by practitioners with experience at Amazon India, Intuit QuickBooks, and the Tata Group. Meet the team →

Published 27 June 2026

Domain expertise

TDS Reconciliation GST Input Credit Platform Settlements NACH Batch Matching Bank Reconciliation Form 26AS Matching ERP Integrations Enterprise Finance Ops

Reviewed by

NK

Navin Krishnan

Managing Director & Founder — Terra Insight

Ex Amazon India · Intuit QuickBooks · Tata nexarc

ISO 27001:2022 Patent Pending Incorporated 2024