The Retroactive Merit That Broke the Compa-Ratio
A 400-employee business unit finalized merit increases in March with an effective date of January 1. After the cycle closed, HR discovered that 38 employees in the Operations supervisory job profile had been mapped to the wrong salary plan, so their merit targets were calculated at 3% instead of the intended 4.5%. The business unit's compa-ratio budget was fully consumed by the March run. Leadership wants the difference paid retroactively to January 1. Payroll runs semi-monthly, and the next two cycles are already locked for processing. The Compensation Partner notes that the salary plan assignment is a position-level field, and 12 of the 38 employees have since changed positions within the same job profile.
1. What is the correct sequence to correct the merit targets and pay the retroactive difference without corrupting the current compa-ratio budget?
Read the worked answer
The root cause is a plan assignment error, not a merit calculation error, so fix the assignment first and let the calculation re-derive.
- Correct the salary plan on the position for the affected positions (or the job profile mapping if the plan is driven there). Confirm the 4.5% target populates on the compensation record.
- Re-run the merit process for the affected population only - do not re-run the whole cycle, which would re-apply increases to the 362 unaffected employees.
- Handle the 12 position-changers separately. Their current position may carry a different plan. Validate each one's effective-dated plan as of January 1, not today, or the retro will calculate against the wrong target.
- Use a separate one-time payment or an off-cycle retro element for the January-to-current delta rather than editing the original merit event. Editing history breaks audit and may double-count in the budget.
- Reconcile the compa-ratio budget by loading the retro as a distinct cost center line so the original cycle's budget consumption stays intact for reporting.
The trap is treating this as a pay-rate edit. Retroactive merit corrections should be additive payments against corrected targets, preserving the original effective-dated event.
2. Twelve employees changed positions after the merit run. What specific risk does this create for the retro calculation, and how do you mitigate it?
Read the worked answer
The risk is effective-date drift. If you calculate the retro against each employee's current position and plan, you apply the 4.5% target to a period when they were correctly on a different plan, or you apply it to a position that wasn't part of the error at all.
Mitigation: evaluate the salary plan as of January 1 using the effective-dated position history. For each of the 12, determine whether they were in the affected Operations supervisory profile on January 1:
- Were affected, then moved: pay retro only for the period they held the affected position.
- Moved into the profile after January 1: no retro owed for the prior period.
- Moved out but still in profile: full-period retro applies.
Build the retro as a dated segment per employee (start date to position-change date, then a second segment if applicable) rather than a single lump sum. This keeps the payment defensible in audit and prevents overpayment.