Do I have to pay payroll taxes in the state where my remote employee lives?

Yes. SUTA (state unemployment tax) and state income tax withholding are based on where the employee physically performs the work — not where your company is located. If you hire a remote employee in Ohio, you must register with the Ohio Department of Job and Family Services and withhold Ohio income tax, regardless of your company's location.

What is 'nexus' and why does it matter for remote employees?

Nexus means having a sufficient connection to a state to trigger tax obligations. Having a remote employee in a state typically creates nexus, which may require you to register for state income tax, collect and remit sales tax, and file state business tax returns. One remote employee can create compliance obligations across your entire business in that state.

Should I pay remote employees based on their local market or my company's market?

This is a key policy decision. Location-adjusted pay (based on employee's cost of living) reduces payroll costs for employees in lower-cost areas. Company-based pay treats everyone equally but may overpay employees in low-cost markets or lose talent in high-cost markets. Major tech companies use both approaches — there's no single right answer.

What is the cost difference between a remote employee in a high-tax vs. low-tax state?

The employer payroll tax difference alone can be $500-$2,500/year per employee between a low-obligation state (Florida: ~$200/year SUTA) and a high-obligation state (Washington: ~$1,500+ with PFML). But salary expectations in Seattle vs. Tampa also vary significantly — often $10,000-$30,000 for comparable roles — making location a major total compensation factor.

What happens if I don't register in a remote employee's state?

You'll owe back taxes, penalties, and interest when discovered (often during a state unemployment or income tax audit). States share employment data. Penalties typically run 5-25% of unpaid taxes plus interest. More seriously, your employee may have had the wrong amount withheld, creating problems for their personal tax return.

Remote Employee Costs: How Work Location Affects Your

Remote hiring feels like it should be simpler and cheaper than local hiring. Sometimes it is — but geography creates hidden costs through state tax registrations, multi-state compliance requirements, and salary market expectations that vary dramatically by location.

When the pandemic made remote work universal, many companies discovered that "hiring anywhere" comes with hidden complexity. Your remote employee in Denver creates Colorado tax obligations. The one in Seattle triggers Washington's paid family leave program. The one in New Jersey? You're now collecting and remitting New Jersey income tax.

Remote hiring isn't free. Here's what it actually costs — and how to manage it.

The Multi-State Compliance Cost

State Tax Registration

Each state where you have employees requires you to register as an employer. This typically means:

Registering with the state's unemployment agency (for SUTA)
Registering with the state's tax agency (for income tax withholding)
Potentially registering as a foreign entity doing business in that state (with your Secretary of State)

Registration itself is often free, but payroll services like Gusto or Rippling charge extra for multi-state payroll — typically $25-$50/month per additional state. ADP and Paychex quote separately for multi-state complexity.

Workers' Compensation by State

Workers' compensation is state-specific, and having an employee in a state creates a workers' comp obligation there. If your policy doesn't cover that state, you need either an endorsement on your existing policy or a separate policy. This typically costs $100-$500/year per additional state registration fee plus appropriate coverage.

Employer Tax Cost Comparison: Remote Employee in Different States

Assume you're hiring a remote software developer at $95,000 salary. Here's the employer payroll tax cost depending on where they live:

Employee State Employer FICA SUTA State Add-ons Total State+SUTA Florida$7,268$189$0$189 Texas$7,268$243$0$243 Arizona$7,268$160$0$160 California$7,268$238~$475 (SDI)$713 New York$7,268$503~$354 (DBL+PFL)$857 Washington$7,268$728~$831 (PFML employer share)$1,559 New Jersey$7,268$1,311~$423 (FLI+TDI)$1,734 Colorado$7,268$452~$855 (FAMLI employer share)$1,307

The employer payroll tax difference between your Florida hire and your New Jersey hire: $1,545/year — before accounting for salary differences.

The Bigger Factor: Salary Market Expectations by Location

Payroll tax differences are real but relatively small. The bigger cost driver is salary expectations — which vary significantly by location even for identical roles.

Location Median Software Engineer Salary Indexed to National Average San Francisco Bay Area$165,000-$200,000145-175% Seattle$140,000-$170,000125-150% New York City$135,000-$165,000120-145% Boston$125,000-$155,000110-135% Austin$110,000-$135,00095-120% Denver$105,000-$130,00095-115% Atlanta$95,000-$120,00085-105% Tampa$85,000-$110,00075-95% Indianapolis$80,000-$100,00070-90% Tulsa / OKC$70,000-$90,00060-80%

Hiring in Tulsa vs. San Francisco for the same role can mean a $70,000+ salary difference — dwarfing any payroll tax consideration.

Location-Based Pay Policies: The Three Approaches

Approach 1: Location-Adjusted Pay

Pay is adjusted based on the employee's geographic cost of living. Someone in San Francisco gets paid more than someone doing the same job in Kansas City. Reduces total labor costs for distributed teams but can feel unfair to employees who relocated to save money.

Companies using this approach: Meta, Google, Stripe, Shopify (historically)

Approach 2: Single-Rate Pay (Company Location)

Everyone doing the same job earns the same salary, regardless of location. Based on the company's headquarters market. This attracts talent in lower-cost markets (great deal for them) but may be uncompetitive in expensive markets.

Companies using this approach: GitLab (pays San Francisco market rates everywhere), Buffer

Approach 3: Zones-Based Pay

Salaries are set by geographic zones (e.g., Tier 1 cities: NYC, SF, Seattle; Tier 2: Austin, Denver, Chicago; Tier 3: everywhere else). Compromise between full location adjustment and single rate.

Companies using this approach: Spotify, Lyft, many mid-size tech companies

The Total Cost Model: San Francisco vs. Kansas City Remote Employee

A full-stack developer role:

Cost Item SF Bay Area Kansas City Base salary (market rate)$175,000$95,000 Employer FICA$13,256$7,268 SUTA (CA vs. MO)$238$237 State add-ons~$700$0 Health insurance (employer)$8,000-$14,000$7,000-$12,000 401k match (5%)$8,750$4,750 Total employer cost~$207,000~$115,000

Savings from Kansas City hire: ~$92,000/year. The location tax difference is less than 1% of that gap — the entire savings comes from salary market expectations.

Compliance Checklist for Remote Employees

When adding a remote employee in a new state, complete this checklist:

Register with the state unemployment agency (SUTA)
Register for state income tax withholding
Confirm your workers' comp policy covers that state or get an endorsement
Check for state-specific paid leave programs (CA, NY, WA, NJ, MA, OR, CO, CT, DE, MD)
Register as a foreign entity with the Secretary of State if required
Verify any state-specific employment laws (break requirements, overtime rules, final pay timing)
Update payroll software to calculate correct state withholding

Calculate Remote Employee Costs

Use our Employee Cost Calculator to compare employer costs across different states. Select any of the 51 jurisdictions to see FICA, SUTA, state disability, and paid leave costs side by side — so you can make location decisions with accurate cost data.

For state-by-state comparisons of employer costs, use our state comparison tools to evaluate two states head-to-head with the same salary inputs.

Remote Employee Costs: How Work Location Affects Your Bottom Line