Running payroll for a fully distributed team across multiple US states is one of the most compliance-intensive administrative tasks a growing startup faces. Each state has its own income tax withholding rules, unemployment insurance requirements, workers' compensation mandates, and new hire reporting obligations. A company with employees in eight states is navigating eight separate regulatory environments simultaneously, every pay period. The failure mode is gradual accumulation of compliance gaps that surface during a funding round due diligence or state audit at exactly the wrong time.
This guide is for founders, HR managers, and finance leads at companies with remote teams spread across multiple US states who want to understand what multi-state payroll compliance actually requires and which platforms handle it well. It covers state income tax withholding mechanics, unemployment insurance, workers' compensation across states, and the specific platform features that matter for distributed teams. It focuses on US domestic multi-state compliance; international payroll for employees and contractors in other countries is a separate topic with its own platform considerations and is not covered in depth here.
Why Multi-State Payroll Is Genuinely Complex
The complexity of multi-state payroll is not primarily technical—it is regulatory. Every state that has a personal income tax (currently 43 states plus Washington DC) requires employers to register as an employer in that state, obtain a state employer identification number, withhold state income tax at the correct rate from employee paychecks, file periodic payroll tax returns, and remit the withheld amounts on the required schedule.
The compliance calendar is asymmetric. Some states require monthly remittance when withholding exceeds a threshold; others permit quarterly filing. A few states—California and New York prominently—have electronic filing mandates that apply to all employers above a certain size. Getting the schedule wrong—filing quarterly when monthly is required—creates penalties and interest even when the tax amount was correct.
Beyond income tax, employers face state unemployment insurance (SUI) obligations. SUI tax rates vary by state, and new employers are assigned a standard rate while they build their claims history. SUI is filed quarterly in all states but rates and taxable wage bases differ significantly—some states have wage bases under $10,000, while others exceed $40,000 or more. For a company with employees in eight states, this means eight separate SUI accounts, eight quarterly filings, and eight different rate and wage base combinations to track and update annually.
Workers' compensation is a third dimension. Every state requires employers to maintain workers' comp coverage for employees. The requirements for obtaining coverage and the premium rates vary by state and by job classification. A software company with engineers working remotely has a very different risk profile than a logistics company, but the administrative requirement to maintain active coverage in each state applies equally.
State Tax Withholding: The Core Mechanics
The fundamental rule for state income tax withholding is that an employee is taxed in the state where they perform their work—which for remote employees is their state of residence. A software engineer working from their home in Colorado is subject to Colorado income tax withholding regardless of where the company is incorporated or headquartered.
Withholding rates depend on the state's tax structure. Some states have flat rates—Colorado at 4.4%, Pennsylvania at 3.07%—while others have progressive brackets that depend on the employee's filing status and income level. Employees must complete a state withholding form equivalent to the federal W-4 for each state where they owe tax. Payroll platforms handle this automatically when the employee's work state is correctly configured, but it requires that employee location be kept current in the payroll system in real time.
Reciprocity agreements between specific pairs of states—Virginia, Maryland, DC, and Pennsylvania have agreements with each other; Wisconsin and Illinois have one—allow residents of one state to pay income tax only to their state of residence when working in an adjacent state. For remote employees working from their state of residence, these are largely irrelevant, but they matter for employees in specific border-commute situations.
Multi-State Payroll Platforms: What to Look For
Not all payroll platforms handle multi-state compliance equally well. The key capabilities that matter for distributed teams are:
Automatic state registration: Some platforms—Gusto and Rippling notably—offer to register the company as an employer in new states as remote employees are onboarded, eliminating the manual process of applying for state employer IDs, SUI accounts, and workers' comp coverage in each state.
Built-in SUI rate management: The platform should maintain the correct SUI rate for each state and update it when states adjust rates annually. Platforms that require manual rate entry create a compliance risk.
Multi-state year-end reporting: Year-end W-2 processing for multi-state employees requires allocating wages to each state correctly and generating the appropriate state filing attachments. This is more complex for employees who moved states during the year.
Compliance alerts: The regulatory landscape for state payroll taxes changes continuously. A platform that proactively surfaces rate changes, new requirements, and threshold updates reduces the risk of missed compliance steps.
Gusto handles multi-state payroll for companies across all 50 US states. Its guided setup for new state compliance, automatic state registration service, integrated SUI management, and built-in workers' comp partnership make it well-suited for Series A and B companies with distributed remote teams. For a company like a 40-person Series A SaaS with employees in 10 states, Gusto's automatic registration and compliance calendar management covers the majority of the multi-state surface area at a per-employee pricing model that scales predictably.
Rippling extends this with deeper automation for companies with larger or more complex multi-state configurations. Its unified employee record means that a change of address for a remote employee propagates automatically to the payroll system, benefits administration, IT access, and equipment shipping—eliminating the multi-system update process that creates errors at companies managing HR data in multiple disconnected tools. For a 100-person Series B company with employees in 18 states and a complex mix of benefit plans, Rippling's platform consolidation justifies the higher implementation investment.
Workers' Compensation for Remote Teams
Workers' compensation compliance for remote employees in multiple states is a frequently underestimated administrative burden. Every employee must be covered under a workers' comp policy in their state of employment, and the execution involves managing relationships with state-managed funds in monopolistic states (Ohio, Washington, Wyoming, and a few others require coverage through the state fund) and private carriers in all other states.
For a startup with employees in 8–10 states, maintaining separate workers' comp policies across multiple carriers creates annual renewal complexity and premium management overhead. Payroll platforms that include workers' comp administration simplify this significantly. Gusto has a workers' comp partnership that allows coverage to be purchased through the platform, with premiums calculated and paid based on actual payroll rather than an estimated annual payroll with a year-end audit adjustment. Rippling offers similar functionality as part of its broader HR suite.
Employee classification for workers' comp purposes matters. Software engineers working from home on computers are in a low-hazard classification with correspondingly low premium rates. A company that incorrectly classifies employees or fails to update classifications when job roles change may be over- or under-paying premiums—either a cash flow issue or a coverage gap.
Local Payroll Taxes
A third tier of complexity sits below the state level: local payroll taxes in major cities and counties. New York City imposes a city income tax on residents. San Francisco imposes a payroll expense tax on employers. Philadelphia imposes a wage tax on both residents and non-residents who work in the city. Denver imposes an occupational privilege tax.
These local taxes are generally handled automatically by payroll platforms for major supported jurisdictions, but companies hiring in high-local-tax cities should verify that their payroll platform specifically supports those requirements before completing the hire. For unusual local taxing jurisdictions—smaller cities or counties with idiosyncratic rules—confirming platform coverage in advance avoids a compliance gap.
Recommendation
For most Series A and B startups with remote teams spread across multiple states, Gusto provides the right balance of multi-state compliance capabilities and ease of use. Its automatic state registration service, built-in SUI management, integrated workers' comp, and guided onboarding for new remote hires cover the majority of the multi-state compliance surface area. The per-employee pricing model scales appropriately with team growth.
Rippling is the better choice for companies with 50+ employees across many states, particularly those that also need to manage IT provisioning, benefits administration, and global payroll from a single system. The platform's unified employee record eliminates the synchronization overhead that comes from managing payroll, HR, and IT in separate tools.
For companies planning rapid multi-state expansion, it's worth registering employer accounts in anticipated states before the first employee is hired there—the registration process takes days to weeks, and hiring someone in a state where you're not registered creates a compliance gap from day one.
Conclusion
Three core principles for multi-state payroll: Register in each state before the first payroll run for employees there, not after. Choose a payroll platform with automatic state registration support to eliminate the manual burden as the team grows. Keep employee address data current in real time—a remote hire who moves to a new state creates a new compliance obligation on their first day in the new location, and late discovery means late compliance.
The next step is to audit the current team's state distribution against the payroll platform's supported jurisdiction list. Any state where the company has employees but the payroll platform has compliance gaps is a risk requiring immediate attention.
FAQ
**Q: If a remote employee moves to a new state, what changes in payroll?**The company must register as an employer in the new state if not already registered, update withholding setup to the new state's rules, obtain updated state withholding forms from the employee, and potentially establish workers' comp coverage. Rippling automates several of these steps through its unified HR system.
**Q: Are there states with no income tax that simplify multi-state payroll?**Yes—Alaska, Florida, Nevada, South Dakota, Texas, Washington, and Wyoming have no state income tax, eliminating state withholding for employees in those states. SUI registration and workers' comp requirements still apply regardless.
**Q: What happens if a company runs payroll in a state without being registered?**The company is non-compliant and subject to back taxes, penalties, and interest. The exposure grows with each pay period the issue persists, making early discovery and remediation important.
**Q: Do payroll platforms handle all compliance, or is a payroll attorney still needed?**Platforms handle mechanics: registration, calculation, withholding, filing, and remittance. They don't provide legal advice for complex situations—multi-state moves, stock option taxation across states, executives with income in multiple states, or ambiguous cases. An employment attorney or specialized payroll tax advisor is appropriate for those scenarios.
**Q: Does hiring a remote employee in a new state also create sales tax nexus?**Yes. Employees create physical nexus for sales tax purposes in their state of residence, independent of economic nexus thresholds. This is why connecting payroll data to the sales tax nexus analysis—as Anrok does through HR integrations—is important for distributed SaaS companies.
