Salary budgeting basics
How to build a salary budget that holds
Headcount, pay bands, a fixed merit pool, and the employer costs that attach to every dollar of pay — assembled in the order most teams actually build them.
One fiscal year, twelve months of pay decisions — the live column marks the period you are budgeting now.
What a salary budget actually contains
A salary budget is the money an employer plans to spend on employee pay over a defined period, usually a fiscal year. It sounds simple until you separate the pieces: base pay for people already on staff, planned increases, a bonus or variable pool, and the employer-side payroll costs that attach to every dollar of gross wages.
Teams that treat the budget as one lump sum run into trouble by mid-year. This guide walks through the inputs in the order most teams build them, and it names the mistakes that show up again and again.
Five lines to separate
- Base pay for staff already on the roster
- The increase pool, fixed before it is distributed
- Bonus and variable pay on their own line
- Employer-side payroll costs on gross wages
- Budget-versus-actuals tracking through the year
Start with headcount, not with a percentage
The first input is who you are paying and for how long. Headcount planning means listing current roles, planned hires with target start dates, and known departures. A hire starting in month eight costs roughly four months of salary in that fiscal year, not twelve. Getting this wrong is the single most common way a salary budget drifts.
Build the roster first, then attach pay to each line. Keep the roster in one place with a start month next to every planned hire, so you can re-run the math when a start date moves. A roster that lives in three spreadsheets will not survive the first quarter.
Departures matter as much as hires. If you know a role ends in month five, the budget should stop paying for it in month five. Leaving that cost in place is how a budget looks healthy in January and tight by June.
The same annual salary costs a quarter of its yearly total when the start date lands in month ten, and the full total when it lands in month one. Multiply your salary figure by the share of the year the person is actually on payroll.
Pay bands give the budget a ceiling
A pay band is the approved range for a role or level, with a minimum, midpoint, and maximum. Bands stop the budget from being an open-ended promise, because every offer and every raise lands inside a known range. When you build bands, tie them to the market data your organization already uses rather than inventing numbers. A band without a midpoint is just a range; the midpoint is what tells you whether someone is paid below, at, or above the target for their level.
Minimum
Entry for the level
The floor for a new hire with the skills the role needs and little time in the level. Offers below this line usually mean the band is wrong, not the candidate.
Midpoint
The target for the level
This is the number that does the work. Position in band is measured against it, and the merit matrix reads it directly. A band without a midpoint cannot tell you whether pay is on target.
Maximum
The top of the range
Above this line, an increase pushes the person out of the band. That is a promotion or a band review, and it belongs in a separate conversation from the annual increase cycle.
The merit matrix distributes a fixed pool
A merit matrix allocates a limited increase pool across employees using two inputs, usually performance rating and position in the pay band. The pool is fixed before the matrix runs, which is the point: you decide the total increase budget, then the matrix decides who gets what.
Set the pool first
A common error is setting the pool after reviewing individual cases, which turns a budget into a negotiation. Fix the total increase figure, then let the matrix distribute it. The matrix then produces a defensible, repeatable distribution you can explain to a manager who disagrees with one cell.
Write the two axes down before you run anything. Rating on one side, position in band on the other, and a percentage in each cell. Anyone reading the result can see how it was produced, which matters more than the exact percentages you pick.
Two inputs
- Performance rating
- The review outcome for the period, applied consistently across teams.
- Position in band
- Where pay sits against the midpoint, which keeps the pool from stacking above the range.
Bonus and variable pay need their own line
Base salary and bonus are different costs with different timing. A bonus pool may be earned across the year but paid in a single quarter, which changes when the cost hits your forecast.
Keep bonus and variable pay on a separate budget line so the timing is visible. If you fold them into base, you lose the ability to see which cost moved when the actuals come in. A single merged line hides the quarter where the payment landed, and that is usually the quarter someone asks about.
Commission, shift differentials and spot awards belong on the variable line too. Each has its own trigger and its own lag between when it is earned and when it is paid, and separating them is what makes the budget-versus-actuals comparison readable later.
Two lines, two timings
Do not forget employer payroll costs
Every dollar of gross wages carries employer-side costs: the employer share of payroll taxes and any benefits the company funds. These are real budget items, not rounding errors. Teams that budget gross salary only and treat employer costs as a surprise end up revising the budget in the first quarter.
Estimate the employer cost rate your organization actually experiences and apply it to the gross wage total. The rate is not universal, so use your own figures. A separate line keeps the total visible without hiding it inside base pay, and it makes the gap obvious when someone asks why the payroll total is higher than the salary total.
How to apply it
- Add up gross wages for the year from your roster and pay lines.
- Apply your own employer cost rate to that total.
- Keep the result as its own line, reviewed on the same cadence as the rest of the budget.
Budget versus actuals is the feedback loop
Once the year starts, compare budget to actuals on a regular cadence. The variance tells you two different things, and mixing them up is how a budget gets quietly rewritten until it means nothing.
A timing shift
A hire started later than planned, so the cost moved to a later month. The budget is still correct. Adjust the month, not the plan.
A plan revision
The plan itself was wrong, for example the increase pool was too small to retain people. That is a real revision and it deserves a decision, not a silent edit.
The rule
Separate timing from planning before you change any number. If you cannot say which one moved, you are not ready to revise the budget.
Keep it to a size you can maintain
A salary budget does not need to be complex to be useful. A 40-person company with one finance generalist should run a simpler model than a 400-person company with a compensation analyst. Complexity you cannot maintain monthly is worse than a simple model you actually update.
Start with headcount, base pay, increase pool, bonus, and employer costs as five separate lines. Add detail only when a real decision needs it. If a line has never changed a decision in two cycles, it is a candidate for removal.
Where the detail pays off
Detail earns its place when it answers a question a manager, a finance lead, or a hiring plan will actually ask during the year. Everything else is upkeep.
Where this connects next
Payroll forecasting
Once the budget exists, the next question is what it costs over time as things change. That is payroll forecasting, and it uses the same inputs on a moving timeline — hires, raises and departures re-run month by month instead of held to one annual figure.
Move on to payroll forecastingChoosing software
If you are choosing software to support this work, the comparison page describes what different platforms are built for by team size and workflow. Read this page first; the tool decision is easier when the inputs are already clear.
Compare planning toolsQuestions that come up while building the budget
What is the difference between a salary budget and a payroll forecast? +
The budget is the plan for a defined period. The forecast is the running estimate of what that plan costs as hires, raises, and timing change. The budget is fixed; the forecast moves.
How many increase pools should a small company run? +
Usually one merit pool for the year, kept separate from any bonus pool. Splitting increases into multiple pools adds complexity that a small finance team may not be able to maintain.
Should employer payroll costs be inside the salary budget? +
Yes. They attach to gross wages and are a real cost. Keeping them as a separate line makes the total visible without hiding them inside base pay.
Start with the inputs, then pick the tool
Headcount, pay bands, the merit pool, bonus timing and employer costs — five lines that make a salary budget defensible for the year ahead. If a step here needs a second opinion before your cycle starts, the editorial team reads every message.
Misones editorial
450 Lexington Ave, New York, NY 10017, USA
Monday to Friday, 9:00 AM – 6:00 PM