News, Tips & Resources

The withholding obligation travels with the employee

Your company’s payroll tax registration is tied to where your employees work, not where your HR team sits. The default rule under state income tax law is that withholding is owed to the state where the employee physically performs services. That principle is straightforward when everyone is in the same office. It becomes complicated the moment a developer moves to Colorado, a salesperson starts calling from Georgia, or a project manager spends three weeks at a client site in California.

The compliance exposure isn’t theoretical. Missed registrations, incorrect withholding, and unfiled returns can span multiple years before anyone catches them, and by then, remediation is far more complex and costly than getting it right the first time. The sections below lay out the framework every payroll team needs to manage withholding correctly for remote and traveling employees in 2026.

How payroll tax nexus is triggered

Nexus is the connection between your business and a state that gives that state the legal authority to impose tax obligations on you. For payroll purposes, the threshold is low: having even one remote worker in a state generally triggers full registration obligations. That means registering with the state’s department of revenue for income tax withholding and with the state workforce agency for State Unemployment Insurance (SUI, also called SUTA).

Nexus does not require intent. An employee who opens their laptop in a home office in a new state is creating a payroll compliance obligation for the employer, regardless of whether the employer has a physical office there, has marketed into the state, or even knows the employee has moved. 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.

The registration sequence is generally the same across states: file with the Department of Revenue (or equivalent) for an income tax withholding account, then register with the state’s unemployment agency for a SUTA account. Confirm the exact sequence and forms with each state’s agencies directly, since they vary.

The basic withholding analysis: work state, resident state, and the credit

When an employee lives and works in the same state, the analysis ends quickly. The complexity begins when those two states differ.

• Work state withholding: As a general rule, employers must withhold income tax for the state where the employee performs services. Almost all states require this of nonresidents earning wages within their borders.
• Resident state withholding: The employee’s home state typically taxes their worldwide income. When the employee has already had tax withheld by the work state, most states allow a credit for taxes paid to the other state, reducing or eliminating double taxation. The employer’s role is to withhold correctly for both—the credit is resolved on the employee’s return.
• No-income-tax states: Nine states impose no state income tax on wages: Alaska, Florida, Nevada, New Hampshire (on wages), South Dakota, Tennessee (on wages), Texas, Washington, and Wyoming. If either the work state or the resident state is on this list, the withholding picture simplifies accordingly.

Reciprocity agreements: when the default rule doesn’t apply

Reciprocity agreements are bilateral arrangements between neighboring states that override the work-state default. Under a reciprocity agreement, an employee who lives in one state and works in another pays income tax only in their state of residence. For the employer, that means withholding only to the employee’s home state—no nonresident registration required in the work state for that purpose.

The catch: reciprocity is not automatic. The employee must submit the correct exemption certificate (each state has its own form) to claim the benefit. Without that form on file, you’re expected to withhold for the work state. Note also that reciprocity applies only to wage income—it doesn’t extend to business income or other compensation types such as commissions attributed to specific states.

Roughly 15 states and the District of Columbia participate in some reciprocity arrangement, and each agreement is bilateral and specific. Indiana, for example, has reciprocity with Kentucky, Michigan, Ohio, Pennsylvania, and Wisconsin. There is no universal reciprocity list; verify each state pair with the relevant state agencies before adjusting withholding.

The convenience-of-employer rule: a different regime entirely

A subset of states takes an aggressive position on sourcing wage income: they assert that a nonresident employee who works remotely for an employer based in their state owes income tax to their state, even if the employee never physically works there—unless the remote arrangement exists for the employer’s necessity rather than the employee’s convenience.

For 2026, eight states enforce some version of this rule: New York, Pennsylvania, Delaware, Nebraska, Connecticut, New Jersey, Oregon, and Alabama. The specific mechanics differ by state:

