Ask most payroll professionals whether employees contribute to state unemployment insurance, and the answer comes fast: no, that is an employer tax. In the vast majority of states, that answer is correct. State unemployment tax, commonly called SUTA, is funded by employer contributions and calculated on employer rate schedules. Employees never see a SUTA line on their pay stub, and payroll teams build their multi-state setup around that assumption because it holds up almost everywhere they operate.
The problem is the word "almost." Alaska, New Jersey, and Pennsylvania are the exceptions. In each of those three states, employees also make a required unemployment insurance contribution that has to be withheld from wages, alongside the employer's own SUTA obligation. It is a small detail with an outsized ability to break payroll compliance the moment a growing company opens its first role in one of these states.
Why the employer-only assumption is right almost everywhere, until it isn't
A correct-almost-everywhere assumption is dangerous precisely because it is so rarely wrong. Payroll leaders responsible for a growing multi-state footprint build muscle memory around state registration checklists that treat SUTA as a single, employer-side line item: register as an employer, get a rate, remit the tax. That pattern holds for the large majority of states a growth-stage company is likely to enter, so it becomes the default mental model.
The trouble is that a mental model built on "almost always" has no natural trigger to flag the exception. Nothing in a standard new-employer state registration workflow automatically surfaces that Alaska, New Jersey, and Pennsylvania handle SUTA differently. A payroll team can do everything right by the checklist they have always used and still miss a required withholding line, simply because that checklist was written for the other 47 states.
What actually has to change when the first hire lands in AK, NJ, or PA
Registering as an employer in Alaska, New Jersey, or Pennsylvania is only half the setup. The other half is adding an employee-side withholding: a deduction taken from that employee's wages for state unemployment insurance, calculated against a rate and wage base that each of those states sets and periodically adjusts on its own. This is not a footnote to the employer registration step, it is a distinct configuration item in the payroll system itself.
That distinction matters because the two obligations are handled in different places. Employer SUTA lives in the employer tax setup. Employee-paid SUTA lives in the employee's withholding configuration, the same category as state income tax withholding. A payroll team that completes new-employer registration in one of these three states but never touches the individual employee's withholding profile has only done half the job, and the missing half is invisible until a filing period, an audit, or an employee's own paycheck math surfaces it.
The two-sided risk of getting it wrong
Missing the employee-paid SUTA setup creates risk in two directions at once, and they compound each other.
The first is an employer liability problem. If the employee-side contribution was never withheld, the company is under-withheld relative to what the state requires, which is an exposure that only grows the longer it goes uncorrected.
The second is an employee relations problem, and it tends to surface at the worst possible moment: when the company fixes the error. Correcting under-withholding retroactively usually means catching up the missed employee contribution in a lump sum, which shows up as a surprise deduction on a future paycheck. From the employee's side, there was no warning, no explanation, and no chance to plan around it. That is exactly the kind of moment that erodes trust in payroll, even when the company is doing the responsible thing by fixing it.
Getting this right the first time avoids both problems. Getting it wrong means choosing between carrying the liability or springing a lump-sum correction on an employee who did nothing wrong.
Building the check into how you expand, not just how you onboard
The practical fix is a process discipline rather than a one-time memorization exercise. Every time a company's multi-state footprint changes, whether that is a first hire in a new state, a returning remote employee who relocates, or an acquisition that brings employees into a new jurisdiction, the payroll team needs a specific check: does this state require an employee-paid SUTA contribution. Assuming last year's state list still applies, or assuming the answer from 46 other states extends to the 47th, is how this exception gets missed.
This is where a connected payroll system earns its keep. AsureCentral is built so that payroll, HR, and tax setup share the same underlying data, which means a new employee record tied to a new state can surface the employee-paid SUTA configuration step at the moment a company registers that first employee in Alaska, New Jersey, or Pennsylvania, rather than relying on a payroll administrator to remember a three-state exception buried in a much longer compliance checklist. For growing companies without a large in-house tax team, that kind of built-in configuration check closes exactly the gap that a correct-almost-everywhere assumption creates.
The employee relations side of a retroactive correction is a judgment call as much as a compliance one: how to communicate the change, how to structure a catch-up so it does not blindside someone, and how to document the correction in a way that holds up if questioned later. That is the kind of question Asure HR Compliance is built to help growing companies work through, pairing certified HR expertise with the compliance administration support that lets a payroll or HR leader handle a correction fairly instead of improvising one under pressure.
A three-state exception worth building into your process
Alaska, New Jersey, and Pennsylvania are a small list, but they sit squarely inside the blind spot created by an assumption that is correct almost everywhere else. For a payroll or HR leader managing a growing multi-state footprint, the fix is not memorizing three state names. It is building a standing question into every expansion event: does this new state change what gets withheld from the employee, not just what the employer owes.
This is one of two common multi-state payroll errors covered in more depth, alongside the mechanics of new-employer rate periods and experience rating, in the broader resource from Asure, Why Multi-State SUTA Costs Surprise Growth-Stage Companies.
