Remote Work & Tax Nexus: Is Your PA Startup Unknowingly Violating Other States’ Laws?

What “Tax Nexus” Means For a Pennsylvania Business

Nexus is just a legal word for connection. When your business has enough connection to a state, that state can make you register, file, and pay there. For years, nexus meant physical presence. You needed an office, a warehouse, or a store. That standard is gone. A single remote employee can now be enough on its own. The real question in a PA business tax nexus review is easy to ask and harder to answer:

How One Remote Employee Creates Multistate Exposure

Picture a common setup. Your company is formed in Pennsylvania. Your office sits in the Philadelphia suburbs. You hire one full-time employee who lives and works in New Jersey.

That single hire can pull your company into New Jersey’s system. The employee’s presence, not a contract or a sale, is usually what does it. Once it happens, several separate obligations can switch on at the same time. Owners tend to assume payroll software handles all of it. It doesn’t.

Here’s what actually gets triggered, and why each one is its own question:

• Corporate income or franchise tax. The other state may treat you as “doing business” there and expect a return. In New Jersey, that’s the Corporation Business Tax.
• Payroll withholding and unemployment. You generally withhold the work state’s income tax and register for its unemployment insurance.
• Foreign qualification. Most states require an out-of-state company with employees there to register to do business, appoint a registered agent, and pay annual fees.
• Employment law. The other state’s wage, overtime, leave, and termination rules can apply to that worker, even if your handbook was built for Pennsylvania.

These are four different legal regimes, not one. An accountant may catch the filings. The harder calls, whether you owe anything and where, are legal questions first.

The Federal Protection That’s Narrower Than People Think

Before assuming the worst, there’s one federal rule worth knowing. It’s called Public Law 86-272. It can shield a company from another state’s net income tax, but only in a narrow case: when your sole activity in that state is soliciting orders for physical goods, with those orders approved and shipped from outside the state.

That protection is thin for remote teams. An employee who writes code, handles support, or manages accounts almost always falls outside it. P.L. 86-272 also covers net income tax only. It does nothing for franchise tax, gross receipts tax, payroll, or sales tax. So a single non-sales employee in another state usually clears the federal floor and lands you squarely in that state’s reach.

Why the New Jersey Example is Actually the Easy Case

New Jersey is a useful illustration for a reason most articles miss. On the personal income tax side, it’s the friendliest neighbor Pennsylvania has.

The two states share a reciprocal income tax agreement. A New Jersey resident working for your PA company pays New Jersey income tax, not Pennsylvania’s, and your withholding follows the employee’s home state. New Jersey confirmed as much when it adopted its convenience-of-the-employer rule in 2023. That rule expressly does not apply to Pennsylvania residents, precisely because of the reciprocity agreement.

Most state lines are messier. Pennsylvania runs its own convenience-of-the-employer doctrine for nonresidents. If a remote worker still touches Pennsylvania at all, the Commonwealth may count their out-of-state days as PA earnings when the remote work is for the employee’s convenience rather than your necessity. Pennsylvania’s reciprocity agreements cover only a short list of neighbors: Indiana, Maryland, New Jersey, Ohio, Virginia, and West Virginia. A remote hire in New York, North Carolina, or California brings none of that relief, and the analysis gets real.

The lesson isn’t that New Jersey is safe. It’s that the answer turns on the specific pair of states involved. A clean result in one direction tells you nothing about the next hire.

Common Scenarios That Create Multi-State Exposure

In practice, the same patterns show up again and again in multistate startup compliance. None of them feels like a legal event at the time. Each one can become one later.

Scenario A: The First Remote Hire. A startup hires its first out-of-state employee and assumes the payroll platform handles everything. It doesn’t. Payroll software withholds taxes, but it doesn’t decide whether you owe corporate tax, need to foreign-qualify, or have to follow a new state’s employment laws.

Scenario B: Employee Relocation. An existing employee moves to another state, often without formal approval, and the company never updates its posture. The obligations attach from the date of the move, not the date you find out.

Scenario C: Contractors Misclassified as Employees. A company engages a “contractor” in another state who functions like an employee. That creates both nexus and a classification problem at once, which is worse than where you started.

Scenario D: Founders Working Across State Lines. A founder splits time between Pennsylvania and a second home, building nexus in both places without meaning to.

What Does Not Automatically Create Nexus

Not every out-of-state connection is a trap. A few arrangements carry lower risk:

• A genuinely independent contractor, properly classified, is less likely to create nexus than an employee.
• Selling into another state, on its own, usually raises only economic nexus, which is mostly a sales tax question after South Dakota v. Wayfair (2018).
• Passive ownership interests generally don’t create operating nexus.

These are fact-specific calls, though, not safe assumptions. The contractor who looks independent on paper but takes daily direction is exactly the arrangement states reclassify.

A Hidden Risk: Backdated Liability

The existence of nexus isn’t usually the worst part. The timing is.

States can assess tax retroactively, add penalties and interest, and demand back filings. In many states, the clock on an unfiled return never really starts. There’s no statute of limitations protecting a return you never filed, so the lookback can stretch well beyond a year or two. A remote employee who’s been sitting in another state for three years can represent three years of quiet exposure that surfaces all at once.

States are also enforcing these rules harder than they once did. Tax tribunals have upheld aggressive remote-work sourcing positions, including a closely watched New York decision in 2025. The direction of travel is toward more enforcement, not less.

5 Practical Steps From a Corporate Attorney to Stay Compliant

If you’re running a Pennsylvania startup with remote workers, you need a system, not a one-time fix. Five steps cover most of the risk.

1. Map where your people are. Keep a current record of every employee, contractor, and founder by work location, and update it whenever someone moves.
2. Conduct a nexus analysis. For each state where someone sits, determine whether nexus is triggered and identify the registrations it requires.
3. Register where required. This can mean foreign qualification, a state tax account, and a payroll tax account.
4. Align payroll and HR systems. Confirm proper withholding, state-specific policies, and accurate worker classification.
5. Build an ongoing compliance calendar. Track annual filings, tax deadlines, and renewal dates so nothing lapses.

The goal is simple. You want to find your exposure before a state agency finds it for you.

Where a Business Lawyer Fits In

There’s a clean division of labor here. Accountants handle the filings. A business lawyer figures out whether you should be filing at all, and where.

A startup lawyer helps you:

• Determine where nexus actually exists, which is a legal threshold question rather than a bookkeeping task.
• Coordinate your entity registration strategy across states.
• Align contracts and employment terms with each state’s law.
• Manage exposure before it hardens into liability.

If you’re looking at two or three years of unregistered activity, that’s the moment to get counsel involved early. Voluntary cleanup almost always beats a state-initiated assessment.

Questions About PA Business Tax Nexus? Speak To a Corporate Attorney

Remote work has quietly turned many Pennsylvania startups into multi-state businesses. If you have out-of-state employees, remote founders, or distributed operations, you likely need to evaluate your PA business tax nexus exposure.

If you’re not sure whether your company has crossed a line in another state, it’s worth analyzing now, while you still control the timing. Reach out to our business team and we’ll help you map your exposure and close the gaps before they turn into liability.