An international payroll system is whatever machinery turns employment terms in several countries into correct net pay, filings and payslips in each of them. Under one label sit three different architectures: a single engine with country rule sets, an aggregation layer over in-country providers, and payroll run inside an employer of record's service where you have no entity. They differ in who calculates, who files and who is liable, and the differences matter more than the demo. This page sets out how each works and the questions that expose which one a vendor is actually selling.
What every architecture must produce per country
Whatever the system, each country demands the same outputs on its own terms: a gross-to-net calculation under local tax and social security rules, employer contributions costed on top, a compliant payslip, net pay in local currency, and statutory reporting into that country's own channel. Denmark illustrates how specific the channel is: employers report pay to the Danish Tax Agency through the eIndkomst income register, the agency's own system, on its own cadence. The UK expects PAYE to be operated even for employees working abroad in many cases, and the US expects employers to keep withholding on US citizens posted overseas. A payroll system's coverage claim for a country means little until you know whether it files into that country's actual interface or hands you a file to submit yourself.
Single engine, aggregator, or EOR-run
A single-engine system runs one codebase with maintained rule sets per country: cleanest data model, real-time consolidated reporting, but genuine depth in fewer countries, because every statutory change in every country must land in one product's release cycle. An aggregator contracts an in-country payroll provider per country and standardises the inputs, outputs and support in one wrapper: broad coverage and local expertise, with consistency only as good as the wrapper's data discipline. EOR-run payroll is different in kind: the EOR is the legal employer in the country, so it runs payroll as part of employment, and you never touch the mechanics. Most companies with more than a handful of countries end up combining models, engine or aggregator where they have entities, EOR where they do not.
Where systems fail in practice
The recurring failures are at handoffs, not in arithmetic. HR changes arrive after cut-off and are keyed manually into the country engine; a currency purchase misses a bank holiday and pay day slips; a filing is generated but never submitted because the platform's job ran and nobody checked the government portal's receipt. Cross-border movers add a quieter failure: which country's social security applies is set by treaty, and the US alone has totalization agreements with 28 countries, evidenced by certificates of coverage; a system defaults to deducting the usual country's contributions unless a human records the determination. The controls that work are unglamorous: per-country filing evidence captured every cycle, month-on-month variance review per person, and a named owner for each country calendar.
How to evaluate a vendor's claim
Ask four questions per country on your list. Who performs the gross-to-net: the vendor's engine, a partner, or the vendor's EOR entity? Into which government system does the statutory reporting go, and does the vendor submit or merely generate? Who is liable when a filing is late or wrong, in the contract's words? And what is the price per payslip per country at your headcount, including implementation, year-end and off-cycle runs? Then ask to see a real payslip and a real filing receipt from one of your countries. A vendor selling an aggregator will name partners; one selling an engine will name rule-set update cadence; one selling EOR will talk about employment. All three can be right answers; the mismatch to avoid is buying one while believing you bought another.
Questions people ask about international payroll systems
Is one international payroll system enough for every country?
Rarely at real depth. Single engines cover their strongest countries well; aggregators reach further through partners; EOR covers countries where you have no entity. Most multi-country employers run a deliberate mix and judge each country on who calculates, who files and who is liable.
Does an international payroll system file taxes for us?
Sometimes it files, sometimes it only generates the file. The difference is the whole compliance question, and it varies by country within one vendor. Confirm per country whether submissions go into the authority's system, such as Denmark's eIndkomst register, under the vendor's hand or yours.
What data does a payroll system need from HR?
Employment terms with effective dates: pay, role, location, hours, benefits elections, joiners and leavers, plus bank details and tax identifiers. The reliability of the feed matters more than its format; changes arriving after cut-off are the most common cause of wrong payslips.
How do payroll systems handle employees who move between countries?
They calculate whatever country they are told; the determination is human. Social security treaties, including the 28 US totalization agreements, decide which system a posted worker pays into, documented by a certificate of coverage that must be recorded in the payroll before the first cross-border run.