Moving to a Multi-Country Payroll Provider: A 90-Day Migration Checklist
Most multi-country payroll migrations succeed or fail on the cutover date, well before anyone configures software. This week-by-week 90-day plan covers data mapping, year-to-date balances, filing authorizations and parallel runs.
Pick the cutover date before you sign anything
When you move several countries onto one multi-country payroll provider, the date of the first live payroll matters more to the project than the vendor you pick. If you cut over at the start of a country's tax year, the new provider starts there with clean balances. If you cut over mid-year, it inherits every year-to-date figure from the old provider and then has to produce year-end filings for pay it never processed. That's where most reconciliation problems come from.
The catch is that tax years don't line up. The UK's tax year starts on 6 April and India's financial year on 1 April. Australia's starts on 1 July and South Africa's on 1 March. Most of continental Europe runs on the calendar year, and so do Singapore, Brazil and Mexico. No single date is clean everywhere, so you have to decide which countries get the clean start.
| Cutover option | Clean start for | Mid-year migration for | Best when |
|---|---|---|---|
| 1 January payroll | Most of Europe, Singapore, Brazil, Mexico | UK, India, Australia, South Africa | Most of your headcount is in calendar-year countries |
| April payroll | UK, India | Calendar-year countries | UK or India is your largest or most complex payroll |
| Phased waves | Each wave timed to its own tax year | None, if planned well | Five or more countries, and enough internal capacity to run two providers for up to a year |
Our view: for companies with 50 to 500 employees across four to ten countries, phased waves usually justify the extra coordination. Every mid-year migration you avoid removes a full set of balance loads and a messy year-end. Start with the country where the old provider causes the most pain and time it to that country's tax year. Then move the calendar-year countries together in a 1 January wave. Count back 90 days from each go-live date to set your kickoff.
Weeks 1–2: Scope, contracts and your exit from the old provider
Start with an inventory for each country: headcount, pay frequency, pay elements, benefits, pension or provident schemes, unions or collective agreements, and every filing the current provider makes for you. That inventory becomes the scope schedule in the new contract. Anything left out of it will come back later as a change request, and you'll pay for it.
On price, typical 2026 market ranges for international payroll outsourcing are roughly $25–$80 per employee per month in established markets. Countries with complex statutory schemes or few local partners can run $60–$150. One-time implementation fees often fall between $1,000 and $5,000 per country. These ranges vary widely by contract, volume and region, so treat them as a sanity check and get written quotes. The biggest cost drivers are:
- how many pay elements you have
- how often you run off-cycle payrolls
- which year-end filings are included
- whether the vendor's own entity or an in-country partner does the processing
Settle three things in these two weeks:
- Read your current contract's exit terms. Check the notice period (60–90 days is common), the data export formats and any fees for historical reports. The notice period may set your timeline more than anything else.
- Request a full data extract now. Ask for at least two years of payslips, payroll journals, filings and employee master data, in machine-readable form.
- Make the new vendor list, country by country, which payrolls it processes in-house and which it subcontracts. That decides who fixes errors and how fast. If a vendor won't tell you, don't sign.
Weeks 3–5: Payroll data mapping and year-to-date balances
Data mapping translates every field and pay code in the old system into the new one. Don't let the vendor do it alone from a template. Build a mapping workbook for each country with these columns: old code, new code, taxable or not, subject to social security or not, pensionable or not, and where it's reported on year-end filings. If a code gets the wrong tax treatment, gross pay will look right and every deduction will be wrong.
For any country migrating mid-year, load year-to-date balances for each employee. That covers gross pay, taxable pay, tax withheld, employee and employer social contributions, and pension contributions. In the UK, the new provider keeps filing under your existing employer PAYE reference. It needs those balances for the cumulative tax calculation and for year-end reporting that covers the whole tax year. In India, the new provider files the remaining quarterly TDS returns, including the final-quarter return that carries full-year salary detail, and issues Form 16 for the whole financial year. So it needs every month the old provider ran.
A hypothetical example: a 60-person company moves its UK and India payroll in October. The UK has 25 employees on 14 pay codes. India has 35 employees on 22 salary components. At code level, that's more than 1,100 balances to load and tie back to the old provider's journals, before you count the statutory totals. Budget two to three days of finance time per country for this.
Weeks 4–8: Filing authorizations with tax and social security bodies
Changing provider usually doesn't change your employer registrations, because the legal employer stays the same. What changes is who is authorized to file for you. Every tax authority, social security body and pension scheme has to recognize the new agent, and some of those authorizations take weeks. Start them in week four at the latest.
- UK: authorize the new provider as your PAYE agent with HMRC, and update the data connection to your workplace pension provider.
- India: give the new provider access for TDS, Provident Fund, ESI and state professional tax filings, and agree how digital signature certificates will be held and used.
- Germany and much of the EU: confirm the provider can submit electronic tax and social insurance reports under your existing employer numbers.
- Latin America and Southeast Asia: check government portal credentials and digital certificates. Mexico, for example, requires payroll receipts to be issued as stamped electronic invoices, and Brazil's eSocial reporting runs on digital certificates. In some markets, these credentials are tied to a named local legal representative.
If you're adding a country and need a brand-new registration, expect anywhere from several weeks to a few months. That country probably won't make a 90-day cutover, so put it in a later wave. Ask the vendor for its recent registration times in each country. If the answer is "two weeks everywhere," assume the vendor hasn't done this in most of those countries. Rules and timelines change, so have a local tax adviser confirm your obligations in each jurisdiction.
Weeks 8–11: Parallel payroll runs and variance sign-off
In a parallel run, the new provider processes a real pay period from the same inputs as the old one, but nobody gets paid from its output. You then compare the two results line by line. Plan at least two parallel runs per country. Where there's overtime, commission or shift allowances, plan three.
Agree tolerance rules before the first run. The standard we'd use is zero variance on net pay and tax. On employer contributions, accept small differences only if they come from rounding and you've documented them. Every variance needs a root cause. It's almost always one of three things: a mapping error, a missing year-to-date balance, or an error by the old provider. Don't assume the old figure is the correct one. If the old provider got it wrong, ask an adviser whether you need a correction filing.
| Week | Activity | Exit criterion |
|---|---|---|
| 8–9 | Parallel run 1 | Every variance logged with a root cause |
| 10 | Fixes, then parallel run 2 | Zero unexplained variance on net pay and tax |
| 11 | Parallel run 3 if needed; go/no-go meeting | Finance, HR and the vendor sign off in writing |
If a country fails go/no-go, move it to the next wave. Pushing a country live with known variances costs more in corrections and employee trust than waiting a month.
Weeks 12–13: Go-live, hypercare and switching off the old provider
Before the first live payroll, send employees a short notice. Tell them payslips will look different, which portal to use and who to contact if something looks wrong. Keep the old provider under contract during the first live run so it can still answer questions about past periods.
- Reconcile the first live payroll to the bank file and the general ledger within 48 hours.
- Confirm that each authority accepted the first statutory filings. A submission receipt isn't enough.
- Keep a hypercare ticket log for 30 days, and write response-time commitments into the contract.
- Archive the old provider's records to meet each country's retention rules. These typically range from about three to ten years, depending on the country and the type of record.
Give the old provider final notice only after one of two things: the new provider has completed its first year-end in every migrated country, or you hold every record you'd need to complete that year-end yourself. Use one test: if you couldn't rebuild a year-end filing from the data you hold, keep the old provider on.
Frequently asked questions
Is 90 days realistic for a multi-country payroll migration?
Yes, for a wave of three to six countries where your employer registrations already exist and the vendor processes those countries in-house or through established partners. It gets tight if you're adding a new country, moving a heavily unionized workforce or running weekly payrolls. In those cases, plan for about 120 days or split the work into waves.
Can we switch payroll providers in the middle of a tax year?
Yes. The new provider then has to inherit accurate year-to-date balances and produce year-end filings for pay periods it didn't process. That's manageable if you load balances for each employee and check them during parallel runs. Where you can, time each country's switch to the start of its own tax year so the problem doesn't arise.
How many parallel payroll runs do we need?
Two per country is the practical minimum. Three is safer for payrolls with variable pay such as overtime, commission or allowances. Agree before the first run that there must be zero unexplained variance on net pay and tax before go-live. If a country still has variances after three runs, delay that country.
What does international payroll outsourcing typically cost?
Typical 2026 market ranges are roughly $25–$80 per employee per month in established markets and $60–$150 in complex or thinly served countries. Implementation often runs $1,000–$5,000 per country. Pricing varies by region, volume and contract. Off-cycle runs, year-end filings and extra pay elements are common add-ons, so get the full fee schedule from each vendor in writing.
Do we need new tax registrations when we change payroll provider?
Usually not. The employer entity stays the same, so its registrations carry over. The new provider needs agent or filing authorization with each tax authority, social security body and pension scheme. Those authorizations can take several weeks, so start them by week four, and have a local tax adviser confirm the specifics in each country.
What data should we get from our old provider before leaving?
Get employee master data, at least two years of payslips and payroll journals, all statutory filings and acknowledgments, year-to-date balances for each employee, and pension or benefit contribution histories. Ask for machine-readable formats, not just PDFs. Check your contract early for export fees and the notice period, because they often set your timeline.
Written by the Remote Desk Group editorial team. Prices, features and rules change often - confirm details with the vendor or a licensed professional before you decide.