Multi-state payroll for US businesses: A complete guide (2026)

The first time most US businesses realize they have a multi-state payroll problem is when a notice arrives from a state they didn't know they were operating in. An employee moved to Colorado and kept working remotely. A salesperson started making calls from Georgia. A new hire in Texas relocated to Tennessee to accommodate the growing needs of a business. A consultant on a project worked three days at a client site in California.

Each of those situations creates a tax nexus — a legal connection to a state that triggers withholding obligations, registration requirements, and filing deadlines. The obligation doesn't disappear if you ignore it. It accumulates interest, penalties, and (in worst cases) personal liability for the people who signed off on the payroll.

For most of the post-war era, this was a problem reserved for large enterprises with offices in multiple states. Then 2020 happened. Remote work moved from a fringe accommodation to the default for most industries. By 2026, multi-state payroll isn't an enterprise problem anymore — it's the routine reality for almost every growing US business that hires beyond its home state, even once.

This guide is for the US businesses — from a five-person startup with a remote engineer in another state to a 200-person mid-market business managing employees across a dozen jurisdictions that needs to get multi-state payroll right in 2026. We'll walk through what multi-state payroll is, how nexus works, the rules that govern withholding when employees live in one state and work in another, what changed for 2026, the specific compliance traps in California, New York, Pennsylvania, and Ohio, what to look for in multi-state payroll software, and how the right cloud-based system turns 50-state compliance from a quarterly scramble into a quiet background process.

What is multi-state payroll?

Multi-state payroll is the process of managing wages, taxes, deductions, and compliance for employees who live in, work in, or move between more than one US state during a tax year. It involves calculating and withholding the correct federal, state, and local income taxes for each employee, paying the right state unemployment insurance (SUI), filing quarterly returns with each state agency where you have employees, and complying with each jurisdiction's wage-and-hour, paid leave, and workers' compensation rules.

In a single-state payroll, the rules are relatively contained: federal withholding plus one state's withholding, one set of quarterly returns, one minimum wage, one overtime rule, one SUI rate. In multi-state payroll, every one of those variables multiplies — and they don't all line up neatly. Each state has its own income tax brackets (or no income tax), its own unemployment wage base and contribution rate, its own paid leave program (or not), its own filing schedule, and its own enforcement appetite.

The complexity scales with two things: the number of states where you have employees, and the rate of employee mobility (people moving between states, hybrid workers crossing state lines, etc).

Why multi-state payroll matters more than ever in 2026

A few structural shifts have made multi-state payroll a near-universal concern for US businesses, not just a problem for the Fortune 500.

Remote work is permanent. A meaningful share of the US knowledge workforce now works partially or entirely from home, and home isn't always in the state where the employer is headquartered. Once you have one remote employee in another state, you have multi-state payroll obligations.

State enforcement has gotten more stringent. State revenue and labor agencies now actively look for unregistered employers based on data shared between states, federal tax filings, and even social media. The era of "they won't notice one employee in another state" is over.

The penalties have grown. Penalties for failing to register, withhold, or file in a state where you have employees can compound quickly: 5-25% of unremitted taxes plus interest at the state level, loss of the 5.4% FUTA credit (which raises federal unemployment tax from 0.6% to 6.0%), state-level penalties of up to $250,000 per violation in some jurisdictions, and personal liability for officers in some states.

2026 brought a wave of state-level changes. Nineteen states raised their minimum wages, three states launched new Paid Family and Medical Leave programs, eight states cut their income tax rates, multiple states updated their de minimis thresholds, and the federal Social Security wage base jumped from $176,100 to $184,500.

Manual tracking of all of this isn't feasible past about 10 employees and 2-3 states. Multi-state payroll software isn't a productivity upgrade anymore — it's compliance infrastructure.

Understanding payroll nexus: when you owe state taxes

The legal foundation of multi-state payroll is a concept called nexus. Nexus is the connection between your business and a state that gives that state the legal right to require you to register, withhold, and file.

