The New Buying Logic for HR and Payroll: 428 Interviews, Two Waves

Put the two waves together and the picture is stable: 81% of the 428 leaders interviewed are not on a single unified system, and two in three describe environments that only stay aligned because someone re-keys changes, exports and imports files, or reconciles mismatches by hand. The share on one system barely moves, from 18% in the first wave to 21% in the second.

What the second wave adds is the texture of that work. Two in three organizations (67%) hold people data in two or more systems, nearly half (49%) see records drift out of sync at least occasionally, and at 38% of organizations someone spends a few hours or more every week reconciling data between systems. The first-wave leaders described the same tax in kind: applicant tracking that does not talk to time and attendance, payroll that does not feed benefits, records re-keyed between tools that were never designed to connect.

“The real expense of a fragmented back office is the manual work no one prices at purchase. This research puts numbers to what finance leaders feel every close cycle: disconnected systems are a recurring tax, and consolidating onto one is as much a cost decision as an operational one.”

When leaders in either wave describe what they want, they do not list features. They describe a single system: one platform, one app, one source of truth, so employees and administrators stop jumping between tools and reconciling data by hand. Across 428 interviews, more than four in five have not reached that state.

The first wave could only infer demand from that gap. The second wave asked the question outright, and the answer confirms the inference: 62% of leaders would welcome one unified system (38% outright, 25% with reservations), 30% are already unified or expect little practical change, and only 6% would prefer to keep separate systems. The appeal tracks the pain. Among leaders in fragmented multi-system setups, 87% would welcome one system (53% outright, 34% with reservations), against 58% in partially unified environments, and only 8% of the fragmented group would keep separate systems.

In both waves the reasoning is about risk rather than tidiness: fewer integration points that can break, fewer manual touch points where errors enter, and a smaller surface area to secure and audit. The second wave puts a number on the benefit leaders name first: less manual entry, reconciliation, and data movement (40%), ahead of better reporting and visibility (17%), more consistent and secure data (17%), and fewer logins and vendors to manage (16%).

“For years, HR and payroll were bought feature by feature. What stands out here is that leaders are done managing the seams between systems. The teams that feel in control are the ones who stopped reconciling by hand and moved to a single source of truth, and that is a people decision as much as a technology one.”

Compliance and security were on every leader's mind in both waves, and in both the confidence that exists is built on effort rather than architecture. In the first wave, 55% felt confident because they had formal controls, vendor safeguards, and active oversight in place, 18% mainly relied on IT, vendors, or outside experts, and 27% felt exposed by manual processes and disconnected tools. The second wave shows what that effort looks like: 57% still track at least some regulatory change by hand, 52% manage compliance across multiple states or countries, and 45% have had a compliance scare, close call, or security incident at some point.

The two waves also agree on where exposure comes from. First-wave leaders tied it directly to disconnected data, with every integration a potential point of failure or leak. The second wave measured it: among leaders in fragmented multi-system setups, 24% feel exposed, against 2% in partially unified environments and none of those on a unified single system. Almost nine in ten leaders who feel exposed run fragmented setups, and 19% name manual file transfers, disconnected-system errors, or integrations as their single biggest security risk.

Taken together, 428 interviews describe confidence that holds because people watch it constantly, not because the systems handle it. That is why consolidation reads as risk reduction rather than convenience in both waves.

“The finding that stays with me is that most leaders' confidence in compliance is manual. It holds because people watch it constantly, not because the systems handle it. That is a heavy load to carry, and it is why moving to one unified system reads as risk reduction, not convenience.”

Across both waves, buyers have moved past subscription price as the measure of value. About eight in ten of the 428 leaders judge a platform across the whole cost of ownership: license, implementation, services, configuration, and the internal effort needed to run and optimize it. The contract price is one line item, not the decision. That challenges a common assumption in the category, that buyers ignore services and support when comparing vendors. They do not, and the second wave shows why: the costs that surprise them arrive after signing. Leaders say buyers most often underestimate ongoing support, maintenance, and paid add-ons (30%) and implementation, configuration, and internal labor (29%), and 48% of those who could judge a past purchase underestimated its full cost.

Support sits inside the same calculation in both waves. In the first wave, 77% wanted dedicated, continuous human support from specialists who know their account rather than a ticket queue. In the second wave, 74% strongly prefer or consider essential a dedicated contact who knows their business, and 55% have been through generic support that caused delays, repeated explanations, or a missed payroll-critical issue. Buyers are pricing the effort and risk around the software as well as the license, and the partner who stays after go-live is part of what they are buying.

