Skip to main content
Last reviewed: 2026-08-29 · Reading edit: 2026-09-06 Decide when commission is earned and paid before announcing a compensation plan. A signed contract, an invoice, and collected cash are different events. Make any repayment or draw rules clear, and have the policy reviewed for the jurisdictions where the team works. Define the earning event; Set the payment schedule; Explain adjustments Reading guide: define the earning event → set the payment schedule → explain adjustments.

Use this when

  • Commission pays at booking and finance is surprised by early churn, refunds, or never-collect.
  • New hires cannot live on base during a long cycle, so someone invented a “temporary extra” with no end date.
  • Reps call commission monopoly money because reversals can appear for a year.
  • Draws are how you hide a quota or a territory that cannot work—see GTM planning.

Do not use this when

  • There is no written plan and no credit event. Write sales compensation first.
  • You need RevOps leaders paid for systems they own. That is RevOps compensation, not a clawback clause.
  • Legal, works council, or payroll must set recovery. This page will not override that.

A few useful terms

Keep this in mind

Pay timing follows revenue risk. The earlier you pay relative to cash and retention, the more you need a written recovery or a holdback. A draw is a bridge for timing, not a subsidy for a book that cannot hit quota. If draws are common, the plan, the territory, or hiring is wrong—do not extend the draw.

How to do it

Step 1: Define when revenue earns credit

On the same page as the credit event, write the risk: cancel, refund, non-payment, never go-live, contraction after signature. If those events are rare and collections are boring, you can pay mostly at booking and claw back only the ugly cases. If the motion is usage, implementation-heavy, or cash-fragile, paying 100% at signature is how you fund finance’s surprise. Holdback and clawback are substitutes. Holdback is quieter: you never handed over the risky slice. Clawback is louder: you paid, then you take it back. Choose on purpose.

Step 2: Explain repayment and adjustment rules

If you pay before the dollar is safe, clawback (or holdback) is part of the plan, not a Q4 exception. A policy that can be administered:
  1. Triggers in the plan (cancel, refund, non-pay, no go-live—not “finance is unhappy”).
  2. Window with a start and an end. Operators who run recovery as a system tend to keep windows short and known. A year-long sword trains people not to trust the paycheck. Write your days; do not paste a vendor’s 60–120 as law.
  3. Recovery method (usually future commissions, with a carry-forward if one period cannot absorb it).
  4. Cap per cycle so one reversal does not zero a household. A cap is a policy choice; if you skip it, say why.
  5. Quota treatment. A common operator choice: reverse commission dollars, not the quota credit, so the next period does not start from a hole you already punished in cash. If you reverse quota too, write that—it is a different job.
  6. Visibility. Which deals are still inside the window, when it ends, what a trigger would do. A surprise deduction is a dispute factory.
  7. Who calculates, in what system, by what date. Spreadsheet clawbacks without an audit trail are how ops refuse the policy.
Cash and the balance sheet change posture. A company that cannot fund commissions on uncollected bookings should pay less up front, not write a meaner novel after payroll.

Step 3: Define any temporary draw carefully

Ask: is there a timing gap (effort now, earnings later) that the person does not control? New-hire ramp on a long cycle, a territory reset you caused, a plan migration, delayed lead flow you own. If the answer is “they are missing quota,” that is not a draw. That is sales compensation and territory math. Recoverable when the risk is their ramp and future production. Non-recoverable when the company created the disruption and you want a clean window (plan change, delayed product, book timing you broke, leave coverage). The type matters less than whether you should offer one at all. Guardrails that keep draws from becoming pay:
  • Time-boxed (start and end dates). Stretching past a cycle because “they’re trending” is usually a plan problem.
  • Amount as a fraction of target monthly variable, not a vibe. Replacing more than the target variable quietly buys above-plan pay.
  • Documented before day one: amount, dates, recovery, what happens on termination—counsel on that last line.
  • No stacking a full draw on reduced quota and a guarantee unless you intend above-target cash during ramp.
  • Exception governance: sales leadership + finance approve; monthly list of balances and exception count. When the list is long, stop hiring into the same math.

