Company profile
| Company | Meridian Networks (composite) |
|---|---|
| Business | Network management software |
| Growth | Three acquisitions in thirty months |
| Sales organization | 1,900 quota-bearing members across 38 countries |
| Situation | Four compensation plans and four payment systems running in parallel |
| Constraint | Payment continuity for every seller in every cycle, and SOX-compliant controls |
Background
Meridian had grown by acquisition, and each acquired business arrived with its own product, customers, quota logic and compensation plan. Each plan continued to run beside the parent program. By the third acquisition the company had four plans, four payment mechanisms, and a finance team that closed each commission cycle by reconciling four sets of calculations, six of them partly on spreadsheets.
Compensation at this scale amplifies every error. A flaw in plan design or calculation reaches thousands of people in a single cycle, and a seller who is paid incorrectly once begins to verify every later payment independently.
The challenge
| Measure | Starting point |
|---|---|
| Commission calculation accuracy | 91% |
| Separate compensation plans and payment systems | 4 |
| Calculations run partly on spreadsheets | 6 programs |
| Disputes per quarterly cycle | 140 |
| Days to close a commission cycle | 18 |
| Audit trail for every calculation | none |
| Quotas set from a capacity model | none; set top-down |
Three risks sat behind these figures. Finance could not forecast compensation cost, so quarterly accruals were wrong in both directions. The acquired sales organizations did not know whether their pay would change when their plan was absorbed, and the strongest sellers at each had begun to take outside calls. And the company’s SOX controls required a defensible audit trail for every calculation affecting the financial statements, which did not exist.
Approach
Governing rule. No seller would go a cycle without an accurate payment. The integration could take as long as needed, and any design that cost an acquired team one incorrect payment would cost more in trust than it saved in time. Every sequencing decision followed from this rule.
1. Map each program before moving anything. The first six weeks produced no new plan. Each acquired program was mapped against the parent framework: how credit was assigned, how quota was set, how accelerators and clawbacks operated, when payment was triggered, and which exceptions existed. The exceptions were the substantive work. One acquired company paid accelerators on cumulative annual attainment where the parent paid quarterly. Another applied a clawback for twelve months where the parent applied one for six. In a third, a regional leader had made an undocumented commitment to six sellers on how a strategic account would be credited, and finance had been paying it by hand for over a year. None could be resolved by defaulting to the parent’s rule. Each was decided on its merits and communicated before it changed. The undocumented commitment was honored through the end of the plan year, documented, and ended at the plan boundary with notice.
2. Sequence the transition by seller. Each seller remained on a plan they understood until the new plan was proven for their role. For each role, the new calculation ran in parallel with the old for two full cycles, with payment on the old plan. A role moved only when the two matched within tolerance for the entire parallel period. In the first parallel run about 6% of calculations differed. Nearly all differences traced to three causes: a rounding convention, a rule for splitting credit on multi-seller deals, and the treatment of partial-period quotas for new hires. Each was resolved in the design, not in a seller’s pay. One role never matched: a channel-management role built on a rebate structure the platform could not express cleanly. The company chose a small documented exception, held in the same audit trail as every other calculation, over bending the plan.
3. Move calculation into one governed system. Calculation moved into governed logic in the compensation platform, replacing the spreadsheet supplements one program at a time. Every calculation produced a record of inputs, rules applied, outputs and approver. An approval workflow required a second reviewer above a set threshold. Documented controls tied the record to the SOX requirements, and the first audit of the new process found no gaps. The legacy spreadsheets were archived with the final parallel results so any dispute over a legacy payment could be answered with data.
4. Replace informal disputes with a defined process. A disputed commission had previously gone to whichever manager the seller trusted, and the answer depended on the manager. A single channel was established, with acknowledgement within one business day, a service level for resolution, an escalation path, and a documented rationale for each decision, so identical cases received identical outcomes. Managers stopped adjudicating pay.
5. Rebuild plans on capacity. Each of the four plans set quota top-down, and attainment was skewed at both ends in all four. Plan design, quota setting and territories were rebuilt from capacity models: headcount, ramp time and historical productivity set against the revenue plan. Territories were redrawn against real account data so each seller had a defined, workable book. The method was documented for the next planning cycle.
6. Report in one view. Dashboards connected individual incentives to organizational outcomes: attainment distribution, accrual liability and payout forecast. Finance could, for the first time, forecast compensation cost against plan with confidence.
The third integration. By the third acquisition the process was repeatable. Mapping took three weeks, against six for the first. First-pass parallel variance was under 2%. The first acquisition took eleven months from mapping to retirement of its legacy plan. The third took six.
Results
| Measure | Before | After |
|---|---|---|
| Commission calculation accuracy | 91% | 98%+ |
| Separate plans and payment systems | 4 | 1 |
| Calculations run on spreadsheets | 6 programs | 0 |
| Disputes per quarterly cycle | 140 | 22 |
| Days to close a commission cycle | 18 | 6 |
| Payment disruptions during acquisition integrations | not tracked | 0 |
| Compensation governance findings in audit | no audit trail | 0 |
Accuracy held at 98% and above through each of the three integrations, leading to a compensation program the field trusted and finance could forecast. The acquired sales teams retained confidence through the transition because their pay stayed correct, and attrition among their strongest performers returned to the parent company’s rate within two quarters.
About this study
Illustrative: modeled scenario, not a client engagement. Meridian Networks is invented. The starting conditions are modeled on companies that grow through acquisition. The accuracy level of 98% and above, the audit trail and the dispute process correspond to the standard this work has been held to at scale.