Ask any HR director how many people work at their company and you’ll get one of two answers: a confident number that turns out to be three months stale, or an honest “let me check.” Headcount — the single most fundamental workforce metric — has been surprisingly hard to get right in most ERP systems. Not because it’s technically difficult, but because nobody built a proper report for it. Odoo 20 fixes that with a headcount analytics report baked directly into the Payroll module.
A Number That Moves and a Report That Follows
The headcount report tracks workforce size over time, which is the key phrase. Static headcounts are easy — count the active employees on any given day. What’s hard, and what matters for planning, is seeing how that number changes. When did the engineering team grow from twelve to twenty? Did the sales departures in Q2 actually get backfilled? Is the operations team still growing at the rate the budget assumed?
The report answers these questions with both graph and pivot views. The graph view gives you the visual trend line that executives want in quarterly reviews. The pivot view gives you the raw numbers that finance needs for cost modeling. Same data, two presentations, no export-to-Excel step in between.
Filters That Match How People Actually Think About Teams
You can slice the headcount by department, job position, and contract type — which are the three axes that HR teams actually use when they think about workforce composition. Department tells you where people sit organizationally. Job position tells you what they do. Contract type tells you how they’re employed: full-time, part-time, fixed-term, freelance.
That last filter is more important than it might seem. A company with 200 employees and 50 contractors looks very different from one with 250 full-time staff, even though the total headcount is the same. The cost structure is different, the management overhead is different, and the planning assumptions are different. Being able to split these out in a single report without building a custom query is the kind of thing that saves an HR analyst half a day every month.
New Hires Versus Departures: The Number Nobody Tracks Well
The report surfaces month-over-month changes, which means you can finally see net headcount movement without manually comparing two snapshots. How many people joined this month? How many left? What’s the net? These are questions that every people leader asks regularly and that most organizations answer by pulling data into a spreadsheet and doing the subtraction themselves.
Having this built into payroll specifically is a smart architectural choice. Payroll knows exactly who gets paid and when. It knows start dates and end dates with precision that HR systems sometimes lack, because payroll has to be right — the alternative is paying someone who left or not paying someone who started. Anchoring the headcount report to payroll data means the numbers have the same level of accuracy that auditors expect.
The Boring Metric That Drives Everything Else
Headcount isn’t glamorous. It doesn’t have the emotional pull of engagement scores or the strategic weight of revenue per employee. But it’s the denominator in almost every other workforce metric. Turnover rate? You need headcount. Cost per employee? Headcount. Manager span of control? Headcount by reporting line. Training budget per capita? Headcount again.
When the baseline number lives in a proper report with time-series tracking and dimension filtering, all of those derived metrics become possible without a data warehouse. That’s the real value of this addition — not just the headcount report itself, but every analysis it enables downstream. For a company running its entire HR stack on Odoo, this closes one of the last gaps between “we use an ERP” and “we actually know what’s happening in our workforce.”