Global groups don't have a payroll problem. They have a visibility problem.
Most multinationals run close to five payroll systems and cannot say, on any given day, what payroll actually costs them.
The average enterprise now runs close to five separate payroll systems, and two-thirds of organisations with operations in five or more countries cannot see payroll’s processing status across all of them on any given day, according to Strada’s 2026 Global Payroll Workforce Possibility Report. That is not, in the end, a payroll problem. It is a visibility problem — and, as the figures below show, a costly one.
On this page
Five systems, one number nobody can produce
Ask a group HR director how many payroll providers the organisation uses worldwide, and the honest answer, more often than not, is "we’re not entirely sure." That is not a failure of the individual. It is the predictable result of how global payroll actually gets built. A company rarely designs its payroll estate; it accumulates one. An acquisition arrives with its own contracts and its own provider, already live and already paying people correctly, so nobody touches it. A new market opens and the regional HR lead signs with whichever local specialist a peer recommended. A decade and a dozen deals later, nobody owns the whole picture, because payroll sits split across HR, finance and local country management, and none of the three is positioned to see all of it at once.
The scale of that fragmentation is now well documented. Three-quarters of organisations use more than two vendors to manage global payroll, and more than a third use three to four, according to a 2026 survey of 319 senior payroll leaders by KPMG and UKG. The same research found that 92% of organisations claim to have a global pay strategy, but only 33% have actually achieved a standardised operating model to go with it — the ambition is close to universal; the execution isn’t. PayrollOrg’s 2025 "Getting the World Paid" survey adds a related detail: of the minority of companies (33%) that do use a single global payroll provider, more than a quarter still run two to five additional providers alongside it for specific regions. Consolidation, in other words, is often only partial even where it has nominally happened.
What fragmentation actually costs
Two numbers get conflated here, and it is worth separating them properly. The first is the cost of payroll in the literal sense: gross salary, employer social security or National Insurance contributions, statutory health and accident insurance, pension contributions, and whatever other employer-side charges a given country requires. That number is genuinely large — KPMG’s 2026 research puts total payroll cost at 40–60% of operating expenses for a typical organisation — but it describes labour intensity, not administrative quality. A retailer or a manufacturer with thousands of employees will sit in that range however well or badly its payroll is run.
The second number is the fully loaded cost of running the payroll function itself: the systems and licences, the local providers and brokers who administer it country by country, the static and master data management that keeps tax codes, bank details and cost centres accurate across entities, and the hours spent reconciling all of it. That figure is far smaller as a share of the first one, but it is the one this article is actually about, and it is the one riddled with the fragmentation described above. None of it shows up on a P&L as a line called "payroll administration waste." It is buried in late-payment penalties, correction cycles run twice because the first pass used the wrong exchange-rate date, duplicate software licences nobody cancelled after a provider switch, and the hours a regional controller spends reconciling three currencies against a head-office template built for one.
That inefficiency shows up directly in the numbers, expressed as a share of the money actually moving through payroll rather than of total opex: Strada puts it at 2.6% of annual payroll spend lost to errors, rework, compliance failures and plain inefficiency — on a $200 million payroll, that is roughly $5.2 million a year, recurring. The KPMG/UKG survey found 38% of large organisations reporting $1–5 million in preventable annual losses, and notes that even 1% of wasted spend can reach $15 million at scale. Almost half (47%) of Strada’s respondents with operations in five-plus countries incurred compliance-related costs above $500,000 in the past year alone.
Neither survey breaks down what a "compliance-related cost" actually is, so it helps to be concrete. In the UK, HMRC fines an employer between £100 and £400 a month, depending on headcount, for every Full Payment Submission filed late under Real Time Information — and that penalty applies separately to each PAYE scheme a group runs. It is a small number on its own. Multiplied across a dozen local entities, twelve pay cycles a year, and the routine chaos of a provider switch or an acquisition mid-year, it compounds quickly — and that is before misclassification penalties or under-remitted social contributions, which tend to be far larger, are even factored in.
Why "just consolidate everything" is the wrong first move
The instinctive fix — pick one platform, migrate every entity onto it — is available, and for some companies it is right. ADP’s Global Payroll product, for instance, is explicitly built as a single system of record, replacing local point solutions across 140-plus countries and territories rather than working around them. That model suits organisations with a manageable number of large entities, or ones already mid-way through a broader systems consolidation as part of an M&A integration programme.
But for a global group whose local providers already work — they pay people correctly, on time, in compliance with local law — full re-platforming is slow, expensive, and carries exactly the operational risk payroll can least afford: nobody wants a payroll failure caused by a systems cutover. A second model works differently, and it is no longer treated as a stopgap: an aggregation layer that sits on top of the providers already in place, rather than replacing them, is now sold as a dedicated product in its own right. Deel’s "Payroll Connect" feature, for example, lets a company view its own centrally run payroll and its third-party payrolls side by side in one dashboard during a transition, so a team can start with a single country or entity and expand at its own pace, rather than switching every provider on day one. Most of these aggregation tools are also built to plug into whichever HRIS a company already runs — Workday, SAP SuccessFactors, Oracle — rather than requiring a parallel system, which matters for any group that has already invested years in a single HRIS backbone across its brands and sites. The point here isn’t to endorse a specific vendor; it’s that "integrate rather than replace" is now a credible, productised path, not a compromise.
You can’t fix what you haven’t priced
Whichever path a company eventually takes — full consolidation, an integration layer, or a mix by entity size — that decision is only as good as the inventory it rests on. And on the evidence, that inventory is often missing: just 28% of companies in PayrollOrg’s 2025 survey report having a formalised global payroll strategy at all, which suggests a majority are managing the estate reactively, provider by provider and renewal by renewal, rather than from a full picture of what is running and what it costs. It is hard to choose well between consolidating and integrating — or to decide, deliberately, to do neither for now — without that picture: entity by entity, what is actually running, what it costs, and where the exceptions live. Building it is the unglamorous step many organisations skip, because it sits at the boundary between HR, finance and IT, and nobody’s mandate quite covers it.
It doesn’t stop at payroll
The same confusion — mistaking the size of a spend category for the cost of administering it — shows up in two adjacent areas that often surface in the same conversation, even though they are separate problems and should be scoped as such.
Contractor and contingent-worker payments are one. No survey we have found measures this directly, but the same forces that fragment payroll apply just as plausibly here: decentralised hiring and entity-by-entity decisions tend to produce a similarly uncoordinated set of agencies and platforms for paying contractors, each carrying its own compliance exposure that varies by country — the UK’s IR35 regime is a widely cited example in Western Europe. Several of the payroll aggregation platforms already mentioned, including Deel and Papaya Global, now handle contractor payments alongside employee payroll for exactly this reason, but it remains a distinct workstream.
Expense management is the other, and the underlying mechanism is the same one driving payroll fragmentation: without a reason to standardise, corporate cards and travel-and-expense claims tend to pile up one system per entity, reconciled manually at head office. Brex’s Global product, for instance, consolidates corporate cards, expense management and local-currency payments across more than 200 countries and territories in upwards of 100 currencies for multinational groups, and already covers UK and European entities that sit within a group with US operations. Brex itself is not yet licensed to onboard businesses operating solely within the EU or UK without a US presence, so today it fits the multinational case specifically, not a standalone European card provider.
These platforms can also put employee and contractor spend in one place, though it is worth being precise about what that means. Ramp, for example, has a distinct "Guest" access tier built for contractors and temporary workers: a Guest can be issued a card or submit reimbursement claims, and that spend then appears in the same admin-side reporting as regular employees’ — without giving the contractor visibility into anyone else’s spend or the company’s wider finances. What gets consolidated is discretionary, non-personnel spend: travel, software, equipment, client costs. It does not touch the contractor’s own fee or invoice, which still runs through accounts payable or, increasingly, through the same EOR platforms already handling contractor payroll.
Aulay’s view
Standardise the exceptions before you build or buy anything. That is most of the value a "payroll transformation" project is actually chasing, and it is achievable without touching a single vendor contract. The case is strongest for organisations with a genuinely global footprint outside financial services — manufacturing groups with plants across several regions, retail groups with brands and stores in dozens of markets, head offices running functions across multiple time zones — precisely because fragmentation compounds fastest where there is no shared entity structure to begin with, and where payroll has never been anyone’s full-time job to rationalise.
If your organisation runs payroll across ten or more countries and no one can currently produce a single, reliable figure for what all of it costs, that is the starting point, not something to fix later. Aulay works with group HR, Comp & Ben and HRIS leaders to run that payroll footprint review and turn it into a consolidate, integrate or hold decision that fits the business as it actually is — not as a vendor’s roadmap assumes it to be. Get in touch with Aulay to scope a payroll footprint review for your organisation.
References
1. Strada, "Global Payroll 2026 Workforce Possibility Report," published 22 July 2026
https://stradaglobal.com/insights/global-payroll-workforce-report/
2. KPMG, "Payroll at the tipping point: The case for C-suite elevation," 2026
https://kpmg.com/us/en/articles/2026/global-payroll-survey-report.html
3. UKG, "UKG and KPMG: Nearly 40% of Employers Suffer Millions of Dollars in Preventable Losses Annually Due to Global Payroll Errors," newsroom release, 31 March 2026
https://www.ukg.com/company/newsroom/ukg-and-kpmg-nearly-40-employers-suffer-millions-dollars-preventable-losses-annually-due-global-payroll-errors
4. PayrollOrg (American Payroll Association / Global Payroll Management Institute), "2025 Getting the World Paid Survey Report," fielded 3 February – 3 April 2025, 585 respondents, pp. 5–7.
https://info.payroll.org/pdfs/global/Global-Payroll-Week-2025-survey-results.pdf
5. Deel, "Payroll Solutions" product page, section "Payroll Connect," accessed September 2026.
https://www.deel.com/solutions/payroll/
6. "ADP Global Payroll" product page, ADP, accessed September 2026.
https://www.adp.com/what-we-offer/products/adp-global-payroll.aspx
7. Brex, "Global" product page, accessed September 2026.
https://www.brex.com/product/global
8. Brex, "Brex EU Expansion" support page, accessed September 2026.
https://www.brex.com/support/brex-eu-expansion
9. HM Revenue & Customs, "What happens if you don’t report payroll information on time," gov.uk guidance, accessed September 2026.
https://www.gov.uk/what-happens-if-you-dont-report-payroll-information-on-time
10. Ramp, "User role deep-dive: Guest," Ramp Help Center, accessed September 2026.
https://support.ramp.com/hc/en-us/articles/18547246096531-User-role-deep-dive-Guest
Frequently asked questions
- Is consolidating onto one payroll platform always the right fix for fragmentation?
- No. Full consolidation suits organisations with a manageable number of large entities, or those already mid-way through a broader systems consolidation. For many global groups, an integration layer over existing, functioning local providers reaches the same visibility and control faster and with less operational risk.
- What is the difference between a global payroll platform and a payroll aggregation layer?
- A platform such as ADP Global Payroll replaces local systems with one system of record. An aggregation layer, such as Deel’s Payroll Connect, sits above existing local and third-party providers and gives a consolidated view without requiring their replacement.
- What should come before choosing between consolidating and integrating?
- A payroll footprint review: a full inventory of every entity, provider, contract and cost line, mapped against actual headcount. Fewer than three in ten organisations currently have a formalised global payroll strategy to base that decision on.
- Does this also apply to contractor payments and expense management?
- The same fragmentation logic plausibly extends to both, though it is not separately measured the way payroll fragmentation is. Either way, they are separate problems from payroll and should be scoped as such: Deel and Papaya Global now handle contractor payments alongside employee payroll; expense management has its own emerging aggregation layer, such as Brex’s Global product for multinational card and spend consolidation, or Ramp’s "Guest" tier for issuing cards to contractors. What gets consolidated in every case is discretionary, non-personnel spend — not the contractor’s own fee, which still runs through accounts payable or an EOR platform.