Why No One Wants to Own the Comp Process

Ask a RevOps leader who owns the commission process, and they’ll tell you it’s Finance’s job, since Finance owns the expense line.

Ask Finance, and they’ll tell you it’s RevOps’ job, since RevOps owns the CRM data the calculations run on.

And ask the CRO, and they’ll tell you they thought someone else had already figured this out.

This indicates a structural gap. Incentive pay sits at the intersection of two functions, each with a real, defensible reason not to want the job and a defensible reason they can’t fully do it alone.

Understanding why both sides push back is the first step to building an ownership model that actually holds.

Why RevOps doesn’t want to own it

RevOps has become the team responsible for everything that touches the CRM, which by extension means everyone assumes RevOps also owns whatever touches commissions.

In practice, most RevOps teams are already stretched across territory and quota planning, pipeline hygiene, forecasting, tooling, and enablement, before compensation ever enters the picture. Adding a full incentive pay process on top is less “new project” and more “new full-time job.”

This is exactly the kind of unbounded scope creep that shows up in Forbes’ recent look at “scope leap”, where high performers keep absorbing adjacent responsibilities until the original job is unrecognizable.

There’s a second, sharper reason RevOps resists it: comp is a thankless process to own without financial authority.

When a payout looks wrong, reps go to RevOps first, because RevOps runs the system reps can see. But RevOps rarely has the authority to unilaterally change an accrual policy, override a plan exception a sales leader promised verbally, or decide how a disputed deal should be treated for revenue recognition purposes.

They inherit the blame without holding the decision rights, which is the exact dynamic durity.com’s writeup on the RevOps framework for stopping finance and sales fights over numbers points to as the root of most RevOps-Finance friction: ownership without authority breaks down the first time the numbers are contested.

Internally, this is the same gap covered in QuotaPath’s RevOps guide to sales compensation management and comp plan design for RevOps: RevOps is well positioned to design and operate the plan, but poorly positioned to own its financial consequences.

Why Finance doesn’t want to own it

Meanwhile, Finance’s resistance runs in the opposite direction.

Finance genuinely does own the hard accounting underneath incentive pay. Commission expense has to be accrued correctly, and under ASC 606, sales commissions tied to obtaining a contract typically have to be capitalized and amortized over the expected customer life rather than expensed immediately.

FloQast’s breakdown of how to book a deferred commission journal entry under ASC 606 is a good look at just how much technical accounting judgment sits underneath a number that looks, from the sales floor, like a simple payout. QuotaPath’s own deferred commissions accounting guide covers the same mechanics in more depth.

What Finance lacks is visibility into the deal-level data the calculations depend on, or context on why a plan is structured the way it is.

Finance can tell you whether an accrual is compliant. Finance usually cannot tell you whether a rep’s quota was set correctly, whether a deal was misclassified in the CRM, or whether a plan exception a sales manager approved six months ago ever got documented anywhere.

That gap is part of why analyst firms increasingly treat incentive compensation management as its own discipline rather than a subset of either accounting or sales operations. Gartner’s definition of incentive compensation management frames it explicitly as software and process that spans plan design, calculation, and payout, not just the expense entry at the end of it.

There’s also a role Finance genuinely doesn’t want: being the function that says no.

Capping an over-earning payout, holding a commission pending a deal review, or enforcing a clawback are decisions with real relationship cost with the sales org, and Finance would generally rather not make that call in isolation, without an operational partner who actually understands the deal.

Why the comp process needs both

Our position: comp ownership should be shared across RevOps and Finance.

Ownership stalls because comp isn’t a single decision; it’s a chain of decisions, and RevOps and Finance each hold different links in that chain.

This is the problem Bain & Company’s RAPID framework was built to diagnose: most process breakdowns don’t come from a lack of talent, they come from unclear decision rights, where multiple people can weigh in but no one is clearly accountable for the final call. Bain’s own writeup on why RAPID adoption works better when organizations slow down and actually assign the roles is a useful lens here: comp ownership fights are usually a decision-rights problem wearing a staffing problem’s clothes.

Applied to incentive pay, RevOps has the operational and data context: they know the CRM, the deal data, the quota logic, and the day-to-day questions reps actually ask. Finance is the function with the compliance and financial context: they know what’s defensible under ASC 606, what the accrual exposure looks like, and what an auditor will ask about.

Neither function can responsibly make every call in that chain alone.

Forrester’s analysis on the compensation capabilities inside sales performance management makes a similar point from the vendor-market side: the tooling in this space increasingly has to serve both an operational and a financial user, because the process itself was never meant to sit entirely inside one function.

When ownership isn’t clarified, the failure mode is predictable: a shadow spreadsheet somewhere becomes the “real” numbers, reps stop trusting their statements, disputes escalate to leadership instead of getting resolved at the source, and the accrual finance reports to the board don’t actually reconcile with what operations paid out. None of that is a talent problem. It’s what happens when a cross-functional process has no explicit owner for any of its decisions.

What shared ownership actually looks like

The fix isn’t picking a single owner, since neither function can carry the whole process alone. It’s assigning explicit decision rights to each part of the chain, the way QuotaPath’s own look at who owns compensation planning and RevOps and Finance alignment both lay out in practice:

• RevOps owns plan design, CRM data integrity, and day-to-day calculation logic, since that’s where the operational context lives.
• Finance owns accrual policy, ASC 606 treatment, and final sign-off on anything with real financial exposure, since that’s where the compliance context lives.
• Plan changes and disputed payouts route through both, ideally via a standing comp committee rather than an ad hoc email thread. (QuotaPath’s guide to who should sit on a sales compensation committee is a useful starting point for defining that group formally instead of letting it form by accident during the first dispute.)

None of that works well on spreadsheets, because spreadsheets have no audit trail and no way to enforce who approved what. A shared system of record, where RevOps can manage plan logic and data mapping and Finance can see the same numbers with a defensible accrual trail underneath them, is what actually makes joint ownership sustainable instead of aspirational. That’s the gap QuotaPath is built to close: build the compensation plan with the operational logic RevOps needs, backed by the calculation transparency Finance needs to sign off on it, and model the payout scenarios both sides need to see with the sales compensation calculator before a plan ever goes live.

The takeaway

Nobody wants to own the comp process alone because no one function actually can. RevOps has the data and the operational context but not the financial authority. Finance has the compliance obligation but not the deal-level visibility. The organizations that get this right stop looking for a single owner and start assigning clear decision rights across both, backed by a system that gives them a shared source of truth instead of two sets of numbers that don’t agree.