Every HCM vendor tells you they do it all. Almost none of them do.
Behind every platform demo, every slick sales deck, and every requirements checklist tick, there are three distinct systems doing three very different jobs. And almost every vendor has a meaningful weakness in at least one of them.
That weakness rarely shows up in the demo. It shows up six months after go-live — in payroll errors, scheduling gaps, and compliance headaches that nobody can quite explain.
To spot the weakness, you first need to understand what the three systems actually are, why they're not the same thing, and where vendors consistently fall short in each one.
HCM — the people system
HCM — Human Capital Management — manages the employee as a person within the business. The core record. Job, role, manager, location. Onboarding and offboarding. Documents and policies. Performance, learning, time off.
Done well, a strong HCM should do one thing above all else — eliminate manual work from your HR team. Custom fields, automated workflows, role-based access, document management — when these work properly, your HR team stops living in spreadsheets and email chains.
That's the test. Not whether the vendor ticks the feature box. Whether your HR processes can genuinely be digitised, and manual work eliminated.
Many HCM vendors battle to get an A for that test. The core HR record is usually where they're strongest. Automation is where it gets tough. Vendors built around automation from the ground up — for example, HiBob — tend to score better here than legacy platforms with bolt-on workflows.
So before you sign anything — don't just ask if the system does onboarding or performance. Ask to see it automated. Ask how much configuration you get without needing a developer. Ask what your HR team will still be doing manually in twelve months.
If the demo doesn't show you that, push harder. Or walk away.
And that's just the HR side. Because there's a second system sitting beneath HCM that is more complex, more commonly misrepresented, and directly responsible for the majority of payroll errors.
WFM — the operational engine
80% of payroll errors don't start in payroll. They happen in the most politically complex system in the HR tech landscape.
WFM — Workforce Management — is the operational engine that sits between your people and their pay. It's where schedules are built. Where attendance is captured. Where lateness, absences, shift swaps, and breaks are managed. Where overtime, premiums, and allowances are calculated. And where worked time is turned into the gross pay inputs that feed payroll.
Three departments live inside it daily.
Operations use it to deploy the right people at the right time. Payroll depend on it to produce accurate pay inputs. HR police it to ensure policies and work rules are applied correctly.
When it works, nobody notices. When it doesn't, everyone blames each other. That's what makes it the most politically complex system in your business — and exactly why it's where things go wrong.
WFM vendors who do this well — for example, Dayforce — almost always handle payroll well too. The gap tends to appear on the HCM side — employee records, people processes, HR automation. If you're looking at a WFM vendor and expecting a strong HR system alongside it, push hard on that before you commit.
But the bigger risk isn't the vendor. It's the demo.
Most businesses let vendors show them their best case scenario. That's not where systems fail. Here's how to run a better one.
Bring your most complex pay rules into the room. Overtime thresholds, split shift premiums, public holiday allowances — whatever is hardest in your business. If the answer involves workarounds, you have your answer.
Get your operations and store managers into the demo, not just HR and IT. They are the daily users. Scheduling, shift swapping, and timesheet approval need to be fast and intuitive for someone whose primary job is running the operation, not running the system. If it creates friction in the demo room, it will create errors in the field.
Ask the vendor to show you how the system is configured for locations that operate differently. A generic setup rolled across sites of different shapes and sizes is a system that works for nobody. If the answer is vague or involves significant configuration cost, that tells you everything.
Payroll — the final line of defence
Payroll teams are the goalkeeper. When they're the ones catching errors, that's not a payroll problem. That's an upstream problem.
Payroll takes everything — salary, gross pay inputs from WFM, bonuses, commissions, benefits — applies the right deductions, tax, and statutory obligations, and produces the employee's final pay. Payslips, reporting, compliance submissions. Done correctly, it's invisible. Done poorly, it's the most visible failure in your business.
Payroll vendors are generally good at the core. Legislative compliance, calculations, deductions — the established vendors handle this well.
Here's where it gets interesting.
Payroll vendors already hold the employee record. It's a natural part of what they do — they need to know who to pay. And increasingly, they're using that foothold to branch into HCM. HR modules, people processes, self-service — packaged alongside the payroll engine as a full solution.
Holding an employee record and managing people processes well are two very different things.
Before that module is on your requirements list, test it the same way you'd test any HCM — automation, workflows, configurability. A payroll vendor's HR module is often where the weakness quietly lives.
Beyond that, two things to validate before you sign.
First, integrations. Specifically, how cleanly does the system import changes from your HCM and WFM? New starters, leavers, pay changes, worked time — if that data doesn't flow accurately and automatically, your payroll team becomes a manual checking function. That's not what they're there for.
Second, benefits. Taxable benefits sitting outside payroll is a compliance gap that catches businesses out more often than it should. Ask the vendor how benefits are handled and how they feed into payroll calculations.
So where does that leave you?
Three systems. Three distinct jobs. And almost every vendor with a weakness in at least one of them.
The next time a vendor tells you they do it all — you'll know exactly what to ask, who to bring into the room, and where to look.
Because the gap between what a vendor promises and what a system actually delivers rarely shows up until after you've signed. The businesses that avoid that gap are the ones who understood the landscape before they walked into the demo.
Now you do.