The 6-step Commission Cycle
Every commission cycle moves through six steps. Each is auditable, version-locked, and signed off - that's how a 99%-accurate cycle differs from a 90%-accurate one.
Every commission cycle starts with data - bookings from CRM, account hierarchies from ERP, employment data from HRIS, refunds and cancellations from billing. The Gather step is responsible for getting all of it into the calculation engine on a defined cadence with no manual prep.
Activities
- Pull bookings from CRM (closed-won deals)
- Pull account hierarchies and territory assignments
- Pull employment status from HRIS
- Pull refunds, cancellations, and billing adjustments
- Pull plan version and effective-date metadata
- Snapshot every input for audit-trail purposes
Outputs
- Frozen dataset for the calculation cycle
- Audit-trail row per source with timestamp
- Data freshness report for SalesOps
Risks
- Stale CRM stages - deals not actually closed
- Missing account hierarchy updates after reorgs
- Refunds processed in billing but not flagged to ICM
Validation is what separates a 99% accuracy commission process from a 90% one. Pre-calc validations check field completeness, owner assignments, hierarchy currency, and product mappings. If any check fails, the cycle pauses for SalesOps remediation - never ships statements with bad data.
Activities
- Validate deal stage = closed-won + signed contract attached
- Validate account owner non-null and current
- Validate hierarchy + territory + plan-version assignments
- Validate product / SKU mappings to commissionable rate-card
- Reconcile total bookings vs. CRM and finance source
- Surface failures to RevOps with remediation owner
Outputs
- Cleaned, validated dataset ready for rule application
- Validation-pass certificate with hard-stop on failure
- Remediation queue for SalesOps
Risks
- Invalid deals counted toward attainment
- Mis-assigned accounts crediting the wrong rep
- Currency conversion errors on multi-region plans
Calculation applies plan rules in a defined order: crediting → attainment → tier rate → accelerator → kicker → adjustment → hold-and-release. Each step is auditable, reproducible, and version-locked to the plan as of the deal effective date. The same deal calculated in May and again in December should produce identical results.
Activities
- Apply crediting rules (territory + ROE + splits)
- Compute attainment per period and per quota line
- Apply tier rate and accelerator math
- Apply kickers and conditional bonuses
- Apply hold-and-release / clawback adjustments
- Generate per-rep, per-deal calculation log
Outputs
- Per-rep payout amounts with deal-level detail
- Calculation log with rules applied at each step
- Pre-statement summary for manager review
Risks
- Plan-version mis-match on retroactive adjustments
- Splits not summing to 100% (or overlay total >100% by design)
- Accelerators applied to dis-allowed components
Calculations route to managers for approval before statements go to reps. Managers verify deal-level credit, surface exceptions, and approve any manual adjustments. The approval workflow is signed and timestamped - feeding directly into the audit trail. Exceptions are routed for SalesOps + Finance review.
Activities
- Manager review of team statements with deal-level detail
- Surface exceptions and disputes via workflow
- Apply approved adjustments with rationale
- Sign off on team-level totals
- Route material exceptions to SalesOps + Finance
- Lock the calculation period for audit
Outputs
- Manager-approved per-rep statements
- Adjustment log with rationale + approver
- Exception report for SalesOps escalation
Risks
- Manager rubber-stamping without review
- Adjustments applied without rationale
- Exceptions discovered too late for cycle
Statements ship to reps via the rep-facing portal with deal-level detail and click-through to CRM. The payroll file is delivered to AP / payroll for the cycle's pay date. A typical SLA: statements live by day 5, payroll file by day 7-8 of the new period.
Activities
- Publish statements to rep portal
- Email and notify reps of statement availability
- Open the dispute / acceptance window
- Deliver payroll file to AP / Payroll
- Post amortization entries to GL (ASC 606)
- Record pay-cycle batch for audit trail
Outputs
- Rep-facing statement with deal-level detail
- Payroll batch delivered to AP
- GL journal entries posted
- Statement-acceptance and dispute portal active
Risks
- Rep statement formats inconsistent with prior cycle
- Payroll file format mismatch
- GL entries missing cohort tags for ASC 606
The cycle isn't complete when statements ship - it's complete when disputes resolve, true-ups process, and patterns feed back into the next plan iteration. A clean adjustment log + monthly trend reporting separates a SalesOps team from a fire-fighting team.
Activities
- Triage dispute queue against published SLA
- Apply true-ups for late-arriving deals
- Process clawbacks for refunds / cancellations
- Aggregate disputes monthly to identify systemic gaps
- Update Rules of Engagement based on patterns
- Run quarterly comp-pulse with reps
Outputs
- Closed dispute log with rationale
- True-up adjustments posted to next statement
- Quarterly plan-effectiveness report
- Updated ROE document
Risks
- Dispute backlog growth (>5 business days)
- Repeat issues without ROE updates
- True-ups missed - quiet under-payment to reps