What Is Payroll Nexus, and Why Is Your Growing Business Probably Already Exposed?
Updated: Sep 29
Payroll nexus means your business created payroll tax obligations in a state because of employee activity there, with no office required. One remote hire, one relocation, one expanding sales team can trigger registrations, unemployment accounts, and filings you never knew existed. Here is a practical guide to what payroll nexus is and how to spot your exposure before the notices arrive.
There is rarely a dramatic moment where someone announces that a business now has payroll nexus. It happens quietly. A company hires a remote employee, a manager relocates, a salesperson starts working from another state, or a fast-growing business expands without updating its payroll infrastructure. Months later, notices arrive, agencies request registrations, unemployment filings turn up missing, and withholding accounts were never established.
For a lot of growing businesses, payroll nexus is one of the least understood operational risks tied to remote work and multi-state expansion, largely because most explanations of it are overly legal, overly technical, or disconnected from how businesses actually run. Operationally, it is far more practical than that.
What Is Payroll Nexus in Plain Terms?
At its core, payroll nexus means a business created payroll tax obligations in a state because of employee activity there. Having an employee working in a state can trigger requirements like state withholding registration, unemployment tax registration, payroll tax filings, labor department compliance, and in some places local payroll tax obligations.
The key idea is that a business does not need a physical office in a state to create payroll obligations there. In today's remote work environment, employee presence alone is often enough to create payroll nexus exposure, and that is where many growing companies run into operational trouble. It is worth separating from income tax nexus: payroll nexus specifically concerns the payroll tax obligations tied to where employees work, which can exist independently of a business's income tax footprint.
If you already know a specific state where an employee is working and you're not sure registration was ever completed, that is a specific, fixable gap.
How Does a Business Actually Create Payroll Nexus?
Almost no business sets out to create multi-state payroll complexity. It develops gradually through growth: hiring a remote employee in another state, letting an employee relocate permanently, expanding a sales or operations team regionally, converting a contractor to an employee, opening a satellite operation, or supporting hybrid and flexible work.
These changes usually happen faster than payroll compliance processes can adapt. The business is focused on hiring talent and supporting growth, while the payroll obligations that come with each new work location never get formally evaluated. That is why companies so often discover nexus only after a notice arrives, a provider transition begins, or a compliance review takes place. A single remote hire is one of the most common triggers, which our Remote Employee Compliance page covers in depth.
What each common trigger usually creates:
Trigger | What it usually creates |
Hiring a remote employee in a new state | Withholding registration, unemployment registration, payroll filing obligations |
An employee relocating permanently | The same requirements in the new state |
Expanding a sales or ops team regionally | Registration in each state the team actually works from |
Converting a contractor to an employee | Full payroll registration in that employee's state |
Opening a satellite operation | Registration, plus local or municipal obligations depending on the state |
Supporting hybrid or flexible work | Registration wherever the employee is actually performing the work |
Why Are Remote Employees Such a Common Payroll Nexus Trigger?
Remote work fundamentally changed payroll. Businesses that once operated from centralized offices now employ people across many states and time zones, which vastly enlarges the payroll compliance footprint. A company in one state that hires a remote employee in another may have no office, warehouse, or storefront there, yet that employee's presence can still create withholding obligations, unemployment tax requirements, payroll filing responsibilities, and labor-related compliance in the new state.
This surprises many employers, because they assume nexus only applies when they open a physical location. In practice, employee presence is frequently enough on its own. The mistake underneath it is treating a remote hire as a simple headcount addition rather than as potential entry into a new jurisdiction.
Does Payroll Processing Mean My Nexus Obligations Are Handled?
No, and this is the most important distinction to internalize. Payroll processing is not the same as payroll compliance. A payroll system can process wages, run direct deposits, and appear to withhold taxes correctly while the nexus-related obligations underneath, state registrations, unemployment accounts, payroll filings, and local obligations, remain unresolved.
The payroll looks healthy on the surface while compliance gaps build quietly behind it, which is exactly why businesses feel blindsided when notices finally arrive. Payroll platforms depend heavily on the employer to identify work locations and complete registrations; if those steps never happen, the software keeps processing while exposure accumulates. This is the same processing-versus-compliance gap our companion post on whether new payroll software fixes compliance problems examines from the software side.
A missing registration doesn't announce itself. It sits underneath payroll that looks completely normal, which is exactly why it's worth checking directly rather than assuming.
Why Do Growing Businesses Miss Payroll Nexus Until It Becomes a Problem?
Nexus problems usually begin with operational disconnects. Responsibility is split across HR, payroll administrators, finance, outside providers, and operations leadership. HR manages hiring, payroll processes checks, managers approve remote work, and no single owner evaluates state payroll exposure. As the business grows, those gaps get harder to manage, especially in startups, healthcare, staffing, transportation, consulting, and remote-first companies.
The common mistakes are all operational rather than technical: hiring remote employees before completing registrations, failing to update payroll when employees relocate, assuming the provider handles nexus analysis, registering for withholding but not unemployment, overlooking local payroll taxes, and not tracking employee work locations. Payroll keeps processing normally through all of it, and that delayed visibility is what makes nexus dangerous. By the time the problem surfaces, multiple quarters may already need cleanup, which is why treating nexus as ongoing operational infrastructure rather than a one-time registration task matters so much as you scale.
Frequently Asked Questions
What is payroll nexus?
Payroll nexus is the payroll tax obligation a business creates in a state because an employee works there. It can require state withholding registration, unemployment tax registration, and payroll filings, and it does not depend on having a physical office in the state. Employee presence alone is often enough to create it.
Can a remote employee create payroll nexus in another state?
Often yes. A remote employee working in a state where the business has no office can still create withholding, unemployment, and filing obligations there. The employee's work location is what matters, so a single remote hire can extend payroll nexus into a new state without any other physical presence.
Is payroll nexus the same as income tax nexus?
Not necessarily. Payroll nexus specifically concerns payroll tax obligations tied to where employees work, such as withholding and unemployment. A business can have payroll nexus in a state without the same income tax footprint, so the two should be evaluated separately rather than assumed to move together.
Does having payroll nexus mean I owe taxes in that state?
It means you likely have obligations there, which typically include registering for withholding and unemployment and filing payroll returns for the employee working in that state. Whether a balance is owed depends on the specifics, but the registration and filing responsibilities generally begin once an employee is working in the state.
What does it cost to register a state where I have payroll nexus?
Aureus charges a flat fee starting at $475 for a standard state, or $675 for a complex state with local or municipal income tax, with a lower rate for each additional state registered in the same order. Registrations submit within 5 business days under standard processing, with 48-hour rush processing available.
If you already know a specific state where an employee is working and you're not sure registration was ever completed, that is a specific, fixable gap.