“The clearest signal here is that buyers no longer equate price with value. Nearly eight in ten weigh total cost of ownership, the implementation, the services, the ongoing support, over the subscription line. On that math a fragmented stack carries a recurring tax in manual work, and consolidating onto one well-supported system is as much a finance decision as an operational one.”

Neither wave finds switching impossible. Both find it high-stakes. In the first wave, 63% said a switch is manageable yet highly time- and resource-intensive, 26% called it a major burden and a high-risk disruption, and only 11% were readily open to change. The weight comes from what these systems touch: payroll and HR reach every employee, so any transition carries the risk of disrupting pay, benefits, and trust.

The second wave moved from attitude to experience. Of the 65 leaders who personally led an implementation in the last few years, 54% met at least one hidden cost, most often consultant, configuration, or support fees (23%), and 49% needed more time, staff, or budget than planned. The same group also shows what tips the balance: 66% say the vendor made migration, setup, or training easier or gave strong hands-on support, against 29% who say the vendor made it harder. Asked what holds them back from a change, second-wave leaders most often say their current system works (33%), followed by the cost of switching (26%) and timing and capacity (19%), and the information they most want before signing is the all-in cost of integrations, services, support, and future fees (31%).

Across 428 interviews, the conclusion is the same: buyers will move when the upgrade clearly outweighs the strain and when they believe the migration itself will be handled. Confidence in the move is what turns a feared project into a manageable one.

Buyers in both waves are not resistant to automation. They are conditional about it. The first wave found 80% open to AI and automation in HR and payroll as long as human oversight and guardrails stay in place, with 15% broadly hesitant and 5% willing to allow it only in low-risk tasks. The line they drew was at high-stakes, money-touching decisions, where they wanted approval workflows, explainability, audit trails, and proof before handing over control.

The second wave kept the stance and named the conditions. 86% say reliability and predictability come first when they weigh new AI features, and 89% raise at least one concern, led by errors, hallucinations, and payroll accuracy (40%), bias and explainability (20%), and data privacy and security (19%). What would earn more trust is proof: accuracy demonstrated over time (39%), human approval checkpoints and override controls (24%), and testing on their own scenarios or peer evidence (20%). Most already automate part of the work, most often payroll, tax, and calculations (34%).

Both waves also tie trust in automation to the data underneath it. The first wave argued that automation feels safer on one governed source of truth than across disconnected systems. The second wave measured the link: 30% say AI would earn more of their trust if it drew on one unified data source, and 16% have already seen data from multiple systems cause errors, inconsistency, or rework in automation.

Routine decisions are a steady weekly load on managers. 37% of leaders say managers spend a few hours a week on them and 26% say half a day or more. 30% say less than an hour, 7% say it varies widely by manager or team, and just 1% say these decisions are already largely automated.

Time-off, leave, and time-card approvals create the most friction (29%), followed by expense approvals (23%), payroll exceptions and corrections (19%), and employee changes and scheduling (17%). Most leaders (61%) call the time reasonable, but 24% say it is too much and another 10% say it could be cut through automation. The heavier the load, the less reasonable it feels: where managers spend half a day or more each week, 47% of leaders say it is too much, against 7% where it takes less than an hour.

This is the quantity the first wave's findings only implied. The first-wave leaders who were open to automation with oversight were describing a willingness. The second wave shows the work that willingness would apply to, and it is measured in manager hours every week.

Leaders are ready to let policy decide the routine. 77% agree that routine HR and payroll decisions should be automated whenever company policies clearly define the expected response: 44% strongly and 33% generally. 9% are neutral and 15% lean toward disagreeing or disagree.

Support holds even among the cautious. 57% of leaders who are holding back on automation today still agree, and agreement rises with the workload, from 68% where routine decisions take managers less than an hour a week to 91% where they take half a day or more. Leaders draw the line at exceptions: 33% would let clear policy-defined decisions run end to end, 34% want human review kept for exceptions, high-impact changes, and sensitive cases, and 16% want automation to recommend or route with a person approving. Only 17% want a person involved in every routine people decision.

Practice lags behind. Only 24% have automated any policy so far, most often for time-off, scheduling, or approvals (17%), and another 7% are piloting or planning it. Read against the first wave, this is the same conditional openness, made operational: automation leaders control, running on their own rules, with people reviewing the exceptions.

“HR and payroll leaders are increasingly looking for software that automates decisions for them. They want to reduce the operational burden created by disconnected systems. They want data consolidation that enables full-solution automation through decisioning logic, reducing manual work, improving accuracy and giving organizations greater confidence in their data. When information flows through a single software, teams can automate routine processes, spend less time reconciling systems and focus more on supporting employees and driving business outcomes.”