How to Settle FMCG Distributor Claims

11 Jul 2026 · ClaimDS Team · 12 min read

The end-to-end process to settle FMCG distributor claims — evidence, validation against scheme rules, approval and settlement by credit note.

ClaimDS article banner: How to Settle FMCG Distributor Claims

Settling an FMCG distributor claim runs through six stages: the scheme circular is published and communicated, the distributor accrues and files the claim with evidence, the field or ASM verifies it, finance validates it against the scheme rules and base data, an approver signs off per the delegation-of-authority matrix, and the claim is settled — usually by credit note — and reconciled. Two stages cause most of the delay: gathering complete evidence, and validating each claim line against the scheme circular. The rest moves fast once those two are clean.

All ₹ figures below are illustrative, not benchmarks. Your scheme circular and agreement always govern. This guide owns the end-to-end process; for the arithmetic of each claim type, see how to calculate FMCG distributor claims, and for the wider channel picture, the pillar on channel claims and rebates in Indian FMCG.

The six-stage FMCG claim settlement process

Every distributor claim, whatever its type, moves through the same six stages. Getting the sequence right — and knowing which two stages absorb most of the time — is what turns a backlog into a predictable pipeline. The generic version of this lifecycle is set out in the claim process explained; below is the FMCG-specific shape.

Stage 1 — Scheme circular published and communicated

Everything downstream traces back to the scheme circular: the document that fixes what the scheme rewards, the qualifying products and period, the slab or per-unit rate, any caps, and the claim window. If the circular is ambiguous — an unstated base, a rate that could apply per-tier or whole-volume — every claim under it inherits that ambiguity and disputes multiply at validation. A clean circular names the base (primary purchases or secondary offtake), states whether returns net off, and fixes the evidence a claim must carry. It also needs to actually reach the field and the distributor, not sit in an inbox. The menu of scheme designs a circular can describe is mapped in types of trade schemes in India and the FMCG-specific set in FMCG trade schemes explained. This stage costs little time but sets the ceiling on how cleanly the other five can run.

Stage 2 — Distributor accrues and files the claim with evidence

The distributor computes the claim against the circular and files it with supporting evidence — the primary invoices, the secondary offtake statement where the scheme rewards sell-through, photo proof for display or damage, and retailer-level detail where required. This is the first of the two slow stages: evidence gathering is where claims sit for days, because the distributor is assembling records after the fact. Filing inside the claim window matters as much as the amount — a correct claim filed late is still rejected. Whether the base is primary or secondary shapes what evidence is needed; the distinction is unpacked in primary, secondary and tertiary sales, and the mechanics of sell-through claims in secondary scheme settlement. A claim filed complete on the first pass is the single biggest lever on total settlement time. In ClaimDS, distributors and internal teams file claims against the specific scheme and attach the base data and proof in one place.  The step-by-step is documented in submit a sales claim.

Stage 3 — Field / ASM verification

Before finance sees the claim, the field — the ASM or sales officer closest to the market — verifies the claims that need eyes on the ground: that the display existed, the damage was genuine, the offtake looks real for that retailer set. This is the human check that base data alone cannot give, and it is where scheme leakage is caught early rather than clawed back later. The trade-off is speed: routing every claim through field verification slows the pipeline, so most companies verify by exception — value threshold, claim type, or a risk flag — rather than universally. Damage, expiry and returns claims almost always need it, because they hinge on physical stock; the treatment of those is in credit notes for expired and damaged goods returns and returns, reversals and cancellations in channel claims. Clear ownership at this stage keeps it from becoming a bottleneck.

Stage 4 — Finance validation against scheme rules, base data and caps

This is the second slow stage, and the one that most determines whether settlement is defensible. Finance recomputes the claim from the base data rather than trusting the filed figure: does the amount match the circular's rate on the correct net base, is it within any cap, was it filed in the window, is it a duplicate of a claim already settled? Validation is arithmetic plus rule-checking, and it is exacting precisely because a wrong approval here becomes a real over-payment. ClaimDS validates each claim against its own scheme rules and base data, and flags mismatches, breached caps and likely duplicates for a reviewer rather than passing them silently.

ClaimDS claim validation screen, checking a claim against its scheme rules and base data. Validation: a claim checked against its scheme rules and base data.

