Retailer and dealer incentive calculation, made easy
In most brands the incentive calculation starts after the month closes. Someone exports invoices from the ERP, matches them to thirty or forty live circulars in separate spreadsheets, argues with sales about which dealer was eligible, and sends finance a number two to three weeks later. None of that work is hard arithmetic. It is hard because the rules, the data and the approvals all live in different places.
Retailer and dealer incentive calculation becomes easy when four things are true: every scheme is stored as configuration rather than as a spreadsheet, every scheme reads the same invoice feed from the ERP, the calculation runs every day instead of once after month end, and every number carries the list of invoices behind it. Unotag's scheme engine does this for dealers, retailers, channel partners, franchisees and field teams on one set of rules, so a new circular is a configuration task and month-end close is an approval task, not a calculation project.
Why incentive calculation is slow today
Ask the person who runs the scheme spreadsheet where the days go. The answer is rarely the formulas. It is usually one of these:
- One spreadsheet per circular. Each scheme has its own workbook, its own copy of the invoice export and its own interpretation of who is eligible. Forty schemes means forty places where a dealer's purchases are counted, and they do not always agree.
- Eligibility is the slow part. The circular covers three districts, two dealer types and everyone in an attached list. Mapping that onto dealer codes, and remembering that one dealer has an old and a new code after a firm change, takes longer than the slab calculation.
- Returns arrive late. A credit note for a return dated in the scheme period arrives on the 9th of the next month. The payout has to be recalculated, and usually is not.
- Retailers have no invoice in your ERP. Retailer schemes are proved by the distributor's invoice, a photo of a bill or a product scan, so their calculation runs on a different data set from dealer schemes, often by a different team.
- Every number is argued. When a dealer or a sales officer disputes a figure, the only way to answer is to rebuild it by hand, so disputes are answered slowly or not at all.
Watch: the Unotag scheme calculator, in 86 seconds.
- 1CircularPasted as text; AI structures it, a person checks the preview
- 2ConfigurationOne of 16 scheme kinds, eligibility by rule, dealer codes clubbed
- 3One invoice feedSAP, Oracle, Microsoft Dynamics, Tally, Zoho, ERPNext, LOGIC, eZee or Excel
- 4Daily calculationEvery dealer, every live scheme, returns netted off
- 5Dealer sees itProgress, earnings and next target in app, WhatsApp or your app
- 6ApprovalHolds, caps and overrides recorded in a payout ledger
- 7SettlementCredit-note file to the ERP or UPI payout
Seven changes that make calculation routine
Schemes become configuration
Each circular is set up once by choosing a scheme kind (slab, growth over last year, milestone blocks, target, collection, cash discount, short window, new dealer, share of wallet, in-kind) and filling in its parameters. On Unotag a circular can be pasted in as text; AI structures it into a configuration with a preview that a person checks before saving. There is no workbook to copy next month.
One invoice feed for every scheme
Invoices, returns and credit notes come in once, through integration with SAP (all versions, including ECC, S/4HANA and Business One), Oracle, Microsoft Dynamics, Tally, Zoho, ERPNext, LOGIC ERP, eZee or any other ERP, or from a daily Excel upload, and every scheme reads the same lines. Two schemes can no longer count the same dealer's purchases differently.
Eligibility as rules, with clubbing
Coverage is defined by state, district, region, sales office, dealer type, price cluster or an uploaded list of dealer codes. Old and new codes of one dealer are clubbed so the dealer is calculated as one business.
Calculation every day, not once a month
Because the rules and the feed are fixed, the engine recalculates every dealer on every live scheme whenever new invoices land. Month end stops being the moment the number is discovered and becomes the moment it is approved.
The circular's own examples become tests
Most circulars print a worked example: a dealer who buys 1,200 bags earns this much. Before go-live each of those examples is run through the engine as an automated test. If the engine and the circular disagree, the configuration is wrong, and that is found before any dealer sees a number.
Returns and backdated schemes recalculate themselves
A return inside the period reduces the qualifying figure and the payout moves with it. A scheme announced on the 10th with effect from the 1st picks up the invoices already billed. Nobody has to remember to redo the sheet.
Every number carries its invoices
Each dealer's result on each scheme lists the invoices that counted and the ones that did not, with the reason. A dispute is answered by sending that list, and finance approves from the same view, with holds, caps and overrides recorded in a payout ledger.
Worked example: one dealer, three schemes, one feed
An illustrative example of what the engine does every day for every dealer. The dealer is in three live schemes in the same month, all reading the same invoices.
| Scheme | Rule (from the circular) | Dealer's position on the 20th | Earned so far | Next target |
|---|---|---|---|---|
| Quantity slab, retroactive | 800–1,199 bags ₹4/bag; 1,200+ bags ₹6/bag on all bags | 950 bags | ₹3,800 | 250 more bags lifts the rate to ₹6 on all 1,200: ₹7,200 |
| Growth over last year | 10% growth over same month last year earns 1% of value | Last year ₹9.0 lakh; this month ₹9.4 lakh | ₹0 (4.4% growth) | ₹0.5 lakh more reaches 10% growth: ₹9,900 |
| Cash discount | Paid within 7 days 2%, within 15 days 1% | Two invoices paid on day 5, one open on day 9 | ₹6,200 | Pay the open ₹1.8 lakh invoice by day 15 for ₹1,800 |
One combined next target: 250 more bags clears the slab and the growth gap together.
At this dealer's average price of about ₹990 a bag, the 250 extra bags add roughly ₹2.5 lakh of value, which also clears the ₹0.5 lakh gap on the growth scheme. That combined next target, one purchase figure that moves two schemes at once, is the number a dealer acts on. Working it out by hand across three spreadsheets is impractical; for an engine it is a by-product of the daily run. The dealer scheme payout formulas post walks through each scheme kind in rupees.
Retailer incentives on the same engine
Retailers and sub-dealers do not buy from you directly, so their schemes need a different proof: the distributor's invoice, a photo of the purchase bill read by OCR, or a product scan. The calculation does not change. A retailer purchase slab, a counter-sales scheme or a display incentive is configured the same way as a dealer scheme and settled through the same approval ledger, by UPI or rewards rather than credit note. Electricians, plumbers, painters, franchisees and field teams follow the same pattern. The retailer incentive program guide covers scheme design for that tier.
Sales team incentives from the same invoices
The invoices that drive dealer schemes also drive the incentives of the people who sell to those dealers. Unotag calculates sales team incentives on the same feed: each invoice is attributed to the salesperson mapped to that customer on the invoice date, plans combine gates (minimum sales against target, premium share, beat adherence, new counters) with earning components (slabs on sales, premium mix, product push, new business, growth), and managers' results roll up from their teams. The sales incentive calculation guide covers that side in detail.
What it changes for each team
| Team | Before | After |
|---|---|---|
| Sales operations | Days of spreadsheet work after month close | Reviews exceptions and approves; new circulars are configured in minutes |
| Finance | Receives one total with limited working | Approves per dealer with the invoices behind each figure; credit-note file generated |
| Sales officers | Learn the result when the credit note posts | See every dealer's position and next target during the month |
| Dealers and retailers | Find out what they earned weeks later | See progress, earnings and next target daily in the app, WhatsApp or the brand's own app |
| Audit | Rebuilds samples by hand | Reads the payout ledger: who changed what, when and why |
Key takeaways
- Incentive calculation is slow because rules, invoice data and approvals live in separate spreadsheets, not because the arithmetic is hard.
- Store each circular as configuration, read one invoice feed, define eligibility as rules with dealer-code clubbing, and recalculate daily.
- Run the worked examples printed in each circular as automated tests before any dealer sees a number.
- Attach the counted invoices to every result so disputes and approvals use the same evidence.
- Retailer, influencer, franchisee and field incentives use the same engine with a different proof of purchase.
Frequently asked questions
How do you calculate dealer incentives?
For each scheme, take the dealer's qualifying invoices in the period net of returns, apply the scheme condition (quantity, value, growth or payment days) and the incentive rule (per unit, percentage, fixed or slab). A scheme engine does this for every dealer and every live scheme from one invoice feed and keeps the invoices behind each figure.
How can we automate scheme calculation instead of using Excel?
Move each circular into configuration on a scheme engine, connect the ERP invoice feed or a daily Excel upload, define eligibility as rules, and reproduce the circular's worked examples as tests. After that, the calculation runs daily and month end becomes an approval step.
How is retailer incentive calculation different from dealer incentive calculation?
The rules are similar; the proof is different. Dealer schemes read your primary invoices from the ERP. Retailer schemes read distributor invoices, OCR of purchase bills or product scans. On Unotag both run on the same engine and approval ledger.
How do you handle returns in incentive calculation?
Returns and credit notes dated inside the scheme period should reduce the qualifying figure even if they arrive after the period. A scheme engine recalculates automatically when the return lands, so payouts are corrected before approval rather than recovered later.
Can one invoice count for more than one scheme?
Yes, if the circulars allow it. A dealer's invoice commonly counts toward a quantity slab, a growth scheme and a cash discount at the same time. Where a circular excludes overlap, that exclusion is part of the scheme's configuration.
Which ERPs can feed the incentive calculation?
Unotag integrates with SAP (all versions, including ECC, S/4HANA and Business One), Oracle, Microsoft Dynamics, Tally, Zoho, ERPNext, LOGIC ERP, eZee or any other ERP, and with any CRM in use. The engine needs dealer code, date, product, quantity and value for each invoice line, plus returns and credit notes; where an integration is not ready, a daily Excel upload works.
How long does it take to set up a new scheme?
Once invoices and the dealer master are connected, a scheme that fits an existing scheme kind takes minutes to configure on Unotag, including a cost projection on past purchases before it is published.
How do you prove an incentive calculation is correct?
Reproduce every worked example printed in the circular as an automated test before go-live, and attach the list of counted and excluded invoices to every dealer's result so anyone can check the figure.