Somewhere between the open enrollment packets and the holiday schedule requests, an envelope from your state's unemployment agency lands in a mail pile. It looks like every other government notice, so it waits. Maybe it gets scanned to a shared drive. Maybe it gets forwarded to someone who left the company in August. And months later, a tax notice arrives, or a quarterly return comes up short, and everyone spends a week reconstructing what happened.
If that story sounds familiar, you're in good company. Missed or mishandled state unemployment insurance rate notices are among the most common problems we untangle for ADP clients, and they're almost always discovered long after the fix was easy. The notice itself takes five minutes to handle. The cleanup after ignoring it can take a quarter.
The season for these notices is starting now. Here's what they are, why the rate on file in ADP has to match them exactly, what goes wrong when it doesn't, and how to build a process so this never becomes your February emergency.
State unemployment insurance, or SUI, is an employer-paid tax in nearly every state (a few states also collect a small employee share). Unlike most payroll taxes, your SUI rate is not a flat, published number. It's assigned to your company individually, usually once a year, based on your "experience": how much unemployment benefit has been charged to your account, the size of your taxable payroll, the health of the state's unemployment trust fund, and the state's own rate schedule for that year.
The rate notice is the state's official letter telling you your assigned rate for the coming year. It typically includes your new rate, the effective date (January 1 in most states, though several states run a different fiscal year), your taxable wage base for the year, and sometimes surcharges or fund-solvency add-ons that ride along with the base rate. Some states also show how the rate was computed and give you a window to protest it if you believe the calculation is wrong.
Two things make these notices easy to mishandle. First, they're addressed however the state has you registered, which may be a legal entity name and an address nobody checks. Second, they look routine. They are not routine. That single percentage drives real tax dollars on every payroll you run.
There is no national schedule. Many states mail rate notices in November and December for a January 1 effective date. Others send them in late December or January, after the rate has technically taken effect. A handful of states operate on a July fiscal year and send notices in the spring. Some states have moved to electronic-only delivery through their employer portals, which means the "mail pile" problem becomes a "nobody logged into the portal" problem.
The timing creates a trap: your first payrolls of the new year may run before the notice arrives. ADP continues calculating at the rate on file until a new one is entered with its effective date, which is reasonable, because it's the only rate anyone knows. But it means a late-arriving notice almost guarantees at least one payroll calculated at the old rate. That's normal and fixable. What's not fine is letting the gap run for two quarters because the notice sat unopened.
Mark your calendar by state. If you know Maryland typically issues rates in a certain window and you haven't seen yours, go get it from the state portal rather than waiting on the mail.
Your payroll system computes SUI tax as your assigned rate times each employee's taxable wages, up to that state's wage base. ADP then deposits that tax and files your quarterly unemployment returns based on those calculations. The state, meanwhile, computes what you owe using the rate it assigned you. If the two rates differ, every single payroll produces a small error, and small errors compound across employees, pay periods, and quarters.
It's worth being precise about effective dates too, not just the rate. A correct rate entered with a wrong effective date creates the same mismatch. If your state's new rate applies January 1 and it's entered effective February 1, the January payrolls calculated at the old rate, and your first-quarter return won't tie to the state's expectation.
And don't stop at the base rate. Some states assign separate components: a base experience rate plus a surcharge, an administrative assessment, or a training fund tax. Depending on the state, these may need to be reflected in your setup individually. Enter only the base rate when the state expects base plus surcharge and you'll be under-collected all year by a margin nobody notices until reconciliation.
If the rate on file is lower than your assigned rate, you under-deposit. Each quarter, the return filed on your behalf understates what the state believes you owe. Eventually the state notices, and you receive a balance-due notice, often with penalty and interest attached. Because the error usually spans multiple quarters, the fix isn't one payment; it's amended returns for every affected quarter, plus catching up the tax itself, which by then is a lump sum nobody budgeted.
If the rate on file is higher than your assigned rate, you over-deposit. That sounds harmless, but it's your cash sitting with the state, and recovering it still requires amended returns or credit requests. We've seen employers overpay for years because a rate increase was entered once, then the following year's decrease never was.
There's a second-order cost, too: mismatched rates poison your reconciliations. When your quarterly wage and tax reports never quite tie to state statements, your team stops trusting the reports, and real problems hide behind the noise of the known discrepancy. One wrong rate can burn hours every quarter in "why is this off again?" conversations.
When the notice arrives, treat it as a small controlled process, not a data entry task. Confirm the notice matches your company: legal name, state account number, and the entity it applies to (if you run multiple company codes or FEINs, each may have its own rate). Capture the pieces: base rate, any surcharges or assessments, the effective date, and the taxable wage base shown.
Then get the rate into ADP promptly, with the effective date from the notice, not the date you happened to enter it. Depending on your ADP setup and service level, SUI rate changes may be something you enter directly or something you submit to ADP with a copy of the notice. Either way, the notice document matters: it's the state's word on what the rate is, and it should be retained where you can find it at reconciliation time.
Finally, verify. After the first payroll following the change, spot-check one employee in that state: taxable wages times the new rate should equal the SUI tax on the register. Two minutes of arithmetic confirms the whole chain worked. If any payrolls already ran at the old rate after the effective date, quantify the difference and correct it in the current quarter while it's still current.
One more thing worth doing while you have the notice in hand: read the experience-rate calculation. If your rate jumped, check whether the benefit charges driving it are actually yours. Errors happen, and most states give you a limited protest window measured in days, not months. A successful protest lowers every payroll for the rest of the year.
If you have employees in eight states, you have eight rate notices, eight effective-date conventions, eight wage bases, and eight portals, and the notices will not arrive in the same month. Remote work has quietly turned many single-state employers into multi-state employers, and SUI is often where that shows up first, because hiring one remote employee in a new state means registering for a new unemployment account and receiving a rate you've never had before.
New-state setups deserve extra care. Until your registration is complete, you may be operating under a temporary or standard new-employer rate, with the state's assigned rate arriving later and sometimes applying retroactively. Track those open registrations the way you'd track an open invoice: someone owns each one until the real rate is on file and verified.
Build one tracking sheet for all of it: state, account number, current rate, new rate, effective date, date entered in ADP, date verified against a payroll register. Ten minutes per state per year, and your whole SUI posture is auditable at a glance.
A client with about 120 employees across three states came to us with a balance-due notice from one state for roughly $4,800, plus penalties and interest. Here's what had happened. Their rate notice, mailed the previous November, assigned a rate of 3.4%, up from 2.1% after a year with several unemployment claims. The notice was scanned into a folder and never acted on. Payroll ran all year at 2.1%.
The math is unglamorous but instructive. With about $1.5 million in taxable SUI wages that year, the difference between 2.1% and 3.4% was roughly $19,500 in tax the state expected. Quarterly filings understated it, the state caught up with them in the fourth quarter, and the total bill, with penalties and interest, landed near $21,000, all at once, in December.
We helped them file the amended quarterly returns, negotiate a penalty abatement based on their clean prior history (the state agreed to waive a portion), and set up a simple notice-handling process: one owner, one tracking sheet, a calendar reminder per state, and a verification step after the first payroll at each new rate. The next year, all three rate changes were entered and verified within a week of arrival. Total cost of the new process: about an hour a year.
Yes. On $2 million of taxable wages, 0.2% is $4,000 a year, and even small mismatches force amended returns and make every reconciliation noisy. The effort to enter the rate is identical whether the change is large or small, so enter it.
No, this happens constantly. Enter the new rate with its correct effective date, then quantify the difference on the payrolls that already ran and correct it within the quarter. Caught inside the same quarter, it's an adjustment. Caught two quarters later, it's amended returns.
Often, yes. Check the benefit charges and payroll figures on the calculation. If former-employee claims were charged to your account in error, or the state used wrong wage data, you can protest, but the window is short, so review the notice the week it arrives. Timely, well-documented protests do succeed.
A healthy SUI process is boring, and that's the point. One named owner for unemployment notices in every state, with portal logins that don't die when an employee leaves. A tracking sheet listing every state account, its current rate, and its wage base. A standing calendar reminder in each state's notice season to go find the rate if it hasn't arrived. Entry into ADP within days of receipt, with the state's effective date. And a one-employee spot-check after the first payroll at each new rate, initialed and filed.
That's the whole system. It costs almost nothing, and it eliminates a category of tax notice entirely.
If you'd rather not build and babysit that process yourself, this is exactly the kind of work we handle. Ignite HCM consultants are former ADP service professionals who work with ADP clients exclusively, and we've cleaned up more missed rate notices than we can count. We'd rather help you catch the next one on time. No tickets, no hold queues — a dedicated consultant who knows your states, your setup, and your history. Hair on fire? Call us.
Got a rate notice sitting in a pile right now? REQUEST A CONSULTATION.
ADP and the ADP logo are registered trademarks of ADP, Inc. This article is general guidance, not tax or legal advice; SUI rules, rates, and wage bases vary by state and change annually, so confirm specifics with your licensed advisor and your state agency.