A Slack message from an engineer that reads “by the way, I moved to Colorado last month” is more expensive than most founders realize. By the time you read it, the company is already late on a state withholding registration, accruing potential unemployment insurance penalties, possibly out of compliance with a paid sick leave ordinance, and exposed to wage-payment rules nobody on the team has read.
The good news is that each piece of this is small. The bad news is that there are about ten pieces, they all activate at once, and they activate the moment the employee starts working in the new state — not when you find out.
This post is the checklist. Every new state your company has an employee in triggers the same cascade. Modern payroll providers handle most of the execution, but they can’t act on what you haven’t told them, and they don’t catch policy gaps. Founders need to know what the cascade is so they can drive it on time.
What “having an employee in a state” actually means
The legal trigger is simpler than founders expect. If an employee performs services for your company while physically located in a state — even one day a week, even from a coworking space, even from a parent’s spare bedroom in summer — the company has a presence in that state for employment purposes.
This is separate from sales tax nexus, separate from corporate income tax nexus, and separate from where the company is incorporated. Employment presence is its own analysis. The threshold is essentially zero days for income tax withholding (some states have a de minimis exception, most don’t), and zero days for unemployment insurance.
What this means operationally: every employee’s primary work location matters, and the moment it changes, the company has obligations in a new jurisdiction.
The registration cascade
When you hire your first employee in a new state, here is what activates. The order is roughly the order in which you need to handle them.
State income tax withholding registration. You register with the state’s revenue department, receive a withholding ID, and configure your payroll provider to withhold and remit state income tax from that employee’s pay. Required in 41 states (the 9 without state income tax: AK, FL, NV, NH, SD, TN, TX, WA, WY). Penalties for late registration vary by state but typically include interest on unpaid withholdings plus modest penalty fees.
State unemployment insurance (SUTA) registration. You register with the state’s unemployment insurance agency, receive an employer account number, get assigned an experience rate (or new-employer rate), and begin paying state unemployment tax on the employee’s wages up to that state’s wage base. Required in all 50 states plus DC and territories. SUTA rates vary wildly by state — Washington new-employer rate is around 1.0% on the first $72,800; California is around 3.4% on the first $7,000.
Workers’ compensation coverage. Most states require workers’ comp coverage from the first employee. Some states allow you to add the new state to your existing carrier’s policy; others require a state-specific policy. Coverage in monopolistic states (Ohio, Washington, Wyoming, North Dakota) must be purchased through the state fund directly. Workers’ comp is not optional and the penalty for going without it is substantial — including criminal liability in some states for willful violations.
State disability insurance (SDI) and paid family leave. Five states have mandatory state-administered disability insurance: California, Hawaii, New Jersey, New York, Rhode Island. Several more have mandatory paid family leave programs: California, Connecticut, Colorado, Delaware, Maryland, Massachusetts, Minnesota, New Jersey, New York, Oregon, Rhode Island, Washington, plus DC. These programs require employer registration, employee deductions, and quarterly filings.
Local tax registrations. Cities and counties with local income taxes: New York City, Yonkers, Philadelphia, Newark, certain Ohio cities, Pittsburgh, several Pennsylvania municipalities, Detroit, several Indiana counties, Kansas City, St. Louis, San Francisco (gross receipts), and others. The Pennsylvania Local Earned Income Tax system is its own special complexity — every Pennsylvania resident owes local EIT to their municipality of residence, which requires its own quarterly filing.
New hire reporting. Federal law (the PRWORA) requires every employer to report each new hire to the state’s new-hire registry within 20 days (sooner in some states). Used for child support enforcement primarily. Most payroll providers handle this automatically, but only if they know about the hire — which they will if you onboarded through the HRIS, and they won’t if the employee was somehow added outside the standard flow.
The minimum-wage, overtime, and wage-payment trap
Federal wage and hour law sets the floor. State and local law goes meaningfully above it in many places. The variables:
Minimum wage. Federal floor is $7.25/hour. As of 2026, state minimums range from $7.25 (several states) to $17+ (California, Washington, others). Many cities have local minimums higher than the state — San Francisco, Seattle, NYC, DC. The applicable minimum is the highest of federal, state, and local for the location where the employee actually works.
Overtime. Federal overtime is 1.5x for hours over 40 in a workweek. California requires 1.5x over 8 hours in a day, 2x over 12 hours in a day, and 1.5x for the first 8 hours of the seventh consecutive workday. Other states have their own variations. The overtime calculation must match the state in which the work was performed.
Exempt classification. The federal salary threshold for exempt status was $58,656 annually as of the most recent rule (subject to ongoing court challenges). Several states require higher thresholds — California is around $66,560 for exempt status (and that’s just the salary test; the duties test is separate and stricter). An employee who is exempt in Texas may not be exempt in California.
Pay frequency. Most states require at least semi-monthly pay; some require weekly for certain industries (NY for manual workers). Pay frequency violations are common when remote employees move between states.
Final paycheck timing. Federal law leaves this to states. California requires the final paycheck essentially immediately upon involuntary termination. Some states allow several days; others allow it to be paid at the next regular payroll. The penalty for missing the deadline can be substantial in some states — California’s “waiting time penalty” alone can reach up to a month’s wages in some circumstances.
The trap: each of these rules attaches to the location where the work is performed. A founder running payroll in their head (“biweekly, federal overtime, fine”) is creating exposure they don’t see the moment an employee moves.
Paid sick leave and parental leave by state
About 18 states and 20+ cities have mandated paid sick leave laws as of 2026. Hours accrue from day one or with some accrual cap; the rules differ in every state and city.
About 13 states plus DC have mandated paid family leave programs. Some are employer-funded, some are state-administered through payroll deductions, some are hybrid.
If your handbook says “we have unlimited PTO” and you have an employee in California, the unlimited PTO does not automatically satisfy California’s separate paid sick leave requirement. The structure has to be explicit — see building an employee handbook for the handbook implications.
What this means operationally: every state of employment changes the leave landscape. A 50-person company across 12 states has 12 separate sets of leave rules to track.
Non-compete and non-solicit enforceability
Several states have meaningfully restricted or banned non-compete agreements: California (banned), Oklahoma, North Dakota, Minnesota, and several others have substantial limits. Massachusetts allows non-competes with specific consideration and time limits. The FTC’s 2024 rulemaking attempted a federal ban; it’s been litigated and the status is in flux.
Practically: an employment agreement that includes a non-compete for an employee based in California is unenforceable as to that employee. An overly broad non-solicit may be unenforceable as well, depending on state law and how it’s drafted.
What this means for offer letters: standard templates don’t work across states. Either you have state-specific addenda for the restrictive covenant sections, or you accept that the covenants won’t be enforceable for some of your employees, or you ask employment counsel to draft state-aware versions.
What modern payroll providers handle (and don’t)
Rippling and Gusto handle the mechanical compliance well. Specifically, what they handle:
- State income tax withholding registration in most states (varies by provider and state)
- SUTA registration and quarterly filings
- State disability insurance and paid family leave deductions and filings (in the states they support)
- Most local tax registrations and filings (Rippling broader coverage; Gusto more limited)
- New hire reporting
- W-2s, 1099s, ACA reporting
What they don’t handle:
- Workers’ comp procurement (Rippling and Gusto have partner integrations but you contract the policy separately)
- Updating your handbook for state-specific leave policies
- Adjusting exempt/non-exempt classifications when an employee moves to a state with stricter rules
- Reviewing employment agreements for state-specific enforceability
- State-specific harassment training requirements
- State-specific posting requirements (the labor-law posters you’re required to display, which now extend to digital postings for remote employees in some states)
The split: providers handle taxes and filings; you (or your HR person) handle policy, classification, and the underlying employment relationship.
What we recommend operationally
The startups that handle multi-state employment well do five things consistently.
Treat every new state as a project. New state hire = a one-page checklist that runs every time. State withholding registration, SUTA, workers’ comp, SDI/PFL if applicable, local taxes if applicable, handbook addendum, employment agreement review, payroll provider state-add.
Require employees to notify HR before moving. This is a policy in the handbook. Employees who move without notifying HR create avoidable exposure. The expectation has to be clear and the workflow has to be easy (a single form, ideally in the HRIS).
Use Rippling or Gusto as the system of record. Integrated payroll stacks handle most of the mechanical work. Manual payroll across multiple states is where errors compound.
Update the handbook quarterly for state-law changes. California, New York, Illinois, Washington, Colorado, Massachusetts, and Oregon are the most active. A 5-state company can probably review semi-annually; a 12-state company needs quarterly cadence.
Have a relationship with employment counsel. You don’t need a full-time lawyer; you need someone you can call when an employee moves to a new state, when you have a termination question, or when a state law changes. Budget $5K-15K per year in legal spend for a multi-state company at Series A/B scale.
The cost of doing this well is modest — a few hours of HR time per new state, a handbook update cycle, and a counsel relationship. The cost of doing it badly is multiplied state filings, retroactive registrations, penalty interest, and the specific California waiting-time penalty that has gotten more than a few startups for $20K-50K on a single termination.
When to bring in operator support
You probably don’t need outside help if you have under 5 employees in 1-2 states with a clean Gusto or Rippling setup and a baseline handbook.
You likely want operator input if:
- You’re scaling past 25 employees across 5+ states and the compliance load is starting to slip
- You’re hiring your first employee in California, New York, or another high-complexity state and don’t have the handbook addenda in place
- You’re inheriting a multi-state payroll setup from a prior administrator and need to validate that nothing’s been missed
- You’re going through diligence for a Series B raise or M&A event where employment compliance is going to be scrutinized
- You’ve gotten a notice from a state agency (SUTA audit, withholding mismatch, paid leave claim) and don’t know how to respond
Pegacorn Group works with venture-backed Series A and B startups on building the HR and payroll infrastructure that makes multi-state employment a non-event. If you’re growing across state lines and want to make sure you’re not building exposure you can’t see, let’s talk.
This post pairs with: How to administer payroll and 401(k) plans at a startup, The Series A/B benefits stack, Building an employee handbook that actually protects you, and When to hire your first HR person.