How to run payroll in multiple countries

Most teams do not plan multi-country payroll. It arrives one hire at a time — a contractor in Poland, then an employee in Brazil, then someone in Canada — until finance is running four processes with four deadlines and no shared calendar. This guide is the operating playbook for turning that into one system, whether you run it in-house, through a global payroll provider, or through an employer of record. It does not assume you already have entities everywhere — most of this is written for the common case: some countries you own, some you do not, and both employees and contractors on the same team.

Last updated July 31, 2026. Jump to: Map your people · Entity vs. EOR, per country · One payroll calendar · FX and payment rails · Who owns the filings · Contractors vs. employees · Worked example · Failure modes · FAQ

Step 1: map where your people are, and how they are engaged

Before anything else, build one list. It sounds basic, and most teams skip it — which is exactly how payroll ends up fragmented. For every person you pay, capture four facts:

• Country of work. Not the country your company is headquartered in — the country the person actually sits in day to day. That is the country whose employment and tax law applies.
• Employment status. Employee or independent contractor. This is a legal classification, not a label you pick for convenience — get it wrong and you carry misclassification risk, covered below.
• Legal footing. Do you already have an entity there, or are you employing through an employer of record (EOR)?
• Pay currency and frequency. What currency they are paid in, and how often local law or your contract requires it.

One spreadsheet with these four columns, kept current, is the foundation the rest of this guide sits on. Payroll problems are rarely math errors — they are mapping errors: someone paid on the wrong cycle, in the wrong currency, under the wrong classification, because nobody wrote it down.

Step 2: decide entity vs. EOR, country by country

This decision is not global. It is local, and it can be different for every country on your map. A company can run its own entity in Canada, use an EOR in Brazil, and engage contractors in a third country — all at once, all correctly.

The question that decides it: do you already have a legal entity in that country?

• Yes, you have an entity. Run payroll on it — in-house, or through a global payroll provider if you want it consolidated with your other countries. This is usually the cheapest and fastest option once the entity exists.
• No entity, and no near-term plan to build one. Use an employer of record. The EOR is the legal employer, runs local payroll, and carries most of the statutory compliance, for a recurring per-employee fee.
• No entity, but a large permanent team justifies one. Open an entity, then move to the first option. This has real up-front cost and takes longer, so it rarely makes sense for the first hire in a country.

Our global payroll vs. EOR vs. entity guide walks this decision in more depth. The short version: most teams start every new country on an EOR, and only open an entity once headcount there earns the fixed cost.

Step 3: build one payroll calendar around every local cutoff

Every country runs its own payroll cutoff — the date by which hours, changes, and new hires must be submitted for that pay period to be processed on time. Miss a cutoff and the person is often not paid until the next cycle, sometimes a full month late.

Cutoffs also do not line up. Germany typically processes payroll monthly, with pay landing around the 25th. Brazil pays monthly by the 5th of the following month, or bi-monthly on the 5th and 20th. Canada runs monthly or semi-monthly, and the exact schedule shifts by province and employer. Three countries, three different calendars — and that is before you add a fourth.

The fix is one master calendar, not three separate ones. Put every country's cutoff, pay date, and any local reporting deadline on a single shared timeline. Whoever runs payroll — your team, an EOR, or a global payroll provider — should submit against that one calendar, not remember four different dates from memory.

Build in buffer time too. New-hire and change submissions should clear the local cutoff by several business days, not land on the deadline itself. A public holiday, a bank delay, or a document review can eat that margin fast.

Step 4: plan FX and payment rails before the first cross-border pay run

Paying someone in a different currency stacks two costs on top of the salary: the transfer itself, and the exchange rate on the conversion. The rate is usually the bigger cost, and it is often hidden inside the rate rather than shown as a fee. Traditional banks commonly mark up cross-border transfers by roughly 2%–5% against the mid-market rate; modern payment platforms typically bring that down to roughly 0.5%–1.5% (industry FX-cost commentary, checked July 2026 — see brief for sources). Across several countries every month, that spread is worth shopping, not assuming your default bank is competitive.

Three things to settle before your first multi-country pay run:

