Your Last Employee Left That State. Your Filing Obligation Didn't.

Most payroll tax compliance advice is about scaling up: you hired someone in a new state, here’s what you now owe. Far less is written about the other direction. An employee in Colorado resigns and isn’t replaced. A sales office in Georgia closes. A remote hire in Ohio relocates back to your headquarters state.

The payroll stops. The obligation doesn’t.

Here’s the part that surprises people: from the state’s perspective, nothing has changed. Your withholding account is still open. Your unemployment account is still open. Both still expect returns on the same schedule they always did. And when those returns don’t arrive, the state doesn’t conclude that you’ve wound down—it concludes that you’ve stopped filing.

An Account Is an Obligation, Not a Description

The mental model that causes this problem is treating a state tax account as a record of activity. It isn’t. It’s a standing obligation with a filing calendar attached.

When you registered, the state assigned you a filing frequency—monthly, quarterly, semi-weekly deposits with quarterly reconciliations, whatever the rules dictated based on your expected liability. That calendar was set at registration and persists until something formally changes it. The agency has no mechanism for noticing that your headcount in the state went to zero, and in most cases it has no interest in inferring it. Employers stop and start payroll in a state all the time—seasonally, between hires, during hiring freezes. A quarter with no wages is not evidence that a business has left.

So the state’s default assumption is continuity. Your account remains active, your due dates remain in force, and the return that’s expected each period is a zero-dollar return: a filing that reports no wages and no tax, but is still a filing.

Skip it, and you haven’t reported “nothing happened.” You’ve failed to file.

Why Failure-to-File Is the Expensive Part

This is where the real cost lives, and it runs directly counter to intuition.

Most people assume penalties scale with the tax owed. If you owe nothing, the penalty on nothing should be nothing. That’s how failure-to-pay penalties generally work—they’re calculated as a percentage of the unpaid balance, so a zero balance produces a zero penalty.

Failure-to-file penalties frequently work differently. Many states impose a flat minimum penalty per delinquent return, or a per-day or per-month charge that accrues independently of the tax due. Unemployment agencies in particular often assess penalties tied to the wage report itself—sometimes structured per employee, sometimes as a flat amount per late report—because the report has administrative value to the state whether or not any contribution accompanies it.

The result is a penalty structure that produces a genuinely absurd outcome: a company that owed a state nothing for eight straight quarters can accumulate a four-figure balance made up entirely of penalties for not filing the returns that would have reported the nothing. There’s no underlying tax to dispute. The liability is purely procedural.

And it compounds quietly. There’s no payroll running in that state, so nobody is looking at the account. The notices go to an address on a registration form filed years ago, or to a portal login nobody checks anymore. By the time the balance surfaces—often during due diligence, or when the company tries to re-register after hiring there again—it represents years of accrual.

The Failure Mode Is Structural, Not Careless

It’s worth being clear about why this happens to well-run finance teams.

Every other part of your payroll tax process is driven by payroll data. Wages flow from the payroll system into calculations, deposits, and returns. That pipeline is self-maintaining in the sense that activity generates its own reminders—a payroll run in a state produces the obligations for that state.

Zero-dollar returns invert the logic. The obligation exists precisely because there’s no data. Nothing in the payroll system triggers it, no wage file references it, and no calculation produces it. It has to be driven by a separate register of open accounts, maintained independently of payroll activity.

Most organizations don’t have that register. They have a payroll system, and their payroll system’s view of “states we file in” is really “states we paid wages in this period.” The moment a state drops off that list, it drops out of the process entirely—while remaining fully active on the agency’s side.

That gap is the whole problem. It isn’t carelessness. It’s a structural blind spot in how nearly every payroll operation is wired.

Closing an Account Is the Fix—And It’s Its Own Process

The way out is to formally close the accounts you no longer need. But “closing” is not one action, and it isn’t automatic.

It’s per-account, not per-state. Your withholding account and your unemployment account are administered by different agencies in most states—revenue on one side, labor or employment security on the other. Closing one does nothing to the other. Companies routinely close withholding, assume they’re done, and keep accruing unemployment report penalties for years.

It requires an affirmative filing. Depending on the state, that means a specific closure form, an account-status change in the agency’s portal, a checkbox on your final return, or written notice. There’s usually an effective date and a reason code, and the agency generally wants to know whether you’ve ceased operations entirely, sold the business, or simply have no employees in the state.

Final returns still have to be filed. Nearly every state requires you to file through the closure period before it will process the request—and often a final annual reconciliation and the associated W-2 data as well. You cannot close your way out of returns you already owe.

It doesn’t erase what already accrued. Closing stops the bleeding going forward. Penalties already assessed for prior unfiled periods remain, and generally have to be addressed on their own—which is precisely why catching this early matters so much more than catching it eventually.

There’s a real timing judgment. If you expect to hire in that state again within a few quarters, closing and re-registering may cost more effort than filing zeros through the gap—and re-registration can carry consequences of its own, including a new employer SUI rate if you lose the experience rating tied to the original account. That’s a deliberate decision to make with the numbers in front of you, not a default to fall into by inaction.

The Discipline That Prevents It

The operational fix is a single artifact most companies don’t maintain: a register of every open state tax account, keyed to the agency and account number rather than to current payroll activity, with the filing frequency and status for each.

With that register, the question at each period close changes from “which states did we pay wages in?” to “which accounts do we have open, and has each one been satisfied?” Those are different questions, and only the second one catches dormant accounts.

Then, whenever an account goes quiet, make an explicit decision: close it, or keep it open and file zeros. Either is defensible. What isn’t defensible—and what costs real money—is never making the decision at all.

At Tax Rails, open accounts are tracked as first-class objects, independent of whether wages flowed in a given period. A dormant account still appears on the filing calendar, still produces its required return, and still gets reconciled. When a client decides to exit a state, closure is handled as a defined process—final returns, the closure filing itself, and confirmation from the agency that the account is actually closed rather than merely assumed to be.

The Bottom Line

State payroll tax accounts don’t close themselves, and states don’t infer your intentions from your silence. Until you formally close an account, you owe a return every period—and the penalties for not filing those returns are largely indifferent to the fact that you owed no tax.

If you’ve been in and out of states over the past few years, it’s worth pulling the list of every account you’ve ever registered and confirming the current status of each. Some of them are probably still open. Some of them may already be accruing.

Happy to help you work through it.