Paying one contractor in one state is simple. Paying 20 contractors across 12 states feels like it should be 12 times the work. In practice it is worse than that, because every state adds more than another payment to run: it adds another set of rules about who counts as a contractor at all.
Plenty of companies get here one hire at a time. A specialist in Texas, a developer in Ohio, a project team that turned out to live in 9 different states. Nobody designed the footprint. Then someone in finance asks a reasonable question about state filings, and nobody has a confident answer.
Three things are worth knowing: what actually changes when contractors cross state lines, where the real risk sits, and when to stop managing it by hand.
Paying true contractors across states is the easy part
For genuine independent contractors, the payment side of multistate work is mostly a reporting job. Federally, the 1099 forms cover the income. Some states want their own copy of that reporting, some take it through the combined federal and state filing program, and a few have requirements of their own. Administrative work rather than danger, and all of it trackable.
That's the version of the problem most payment tools are built for, and it's the version most companies think they have.
The real problem is that "contractor" means something different in each state
The classification tests are where multistate work turns dangerous. The IRS runs one test. States run their own, and some of the biggest contractor states run much stricter ones. California and New Jersey, among others, apply versions of the ABC test, which presumes a worker is an employee unless the company can prove otherwise on all three parts.
So the same person, doing the same work, can be a legitimate contractor in one state and an employee in another. Your risk is not the average across your footprint. It is the strictest state you touch.
And the moment any contractor in any state should really be an employee, the easy version of the problem disappears. Employing someone in a state generally means registering as an employer there: payroll tax accounts, unemployment insurance, workers compensation. Multiply that by every state where a conversion is overdue, and add the retroactive exposure for the period they were misclassified.
The tipping point
There is a workforce size where hand managing this stops being sensible, and it's smaller than most companies think. The pattern that shows up over and over: contractor records living in a spreadsheet next to the payroll system, classification decided by whoever did the engagement, and no one person who can say, today, how many states the company is exposed in.
Three signs the tipping point has passed. Nobody can produce the state by state contractor list without an afternoon of work. Classification calls were made engagement by engagement, without a consistent test. And at least one contractor has been engaged in California, New Jersey, or another strict test state without anyone checking that state's rules specifically.
What the fix looks like
The fix is centralizing the thing that is currently scattered: one consistent classification standard, one record of the reasoning, and one place where per state compliance is somebody's actual job.
That is the shape of what myBasePay does for flexible workforces. For genuine 1099 contractors, our Agent of Record service applies a consistent classification standard across every state, handles agreements and payments, and keeps the compliance file. For flexible workers who should be W-2, our Employer of Record becomes their legal employer, already set up in all 50 states, so a conversion doesn't put employer registrations on your plate: the EOR carries them. Your team keeps directing the work. The state by state burden moves to a partner built to carry it.
Frequently asked questions
Do I have to register my company in every state where a contractor lives?
Generally no, for genuine independent contractors: engaging a true 1099 contractor does not usually require registering as an employer in their state. The risk is classification. If a contractor in a state should legally be an employee, employing them there generally does require registration, along with payroll tax and insurance obligations.
Do states have different rules for independent contractors?
Yes. The IRS applies its common law test, but states run their own tests, and some are much stricter. California and New Jersey, among others, apply versions of the ABC test, which presumes a worker is an employee unless the company proves otherwise. The same worker can be classified differently in different states.
What is the biggest risk of paying contractors in multiple states?
The biggest risk is classification rather than payment. Moving money and filing 1099 forms is manageable. The exposure comes from a contractor in a strict test state who should legally be an employee: back taxes, penalties, and employer registration obligations in that state, applied retroactively across the engagement.
How does an Employer of Record help with multistate workers?
An Employer of Record is already established as an employer across all 50 states. When a flexible worker needs to be W-2, the EOR employs them on your behalf and carries the employer registrations, payroll accounts, and state by state employment rules. Your team directs the work; the EOR carries the compliance.
This guide is general information about multistate contractor compliance, not legal or tax advice for your specific situation. For that conversation, talk to us or your counsel.