New Year Payroll Tax Rate Changes: What Employers Must Update in January

The risk in January is not that rates changed. Everybody knows rates change.

The risk is that a dozen separate items change at once, in different systems, and responsibility for them is split — some maintained by the payroll provider and some by the employer. The failure mode is a client who assumes the provider handles all of it, and a practitioner who assumes the client checked.

So the useful thing this post can do is divide the list by who has to act, and then name the one error that runs all year.

What the Provider Updates

Typically maintained by the payroll provider without employer action, and worth verifying rather than assuming:

Federal withholding tables and the withholding computation method.

Social Security and Medicare rates and the Social Security wage base.

Federal unemployment rate and wage base, including any credit reduction applicable to a state.

State withholding tables for states where the employer is registered.

State unemployment wage bases.

The verification matters because a provider maintains these for the accounts it knows about. A state the employer registered in during the year, or an account set up incorrectly, may not be updated.

What the Employer Must Update — and the One That Costs Most

These do not update themselves, and the first one is the most common January error in payroll.

The state unemployment experience rate

Each state mails the employer a new experience rate, and somebody has to enter it.

Three things make this the costly one:

It arrives by mail, to whoever is on file, frequently at an address that is not the payroll department, and it is easy to discard as routine correspondence.

There is a deadline to protest it, and an employer who believes the rate is wrong — because of a misapplied claim, a wrongly charged former employee, or an acquisition — loses the ability to contest it once the window passes.

An unentered rate means the prior year's rate runs all year. If the new rate is higher, the employer under-pays every quarter and owes the difference with interest. If it is lower, the employer over-pays all year and has to claim it back. Either way, discovering it in the fourth quarter means amended returns for every prior quarter.

For a multi-state employer this is a per-state task, and it is the item most worth a calendar entry.

New registrations

Any state or local jurisdiction where the employer became liable during the prior year — most often because an employee moved, per our post on multi-state payroll. Registration, account numbers, and deposit setup must exist before the first payroll in that jurisdiction.

Everything employee-specific or plan-specific

Benefit premium amounts, retirement plan elections and limits, garnishment recalculations, and employee withholding elections. The provider cannot update what only the employer knows.

The January Checklist

Fifteen items. Work through them before the first payroll, not after.

1. Social Security wage base — verify the new base took effect, and verify that each employee's year-to-date accumulator reset.
2. State unemployment experience rate, per state, entered — per above.
3. State unemployment wage bases, per state.
4. State withholding tables, including any state that changed its withholding method rather than only its rates, which requires a configuration change rather than a table update.
5. Local jurisdiction taxes — new city, county, school district, or transit taxes, including for any employee who moved. This is the most commonly missed obligation in the whole list.
6. Minimum wage changes — federal, state, and local, noting that effective dates are not always January 1 and that local ordinances frequently exceed state rates. Check every jurisdiction where an employee works.
7. Exempt salary thresholds for overtime exemption, federal and state, applying whichever is higher. An employee whose salary no longer meets the threshold becomes overtime-eligible, which is a classification change rather than a rate change.
8. Retirement plan limits — the deferral limit, catch-up amounts, and the compensation limit — plus any change to the employer formula and any automatic escalation step scheduled to occur. Our post on plan amendment deadlines covers the document side.
9. Health savings account and flexible spending limits, and any carryover or grace period election.
10. Benefit premium changes, with the new deduction amounts and their correct pre-tax or post-tax treatment.
11. Mileage and per diem rates for reimbursement, and confirmation that the accountable plan requirements are still met.
12. Garnishment recalculation. The non-obvious dependency: the federal disposable earnings floor for creditor garnishments is expressed in terms of the minimum wage, so a minimum wage change alters the protected amount and every affected garnishment must be recomputed. Our post on wage garnishments covers the calculation.
13. Employee withholding elections — new federal and state forms as submitted, and specifically the renewal of any claimed exemption from withholding, which expires and must be re-claimed. An employee whose exemption lapsed and who was not switched to withholding has an unpleasant surprise coming, and the employer has a compliance problem.
14. Deposit schedule, redetermined from the lookback period. A growing employer can move to a more frequent schedule, and depositing on the prior year's schedule is a failure even when the full amount is paid.
15. New state programs — paid family and medical leave, state disability, and state-facilitated retirement mandates, each with registration, contribution, and employee notice requirements, and each with its own effective date.

Verify With a Test, Not a Belief

The step almost nobody performs and the one that catches errors before they compound.

Run the first payroll and hand-check three to five employees. Pick a high earner, a low earner, someone with benefit deductions, someone with a garnishment, and — if applicable — someone who capped out on Social Security last year.

For each, compute the withholding manually and compare it to what the system produced. Differences are either an explanation you need or an error you just caught.

Then reconcile the first payroll at the register level:

Gross to net for the whole run, tied out.

Employer taxes recomputed independently — Social Security, Medicare, federal unemployment, and each state's unemployment at the new experience rate.

Wage base restarts confirmed. Every employee's year-to-date figures should be zero, and Social Security should be withholding again on anyone who reached the base last year. A system that carried forward accumulators will under-withhold all year and it is invisible without this check.

Any employee whose net pay changed materially, with a reason.

Twenty minutes, and it is the difference between finding a wrong rate in the first cycle and finding it in the twenty-sixth.