For payroll purposes, nexus is created the moment an employee performs work in a state — no matter how briefly, no matter the dollar amount. Unlike sales tax nexus (which usually has a $100,000+ threshold in most states), payroll tax nexus has a zero-dollar threshold. A single remote worker in California, an employee who takes a meeting in Manhattan, a salesperson who visits Georgia for two days — any of these can trigger payroll nexus.

Once nexus is established, the employer typically has 15-20 days to register with three separate agencies in that state:

1. State Department of Revenue — for income tax withholding (in the 41 states plus D.C. that have state income tax)

2. State Department of Labor — for state unemployment insurance (in all 50 states)

3. State Workers' Compensation agency — for workers' comp coverage (in 49 states; Texas is the only opt-in exception)

Four states (North Dakota, Ohio, Washington, Wyoming) operate "monopolistic" workers' compensation programs where you must purchase coverage from the state fund — you can't use a private insurer.

In the words of payroll compliance teams who deal with this every day: start the registration process 60 days before your first payroll in a new state. The actual processing time at most state agencies is 2-6 weeks, and trying to compress that timeline into 15 days is how compliance gaps start.

The four ways nexus gets established

Most businesses think of nexus only in terms of "where do my employees live?" That's necessary but not sufficient. Nexus can be triggered in four distinct ways:

1. Physical nexus. An employee, contractor, or office located in the state. Even one remote employee triggers full payroll tax nexus.

2. Economic nexus. Hitting a threshold of revenue or transactions in a state — most commonly $100,000 in sales or 200 transactions per year. This typically affects sales tax more than payroll, but it can drag corporate tax obligations along with it.

3. Click-through nexus. Affiliate marketing relationships in a state.

4. Affiliate nexus. Through subsidiaries, parent companies, or related entities.

For payroll specifically, physical nexus through employees is the dominant trigger. The moment an employee is physically performing work in a state — at home, at a client site, at a coffee shop on a Tuesday afternoon — your business has obligations there.

Federal payroll obligations: what stays the same

Before we get into state-specific rules, it's worth grounding in the federal layer, which applies regardless of which state(s) employees work in. Per IRS Topic 751, updated January 2026:

• Social Security: 6.2% (employer) + 6.2% (employee) on wages up to the 2026 Social Security wage base of $184,500. Maximum employee tax: $11,439.

• Medicare: 1.45% (employer) + 1.45% (employee) on all wages, no cap.

• Additional Medicare Tax: 0.9% on employee wages over $200,000 in a calendar year, withheld by the employer with no employer match.

• FUTA: 6.0% on the first $7,000 per employee, typically reduced to 0.6% with the SUTA credit (when state unemployment is paid timely).

These rates apply uniformly. The complexity is in everything that comes after.

State income tax: the default rule and the exceptions

The default rule for state income tax withholding is straightforward: withhold for the state where the employee physically performs the work. If an employee lives in Texas (no state income tax) and works from a home office in Texas, you withhold Texas income tax — which is zero. If an employee lives in California and works from a home office in California, you withhold California state income tax, which is among the highest in the nation.

That's the simple case. There are three structural exceptions where the default rule breaks down: states with no income tax, states with reciprocity agreements, and states with convenience-of-the-employer rules.

States with no income tax

Nine states have no state income tax on wages: Alaska, Florida, Nevada, New Hampshire (interest/dividends only, repealed for 2026 wages), South Dakota, Tennessee, Texas, Washington, and Wyoming. If your employee works in one of these states, no state income tax withholding is required — though you still owe SUI and may owe local taxes.

Reciprocity agreements: simplifying cross-border work 

Sixteen states plus the District of Columbia have reciprocity agreements with one or more other states. These agreements say: if an employee lives in State A and works in State B, and the two states have a reciprocity agreement, the employer withholds only for the employee's home state (A). The employee files only their home state return.

