Sales Commission Recovery Services
Lanshore takes over sales commission implementations that are not paying correctly and brings them back to a controlled monthly cycle. The order of work is deliberate: stabilize the cycle you are in now so people get paid, diagnose whether the failure is the plan, the data, or the configuration, and only then decide whether the build is repaired or replaced. In one engagement for a multi-billion-dollar software company whose commission process had been broken for over a year, payments were going out on manual overrides and every cycle added more workarounds on top of a mis-architected implementation; the redesign restored systematic calculation accuracy, eliminated the manual override layer, and re-established a controlled, repeatable monthly cycle.
Doug Erb, Founder & CEO · Updated
Doug Erb founded Lanshore and has designed, built and run sales compensation systems since 2000, from Callidus and Trilogy through Varicent, Xactly, CaptivateIQ, Performio and SAP Commissions. He also leads the firm's AI and automation practice and its energy programs, including program management of a $53M greenfield S/4HANA implementation at PEMEX.
Who it is for
Companies where the commission system is live and wrong. Typical callers are a VP of Sales Operations whose reps no longer believe their statements, a Head of Incentive Compensation who has inherited a build nobody can explain, or a CFO who cannot sign off on the accrual. The common pattern is a cycle that only closes because two or three people apply manual adjustments they carry in their heads, and an implementation partner who has either left or is the reason you are calling. It also fits teams mid-implementation who can already see the first live cycle will not be right.
The problems it solves
The override layer has become the system
When the engine stops producing payable numbers, someone starts adjusting them by hand. Within a few cycles the overrides are load bearing: they encode plan rules that were never configured, and nobody can say which numbers the system produced and which a person did. This is the first thing to unwind, because every other diagnosis is unreliable while it is in place, and it is the single clearest audit finding in a commission program.
Nobody can say what the system is supposed to do
Most failed builds have no plan specification. The configuration became the specification, so there is no document to test the system against and no way to tell a defect from a design decision. Rebuilding without reconstructing that document first just produces a second system nobody can verify.
The real failure is usually upstream
Teams call about the commission platform, and the cause is often the crediting data arriving from CRM, ERP, order or billing systems: a missing flag, a hierarchy that changed without anyone telling comp, territories that do not match the rosters. Replacing the platform without fixing the feed reproduces the same failure on a newer screen.
Trust is gone before the numbers are fixed
By the time a recovery starts, reps are keeping their own spreadsheets and disputes arrive before statements do. Fixing the calculation does not by itself fix that, because nobody believes the new number either. The recovery has to produce something a rep can check themselves, and an explanation of what changed and why, or the dispute volume stays where it is.
Deciding between repair and rebuild
This is the expensive judgment and it gets made emotionally, usually against whoever delivered the original build. Some implementations are structurally sound with a handful of wrong rules. Others are mis-architected in ways that make every future plan change a custom project. The decision should rest on how the build handles the hardest components you actually pay, not on how the last project felt.
How Lanshore delivers it
- 1
Stabilize the current cycle
The first priority is paying people on time while the diagnosis happens. We work the cycle with your team, document every manual adjustment as it is made rather than afterward, and get the overrides out of people's heads and into a record. That record becomes the main evidence for what the system is failing to do.
- 2
Reconstruct the plan specification
We rebuild the document that should have existed: crediting rules to the field level, accelerator and cap interactions, overlay and split treatment, draws and clawbacks, retroactive quota handling. It is written against the plan clauses it implements, so there is finally something to test the system against. You keep it whether or not we do the rebuild.
- 3
Diagnose plan, data, and configuration separately
We reconcile a full cycle three ways: what the plan says you owe, what the source data supports, and what the system calculated. Variances get attributed to a named cause rather than argued about. This is what separates a configuration defect from a crediting feed problem from a plan that was never implementable as written.
- 4
Recommend repair or rebuild, with the reasoning written down
We test the existing build against your hardest plan components and say plainly which path we recommend and what each costs in time. Lanshore implements nine SPM platforms and resells none of them, so a recommendation to move platforms is not a commission for us, and neither is a recommendation to stay.
- 5
Fix, run in parallel, and prove it
Whichever path is chosen, the corrected calculation runs in parallel against the current one across a full cycle including a month-end, with every variance resolved to a named cause before anyone is paid from it. Restated history is reconciled where clawbacks and disputes reach backward.
- 6
Hand back a cycle your team can run
Recovery is not finished when the numbers are right, it is finished when the cycle closes without heroics. We document the configuration, train the administrators, and can run comp operations as a managed service if there is no one in seat to hold it.
Platforms we deliver on
Related case studies
- Architecture redesign to fix a broken compensation process
Commission process broken for over a year, restored to systematic accuracy
- Linking sales commission data between financial systems and CRM
Manual link between financial systems and CRM fully automated
- Tackling resource challenges with expert advice and managed services
Error-prone manual Excel commission process replaced with managed operations
Related: SPM consulting for complex compensation plans · Audit-ready payout transparency · SPM managed services
Sales Commission Recovery Services: FAQ
- Can you take over an implementation another partner started?
- Yes, and it is a large share of this work. We do not require that the original build be scrapped. The first step is the same either way: stabilize the current cycle, reconstruct the plan specification that is usually missing, and reconcile a full cycle so the failure is attributed to the plan, the data, or the configuration rather than to whoever is in the room.
- How quickly can we stop paying people incorrectly?
- Stabilizing the cycle so payments go out on time with every adjustment documented is usually the work of the first cycle or two, because it is process and evidence rather than reconfiguration. Correcting the underlying calculation takes longer and depends on which of the three causes is in play. A crediting feed problem can be fixed quickly once identified. A mis-architected build that needs replacing is a project, and we will say so rather than let it arrive as a surprise.
- Should we rebuild on the same platform or move?
- Test the existing build against the hardest components you actually pay: multi-level crediting, overlapping territories, retroactive quota changes, restatements. If the platform can express those natively and the problem is how it was configured, rebuilding in place is usually faster and cheaper. If the build only works through custom logic that one person understands, that will keep happening. Lanshore resells none of the nine platforms it implements, so neither answer pays us differently.
- What do we do about the historical errors?
- Quantify them before deciding, because the answer is a policy question rather than a technical one. We reconcile the affected periods and show who was overpaid and underpaid and by how much. What you do then, correcting forward, recovering, or absorbing, depends on your plan documents, your jurisdiction, and your own legal and payroll advice, which we do not substitute for.
- How do you rebuild rep trust once statements are wrong?
- By making the number checkable rather than by asserting it is now correct. That means statements that show the underlying transactions and the rule applied, a dispute path with a stated response time, and a direct explanation of what changed and which periods are affected. Dispute volume returning to a normal level is a better signal that the recovery worked than any internal reconciliation.
Talk to Lanshore
A 30-minute call. We look at your plans, your systems, and where this would change your comp operations first.
