A business owner hires a great candidate who happens to live three states away, sets them up on payroll, and moves on. Nothing about the hiring process feels like it should touch corporate tax filings. But in most states, physical presence is physical presence, and an employee working from a home office counts. One remote hire can be enough to establish nexus, the legal threshold that gives a state the right to tax your business or require you to register and file there.
What we see most often is confusion between sales tax nexus, which many owners have at least heard of, and payroll or income tax nexus, which is a separate and often stricter standard. Sales tax nexus usually depends on a revenue or transaction threshold. Employee-based nexus frequently doesn't. In many states, a single employee physically working within the state is enough on its own, regardless of revenue generated there. That employee doesn't need to be selling anything or meeting with clients. Their desk being in that state is often the entire trigger.
Once that nexus exists, a handful of obligations tend to follow in sequence. State income tax withholding is usually the first: the employer generally has to register with the state's tax agency and start withholding state income tax from that employee's wages, separate from whatever is already being withheld for the employer's home state. State unemployment insurance (SUTA) registration is typically next, since most states require employers with even one covered employee to register and pay into the state fund. Depending on the state and the business's activity, corporate income or franchise tax nexus can follow as well, which means the business may need to file a state return and apportion some share of its income to that state, even if the employee's role has nothing to do with generating revenue there. And workers' compensation coverage (see: Insurance services) is its own separate requirement, since most states require coverage for any employee working within their borders, regardless of where the company is headquartered.
The comparison worth making here is proactive registration vs. reactive discovery. A business that registers before or immediately after the hire deals with a short list of setup tasks: a withholding account, a SUTA account, possibly a corporate registration. A business that doesn't often finds out the obligation existed when a state sends a notice, sometimes years later, covering back taxes, penalties, and interest across the entire period the employee worked there. States have gotten better at cross-referencing federal W-2 filings against their own registration records, which is usually how these gaps surface.
This is also where the cross-disciplinary piece matters. A remote hire is not purely an HR decision. It's a payroll tax question, a workers' comp question, and potentially a corporate tax filing question, all triggered by the same event. In practice, this usually shows up when a hiring manager makes an offer without looping in anyone who handles tax or compliance, because from the hiring side, nothing about the process looks different from hiring locally. The gap isn't a lack of diligence. It's that the trigger point (an offer letter) and the compliance obligation (a state tax registration) live in completely different parts of the business and nobody owns the handoff between them.
One thing owners consistently underestimate is how fast this compounds with a distributed team. One remote employee in one new state is a manageable setup task. Five employees across five states, hired over eighteen months without a consistent process, is a much harder problem to unwind retroactively, because each state has its own registration timeline, its own penalty structure, and its own definition of what triggers nexus in the first place. A written policy for how remote hires get flagged and registered (see: HR & Workforce services) closes most of that gap before it opens.
There's also a question worth asking before the hire, not after: does this role need to be based in that state at all, or is there flexibility in location that could avoid creating nexus in the first place? That's not always the right call, since restricting a hiring pool to avoid a tax registration can cost more in missed talent than the registration itself would ever cost. But it's a tradeoff worth making consciously rather than discovering it wasn't considered at all.
If your business has hired outside its home state, or is about to, it's worth confirming what that hire actually triggers before the first payroll run, not after a state notice arrives. A quick review of your multi-state exposure (see: Tax services) usually takes less time than most owners expect, and it's a much smaller task than unwinding a multi-year gap. Reach out (see: Contact) and we can walk through what your current footprint actually looks like.