Most companies run commission as a payroll task. Finance or HR collect the numbers at month-end, fix the spreadsheet and pay. That gets the money out the door, but it does nothing for the reason commission exists: to steer what reps do every day. Commission is the biggest motivation lever a sales org has. It belongs inside the revenue engine, owned by RevOps, running next to the CRM and visible to reps while they can still act on it.
Below: the operating model step by step, how it changes with company size, how to measure whether a plan works, and a 90-day plan for a RevOps leader. It includes new data from 2,375 public sales job ads.
Key findings
- 21.8% of 2,375 open sales job ads (879 companies, read 2 November 2026) say the role pays commission or OTE. The rest do not say the role pays commission.
- 0.27% of 17,970 open job ads at 1,868 companies were RevOps or sales operations roles. That is about one ops role for every 48 sales-role ads.
- 20% of those 49 RevOps and sales ops ads name commission or compensation work as part of the job (10 of 49).
- 2.3% of the companies had an open RevOps or sales ops role at all. Hiring for the function is still rare.
Who owns commission today, and why is that the problem?
In most companies commission is owned by finance or HR and handled at month-end. Their job is to pay the right amount on time, and they usually do. The problem is that nobody owns the other half: whether the plan makes reps do what the business needs.
The typical month looks like this. Someone exports won deals from the CRM. Someone else matches them against a spreadsheet of rates, splits and exceptions. The sales manager is asked to confirm. Reps get a number after the month is over, often by email, and the questions start. Corrections go into next month. Payroll gets a file.
Each step is reasonable on its own. Together they produce three effects that hurt sales performance:
- Reps learn what a deal paid weeks after closing it. The motivating moment is gone.
- Data errors are found by the person least able to fix them. Finance spots a wrong owner at month-end. The rep who knows the truth sees it last.
- The plan is never checked against behaviour. If it was meant to push multi-year deals, nobody measures whether it did. It is renewed because it was paid correctly.
Anders Goosmann, CEO of Prowi, lived this before he started the company. "I ran a 10-person sales team at Webshipper up to the exit in 2021. Commission ran in a spreadsheet, and it caused disputes, clawbacks and endless emails. It got so bad that we nearly went back to fixed salaries."
Going back to fixed salaries would have meant giving up the strongest motivation lever the team had, only because it was hard to run.
His conclusion is blunt: "If you treat commission as payroll, you've already failed." That is not an argument against spreadsheets. They kind of work for payout. They do not work for steering behaviour, because nobody looks at them until the month is over.
What does it mean to treat commission as a RevOps system?
Treating commission as a RevOps system means plan design, data rules, calculation, rep visibility and measurement are run as one system next to the CRM, owned by RevOps. Finance keeps control of approval, accounting and payout. The difference is who is responsible for the plan working, not just for the plan being paid.
Revenue operations already owns the machinery that turns pipeline into revenue: lead routing, territories, stages, the forecast and the CRM itself. Commission is part of that machinery. It decides which deals reps chase, how they price, what they log and when they close. Leaving it outside RevOps is like letting someone outside RevOps define the deal stages.
For the wider picture of the discipline, see our guide to commission management.
Payroll mindset vs RevOps mindset: what actually changes?
The two mindsets ask different questions. The payroll mindset asks "did we pay the right amount?" The RevOps mindset asks "did the plan make the right things happen, and did we pay the right amount?" The table shows how that plays out.
| Dimension | Payroll mindset | RevOps mindset |
|---|---|---|
| Main question | Did we pay the right amount on time? | Did the plan drive the behaviour we wanted, and was the pay right? |
| Owner | Finance or HR | RevOps, with finance owning approval and payout |
| When numbers are known | After the period closes | Continuously during the period |
| Source of truth | A spreadsheet built from a CRM export | The CRM records themselves, with written crediting rules |
| What reps see | A total, after the fact | Each deal's effect on their pay, while the period is open |
| How data errors are found | By finance at month-end | By reps, when a deal does not show up as expected |
| Disputes | After payout, by email | During the period, on the deal record |
| Plan changes | Once a year, based on budget | Planned cycle, based on measured behaviour |
| Success measure | No payroll errors | Target behaviour moved, cost of sales in range, few disputes |
| Relationship with the CRM | A data source to export from | The system the plan runs on |
Why is commission the biggest motivation lever in a sales org?
Commission is the only part of pay that moves with every deal a rep closes. That makes it the most direct signal a company can send about what it values. But it only steers behaviour when reps know what they stand to earn, and most never really do.
Base salary does not move with a deal. Contests are temporary. Manager attention covers a few deals a week. Commission is the lever a rep feels on every deal. The psychology behind this is covered in sales incentives that work.
Yet most reps cannot say what a specific open deal is worth to them. They know their rate, roughly, but not how splits, product mix, contract length or tiers change it. The plan's finer signals never reach them.
Anders puts the gap this way: "A dashboard shows what a deal is worth to the company. Prowi shows what it's worth to the rep." Take an illustrative deal. The pipeline report tells a manager it is worth 40,000 USD in annual contract value. The rep wants to know whether it is worth 2,400 USD (6%) or 3,600 USD (9%) to them, and what would move it. When they can see that, the plan starts doing its job. There is more on this in why reps who see commission in real time perform better.
What changes when commission lives next to the CRM?
When commission is calculated from the CRM records sales already maintains, there is one version of the truth. Changes to a deal reach the rep's statement the same day, data problems surface as rep questions instead of month-end surprises, and RevOps can test plan changes on real pipeline.
Five concrete things change:
- No second system. Reps do not report deals twice. The plan runs on the deals they already keep in HubSpot, Pipedrive, Salesforce, Microsoft Dynamics 365 or Podio.
- Same-day feedback. A deal moved to closed won shows up in the rep's earnings during the period. In Prowi, reps see this in the mobile app (iOS and Android) and on the web.
- Data quality gets an owner. When a deal does not appear on a statement, the rep notices and fixes the record. This is the subject of our companion piece, commission data as a CRM data quality tool.
- Plans can be simulated. RevOps can run a proposed plan over last year's deals and this year's pipeline before anyone signs it.
- Commission cost becomes forecastable. If you know the pipeline and the rules, you can estimate next quarter's commission cost. Finance gets an accrual they can trust.
What is the RevOps operating model for commission?
The operating model is a loop of six steps: design the plan, define the data and crediting rules, give everyone live visibility, run statements and approval, hand approved amounts to payroll, and measure whether the plan drove the behaviour you wanted. The last step feeds the next design cycle.
- Plan design: decide what behaviour the plan should reward, then turn it into rules a rep can understand.
- Data and crediting rules: define which CRM fields count, which date counts and who gets credit.
- Live calculation and visibility: calculate earnings continuously and show reps and managers the same numbers.
- Statements and approval: close the period, review exceptions and approve each rep's statement.
- Payroll handoff: pass approved amounts to payroll in a format payroll can use without rework.
- Behaviour review: measure whether the plan moved the behaviour it was designed for, and feed that into the next cycle.
Step 1: How should the plan design cycle work?
Run plan design as a fixed annual cycle, with a half-year checkpoint. Start from the behaviour you want, not from last year's plan. Test the proposed plan on real data before anyone signs it.
A workable cycle has four stages. The sales leader states the intent in plain words, such as "more mid-market logos" or "fewer heavy discounts". RevOps turns it into mechanics: rates, tiers, multipliers, caps, splits. Finance checks cost at different attainment levels. HR or legal checks that the plan document and contracts match.
Two rules keep this honest. Every plan element must point at a named behaviour. If nobody can say what a kicker is for, remove it. And every element must be explainable in one sentence to a new rep. Complex plans lose trust. The principles behind a plan that holds up are in how to design a fair and scalable commission model, and worked examples for AEs, SDRs, account managers and others are in our commission plans by role hub. To check an existing plan quickly, use the commission plan health check.
Step 2: Which data and crediting rules does the plan need?
Write down, field by field, what the plan reads from the CRM and what each value means for pay. If two people could read a rule differently, it will cause a dispute. The rules belong in a shared document that RevOps maintains, not in a formula.
A complete rule set answers five questions for every deal: what was sold, whose deal it is, when it counts, what state it is in, and how much it is worth. In CRM terms that is usually product or line items, deal owner and split fields, close or won date, deal stage, and amount. Add rules for the edge cases you know will happen: owner changes mid-deal, deals that reopen, partial cancellations, deals signed in one currency and booked in another. Our glossary entry on the crediting rule covers the common patterns.
Agree who may change which field after close. If the amount on a closed won deal can be edited by anyone, the plan is open to accidental and deliberate changes. Most CRMs support field permissions or at least change history. Use them.
Step 3: What does live visibility require?
Live visibility means each rep sees their own earnings update as deals change, and managers see the same numbers for their team. It requires that calculation runs automatically from the CRM, without someone rebuilding a spreadsheet.
The point is not a nicer report. It is timing. A rep who sees that moving a deal from 12 to 24 months changes their payout will ask the customer about term length while the deal is still open. A rep who learns it at month-end cannot. In Prowi, when a period starts, each rep gets a statement that updates live through the period, so the plan's signal arrives while the rep can still act on it.
Visibility also changes one-to-ones. They can start from the statement: which deals count, which are missing, which are close to a tier.
Step 4: How should statements and approval work?
At period close, every rep's statement should move into a review state, exceptions should be resolved, and someone with authority should approve it. Approval is where finance and sales leadership take formal responsibility for the amount.
This is how it works in Prowi. When a period closes, the commission statement moves to "awaiting approval" and the approval flow starts. When it is approved, the amount is added to the rep's account balance in Prowi. Prowi also handles corrections and clawbacks.
Whatever tool you use, keep three habits. Approve on the statement, not in an email thread. Record why an exception was made. And keep closed periods closed: correct forward, so the history stays auditable. Our guide to avoiding commission disputes goes deeper on exceptions.
Step 5: What does a clean payroll handoff look like?
A clean handoff gives payroll one approved amount per person per period, in a format the payroll system accepts, with no manual retyping. Finance or HR stays in control of when it is paid.
In Prowi, approved commission is passed on to payroll either by finance or HR, or automatically through the payroll integration. Zenegy receives a direct push. Danløn, Visma Dataløn, Lessorløn and Visma Enterprise receive approved commission through Prowi's payroll file. Either way, payroll gets numbers that have already been approved, so it never has to judge whether a deal counts.
Payroll also has legal edges, and they differ by country. This is general guidance, not legal advice:
- United States: wage rules are set at both federal and state level and vary widely. California, for example, requires commission agreements to be in writing and to state how commission is computed and paid (California Labor Code section 2751).
- United Kingdom: an employer may only deduct from wages when a statute or a written contract term allows it, or the worker has agreed in writing beforehand (Employment Rights Act 1996, section 13). That matters for clawbacks.
- EU and the Nordics: the EU Pay Transparency Directive treats variable pay as part of pay and asks for gender pay gap reporting on variable components. See our guide to the directive and commission.
In all cases, check with local employment counsel before you change how commission is calculated, clawed back or documented.
Who does what in the operating model?
RevOps owns the system end to end, but it does not own every decision. Sales leadership owns intent, finance owns cost and payout, HR or legal own the contract, and reps own their data. The table makes the split explicit.
| Step | Sales leadership | RevOps | Finance | HR or legal | Reps |
|---|---|---|---|---|---|
| Plan design | States the behaviour wanted, signs off | Designs mechanics, simulates on real data | Sets budget, checks cost range | Checks contract and plan document | Give feedback on clarity |
| Data and crediting rules | Settles credit disputes | Writes and maintains the rules | Confirms revenue definitions | None | Keep their deals accurate |
| Live visibility | Uses statements in one-to-ones | Runs the calculation and access | Reads the commission accrual | None | Check their own statement |
| Statements and approval | Approves for their team | Resolves exceptions, prepares close | Final approval | None | Raise questions before close |
| Payroll handoff | None | Delivers the approved file or push | Owns timing and booking | Owns payroll compliance | None |
| Behaviour review | Decides what to change | Measures and reports | Reports cost of sales | Flags legal constraints on changes | Answer a short plan survey |
How does the model look at 10, 40 and 150 reps?
The six steps are the same at every size. What changes is who wears the RevOps hat, how many plans you run and how much you can automate. The scenarios below are illustrative, built from common setups, not from specific companies.
Scenario A: 10 reps, one plan, founder-led sales (illustrative)
A software company with 10 reps and one AE plan: 10% of first-year contract value, paid monthly, with a 90-day clawback. There is no RevOps hire. The head of sales or a finance generalist runs commission in a spreadsheet, two days a month.
The team size matches the Webshipper team Anders describes above. At this size the payout part works. What breaks is trust: every rep keeps their own shadow spreadsheet, and every month-end produces a handful of questions that take days to settle. The first priority is not a new plan. It is writing the crediting rules down and making earnings visible during the month. One person, a few hours a week, owns the system. If each rep earns 15,000 to 25,000 EUR in commission a year (an assumption for this example), the company pays out 150,000 to 250,000 EUR. That is large enough to deserve a process.
Scenario B: 40 reps, four roles, first RevOps hire (illustrative)
A scale-up with SDRs, AEs, account managers and a channel team: four plans, splits between SDR and AE, and a quarterly accelerator. A RevOps manager has just been hired and inherits a spreadsheet with dozens of tabs.
Here the main risk is complexity. Splits and role changes cause most disputes, and finance spends several days on every close. The priority is to move calculation onto the CRM, define split rules as fields rather than notes, and introduce a formal approval step. This is also the size where simulating a plan on real deals before launch starts to matter, because one wrong threshold applies to 40 people at once. Our article on commission software implementation describes what that move typically involves.
Scenario C: 150 reps, several countries, RevOps team (illustrative)
A company selling in the US, the UK and three EU countries, with 150 reps on eight plans and payroll in several systems. RevOps is a team of four.
The challenge here is consistency and compliance. Plans differ by country because employment law and market norms differ. Currency, clawback rules and payout timing vary. The priority is a single rule set with country variants, one approval flow, a payroll handoff per payroll system, and a quarterly behaviour review per segment. Plan changes need a longer runway, because contracts and works councils may be involved in some EU countries.
| Dimension | 10 reps | 40 reps | 150 reps |
|---|---|---|---|
| Who owns commission | Head of sales or finance generalist | First RevOps hire | RevOps team, with a compensation owner |
| Number of plans | 1 to 2 | 3 to 5 | 6 or more, with country variants |
| Main source of disputes | Unwritten rules | Splits and role changes | Country differences and plan changes |
| Design cycle | Annual, informal | Annual with half-year checkpoint | Annual, segment reviews each quarter |
| Payroll handoff | One payroll system, one file | One payroll system, approval step | Several payroll systems, one approved source |
| First priority | Write rules, show live earnings | Move calculation onto CRM, formal approval | One rule set, country variants, behaviour reviews |
| Calculator or system | A calculator can be enough | A system starts to pay off | A system is required |
If you are unsure which side of that line you are on, our comparison of a commission calculator vs a commission management system lists the capabilities that separate them.
How do you measure whether the plan drives the behaviour you want?
Name the behaviour each plan element is meant to drive, pick one metric for it that comes straight from the CRM, and compare the period before and after the plan change. Look at the distribution across reps, not just the average, because a plan that moves three top reps and nobody else is not working.
The table pairs common plan goals with a lever, a metric and a warning sign. The metrics are definitions, not benchmarks. Your own baseline is the benchmark.
| Behaviour you want | Plan lever | Metric from the CRM | Warning sign |
|---|---|---|---|
| More new customers | Higher rate on new business than on expansion | New-logo share of bookings per rep | Expansion deals relabelled as new |
| Longer contracts | Multiplier on multi-year terms | Share of won deals with a term of 24 months or more | Longer terms with weaker cancellation clauses |
| Price discipline | Commission on gross margin, or a discount threshold | Average discount on won deals | Deals stalled at the threshold |
| Focus on a new product | Temporary kicker on that product | Share of deals including the product | Product bundled in at near-zero price |
| Even performance across the team | Accelerators above quota, tiers below | Spread of attainment across reps | Most pay going to a few reps while the middle stalls |
| Accurate pipeline | Pay on won date and signed amount only | Close-date changes per deal before won | Deals pushed across period boundaries |
Alongside behaviour metrics, track the health of the system itself. Five measures cover most of it:
- Attainment distribution: how many reps are below 50%, at 50 to 100%, and above 100% of quota. A plan with almost nobody at target has a quota problem, not a motivation problem.
- Cost of sales: total commission as a share of the revenue it paid for, by segment. Compare it with the range finance agreed during design.
- Disputes per period: questions that changed a statement. A rising count points at an unclear rule.
- Days to close a period: from period end to approved statements. Long closes mean manual work is hiding somewhere.
- Manual corrections: adjustments outside the rules. Each is a rule not yet written.
Review behaviour metrics quarterly and system health monthly, and bring both to the annual design cycle. Plan design then starts from what the plan actually did.
What are the strongest objections to RevOps owning commission, and how do you answer them?
The objections are real, and most contain something true. The answer is rarely "RevOps takes over". It is a clear split: RevOps owns design, data and measurement, while finance keeps approval, accounting and payout.
| Objection | What is true in it | How to answer it |
|---|---|---|
| "Anything that becomes pay must sit with finance." | Payout needs financial controls and segregation of duties. | Finance keeps final approval and payout. RevOps cannot pay anything finance has not approved. |
| "We are too small for RevOps." | A 10-rep team cannot justify a RevOps hire for commission alone. | RevOps is a role, not a headcount. One person owning the system a few hours a week is enough at that size. |
| "If reps see the calculation, they will game it." | Any plan can be gamed. | Reps game opaque plans too, just invisibly. Live numbers make gaming visible early, and it can be fixed in the rules. |
| "Our spreadsheet works." | For payout, it often does. | Agree, and ask a different question: does the spreadsheet change what reps do during the month? If nobody sees it until month-end, it cannot. |
| "Live numbers will create daily disputes." | Visibility does surface more questions early on. | Those questions existed already. They just arrived after payout. Settling them during the period is cheaper, and the count falls once the rules are written down. |
| "Plan changes will get harder with more scrutiny." | A visible plan is harder to change quietly. | That is a feature. Plan changes should be explained, tested and documented. Our guide to rolling out a new commission plan shows how. |
What mistakes do teams make when they move commission into RevOps?
The common mistakes are about scope and sequence: trying to redesign the plan and the system at the same time, automating unwritten rules, and forgetting finance. Each of them is avoidable.
- Changing the plan and the system at once. If payouts change in the same month as the tool, reps cannot tell whether a difference is a bug or a design choice. Move the current plan first, then change it.
- Automating rules nobody wrote down. Software calculates exactly what you tell it. If the rule lives in one person's head, write it before you build it.
- Leaving finance out until go-live. Finance needs to trust the numbers before the first approval. Run one or two periods in parallel with the old method and compare.
- Too many plan elements. Each kicker, exception and multiplier adds a reason for a dispute. If you cannot name the behaviour it drives, remove it.
- No owner after launch. A system without an owner decays into a spreadsheet again within a year. Name the owner and give them the monthly close.
What should a RevOps leader do in the first 30, 60 and 90 days?
Spend the first 30 days understanding the current plan and its data, the next 30 making earnings visible and the rules explicit, and the last 30 running a clean close and setting up behaviour measurement. Do not redesign the plan in this period. Earn trust with the current one first.
| Period | Goal | Actions | Output |
|---|---|---|---|
| Days 1 to 30 | Understand what exists | Collect every plan document and spreadsheet. Interview sales leaders, finance, payroll and three reps. List every disputed case from the last two quarters. Map each plan rule to a CRM field. | A written rule inventory and a list of gaps between plan, data and practice |
| Days 31 to 60 | Make rules explicit and earnings visible | Write crediting rules field by field. Agree field permissions after close. Choose how calculation will run from the CRM. Give reps and managers a view of their own earnings, even a simple one. | An approved rule document and live earnings for at least one team |
| Days 61 to 90 | Run a clean close and start measuring | Run one period with a formal statement and approval flow, in parallel with the old method. Agree the payroll handoff with finance. Pick two behaviour metrics per plan and record the baseline. | One approved period with no rework, a payroll handoff finance trusts, and a baseline for the next design cycle |
By day 90 you should be able to answer three questions in one sentence each: what the plan is meant to drive, whether reps can see what they earn, and how long the last close took. If you can, you are running commission as a system.
Where do the job-ad numbers come from?
The figures come from Prowi's own dataset of public job ads, read on 2 November 2026. They show what companies write in ads, not what they pay.
- Sample: 17,970 open job ads from the public careers pages of 1,868 companies that Prowi tracks, excluding recruitment agencies. About half of the companies with sales ads use a .com domain, a fifth a Nordic one.
- Sales ads: 2,375 ads at 879 companies with a selling-role title (SDR or BDR, account executive, account manager, business developer, sales manager, presales and similar).
- Commission: the ad says the role itself pays commission, OTE or variable sales pay, in any language in the set. Other meanings, such as "European Commission" or partner commission, do not count.
- RevOps and sales ops: matched on job title. We read all 49 ads to find the 10 that describe commission or compensation work.
- Limits: companies may pay commission without saying so, or have RevOps without an open role. No company is named.
| Company web domain | Sales ads (count) | Ads mentioning commission or OTE (count) | Share (%) |
|---|---|---|---|
| .com | 1,240 | 294 | 23.7% |
| Nordic country domains (.dk, .se, .no, .fi) | 502 | 72 | 14.3% |
| Other European country domains | 272 | 40 | 14.7% |
| Other domains (.io, .ai and similar) | 361 | 111 | 30.7% |
| All sales ads | 2,375 | 517 | 21.8% |
Of the 879 companies with sales ads, 217 (24.7%) mention commission in at least one of them. Few companies describe their plan to candidates, and fewer hire someone whose job is to make it work.
FAQ
Who should own sales commission, RevOps or finance?
Both, with a clear split. RevOps should own plan mechanics, crediting rules, calculation, visibility and behaviour measurement. Finance should own budget, final approval, accounting and payout. Sales leadership owns what the plan is meant to achieve.
Do we need commission software to run commission as a RevOps system?
Not at the start. You can write rules, show earnings and run a formal approval with simple tools. Software starts to pay off when you have several plans, splits, frequent disputes or more than a few days of work at every close, because it calculates from the CRM continuously and keeps the audit trail.
How often should a commission plan change?
Plan for one main design cycle a year, with a half-year checkpoint for small adjustments. Change mid-period only when something is clearly broken, and explain the change in writing before it takes effect. Check local employment counsel before changing terms that are part of employment contracts.
Won't real-time commission create more disputes?
It surfaces disputes earlier, which is the point. Questions that used to arrive after payout arrive while the deal can still be corrected. Once crediting rules are written down and visible, there are fewer reasons to ask.
What is the difference between RevOps and sales ops for commission?
Sales ops traditionally supports the sales team only. RevOps covers marketing, sales and customer success as one revenue engine. For commission the difference matters when plans span roles, such as SDR and AE splits or account manager plans tied to retention, because the data comes from more than one team.
Want to see how live commission works on your own CRM data? Book a demo and we will show you a statement built from your deals.