Salary Raise Budget Calculator
Plan salary raises by employee row or pooled salary base, with fiscal-day proration, employer burden, budget fit, and scenario comparisons.| Measure | Value | Meaning | Copy |
|---|---|---|---|
| {{ row.measure }} | {{ row.value }} | {{ row.meaning }} |
| Label | Current | Raise rule | New salary | Annual increase | Loaded annual | First-year cost | Status | Copy |
|---|---|---|---|---|---|---|---|---|
| {{ row.label }} | {{ row.current }} | {{ row.raise_rule }} | {{ row.new_salary }} | {{ row.annual_increase }} | {{ row.loaded_annual }} | {{ row.first_year_cost }} | {{ row.included }} |
| Scenario | Annual salary increase | Loaded annual | First-year cost | Budget variance | Average first-year | Fit | Copy |
|---|---|---|---|---|---|---|---|
| {{ row.scenario }} | {{ row.annual_increase }} | {{ row.loaded_annual }} | {{ row.first_year_cost }} | {{ row.budget_variance }} | {{ row.average_first_year }} | {{ row.fit }} |
A raise plan has two different price tags. The annual salary increase is the recurring amount added to payroll, while the first-year budget cost depends on when the raises take effect. Confusing those figures can make a proposal look affordable in its launch year even though the next full year costs much more.
Planning can begin with individual salary rows or with one eligible salary pool. Row-level work suits mixed decisions such as a 4% merit increase for one role and a fixed annual adjustment for another. An aggregate pool is useful when only the total eligible salary base and a common percentage or fixed amount are known.
| Amount | What it answers | Common mistake |
|---|---|---|
| Annual salary increase | How much base salary rises over a full year | Treating a partial-year cost as the recurring run rate |
| Loaded annual increase | Annual increase plus a user-supplied employer burden allowance | Assuming one burden rate represents actual payroll and benefits |
| First-year cost | The loaded increase inside the selected fiscal period | Prorating by months when the plan uses calendar days |
| Budget variance | Budget cap minus first-year cost | Reading a positive variance as proof that the policy is equitable or approved |
Budget fit is only one review. Eligibility, pay equity, salary ranges, promotion rules, payroll timing, benefits, taxes, and local employment requirements still need their own checks. Labels should also be anonymous when a plan may be shared or exported.
How to Use This Tool:
Choose the planning detail you actually have, then keep the fiscal period and currency consistent across the plan.
- Select Salary rows for mixed employee or role decisions, or Aggregate salary pool for one pooled assumption. Enter percentage raises as percentages and fixed raises as annual amounts.
- Set the First-year budget cap, fiscal start and end, and Raise effective date. Use a cap of zero when you want cost totals without a within-cap or over-cap decision.
- Open Advanced to add a verified employer burden rate or up to eight comparison percentages. Alternate percentage scenarios apply to the included salary base rather than replaying mixed row-level rules.
- Compare First-year cost, Loaded annual increase, and Budget variance. Check excluded rows and the fiscal-day count before using the result in an approval draft.
Interpreting Results:
Within cap means the modeled first-year cost is less than or equal to the entered cap. Over cap means budget variance is negative. A zero cap produces No cap, so the amounts remain useful but no budget-fit conclusion is made.
The Annual salary increase excludes employer burden. Loaded annual increase adds the selected burden allowance, and First-year cost applies the fiscal proration to that loaded amount. When the effective date is after fiscal year-end, first-year cost is zero even though the annual run rate remains.
Scenario percentages are clean salary-base comparisons. They do not preserve a mixed set of fixed and percentage raises, so compare them with the current plan as alternatives rather than as row-by-row revisions.
Technical Details:
Each included row is converted to an annual salary increase, optionally loaded with a user-supplied burden rate, and then prorated over inclusive calendar days. Excluded rows remain visible but do not contribute to totals.
Formula Core
For salary S, percentage raise p, fixed annual raise F, burden rate b, remaining fiscal days dr, and total fiscal days df, the calculation uses:
An effective date on or before fiscal start gives P = 1. A date after fiscal end gives P = 0. Otherwise, both the effective date and fiscal end are counted in dr, and both fiscal boundary dates are counted in df.
Rule Core
| Rule | Exact behavior |
|---|---|
| Row limit | Salary-row mode accepts 1 to 50 rows; each row may be included or excluded. |
| Raise values | Percent and fixed annual values must be nonnegative; aggregate percentages may be 0% through 1,000%. |
| Employer burden | The entered 0% through 100% rate is ignored until Employer burden is enabled. |
| Budget fit | Cap > 0 and variance ≥ 0 is Within cap; cap > 0 and variance < 0 is Over cap; cap = 0 makes no fit decision. |
| Scenario percentages | Up to eight unique values from 0% through 100% are applied to the included salary base. |
A midyear example shows the sequence. A 72,000 salary with a 4% raise creates a 2,880 annual increase. At an 18% burden rate, loaded annual cost is 3,398.40. An effective date of July 2 in the 2026 calendar year counts 183 of 365 days, producing a first-year cost of 1,703.86.
Money is rounded to cents after each row's annual increase, loaded annual amount, and first-year cost. Included row values are then summed and totals are rounded to cents. The currency label changes presentation only; no exchange-rate conversion occurs.
Limitations and Privacy:
This is a budgeting model, not payroll, tax, compensation-policy, or legal advice. The burden rate is entirely user supplied and does not calculate jurisdiction-specific employer taxes or benefits.
- Proration uses calendar days, not pay periods, workdays, or payroll cutoffs.
- One effective date applies to the whole plan; staggered dates require separate runs.
- Calculations run in the browser, but labels and values may be carried into shared links or exports. Use anonymous role names or codes instead of personal data.
References:
- Employer Costs for Employee Compensation calculation, U.S. Bureau of Labor Statistics, updated October 24, 2025.