If your company operates in more than a handful of states, state unemployment tax is one of the few payroll costs that changes every year and rarely gets modeled with the same rigor as headcount or benefits. Most finance teams find out what SUTA actually costs when the rate notices start arriving, months after the budget is already locked. By then, the forecast is just a reaction.
There is a better sequence. Before the hiring plan for next year is finalized, a CFO, Controller, or Payroll Leader can build a defensible, per-state SUTA forecast using data the company already has. The steps below walk through that process in order, from the hiring plan through the annual rate notice that eventually tells you how close you got.
Step 1 Pull Projected Headcount and Wages by State
Start with the hiring plan, not last year's payroll report. For every state where the company currently has employees, pull projected headcount and wage totals for the forecast period. Then do the same for any state the company expects to enter for the first time, whether through a new office, a remote hire, or an acquisition.
This step matters because SUTA is calculated per state rather than as a single blended number. A hiring plan that adds twenty people in one state and five in another produces two very different tax exposures, and a forecast built off a company-wide average will miss both. If the hiring plan itself is still in flux, use the most current version and plan to revisit the forecast once headcount numbers firm up.
Step 2 Gather Current and New-Employer SUTA Rates by State
Once you know where the wages will be earned, pull the current SUTA rate for every state where the company already has an active account. Rates are assigned per employer, per state, and they move year to year based on that employer's experience rating, so last year's rate is a starting reference rather than a fixed input.
For any state the company is entering for the first time, there is no experience rating yet, so the state assigns a new-employer rate instead. That rate is set by the state, not the company's history, and it applies until enough time passes for the state to calculate an experience-based rate. Both figures, current rate and new-employer rate, need to come from the company's own state UI accounts or payroll system rather than being estimated, since they vary by state and by year.
Step 3 Confirm Each State's Taxable Wage Base and Model Exhaustion
Every state sets its own taxable wage base, the amount of an employee's annual wages subject to SUTA before no further tax applies for that employee in that state for the year. Wage bases vary widely from state to state, and they are typically updated annually, so pulling last year's figure and assuming it still applies is a common source of forecast error.
This step is also where per-employee timing becomes important. A high earner in a state with a low wage base may exhaust that base early in the year, after which their wages stop generating SUTA liability for the rest of the period. A workforce concentrated in a state with a high wage base behaves differently. Modeling this at the employee level, rather than assuming every dollar of payroll is taxable all year, is what turns a rough estimate into a usable forecast.
Step 4 Build a Claims-Activity Assumption From Real History
The fourth input is the one most forecasts skip entirely, an assumption about unemployment claims likely to be charged against the company's account during the forecast period. Claims activity directly affects a company's experience rating and, in turn, its future SUTA rate, so ignoring it means ignoring the mechanism that moves the rate in the first place.
Rather than assuming zero claims or borrowing an industry average, build this assumption from the company's own recent claims history. A business with layoffs, seasonal turnover, or a recent restructuring should expect that history to influence upcoming rate notices, and the forecast should reflect that rather than treating every year as a clean slate.
Step 5 Use the Rate Notice as Your Annual Calibration Checkpoint
Once the forecast is built, the annual rate notice becomes the moment to check your work rather than just another document to file. When the notice arrives, request the accompanying benefit charge statement and compare the two side by side.
Confirm three things: that only legitimate claims were charged to the account, that the payroll denominator the state used to calculate the rate matches the company's actual taxable payroll, and that the correct rate schedule was applied for that state and year. Any discrepancy found here should feed directly back into next year's forecast inputs, whether that means disputing a charge, correcting a wage base assumption, or adjusting the claims assumption in step four. This is the step that closes the loop between what was forecast and what actually happened, and it is also the step most companies skip because it arrives outside of budget season.
What Happens When You Skip This and Use Last Year's Blended Rate
The shortcut many finance teams fall back on is taking last year's total SUTA cost, dividing it by headcount, and applying that blended rate to next year's plan. It is fast, but it breaks down as soon as the company's state mix changes, and growth-stage companies are constantly changing their state mix.
A blended rate averages away exactly the information that matters, the difference between a state with a high current rate and one with a new-employer rate, the difference between a wage base that gets exhausted mid-year and one that does not, and any claims activity that is about to move a specific state's rate up or down. Companies that rely on it tend to be surprised twice, once when the actual per-state cost comes in higher than the average implied, and again when the rate notices show the gap was predictable all along once the four inputs were modeled separately.
Where AsureCentral and AsureWorks Fit
The reason this forecast is hard to build isn't the math, it's that the four inputs usually live in different places: a hiring plan in one spreadsheet, current rates in state portal logins, wage base figures in a payroll vendor's documentation, and claims history in whatever notices were filed away last year. AsureCentral holds payroll, headcount, and state-by-state wage data in one connected system, so a Payroll Leader or Controller building this forecast is pulling from one source instead of assembling exports from several.
For a company that would rather have this forecast built and maintained by specialists, including the annual rate notice and benefit charge statement review described in step five, AsureWorks offers a done-for-you alternative. Asure specialists handle the payroll administration work directly while the client remains the employer of record, so the forecasting and reconciliation work gets done without the company adding internal headcount to own it.
This four-input model, along with the broader mechanics behind new-employer rate timing and experience rating, is covered in more depth in Why Multi-State SUTA Costs Surprise Growth-Stage Companies, the broader resource this guide draws from.
