Blog/Manufacturing

Dealer Scheme and Incentive Calculation Without Month-End Disputes

Write scheme rules that calculate cleanly from invoice data so dealer payouts are accurate, explainable and settled on time.

By Sagar Makker · 7 min read · October 2026
Industrial Factory
In short
Most scheme disputes start with ambiguous rules written in a circular, not with calculation errors.
Convert every scheme into a structured rule table before launch, then calculate from invoice lines only.
Share a dealer-wise statement before payout so disputes are raised early, not after credit notes go out.
The problem

This is for sales heads, commercial teams and accounts staff who run dealer schemes: quantity slabs, value targets, product-mix bonuses, early-payment discounts and tour incentives. When schemes are calculated in spreadsheets at month end, payouts are late, dealers question every number, and sales officers spend days defending figures instead of selling. This post shows how to define scheme rules so they can be calculated reliably, how to share statements, and how to settle payouts with fewer arguments.

A scheme circular says dealers who buy above a target in the quarter get an extra discount on the full quantity. It does not say whether returns are netted, whether the target is on billed or dispatched quantity, or which SKUs count. At quarter end, the commercial team builds a spreadsheet from ERP exports, makes judgement calls, and sends the numbers. Dealers compare against their own purchase records and the disputes begin.

Several schemes often run at once and overlap. One dealer qualifies for a slab, a product-mix bonus and a cash discount, and nobody is sure whether they stack. Corrections are made by hand, credit notes are issued late, and some dealers are overpaid while others wait. Trust drops, and the next scheme gets a weaker response because dealers doubt they will be paid correctly.

Why it happens
01Scheme circulars written in prose, leaving netting, eligibility and stacking undefined
02Calculation done in personal spreadsheets from ERP exports, rebuilt every period
03Sales returns, cancellations and rate differences not linked back to the original scheme
04No dealer-facing statement, so disputes surface only after credit notes are issued
05Scheme approval and payout steps owned by different teams with no shared record
How to fix it
1
Turn each scheme into a rule table
The commercial team writes every scheme as fields: period, eligible SKUs, basis (billed, dispatched or paid), slabs, returns treatment, stacking with other schemes and payout mode. Sales head signs off before the circular goes out.
2
Calculate from invoice lines only
Accounts runs calculations directly on invoice and credit note lines from the ERP, not on summary reports. Each payout line should trace back to specific invoices, so anyone can check how a figure was reached.
3
Handle returns and corrections explicitly
Define how sales returns, cancelled invoices and rate differences reduce scheme value, and in which period. The commercial team applies the same rule for every dealer and records any exception with approval.
4
Share a provisional dealer statement
Before payout, sales operations sends each dealer a statement showing qualifying invoices, slab reached and amount due. Give a dispute window you define, such as seven days, and log every query against the statement.
5
Settle through credit notes with approval
After the dispute window, accounts issues credit notes or payouts as per the approved statement. Check GST treatment of scheme credit notes with your tax advisor. Finance controller approves the final batch.
Worked example
A paint maker with overlapping quarterly schemes

A decorative paints manufacturer ran a volume slab, a premium-range bonus and a cash discount in the same quarter. Before, the commercial team spent the first weeks of each new quarter reconciling spreadsheets, and many dealers disputed their payouts because returns were treated inconsistently. The company rewrote each scheme as a rule table with netting and stacking spelled out, calculated from invoice lines, and sent provisional statements with a fixed dispute window. After the change, most queries were resolved before credit notes were raised, payouts went out sooner, and sales officers stopped spending their month start defending numbers.

Common mistakes
×
Launching a scheme before rules are complete
Gaps in the circular become disputes later. Fill in basis, returns treatment and stacking before launch, even if it delays the announcement by a day.
×
Paying first and reconciling later
Overpayments are hard to recover from dealers. Share a provisional statement, close the dispute window, then issue credit notes once.
×
Letting sales officers promise custom terms
Verbal side deals break the calculation and create unfairness. Record any dealer-specific term as an approved exception in the rule table.
Where an AI agent helps
Input
Scheme rule tables, ERP invoice and credit note lines, dealer master
Agent does
Calculates scheme eligibility per dealer, flags edge cases and drafts dealer statements
Human gate
Commercial head approves statements; finance approves credit note batch
Outcome
Dealer-wise scheme statements and a credit note register ready for posting
Checklist
Rewrite active schemes as structured rule tables
Define returns and cancellation treatment per scheme
State clearly whether schemes stack or not
Calculate payouts from invoice lines, not summaries
Send provisional statements with a fixed dispute window
Record every exception with approver and reason
What to measure
Days from period close to scheme payout
Dealer disputes raised per scheme
Credit notes reversed or corrected
Share of payouts traced to invoice lines
Questions
How do we stop dealers disputing scheme payouts?

Remove ambiguity before launch and share numbers before paying. A rule table that defines basis, eligible SKUs, returns and stacking, plus a provisional statement that lists qualifying invoices, lets dealers check their own records and raise issues early.

Should schemes be calculated on billed, dispatched or paid quantity?

Any can work, but choose one per scheme and say so in writing. Billed is simplest to calculate; paid quantity encourages collections but delays payout. Whatever you choose, apply it consistently and explain it in the circular.

How should sales returns affect a scheme already earned?

Define a rule upfront, such as netting returns within the same scheme period and adjusting later returns in the next statement. The key is consistency across dealers and a clear record of which invoices were reduced.

What is the GST treatment of scheme discounts given through credit notes?

It depends on how the discount is agreed and documented, and whether it is linked to specific invoices. Treatment has been subject to clarifications over time, so check the current rules with your tax advisor before finalising the credit note process.

Keep reading
All posts →
Industrial MachineManufacturing
Distributor Claims Settlement: Clear the Backlog and Keep Trust
7 min readRead →
Industrial MachineManufacturing
Dealer Onboarding for Manufacturers: From Application to First Order
6 min readRead →
Engine MachineManufacturing
Dealer Credit Limit Holds: Release Good Orders Faster, Safely
6 min readRead →
Next step

Want this fixed in your business?

Send the workflow. You get a scope and a fixed price within two working days — or a straight answer that it isn't a fit.

Secure by default · find → fix → verify · authorised scope only
Send a brief →enquiry@xdqlabs.com