The Governance Gap: Why HR and Payroll Need More Than a One-Way Integration

Many organisations are investing heavily in Core HR platforms with a clear ambition: create a single source of workforce data, strengthen governance and improve confidence in the information being used to run the organisation. All entirely sensible. But there is an assumption I see repeatedly that worries me:

Core HR holds the master record and sends the relevant data to payroll – therefore the workforce is governed.

Some would argue payroll is the master rather than Core HR. In my view, it doesn't matter which you choose: neither is truly the master unless the loop between them is closed. Sending data successfully from one system to another proves that the integration worked. It doesn't prove that the two populations remain aligned – and that distinction matters.

The organisation chart and the payroll have to tell the same story

On a process map, the employee lifecycle can look beautifully straightforward. Someone joins, the approvals happen, their record is created in Core HR, the information passes to payroll and they are paid. But payroll environments are rarely that neat.

Large organisations may operate across different countries, legal entities and payroll providers, some highly integrated and others dependent on files or manual activity, with local regulations and legacy technology that cannot disappear overnight. And, crucially, there may still be ways for information to enter or change in payroll outside the intended Core HR route.

Usually this isn't because someone is deliberately avoiding governance. It's because payroll has to run. People need to be paid, deadlines are immovable and local teams find practical ways to resolve problems. But it creates an important control question:

If someone can enter payroll without following the intended HR process, how do we know?

That, for me, is the governance gap.

A single source of truth has to be proven

We use the phrase single source of truth a lot in transformation. But declaring a system to be the master doesn't make everything within it correct – and it certainly doesn't guarantee that another critical system hasn't quietly diverged from it.

Imagine Core HR says the organisation employs 20,000 people, and payroll pays 20,017. Many of us don't need to imagine it – we've seen it. Which number is true?

There may be perfectly legitimate reasons for the difference. Timing, different population definitions, retrospective changes or local requirements can all create explainable exceptions. The important point is that someone should know there is a difference, understand why it exists and be accountable for resolving it where necessary. Without that, we are simply trusting that the process worked because we sent the right information at the beginning.

The missing control is reconciliation

I learned this early in my systems, operational and transformation career. We had implemented a global ERP that fed payroll in our jurisdiction, but there was no closed loop back. I worked hard to build one against a lot of resistance, and early on the reconciliation turned up a ghost employee who had been on the books for around two years. It wasn't someone who had been due to start and never arrived; it was fraud, and it ended up in the hands of the police. It's the only time in my career I've seen that, and I truly believe it's rare – but it's exactly what an unreconciled system allows.

For me, this is where the design needs to change. Rather than thinking about HR and payroll as a simple sender-and-receiver relationship, we need to think about the employee lifecycle as a closed loop. The HR process authorises and records the workforce change, the relevant information moves into payroll, payroll executes – and then the resulting payroll population is reconciled back against the governed workforce population.

That final step is what surfaces the exceptions. Are we paying people who don't appear in the expected HR population? Are people missing from payroll who should be there? Are changes reflected consistently across both systems? Has something entered payroll through an alternative route?

The purpose isn't simply to find discrepancies and correct the data. The more valuable question is why the discrepancy was possible in the first place. A difference may be a data issue, but it may also expose a broken process, an unclear ownership model, an integration failure, a local workaround or a gap in the control environment. That's useful information, because governance is no longer just checking the output – it is helping us improve the process.

This doesn't require one global technology solution

Closed-loop governance doesn't mean every country or business needs exactly the same payroll system; for many complex organisations, that simply isn't realistic. You can have different providers, technologies and integration methods and still share a common control principle. Nor does it mean one-way integrations are wrong – they are an important part of an efficient technology landscape. They just aren't the whole control.

What matters is being clear about the relationship between the systems. Core HR may be the authoritative source for the workforce record; payroll may be the authoritative source for what was actually paid. Good governance connects the two. It establishes what should flow between them, what comes back, what is reconciled, which differences are acceptable and who owns the exceptions.

Real governance is not about controlling a system. It is about designing an end-to-end workforce lifecycle that reflects how work actually happens.

This is much bigger than HR systems

Workforce data increasingly feeds decisions well beyond HR – employment cost, headcount, workforce planning, compliance, and the modelling of productivity, skills and future requirements. AI will only make the quality of that data more important.

If different parts of the organisation are working from subtly different versions of the workforce, the problem doesn't stay between HR and payroll. It flows into reporting, financial planning, analytics and ultimately executive decision-making. The question "How many people do we employ?" should be one of the easiest for a large organisation to answer. Surprisingly often, it isn't.

From data integration to genuine governance

If we want to call Core HR our single source of truth, we need confidence that the workforce represented in our systems remains aligned with the workforce operating – and being paid – in the real organisation. That means designing feedback and reconciliation into the model, making exceptions visible and using those exceptions to improve the underlying process.

Because ultimately, governance isn't about declaring where the truth lives.

It's about continually proving that what we believe to be true still matches reality.