Cross-Border Remote Workers — The Tax Nexus Question in 2026

Remote hiring didn't invent the international-tax nexus problem, but it turned a corporate-tax-department issue into a small-business issue. A ten-person California SaaS company with one engineer in Lisbon, one contractor in Bengaluru, and a support lead who moved from Los Angeles to Austin now has three separate nexus questions to answer — and none of them are as simple as "we're a US company, we file a US return."

The mistakes we see most often aren't exotic. They're the ordinary ones — misclassifying the relationship, missing a state registration, or assuming a totalization agreement covers something it doesn't. Here's the mechanical picture for 2026.

Permanent establishment doesn't need an office

The classic image of permanent establishment (PE) is a warehouse or a branch office. Under most modern US tax treaties — which follow the OECD Model — a PE can be created by activity, not just by real estate. Two triggers matter for remote-hiring US companies:

• The dependent-agent rule. If a person habitually concludes contracts or plays the principal role leading to the conclusion of contracts on behalf of a US company from another country, that person's presence can create a PE for the US company in that country. This is not limited to a formal sales title. A country manager, a business-development lead, or an account executive with authority to bind the company can trigger it.
• The 183-day rule (for employees, not the company). Under most treaties, an employee's compensation is exempt from host-country income tax if the employee is present fewer than 183 days in a 12-month rolling period, the compensation is paid by (or on behalf of) a non-resident employer, and the compensation is not borne by a PE in the host country. Miss any of those three conditions and the host country generally has the right to tax.

The dependent-agent test is where most small-cap US companies get in trouble. A "US company with a remote sales lead in Germany" and a "German PE of a US company" are the same fact pattern in German tax terms if that sales lead has authority to close deals. The corporate income tax exposure that follows — German corporate tax on the profits attributable to that PE, plus filing obligations — is expensive to unwind after the fact.

What we're doing about it: for any US client hiring outside the US, we run a role-by-role PE assessment before the hire, not after. The right time to structure around dependent-agent risk is before the offer letter goes out.

Employee vs. contractor is a jurisdictional question, not a US question

The default US instinct is to hire a foreign worker as an independent contractor to avoid US payroll registration and worker-classification issues. That instinct solves the US problem and creates a host-country problem.

Most non-US jurisdictions treat classification substantively — the actual relationship controls, not the label on the invoice. Countries with active enforcement (Germany, France, the UK, the Netherlands, Brazil, and increasingly Portugal and Spain) will reclassify a "contractor" who works exclusively for one company, follows the company's direction, and uses the company's tools as an employee. Reclassification generally means:

• Retroactive employer social contributions
• Retroactive income tax withholding obligations
• Penalties and interest on both
• Sometimes local labor-law entitlements (severance, vacation accruals, notice periods)

The common alternative — an employer-of-record (EOR) — solves classification cleanly by placing the worker on the payroll of a local entity that provides the US company services. It also creates its own PE analysis, because the EOR's relationship with the US client and the worker's activities still need to be checked against the dependent-agent rule.

What we're doing about it: we treat classification as the second question after PE, not the first. The first question is whether the role itself creates PE risk. The second is how to structure the relationship — direct hire through a foreign subsidiary, EOR, or contractor — given that answer.

Totalization agreements cover Social Security, not income tax

Totalization agreements are frequently misunderstood as blanket bilateral tax treaties. They're not. The US has totalization agreements with roughly 30 countries — including the UK, Germany, France, Japan, Australia, Canada, and most of Western Europe — and each one addresses a narrow set of issues:

• Which country's Social Security system a worker contributes to
• How work credits transfer for retirement benefit purposes
• Elimination of double Social Security taxation for cross-border workers

They do not cover income tax, corporate tax, VAT, or GST. They also do not exist for large sending countries — India, Colombia, Nigeria, the Philippines, most of Southeast Asia — where much cross-border remote hiring actually happens. For a US company hiring a contractor in Bengaluru or an employee in Bogotá, there is no totalization coverage, which means potential exposure to both US self-employment tax (for a US-person contractor) and local social contributions (for either a US-person or local employee, depending on structure).

