The Duplicate Commission Line That Had a Sales Team Chasing Money They Had Already Been Paid

Most incentive pay problems start small. A metric drifts a little from what it is supposed to measure, a rule gets applied inconsistently from one pay period to the next, or two systems end up tracking the same thing without anyone deciding which one is the source of truth. None of that looks urgent on its own. Then a rep asks why their check does not match what an app is showing them, and the owner realizes they are now the referee for a dispute they did not know was brewing.

That is roughly what happened at a small home services company that sells and installs window treatments and interior furnishings, running a two-person inside sales team out of a single office. The company had a legitimate, well-intentioned sales incentive: a commission on closed sales, paid out automatically through payroll every pay period. That part worked fine on its own. The trouble started when the same incentive also showed up, separately, inside ShareWillow as its own commission line item, tracked and displayed to the reps like it was a second, unpaid amount.

It was not a second amount. It was the same money, counted twice on paper. But the reps had no way of knowing that just from looking at their dashboard. They saw a commission line inside ShareWillow, assumed it was still owed to them, and asked the owner about it. Then they asked again the next pay period, because the number was still sitting there. The owner ended up doing the same manual explanation over and over: that money already hit your check through payroll, this is not new money, ignore this line.

A display bug that would have paid out an incomplete quarter

Underneath the duplicate-tracking problem was a second, sharper issue. One of the two reps had a quarterly sales threshold to hit, tied to a close-ratio qualifier, before she was eligible for a bonus tied to that period. Partway through the quarter, with her close ratio sitting at 93 against a required 120, the plan was still showing her as on track to receive a $600 payout. The threshold existed to make sure the bonus reflected a full quarter of qualifying performance. In practice, partial progress toward that number was rendering as if it had already been cleared.

That is a dangerous kind of bug precisely because it is invisible until someone is looking for it. A rep glancing at the app sees a dollar figure next to her name and reasonably assumes it reflects what she has earned. An owner who is not cross-checking every qualifier manually every pay period has no easy way to catch a partial-progress number rendering as a completed one. Left alone, it would not have surfaced as a real problem until the actual payout ran, at which point the company would have had to either pay out $600 that had not been earned under the plan's own rules, or claw back an expectation the rep had already been shown as true.

Put the two problems next to each other and the shape of the situation becomes clear. One system was showing money that had already been paid as if it were still outstanding. Another qualifier was showing a bonus as earned before the quarter's rules had actually been satisfied. Neither problem was a philosophical disagreement about how the plan should work. Both were the plan quietly telling the team something that was not true, and the owner was the one fielding the resulting confusion, pay period after pay period, without a clean way to explain it.

Deleting the redundant plan instead of patching around it

Working with ShareWillow, the company made the less obvious but more durable choice: instead of trying to explain the duplicate line item better, it deleted the redundant plan entirely. The payroll-based commission stayed exactly where it was, inside payroll, where it belonged and where it was already working. The parallel commission line inside ShareWillow that had been shadowing it was removed, so there was only ever one number for a rep to look at for that incentive, not two.

In its place, the team consolidated everything into a single, clearly named quarterly sales bonus. Instead of a rep needing to mentally net out a payroll commission against a ShareWillow line to figure out what they actually still had coming, there was one plan, one number, and one place to check it. That single change removed the entire category of "is this the same money or different money" questions the owner had been fielding.

The close-ratio qualifier got the more structural fix. Rather than let partial progress toward the 120 threshold render as a partial payout or, worse, a fully eligible one, the qualifier was rebuilt as all-or-nothing. A rep sitting at 93 against a required 120 now shows exactly what she has: progress toward a bar she has not cleared yet, with no dollar figure attached until she actually clears it. The fix does not just correct a display bug. It aligns what the app shows with what the plan document has always said the rule was supposed to be.

This is part of their payroll, so it's not an award, and it's kind of an extra step I have to do. That's been the source of the most confusion with my employees. They thought they'd get it from ShareWillow. I'm like, no, no, you've already been paid for that.

The owner also changed how the team engages with the plan day to day. Total-to-date sales now get updated every two weeks instead of left stale between check-ins, so both reps can watch their progress toward the $1,200 quarterly tier build in something close to real time, right from the plan's home screen in the mobile app. That is a small operational habit, but it matters: a plan that only gets checked when someone is confused about a check is a plan that generates confusion by default. A plan that gets glanced at every two weeks, with numbers a rep can actually trust, becomes something closer to a running scoreboard instead of a recurring dispute.

None of this required the company to change what it wanted to reward. Sales performance was always the right thing to pay for, and the payroll commission that had been doing that job correctly never needed to move. What changed was making sure there was exactly one place to look for the truth, and that the truth being shown actually matched the rules the plan was built on.

Watching the fix land, live, in the same session

The clearest proof the fix worked did not take a full quarter to show up. It happened in the same working session where the qualifier got rebuilt. The moment the close-ratio requirement switched from a soft, partial-progress read to a hard all-or-nothing gate at 120, the rep sitting at 93 immediately stopped showing an eligible $600 payout. No adjustment, no manual override, no argument to have later at payout time. The plan simply started reflecting what its own rules had always intended.

In the same session, the second rep, who had actually cleared both her sales kicker and her close-ratio bar for the quarter, was correctly confirmed for her payout. That side-by-side moment is worth sitting with: one rep's number corrected downward to zero because she had not earned it yet, and another rep's number held steady because she had. That is what a plan working as designed looks like from the inside. Nobody has to argue about it, because the number and the rule finally agree.

The structural cleanup also simplified what the team has to manage going forward. The company went from two overlapping tracking systems and five KPIs down to one plan and four KPIs. A fifth metric, average sale value, was retired in the same pass because a CRM migration had made it impossible to calculate cleanly, and there is little value in a plan carrying a metric nobody can actually verify. Fewer moving parts is not a consolation prize here. It is the entire point: a plan that is simpler to check is a plan that is harder to quietly get wrong.

What this means for your shop

This was not a dramatic rebuild. It was a small team's incentive plan getting untangled from a redundant tracking system and a soft threshold that had drifted from what it was supposed to enforce. A few lessons carry over to almost any shop running commission or bonus pay.

• One incentive should live in exactly one place. If the same commission shows up in payroll and in a separate tracking tool, you have built a system that will generate confusion on a schedule, whether or not the numbers are technically correct.
• Qualifiers should be all-or-nothing when the rule is all-or-nothing. If a threshold exists to gate a payout, make sure the software actually gates it. A qualifier that lets partial progress render as a completed one will eventually pay out money nobody signed up to pay.
• Cross-check live, not just at payout time. The bug in this plan was only caught because someone looked closely at a specific rep's numbers before the pay period closed. Waiting until payout to notice a discrepancy is waiting until it is already expensive to fix.
• Retire metrics you can no longer verify. A KPI that survives a system migration in name only, with no clean way to calculate it, is worse than no KPI at all. It just sits there looking official.
• Make the plan easy to check without asking the owner. Updating numbers on a predictable cadence, and putting them somewhere a rep can pull up on their own, removes the owner from the role of manual translator between the plan and the paycheck.

A commission plan that needs constant explaining is usually a sign that something underneath it, not the reps asking the questions, needs fixing. For home services companies running sales incentives through payroll, a second tracking layer can quietly turn a simple bonus into a recurring source of confusion. ShareWillow consolidates incentive tracking into a single source of truth, with qualifiers that actually enforce the thresholds they are built around, the same kind of accuracy fix behind how a GPS tracking bug was inflating a technician's overtime by nearly half. See what a single, accurate incentive plan would look like for your team, based on what we have learned from over 200 service businesses.