How to Calculate FMCG Distributor Claims (With Worked Examples)
How to calculate FMCG distributor claims — scheme slabs, secondary schemes, damage, price drops and display claims, with worked examples in ₹.
Every FMCG distributor claim is, at its core, a small formula: a base, a rate or unit value, and the evidence that proves both. This guide works through the math for the five common claim types — with illustrative ₹ examples — then lists the calculation errors that cause most disputes. For the process around the math, see distributor claims management; this article owns the arithmetic.
All numbers below are illustrative, not benchmarks. Your scheme circular and agreement always govern.
Scheme / rebate claims: slabs on the net base
A slab scheme pays a rate that depends on qualifying purchases for the period. The base is net: gross qualifying purchases minus returns.
Illustrative example. A quarterly scheme pays 1% below ₹25,00,000, 1.5% from ₹25,00,000, and 2% from ₹50,00,000 — the achieved slab's rate applying to the whole base. A distributor buys ₹54,00,000 gross but returns ₹6,00,000:
| Step | Value |
|---|---|
| Gross qualifying purchases | ₹54,00,000 |
| Less: returns | ₹6,00,000 |
| Net base | ₹48,00,000 |
| Slab achieved | 1.5% (below the ₹50,00,000 boundary) |
| Claim | 1.5% × ₹48,00,000 = ₹72,000 |
Calculated on gross, the same distributor would claim 2% × ₹54,00,000 = ₹1,08,000 — a ₹36,000 over-claim from one missed subtraction. Whether the rate applies to the whole base or per tier is a scheme-design choice; the structures are in volume rebates.
Pro-rating a mid-period join. If a distributor is onboarded partway through the period, pro-rate the slab boundaries, not the rate. Illustration: a 2% slab sits at ₹45,00,000 for the quarter; a distributor joins with two of three months left, so the boundary pro-rates to ₹30,00,000. Net purchases of ₹32,00,000 clear it: claim = 2% × ₹32,00,000 = ₹64,000. Unprorated, the same distributor would miss the slab entirely.
Secondary scheme claims: computed from secondary sales
Primary schemes reward what the distributor buys; secondary schemes reward what the distributor sells to retailers — so the base is secondary sales data, not purchase invoices.
Illustrative example. A scheme pays ₹20 per case on secondary sales of a brand during the month. The distributor's DMS shows 9,600 cases billed to retailers and 400 cases returned by them: net 9,200 cases × ₹20 = ₹1,84,000.
Evidence is the hard part: a retailer-wise secondary sales report for the exact scheme window, net of retailer returns, plus the scheme circular. Without secondary data the brand cannot validate the claim — only trust it. The full settlement mechanics are in secondary scheme settlement.
Damage and expiry claims: valuation basis × verified quantity
The formula is one multiplication; the disputes are all in the two inputs.
Valuation basis — the agreement should fix one of:
| Basis | What it means |
|---|---|
| Invoice price | The price the distributor was billed |
| Landed cost | Invoice price plus freight/handling to the distributor |
| Agreed % | A fixed percentage of invoice price (e.g. 80%) |
Illustrative example. 240 units expire; invoice price ₹150 per unit; the agreement pays 80% of invoice: 240 × ₹150 × 80% = ₹28,800.
Quantity verification is the other input: batch and expiry records, photos or physical verification, and — where stock is returned rather than destroyed — the return document. Expiry returns in FMCG often route through a buyback arrangement; see buyback in FMCG.
Price-drop / stock compensation: units in stock × price difference
When a price is cut, the distributor holds stock bought at the old price. The claim is: verified units in stock on the price-change date × per-unit price difference.
Illustrative example. A price cut of ₹12 per unit takes effect on the 1st; the distributor's verified stock on hand that morning is 15,000 units: 15,000 × ₹12 = ₹1,80,000.
The arithmetic is trivial; the evidence — a stock count as of the exact change date — is everything. One interaction to watch: compensated stock often shouldn't also count toward the rebate base, or the same units pay twice. That sequencing problem is worked through in how stock compensation interacts with the rebate process.
Display and visibility claims: proof of performance
Display claims pay for shelf space, visibility windows or paid displays — a fixed amount per outlet per period, payable only against proof of performance.
Illustrative example. A brand pays ₹8,000 per outlet per month for an end-cap display across 12 agreed outlets. Photo audit passes 11 of them: 11 × ₹8,000 = ₹88,000 — not 12 × ₹8,000.
Evidence: the agreed outlet list, dated (ideally geo-tagged) photos per outlet, and the activity window. There is no formula rescue for a missing photo.
Common calculation errors
| Error | What goes wrong |
|---|---|
| Gross instead of net base | Returns not subtracted; scheme over-claims (the ₹36,000 gap above) |
| Missed late returns | Returns posted after period-close never reduce the base |
| Wrong slab boundary | Whole-base rate applied when the scheme is per-tier (or vice versa), or an unprorated boundary for a mid-period join |
| Double-counting | The same units claimed under a scheme and compensated as damage/price-drop |
| Stale price masters | Old unit prices used for damage or price-drop valuation |
Each of these is exactly the kind of silent gap that turns into disputed credit notes downstream — the flow they disrupt is in the claim process explained.
Pre-submission checklist
Before a claim leaves the building:
- Base reconciled — gross purchases/sales minus all returns for the window, including late ones.
- Right rate, right slab — rate matches the circular; boundary check done on the net base; mid-period joins pro-rated.
- Valuation basis stated — invoice price / landed cost / agreed %, named in the claim, matching the agreement.
- Quantity evidenced — counts, batches, photos or DMS reports attached, dated inside the scheme window.
- No overlap — units claimed here aren't also sitting in another claim.
- Period and deadline — the claim cites the exact scheme window and lands before the submission cut-off.
The submission mechanics themselves are covered in how to submit a rebate claim request.
How automation removes the arithmetic risk
Every formula on this page is simple; the risk is doing hundreds of them per month, per distributor, per scheme, in spreadsheets. Rebate management software computes the base net of returns automatically, applies the slab logic from the scheme master rather than a remembered rule, pro-rates mid-period joins, blocks double-counting across claim types, and attaches the evidence to the claim record. The capability list for FMCG specifically is in rebate software features for FMCG, and how to evaluate vendors is in the distributor claims software buyer's guide.
ClaimDS does this math natively for Indian FMCG channels — slab schemes, secondary settlement, damage, price protection and display claims in one ledger, settled by GST-compliant credit notes, priced for the mid-market.
GST note: Distributor claims settle via credit notes, and the type of credit note affects taxable value and input tax credit — see financial vs. tax credit notes. This is general information, not tax advice.
Frequently asked questions
How is a distributor scheme claim calculated?
Take qualifying purchases for the scheme period, subtract returns to get the net base, find which slab the net base lands in, and apply that slab's rate the way the scheme circular says — on the whole base or per tier. Mid-period joins pro-rate the slab boundaries, not the rate.
Should scheme claims be calculated on gross or net purchases?
On net purchases — gross qualifying purchases minus returns (and minus compensated stock, if the scheme excludes it). Calculating on gross is the single most common over-claim, because returns often land after the period the purchases were booked in.
How are damage and expiry claims valued?
At whatever valuation basis the agreement fixes — invoice price, landed cost, or an agreed percentage of invoice price — multiplied by the verified quantity. The formula is trivial; disputes come from an unstated basis or an unverified count.
How is a price-drop or stock compensation claim calculated?
Verified units in stock on the price-change date multiplied by the per-unit price difference. The arithmetic is one line; the work is evidencing the stock count as of that exact date.
What evidence does a secondary scheme claim need?
Secondary sales data — a retailer-wise report from the distributor's DMS or sales records for the scheme window, net of retailer returns — plus the scheme circular. Without secondary data the claim cannot be validated, only trusted.
See ClaimDS on your own claims data
A 30-minute walkthrough tailored to how your channel actually settles claims.
Related posts
Designing Claim and Rebate Approval Workflows That Don’t Bottleneck Settlement
How to design claim and rebate approval workflows — role-based routing, authority thresholds, SLAs, escalation — that keep settlement moving, not stuck.
Distributor Claims Software: Buyer's Guide for Indian Businesses
A vendor-neutral buyer's guide to distributor claims software for India — top features, benefits, how to choose for FMCG, where to buy, and an evaluation scorecard.
Distributor vs. Dealer vs. Super-Stockist: Who's Who in the Indian Channel
A plain-English glossary of the Indian route-to-market — manufacturer, C&F, super-stockist, distributor, wholesaler, dealer, retailer and stockist — and how goods and claims flow.