Aggregator or In-Country Partner? How International Payroll Outsourcing Really Works
Most global payroll contracts run through subcontractors you never meet. Here's who is liable when a filing is late or a payslip is wrong, and which SLA clauses make that liability enforceable.
The question to settle before you sign: who fixes it, and who pays
Say you're comparing two proposals for payroll in six countries. One is a global platform with one login and one invoice. The other is a local bureau in your largest market. Both promise accuracy. The question that separates them is narrower: when a tax filing in Poland goes in late or a payslip in Mexico is wrong, who catches it, who corrects it, and who pays the penalty?
In most international payroll outsourcing arrangements, responsibility is split across three parties, and the contract usually gives the vendor less of it than buyers expect. Once you understand the delivery chain, you can read a proposal for what it commits to rather than what the sales deck implies.
Platform, in-country partner and your own team
A payroll aggregator sells you the top layer: the interface, the data model, consolidated reporting and often the funding and payment flows. In many countries it doesn't calculate pay itself. That work goes to an in-country payroll provider, a local bureau under subcontract that applies local tax tables, social security rules and filing formats, and often submits to the authorities.
Large aggregators typically run their own operations in a handful of core markets and use partners elsewhere. The mix differs by vendor and country and changes over time, so ask for it in writing for each country you need.
The third layer is you. Your team sends the inputs (hires, leavers, salary changes, bonuses, unpaid leave) before each country's cutoff, approves the pre-payroll register and funds on time. Much of what gets reported as a payroll error starts here.
Where payroll errors usually start
| Failure point | Typical cause | Usually owned by |
|---|---|---|
| Late or wrong input | Missed cutoff, bonus approved after the deadline, termination not reported | Your team |
| Calculation error | Outdated tax table, wrong social security ceiling, misclassified allowance | In-country partner |
| Handoff loss | Pay elements mapped badly between the platform and the local system | Aggregator |
| Late filing or remittance | Submission not made by the statutory deadline | Whoever the contract names as submitter |
| Funding delay | Your transfer arrives late, or the vendor's treasury cycle slips | You or the aggregator |
The handoff row deserves the most attention. Partners blame inputs and aggregators blame partners. If nobody is named for the handoff, you carry the error.
Aggregator or direct in-country provider: which model fits
If you operate in one or two countries with meaningful headcount in each (roughly 25 or more people), a direct in-country provider is usually the better fit. You deal with the people who do the calculation, escalation takes one step, and pricing is typically lower. The downside: every new country brings another contract, data format and set of reports to reconcile.
With four or more countries and small teams in most of them, an aggregator usually earns its markup. You get one data model, one approval workflow and consolidated cost reporting, which matters to a CFO closing the books across currencies. What you give up is proximity to the expert, since your ticket passes through the platform before it reaches the local bureau.
Many mid-sized companies end up with a hybrid: a direct provider in the largest market and an aggregator for the long tail. That only works if your HRIS feeds both cleanly.
Outsourced payroll liability: what the vendor will and won't carry
In most jurisdictions the statutory duty to withhold and remit stays with the employer, whoever runs the payroll. Outsourcing moves the work, not the legal obligation. Whether the rules are PAYE-style withholding in the UK, income tax and provident fund contributions in India, or wage tax in Germany, authorities generally pursue your entity for penalties and interest. Details differ by country, so confirm with local counsel.
So outsourced payroll liability is really about contractual recovery. You want the vendor to reimburse penalties, interest and correction costs caused by its own errors. Three points decide whether that promise has any value:
- The cap. Many standard contracts cap total liability at a few months to a year of fees. If penalty indemnity sits inside that cap, it may barely cover one bad filing in a high-penalty country.
- Flow-down. Check that the aggregator's contract with its partner contains matching obligations. If it doesn't, the aggregator may refuse to absorb a cost it can't recover.
- Prime contractor status. Confirm that the aggregator, not the partner, is contractually responsible to you for subcontracted work.
An employer of record is different. The EOR is the legal employer and carries the statutory obligation directly, although its contract will still push input-related costs back to you. Have employment and tax counsel in each relevant country review the liability terms before you sign.
What the payroll service level agreement must actually say
A payroll service level agreement that only promises "payroll processed on time" won't protect you. Insist on these clauses:
- Country-by-country responsibility matrix stating who calculates, who approves, who submits each filing and who remits each payment.
- Outcome metrics: net pay received by the pay date, and filings and remittances made by the statutory deadline. Measure outcomes, not internal processing steps.
- Input cutoff calendar per country, commonly several business days before pay date, so responsibility can be assigned when something goes wrong.
- Accuracy and correction terms: vendor-caused errors fixed with an off-cycle run within a set number of business days, at no charge.
- Penalty indemnity for vendor-caused fines and interest, either uncapped or under a separate, higher cap.
- Service credits large enough to matter, expressed as a percentage of the affected country's monthly fee per breach.
- Subcontractor disclosure, with advance notice before a partner changes.
- Data protection terms covering a sub-processor list and cross-border transfer mechanisms under laws such as GDPR, India's DPDP Act and Brazil's LGPD.
- Exit support: full data export, year-end filings for the transition year and a defined handover period.
What drives the price
| Model | Typical 2026 range (USD) | Setup |
|---|---|---|
| Payroll aggregator | $30–$120 per employee per month, per country | Often $1,000–$5,000 per country |
| Direct in-country provider | $10–$60 per employee per month | Often low, but monthly minimums are common |
| Employer of record (for comparison) | $400–$900+ per employee per month | Usually none |
These are typical 2026 market ranges. Pricing varies by contract and local market, so confirm with vendors. Within each range, the main cost drivers are country complexity (Brazil and India usually cost more than Ireland), off-cycle runs, year-end processing, FX and funding fees, and HRIS integration.
Here's a hypothetical: a 45-person company with 30 staff in the UK, 8 in the Philippines, 4 in Germany and 3 in Brazil. An aggregator at around $60 per employee per month across all four countries comes to about $2,700 a month. A hybrid could be a UK bureau at $20 per employee ($600) plus an aggregator for the other 15 people at around $75 ($1,125), about $1,725 in total. The hybrid costs less, but you run two systems and two SLAs.
Red flags, and a test to run this week
- The vendor won't name the in-country partner for a given country.
- SLA metrics measure internal processing, not pay received and filings accepted.
- Penalty indemnity sits inside a general liability cap of a few months' fees.
- There's no written cutoff calendar for each country.
- Vendor-caused corrections are billed as standard off-cycle runs.
Then run a test. Ask each finalist for two things covering your two largest countries: its responsibility matrix, and a written walk-through of how it would handle a late-filing penalty caused by its partner. Ask who pays, how quickly, and under which clause. A vendor that answers clearly within a week has thought about accountability. One that can't will probably be just as vague when a real penalty notice arrives.
Quick answers
If my payroll vendor makes a mistake, will the tax authority pursue the vendor or my company?
In most countries the authority pursues your company, because the employer keeps the statutory duty to withhold and remit. Your protection is contractual: an indemnity clause that makes the vendor reimburse penalties and interest caused by its error. An employer of record works differently because it is the legal employer.
How do I find out whether an aggregator uses a partner in a specific country?
Ask for a written list of the delivery model for each country, showing which run on the vendor's own operations and which run through partners, and attach it to the contract. Also require advance notice before any partner changes. A vendor that won't disclose this is asking you to accept risk you can't assess.
What service credit level is reasonable in a payroll SLA?
Credits are negotiable and vary by contract, usually set as a percentage of the affected country's monthly fee per breach, with higher credits for repeated failures. They don't replace penalty indemnity, which should cover the actual fines and interest caused by the vendor's error.
Written by the Expat Team Group editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.