Compensation planning
Building salary structures and merit plans
Compensation planning decides how your payroll budget actually gets spent. This guide covers salary bands, merit matrices, and bonus pool sizing, so individual pay decisions stay consistent with the labor budget you already approved.
Bands set the range before the offer, so two managers hiring the same role land in the same place.
Midpoints let you estimate cost from headcount instead of rebuilding a spreadsheet each quarter.
One merit pool, one matrix, and the increase cost lands in the quarter you forecast.
Salary bands: set the range before the offer
A salary band defines the minimum, midpoint, and maximum for a role, usually tied to a market reference and an internal level. Bands exist so that two managers hiring for the same role do not land on wildly different numbers.
Build bands for roles you hire repeatedly, and leave genuinely unique roles out of the structure rather than forcing a bad fit. Review bands annually, because market movement does not wait for your fiscal year.
Minimum
The floor for a role. New hires with partial experience usually start here, and the number should match what your market actually pays, not what the last offer happened to be.
Midpoint
Where a fully competent performer sits. This is the number you multiply by headcount when you estimate salary cost for the coming year.
Maximum
The top of the range for that level. Pay above it is an exception with a written reason, not a quiet adjustment a manager makes alone.
A band with no maximum invites drift: each raise looks small on its own, and the role quietly becomes more expensive than the level it was priced at.
Midpoint is a planning tool, not a rule
The midpoint is useful for budgeting because you can estimate total cost from midpoints and headcount. It is not a rule that every employee must reach.
Someone early in a role may sit below midpoint; someone with rare skills may sit above it. What matters is that the reason is written down, so the next review starts from a decision instead of a blank page.
Merit matrices: connect performance to increase
A merit matrix links a performance rating to an increase percentage within a budget envelope. The matrix forces a tradeoff: if you give top performers a larger increase, the average increase has to come down elsewhere.
Set the total merit pool first, then build the matrix so it distributes that pool. Without a matrix, merit cycles turn into a series of individual negotiations that almost always exceed the budget.
Rating band
Increase position in the pool
What the manager must write down
Above expectations
Draws the largest share of the pool; the number of people here caps how much everyone else can receive.
Which results carried the year, and whether the role is still priced at the right level.
Meets expectations
Takes a moderate increase that keeps pace with the market reference for the role.
Where the employee sits inside the band, and whether position in range is drifting.
Below expectations
Receives little or nothing from the pool, and that decision is documented before the conversation.
What has to change by the next review point, with a date attached.
Work the matrix from the pool downward. Building it upward from individual increases is how merit cycles end up over budget before finance ever sees them.
Bonus pools and variable pay
If you run bonuses, size the pool before you communicate individual targets. A pool sized as a percentage of salary budget is easier to forecast than discretionary awards decided at year end.
Paycom's compensation planning workflow is commonly framed around merit matrices and performance-linked pay decisions, tied to salary parameters and payroll, which is the operational version of this: the decision and the payment sit in the same system.
When the bonus decision lives in one tool and the payment runs through another, every cycle needs a reconciliation step. That step is where targets and payouts quietly drift apart.
Keep the plan inside the payroll budget
Compensation decisions have to reconcile with the labor budget you built earlier in the year. If the merit cycle lands in Q3, the increase cost belongs in the Q3 forecast, not in a separate compensation spreadsheet.
When HR and finance use different documents, the budget becomes a formality and the variance shows up in the payroll run. One shared forecast keeps the number you approved and the number you pay on the same page.
A simple check works well: compare the forecasted increase cost against actual pay changes each cycle. If the two diverge, find the decision that was made outside the plan before adjusting the budget.
What a reconciliation pass covers
- Pool against forecast. The merit and bonus pools are compared with the labor budget line for the same quarter.
- Position in band. Each increase is checked against the employee's place in the range, not just the percentage given.
- Exceptions on record. Any pay above maximum carries a written reason and a review date in the same document as the budget.
- Timing of the run. The cycle's effective date is matched to the payroll period so the cost lands where it was planned.
Multi-state pay and location adjustments
If you hire across states, a single national band will either overpay in lower-cost markets or fail to attract in higher-cost ones. Location-based adjustments add complexity, but they are easier to manage than case-by-case exceptions.
Decide your approach before the next offer, and document it so managers apply it consistently. Two questions settle most of it: which locations get an adjustment, and whether the adjustment moves the whole band or only the offer.
Whichever you choose, write the rule where managers can find it. An adjustment applied from memory is an exception waiting to happen.
Approach
One national band
Simple to explain and cheap to administer, but it compresses the range where market pay differs most.
Approach
Location-adjusted band
The band shifts by location tier, so the midpoint still means something in each market you hire in.
Approach
Remote benchmark
Price fully remote roles against one chosen market, and say which market that is, so offers stay comparable.
Approach
Case-by-case exception
Fast for one hire and expensive for ten. Use it rarely, and record the reason each time it happens.
Whatever you pick, the same rule has to survive a manager change and a busy hiring quarter.
Communicating the structure
Employees do not need to see the full matrix, but they should understand how their pay is set and when it is reviewed. A short explanation of the band, the review cycle, and what drives an increase prevents most of the questions that otherwise reach HR during merit season.
Three sentences usually do the work: the role sits in a band with a minimum and maximum, pay is reviewed once a year, and the increase depends on performance against agreed goals. Managers who can repeat that consistently spend less time defending individual numbers.
If a raise is not happening this cycle, say so plainly and name the next review point. Silence is what turns a pay conversation into a retention problem.
Reviewing the structure each year
Bands drift, roles change, and market data moves. Set one annual review point, check bands against current market references, and check your actual pay distribution against the bands.
If a significant share of employees sits above maximum, the band is outdated, not the people. The same review should catch roles that have quietly changed scope and no longer match the level they were priced at.
Keep the review on a fixed date each year so it feeds the labor budget you are already building, rather than arriving after the forecast is closed.
Questions that come up before merit season
Short answers to the decisions finance and HR teams revisit most often when they set or repair a structure.
Ask a compensation questionHow many salary bands does a small company need?
Fewer than you think. Most small employers can start with bands for the roles they hire repeatedly and leave one-off roles outside the structure until a pattern appears. A band you cannot explain to a manager is worse than no band at all.
Should merit increases be a percentage or a fixed amount?
Percentages preserve relative pay differences and are easier to budget as a pool. Fixed amounts are simpler to explain but compress pay differences over time, because the same dollar figure is worth less to a higher salary.
How do we handle an offer above the band maximum?
Treat it as a deliberate exception with a written reason and a review date. Repeated exceptions mean the band, not the candidate, is the problem, and the annual review is the right place to fix it.
Where does the increase cost belong in the forecast?
In the quarter the increase takes effect, inside the same labor budget as the rest of payroll. A compensation spreadsheet that sits outside the forecast guarantees a variance in the payroll run.
Put the structure next to the budget
Bands, a merit matrix, and a sized bonus pool are the parts that keep compensation decisions explainable. The last step is making sure they reconcile with the payroll budget you already approved, and that the people who make offers can find the rules.
If the pieces are not in place yet, start with the budget and work forward. If they are, review the bands against current market references and check where your people actually sit in range.
Endeveree — 1201 N Market St, Suite 111, Wilmington, DE 19801, USA · +1-302-555-0184 · info@endeveree.com · Monday–Friday, 9:00 AM – 6:00 PM ET