• Who absorbs the FX spread. Most employers pay the local-currency amount in full and absorb the conversion cost themselves, so pay does not fluctuate with the exchange rate.
• How money moves. A local bank account per country, a multi-currency payment platform, or a payroll/EOR provider that already handles the transfer inside its fee. Fewer moving parts, fewer failure points.
• How rate swings are handled. If pay is set in your home currency but delivered in local currency, decide upfront whether you lock the rate at run time or let it float, and tell people which.

This is one place an EOR or global payroll provider earns its fee: the transfer and conversion are usually built into what you pay them, instead of a separate problem per country.

Step 5: know who owns the statutory filings in each country

Payroll does not end when someone is paid. Behind every pay run sit statutory filings — tax withholding remittances, social security contributions, pension deposits — each with its own deadline and its own government agency. Miss one and the exposure is not just a late fee; in most countries it is interest, and it can be a compliance flag that follows the entity.

Who owns the filing depends entirely on the model you picked in step 2:

The practical rule: write down who is legally on the hook if a filing is late, not just who clicks submit. If the answer is unclear, close that gap first — before the compliance exposure closes it for you.

For a country-by-country look at what employers actually owe, our employer payroll taxes by country guide breaks down statutory employer contributions across the countries in our corpus.

Step 6: keep contractor invoicing and employee payroll in separate lanes

A multi-country team is rarely all employees or all contractors — it is usually both, and the two need different processes, not the same one stretched to cover both.

Employee payroll runs on a fixed schedule, with tax withholding, social contributions, and statutory benefits calculated automatically as part of the pay run. Contractor payments run on invoices: the contractor bills you, you pay the invoice, and there is no withholding or benefits accrual, because a contractor is not on your payroll.

Running both through the same system without separating them is how misclassification risk creeps in. If a "contractor" is paid on a fixed monthly schedule identical to your employees, given the same equipment, and managed the same way, several countries' labor authorities will look past the invoice and treat the relationship as employment — with back pay, back contributions, and penalties attached. Our pay international contractors guide covers the invoicing side in detail.

For contractors you engage regularly across borders, a contractor of record sits between a raw invoice relationship and full employment — it formalizes the engagement and keeps the paper trail clean, without turning the person into an employee they are not.

A worked example: 12 people across Germany, Brazil, and Canada

A 12-person team, spread three ways: 5 employees in Germany, 4 in Brazil, 3 in Canada. No legal entity anywhere yet. Here is how the six steps play out.

Map. Twelve rows, one spreadsheet: country, employment status (all employees here), legal footing (none yet), and pay currency (EUR, BRL, CAD).

Entity vs. EOR. With five or fewer people per country and no entity anywhere, an EOR is the practical starting point in all three — three entities are hard to justify at this headcount. Germany needs a specific flag: standard EOR is not recognized there, so the provider needs an AÜG employee-leasing licence to operate compliantly.

Calendar. Germany runs monthly, paid around the 25th. Brazil runs monthly by the 5th of the following month (or bi-monthly, 5th and 20th), plus a mandatory 13th-month salary split across two installments due by November 30 and December 20. Canada runs monthly or semi-monthly by province. All three go on one shared calendar, with data submitted several business days ahead of each cutoff.

FX. Salaries are set and paid in EUR, BRL, and CAD — three separate conversions every pay run if the company reports in USD. An EOR that already handles the transfer removes three FX relationships from finance's plate.

Filings. With EOR in all three countries, the EOR carries the statutory filings — German social insurance, Brazilian INSS and FGTS, Canadian CPP/EI — as the legal employer. The company's job is accurate hire data before each cutoff, and paying the EOR's invoice on time.

Contractors vs. employees. All 12 are employees here, so nobody is paid on an invoice. If the team later adds a contractor in a fourth country, that person runs through a separate invoicing process from day one, not the payroll built for the 12 employees.

Cost shape: statutory employer costs differ sharply by country before any provider fee. Germany runs roughly 21% of gross salary; Brazil roughly 35%–37%; Canada roughly 9%–12% depending on province (checked July 2026). A flat, published EOR fee like Remote&'s $400 per employee per month at least makes the platform side predictable across all three, so the only real variable left is each country's statutory rate.

Common failure modes

The same handful of mistakes account for most multi-country payroll problems. Most are avoidable once you know to look for them.