The over-claims caught here are the ones that otherwise become deductions and disputes downstream — the mechanism behind revenue leakage in rebate programs and the discipline in deduction management best practices.

Ready to see validation run on your own scheme circulars? Book a demo and we will walk a live claim through the six stages on your data.

Stage 5 — Approval per the delegation-of-authority matrix

A validated claim still needs sign-off, and the delegation-of-authority matrix decides who signs. Approval routes by value: a field or finance manager clears smaller claims, while larger ones escalate to a controller or CFO. The matrix exists to keep small claims fast without letting a large one settle on one person's say-so — and to leave an audit trail of who approved what. Well-designed approval routing is the difference between a queue that clears daily and one that waits on a single overloaded approver; the patterns are in claim and rebate approval workflows and the finance-owner view in claims and deductions management for the CFO. ClaimDS routes each claim to the right approver by value and records every approval and rejection with a reason.  The workflow is documented in the claim approval workflow.

Stage 6 — Settlement by credit note or payout, and reconciliation

Once approved, the claim is settled — in the Indian channel, usually by credit note against the distributor's account rather than cash, because it offsets what the distributor owes and keeps the GST trail clean. The credit note must carry the right GST treatment; whether it is a financial or tax credit note changes the reporting, as set out in financial vs tax credit notes under GST and GST credit notes for rebates under Rule 53(1A). Settlement is not the end: the credit note has to be reconciled back against the accrual and, on the GST side, against the returns — the discipline in reconciling scheme credit notes to GSTR-2B/3B. ClaimDS settles approved claims by credit note and reconciles each one against its accrual and the partner account.  The how-to is in reconcile a claim to a credit note, and cancellations in rebate clawbacks and scheme cancellations.

The evidence standard

Most disputes are not disagreements about the scheme — they are disagreements about evidence. A claim that arrives with everything below can be validated on the first pass; a claim missing any row goes into the slow lane. The full documentation discipline is in the scheme settlement GST documentation playbook; this is the working checklist.

Evidence element	What a valid claim carries	Why it matters
Scheme circular reference	The specific circular and scheme the claim is filed under	Fixes the rate, base, caps and window the claim is judged against
Base data — primary	Primary purchase invoices for the qualifying period	The base for schemes that reward what the distributor buys
Base data — secondary	A secondary offtake / retailer-wise sales statement	The base for sell-through schemes; a claim without it can only be trusted, not validated
Photo proof	Dated images for display, visibility or damage claims	The only evidence that a physical condition existed
Retailer-level detail	Retailer-wise breakup where the scheme requires it	Lets finance test the claim against real outlets, not a lump sum
Claim-window compliance	Proof the claim was filed inside the circular's window	A correct claim filed late is still ineligible

The base data is the element that carries the most weight. Because validation recomputes the claim from primary invoices and secondary offtake rather than trusting the filed figure, an unstated or unmatched base is the single deepest cause of disputes. The mechanics of computing each claim from its base are in how to calculate FMCG distributor claims.

Why claims get rejected

Rejections cluster around eight recurring causes. Each is concrete, and each has a fix — which is why a rejected claim is usually recoverable rather than lost. This is also the highest-leverage list to fix upstream, because every avoided rejection is a claim that settles on the first pass.

#	Rejection reason	The fix
1	Claim exceeds the scheme rate or cap	Recompute at the circular's rate and cap; re-file the eligible amount
2	Base data does not match	Reconcile the claimed base to the actual primary/secondary records before re-filing
3	Claimed on gross, returns not netted off	Net returns from the base; gross claiming is the most common over-claim
4	Filed after the claim window closed	File inside the window; where a genuine delay exists, seek an agreed extension
5	Duplicate of a claim already settled	Check the claim register before filing; settle once per scheme line
6	Evidence missing (offtake, photo, retailer detail)	Attach the evidence the scheme requires before, not after, filing
7	Wrong scheme or product mapping	File against the correct circular and qualifying SKUs
8	GST treatment on the credit note is wrong	Apply the correct financial vs tax credit-note treatment for the case

Reasons 2 and 3 — base mismatches and un-netted returns — are the most frequent, and both trace back to how the base was assembled at filing. The returns question specifically is handled in returns, reversals and cancellations in channel claims, and the GST treatment in reason 8 in GST adjustments in channel settlements. Fixing rejections at the source is what turns a re-work queue into a clean pipeline — the argument in challenges of manual rebate processing.

