Remote Startup Multi-State Payroll Case Study: Cleaning Up Eight States Before It Became a Crisis
Sam's List Editorial | 2026-06-23
Remote Startup Multi-State Payroll Case Study: Cleaning Up Eight States Before It Became a Crisis The fastest way for a remote startup to rack up tax penalties is to hire great people and forget where they live. That is the short version of this remote startup multi-state payroll case study. The longer version is more useful, because the company in it did almost everything right except the one thing that quietly compounds: registering for payroll taxes in every state where it actually had an employee. (A note before we start — the company and numbers below are an illustrative composite, not a single audited client. The mechanics are real. The penalty math is the kind anyone in this spot can run.) Here is the setup. A 14-person SaaS startup, fully remote from day one, hired across eight states in its first big growth year. Engineers in Texas and Colorado. A sales lead in New York. Support reps in Pennsylvania, Georgia, Ohio, North Carolina, and Arizona. The founders ran payroll through a popular self-serve platform, hit "approve" every two weeks, and assumed the software was handling the rest. The software was not handling the rest. The thing nobody tells you about hiring across state lines A single remote employee can create a tax obligation in their home state. Not "might." Does. When someone performs work from their house in Ohio, the company generally has to register for income tax withholding and state unemployment in Ohio, even if the company has no office, no customers, and no other footprint there. Payroll platforms will happily run a check for an employee in a state you have not registered in. They do not stop you. They do not file the registration for you. They withhold based on whatever you told them during onboarding — and if you told them nothing, they sometimes withhold nothing, or withhold for the wrong state. This startup had registered in three states. It had employees in eight. That five-state gap is the entire story. What the multi-state audit in this payroll case study actually found When the founders brought in Bookkeeper360 — a firm whose payroll and multi-state work you can verify through their reviews on Sam's List — the first step was not a fix. It was a count. A proper multi-state nexus cleanup starts with mapping every employee to every state obligation: income tax withholding, state unemployment insurance (SUTA), and any local taxes underneath. For unemployment, states generally follow the Department of Labor's "localization of work" test, which for a fully remote employee usually lands the obligation in the state where they...