• New York maintains the strictest interpretation. It presumes that all remote work is performed for the employee’s convenience unless the employer can prove otherwise. New York’s tax department actively audits out-of-state remote workers, and employer necessity claims require extensive documentation. A 2025 New York Tax Appeals Tribunal decision (Matter of Zelinsky) reaffirmed the rule’s constitutionality even for employees who physically worked entirely outside the state during a period of employer-mandated remote work.
• Connecticut and New Jersey apply a reciprocal version: their rules only activate for residents of states that impose a similar test themselves.
• Nebraska amended its rule in 2024 to require at least seven days of the employee’s physical presence in the state before the convenience rule applies at all. If a nonresident never works in Nebraska during the tax year, the rule won’t attach.
• Oregon applies a limited version affecting only nonresident managerial workers.

The practical risk for payroll teams: an employee who works remotely from, say, Virginia for a New York-based employer may have New York income tax withheld on the full year’s wages under the convenience rule—while also owing Virginia tax on the same income, depending on whether Virginia grants a full credit. That scenario warrants direct analysis by a qualified state and local tax advisor, not a reliance on general guidance alone.

If your organization has employees working remotely for an employer based in one of these states, document the business rationale for the remote arrangement. Most convenience-rule states provide an exception when the employer can demonstrate genuine business necessity—such as no available office space, a role that requires the employee to be in a specific location, or an employer-mandated remote policy. The burden of proof falls on the employer, and that documentation needs to exist before an audit, not during one.

Traveling employees and day-count thresholds

Remote employees who work from a fixed home office are one scenario; employees who travel regularly for work introduce a different layer of complexity. Some states do not require withholding until a nonresident employee has exceeded a threshold number of days worked or a minimum amount of wages earned within the state. Once that threshold is crossed, withholding is generally owed retroactively from the first day of services—which is why many employers choose to begin withholding from day one rather than try to track thresholds precisely.

States with day-count thresholds are inconsistent in how they define a “day,” what exceptions apply, and what counts toward the threshold (travel days, partial days, days performing exempt activities). The only reliable approach is to track where employees are working, to what extent, and to verify each state’s current rule with the relevant revenue department.

State unemployment insurance: one state per employee

Unlike income tax withholding, where you may owe obligations to multiple states for a single employee, SUTA is paid to only one state per employee. The U.S. Department of Labor’s Localization of Work Provisions provide a sequential four-test framework for determining which state that is:

1. The state where the work is localized (where the employee works entirely or mostly).
2. If not localized, the state where the employee’s base of operations is located.
3. If there is no base of operations, the state from which the employer directs or controls the work.
4. If none of the above resolves the question, the employee’s state of residence.

For a fully remote employee working exclusively from their home state, the answer is usually straightforward: SUTA goes to the home state. For employees who travel regularly across states, the analysis requires a fact-specific review. Work through the DOL’s four tests before making an assumption.

Keep in mind that SUTA wage bases vary significantly by state. In 2026, for example, the 2026 Social Security wage base is $184,500, but state SUTA wage bases are entirely separate figures set by each state independently, ranging from the federal FUTA minimum of $7,000 in states like California and Florida to over $70,000 in states like Washington. Confirm the current wage base with each relevant state’s unemployment agency. Also note that Alaska, New Jersey, and Pennsylvania require employee-side contributions to the unemployment fund—withholding logic in those three states must account for that deduction in addition to the employer obligation.

Registration and ongoing obligations when a new state is triggered

Once you’ve determined that a new state is in scope, don’t wait until the next payroll run to act. Register with the state’s Department of Revenue and unemployment agency before or alongside the employee’s first paycheck in that jurisdiction. Running payroll without the required accounts creates back-filing exposure that compounds over time.

The standard sequence:

1. Register for a state income tax withholding account with the Department of Revenue (or equivalent).
2. Register for a SUTA account with the state workforce agency.
3. Obtain the employee’s state-specific withholding certificate (the equivalent of Form W-4 for that state—most states have their own form).
4. Confirm the applicable deposit schedule and filing frequency for the new state.
5. Review the state’s employment law requirements: minimum wage, pay frequency, final-paycheck timing, and mandatory leave programs may differ materially from your home state.
6. Confirm workers’ compensation coverage extends to the new state; many states require a separate policy or endorsement.

For employees who move states mid-year, stop home-state withholding and start new-state withholding as of the employee’s move date—not the next quarter, not the next W-4 update cycle. The date of the move is the dividing line for apportioning the tax year between two states.

