How Global Payroll Works

It’s the second week of June. Your company has just signed three new hires in three new countries (a senior engineer in Portugal, a product designer in Mexico, and an account executive in Singapore) with start dates stacked into the first week of July.

Your existing payroll covers the UK, the US, and Germany. You now have three weeks to register or onboard providers in three new jurisdictions, capture local tax IDs, set up local-currency funding, and get the first run out the door without missing a statutory deadline.

The finance director wants a single consolidated journal entry by 5 July. The CEO wants to know “how much it costs per head.” Nobody on the team has paid anyone in Portugal before.

That is what global payroll actually feels like in practice. It is not a software category. It is a recurring operational rhythm (register, calculate, fund, file, pay, reconcile) repeated every month, in every country, against deadlines you do not control.

The point of this guide is to show you how that rhythm works mechanically, where it breaks, and what to do about it before you sign the next provider contract.

What global payroll actually covers: beyond just paying people

Global payroll is the end-to-end process of compensating employees in countries where your company has a legal obligation to do so. The “paying people” part, net wages hitting bank accounts on the agreed pay date, is roughly fifteen percent of the work.

The other eighty-five percent sits in registration, calculation, statutory filing, reconciliation, and audit trail.

For a finance or People Ops lead running multi-country payroll, the actual scope covers the following operational stages, every cycle, in every country:

• Employee data intake. New starters, leavers, salary changes, bonuses, expenses, equity events, and absences must be captured before the country cut-off. UK: 18th for a 28th pay date; Germany: 20th for end-of-month; Brazil: 5th for 5th-of-next-month.
• Gross-to-net calculation. Statutory income tax, social security contributions (employee and employer), pension contributions, union dues, garnishments, and benefits-in-kind all flow through this step. The calculation is country-specific and changes with every budget update or rate adjustment. Mexico’s IMSS contribution ceilings reset every February; the UK’s National Insurance thresholds change every April; France’s URSSAF rates can change mid-year.
• Funding. Wire gross payroll plus employer contributions in local currency. Funding cut-offs sit one to three banking days before pay date, in local time.
• Statutory filing and remittance. Tax withholdings and social contributions get filed with the relevant authority (HMRC in the UK, IRS and state authorities in the US, URSSAF in France, INPS in Italy, IMSS in Mexico) on a country-specific schedule: monthly, quarterly, or annually depending on jurisdiction and headcount band.
• Reconciliation and journal posting. Each country’s payroll output feeds into the accounting system as a journal entry, mapped to cost centres with FX rates locked at a defined date.
• Year-end reporting. P60/P11D (UK), W-2/1099 (US), Lohnsteuerbescheinigung (Germany), STP finalisation (Australia), eSocial (Brazil), each on its own deadline and format.

If any of those six stages fails (a missed cut-off, a wrong tax code, a late filing, a misposted journal) the cost lands on the company in penalties, employee complaints, or audit findings.

The payoff for getting it right is a payroll function that runs as background infrastructure rather than a monthly emergency.

The four global payroll delivery models (and how they differ operationally)

Model 1: In-country providers, managed in-house

The company contracts a separate local payroll provider in each country (ADP in France, DATEV in Germany, Gusto in the US, MHR in the UK, Wagestream’s local partners, etc.) and runs them in parallel. The internal payroll team consolidates outputs.

Operational reality: this gives you the deepest local expertise per country, because each provider is a domestic specialist.

It also gives you the heaviest internal coordination load: the team is reconciling six to twelve different output formats, deadlines, and contact points every month. Realistic threshold: viable up to roughly four to six countries with one full-time payroll lead.

Above that, the coordination cost dominates.

Model 2: Aggregator (multi-country payroll platform)

A single platform (CloudPay, Papaya Global, Deel Global Payroll, Remote Payroll, Multiplier) sits in front of in-country processors, presenting one UI, one data model, one reporting pack. You trade local depth for consolidated reporting and one cut-off discipline. Implementation: 8–16 weeks per country.

Cost: $25–$80 per employee per month. Best fit: own entities in five-plus countries.

Model 3: Employer of Record (EOR)

The EOR is the legal employer. You pay a fully-loaded monthly invoice of $299–$699 per employee (gross salary, employer contributions, EOR fee). Zero entity setup, zero local filings, fastest hire-to-start (5–15 business days).

