At enterprise scale HR products have converged on features and diverged on how well they handle a global organisation's contradictions: one data model across many countries, local requirements that cannot be configured away, and a change programme the organisation has to absorb alongside everything else.
One data model, many jurisdictions
The system has to express a single employee record while supporting country specific fields, contract types and statutory requirements. Products differ sharply in whether local requirements are configuration or bolt ons, and the difference shows up as a maintenance burden in every country outside the vendor's home market rather than as a gap in a demonstration.
Integration load is the real project
Identity, payroll in each country, finance, learning, access provisioning, and whatever the business has built. Count them, name an owner for each, and ask for reference customers running the same set. Enterprise HR programmes overrun on integration and data migration far more often than on configuration.
Change capacity, not capability
The organisation can absorb a limited amount of change per year, and an HR system touches every manager. A phased rollout by region or function usually beats a single cutover, and the programme that succeeds is the one scoped to what people can actually adopt rather than to what the product can do.
Questions people ask about enterprise human resources software
Should payroll be part of the same product?
One platform with local payroll partners is the common answer. Direct payroll in every country is rare and worth verifying country by country.
How long does an enterprise implementation take?
Quarters to years depending on scope, with data migration and integration dominating rather than configuration.
What derails these programmes?
Underestimating data quality and the local requirements that cannot be configured away. Both are discoverable early if you look.