What is global payroll compliance?

It is the discipline of paying people in multiple countries correctly, on time, and provably: the right gross-to-net calculation under local rules, the right employer contributions, tax withheld and remitted on the local deadline, statutory filings submitted, payslips issued in the required format, and records retained long enough to survive an audit. Paying the right net amount is the easy half; the filings and the evidence trail are what actually fail.

What are the most common global payroll compliance failures?

Five recur everywhere. Worker misclassification — long-term full-time contractors who are employees in substance. Permanent establishment risk created by a senior employee signing deals in a country where you have no entity. Late or wrong statutory filings, which usually carry per-day penalties. Wrong benefit-in-kind treatment for stipends, equity and allowances. And no single owner: payroll sits between finance and HR, so nobody reconciles it.

How do you run payroll across multiple countries?

Three models. Aggregator or global payroll platform: one contract, local partners underneath — fastest, weakest on edge cases. Employer of Record: the provider is the legal employer where you have no entity — right below roughly ten people per country. In-house with local providers per country: cheapest at scale, highest coordination cost. Most companies end up hybrid — EOR for the long tail, in-house for the two or three countries with real headcount.

What is permanent establishment risk?

If your employees in a country do more than support work — negotiating contracts, closing revenue, running a fixed place of business — the tax authority can decide you have a taxable presence there and assess corporate tax on attributed profit, plus penalties. It's a real risk with sales leaders and country managers, and it does not go away because you used an EOR. Sales roles in new markets deserve a tax opinion before the offer, not after.

How do you control payroll data privacy across countries?

Payroll is the most sensitive dataset most companies hold. Set one processing agreement per provider, define where data is stored and for how long, restrict access to named individuals rather than to teams, keep bank-detail changes on a verified out-of-band process, and log every export. Under GDPR you need a lawful basis and a retention schedule; several jurisdictions add local storage or works-council requirements.

What does a monthly payroll close look like?

A calendar, not a scramble. Lock inputs (new hires, leavers, variable pay, leave, one-off allowances) at a fixed cut-off. Run a preliminary calculation and reconcile against last month line by line — a variance report catches almost every error. Sign off with two named approvers. Fund and pay. Then file, remit and archive within the local deadline, and reconcile payroll to the general ledger the same week rather than at year end.

Do we need an EOR or our own entity in each country?

Under about five employees in a country, an EOR is faster and cheaper than registering an entity and standing up local compliance. Between five and ten, model both — the crossover depends on local employer contributions and accounting costs. Past ten, or wherever you're making a decade-long bet, your own entity usually wins on cost and gives you control over contracts, notice terms and benefit design.

How does Nepal fit into a global payroll model?

Nepal is a common addition for engineering and back-office capacity. The employer load is the Social Security Fund at 20% of basic salary (11% more withheld from the employee), income tax withheld monthly under progressive slabs, a one-month Dashain festival bonus that must be accrued, and Nepal Rastra Bank rules on how foreign-currency salary reaches the country. Most companies start on an EOR and open a Pvt. Ltd. once the team passes ten.

Multi-country operations

Global payroll compliance — the checklist, not the sales deck.

I've run people operations and payroll across Nepal, the Philippines, Australia and the United States. Multi-country payroll rarely fails on the maths — it fails on classification, on a missed filing deadline, and on nobody owning the close. This is the operating checklist I use, and the honest trade-offs between an aggregator, an Employer of Record, and running it in-house.

Review your payroll setup How I work →

Failure modes

Five ways multi-country payroll goes wrong.

Misclassification. Full-time people on contractor invoices because it was faster. The bill arrives as back contributions, leave, notice and penalties — usually at exit or diligence.
Permanent establishment. A country manager closing revenue where you have no entity can create a taxable presence. An EOR does not fix this.
Filing drift. The payment lands but the return is late. Most jurisdictions price this per day, and interest compounds quietly for years.
Benefit-in-kind blind spots. Stipends, insurance, relocation and equity each have local tax treatment. Getting these wrong understates cost and creates employee tax surprises.
No owner. Payroll sits between HR and finance, so the variance report nobody runs is the control nobody has.

The checklist

Five areas, sixteen controls.

Classification

Every worker mapped to employee, EOR employee, or genuine contractor — with a written reason
No contractor working full-time hours under your direction for more than three months
Contract language reviewed locally, not translated from the US template

Calculation