Spreadsheets vs a claims system

Most FMCG teams start settling claims in spreadsheets, and for a handful of schemes a month that is genuinely fine. The problem is not the spreadsheet — it is what happens to it at scale, across many distributors, many schemes and many claim windows at once. The honest comparison is operational, not a promised return: below is what actually breaks.

Operational reality	In spreadsheets	In a claims system
Version control	Copies diverge across people and months; no single truth	One record per claim, one current state
Audit trail	Manual, reconstructable at best	Every action and approval recorded against the claim
Duplicate detection	Eye-balled; duplicates settle unnoticed	Flagged against the claim register at validation
Ageing visibility	Rebuilt by hand each time someone asks	Ageing and status visible across the channel at once
Reconciliation	Hand-matched credit note to accrual	Each settlement reconciled to its accrual
Validation against rules	Re-typed formulas, drift over time	Recomputed from base data against the scheme rules

Note what is not claimed here: no percentage saved, no ROI figure. The case for a system is that the failure modes above are structural to spreadsheets — version drift, no real audit trail, no duplicate detection, no live ageing, hand reconciliation — and they get worse, not better, as claim volume grows. ClaimDS holds one record per claim with its full history, shows claim ageing and status across the channel in one view, and reconciles each settlement to its accrual.

ClaimDS sales claims queue showing claims and their ageing and status across the channel. Claim ageing and status across the channel, in one view.

Whether that trade-off is worth it depends on your claim volume and how much the current backlog costs you — the buyer's-eye view is in distributor claims software: a buyer's guide, the settlement-specific angle in distributor claim settlement software, and how a system connects to your ERP in ERP integration for claims, rebate and TPM software. For the accounting behind the accruals a system reconciles against, see rebate accrual management, and for who in the channel files which claim, distributor vs dealer vs super-stockist. The GST side of every FMCG settlement is set out in the sibling on GST treatment of FMCG claims and schemes, and the operational discipline in distributor claims management.

Settling FMCG distributor claims well is not clever math — it is a clean circular, complete evidence, honest validation against the rules, clear approval authority, and a credit note that reconciles. Get the two slow stages right and the rest follows. To see the six-stage process running on your own scheme circulars and claim types, book a demo.

Frequently asked questions

How long does an FMCG claim take to settle?

There is no fixed number — it depends on how complete the evidence is and how cleanly validation runs. A claim filed with its scheme circular reference, matching base data and any required proof can move through verification, approval and credit note quickly. Missing evidence or a mismatch against the circular is what stretches settlement from days into weeks.

What documents are needed for a distributor claim?

A valid claim carries the scheme circular reference it is claimed under, base data (primary purchase invoices plus a secondary offtake statement where the scheme rewards sell-through), photo proof for display or damage claims, retailer-level detail where the scheme needs it, and proof it was filed inside the claim window. Missing any of these is the most common reason a claim stalls.

Why was my claim rejected?

The usual reasons are concrete: the claimed amount exceeds what the scheme circular allows, the base data does not match, the claim was filed after the window closed, it duplicates one already settled, evidence was missing, or returns were not netted off. Each has a fix — correct the base, attach the evidence, or re-file the eligible portion within the window.

Is a claim settled by credit note or payment?

In the Indian channel most distributor claims are settled by credit note against the partner's account rather than by cash payout, because the claim offsets what the distributor owes and keeps the GST trail clean. Some cases — an exited distributor, or an agreement that specifies a payout — settle by payment. The agreement and scheme circular decide which applies.

What is base data in a distributor claim?

Base data is the transactional record a claim is computed from: primary purchase invoices for schemes that reward what the distributor buys, and secondary offtake or retailer-wise sales statements for schemes that reward sell-through. Validation recomputes the claim from this base rather than trusting the claimed figure, which is why an unstated or unmatched base is the deepest cause of disputes.

Who approves an FMCG distributor claim?

Approval follows a delegation-of-authority matrix: finance validates every claim, then approval routes by value — a field or finance manager clears smaller claims, while larger ones escalate to a controller or CFO. The matrix keeps small claims fast and puts senior eyes on the ones that carry real money, with each approval recorded for audit.

See ClaimDS on your own claims data

A 30-minute walkthrough tailored to how your channel actually settles claims.

Book a demo