BAMML Executive Insights

Your HR Report and Your Management Accounts Are Describing Two Different Companies

Industry: Cross-sector C-suite & Board · Primary pillar: Executive Decision Intelligence · Secondary: Workforce Governance; Financial Governance

5 min read

Two reports land on the same table at the same meeting.

The management accounts describe an organisation made of revenue, cost, margin and variance. It has departments, and the departments have budgets, and some of them are over.

The HR report describes an organisation made of headcount, vacancies, absence, turnover and disciplinary cases. It has departments too, and some of them have problems.

They are describing the same company. They almost never reconcile — and the executive is expected to integrate them mentally, in real time, while the meeting moves on.

What is actually happening

The two reports were built by different functions, for different purposes, to different conventions.

A finance manager working on a spreadsheet and an HR manager working on a separate report, in offices on either side of a glass wall, each focused on their own screen

They often use different periods. They frequently count employees differently — permanent, temporary, contractor, fixed-term all move between categories depending on who is counting and why. They organise around different structures, because the finance cost-centre map and the HR reporting line map are rarely identical. And they define almost nothing in common.

Each is internally coherent. Neither is wrong. They simply do not join.

So when the finance report shows labour cost up in a department, and the HR report shows absence up in what may or may not be the same department, no mechanism exists to ask whether those two facts are related. The question would have to be asked by someone, and it belongs to neither function.

Why it matters

The questions that matter most sit precisely in the gap between the two reports. Which means they belong to nobody, and get asked by nobody.

An executive at a boardroom table looking between a financial report and a workforce report, thoughtful, with colleagues in the background

Consider what the executive cannot currently answer without commissioning special work:

What did absence cost us last quarter? HR has the rate. Finance has the cost base. Nobody multiplies.

Is our overtime a demand problem or a staffing problem? Payroll shows the overtime. HR shows the vacancies. The relationship between them is never reported.

Which departments have labour cost rising faster than output? Finance has the cost, operations has the output, and the two are not presented together at departmental level.

Are our highest-turnover roles also our highest-overtime roles? Both facts exist. Nobody has ever put them in the same table.

Each of these is answerable from data the organisation already holds. None of them is answered, because answering requires joining two reports that were never designed to join — and the effort of doing it manually means it happens once, for a specific crisis, and then stops.

The Integrated View

The question Where half the answer lives Where the other half lives Who currently asks
What did absence cost? HR — absence rate Finance — cost per employee day Nobody
Is overtime structural? Payroll — overtime hours HR — vacancies and turnover Nobody
Which department is getting more expensive per unit? Finance — departmental cost Operations — output Nobody
Are we losing our most expensive-to-replace people? HR — turnover by role Finance — replacement cost Nobody
Is our workforce risk financial yet? HR — cases, absence, IR Finance — provisions, variance Nobody

That final column is the argument of this article. The failure is not that anyone is doing their job badly. Both functions are producing exactly what they were asked for. The failure is that nobody was ever made accountable for the join.

What this looks like when it is fixed

One BAMML client, an industrial operation, carried high overtime, high absenteeism, high sick-leave records, workplace accidents and incidents of fuel theft. Each was owned by somebody. Each was reported somewhere. For years they were treated as five unrelated problems.

A finance manager and an HR manager sitting side by side at one screen, both pointing at a combined view of financial and workforce charts

They were not five problems. They were one system, and it was visible the moment somebody looked at the five together.

Aligning individual and team performance to the organisation's actual targets, and enforcing consistent implementation of policies that already existed, moved all five: staff turnover fell below 2%, overtime reduced to public holidays only, and the operation went more than a year with no reported accidents.

Nothing in that engagement required data the client did not already have. What it required was one view.

What to do on Monday

Do not commission a reporting project. Ask three questions and see what happens.

  1. What did absence cost us last quarter, in rands?
  2. Are the departments with the highest overtime the same departments with the highest vacancies?
  3. Which three roles are most expensive to replace, and what is our turnover in those roles?

Then observe the response. If the answers arrive quickly, your reporting already joins and this article is not about you. If they require a special exercise, two people, and a week — that is the finding, and it is a finding about your executive information rather than about your people or your costs.

The organisation described in your management accounts and the organisation described in your HR report are the same organisation. Until your reporting says so, you are managing two companies, and neither of them exists.

Share this insight LinkedIn Email Book a conversation

← All Executive Insights