• No single calendar. Four countries run off four separate mental deadlines instead of one shared timeline — how cutoffs get missed and pay dates slip.
• Treating contractors like employees, or the reverse. A contractor paid on a fixed payroll-style schedule with no invoice trail creates misclassification exposure. An employee run through contractor invoicing skips statutory benefits they are legally owed.
• Absorbing FX cost nobody chose to absorb. Not deciding upfront who bears the exchange-rate spread means it lands wherever the default banking setup puts it — often eating into pay without anyone intending that.
• Assuming one country's answer fits all. Germany's AÜG licensing, Brazil's 13th-month salary, Canada's provincial variation — all real, all different, all invisible if "payroll" is treated as one generic process.
• Nobody named as the filing owner. Assuming "the provider handles it" without confirming, in writing, who is on the hook if a statutory filing is late.

When to run it yourself, and when to outsource

None of the six steps require outsourcing — a well-run in-house team can do all of them. But the case gets stronger as the country count grows: every new country adds its own cutoff, filings, and local rules, and that does not scale linearly with a small internal team. A rough guide: one or two countries with an existing entity, in-house is usually enough. Past three or four, especially mixing entity and no-entity countries, a global payroll provider or EOR that consolidates the load starts paying for itself.

Evaluating providers, look for four things: published, dated pricing, not a "contact sales" number you cannot budget; coverage in every country on your map, including quirks like Germany's AÜG requirement; a stated cutoff calendar per country; and clear ownership of statutory filings written into the contract, not said on a sales call. Our best global payroll providers guide compares options against this list.

Frequently asked questions

How do you run payroll in multiple countries?

Six steps, in order: map where every person works and how they are engaged; decide entity vs. employer of record per country; build one shared payroll calendar around every local cutoff; plan how money moves and converts between currencies; confirm who owns each statutory filing; and keep contractor invoicing separate from employee payroll. Most failures come from skipping the mapping step and running each country as a one-off.

What is global payroll outsourcing?

It means handing the operational work of running payroll across countries — calculating pay, filing statutory contributions, moving money in the right currency — to a third party, instead of building that in-house per country. It covers two setups: a global payroll provider running payroll on entities you already own, and an employer of record that also becomes the legal employer where you have none. Which one you need depends on whether you hold an entity there already.

Do I need a legal entity in every country I pay someone in?

No. You need one if you want to run payroll directly and be the legal employer yourself. Without one, an employer of record becomes the legal employer and runs local payroll, so you can employ someone without incorporating first. Most teams open entities only once headcount in that country justifies the fixed setup cost.

How do payroll cutoffs differ by country?

Every country sets its own submission deadline and pay date, and they rarely line up. Germany typically pays monthly around the 25th; Brazil pays monthly by the 5th of the following month or bi-monthly on the 5th and 20th, plus a mandatory 13th-month salary due by November 30 and December 20; Canada runs monthly or semi-monthly, varying by province. The fix is one shared calendar covering every cutoff, not tracking each one separately.

Who pays the FX cost when paying someone in another currency?

That is a choice, not a default. Most employers pay the full local-currency amount and absorb the exchange-rate spread themselves, so a bad conversion month does not shrink the employee's pay. Traditional banks commonly mark up cross-border transfers by roughly 2%–5% against the mid-market rate; payment platforms built for this typically run 0.5%–1.5% (industry commentary, checked July 2026). That spread is worth shopping, not assumed away.

How is paying contractors different from running employee payroll internationally?

Employee payroll runs on a fixed schedule with tax withholding and statutory contributions calculated automatically. Contractor payments run on invoices, with no withholding and no benefits accrual, because a contractor is not employed by you. Running both through the same process — especially paying a contractor on a fixed, payroll-style schedule — is a common misclassification risk. A contractor of record formalizes a recurring cross-border contractor relationship without converting it into employment.

What is international payroll outsourcing best suited for?

It fits best once a team runs payroll in three or more countries, or mixes entity-owned countries with employer-of-record countries — where a shared calendar, consolidated filings, and one FX relationship save real time over managing each country separately. A single country with an existing entity often does not need it at all.

Who is responsible if a statutory payroll filing is late?

It depends on the model. Running payroll on your own entity keeps legal responsibility with you, even if a provider processes the filing. Using an employer of record shifts the statutory filing obligation to the EOR as the legal employer — your job is accurate data before each cutoff and paying their invoice on time. Confirm this ownership in writing per country; do not assume it.