Incentive plans with periods, member scoping by partner, branch, customer or resource, eleven target types — order and invoice counts, quantities, values, unique items, or a custom KPI — and eight reward types. A target-vs-attainment widget on web and mobile shows every rep where they stand.
Fifteen scheme types across sale, purchase and repair documents with condition builders, slabs, free items and item groups, account budgets and a consumption ledger — recommended in the order flow, recomputed authoritatively at posting.
Reward points earned through schemes accrue on the customer account with available-balance tracking, visible on the record.
Every row ships today and traces to a capability described on this page.
| Capability | xMatix Rewards |
|---|---|
| Incentive plans, periods and slabs | Native |
| Eleven target types, including custom KPIs | Native |
| Eight reward types | Native |
| Fifteen trade-scheme types | Native |
| Scheme budgets with a consumption ledger | Native |
| Rule-based account groups and discount groups | Native |
| Mid-period attainment visibility on web and mobile | Native |
| Account reward points | Native |
| Incentives computed from posted documents | Native |
| Scheme-gap nudges on the order | Integrated — Sense |
| Purchase-side schemes (per PO / per bill) | Native |
From the documents themselves. Plans, periods and slabs are defined once, and attainment computes from the orders and invoices already in the system — not from a spreadsheet assembled the night before payout. That is also why payout day holds up: plan, period and KPI reports show exactly how every figure was earned, so the number defends itself instead of starting an argument.
Yes — target versus attainment sits on the rep's own screen, web and mobile, mid-period. The point is motivation while it can still change the number: a rep who can see the gap in week three behaves differently from one who learns it after the quarter closes. Sense adds the nudge on the order itself — “add five more units to hit the slab” — so near-misses convert instead of expiring.
No — each account's scheme budget is tracked as it is consumed, and the promotion ends when the budget does. Fifteen scheme shapes — slabs, free goods, points and their cousins — run on one engine with conditions combined any way you need, and all of them respect the same budget ledger. The offer that quietly overspends its allocation is not a risk you have to audit for afterwards.
Eleven target types — order value, invoice count, unique outlets covered, and custom KPIs you define from real transactions, among others. Rewards are equally flexible: eight reward shapes, from fixed amounts and percentages to per-unit payouts and gifts, so the incentive matches the behavior you want rather than the other way round. If you can measure it from the documents, you can pay against it.
With the report, not a meeting. Every payout figure traces to the plan, the period and the KPI that produced it, computed from posted documents — so the answer to “why is my incentive this number” is a lookup. Because reps watch the same attainment widgets all period, the figure on payout day is rarely a surprise in the first place; slabs and rates are visible policy, not negotiation.
Yes — the scheme engine’s types include Per Purchase Order, Per Bill, Per Purchase Order And Bill, and their per-period variants, so supplier-side programmes are modelled with the same slabs, budgets and settlement discipline as your trade schemes. The scheme-gap nudge fires on purchase orders too: when a small top-up would reach the next slab, the buyer sees the shortfall and what reaching it is worth before the order posts.