This is meaningful for businesses with employees who commute across state lines or work remotely near borders. If you employ a Pennsylvania resident who works at your office in New Jersey, and they file a New Jersey Form NJ-165 (Employee's Certificate of Non-Residence), you stop withholding New Jersey tax and instead withhold Pennsylvania tax.

States with reciprocity agreements (as of 2026) and the typical exemption forms:

• Illinois ↔ Iowa, Kentucky, Michigan, Wisconsin (Form IL-W-5-NR)

• Indiana ↔ Kentucky, Michigan, Ohio, Pennsylvania, Wisconsin (Form WH-47)

• Iowa ↔ Illinois (Form 44-016)

• Kentucky ↔ Illinois, Indiana, Michigan, Ohio, Virginia, West Virginia, Wisconsin (Form 42A809)

• Maryland ↔ Pennsylvania, Virginia, West Virginia, Washington D.C. (Form MW 507)

• Michigan ↔ Illinois, Indiana, Kentucky, Minnesota, Ohio, Wisconsin (Form MI-W4)

• Minnesota ↔ Michigan, North Dakota (Form MWR)

• Montana ↔ North Dakota (Form MW-4)

• New Jersey ↔ Pennsylvania (Form NJ-165)

• North Dakota ↔ Minnesota, Montana (Form NDW-R)

• Ohio ↔ Indiana, Kentucky, Michigan, Pennsylvania, West Virginia (Form IT-4NR)

• Pennsylvania ↔ Indiana, Maryland, New Jersey, Ohio, Virginia, West Virginia (Form REV-419)

• Virginia ↔ Kentucky, Maryland, Pennsylvania, Washington D.C., West Virginia (Form VA-4)

• West Virginia ↔ Kentucky, Maryland, Ohio, Pennsylvania, Virginia (Form WV/IT-104R)

• Wisconsin ↔ Illinois, Indiana, Kentucky, Michigan (Form W-220)

• Washington D.C. ↔ Maryland, Virginia (Form D-4A)

A critical operational point: until you have the signed exemption form on file, you're legally required to withhold for the work state, regardless of what the reciprocity agreement says. Collecting these forms during onboarding for any cross-border employee is essential.

States that have no reciprocity agreements at all include New York, California, Massachusetts, Connecticut, Colorado, Georgia, Nebraska, North Carolina, Tennessee, and Utah, among others. If you have a cross-border employee involving one of these states, expect to handle nonresident withholding plus a credit on the home state return.

A useful caveat: New York and New Jersey do not have reciprocity. A New Jersey resident working in New York pays New York as a nonresident, and New Jersey provides a credit for taxes paid to New York. This catches a lot of New York-area businesses by surprise.

Convenience of the employer: the rule that flips everything 

A handful of states apply what's called the convenience of the employer rule, which fundamentally changes how remote-work withholding works. Under this rule, if an employee works remotely from another state for their own convenience (rather than because the employer requires it), the employee's wages are treated as earned in the employer's state regardless of where the employee physically performs the work.

The states applying convenience-of-the-employer rules in 2026 include:

• New York — the most aggressive enforcer. If an employer is headquartered in New York and an employee works remotely from another state, New York treats the wages as New York-source income unless the employer can demonstrate the remote arrangement is a genuine business necessity, not just employee preference.

• Connecticut — applies the rule reciprocally with New York.

• Delaware — applies the rule.

• Nebraska — applies the rule.

• Pennsylvania — applies the rule selectively for nonresidents whose Pennsylvania employers require their services performed outside Pennsylvania.

The practical effect: a New York employer with a remote employee in Florida may still owe New York income tax withholding on that employee's wages, even though Florida has no income tax and the employee never sets foot in New York. Reciprocity agreements don't override the convenience rule. This is one of the highest-friction multi-state payroll situations, and it's where having software that knows about convenience-of-the-employer logic earns its keep.

State Unemployment Insurance (SUI/SUTA): one state, not all

SUI is paid entirely by the employer (not the employee, with limited exceptions in Alaska, New Jersey, and Pennsylvania). It funds state unemployment benefits. Every state has its own SUI program with its own wage base and employer-specific rate determined by the employer's experience rating.

Critically, you cannot split SUI across multiple states for the same employee. Per US Department of Labor guidance, an employee's wages are reported to one state for unemployment purposes. To determine which state, use the four-part Localization of Work test, applied in this order:

1. Localization of services: Where is most of the employee's work done? If clearly localized in one state, that's the SUI state.

2. Base of operations: If services aren't localized, where is the employee's base of operations?

3. Place of direction and control: If there's no clear base of operations, where is the employee directed and controlled from?

4. State of residence: As a final fallback.

For most fully remote employees, the answer is the state where they live and work. For mobile employees (sales reps, consultants), the test gets more nuanced, and getting it wrong can result in years of misallocated SUI that's painful to unwind.

The 2026 SUI wage bases vary widely — from $7,000 (in California, Florida, Tennessee, and Puerto Rico) to over $50,000 in Washington and several other states. The employer's actual rate depends on their experience rating, which can range from a fraction of a percent to over 10% in some states.

State Disability Insurance (SDI) and Paid Family and Medical Leave (PFML)

Five states plus Puerto Rico operate State Disability Insurance programs that require contributions:

• California (SDI / PFL) — employee contribution

• Hawaii (TDI) — employee and employer contribution

• New Jersey (TDI / FLI) — employee and employer contribution

• New York (DBL / PFL) — typically employee-paid

• Rhode Island (TDI / TCI) — employee contribution

• Puerto Rico (SINOT) — employee and employer contribution

Beyond SDI, Paid Family and Medical Leave programs are spreading rapidly. As of 2026, the states with active PFML programs include:

• California (PFL — combined with SDI)

• New York (PFL)

• New Jersey (FLI)

• Rhode Island (TCI)

• Massachusetts (PFML)

• Washington (PFML)

• Connecticut (PFML)

• Oregon (Paid Leave Oregon)

• Colorado (FAMLI)

• Maryland (FAMLI) — contributions started 2025

• Delaware (Paid Leave) — launched 2026

• Minnesota (PFML) — launched 2026

• Maine (PFML) — launched 2026

• Washington D.C. (PFL)

Each program has its own contribution rate, wage cap, and reporting requirements. Multi-state payroll software has to know which programs apply for each employee based on work location and apply the right deductions and employer contributions.

Local taxes: the hidden complexity layer

Beyond federal and state, hundreds of US cities, counties, and school districts levy their own local income taxes. The most prominent:

• New York City — separate NYC income tax for residents (graduated up to ~3.876%); Yonkers also has a resident tax.

• Philadelphia and other Pennsylvania municipalities — Pennsylvania has thousands of local Earned Income Tax (EIT) jurisdictions plus a Local Services Tax (LST). Tracking the right rates by employee work and home address is genuinely complex.

• Ohio — over 600 municipal income taxes, administered by multiple agencies (RITA, CCA, plus individual cities). Ohio's school district income taxes add another layer.

• Kentucky — multiple cities and counties levy occupational license taxes.

• Indiana — county-level income tax with separate resident and nonresident rates.

• Detroit, MI — separate city income tax for residents and nonresidents.

• Birmingham, AL — occupational license tax.

• Portland Metro, OR — Metro Supportive Housing Services tax and Multnomah County Preschool for All tax.

• St. Louis and Kansas City, MO — earnings taxes.

Modern multi-state payroll software typically uses a location-based tax engine that determines the applicable local taxes from an employee's work and residence addresses (using latitude/longitude geocoding) and applies them automatically.

State-specific traps to know about

A few states deserve specific attention because they enforce and create disproportionate risk for businesses:

California: Aggressive on nexus — even limited employee activity in California can trigger registration. California has the strictest worker classification rules (the ABC test under AB-5), strict paid sick leave (Healthy Workplaces, Healthy Families Act), pay transparency rules for jobs visible in California, daily overtime (1.5× after 8 hours, 2× after 12 hours per day, plus 7th-consecutive-day rules), and meal/rest break laws with penalty pay. Misclassifying a California worker can attract penalties of $25,000 per violation under California Labor Code Section 226.8.

New York: Convenience-of-the-employer rule, separate New York City and Yonkers income taxes, NY PFL contributions, very specific rules around statutory disability benefits, and aggressive enforcement around wage theft.

Pennsylvania: Local EIT in nearly every municipality, separate Local Services Tax (LST), reciprocity with New Jersey, Indiana, Maryland, Ohio, Virginia, and West Virginia, and the convenience-of-the-employer rule in some scenarios.

Ohio: Hundreds of municipal income taxes administered by RITA, CCA, and individual cities. School district income taxes layer on top. Employees often have a work-state municipality and a home-state municipality both taxing the same income, with credits applying.

Massachusetts: Convenience-style rules in some contexts (specifically, the "Massachusetts source income" doctrine), strict ABC test for worker classification, PFML contributions, and pay transparency rules effective from 2025.

Washington: Capital gains tax (introduced 2022), no income tax on wages, but PFML and Workers' Comp are mandatory and handled at the state level. Long-Term Care (WA Cares) program adds a 0.58% employee contribution.

Colorado: FAMLI contributions, equal pay transparency rules, and a wage theft framework that creates personal liability for officers.

For a multi-state employer with even three or four of these states in the mix, manual compliance is not realistic. The tax tables alone change multiple times a year.

What's new in 2026 for multi-state payroll

The 2026 changes worth knowing about:

• Federal Social Security wage base rose from $176,100 to $184,500, per IRS Topic 751.

• Nineteen states raised their minimum wages effective January 1, 2026.

• Three new state PFML programs launched in 2026 — Delaware, Minnesota, and Maine.

• Eight states cut their state income tax rates for 2026.

• Several de minimis thresholds changed, including Alabama's new 30-day safe harbor (effective October 2025) and Louisiana's upgraded threshold (January 2026).

• Secure Act 2.0 Roth catch-up requirement: Starting in 2026, employees age 50 or older who earned $150,000 or more in FICA wages the previous year must make all 401(k) catch-up contributions on a Roth (after-tax) basis.

• Pay transparency expansion: Multiple states now require salary ranges in job postings, with enforcement varying by jurisdiction.

A multi-state payroll system that doesn't ingest these changes automatically is a multi-state payroll system that's quietly running on stale rules.

How to set up multi-state payroll: a step-by-step process

Here's the operational playbook for a US business adding a new state to its payroll.

Confirm nexus. Once you know an employee will be performing work in a new state, you have nexus. Don't wait to act.

Register with the state Department of Revenue. Apply for a state tax ID for income tax withholding. Lead time: typically 2-4 weeks. Some states offer same-day online registration.

Register with the state unemployment agency. Apply for a SUI account number. Lead time: typically 2-6 weeks. The state will assign your initial SUI rate, often the new-employer rate.

Set up workers' compensation coverage. For most states, this means a private insurance policy. For North Dakota, Ohio, Washington, and Wyoming, this means buying coverage from the monopolistic state fund.

Register for any local taxes. If the employee is in Pennsylvania, Ohio, Indiana, Kentucky, or other local-tax states, register with the relevant local agencies.

Set up state-specific programs. PFML enrollment in states that have it. SDI enrollment where applicable. Paid sick leave compliance per state rules. Long-Term Care withholding in Washington. Any other state-specific levies.

Collect the right onboarding forms. Federal W-4 plus the state's withholding certificate (for the work state) plus, if reciprocity applies, the home state's exemption certificate. Verify I-9.

Configure your payroll system. Add the new state to your payroll software with the correct tax IDs, SUI rate, withholding settings, and any local jurisdictions.

Verify with a test pay run. Before processing the first real payroll, run a test to confirm calculations are correct.

Set up filing reminders. Each state has its own quarterly and annual filing schedule. Most multi-state payroll software handles this automatically — but verify.

What to look for in multi-state payroll software

Here's the evaluation framework for any US business choosing multi-state payroll software in 2026.

Does it cover all 50 states with native support? 

Some platforms claim 50-state support but have meaningful gaps in local tax handling, paid family leave compliance, or specific state edge cases. Test with your actual state mix. Zoho Payroll's US edition handles federal, state, and local taxes for all 50 states, with automatic filings to every relevant agency.

Does it automatically update tax tables? 

Federal, state, and local rates change multiple times a year. The software should pull updates centrally and apply them on January 1 (and mid-year if needed) without you doing anything.

Does it generate W-2s for multi-state employees correctly? 

When an employee works in two states in a single year (or moves mid-year), the W-2 needs to allocate wages and withholding correctly per state. This is one of the most common areas of multi-state payroll error.

Does it handle reciprocity automatically? 

When an employee submits a reciprocity exemption form, the software should let you flag the employee accordingly and switch withholding to the home state automatically. It should also stop withholding the work state immediately, with no manual override required.

Does it handle the convenience-of-the-employer rule? 

For employers with operations in New York, Connecticut, Pennsylvania, Delaware, or Nebraska — and remote employees scattered across the country — the system needs to know about convenience-of-the-employer logic and apply the right state's tax accordingly.

Does it handle local taxes with location-based accuracy? 

For Pennsylvania, Ohio, Indiana, Kentucky, and other local-tax states, the software needs to identify the correct local jurisdictions from the employee's work and home addresses (geocoded, ideally) and apply the right rates.

Does it manage SUI correctly per the Localization of Work test? 

The system should let you assign each employee to the right SUI state, track the wage base and rate, and produce SUI returns for every state where you have employees.

Does it track and apply state-specific paid leave programs? 

PFML, SDI, FLI, FAMLI, TDI, TCI, WA Cares — every active state program should be supported with the right contribution rates and reporting.

Does it support the new 2026 Roth catch-up rule? 

For employees age 50+ earning $150,000+ in the prior year, all 401(k) catch-up contributions must be Roth. Multi-state payroll software needs to identify the affected employees and route their catch-up contributions to a Roth bucket.

Does it integrate with accounting and HR systems? 

Multi-state payroll generates a lot of journal entries, tax accruals, and reconciliation work. Native integration with accounting (Zoho Books, QuickBooks, Xero) and expense management is essential. Zoho Payroll integrates natively with Zoho Books and Zoho Expense — eliminating the manual sync that fragments most multi-state operations.

What's the pricing model? 

Some platforms charge per state, per filing, per W-2, or per employee per state. The economics get ugly fast. Look for transparent per-employee-per-month pricing that includes all states without surcharges. Zoho Payroll's US pricing doesn't add per-state fees — it covers all 50 states at the standard per-employee rate.

How is the support structured? 

When something goes sideways at 5pm on the 28th of the month, you need real support. US-based phone support, knowledgeable agents, and an active knowledge base matter — especially for multi-state issues that don't have one-size-fits-all answers.

How Zoho Payroll handles multi-state payroll for US businesses

We built Zoho Payroll's US edition for the realities of running payroll in 50 states with a workforce that may be sitting in five of them on any given Wednesday. Here's how it maps to the criteria above.

Full 50-state coverage as a default. Federal, state, and local tax handling for all 50 states comes standard — no per-state surcharges, no add-ons. State income tax, SUI, SDI, PFML, FLI, FAMLI, TDI, and other state-specific programs are handled automatically based on each employee's work and residence location.

Automatic tax table updates. The 2026 Social Security wage base ($184,500), the new state PFML programs in Delaware, Minnesota, and Maine, the eight state income tax cuts, the 19 minimum wage increases — all applied automatically from the relevant effective date. No patches, no spreadsheets, no manual updates.

Reciprocity and convenience rules. When an employee submits a reciprocity exemption form, you can flag them in the system and Zoho Payroll switches withholding to the home state. For employers in New York or other convenience-of-the-employer states, the system handles the more complex withholding logic for remote employees.

Location-based local tax handling. Zoho Payroll uses location-based tax determination to identify and apply the right local taxes — Philadelphia EIT, Ohio municipal taxes, NYC and Yonkers, Indiana county taxes, and the rest — without manual configuration per employee.

Multi-state W-2 generation. When an employee works in multiple states in a single year, Zoho Payroll allocates wages and withholding correctly across the W-2's state boxes, ensuring both employee tax filings and state agency reconciliations stay clean.

Native ecosystem integration. Multi-state payroll generates a lot of journal entries — separate state withholding accruals, separate SUI accruals, separate local tax payables. Zoho Payroll's native integration with Zoho Books posts each of these to the right accounts automatically. Reimbursements from Zoho Expense flow into the salary payment, and HR data from Zoho People syncs continuously.

Transparent pricing. No per-state fees, no per-W-2 charges, no extra cost for ACA reporting. The published Zoho Payroll pricing is what you pay.

Modern security with US data residency. 256-bit SSL encryption, multi-factor authentication, role-based access control, and SOC 2 Type II / ISO 27001 / GDPR compliance — backed by US data centers so payroll data stays in the country.

For US businesses that have outgrown spreadsheets but don't want enterprise complexity, Zoho Payroll covers multi-state compliance without making the buyer pay for 50 separate state modules.

Common mistakes US businesses make with multi-state payroll

A few patterns we see repeatedly:

Waiting to register until "we have time." The 15-20 day registration window starts when the employee starts working, not when you get around to it. Penalties begin accruing immediately.

Treating an employee's home state as the SUI state without applying the Localization of Work test. Most of the time the home state is right, but for mobile employees it isn't, and getting it wrong creates years of unwinding.

Missing the convenience-of-the-employer rule. If you're a New York employer with a remote employee in Florida, assuming Florida has no income tax obligation is a costly mistake. New York likely still wants its tax.

Forgetting to collect reciprocity exemption forms. Without the signed form on file, you must withhold for the work state regardless of reciprocity. This catches a lot of cross-border employers.

Underestimating local tax complexity. Pennsylvania alone has thousands of local jurisdictions. Ohio has over 600 municipalities with income taxes. If your software handles these as a list of cities you have to manually enable, you'll miss things.

Ignoring de minimis thresholds for business travel. Twenty-one states plus D.C. require withholding from day one for nonresident workers. California, Massachusetts, Pennsylvania, Kentucky, and others have no minimum threshold. A two-day client visit can trigger withholding obligations.

Choosing payroll software that charges per state. When you have employees in eight states, per-state pricing turns a $200/month bill into a $1,500/month bill. It's a procurement mistake that compounds.

Not allocating multi-state wages on W-2s correctly. If an employee worked half the year in California and half in Texas, their W-2 needs Box 15-17 reflecting both states' wages and withholding correctly. Manual handling is where this breaks.

Frequently asked questions

• What is multi-state payroll? 

Multi-state payroll is the process of managing wages, taxes, deductions, and compliance for US employees who work in or live in more than one state during a tax year. It involves applying federal, state, and local tax rules for each employee's work location, paying state unemployment insurance to the right state, filing quarterly returns with each applicable state agency, and complying with each state's wage-and-hour, paid leave, and workers' compensation rules.

• What triggers multi-state payroll obligations? 

Multi-state payroll obligations are triggered the moment an employee performs work in a state where your business isn't already registered as an employer — even one remote employee in another state creates full payroll tax nexus. Unlike sales tax, payroll tax nexus has a zero-dollar threshold.

• How does state reciprocity work for payroll? 

A reciprocity agreement lets an employee who lives in one state and works in another pay state income tax only to their home state. Sixteen states plus D.C. participate in reciprocity agreements, covering about 30 state-pair arrangements concentrated in the Mid-Atlantic and upper Midwest. To qualify, the employee files a state-specific exemption certificate with the employer (e.g., Pennsylvania Form REV-419, Michigan Form MI-W4). Without the form on file, the employer must withhold for the work state regardless of reciprocity.

• What is the convenience of the employer rule? 

The convenience-of-the-employer rule, used by New York, Connecticut, Delaware, Nebraska, and Pennsylvania (in specific scenarios), treats a remote employee's wages as earned in the employer's state if the remote arrangement is for the employee's convenience rather than the employer's necessity. Reciprocity agreements don't override this rule. New York is the most aggressive enforcer.

• How do I handle SUI for an employee who works in multiple states? 

Per US Department of Labor guidance, an employee's wages must be reported to one state for SUI purposes. The four-part Localization of Work test determines which state: (1) where services are localized, (2) base of operations, (3) place of direction and control, (4) state of residence. For most fully remote employees, this is their home state.

• Do I need to register in every state where I have an employee? 

Yes. Once you have an employee performing work in a state, you typically must register within 15-20 days with the state Department of Revenue (for income tax withholding), the state unemployment agency, and arrange workers' compensation coverage. Lead time on registrations is 2-6 weeks, so start the process before the first payroll.

• What's the penalty for missing multi-state payroll registration? 

Penalties vary by state but commonly include 5-25% of unremitted taxes plus interest, loss of the 5.4% FUTA credit (raising federal unemployment tax from 0.6% to 6.0%), state-level fines up to $250,000 per violation in some jurisdictions, and possible personal liability for officers in some states.

• Does Zoho Payroll handle all 50 US states? 

Yes. Zoho Payroll's US edition handles federal, state, and local taxes for all 50 states, including reciprocity, convenience-of-the-employer rules, multi-state SUI, state PFML programs, SDI, and local tax jurisdictions.

• What changes for multi-state payroll in 2026? 

For 2026: the federal Social Security wage base rose to $184,500; nineteen states raised minimum wages; three new state PFML programs launched (Delaware, Minnesota, Maine); eight states cut their income tax rates; Alabama added a 30-day de minimis safe harbor; Louisiana upgraded its threshold; and the Secure Act 2.0 Roth catch-up rule applies to employees age 50+ earning over $150,000 in the prior year.

• What's the difference between SUI and SDI in multi-state payroll? 

SUI (State Unemployment Insurance) funds unemployment benefits and is paid by the employer in all 50 states. SDI (State Disability Insurance) funds short-term disability benefits and is operated by California, Hawaii, New Jersey, New York, Rhode Island, and Puerto Rico, typically with employee contributions. Both are state-specific and handled separately in payroll.

• Can I switch payroll providers mid-year while running multi-state payroll? 

Yes, but it requires careful year-to-date data migration so W-2s remain accurate. The new provider needs to import each employee's wages, federal withholding, state withholding, SUI wage history, and any local tax history per state. Zoho Payroll's implementation includes guided YTD migration support to make mid-year switches clean.

• Where does Zoho Payroll store multi-state US payroll data? 

Zoho Payroll stores US customer data in Zoho's US data centers, ensuring US data residency for businesses with that requirement. Encryption in transit and at rest is the default, with SOC 2 Type II, ISO 27001, ISO 27701, and GDPR certifications backing the security posture.

A simpler way to run payroll across 50 states

The US payroll environment in 2026 is uniquely challenging — and uniquely fragmented. There's no single federal payroll authority that resolves multi-state complexity. There are 50 separate state revenue agencies, 50 separate state labor agencies, 50 separate state workers' comp regimes, and thousands of local tax jurisdictions on top of that. The rules change every January, and they change again mid-year. The penalties for getting it wrong are real and personal.

The US businesses that handle multi-state payroll well in 2026 aren't doing more manual work. They've moved to cloud-based payroll software that absorbs the complexity — automatic state and local tax updates, native reciprocity handling, convenience-of-the-employer logic, multi-state SUI, location-based local taxes, automatic state filings, and W-2s that allocate correctly across jurisdictions. The finance team approves a pay run; the system handles the rest.

We built Zoho Payroll for US businesses with this in mind — multi-state compliance as infrastructure, not as a checklist your team has to maintain quarter after quarter. From a five-person startup with one remote engineer in another state to a 200-person mid-market business across a dozen jurisdictions, the platform scales without breaking, prices honestly without per-state surcharges, and integrates with the broader business stack so payroll stops being a silo.

A simpler way to pay people across America is a simpler way to run an American business. Try Zoho Payroll free for 14 days and see what multi-state payroll looks like when it's built right.