To track setter and closer commissions, record who set the call and who closed it on every payment, as well as on the deal. Then pay each person their rate on the cash actually collected in a fixed pay period, and log refunds as negative lines. The cleanest place to capture all of this is one short form the closer fills in right after the call.
What is a setter and closer commission?
A setter and closer commission is one sale's commission split between two people. The setter booked and qualified the call. The closer ran the sales call and took payment. In high-ticket coaching it is usually a percentage of cash collected, and each person is paid at their own rate.
Rates vary a lot. One high-ticket sales guide says it "could not verify any standard commission rate." For one real example, a published sales commission policy for a high-ticket program pays setters 5% of net cash collected on sales from appointments they booked, and closers a tiered 10% to 20% based on monthly net revenue collected. That is one company's plan.
Define two things in writing before you track anything:
- Cash collected vs. contracts signed. Commission on cash collected is paid when the money lands. Commission on contracts signed is paid when the client says yes, whether or not they ever pay. The same guide advises owners to "pay on cash collected, not contracts signed."
- Net vs. gross. Decide whether processor or financing fees come off first. The policy above calculates all setter and closer commission after a 15% financing fee from its pay-later provider.
Why are setter and closer commissions hard to track?
The three facts you need live in three places. Who set the call is in the CRM or the booking tool. Who closed it, and what happened, is in the closer's head until they update the CRM. The cash is in Stripe or a financing provider. Payday means joining all three by hand in a spreadsheet.
Where it usually breaks:
- The CRM has one owner per record. In HubSpot, one workaround from the community forum is to copy the contact owner into a custom "Setter" property when a lead arrives, then into a "Closer" property when the lifecycle stage changes. In GoHighLevel, a setting called "Allow different owners for contacts and its opportunities" lets the setter keep the contact while the closer owns the deal (tutorial). Both only work if someone keeps them current.
- The payment doesn't know who closed it. Stripe lets you store key-value metadata on objects, but its docs say metadata "doesn't automatically copy to related objects," apart from a few listed cases. If the closer isn't on the payment, you end up matching by email at the end of the month.
- Payment plans. A program sold on three installments creates three commission events. A spreadsheet can easily pay it once and miss the rest, or pay the full amount up front.
- Refunds. A refund after commission was paid needs to come off the next payout. If nobody links the refund to the original sale, it doesn't.
How do you track setter and closer commissions, step by step?
Write the plan down, record the setter at booking and the closer right after the call, tie every payment to that close, and run payouts on a fixed calendar. These steps work in a spreadsheet, a CRM or custom software. What changes is how much gets typed by hand, and how often someone forgets.
- Write the commission plan. For each role, write down the rate, whether it's on cash collected or contract value, net or gross of fees, the pay period (twice a month or monthly) and what happens on refunds and chargebacks. Add manager overrides if you pay them.
- Record the setter when the call is booked. Use a hidden field on the booking form, a setter field on the contact or a team "set" form. Attach the setter before the call happens so nobody has to remember it later.
- Have the closer fill in a post-call form after every call. It captures the outcome (closed, follow-up, no-show, not qualified), amount, payment plan, processor and notes. Commission is built from this record. If it's optional, it won't get filled in.
- Tie each payment to the closing call. Tag the payment with the deal or call ID. With Stripe Payment Links and Checkout,
payment_intent_data.metadatasaves data onto the underlying PaymentIntent, and Stripe webhooks include that metadata, so an automation can match cash to the close. - Turn each payment into one commission line per person. A $2,000 payment with a 5% setter and a 10% closer is two lines: $100 and $200. Each installment creates its own lines when it is collected.
- Log refunds as negative lines. Use the same people and the same rates with a negative amount. It comes off their next payout.
- Close the period and pay. At the cutoff, lines in that period are owed. Mark them paid with the date. Anything collected after the cutoff goes to the next period.
- Let each rep see their own lines. Setters and closers should see every line they're paid on, and nobody else's. CaptivateIQ suggests a rep-facing view so people can see how cancellations affect their pay.
Example: one sale on a payment plan
These numbers are illustrative only. A $6,000 program is paid in three installments of $2,000, with the setter at 5%, the closer at 10% and no fees deducted.
| Event | Cash collected | Setter (5%) | Closer (10%) |
|---|---|---|---|
| Installment 1 | $2,000 | $100 | $200 |
| Installment 2 | $2,000 | $100 | $200 |
| Installment 3 | $2,000 | $100 | $200 |
| Installment 3 refunded | -$2,000 | -$100 | -$200 |
| Total | $4,000 | $200 | $400 |
Each row lands in a specific pay period, so you can check any number when a rep asks about it.
How should refunds and clawbacks work?
A clawback is when the company takes back commission it already paid because the sale didn't hold. QuotaPath describes it as typically deducted from a later commission check, and says it needs to be in the written comp plan. Set a time window, decide full or partial, and explain it before the first sale.
Choices to make:
- The window. QuotaPath cites HubSpot's own policy, where cancellations in the first four months trigger a clawback and after that the rep keeps the commission. CaptivateIQ suggests 30 to 90 days for short-term products. Match yours to your refund policy.
- Hold or claw back. Some teams don't pay until the refund window closes, so there's nothing to recover. That's cleaner for the books and harder on reps' cash flow. Paying per installment collected already limits how much is at risk on payment plans.
- Partial refunds. Claw back in proportion to what was refunded.
- Chargebacks and financing. Treat a lost dispute like a refund. If a financing provider pays you net of a fee, decide in the plan whether commission is on the net.
- Legal check. CaptivateIQ notes some US states restrict withholding wages without the employee's written consent. If your reps are employees, have the terms reviewed.
Should you use a spreadsheet, CRM or commission software?
A spreadsheet works for a few reps with simple rates, if one person owns it. CRM fields record who set and who closed, but they don't do the math. Commission software handles rates and statements but still depends on clean CRM and payment data. Commission stays accurate when the close, the call notes and the cash sit in the same record.
| Option | Good at | Where it breaks |
|---|---|---|
| Google Sheets or Excel | Free, flexible, quick to start | Manual joins between CRM and Stripe; installments and refunds get missed |
| CRM fields (HubSpot, GoHighLevel) | Recording who set and who closed | Doesn't calculate per-installment commission or clawbacks on its own |
| Dedicated commission software | Rates, tiers, statements, approvals | Only as accurate as the CRM and payment data feeding it; another subscription |
| Zapier or Make | Moving data between tools | Can fail quietly when a field changes; still needs somewhere to store the lines |
| One backend with calls, cash and payouts together | Commission straight from the post-call form and payments | Has to be built and set up around your business |
How does Second Level OS handle payouts?
In a Second Level OS build, commission comes from the closer's post-call form. After the call, the closer fills in one short form that moves the deal to won, logs the payment and works out commission. Payouts then pays the closer, setter and manager override on cash collected from those call notes, each at their own rate, twice a month or monthly.
Second Level OS is a done-for-you service that builds and runs custom software for high-ticket coaching businesses, with leads, calls, closes, cash, payouts and the team in one place and AI on top. Payouts is one of the parts most builds start with, and it follows the steps above. Refunds claw back automatically. Reps see only their own row, and there's a CSV export for whoever runs payroll. Your existing CRM (GoHighLevel, HubSpot or Close) and Stripe stay connected. See what's inside or read what Second Level OS is.
If payday still means a spreadsheet, a Stripe export and a few DMs asking closers what happened on a call, start with the Backend Blueprint call. We go through how your business runs today and map out what would be built. Map my backend.