Comp Plan Versioning
What is comp plan versioning?
Comp plan versioning is the practice of treating every change to a compensation plan as a new, dated version rather than an edit — so that any past payout can be recalculated against the plan that was actually in force when it was earned.
The alternative, which is what most companies do, is to change the plan in place. The rate cell gets updated. The quota gets overwritten. The accelerator threshold moves. And the November payout is now calculated against a plan that did not exist in November.
The question versioning answers
There is exactly one: which plan was this deal paid under?
It sounds trivial. It is the question behind almost every serious comp dispute, every audit finding, and every restated commission accrual — and in a spreadsheet-run comp process, it is genuinely unanswerable six months later.
What a version needs
The mid-year change problem
The setup. On 1 July, the accelerator threshold moves from 100% to 110% of quota. Marcus closed a deal on 20 June and another on 5 July. He finishes the year at 115%.
What this means?
Without versioning, a mid-year change does not just apply going forward. It retroactively rewrites the past, because every historical calculation is re-run against the current formula. Nobody decided that. It is simply what happens when a plan lives in a cell rather than in a version.
The rep will notice, because their June statement will not match their June payout. And they will be right.
Why versioning matters for finance teams
Three reasons, in descending order of how loudly they will be raised at you.
Audit. Commission expense under ASC 606 must be supportable. "This is what the plan says now" is not support for what was paid nine months ago. Auditors ask for the plan in force at the transaction date, and reviewers of ICM software consistently rank audit trails and versioning as the features that matter most.
Disputes. A rep contesting a payout is almost always contesting a plan interpretation, and the plan they signed is the plan that governs. If you cannot produce it, you lose the argument regardless of the merits.
Restatement. Every un-versioned mid-year change silently restates prior-period commission accruals. That is a close-cycle problem disguised as an administrative one.
Common mistakes with comp plan versioning
1. Editing the live plan
The single most common comp operations failure. It takes four seconds and creates a liability with no expiry date.
2. Versioning the document but not the calculation
A PDF in a folder called v3_FINAL_updated.pdf is not versioning. If the engine that calculates commission does not know which version applies to which deal, the document is decorative.
3. No effective date
A version without a date cannot be mapped to a deal. It is a document, not a version.
How Visdum handles comp plan versioning
Every change in Visdum creates a new plan version with an effective date, a diff of what changed, and a named approver — and the calculation engine reads the version that was in force on the deal's close date, not the version that exists today. That means a June deal is paid under June's plan even after a July change, automatically, without a parallel spreadsheet or a manual carve-out. Reps see which version governs their statement. Finance can reproduce any historical payout on demand, which is the actual definition of an audit trail: not a log of who logged in, but the ability to recompute a nine-month-old number and get the same answer.
Take a self-guided product tour →, or see reporting and compliance.
Related terms
Commission Audit Trail · Plan Sign-off · Plan Component · Recompute · Commission Dispute
Calculate your OTE in 30 seconds
Frequently asked questions
What is comp plan versioning?
Treating every change to a compensation plan as a new, dated version rather than an edit in place. Each version carries an effective date, a record of what changed, a named approver, and rep acknowledgement — so that any historical payout can be recalculated against the plan that was actually in force when the deal closed.
Why does versioning matter for commission?
Because without it, a mid-year plan change retroactively rewrites the past. If the accelerator threshold moves in July and the calculation engine simply re-runs against the current formula, a deal closed in June is now paid under a plan that did not exist in June. Nobody decided that — it is just what happens when a plan lives in a spreadsheet cell.
What should a plan version contain?
An effective date, an end date or superseding version, a diff of what actually changed, a named approver, and evidence the rep acknowledged it. A version without an effective date cannot be mapped to a deal, which makes it a document rather than a version.
Is a PDF in a folder enough for versioning?
No. If the engine that calculates commission does not know which version applies to which deal, the document is decorative. Versioning the plan document without versioning the calculation is the most common half-measure — it produces an archive nobody can use to reproduce a payout.
How does versioning affect an ASC 606 audit?
Commission expense must be supportable, and "this is what the plan says now" is not support for what was paid nine months ago. Auditors ask for the plan in force at the transaction date. The practical test of an audit trail is not a login log — it is whether you can recompute a nine-month-old payout and get the same number.
Can you change a comp plan mid-year?
Yes, and companies routinely need to. The requirement is that the change is versioned with an effective date, so deals closed before it are still calculated under the previous version. A mid-year change applied without versioning silently restates prior-period commission accruals, which turns an administrative decision into a close-cycle problem.