The workflow implication is that the totalization question is separate from the income-tax question. Certificate of Coverage (Form USA/[country]-1 in most templates) documents Social Security relief and needs to be issued through SSA before the assignment begins — not after.

W-8BEN vs. W-9 — the workflow that catches people

The document flow is straightforward in theory and error-prone in practice:

• W-9 — collected from any US person (citizen, resident alien, US entity) receiving reportable payments from a US payer. Drives 1099-NEC or 1099-MISC reporting.
• W-8BEN — collected from any non-US individual receiving US-source income to establish foreign status and claim treaty benefits where applicable. Drives 1042-S reporting for the payer.
• W-8BEN-E — the entity version of W-8BEN, collected from foreign entities.

Two common workflow failures:

• Assuming a foreign contractor doesn't need documentation. A payment to a non-US individual for services performed outside the US is generally not US-source income and not subject to US withholding. But the payer still needs a W-8BEN on file to substantiate that determination. Missing documentation flips the default treatment to 30% withholding under Chapter 3.
• Treating a US person abroad as a foreign contractor. A US citizen or green card holder living in Portugal is still a US person for tax purposes. They get a W-9, they get a 1099, and the payer treats them exactly as a domestic contractor for US reporting. The fact that they live abroad is a personal-tax question for them (foreign earned income exclusion under § 911, foreign tax credits) — not a payer-side workflow change.

What we're doing about it: every new non-US relationship gets a documentation review before the first payment goes out. Fixing 1042-S reporting after the fact — and unwinding under-withholding penalties — is materially more expensive than getting the W-8BEN collected up front.

Interstate remote workers create nexus too — and it happens faster than you think

The cross-border story has a domestic version. A US company with one remote employee in a state where the company has no other presence generally creates:

• Income tax nexus in that state, requiring apportioned corporate income tax filings
• Payroll tax registration for state unemployment insurance and income tax withholding
• Sales tax nexus in some states — economic nexus post-Wayfair has largely absorbed this question, but physical presence via a remote employee is still a separate trigger in states that maintain physical-presence rules
• Franchise or gross-receipts tax exposure in states with those regimes (California, Delaware, Texas, Washington, Oregon)

The pattern that keeps costing money is the informal move — an employee relocates to a new state and doesn't tell payroll, or tells payroll but doesn't loop in tax. Twelve months later the company discovers it owes back withholding, back franchise tax, and registration fees in a state it didn't know it was operating in. Voluntary disclosure programs are available in most states, but the negotiation posture is much better if the company comes forward before the state finds out.

What we're doing about it: every quarter we review the employee address list against the entity's registered states. Where there's a new state, we either register or restructure the role — either directly with the client, or with counsel where the exposure warrants it.

The framework that keeps this manageable

For a small-cap or mid-cap US business hiring across borders, the sequence that works is:

• PE risk assessment on the role before the hire.
• Classification and structure given the PE answer — direct hire, foreign subsidiary, EOR, or contractor.
• Documentation — W-9 or W-8BEN, Certificate of Coverage where a totalization agreement applies.
• State nexus check for interstate moves and remote hires — quarterly cadence.
• Home-country tax integration — foreign tax credits, § 911 exclusion for US-person employees abroad, treaty positions where they apply.

None of this is exotic. All of it is boring, complete, and easy to check when the workflow is built into hiring. It's expensive when it's built in after the audit letter arrives.

If your remote hiring has outpaced your tax workflow — or if you're seeing a state registration you don't remember initiating — that's a conversation worth having.

David Meyer, CPA, is a Partner at Laléa & Black and leads the firm's taxation and global trade practice for small-cap businesses, HNW founders, and cross-border filers. Laléa & Black is a Los Angeles CPA firm serving clients across taxation, business management, and investment tax strategy.