The trade: cost per head and reduced control over benefits and termination. Best fit: 1–4 hires in a country with no near-term entity plan.

Model 4: Own entity plus internal payroll

The company sets up its own legal entity in each country and runs payroll on internal HRIS-integrated software (Workday Payroll, SAP SuccessFactors, Oracle HCM with country-specific modules). This is the model used by enterprises with mature in-country headcount.

Operational reality: highest fixed cost (entity setup runs $5,000 to $25,000 per country, plus annual accounting and local director fees of $3,000 to $15,000), lowest variable cost per employee at scale, full control over benefits and equity.

Realistic threshold: cost-effective once headcount in a country exceeds roughly twenty to thirty employees and the country is strategic for the next three years.

The choice between these four is not “which is best”. It is which one fits your headcount band and roadmap in each specific country.

Most multi-country employers run a mixed estate: own entities in two or three core markets, EOR for emerging-market hires, and an aggregator on top of the entity-based countries.

How the payroll cycle works across multiple time zones and currencies

A multi-country payroll cycle is a chain of sequenced cut-offs, each anchored to a local pay date, each requiring funding in the right currency by a specific local-time deadline. A typical six-country month:

• Day 1–5: India and Brazil cut-offs (both pay on the 5th of next month); data needed by the 25th of the prior month.
• Day 10–12: US cut-off (semi-monthly, 15th pay date); data needed 3 banking days prior.
• Day 15: US semi-monthly run. Funding clears via ACH the prior business day.
• Day 18–20: UK, Germany, Singapore cut-offs.
• Day 23–25: Mexico cut-off (15th and 30th cycles). Funding for month-end runs must clear two banking days prior.
• Day 25–28: UK, Germany, Singapore pay dates. Gross funding in local currency must clear by the prior banking day.
• Day 28–30: Mexico month-end pay date. Reconciliation and journal posting for all month-end runs.

The friction point is that “cleared funding” means different things in different banking systems. ACH in the US settles next business day if originated before 2:45 PM ET. SEPA in the eurozone settles same-day for SEPA Instant or next business day for standard SEPA.

Domestic transfers in India settle within two hours via NEFT/RTGS during banking hours. Cross-border wires to Mexico via SWIFT can take one to three business days and incur correspondent bank fees of $15 to $50 per transfer.

If the company holds all its cash in USD or GBP and converts at the point of funding, the FX leg adds another one to two business days for settlement.

That means a UK pay date of 28 May requires the FX trade to settle by 27 May, which means the trade needs to be executed by 25 May, which means the funding decision needs to be made before the UK cut-off on the 18th.

Miss that sequence and either the run lands late or the company eats unfavourable spot rates on a same-day FX trade. The payoff for mapping this calendar early is that funding decisions stop being a monthly fire drill.

Tax and social contribution filing: what happens in each country

Filing is where most unseen work sits and most penalty exposure lives. Each country requires income tax withholding, social contributions, and statutory filings on different schedules:

• UK: RTI full payment submission to HMRC on or before each pay date. PAYE and employer NI remitted by the 22nd of the following month. P60 by 31 May; P11D by 6 July.
• US: Federal income tax (Form 941 quarterly), state income tax (varies by state: California monthly, Texas none, New York semi-weekly for larger employers), FICA (Social Security and Medicare) deposited semi-weekly or monthly depending on lookback period, FUTA quarterly. Annual W-2 to employees and IRS by 31 January.
• Germany: Lohnsteuer via ELSTER by the 10th of the following month. Social insurance due by the third-to-last banking day of the month. Lohnsteuerbescheinigung by 28 February.
• France: DSN filed monthly by the 5th or 15th of the following month (depends on company size), with URSSAF contributions. CSG and CRDS calculated in the same return.
• Mexico: IMSS contributions due by the 17th of the following month. ISR withholding remitted monthly via SAT.
• India: TDS deposited by the 7th of the following month. PF and ESI by the 15th. Quarterly TDS returns; Form 16 to employees by 15 June.

Late penalties scale quickly: UK PAYE from £100 escalating; German Lohnsteuer up to 10% of assessed tax capped at €25,000; US Form 941 up to 15% within 16 days. A six-country team manages 12–20 statutory deadlines per quarter. Treating filing as a tracked workflow rather than ad-hoc work drops audit risk to near zero.

What can go wrong: the failure modes that catch payroll teams out

Failure 1: Misclassified workers

