The short answer
An employee working in another state usually creates obligations in that state on their first paycheck: withholding registration, an unemployment insurance account, new hire reporting and often a paid leave or disability account. The same employee can also create corporate income tax and sales tax filing obligations there. None of it is triggered by revenue, and none of it waits for you to notice.
Hiring one person in another state usually creates payroll obligations in that state on their first paycheck. Registration, withholding, unemployment insurance, and in many places a separate paid leave or disability account. None of it is triggered by how much revenue you have there, and none of it waits for you to notice.
Employers tend to think of a remote hire as a payroll setting. It is closer to opening a small branch office. The usual list for a single employee in a new state:
Each item is minor. The aggregate across a distributed team is a compliance function, and it arrives without anyone deciding to build one.
The default rule is that wages are sourced to where the work is physically performed, and withholding follows the work location. An employee who lives and works in another state generally gets withholding for that state, not for yours, regardless of where your office is and where the payroll is run.
Then it gets more involved:
Two wrinkles catch employers who assume work location settles everything.
Reciprocity agreements. Certain neighboring states agree that a resident of one working in the other is withheld only for their home state. These agreements are specific, bilateral, and dependent on the employee filing a certificate with you. They are useful when they apply and irrelevant when they do not, so never assume reciprocity exists without checking the specific pair of states.
Convenience of the employer rules. A handful of states take the position that if an employee works from home for their own convenience rather than because the employer requires it, the wages remain sourced to the employer's location. When your company is based in one of those states and the employee's resident state also taxes the income, you can face competing claims on the same wages and an employee who cannot fully credit one against the other. Where your situation touches one of these states, the employment agreement language about required work location is not boilerplate. It is evidence.
This is the part that surprises founders. Payroll in a state is a physical presence in that state, and physical presence generally creates nexus for corporate or franchise income tax. One remote employee can therefore create a state income tax return obligation for the company, even if you have no customers, office or property there.
Two consequences follow.
First, the company likely has a filing obligation in that state, often with a minimum tax or fee whether or not there is taxable income allocated there. Those small annual amounts are cheap to pay and expensive to discover three years late with penalties attached.
Second, apportionment changes. Many states apportion income based on revenue sourced to the state, and a few still weigh payroll and property. More importantly, establishing nexus somewhere can change how revenue is sourced out of your home state, which means a new state can reduce tax in one place while adding it in another. The net effect is sometimes favorable. It is never zero, and it should be modeled rather than discovered.
Pass-through entities add a layer, because nexus in a new state can create nonresident filing obligations for the owners and composite or withholding requirements for the entity.
An employee working in a state is physical presence for sales tax purposes as well. For a company selling taxable goods or software, that can create a registration and collection obligation in a state where the economic thresholds alone would not have been met yet.
Software companies get caught here because taxability of software, software as a service and digital products varies sharply by state. The same subscription can be taxable in one state and exempt in the next. One remote engineer can therefore convert a non-issue into a collection obligation on sales you have been making untaxed.
The exposure here is worse than the income tax version, because uncollected sales tax is money you should have collected from customers and now have to pay yourself.
The most common failure mode we see is a reasonable one: the company assumed the payroll platform was handling state compliance because the platform is capable of handling it.
Modern payroll systems will file and remit in any state once the state accounts exist and the employee's work location is set correctly. What they generally do not do is register you, decide whether the work location is set correctly, tell you the hire created a corporate filing obligation, or flag that the state requires a foreign qualification. A professional employer organization takes on more, but the scope of what it covers is defined by your service agreement, and corporate income and sales tax are almost never in it.
So the gaps cluster in predictable places: an employee whose address was updated in the HR system but whose work state was never changed in payroll, a state account that was never registered so filings have been rejecting silently, a paid leave program that started after you onboarded, and a corporate return nobody owns.
The fix is a quarterly reconciliation between your employee roster by work state and your registration list by state. It takes an hour and it is the single highest-value control in this entire area.
Treat the work location as a term of the offer, not an administrative detail discovered at onboarding.
If you discover that an employee has been withheld in the wrong state, the cleanup is mechanical but order matters.
Payroll records are also the input for several other things you will need. If the underlying wage data by state is not clean in the ledger, see our bookkeeping and close work, because apportionment, provisions and diligence all read from it.
We run this as a map, then a build, then a control.
The payroll execution side is described on our payroll services page, and the resulting state entity filings sit with entity tax preparation.
Generally yes. Payroll obligations are triggered by the presence of an employee performing work in the state, not by a headcount or revenue threshold. One employee usually means withholding registration where the state has an income tax, an unemployment insurance account everywhere, and new hire reporting.
Usually not by default. Most providers will file and remit once the accounts exist and the work location is set correctly, but registering the company, deciding the correct work state, and handling corporate income or sales tax obligations are typically outside their scope. Check your service agreement rather than assuming.
Withholding generally follows where the work is physically performed. For a fully remote employee that is their home state. Split schedules require allocation across both, and a small number of states apply a convenience-of-the-employer rule that can keep the wages sourced to the employer's location.
Yes. An employee working in a state is physical presence, which generally establishes nexus for corporate or franchise tax. That often means a return and a minimum tax or fee in that state, and it can change how your revenue is apportioned out of your home state.
Stock compensation is generally sourced over the period the award was earned, so a state where the employee worked while the award was vesting can tax part of the income even after they leave. This requires tracking work location over the life of the grant, and it is the most commonly missed multi-state item.
Establish the correct work location by period, register in the correct state, file and remit the missing returns with an abatement request where reasonable cause applies, and issue corrected wage statements so the employee can file correctly. For corporate and sales tax periods, look at voluntary disclosure before any agency makes contact.
Remote hiring is a good operating decision that quietly creates a compliance function. The cost of doing it correctly is an afternoon of registrations per state and an hour a quarter of reconciliation. The cost of doing it by accident is unfiled returns in several states, uncollected sales tax you now owe yourself, and a diligence finding at the worst possible moment.
If you have hired across state lines without a nexus review, or you are about to, schedule a complimentary consultation. We will map your current footprint against your registrations and tell you exactly which states are open.