How to test whether HR, payroll, performance and learning are genuinely joined up

Wanting one system for HR, payroll, performance and learning is really about wanting one employee record.

This doesn’t necessarily mean one piece of software, and the real test is what happens to your data when something changes.

When businesses seek one system for HR, payroll, performance and learning, they usually assume they’re tackling a software problem.

In actual fact, it’s a data problem.

Let’s look at a scenario: an employee receives a promotion. The change is typed into HR, then typed again into payroll, and then someone remembers the new role requires training. These are all manual inputs, each creating an administrative task for a single event.

Now, buying a ‘single’ platform doesn’t automatically fix this process.

Buying two products doesn’t automatically cause this issue.

The defining factor is whether data is connected and what happens when something changes.

‘All-in-one’ HR software is a marketing category, not a technical one

The term ‘all-in-one’ describes how software vendors package and price their products.

It’s a catch-all term that tells you very little about the data architecture underneath.

An HR suite sold as one product can run its modules on separate databases with overnight syncs.

By contrast, a core HR platform connected to a specialist partner can share one employee database and pass changes through as they happen.

Now, not every HR suite splits up its data, and not every core HR platform connected to partners is truly integrated.

The point is that there’s a level of nuance that needs unpicking when speaking with a vendor.

Three red flags of disconnected data you need to keep an eye out for are:

• The same change needs to be entered more than once – a leave date, a new line manager, a change of contracted hours.
• Month-end requires you to reconcile two systems rather than closing one.
• Reporting across functions means spreadsheet exports before anyone can answer the question.

To determine whether there’s a true connection, ask the vendor: is there one master version of each employee, and what happens to it when something changes?

How to know if an HR system is genuinely integrated

When looking to determine the level of integration on offer, take an ordinary event and follow the journey.

For example, what happens when an employee is promoted?

There’s a pay rise, potentially a new reporting line, a different job family and mandatory training attached to the new role.

Here’s what should happen when everything is connected:

• HR record: job title, job family, grade, line manager and effective date all change in the system, along with terms such as notice period or holiday entitlement.
• Payroll: the new salary applies from the effective date, part-month pay is pro-rated, pension contributions are recalculated on the new pensionable pay and backdating past the cut-off becomes an adjustment, not next month’s correction.
• Performance: objectives shift to match the new role, the employee transfers to their new manager and their previous manager’s feedback history stays intact and accessible.
• Learning: new mandatory courses are assigned with a deadline as soon as the new job title reaches the learning record, automatically where the role is mapped to a learning path, manually where HR and the learning platform aren’t integrated. Old-role training is retired but retained for audit, and a renewal cycle starts for any certification the new role requires.
• Permissions: the new manager receives access to the employee record so they can see pay, absence and performance data, and the former manager loses access and visibility.

What to ask an HR vendor

At each step, there’s a burning question: who types the change, and into what?

When demoing a new HR platform, ask the vendor to run through a multi-touch example like the one provided above, then watch for five things:

1. Where the change is entered, and whether it is entered more than once
2. Whether the effective date reaches payroll unchanged, and what happens when it’s backdated past a cut-off
3. Whether the new manager’s permissions are automatically updated, and what they can see afterwards

Whether role changes sync from HR and trigger assignment by rule, or whether an administrator has to update the learning record first

The difference between a shared record and a synced record

A shared record means there’s one master version of your employee data.

HR, payroll, performance and learning read from that record rather than keeping their own copy.

Enter a change once and see it everywhere.

Synced records mean each system holds its own version of the employee.

They’re linked by a mapping table that says which record in one system belongs to the same person as a record in another, and reconciled on a schedule.

This approach can work provided you know the record is being copied rather than shared, how often and what happens when a copy fails.

Many HR stacks sit between the two, and what you need to determine is not which pattern a vendor claims, but which system is the master and what happens if the two disagree.

Ask the HR vendor these questions to better understand the data capabilities:

1. Is there one employee record across all functions or a mapping table between separate systems?
2. Are updates event-driven or batched on a schedule?
3. What happens if a sync fails, and who is notified?
4. Can we report across HR, payroll, performance and learning?

Where specialist depth beats single ownership

Learning and development is the clearest case for not insisting on a single owner.

A native learning module inside an HR system is often built to handle the basics:

• Assign a course
• Record a completion
• Produce a report

This functionality covers baseline learning and may be all your business requires.

However, bringing in a specialist learning platform enables you to unlock so much more value from the training you provide.