The data problem: you can’t comply with what you don’t know

Most multi-state payroll failures are operational rather than technical. The most common root cause is a missing or outdated work-location record rather than a calculation defect in the payroll system. An employee who relocates without notifying HR, starts working from a second home, or travels extensively without updating their work-address record will generate incorrect withholding in silence.

Practical controls that reduce this risk:

• Require employees to report work-location changes before they take effect, not retroactively.
• Build a mandatory work-location intake field into your onboarding process, capturing physical work address (not just mailing address) and expected travel pattern.
• Conduct a periodic audit of payroll records against HR and expense data to catch unreported moves. Employees who are submitting reimbursements from a state different from their payroll address are a flag worth investigating.
• Treat every employee relocation as a payroll compliance event with a defined checklist: residency confirmation, withholding update, new-state registration if applicable, and reciprocity check.

FAQ

Does a remote employee working in a state for just a few days a year trigger withholding?

It depends on the state. Some states impose withholding obligations from the first day of services performed within their borders. Others have de minimis day-count thresholds—often in the range of 14 to 30 days—before withholding is required. Even in states with a threshold, once you cross it, withholding is generally owed retroactively from day one of services. Because the rules are inconsistent across states and change periodically, the safest practice for employees who travel regularly for work is to begin tracking workdays in each state from the start and verify each state’s current threshold with that state’s revenue department. Many employers choose to start withholding from day one to avoid the complexity of retroactive corrections.

If my company is headquartered in New York but a new hire works remotely from Texas, do I owe New York withholding?

Potentially yes, under New York’s convenience-of-employer rule. If the employee is working remotely from Texas for their own convenience rather than out of employer necessity, New York may source the wages to New York and expect withholding accordingly. Because Texas has no state income tax, there is no competing state obligation from Texas—but the New York exposure remains. This specific scenario is one of the most common multi-state withholding disputes and warrants analysis by a state and local tax professional familiar with New York’s requirements. Documentation of any employer-necessity basis for the remote arrangement should be in place before the employee starts, not assembled after a notice arrives.

Where do I pay SUTA for an employee who lives in one state and regularly travels to several others?

SUTA is paid to only one state per employee. For a traveling employee, follow the Department of Labor’s Localization of Work Provisions in sequence: first, identify whether the work is predominantly localized in one state; if not, look to the employee’s base of operations; then the state from which direction and control originate; and finally the employee’s state of residence. For most employees who travel but have a fixed base, that base-of-operations state will be the answer. Confirm your determination with your state workforce agencies if the facts are ambiguous—an incorrect SUTA assignment can create both overpayment in one state and unpaid liability in another.

Can I use a PEO to avoid multi-state payroll registration obligations?

A professional employer organization (PEO) can handle multi-state payroll administration and typically maintains registrations in multiple states, which reduces the administrative burden significantly. However, using a PEO does not eliminate your organization’s underlying nexus exposure for state income tax and unemployment insurance purposes. States can still assert income and franchise tax obligations against the client employer, and state unemployment insurance liability generally follows the employment relationship, not just the payroll processing arrangement. Consult a qualified tax advisor before relying on a PEO relationship as a compliance backstop for nexus obligations.

Working with Optimus Payroll

Managing withholding across multiple state jurisdictions—each with its own registration requirements, deposit schedules, wage bases, and special rules—is a significant operational burden on top of running an accurate payroll cycle. Optimus Payroll provides multi-state payroll processing, compliance consulting, and managed-services engagements designed for employers who need this handled correctly without building out internal expertise for every state. Contact us to discuss your current footprint and where compliance gaps are most likely to exist.

This article is general informational content and does not constitute legal, tax, or accounting advice. Payroll and tax laws change frequently and vary significantly by state and locality. The rules summarized here reflect publicly available guidance as of July 2026 but may not reflect recent changes in any specific jurisdiction. Before taking any compliance action, confirm current requirements with the IRS, the U.S. Department of Labor, your relevant state revenue and unemployment agencies, or a qualified attorney, CPA, or payroll professional.