← All articles

one-workforce-many-payrolls-why-europes-multinationals-still-lack-a-single-source-of-truth

International organisations want one view of their people and their pay. Most end up with a patchwork of local payroll systems stitched together by APIs. Deloitte and EY have spent years documenting what that patchwork costs.

Consider a company of 800 employees headquartered in Amsterdam, with entities in Germany, Belgium, Poland, Spain and a sales office in Stockholm. HR sits centrally. Payroll does not. Each country runs its own provider, usually chosen at the moment of market entry by a local finance manager with a sensible preference for a vendor who knows the national rules. Five years later the group has one HR policy, five payroll calendars, five data models and no quick, reliable answer when the board asks for total employment cost by country. This is not a failure of competence. It is the logical outcome of growth in a region where employment law remains stubbornly national. Social security contributions, wage tax withholding, collective labour agreements, statutory leave and reporting to local authorities differ in every member state. Standardising HR is a policy decision. Standardising payroll is a compliance and engineering project, and most mid-market organisations never get past the first country.

What Deloitte sees

Deloitte's Global Payroll and Workforce Management Solutions practice has tracked this problem through its Global Payroll Benchmarking Survey, which gathered responses from more than 750 organisations in 55 countries. The findings describe fragmentation as a structural condition rather than an exception. Respondents used almost four third-party payroll technologies on average and many had resigned themselves to the idea that no single global vendor could support their full footprint. Europe stood out. Deloitte identified EMEA as one of the regions where vendor consolidation remains difficult, attributing this partly to country-specific regulation but mostly to the inability of payroll vendors to cover every country with one technology. The operational consequences are visible in the numbers. Respondents in EMEA, APAC and Latin America reported that more than 40 percent of their payroll effort went into manually entering or loading data, which Deloitte linked directly to a high number of vendors and a lack of standardisation. Productivity followed the same pattern: payroll teams in EMEA and Latin America supported roughly 320 employees per full-time payroll professional, against around 1,100 in APAC and North America. Data quality is the less visible cost. Deloitte found that 38 percent of off-cycle payments were caused by upstream processes, with missed or inaccurate HR updates alone accounting for a fifth of them. In other words, the error often originates not in payroll but in the handover between HR and payroll. When asked about their biggest service delivery challenge, 67 percent of respondents pointed to technology limitations. Deloitte also made a candid observation that deserves attention. An integrated HR and payroll system would remove the need to reconcile one system against another, the firm noted, but no single technology yet covers organisations with a large country footprint, particularly where headcount per country is small. That description fits the European mid-market almost exactly.

What EY sees

EY reaches a similar diagnosis from a different angle. Its Global Payroll Survey found that organisations used an average of five payroll providers, with a strong correlation between the number of countries and the number of providers. The more telling finding concerned what happens as that number rises: organisations with six or more providers were more than twice as likely to report difficulties with management and global reporting, and significantly more likely to name data as a key challenge. The relationship with providers is not much healthier. Only 42 percent of respondents described doing business with their payroll provider as easy. When EY launched its Integrated GlobalPayroll Solution in late 2024, Dan Hendy, the firm's Global Legal Transform and Operate Leader, described payroll, mobility and labour law services as typically highly siloed, and cited survey data showing that just 24 percent of organisations were satisfied with their current providers. A separate EY survey of 400 CHROs and heads of talent found that 92 percent see growing demand for international mobility straining these functions, while 87 percent say demand for flexible and hybrid work is increasing pressure on payroll. Both firms converge on the same point. Calculating pay correctly in any single country is a solved problem. The difficulty lies in the seams: between countries, between providers, and between HR and payroll. Their prescription for large enterprises is a centralising layer on top of the landscape, delivered as a managed service. For an organisation of 500 or 1,500 employees, that remedy is often heavier than the problem it solves, which is why most mid-market companies reach for a cheaper alternative.

The integration trap

The standard mid-market answer is to keep local payroll providers in place, implement an HR system on top, and connect the two through APIs. On a slide, the architecture looks clean. In practice it creates three problems that compound over time. The first is fragmentation that integration only disguises. An API connects systems, but it does not unify them. Every local payroll product has its own data model with its own definition of an employee, a contract, a cost center and a pay component. The integration layer translates between those models, and every translation loses nuance. The result is not one employee record but several versions of it, synchronised on a schedule and drifting apart between runs. The second is maintenance cost that rarely appears in the business case. Integrations are not built once. Providers release new API versions, rename fields, deprecate endpoints and change authentication methods. Legislation adds new data requirements that must flow through every connector. Each integration effectively becomes a small software product that needs an owner, monitoring and a test cycle, and the total effort scales with the number of countries multiplied by the number of changes each year. That cost tends to hide in IT budgets, implementation partner invoices and the overtime of payroll staff reconciling mismatches, which is consistent with the share of manual effort Deloitte still observes in fragmented European landscapes. The third is unreliable data. In a hub-and-spoke integration model, the local payroll systems do not communicate with one another, and the central HR system is only as current as its last successful synchronisation. When a sync fails quietly, HR shows one salary while payroll pays another. Group reporting turns into a reconciliation exercise and nobody can say with confidence which system holds the truth. The upstream errors Deloitte measured are the predictable output of this design.

Regulation raises the stakes

European regulation is making fragmented payroll data harder to live with. The EU Pay Transparency Directive required member states to transpose its rules by 7 June 2026, yet only Slovakia, Italy, Lithuania and Malta met that deadline. Several countries, the Netherlands among them, have confirmed a delayed implementation date of 1 January 2027, and the Dutch government published a draft regulation with a reporting template and data specification for consultation this summer. The uneven rollout does not reduce the workload. It multiplies it. Gender pay gap reporting depends on consistent job architecture and comparable pay data across the organisation, and legal advisers expect several member states to add obligations beyond the directive's minimum. An organisation whose pay data lives in five payroll systems with five definitions of a pay component will prepare those reports by hand, country by country, with a real risk that the figures do not reconcile.

A different architecture

PeopleCoral was built for precisely this segment: international organisations with roughly 100 to 2,000 employees operating across the EU and EFTA region. Our starting point is that HR and payroll should share one data model rather than be connected after the fact. The platform gives HR teams the tools they need to run an international workforce from one place: a single employee record across countries, organisational structure, performance management, leave requests, employee engagement and configurable HR workflows. Because payroll is built into the same platform, there is no connector between the HR record and the pay calculation. They are the same record. A change in contract or salary does not need to be synchronised, mapped or reconciled, because there is nothing to synchronise it with. We are also realistic about coverage. Deloitte is right that no single platform covers every country today, and we do not claim otherwise. PeopleCoral is expanding its built-in payroll functionality gradually, adding countries one at a time and only when local compliance is fully in place. That pace is deliberate. Every country added to a native platform removes a seam from the customer's landscape, whereas every country added to an integration architecture creates a new one. For HR leaders planning growth through new markets, mergers or acquisitions, the choice ahead is less about which local payroll vendor to select next and more about which architecture to commit to. The landscape of integrated local systems grows more expensive and less reliable with every country. A unified platform that extends its payroll reach step by step grows simpler.

Payroll without borders. HR without limits.

Sources