A specialist learning provider offers:

• Curated content libraries
• Blended delivery combining eLearning with instructor-led sessions
• Accessibility-optimised content
• Course translation
• In-depth analytics

A dedicated learning platform can go much deeper because learning is its only job, and all of the development time and resources goes into that.

The trade-off is the risk of a second employee database and double the administration.

Unless the record is genuinely shared, you’ll be juggling two systems and two sets of data.

When assessing a learning platform, determine whether:

• Learner accounts are built from the HR record
• A role or department change updates the learning platform
• A leaver in HR removes learning access
• Completion, certification and expiry data can be reported against employment data

IRIS takes the specialist route, integrating with a dedicated learning provider.

IRIS Cascade connects to Kallidus Learn LMS.

Employee records in the HR system are shared with the learning platform, so learner accounts, roles and departments stay up to date without manual intervention.

The connection is configured once at implementation rather than run as an export someone has to remember.

Employees access Learn LMS from inside the IRIS Cascade platform.

Certifications and expiry dates sit against the employee record and can be reported by team, site or role.

What HR integration should include

A demo shows what the software can do on a good day.

Whereas the contract is what you rely on for the next five years.

Get these five clarified and written down before you sign:

• Single sign-on across all systems, so nobody has to maintain separate credentials
• One official version of each employee record, stating which system holds the master copy
• How quickly changes are actioned across systems, defining whether that’s immediately, within minutes or hours
• Joint support ownership, with one named accountable party
• Integration roadmap ownership, including who maintains it and what notice you get if either product changes

The UK payroll and HR obligations that do not change

However your systems are joined up, the UK requirements sit on top and are non-negotiable:

• Real Time Information (RTI) submissions to HMRC on or before each payday
• Pension auto-enrolment, ongoing assessment and re-enrolment every three years
• Statutory payments, including sick pay and family leave pay
• Payroll software that reports PAYE information online to HMRC (HMRC publishes a list of recognised software)
• Holiday pay under UK rules, including irregular hours and part-year workers
• UK GDPR across employee data held in all four functions

The last point often catches organisations out.

Often, payroll and HR data get mapped with precision, but performance and learning are treated as though they sit outside the scope.

They don’t.

Appraisal notes, capability assessments, training records and certification histories are all employee personal data, and they carry the same weight.

This has practical consequences for how joined up your systems need to be.

If a subject access request arrives, you need to know which systems are holding a record of that person and who is accountable for acting in each one.

Preparing for your next HR software demo

At your next demo, count how many places a human has to touch the data.

That number tells you more about whether HR, payroll, performance and learning are joined up than any feature comparison.

Building the case for HR software internally?

Our buyer’s guides cover what to look for by size: HR software for UK businesses with 50–200 employees, HR and HCM software for UK businesses with 200 to 1,000 employees and Enterprise HR and HCM software for UK organisations with 1,000+ employees.

Ready to talk with a vendor? See IRIS Cascade in action and speak with one of our HR specialists.

HR, payroll, performance and learning

Frequently asked questions (FAQs)

If we want one system for HR, payroll, performance and learning, what should we choose? 

Start by defining your desired outcome rather than the product count. Determine which system holds the master employee record. The HR system should hold role, pay and training changes and share them without the need to re-key data. Ask the vendor to demonstrate that with a live example. A single suite and a core platform with specialist partners can both meet that test.

Does all-in-one HR software have to come from one vendor?

No. What matters is whether employee records are connected and changes are made across systems without re-keying. A single vendor can still run modules on separate databases, and a core HR platform with a specialist partner can share one record. When looking at HR software, test the data flow.

What is the difference between an integrated HR system and separate systems that sync?

An integrated system holds one master employee record that every system pulls from. Synced systems each hold their own data, joined by a mapping table and reconciled.

How do I know if an HR system is genuinely integrated?

Ask the vendor to show an example, like an employee promotion, which involves a pay rise, new manager and mandatory training. Count how many times a human enters data. Multiple manual touchpoints indicate separate systems presented as one.

What should I ask a vendor in an HR software demo?

Ask which system is the master record, whether updates are made in real time and whether you can report across all areas. Look for a demonstration, not a description.

What HR software includes payroll for UK organisations?

IRIS provides HR and payroll for UK organisations. IRIS Cascade features built-in payroll, and Staffology HR integrates with Staffology Payroll. Both are built for UK employment requirements and HMRC submissions.