Gross-to-net logic documented per country, including the basic-versus-allowance split where it drives contributions
Employer contributions, bonuses and accruals (festival bonus, gratuity, leave) in the cost model — not just base pay
Benefit-in-kind treatment agreed for stipends, insurance and equity

Filing and remittance

One calendar with every local deadline, owner named per country
Withholding remitted on the local due date, evidence archived
Annual reconciliations and statutory year-end forms scheduled, not improvised

Controls

Fixed input cut-off, month-on-month variance report reviewed before payment
Two named approvers; no single person can change bank details and release funds
Payroll reconciled to the general ledger monthly

Data and risk

Processing agreement and retention schedule per provider
Access restricted to named individuals, exports logged
Permanent-establishment review before any revenue-facing hire in a new country

Operating models

Aggregator, EOR, or in-house.

Model	Best fit	What to watch
Global payroll aggregator	5–20 countries, small headcount each, one finance contract	Local partners vary in quality; edge cases (equity, leavers, disputes) surface late
Employer of Record	New country, under ~10 people, no entity, needs speed	Per-head fee forever; less control over contracts and notice; does not remove PE risk
In-house + local provider per country	Countries with real headcount and a long-term commitment	Highest coordination load; needs a named payroll owner, not a shared inbox

This is operating guidance, not tax or legal advice. Confirm country-specific positions with a licensed adviser in that jurisdiction.

Frequently asked

Global payroll — straight answers.

What is global payroll compliance?: It is the discipline of paying people in multiple countries correctly, on time, and provably: the right gross-to-net calculation under local rules, the right employer contributions, tax withheld and remitted on the local deadline, statutory filings submitted, payslips issued in the required format, and records retained long enough to survive an audit. Paying the right net amount is the easy half; the filings and the evidence trail are what actually fail.
What are the most common global payroll compliance failures?: Five recur everywhere. Worker misclassification — long-term full-time contractors who are employees in substance. Permanent establishment risk created by a senior employee signing deals in a country where you have no entity. Late or wrong statutory filings, which usually carry per-day penalties. Wrong benefit-in-kind treatment for stipends, equity and allowances. And no single owner: payroll sits between finance and HR, so nobody reconciles it.
How do you run payroll across multiple countries?: Three models. Aggregator or global payroll platform: one contract, local partners underneath — fastest, weakest on edge cases. Employer of Record: the provider is the legal employer where you have no entity — right below roughly ten people per country. In-house with local providers per country: cheapest at scale, highest coordination cost. Most companies end up hybrid — EOR for the long tail, in-house for the two or three countries with real headcount.
What is permanent establishment risk?: If your employees in a country do more than support work — negotiating contracts, closing revenue, running a fixed place of business — the tax authority can decide you have a taxable presence there and assess corporate tax on attributed profit, plus penalties. It's a real risk with sales leaders and country managers, and it does not go away because you used an EOR. Sales roles in new markets deserve a tax opinion before the offer, not after.
How do you control payroll data privacy across countries?: Payroll is the most sensitive dataset most companies hold. Set one processing agreement per provider, define where data is stored and for how long, restrict access to named individuals rather than to teams, keep bank-detail changes on a verified out-of-band process, and log every export. Under GDPR you need a lawful basis and a retention schedule; several jurisdictions add local storage or works-council requirements.
What does a monthly payroll close look like?: A calendar, not a scramble. Lock inputs (new hires, leavers, variable pay, leave, one-off allowances) at a fixed cut-off. Run a preliminary calculation and reconcile against last month line by line — a variance report catches almost every error. Sign off with two named approvers. Fund and pay. Then file, remit and archive within the local deadline, and reconcile payroll to the general ledger the same week rather than at year end.
Do we need an EOR or our own entity in each country?: Under about five employees in a country, an EOR is faster and cheaper than registering an entity and standing up local compliance. Between five and ten, model both — the crossover depends on local employer contributions and accounting costs. Past ten, or wherever you're making a decade-long bet, your own entity usually wins on cost and gives you control over contracts, notice terms and benefit design.
How does Nepal fit into a global payroll model?: Nepal is a common addition for engineering and back-office capacity. The employer load is the Social Security Fund at 20% of basic salary (11% more withheld from the employee), income tax withheld monthly under progressive slabs, a one-month Dashain festival bonus that must be accrued, and Nepal Rastra Bank rules on how foreign-currency salary reaches the country. Most companies start on an EOR and open a Pvt. Ltd. once the team passes ten.

Go deeper