The biggest trust break in sales comp isn't a policy dispute — it's a rep running their own math and getting a different answer than the statement shows. Reps check their own calculations more than you think. And when their math says $12,500 and yours says $11,850, they don't assume you're right. They assume they're right and you've shorted them. Whether the truth is a rep misunderstanding or a genuine engine error, the trust cost is the same.
This tool is an independent second-source check. Enter the key parameters for one deal (amount, rep's YTD attainment, quota, base rate, accelerator structure) plus the actual commission your engine paid. The tool computes what it should have paid using straightforward base + accelerator math, flags the variance, and offers likely causes if the numbers don't match.
The math this tool uses
Base + single-accelerator model
We assume a standard commission structure: a base rate applied to every dollar of credited revenue up to an accelerator threshold, then an accelerated rate applied to dollars above the threshold. The threshold is expressed as % of annual quota (typically 100% — i.e., accelerators kick in at full quota attainment).
How the deal splits across the threshold
For each deal, the tool checks the rep's YTD attainment before the deal and the YTD attainment after. If the whole deal falls below the threshold, everything is paid at base rate. If it's entirely above, everything gets the accelerated rate. If the deal straddles the threshold (some below, some above), the portion below gets base and the portion above gets accelerated. This is the most common source of variance with engines that handle the straddle case incorrectly.
What this tool does NOT model
Multi-tiered accelerators (2 or more thresholds), decelerators, caps, draws, payout frequency effects, credit splits, and product-specific rates are all out of scope. This is an intentional simplification — the tool validates the core math, not the full plan. If your engine's output matches this tool's output on base+single-accelerator cases, it's highly likely the engine is correct on the core logic. Deviations in complex cases are a separate investigation.
Most real engine errors happen in the straddle case or in the YTD-attainment calculation, not in the base math. By asking for YTD attainment pre-deal and post-deal (or just pre-deal + deal amount, from which we derive post-deal), we can re-run the straddle logic and see whether your engine got it right. The rest of the inputs are sanity checks.
Calculation Accuracy Checker
Enter one deal + your engine's output. We'll re-calculate and flag variance.
ℹ️ How this tool works +
The question it answers: Is my engine's commission calculation correct on this deal — and if not, what's the likely cause of the variance?
What to enter:
- Deal Details: the deal amount ($) being credited, the rep's annual quota ($), and their YTD attainment before this deal ($).
- Plan Structure: base commission rate (%), accelerator threshold (as % of quota — typically 100), accelerator rate (%).
- Engine Output: the actual commission ($) your engine paid for this deal.
What the math does:
- Calculates the dollar value of the accelerator threshold (quota × threshold %).
- Determines how much of the deal falls below vs above the threshold, given the rep's YTD attainment.
- Applies base rate to below-threshold portion, accelerator rate to above-threshold portion.
- Compares result to the engine's actual output and reports the variance.
What you'll get back:
- Expected commission + actual commission + variance, with a band: Accurate (<1%), Minor (<5%), Material (<10%), Investigate (≥10%).
- Step-by-step calculation breakdown showing how we arrived at the expected number (split across threshold if applicable).
- A ranked list of likely variance causes with investigation guidance (only shown when variance > 1%).
Sample values pre-loaded — click "Check Calculation" immediately to see the output shape. Supports base + single-accelerator plans; does not model caps, decelerators, multi-tier thresholds, or credit splits.
Benchmarks, ranges, and default values in this tool reflect Falcon's practitioner experience across consulting engagements. They are directional starting points, not substitutes for market survey data. For binding compensation decisions, validate key figures against Radford, Mercer, Carta, or WorldatWork survey data for your specific geography, industry, and company stage.
How to interpret the variance
Accurate (<1% variance) — No action needed
Your engine's output matches independent re-calculation. Small variances at this level are almost always rounding differences (fractions of a cent compound over many deals). Move on.
Minor (1–5% variance) — Log and monitor
A variance this small usually indicates a plan-configuration difference rather than a math error — perhaps a rounding rule, a commission-rate entered as 8.00 vs 8.0, or a calendar-day proration. Document the specific deal, check 2–3 similar deals, and if the pattern repeats, dig into engine configuration.
Material (5–10% variance) — Investigate this cycle
The gap is too large to be rounding. Most likely cause: the straddle case (deal crossing the accelerator threshold) is being handled incorrectly. Second most likely: the engine is using a different YTD attainment number than expected. Halt the current cycle's payout on this rep pending investigation.
Investigate (≥10% variance) — Stop payout, diagnose
Do not release the payout to this rep until you understand the discrepancy. 10%+ variance on base+accelerator math indicates either a material plan-configuration error (wrong rate, wrong threshold) or an engine bug. Root-cause before proceeding — releasing the wrong payout and clawing back is worse than a 1-day delay.
If you find a material variance, run at least 5 more deals through this tool before accepting any engine output this cycle. Single-deal errors can be anomalies; pattern errors indicate systemic issues. And when you find the root cause, retroactively re-check prior months — the same error probably affected past statements without being caught.
Engine outputs not matching your expectations?
We help SalesOps teams audit commission engines and find the root cause of systemic variance — not just one-off mismatches. Book a 20-minute review.
Book a 20-minute consultation →FAQ
Not for the direct check. But you can use it to validate the base-to-first-accelerator portion by treating your first accelerator as the threshold and first accelerator rate as the accelerated rate. If that matches cleanly, the first tier is correct. Run it again with the second tier as threshold to validate that layer. Not perfect but catches most errors.
This tool does not model caps. If your deal would push the rep above the cap threshold, the tool's expected number will be higher than the capped actual. That'll read as variance but is legitimate. Run the check on non-capped deals to isolate real errors from cap-driven variances.
Enter the split-adjusted deal amount for the rep you're checking. On a $100K deal split 70/30, run the check on $70K for the primary rep. The math works on the credited amount, not the gross deal amount.
For one deal, yes. Across many deals, a systematic 0.5–1% variance that consistently favors the company can indicate a rounding convention that disadvantages reps. Reps who track their pay will notice this pattern across months even if no single deal crosses the "worth disputing" threshold.