The headcount data your Finance team is working from is probably wrong

The headcount data your Finance team is working from is probably wrong.

Not because anyone has made an error. Because it was never designed to give Finance what Finance actually needs.

Most organisations piece their workforce numbers together from payroll, an HRIS, a set of business unit spreadsheets, and whatever was reported last quarter. Each of those sources was built for a different purpose — compliance, payroll processing, operational scheduling. None of them were built to answer the questions Finance is now being asked to model: what does this workforce actually cost in full, what is it capable of, and what will it look like in two years if current trends hold?

The data exists. It is just fragmented across systems that do not talk to each other, owned by teams with different definitions of the same terms, and updated on cycles that bear no relationship to when the decisions actually need to be made.

What Finance thinks it is modelling

When Finance models a headcount scenario — a restructuring, a new function, a response to a retention spike — it believes it is modelling the workforce. Fully loaded cost by role. Capacity by function. Risk concentration by department. A credible picture of what exists and what changes if you pull a given lever.

What it is actually modelling is the workforce as the data infrastructure happens to describe it. Which is a different thing.

Roles that have evolved but whose job families have not been updated. Costs that sit in the wrong cost centres because of a reorganisation two years ago that nobody reconciled in the system. Capability assumptions built on qualifications recorded at hire, not on what people have actually done since. Attrition figures that reflect who has left, not the differential value of who has left versus who has stayed.

The model is precise. The inputs are not. And in workforce modelling, as in every other kind, precision without accuracy is not rigour — it is false confidence.

The decisions this distorts

This matters because the decisions built on this modelling are not small ones.

Restructuring decisions that remove cost from the wrong places. Hiring freezes that create capacity gaps in functions that are already under strain. Retention investments targeted at average attrition rates rather than the specific roles where departure is most expensive. Headcount approvals granted or withheld on the basis of cost data that does not reflect what the workforce actually delivers.

McKinsey’s 2025 HR Monitor found that only 12% of organisations are conducting strategic workforce planning with a three-year horizon. The other 88% are doing operational headcount forecasting. That gap is not a failure of ambition. It is a direct consequence of working from data that was never built for strategic use.

The question worth asking

The question Finance should be asking is not whether the numbers are correct. It is whether the data infrastructure is capable of producing correct numbers — and if it is not, which of the decisions made on top of it need to be revisited.

Most organisations do not ask that question. Not because the answer is comfortable, but because there is currently no clear path to asking it well.