Step 4: Keep the plan administrable

If CRM + billing + a named ops owner cannot flag the trigger, apply the cap, and show the rep the window, shorten the policy until they can. Buying an ICM tool to rescue an unwritten clawback is how you implement last year’s argument. Software names for a job still start in TOOLS.md; this page is the rule the tool must run.

Worked example (illustrative)

Annual SaaS, invoice in 30 days, rare non-pay. Eight AEs. Not a benchmark. Copy the empty fields. Do not copy the 90 days or the 80/20 split as market law.

Copy: clawback / holdback (fill)

  • Credit event (from the plan):
  • Revenue risks we will not ignore:
  • Pay at credit vs holdback vs pay-on-cash (and why):
  • Triggers:
  • Window (start / end):
  • Recovery method and cap per cycle:
  • Quota: reverse dollars only / reverse credit too:
  • Where the rep sees remaining risk:
  • Calculator, system, payday:

Copy: draw exception (fill)

  • Why this is timing, not a broken quota:
  • Role:
  • Recoverable or non-recoverable (who caused the disruption):
  • Monthly amount (vs target monthly variable):
  • Start / end (no “until they’re ramped”):
  • Recovery mechanics and cap:
  • Interaction with ramp quota and any guarantee (stack? yes/no):
  • Termination / transfer (counsel):
  • Approvers:
  • Monthly balance owner:
Working file: incentive-timing.xlsx.

Before you start

  • The written plan already names the credit event; this page does not invent a second one.
  • Holdback vs clawback vs pay-on-cash is a choice, not a surprise.
  • Triggers, window, recovery, cap, and quota treatment fit on one page.
  • Reps can see which deals are still at risk.
  • Draws have dates; they are exceptions with a monthly list.
  • Draws are not stacked onto a quota the book cannot hit.
  • Ops can run this without heroics, or the policy got simpler.
  • Counsel has seen recovery and termination language if employment rules apply.

Metrics

Do not count “we have a clawback clause” or resemblance to a vendor PDF table as control.

Common mistakes

  • Paying 100% at booking on a motion where cash or go-live is the real event, then arguing in Q4.
  • A window so long the paycheck feels fictional.
  • Recovering quota and cash without saying so, so the next period is a punishment lap.
  • Draws as the default for anyone missing number.
  • Recoverable vs non-recoverable chosen by whoever shouted.
  • Stacking draw + reduced quota + guarantee and calling it ramp.
  • No cap, then a single reversal zeros the period.
  • Spreadsheet recovery with no audit trail and no rep view.
  • Pasting another company’s 70/30 split, 90-day window, or role-by-role draw grid as if it were your cash position.
The rest of the plan is sales compensation. Ops leaders are RevOps compensation. Whether the book can hit quota is GTM planning. The record that billing and CRM must share is CRM data model. New sellers still need a curriculum: SDR onboarding.

Sources and evidence boundary

This is an owner-maintained operating synthesis. It is not a licensed compensation product, not a salary survey, and not legal advice. Clawback as a designed mechanism (triggers, window, recovery from future pay, visibility, cash-posture), holdback as an alternative to paying the risky slice, and draws as time-boxed exceptions (recoverable vs company-caused non-recoverable, no stacking, monthly exception count) are distilled from public RevOps/finance reports on clawback policy and sales draws (QuotaPath clawback playbook; QuotaPath sales draws). Those pages are method prompts, not sources to copy. Conversation counts, percentages, payout-mix tables, role grids, and product pitches in those reports are not this library’s facts or a requirement to buy their software. Named customer anecdotes in the reports stay theirs.
Copyright © 2026 Ivan Xu. All rights reserved. See the copyright and reuse terms. Canonical source: github.com/weilun88313/B2B-Playbook