Skip to content
AnrilX
All SAP modules
HCM

Human Capital

Where overtime is quietly standing in for headcount

Headcount, time and attendance, including the patterns that only show up when you compare one period against another.

See it answer one of these

Ask it

Questions you can ask on day one

Asked in plain language. Each answer prints the SAP entity, field and period it was computed from, underneath the figure.

  • “Where is overtime quietly standing in for headcount?”
  • “Which teams are carrying the most unplanned absence?”
  • “How has headcount moved against plan?”
  • “Which units have had a vacancy open longest?”
  • “How has overtime moved quarter on quarter, by unit?”
  • “What proportion of hours this period were overtime?”

What it reads

The people objects behind an answer

Organisational structure

Units, positions and reporting lines: the shape a headcount figure has to be grouped by to mean anything.

Headcount

Positions filled and vacant over time, against plan, by organisational unit.

Time and attendance

Hours recorded, including overtime, by employee group and period.

Absence records

Planned and unplanned absence, by type, which is what separates a staffing pattern from a seasonal one.

Employee master

The attributes that make a figure groupable: employee group, subgroup, cost centre assignment.

Why it is hard

What no standard report does for you

A staffing gap looks like a cost line

A team that is one person short does not appear as a vacancy for long. It appears as overtime, spread across several people and several periods, which is a cost figure rather than a staffing one, so it is reviewed by whoever owns the budget rather than whoever owns the hiring.

Structure changes underneath the numbers

Organisational units are reorganised, and a comparison across periods has to survive that. A figure grouped by a unit that did not exist last year is not a comparison, it is two different questions on one chart.

Absence is only meaningful against a baseline

An absolute number says nothing. The signal is the comparison (against the team's own previous periods, or against comparable units), which nothing produces automatically.

A staffing problem wearing a cost problem’s clothes

A team that is a person short rarely shows up as a vacancy for long. It shows up as overtime: distributed across several people, across several periods, none of it individually remarkable.

By the time it is visible it is a cost line, which means it gets reviewed by whoever owns the budget rather than whoever owns the hiring. The question that would surface it (overtime as a share of hours, by unit, compared against the same unit six months ago) is a real query that somebody has to sit down and write.

Comparisons have to survive a reorganisation

Organisational structures change, and most period-over-period people reporting quietly ignores that. A unit is merged, a team is renamed, and the chart draws a line across both as if they were the same thing.

AnrilX reports when a comparison spans that kind of change rather than presenting it as a trend. It is the same discipline applied everywhere else on the platform: a figure that is wrong in a way the reader cannot see is worse than no figure.

Aggregate by default

Everything here is grouped (by unit, by employee group, by period) and bounded by the SAP authorisations the person asking already has. A question about data somebody cannot see returns nothing, rather than a figure assembled from rows they were never meant to read.

One of these questions, answered

Where is overtime quietly standing in for headcount?

Five teams have run above 15% overtime for six consecutive months. Packing at plant 1000 is the clearest: 8,940 overtime hours this year, which is 4.6 full-time equivalents being paid at a premium against an establishment that has not moved since 2024.

Team Overtime · as FTE
Packing · plant 1000 8,940 hrs · 4.6 FTE
Inbound · plant 1000 5,120 hrs · 2.6 FTE
Despatch · plant 1200 3,880 hrs · 2.0 FTE

Source: A_TimeSheetEntry and I_WorkforcePerson · overtime hours by OrganizationalUnit against contracted hours · converted at 1,950 hours per FTE · rolling 12 months

Assumed: overtime means hours booked to premium wage types, not hours over a nominal day. Which wage types those are is your configuration, and the list is shown so a different definition can be asked for.

Where it stops

What it will not answer here

The limits particular to this module. Worth knowing before a pilot rather than during one.

  • This is aggregate reporting. Answers are grouped rather than individual, and what any person can see is bounded by their own SAP authorisations.

  • Where a comparison spans an organisational change, the answer says so rather than presenting two different structures as one trend.

  • Overtime, absence and turnover are reported as the payroll and time data record them. Why a pattern exists is a judgement about a team that the platform does not make for you.

Questions people ask us

Is this reporting on individuals?

It answers grouped questions: by unit, employee group, period. And it is bounded by your own SAP authorisations, so a question about data you cannot see returns nothing rather than a leak.

Can it compare across periods if we reorganised?

It will tell you when a comparison spans an organisational change. Presenting two different structures as a single trend is the failure worth avoiding here, because the chart looks entirely normal.

What can it actually show us?

Headcount against plan, vacancy ageing, overtime as a share of hours, absence by type, each grouped the way your organisation is actually structured, with the source of every figure printed underneath.

Bring the question your reports cannot answer

Thirty minutes against a live SAP system we provide: no access to yours, nothing to set up. If it cannot answer, you find that out in half an hour rather than three months into a pilot.