Tell Employees Before They Ask

Net pay changes in January for reasons employees do not connect: wage base resets, benefit premium changes, retirement election changes, a withholding table update, and a new local tax.

A short proactive note explaining what changed and why prevents most of the calls the payroll department will otherwise field for two weeks — and it prevents the employee who assumes an error and escalates.

Structured coverage is available through the Payroll Boot Camp, the Certified Payroll Administrator and Certified Payroll Manager programs, the Payroll Operations Training and Certification Program, Multi-State Payroll Tax Compliance, Details and Best Practices for Calculating Payroll Deductions, How to Minimize and Eliminate Payroll Penalties, and the State Sick Pay Law Review.

Multi-Entity and Multi-State Employers

The January checklist multiplies, and the multiplication is where it breaks.

Every item is per entity and per state. An employer with three entities and employees in five states does not have fifteen items on the list — it has the whole list run fifteen times, with a separate experience rate notice, separate wage bases, separate withholding tables, and separate local obligations for each combination.

The recurring failure is partial completion. A payroll manager updates the primary entity's configuration, confirms it looks right, and never returns to the smaller entities — which are frequently the ones with a single employee in an unusual state and therefore the ones nobody thinks about. That employee's state gets last year's rate all year, and because the entity is small the error goes unnoticed until a notice arrives.

Common ownership does not consolidate the obligations. Related entities each have their own accounts, their own experience rates, and their own filings, and an experience rate that improved for one entity says nothing about the others.

Build the checklist as a grid — entities down one axis, jurisdictions across the other — and require a sign-off per cell rather than per item. It is tedious and it is the only method that makes an omission visible.

Two related items worth checking in a multi-entity group. Whether an employee moved between related entities during the prior year, which affects wage base treatment and can produce over- or under-payment depending on the relationship. And whether any entity was added, dissolved, or reorganized, since a new entity needs registrations completed before its first payroll and a dissolved one needs final returns rather than silence.

Why January Errors Are Expensive

Because they run all year, and the correction cost scales with when they are found.

An error caught in the first payroll is a configuration change. The same error caught in April requires correcting three months of payrolls and possibly an amended quarterly return. Caught in the fourth quarter, it requires amended returns for every prior quarter, corrected wage statements if the error affected taxable wages, employee communications, and — where the employer under-withheld — a decision about whether to recover the amount from employees or absorb it.

That asymmetry is the entire argument for the verification step above.

Where Employers Get This Wrong

• Assuming the provider updates everything, when the experience rate is the employer's to enter
• The experience rate notice discarded as routine mail, or received by someone outside payroll
• The protest deadline missed on a rate the employer had grounds to contest
• Prior-year experience rate running all year, discovered in the fourth quarter
• Local jurisdiction taxes missed for an employee who moved
• Minimum wage checked federally and at state level but not locally
• Garnishments not recalculated after a minimum wage change
• Exempt salary thresholds not checked, leaving an employee misclassified as exempt
• Claimed withholding exemptions not renewed, so an employee has no withholding all year
• Deposit schedule not redetermined from the lookback period
• New state program requirements missed, including notices
• Wage base accumulators carried forward, under-withholding invisibly
• No hand-check of the first payroll
• No employee communication, generating two weeks of calls

The summary: the provider updates the tables and you update the experience rate, the local taxes, the benefit amounts, and the employee elections — and the single highest-value twenty minutes of the payroll year is hand-checking three employees on the first payroll and confirming every wage base restarted at zero.

Frequently Asked Questions

What is the most common January payroll error?

Not entering the new state unemployment experience rate. Each state mails it, frequently to someone outside the payroll department, and if it is not entered the prior year's rate runs all year — producing under-payment with interest or over-payment to reclaim, and requiring amended returns for every prior quarter if discovered late. There is also a deadline to protest a rate the employer has grounds to contest.

What does the payroll provider not update?

Anything only the employer knows: the state unemployment experience rate, registrations in jurisdictions where liability arose during the prior year, benefit premium amounts, retirement plan elections and formula changes, garnishment recalculations, and employee withholding elections. Providers also maintain only the accounts they know about, so a state registered mid-year may not be updated.

Why does a minimum wage change affect garnishments?

Because the federal protected amount for creditor garnishments is expressed in terms of the minimum wage, so a change alters the disposable earnings floor and every affected garnishment must be recomputed. It is a non-obvious dependency and it is routinely missed.

What should be verified on the first payroll of the year?

Hand-check three to five employees — a high earner, a low earner, someone with benefit deductions, someone with a garnishment, and anyone who reached the Social Security wage base last year — against a manual computation. Then reconcile gross to net, recompute employer taxes at the new experience rate, and confirm every employee's year-to-date accumulator reset to zero. A system that carried accumulators forward will under-withhold invisibly all year.

Which withholding election expires?

A claimed exemption from withholding, which must be renewed. An employee whose exemption lapsed and who was not moved to withholding will have a substantial balance due, and the employer has a compliance problem — so the renewal check belongs on the January list.

Why are January errors more expensive than errors later in the year?

Because they run all year. Caught in the first payroll, an error is a configuration change; caught in April it requires correcting three months of payrolls and possibly an amended return; caught in the fourth quarter it requires amended returns for every prior quarter, corrected wage statements where taxable wages were affected, employee communications, and a decision about recovering under-withheld amounts.