Employee or Contractor Across Borders: The Status Questions That Change With Jurisdiction

A software designer in Toronto invoices a California company, joins a daily stand-up run from London, and spends three months each year working from Lisbon. The contract says “independent contractor.” That sentence is useful evidence, but it is not a universal passport. The same working relationship can be classified differently for wage rights, tax withholding, social contributions, benefits, dismissal protection, or immigration purposes—and a country may use more than one status test inside its own system.

The practical mistake is to ask, “Is this person a contractor?” as if there were one global answer. A better question is: for this legal issue, in this place, during this period, what status test applies to these facts?

Start by mapping the legal questions, not the labels

Before comparing countries, write down the consequences you actually need to decide. A payroll team may care about withholding and employer taxes. A worker may care about overtime, paid leave or dismissal rights. A procurement team may care about whether a supplier relationship is genuine. An immigration adviser may care about the right to work in a particular location. Those are related questions, but they are not interchangeable.

In the United States, for example, federal tax classification and federal wage-and-hour classification do not simply use one identical test. State statutes may add another test. In the United Kingdom, GOV.UK expressly warns that a person can have one status for tax purposes and another for employment-law rights. That alone is enough to reject the idea that the wording of a contract settles every issue.

Build a one-page “status map” with columns for the legal regime, location, relevant period, test, evidence and decision owner. If you cannot fill in the “test” column, you are not ready to give a status conclusion.

The United States: federal rules are only the first layer

At U.S. federal level, the Department of Labor’s FLSA analysis focuses on whether a worker is economically dependent on the employer or is in business for themself. The regulatory history is also moving: the Department issued a 2026 proposal to revise the independent-contractor analysis, while its official materials explain the relationship between the 2024 rule, current enforcement policy and private litigation. A company relying on a memo from two years ago should therefore confirm the current federal position before acting.

For federal tax, IRS Publication 15-A uses common-law concepts centered on behavioral control, financial control and the type of relationship. That tax analysis can produce a different practical inquiry from an FLSA wage claim. On top of both, states can impose tests that are more worker-protective or apply to different rights.

A useful U.S. review therefore asks three separate questions: What does federal wage law say? What does federal tax law say? What does the relevant state law say? The answer may also vary by the specific benefit or remedy being claimed.

The United Kingdom: employment rights and tax status may diverge

UK status work is a good illustration of why a global “contractor checklist” is dangerous. Government guidance distinguishes categories such as employee, worker and self-employed person for employment rights, while HMRC uses tax-status analysis and provides the CEST tool for tax questions. The facts that matter include control, personal service, substitution, financial risk and the reality of the relationship, but the legal question still matters.

Suppose a consultant has a limited company and invoices monthly. Those facts may be relevant, yet they do not answer whether an individual has worker rights in a particular dispute, and they do not automatically decide every tax question. The review should identify whether the task is payroll tax, employment rights, pension obligations, holiday pay, or another issue before treating a status result as portable.

Cross-border work adds a second problem: which place gets to ask the question?

Remote work often creates a false sense that the employer’s headquarters determine the law. In reality, the place where work is physically performed, the worker’s habitual work location, the employer’s entities, contractual choice-of-law clauses, local mandatory rules and the duration of the arrangement can all matter. Tax residency, permanent-establishment risk, immigration permission and social-security coordination may sit alongside worker-status questions.

This is where operational facts become decisive. A person who works from another country for five days while visiting family presents a different risk profile from someone who has permanently moved there and manages local customers. A six-week project is different from a two-year relationship that now looks like a permanent role.

Do not answer the classification question before answering the location question. At minimum, record where the person lives, where they actually perform work, where the contracting entity is established, who directs the work, and whether the location changed during the period under review.

Seven facts that travel better than legal labels

Legal tests differ, but a disciplined fact file remains useful across jurisdictions. Capture these seven areas without trying to convert them into a universal score:

Control in practice: who sets hours, location, methods, approvals and priorities?
Personal service: can the person genuinely send a substitute, and has that ever happened?
Economic independence: does the person market to other clients, negotiate price and bear meaningful business risk?
Integration: are they on organization charts, internal systems, recurring team routines or managerial chains?
Tools and investment: who provides equipment, software, insurance, workspace and specialist assets?
Duration and exclusivity: is the engagement project-based or effectively indefinite, and can the person serve competitors?
How the relationship changed: what was true at onboarding that is no longer true today?

These facts should be supported with contracts, invoices, work instructions, calendars, system-access records, approval chains and actual examples. A status review based only on a signed agreement is usually an evidence review with most of the evidence missing.

A scenario: one relationship, three different review files

Imagine a U.S. company hires a UK-based marketing specialist through a consultancy agreement. The specialist originally served four clients, but after eighteen months now spends 90% of working time on this company, attends fixed daily meetings, needs manager approval for leave, uses a company email address and manages two internal employees.

The company should not create one memo titled “Contractor status: yes.” It should create separate workstreams. The U.S. business may need to understand the implications for its own contracting and reporting. UK advisers may need to review employment-rights and tax questions under local rules. If the specialist begins working for long periods from Spain, a third jurisdiction may enter the picture. The facts are shared; the legal conclusions are not automatically shared.

The turning point in this scenario is not the original contract. It is the drift in how the work is actually organized.

What to ask local counsel or payroll specialists

A good local instruction is concrete. Instead of “Is our contractor okay?”, provide the fact file and ask:

Which status tests apply to the specific rights and taxes we are reviewing?
Which date or period matters if the relationship changed over time?
Does a contractual choice-of-law clause change any mandatory local rights?
Are there registration, payroll, social-contribution or reporting steps if status changes?
Are there limitation periods or correction windows already running?
Could a prospective reclassification affect arguments about the historical period?
Which facts are outcome-determinative, and which are merely supportive?

That produces advice that operations can actually use.

The decision rule: classify the question before you classify the person

The safest cross-border workflow is simple to state and easy to ignore: identify the legal issue, identify the relevant jurisdiction, freeze the facts for the relevant period, then apply the current local test. Repeat that process for each separate legal regime rather than copying one answer across payroll, tax and employment rights.

This article provides general information, not legal, tax or immigration advice. Worker status is highly fact- and jurisdiction-specific, and rules can change. Before changing classification, withholding, payroll, benefits or termination arrangements, confirm the current position with qualified professionals in the places that actually matter to the relationship.

A review cadence for relationships that move between countries

Cross-border status work is easier when review is tied to events rather than left for a crisis. At onboarding, record the intended project, expected duration, working countries, customer mix, reporting line, ability to substitute, equipment and pricing model. Then set automatic review triggers: a move to another country, a material extension, a new management responsibility, a shift toward one-client dependence, a change in legal entity, or a request for employee-type benefits.

For each trigger, save a short dated snapshot rather than rewriting history. A file might say: “At month six, the worker moved permanently from Ontario to Portugal; the client approved the move; daily supervision remained in London; no local payroll review has yet been completed.” That factual note is useful to tax, employment and immigration advisers because it separates what changed from what was always true.

This process also reduces the temptation to backdate documents. If the relationship no longer fits the original model, acknowledge the change and assess the consequences from the correct date. A clean chronology is usually more defensible than a late contract amendment that pretends the facts never moved.

A practical review should also distinguish a worker's physical location from the location of the hiring entity and the market served. Those facts can point to different compliance questions. A U.S. company hiring someone who lives and works in another country should not assume that a U.S. contract clause answers local payroll or employment-rights questions. Likewise, a short business trip should not automatically be treated like a permanent relocation. Record duration, habitual workplace, entity relationships and who directs the work before asking advisers for a conclusion. That narrower fact pattern makes the cross-border advice faster and more useful.