A UK “contractor” who works set hours, uses company equipment, and reports to a manager is almost certainly a worker or employee under IR35. The same pattern repeats in Germany (Scheinselbstständigkeit), Spain (falso autónomo), and California (AB5). Remediation typically runs 12–36 months of back-contributions plus penalties.

Failure 2: Missed registration in a new country

Hiring in France without an entity or EOR arrangement has a 60-day clock; after that, URSSAF can deem a permanent establishment. Brazil: 90 days unregistered can trigger labour-court exposure. India has similar risk.

Failure 3: Wrong tax code applied

An employee relocating UK-to-Germany mid-year needs the correct tax code from the date of change. One month with the wrong code creates a reconciliation problem requiring coordination with two tax authorities and possible corrective filings.

Failure 4: Late funding causing missed pay

The most visible failure is a missed pay date. Every payroll team has had at least one: a wire that did not clear because of a public holiday in the receiving country, a funding instruction sent after the bank’s local cut-off, a SWIFT routing error.

The downstream cost is small in cash terms (often a £25 to £50 same-day wire fee) but enormous in trust: employees who have been paid late once become vigilant for life.

The pattern across all four: the failure is not technical, it is operational. The mitigation is process discipline: pre-flight checklists, dual-control on funding, a tracked compliance calendar, and a clear escalation path when the unusual happens.

The payoff is a payroll function that does not consume executive attention.

How to choose a global payroll model for your current headcount and complexity

The decision rule by headcount and capacity:

• 1–4 employees, no entity: EOR. Zero entity setup, zero local filings, 5–15 business day hire-to-start. Expect $299–$699 per employee per month.
• Five to twenty employees in a country, growth flat or modest: Decision point. EOR remains operationally simpler but cost per head starts to compete with entity setup amortised over three years. Run the maths: at twelve employees, EOR at $499 per head per month is $71,800 per year; entity setup at $15,000 plus $8,000 annual maintenance plus a local provider at $40 per employee per month is $28,760 per year, a $43,000 annual saving once the entity is operational. Time horizon matters: under two years, EOR usually wins on total cost.
• 20+ employees, 3-year+ horizon: Own entity plus local provider or aggregator. Fixed costs amortise; local payroll drops to $15–$50 per head.
• Five-plus countries with own entities: Add an aggregator on top. The aggregator does not replace local providers: it provides one consolidated reporting layer, one cut-off discipline, and one source of GL data. Expect $25 to $80 per employee per month for the aggregator layer on top of the local processing fee.
• Internal capacity below one full-time payroll lead: Default to EOR or aggregator with managed services. The hidden cost of provider sprawl is the time of the person consolidating it.

Revisit the model annually against actual headcount and forward plan, not when the current arrangement breaks. The closing rule: pick the model that matches your country headcount today, build the compliance calendar before signing the contract, and price the funding workflow into the operational cost. Get those three right and global payroll becomes infrastructure.

Frequently asked questions

How long does it take to onboard a new country onto an existing global payroll setup?

8–16 weeks for an aggregator or own-entity setup; 5–15 business days for an EOR hire. The longer timeline includes entity registration validation, GL mapping, data migration, and a parallel run.

What is the difference between a global payroll provider and an EOR?

A global payroll provider runs payroll for employees already employed by your local entity. An EOR is itself the legal employer, removing the entity requirement. EOR is operationally simpler and more expensive per head.

Can one platform handle every country we operate in?

Coverage claims of 100+ countries vary widely in depth. Tier-1 markets have mature processing; tier-2 and emerging markets often run on partner providers with reduced reporting. Validate specific country coverage and statutory reporting capability before signing.

What happens if we miss a statutory filing deadline?

Penalties scale from $100 to several thousand dollars per filing plus interest. Repeat lateness triggers audits, which cost far more than the penalties. Providers absorb penalties for their own fault; you pay if the lateness was caused by late data or late funding from your side.

How do we handle currency exposure on multi-country payroll?

Three options: hold operational balances in your top two or three pay currencies; use a specialist FX provider with sub-1% spread; or lock 30–90-day forward contracts on predictable salary obligations.

Should we centralise global payroll or let each country run its own?

Centralise the operational rhythm (cut-offs, funding, GL mapping, compliance calendar) but keep local expertise close to the work. The aggregator-plus-local-provider model is the most common middle ground for five-plus-country employers.