Every B2B sales organization has two parallel accounting systems for revenue: one for the board forecast, and one for commissions. They are often built on different assumptions, reconciled manually at quarter close, and maintained by different people — RevOps owns the forecast, Finance or HR owns comp. When these two systems diverge, the consequences range from inconvenient to genuinely corrosive.
The benign version: a rep hits their quota and earns their accelerator commission, but the board forecast comes in below plan because the quota target was set lower than the board's expectation for that territory. The rep is rightfully paid; the company misses the investor metric. This is a quota-setting calibration problem that reveals itself too late because the comp model and the forecast model were using different target numbers from the start.
The more damaging version: a rep's commission is calculated on gross closed revenue while the forecast model credits territory performance net of discounting. The rep closes a $200K deal at 35% discount — full commission on the gross, but the net ARR contribution to the territory attainment number is $130K. If the quota was set against net ARR and the commission was paid on gross, the rep is fully compensated while the territory shows underattainment — and no one reconciles this until the post-quarter review.
Both problems have the same root cause: comp modeling and quota forecasting are using different definitions of "revenue" applied to different data cuts. The fix is not complex conceptually, but it requires deliberate architecture.
The Definitional Mismatches That Cause the Most Problems
New ARR vs. Gross Closed Revenue
Sales compensation is most commonly structured on closed-won deal value — the contract value at signing. Revenue forecasts, particularly for SaaS companies, are typically structured on net new ARR, which deducts discounting, pro-ration for partial-year contracts, and sometimes expansion versus new logo distinctions. These are not the same number, and treating them as interchangeable creates the divergence described above.
The most common manifestation: a team closes 102% of the quota-to-closed-revenue target and all reps earn their accelerator commission, while the board forecast model shows 89% net ARR attainment because the quarter included a higher-than-expected mix of discounted or short-term contracts. Finance reports a miss; the sales leader reports an overattainment. Both are technically correct. Neither is useful.
Territory Attribution in Comp vs. Forecast
When deals involve overlay reps, solution engineers, or account managers sharing credit, comp plans typically have explicit split rules — 60/40 between the field rep and the overlay, for example. Revenue forecasts typically attribute deals to a single territory owner for the purposes of calculating territory-level attainment. If the split rules in the comp model are not reflected in the territory attainment calculation, a rep can appear below quota on the forecast metric while being fully compensated on the comp metric — or vice versa.
This is not an abstract risk. Any organization with an overlay model or shared-credit structure will hit this divergence. The question is whether it is caught before the QBR or at it.
Timing: When Revenue Counts
Comp plans typically pay commission when a deal is closed-won in the CRM. Revenue forecasts typically credit ARR to the period when the contract start date occurs. For deals signed at the end of a quarter with a contract start date 45 days later, these can land in different quarters. A rep who closes three deals in the last week of Q3 earns commission in Q3; those deals may credit to Q4 ARR depending on how the revenue recognition model is structured. The attainment forecast shows a clean Q3 close; the ARR forecast shows the contribution landing in Q4.
Neither treatment is wrong — they are measuring different things. But when the board question is "did we hit Q3?" the two answers are different depending on which system you look at, and reconciling them mid-presentation is not where a CRO wants to be.
The Shared Data Layer Architecture
The structural solution is a single source of truth for closed revenue — a deal-level record that contains both the gross closed-won value (for commission calculation) and the net new ARR contribution (for forecast and board reporting), along with the territory attribution, effective date, contract start date, and any quota credit adjustments — all maintained in a single table that both the comp model and the forecast model read from.
This is not a new tool. It is a data architecture decision: instead of the comp model pulling from one CRM view and the forecast model pulling from another, both models draw from a centralized, reconciled deal record with explicit fields for each definitional variant.
The practical implementation requires three things: a reconciled deal record schema agreed upon by RevOps, Finance, and Sales Operations before the quarter begins; a clear process for updating that record when deals are modified post-close (partial year adjustments, renegotiations, contract amendments); and a version history so that the record at quarter-end and the record at board-reporting time are distinguishable if there are post-close adjustments.
Quota-Setting as a Shared Input
The upstream version of this problem is quota-setting itself. Comp plans are built against a quota number. Revenue forecasts are built against a revenue target. If the quota and the revenue target were set from different conversations — sales leadership sets quotas in October based on last year's attainment distribution, Finance sets the revenue target in November based on growth model requirements — there is no guarantee they are consistent.
The most common inconsistency: the aggregate quota across all reps (sum of individual rep quotas) is typically set 10–20% above the company revenue target to account for expected attainment below 100%. If the attainment distribution assumption embedded in that quota-setting process is wrong — if the org historically attains at 88% but the quota was set assuming 92% attainment — then hitting the board target requires either a lucky quarter or actual outperformance, not average execution.
When comp modeling and quota forecasting share the same data layer, this assumption becomes visible and explicitly debatable at planning time rather than invisible until the miss happens.
The Legitimate Reasons These Systems Are Separate
We are not saying the separation between comp and forecasting is purely a dysfunction. There are legitimate organizational reasons for it.
Comp data is sensitive. Individual commission calculations contain information about salary structure, deal attribution decisions, and performance ratings that may not be appropriate for the same audience as the revenue forecast. The separation of systems serves a data access control purpose.
Comp models require legal review. Commission plans are contracts. Finance and Legal have review and approval processes for comp plan changes that are separate from the RevOps forecasting cycle. Conflating the two creates governance complexity.
The argument is not for a single tool that does both. It is for a shared underlying deal record — a master revenue record with clear field definitions — that both the comp calculation engine and the forecast model read from, even if they do different things with that record. The shared layer does not require the same people to have access to both outputs. It requires agreement on what the input data means before either model processes it.
A Practical Starting Checklist
For RevOps teams building toward this alignment, the minimum starting actions are: (1) document the exact definition of "revenue" that each system uses — gross vs. net, booking date vs. ARR start date, territory attribution rules — and identify every place they diverge; (2) choose one definition as the canonical attainment metric and build both the comp calculation and the forecast output to report against it; (3) establish a reconciliation process for the deal records that drives both systems, run at least monthly rather than only at quarter close.
The payoff is not just cleaner reporting. When comp and attainment are measured against the same data, the incentive structure that drives rep behavior is aligned with the metric the board is watching. Reps optimize for what gets measured in their comp; if that metric diverges from the board forecast metric, reps will rationally maximize the former at the expense of the latter. Alignment at the data layer is alignment at the incentive layer — which ultimately shows up as fewer attainment surprises, not just cleaner spreadsheets.
