HR and payroll do not need one system - they need clarity on who owns what, and when it becomes true
HR and payroll are often expected to operate as though they are simply two parts of the same process.
In practice, they are doing different jobs, on different timelines, with different rules.
HR manages the employment relationship. Payroll turns that relationship into a correct payment.
Most of the time those two views align.
The problems start when they do not.
An employee’s salary changes. Their hours change. They move roles. Their leave entitlement changes. A new allowance applies.
HR needs to know what is true about that employee.
Payroll needs to know not only what is true, but when it became true, which payroll it affects, what has already been processed, and how the change should be calculated.
That difference is at the heart of many HR and payroll integration problems.
Real time is not always the right time
There is a common assumption that the best integration is a real-time integration.
Something changes in HR and it immediately changes in payroll.
That sounds ideal until you consider how payroll actually works.
Imagine an employee receives a salary increase effective today.
For HR, the new salary is now correct.
Payroll may still be processing the previous fortnight, where the old rate still needs to apply.
If the HR system immediately overwrites the employee’s rate in payroll, the integration may have transferred the data perfectly while creating the wrong payroll outcome.
The same issue can apply to hours, classifications, allowances, organisational assignments and other pay-sensitive fields.
Good integration therefore needs to understand more than the current value. It needs to understand effective dates, payroll periods and transaction timing.
One source of truth does not mean one system owns everything
Another common assumption is that HR should become the master for all employee information and payroll should simply consume it.
That works well for some data.
It works less well for information that is tightly connected to payroll calculation or compliance.
Depending on the organisation, payroll may be the better place to control:
- pay rate tables
- award or agreement entitlements
- leave configuration
- tax declarations
- superannuation details
- payroll calculation settings
Trying to maintain everything in HR simply for the sake of having one master system can create problems with timing, completeness and control.
A better question is: Which system is best placed to own each type of data?
The answer does not need to be the same for every field.
“Integrated” does not always mean integrated
Buying HR and payroll from the same vendor can appear to solve the problem.
Sometimes it does.
But many HR and payroll suites have evolved from different products, technologies or acquisitions. They may share a brand without sharing the same underlying data model, workflow or history.
That means buyers should test what “fully integrated” actually means.
Ask practical questions.
What happens if an employee’s rate changes today while the previous payroll is still being processed?
What happens with retrospective changes?
What happens when HR and payroll hold different values?
Those questions tell you more than a tick beside “HR and payroll integration” on a feature list.
Standard integrations may not fit every organisation
Off-the-shelf integrations are designed for common requirements.
That is often enough.
But many organisations use a mix of specialist systems for recruitment, learning, workforce management, point of sale, rostering or different business units.
The more specialised the organisation becomes, the less likely it is that one standard integration will perfectly reflect how employment actually works.
That is not necessarily a problem.
It may simply mean the organisation has chosen systems that are particularly good at the jobs they perform.
Integration should preserve choice
HR technology tends to change more frequently than payroll.
Recruitment, learning, performance, engagement and workforce management systems evolve quickly.
Payroll generally changes less often because replacement is more complex and consequential.
That suggests HR and payroll should often be evaluated independently.
Then evaluate whether they can be integrated properly.
AI is changing the economics of integration
Historically, custom integration could be expensive and time-consuming.
It can increasingly assist with schema analysis, field mapping, API development, transformation logic, testing, reconciliation and documentation.
That does not remove the need for good design or controls.
But it does change the trade-off.
The question is becoming less:
“Do these systems have an off-the-shelf connector?”
and more:
“Can these systems exchange the information we need reliably, with the timing and controls we require?”
That is a much better question.
The goal is not one system - it is one employment truth
HR does not need every piece of employment data to live in one database.
Payroll does not need to own everything.
And an organisation does not necessarily need one vendor to provide every HR and payroll function.
What it does need is clarity about:
- Who owns each piece of data?
- When does it become effective?
- Which systems need it?
- What happens when those systems are working across different points in time?
Solve those questions well and you can have multiple specialist systems while still operating from one coherent employment truth.
Bruce Sullivan is founder and CEO of Affinity, a company helping enterprise customers across Australia and New Zealand simplify payroll, reduce risk, and increase operational efficiency through intelligent automation.
This article was produced in partnership with Affinity Payroll
