Table of Contents
Loading headings...
Your first international hire works because you can improvise: one contract, one payment method, maybe a local advisor on speed dial. But adding a second country changes things. “Good enough” processes start to break as you juggle multiple sets of employment, tax, payroll, and data rules at once.
This isn’t about getting everything perfect. It’s about understanding which assumptions stop working when you expand beyond a single country.
Understanding payroll from day one.
Read our Founder’s Guide to Getting Started.
What actually changes with country two
Going from one country to two isn’t additive; it’s parallel operations. Every time you make a decision (role, pay, benefits, termination terms, data access), you now have to confirm it works in two places.
Payroll becomes multi-track
A single global payday is rarely sustainable in the long term. Pay frequency, required payroll reporting, payslip content, holiday calendars, and withholding expectations can differ materially by country — and sometimes within a country, depending on worker type and local rules.
In practice, country two forces you to support:
Different pay cycles per country (and sometimes per worker type)
Local currency considerations and cross-border payment logistics
Country-specific withholding and reporting processes
Separate payroll calendars and cutoffs aligned to local requirements
The main operational shift: manual “one-off” payroll work starts to compound. Even if you keep tooling simple, you need a defined process for approvals, cutoff dates, and recordkeeping that can run in parallel without heroics.
Compliance stops being one checklist
Payroll compliance isn’t a single global standard. It’s a set of local obligations that can include tax treatment, social contributions, labor rules, and reporting practices, each with its own definitions and timing.
Country two is where teams often discover that their “standard” offer letter, onboarding flow, and offboarding expectations don’t translate cleanly.
Benefits expectations diverge
Benefits aren’t just a company culture choice. They’re often legally required. Minimum paid leave, sick pay, pension or retirement contributions, and mandated insurance can be legally required depending on the country and worker classification. What’s optional in one place may be non-negotiable in another.
UK examples (statutory requirements and commonly referenced baselines):
Employees are entitled to paid leave minimums, commonly cited as 28 days in many summaries of UK statutory leave.
Employers may have pension auto-enrollment obligations for eligible employees, with minimum contribution rules.
Statutory maternity leave is commonly summarized as up to 52 weeks, with structure defined by UK rules.
The key point isn’t memorizing every rule. It’s accepting that “standard benefits” are local and your baseline needs to adapt.
The three risks that escalate with multi-country hiring
1) Permanent establishment exposure
Permanent establishment (PE) is a tax concept that can create corporate tax presence in a country based on the nature of your activities there. It’s often overlooked in early global hiring — especially for remote-first teams — because it doesn’t always show up immediately in payroll tasks.
PE is fact-specific. Commonly discussed triggers include:
Fixed place of business (traditional office/branch concepts, with complications in remote work scenarios)
Dependent agents (people who effectively act on behalf of the company, including contract authority in some structures)
Certain in-country activities that tax authorities may view as establishing a meaningful presence
Why it matters: If a tax authority determines you created PE, exposure can include back taxes and related penalties, depending on the jurisdiction and facts.
How operators typically reduce risk:
Be deliberate about contract-signing authority and who can bind the company locally
Define roles carefully, particularly for revenue-facing responsibilities
Consider professional tax advice early when hiring into new jurisdictions
Review applicable double taxation treaty frameworks where relevant
Using an EOR can reduce some operational burden, but it does not automatically eliminate PE risk. The underlying facts of what your team does in-country still matter.
2) Worker misclassification
The contractor vs. employee line is not consistent globally. A relationship that looks “contractor-like” in one country may be treated as employment in another — based on control, exclusivity, duration, and how the work is integrated into your business.
You can incur large penalties in certain jurisdictions, but these outcomes are highly dependent on the country and enforcement posture.
Operator approach that tends to hold up better:
Research the local classification tests before hiring in a new country
Use written agreements that match the reality of the relationship
Avoid contractor setups that mirror employment (set hours, single-client dependence, managerial control over day-to-day methods)
Revisit long-running contractor relationships as scope and duration expand
3) Data protection across borders
Once you run payroll and manage employees in multiple countries, you’re handling regulated data flows: IDs, bank details, compensation, tax records, and employment files. Rules vary by jurisdiction, and the EU’s GDPR is a common reference point for companies processing employee data tied to the EU.
Common friction points include:
What data you’re allowed to collect and retain
Where it must be stored
Conditions for cross-border transfer
Access controls (who can see what, and from where)
Country two is often when teams need to formalize permissions, retention, and a clear internal system of record.
How hiring structures change when you hire in country two
Most founders end up choosing among three structures. The right choice depends on speed, headcount trajectory, and how much local complexity you can carry internally.
Option 1: Independent contractors
When it works: Short-term, clearly defined project work with genuinely independent workers.
Where teams get hurt: Long-term, full-time engagements that function like employment. Hiring contractors doesn’t automatically remove tax or legal risk, especially if the working relationship looks like employment under local rules.
Option 2: Employer of Record (EOR)
An EOR can employ workers on your behalf in countries where you don’t have a local entity, typically handling locally compliant contracts, payroll, withholding, and statutory benefits administration.
What an EOR typically handles:
Local employment contracts and onboarding documentation
Payroll processing and tax withholding
Statutory benefits administration and related filings
Employment recordkeeping aligned to local requirements
What stays with you:
Day-to-day management: scope, performance, team operations
Important nuance on liability: EORs can carry significant compliance responsibility as the legal employer in-country, but risk and liability are not automatically “off your plate.” Enforcement exposure and contractual allocation can be fact-dependent, and you still need clear internal controls around what your team is doing locally.
Option 3: Establish a local entity
Creating a local subsidiary or branch is the traditional route. It can provide control and long-term clarity, but it’s slower and typically requires ongoing local administration (payroll, HR, tax, filings).
Country-specific complications you’re likely to encounter
These aren’t comprehensive legal summaries. They’re the kinds of operational surprises that show up when you go from one international hire to two in separate countries.
Canada
Employment and payroll requirements can vary by province, and Quebec can introduce language requirements for certain employment communications.
Australia
Australia can involve layered obligations (including superannuation) and award or classification frameworks that differ by role type and industry. Some states have labor hire licensing regimes that may affect providers depending on the structure and services offered.
India
State-by-state differences can affect practical compliance requirements and payroll components, adding complexity beyond a single national checklist.
United Kingdom
UK hiring often requires adapting to statutory benefits expectations and local payroll norms.
Benefits expectations and administration can also differ across the UK’s nations, which can affect how “one UK policy” lands in practice.
A practical decision framework
Consider contractors (with caution) when:
The work is genuinely project-based and time-bound
The worker controls how and when the work is done
The worker serves multiple clients (or can, in practice)
You’ve checked the local classification standards for that country
Consider an EOR when:
You need to hire in a new country without building local infrastructure first
You want local payroll, withholding, and statutory benefits handled through an established employment wrapper
You’re still learning the local operating environment and want fewer moving parts upfront
Consider establishing an entity when:
You’re committed to a market and expect meaningful headcount over time
You need deeper control over local operations and employment relationships
You’re ready to carry the ongoing administrative burden of local compliance
“Required” vs. “recommended” vs. “common but risky”
When hiring across borders, very few practices are universally required in every country and every worker arrangement. The safer operator move is to separate the always-true disciplines from jurisdiction-dependent requirements.
Practice | Practical status | Why it matters |
Research local labor and payroll rules before hiring | Baseline discipline | Country rules vary; you can’t safely assume your home norms apply. |
Use locally appropriate written contracts | Baseline discipline | Many jurisdictions expect specific terms; templates need local adaptation. |
Classify workers based on local tests | Baseline discipline | Misclassification risk is fact- and country-dependent, but consistently expensive to unwind. |
Confirm pay method, currency, and payslip requirements locally | Jurisdiction-dependent | Some places require local currency and specific payslip formats; others allow more flexibility. |
Provide statutory benefits where applicable | Jurisdiction- dependent | Benefit minimums vary by country and worker type. |
Talk to a tax advisor early when adding countries | Recommended | PE risk assessment and tax posture are fact-specific. |
Run periodic classification reviews | Recommended | Relationships evolve; what was “contractor” in month 2 may not be in month 18. |
Paying contractors like employees (set hours, single-client dependence) | Common but risky | Increases the likelihood that the relationship is treated as employment. |
Assuming US-style at-will employment norms apply globally | Common but risky | Many jurisdictions have tighter termination rules and required processes. |
Using a single global contract template everywhere | Common but risky | Often misses mandatory local terms and can create enforcement problems. |
What founders typically do next
The second country forces an infrastructure decision. Teams that handle it well usually do five things:
Audit the current setup - Especially contractor relationships and who can sign what
Map local obligations - What changes by country for payroll timing, payslips, benefits, and reporting
Choose a hiring model per country - Contractor, EOR, or entity, based on your operating reality
Standardize payroll operations - Define cutoffs, approvals, and a system of record
Build a compliance calendar - Filing deadlines, renewals, and recurring local tasks
The goal isn’t complexity. It’s repeatability.
If you’re an international founder building a U.S. company, multi-country complexity often shows up in hiring outside the U.S. while also paying yourself, opening bank accounts, and keeping accounting clean inside the U.S. entity.
If your first international hire was a workaround, your second country is where you decide what the company’s operating model actually is. Get the structure right, document what changes by jurisdiction, and keep ownership of the risk even when you outsource execution.
For a tighter, founder-oriented walkthrough of payroll decisions and setup, especially for international founders running U.S.-based companies, download the Plane founder’s guide.
Legal disclaimer: The information provided is for informational purposes only and should not be considered legal advice.
Want product news & updates?
Sign up for our newsletter.
