Remote Startup Multi-State Payroll Case Study: Cleaning Up Eight States Before It Became a Crisis

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 actually sit and work. So a remote support rep in Georgia means Georgia SUTA — full stop.

The audit surfaced three problems:

• Five unregistered states with active employees, meaning withholding and unemployment that had never been set up, plus filings that were already late.
• Local taxes in two states the payroll platform had ignored entirely — Pennsylvania's local Earned Income Tax and an Ohio municipal tax, both of which sit underneath the state layer and get missed constantly.
• A New York wrinkle, because New York is one of a small group of states (along with variations in Pennsylvania, Delaware, Nebraska, and New Jersey) that apply a "convenience of the employer" rule. That rule can pull a remote employee's wages into New York's tax net based on where the employer is located, not just where the employee sits — which changes the withholding answer.

None of this had triggered a notice yet. That is the trap. Penalties for late registration and late filings accrue silently, per state, per quarter, and the first letter usually arrives after the bill has already grown teeth.

How the cleanup got done before a single notice landed

The approach was deliberately boring, which is exactly what you want when the alternative is a five-figure penalty cycle.

First, register everywhere with an active employee. Income tax withholding accounts and unemployment accounts in all five missing states, done in the correct order so the account numbers existed before any catch-up filing went in.

Second, file the back returns. Late is better than never, and in most states a voluntary catch-up filing — before the state comes looking — is treated very differently than one extracted by a notice.

Third, request penalty abatement where the facts supported it. Many states allow first-time or reasonable-cause abatement, and the strongest version of that request is one filed proactively, with the registrations already complete and the returns already submitted. You are not asking for mercy mid-violation. You are showing up cleaned-up and asking the penalty to match the corrected behavior.

Fourth, fix the local taxes. The Pennsylvania local Earned Income Tax and the Ohio municipal withholding got set up correctly going forward, and the prior periods were trued up.

What changed, and the math that makes it matter

Run the rough numbers the way Bookkeeper360 ran them. Across five unregistered states, late-registration penalties, late unemployment filings, and late-payment penalties on withholding can stack into the five figures fast — call it a plausible $12,000 to $18,000 of combined exposure for a team this size once interest and per-quarter penalties are layered in.

By registering before any notice and requesting abatement on solid ground, the resolved cost came in at a fraction of that exposure — the registration work, the back filings, and the residual penalties that could not be abated. The difference between those two numbers is the entire value of catching this early instead of opening a certified letter.

The forward-looking win is bigger than the cleanup. Once every state is registered and the payroll platform is configured against the real obligations — not the defaults — the recurring cost is just running payroll correctly. The crisis version of this story, the one where three states send notices in the same quarter, never happens.

Find a bookkeeper who actually knows where your team lives

If you run a distributed team and you have hired faster than you have registered, you are probably in some version of this story right now. The fix is not complicated. It is just specific, state by state, and it gets cheaper the earlier you start.

Bookkeeper360 handles exactly this — payroll and multi-state cleanup for remote-first companies, with QuickBooks and Xero workflows already built around it. Read their verified reviews on Sam's List, then book an intro call and bring your employee-by-state list. The conversation that maps your real obligations is far shorter — and far cheaper — than the one that starts with a penalty notice.

Start with their profile here: Bookkeeper360 on Sam's List.