Commission & Incentive Management
Every commission number should be able to explain itself
A commission and incentive system built around one earning line: the sale it came from, the rule version that applied on that date, how the figure was derived, who reviewed it, and the approved statement that goes to payroll. Calculated, approved and paid stay three different states.
CL-2048Meera S.Channel Sales · September 2026
- Source event
- SALE-4821Sales system · 18 September 2026
- Eligibility
- IncludedEligible value ₹1,00,000
- Rule applied
- R-07 · 4%Channel Sales · Effective 01 Sep
- Review
- Pending
- Statement
- Not approved
- Payout handoff
- Not handed off
The earning is derived from the eligible value and the matched rule. It is calculated, and calculated is not approved.
ILLUSTRATIVE INTERFACE · SAMPLE DATA
Source and eligibility
A sale is an input. A commission is a decision.
The source system knows a sale closed. It does not know whether that sale earns anybody anything — that depends on the compensation rules the business wrote down. The two facts belong in different places, and the second one has to be checkable.
Input
SALE-4821
₹1,00,000
Sales system
18 September 2026 · Complete
Checked against the plan
- Source stateCompleteA sale that has not completed is not yet an eligible event.
- EarnerMeera S.Who the plan credits — recorded, not inferred from whoever touched the deal last.
- Plan periodSeptember 2026Which period the event falls into, so a late entry cannot quietly land in the wrong statement.
- Rule in forceR-07A plan rule that was actually effective on the date the event happened.
Ruled decision
₹1,00,000
Eligible value
Carried into the earning line under R-07, because the plan says so — not because the sale exists.
What is an eligible commission event?
An eligible commission event is a source record — a sale, order, policy, booking or other transaction — that meets the conditions the organisation’s compensation plan sets for earning commission: the state it has to be in, who it is credited to, which period it falls in, and which rule covers it. The system applies those configured conditions. It does not decide on its own that a transaction is commissionable.
Does a closed deal automatically mean commission is owed?
No. A closed deal is the input to the decision, not the decision. Whether it earns commission depends on the plan the business configured — and separately, what an earner is legally entitled to is a matter of their contract and local employment law, not something software determines.
Can different teams have different commission rules?
Yes. Plans are configured per population — a team, a role, a channel, a product category, a partner tier — and an event is matched to the plan that covers its earner and period. Which distinctions exist is defined during scope, around how the organisation actually pays.
Rule versions
The current rate is not the rate that applied
A spreadsheet holds one number in one cell. When the rate changes, the old figure either quietly changes with it or stops being explainable. A rule with an effective period does neither: the event’s own date picks the version, and September keeps September’s rate.
- R-074%Effective 01 SepApplied to this event
- R-085%Effective 01 OctNot in force on this date
R-08 is the current rule. R-07 is the rule that applied.
₹1,00,000 × 4%₹4,000
Can commission rules change by effective date?
Yes, and this is the part spreadsheets handle worst. Each rule version carries an effective period, and an earning line is calculated against the version that was in force on the source event’s own date. Editing today’s rate does not silently recalculate last quarter.
What happens to historical commission when a plan changes?
Nothing, by default. Past lines keep the rule version they were calculated under, so an approved statement stays explainable. If the business genuinely needs to restate a past period, that is an explicit recalculation with its own review — never a side effect of editing a rate.
Can the system handle slabs, tiers or accelerators?
Flat rates, fixed amounts, slabs, thresholds and accelerators are all rule shapes that can be configured. Which of them a build includes is scoped against the plans the organisation actually runs, rather than claimed as a complete library of every compensation structure.
Calculated and approved
Arithmetic is not authority
A figure can be perfectly derived and still be nobody’s decision. The moment those two things share a single status field is the moment a number reaches an earner before anyone has agreed to it — or sits unpaid because agreeing to it was never anyone’s job.
Derived from the source and the rule
SALE-4821R-07 · 4%₹1,00,000 × 4%
Held by a person, against a statement
Before anyone decides
₹4,000
- Review
- Pending
- Statement
- Not approved
- Payout handoff
- Not handed off
The figure is already correct. It is nobody’s decision yet.
After review
₹4,000
- Review
- A named reviewer completes the line.
- Statement
- The line is approved onto a period statement.
- Payout handoff
- The approved statement is released to payroll or finance.
The same ₹4,000, now with somebody’s name against it.
The statement
One total, or the lines that make it
A single figure with nothing behind it is why people keep a private spreadsheet to check their own pay. The same statement, itemised, answers the question they were actually asking: what counted, what did not, and what is still open.
September commission
₹7,200
One figure. No source, no rule, no state.
Statement · September 2026
3 lines
- CL-2048SALE-4821R-07₹1,00,000₹4,000Approved
- CL-2051SALE-4834R-07₹80,000₹3,200Approved
- CL-2060SALE-4890R-07₹1,20,000₹4,800In review · not in the approved total
Approved total · 2 of 3 lines₹7,200
One line is still in review and is not in this total. It has not disappeared — it is visible, with its own state.
What is the difference between calculated and approved commission?
Calculated commission is the figure the rule produces from an eligible event. Approved commission is that figure after a person with authority has accepted it onto a statement. Keeping them separate is what stops an unreviewed number being treated as a promise, and what makes it obvious when a correct figure is stuck waiting for a decision nobody owns.
Does approved commission mean it has been paid?
No. Approved means ready to be handed to whoever runs payment — payroll, finance, or an accounts process. This system records the handoff. Payment itself is confirmed by the system that makes it, and where that connection is built the payment status can come back onto the line.
What should a commission statement show?
Enough for the earner to reconstruct the number without asking: which source event created each line, which rule version applied, the eligible value it was calculated on, the resulting amount, any adjustment, and the state each line is in. A total on its own is the reason people rebuild their commission in a spreadsheet.
Is a commission statement a payslip?
No. It explains how a variable earning was derived and approved. The payslip is produced by payroll, which combines approved pay components and applies whatever statutory treatment applies. The two connect at the handoff and stay separate documents.
Exceptions
The lines that need a person
Most lines calculate and pass. The ones that matter operationally are the handful that cannot, and the difference between a good month and a bad one is whether those surface as work with an owner or as a query three weeks after the statement went out.
Rule not found
CL-2070Held at · Eligibility checkedA source event with no plan rule covering its earner and period. Needs a plan decision before it can calculate.
Source changed
CL-2078Held at · Under reviewThe underlying sale changed value after the line was calculated. Held for recalculation review rather than quietly restated.
Credit needs review
CL-2081Held at · Source recordedTwo people are recorded against the same event. The split is not assumed — somebody confirms the allocation.
Split credit · SALE-4890
- Meera S.60%
- Aarav K.40%
Allocated100%
Where a plan splits credit, the allocation is configured and has to resolve to the full basis before the lines calculate.
How are commission adjustments and clawbacks handled?
As explicit, reviewable events rather than silent edits. When a source record changes after a line was approved, the original line stays as it was and an adjustment is raised against it for review. Silently rewriting an approved figure is precisely what makes earners stop trusting the system and start keeping their own records.
Can commission be split between two people?
Where the plan splits credit, yes — the allocation is recorded against the source event and has to resolve to the configured basis before the lines calculate. Whether splitting applies at all, and on what basis, is a compensation policy the business sets.
Where it sits
One earning line, between two systems that already exist
This system does not replace the one that recorded the sale, and it does not replace the one that pays. It owns the part in between — which nobody currently owns, which is why it usually lives in a spreadsheet.
Source systems
A sale, order, retail transaction or policy event, from whichever system already records it.
Commission & incentive
Eligibility, rule version, calculation, review, statement, approval.
Payroll or finance
Receives the approved statement and runs the payment process.
- CRMCustom CRM
- Owns the lead, the deal, the customer and the sales owner. It can be the source of an eligible event; it does not own the compensation rule.
- POS & retailPOS & retail management
- Owns the retail transaction. A completed sale can qualify a store or field earner under an incentive plan.
- Insurance managementInsurance management
- Owns the policy, the customer, the renewal and broker commission reconciliation inside insurance operations. A policy event can feed an earning line where the plan says so.
- HRMS & payrollHRMS & payroll
- Owns the employee record, the pay run and the payslip. It receives the approved statement; it does not calculate the earning.
- DashboardsDashboards & reporting
- Reads the record once it exists. Reporting on earnings is a view over commission data, not the place the rules live.
What is the difference between commission management and payroll?
Commission management works out and approves the variable earning — which event, which rule, which amount, approved by whom. Payroll takes approved pay components, combines them with everything else a person is paid, applies statutory treatment and produces the pay run. They connect at the handoff and are not the same product.
Is commission management the same as sales performance management?
No. Sales performance management is a broader category that can include territory planning, quota setting, forecasting and coaching alongside compensation. This Product owns the compensation half: how an eligible event becomes a calculated, reviewed and approved earning. It consumes a target where a plan uses one, and does not plan territories or forecast pipeline.
Does it replace our CRM?
No. The CRM keeps owning the deal and the customer relationship. The commission system reads a qualifying event from it and owns what happens next — eligibility, rule, calculation, review and approval — so that compensation logic is not scattered through CRM fields and exported spreadsheets.
Coming off spreadsheets
A formula is not a rule until it can be checked
The commission spreadsheet is usually correct. What it cannot do is show why. Migration is not copying formulas across — it is rebuilding them as rules and then proving them against periods somebody already agreed to.
What exists now
The workbook, the CRM or POS exports it reads, the plan documents, and the adjustment sheet nobody talks about.
Sample check
A representative set of past lines — the ordinary ones and the awkward ones — pulled out to work against.
Map the record
Earner, source event, eligible base, rule and period identified in the current data before anything is rebuilt.
Rebuild as rules
The plan expressed as versioned rules with effective periods, rather than a formula copied cell by cell.
Prove against history
The rebuilt rules run against those past periods and the results compared with what was actually paid. Differences are examined, not averaged away.
Load and verify
Historical lines loaded where they are worth keeping, checked against the statements the business already issued.
Where a past figure and a rebuilt rule disagree, the difference is worth understanding before go-live — often it is a one-off adjustment nobody wrote down, and finding it is part of the value.
Can old commission spreadsheets be migrated?
The rules can be rebuilt and validated against periods you have already paid, and historical lines can be loaded where they are worth keeping. What we check first is what your current sources can actually export — the workbook, the CRM or POS reports it reads, and the plan documents behind it — because the plan usually lives partly in the sheet and partly in somebody’s head.
What can it connect to?
Wherever the eligible event already lives and wherever the approved statement needs to go. We confirm what each existing system can expose, how a qualifying event is represented in it, and what the receiving payroll or finance process can accept, before defining any connection.
What it meets · what changes size
What is in every build, and what a project decides
The lifecycle is the same everywhere. The compensation policy is not, and the parts that vary are the parts worth scoping honestly rather than promising as a feature list.
- Eligible events and rulesIn every build
- Source events, eligibility conditions, versioned rules with effective periods, and the derived calculation.
- Review and approvalIn every build
- Who reviews, what blocks a statement, and the record of who approved what against which period.
- StatementsIn every build
- Period statements built from their lines, with the source, rule and state visible on each.
- ExceptionsIn every build
- Lines that cannot calculate or need a decision, surfaced as work with an owner.
- Payout handoffIn every build
- An approved statement released to payroll or finance, with the handoff recorded.
- Plan shapesScoped per project
- Slabs, thresholds, accelerators and target-linked incentives, configured against the plans you actually run.
- Split creditScoped per project
- Allocation between earners, managers, channels or partners where the plan splits.
- Adjustments and reversalsScoped per project
- How a changed source event is restated, and what happens to a line that was already approved.
- Earner self-serviceScoped per project
- What an earner can see of their own lines, and at which point in the cycle they can see it.
- Source and payroll connectionsScoped per project
- Reading events from existing systems and delivering approved statements to the receiving process.
What makes a commission project larger or smaller
- How many plans really exist
- Three written plans with four undocumented exceptions is seven plans. This is usually the largest single driver.
- How the eligible event is represented
- A clean completed-sale record is straightforward. An event assembled from three systems and a manual note is not.
- How much history matters
- Validating against two past periods is a different project from reconstructing two years.
- Who has to see what
- An operations-only tool is smaller than one where every earner logs in to their own statement.
- Where the approved statement goes
- A reviewed export is smaller than a live connection into a payroll process with its own cut-off rules.
Does every business need commission software?
No. One flat rule, a handful of earners and a low transaction volume is a spreadsheet and a review habit, and that is a reasonable answer. It becomes worth building when plans differ between teams, rules change over time, eligible events arrive from more than one system, exceptions are routine, or people are checking their own pay because the number does not explain itself.
Custom or off-the-shelf commission software?
Established commission and incentive products cover standard plans well, and if your plans fit one of them, buying is faster and cheaper than building — we would say so. Custom earns its place when eligible events come from systems those products do not read, when the compensation logic is specific to how your business actually sells, when several models run side by side, or when the approval workflow is yours rather than the vendor’s.
Who owns the system and the data?
You do. The compensation rules, the earning records, the statements, any code written for you and the accounts it runs on are handed over as agreed in scope.
Automation
The calculation stays deterministic
Commission is one of the few places where a confident guess is worse than no answer at all. The rule engine is explicit logic, and the useful automation sits around it rather than inside it.
Deterministic, in every build
- Applying an approved rule to eligible events as they arrive.
- Deriving the calculation and building the period statement from its lines.
- Flagging events that cannot calculate, and routing them to whoever decides.
- Opening each period’s statements on the cycle the business runs.
Bounded, where it earns its place
- Reading a plan document to draft rules for a person to review before they go live.
- Explaining an existing calculation in plain language, from the deterministic values already on the line.
Does AI decide the commission?
No. The earning calculation is explicit, deterministic logic — the same inputs always produce the same figure, and the figure can be traced to the rule that produced it. Where AI helps is around that: extracting a draft of the rules from a plan document for a person to check, or explaining a line in plain language. It does not set rates, judge eligibility, resolve disputes or approve anything.
Selected work
Structure, state and flow, built for the people who use it
A commission record is a structured object with derived state and a decision interface on top of it. These are three builds where exactly that was the deliverable — a record given a structure, a product surface given real states, and a service given a flow somebody could follow.
Questions
Commission and incentive management, answered
- What is commission management software?
- Software that turns eligible transactions into traceable variable earnings. It records which source event a commission came from, applies the compensation rule that was in force for that event, derives the amount, routes it for review, places it on a statement and hands the approved result to whoever runs payment.
- What is incentive compensation management?
- Incentive compensation management is the broader term. Commission is typically an earning tied to an eligible transaction under a defined rule; incentive compensation can also include bonuses, target-linked earnings and tier-based rules. This Product covers both under one lifecycle, with the more elaborate plan structures configured per project.
- How is commission calculated from a sale?
- The sale is checked for eligibility against the plan — state, earner, period and a covering rule. If it qualifies, the eligible value becomes the base, the rule version in force on the event’s date supplies the logic, and the earning is derived from the two. The line then holds all of it, so the figure can be explained later.
- Can it calculate commission for agents, brokers, distributors or channel partners?
- Yes, where the organisation defines the compensation rules for them. The lifecycle does not care whether the earner is an employee, an agent or a partner — it cares that there is an eligible event, a rule that covers it and somebody who approves the result.
- Can POS or retail sales feed commission?
- Yes, where a completed retail transaction is an eligible event under a plan. The point-of-sale system keeps owning the transaction; the commission system reads the qualifying event and owns the earning derived from it.
- Can insurance policy events feed commission?
- Where the organisation’s own compensation rules make a policy event eligible, yes. What this Product does not do is interpret regulatory commission structures or insurer settlement — it applies the rules the business configures. Insurance operations themselves, including broker commission reconciliation against policies, belong to the insurance management system.
- Does it handle TDS, tax or statutory deductions?
- No, not by default. Tax treatment depends on jurisdiction, the legal relationship with the earner and how compensation is structured, and it belongs with payroll, finance and appropriate professional advice. If statutory handling is genuinely needed in a build, it is a separately scoped requirement.
- Does it post commission to our accounts?
- Financial posting belongs to accounting and finance systems. Approved commission data can be handed to them where that connection is built, but this Product is not a ledger and does not book entries.
- What does a commission project usually start with?
- Writing down the plans that actually exist, including the exceptions that were never documented, and identifying where each eligible event is recorded today. Almost every difficult commission project is difficult because the rules were never fully written down in one place.
Start
Bring us the plan and one difficult month
The fastest way to scope a commission build is a real period with real awkward lines in it. Bring the plan document, an export of the events behind one month, and the statement that went out.
- The compensation plans you run, including the ones that only exist as exceptions.
- Where the eligible event is recorded today — CRM, point of sale, policy system, spreadsheet.
- Who reviews and approves variable pay, and what currently blocks a statement.
- What happens after approval, and which process actually pays it.
- The lines that caused arguments last quarter.