A company usually finds out it has a multi-state payroll problem the same way: someone gets a notice in the mail from a state department of revenue they didn’t know they had a relationship with. By then the company has usually had an employee working there for months, sometimes closing in on a year, and nobody flagged it because nothing about hiring the person felt like it crossed a border.
They filled out an offer letter, signed a contract, and started work from wherever they already lived.
Payroll tax obligations follow the employee’s physical work location, not the company’s headquarters, and not where the employee happens to be paid from. A company based in Delaware with its only office in New York still owes withholding tax in Ohio the moment it hires someone who works from Ohio, even if that person never sets foot in the New York office. This catches founders off guard because most of them assume state tax exposure is about where the company is incorporated or where its bank account sits. It isn’t. It’s about where people are physically doing the work, and remote hiring makes that answer different for every employee on the team.
Withholding registration is usually the first piece that gets missed, and it has a deadline attached to it that most founders don’t know exists. States generally expect an employer to register for state income tax withholding before or shortly after the first paycheck goes out to an employee working in that state, not after. Miss that window and the company owes back withholding, plus interest, calculated from the employee’s start date rather than the date someone eventually noticed the gap. One client had built out a fully distributed engineering team over about eighteen months, hiring one or two people at a time in whatever state they happened to live. Nobody registered the company for withholding in Colorado until a new hire’s second paycheck bounced back from the state’s system with an error, at which point the company had already missed four months of required filings for that one employee alone.
Unemployment insurance registration runs on its own separate clock, and it’s the piece that gets confused with withholding most often, because both show up on the same paycheck and both involve a state agency. They’re not the same registration, and missing one doesn’t tell you anything about whether you’ve handled the other. A company has to register for state unemployment insurance, sometimes called SUI, in every state where it has employees working, and that registration typically needs to happen within 20 to 30 days of the first hire in that state depending on where it is. New employers get assigned a starting SUI rate, usually somewhere in the range of 2 to 4 percent of taxable wages depending on the state, and that rate can climb if a former employee ever files for unemployment against a company that never registered at all. At that point the state doesn’t just charge back taxes. It treats the company as having had the highest possible rate for the entire period it should have been registered.
Foreign qualification is the part almost nobody expects, because it doesn’t sound like a payroll issue at all. Most states require a company to register as a “foreign entity authorized to do business” once it has an employee working there, separate from any tax registration, and separate from wherever the company was originally incorporated. Skip this step and a company can technically lose its ability to enforce contracts in that state’s courts until the registration gets fixed, on top of owing back fees and penalties for every year it operated unregistered. A startup that hires its fifth employee in a fifth state has usually triggered five separate foreign qualification filings without anyone on the founding team realizing that’s what just happened, because the paperwork lives with the Secretary of State’s office rather than the tax department, and nobody thinks to check both.
New hire reporting is the smallest of these requirements and the one most likely to slip through entirely, because it has nothing to do with taxes on its face. Federal law requires every employer to report new hires to a state directory within 20 days of the start date, regardless of which state the employee works in, and that requirement exists specifically to help states enforce child support orders. It’s a short form. It takes a few minutes to file. Companies miss it constantly because it doesn’t show up in most payroll software checklists the way withholding and SUI do, and it’s genuinely easy to forget when nobody’s ever mentioned it.
Local taxes are the layer that catches even careful teams, because they don’t follow any pattern that generalizes from state to state. Pennsylvania has local earned income tax administered by the municipality where an employee lives, not just the state. Ohio has a similar system built around individual cities and school districts, some of which levy their own income tax entirely separate from the state’s. New York City adds its own resident tax on top of state withholding for anyone living within the five boroughs. None of this shows up if a company only checks state-level requirements, and payroll providers don’t always flag it automatically unless someone manually confirms the employee’s specific home address down to the municipality.
The pattern across all of this is the same. None of these requirements are secret, and none of them are particularly hard to comply with individually. A company just has to know to look for five or six different things every time it hires someone in a state it hasn’t operated in before, and most founders learn the list exists only after missing the first item on it.