Show the basis of each count
Keep employee HC, position FTE, authorized roles and management targets distinct rather than adding them together.
WORKFORCE RECONCILIATION
Stop arguing about which headcount number is right.
Different workforce totals can all be correct when they describe different things. HC Controller makes the comparison basis explicit: people, positions, authorization, organization and reporting perimeter, each with effective dates and scope rules.
For the controlling team
Built around your job, not another dashboard.
HR Controllers, Finance, HR operations, organizational planning and data-quality owners.
The problem
Why the numbers take too long to explain.
An HR system may report employees, a position ledger may include vacancies, a target file may express authorization and Finance may exclude a population. Forcing these sources into one unexplained number risks incorrect decisions.
With HC Controller
From the source to the decision.
Compare the same reporting scope
Respect country, legal entity, department, skill hierarchy, worker category, reporting perimeter and effective month.
Expose missing inputs
Show source files, unavailable mapping fields and unresolved exceptions. A missing employee link is not proof that a paid person has no job.
Preserve planned versus actual evidence
Position drill-down can explain a plan or scenario. Position-level actual occupancy needs a source that supports it.
Build a repeatable monthly method
Validate each authorized extract, keep rule definitions stable and archive versions for auditability.
Practical example
What the controller can investigate.
Illustrative example: an HR report lists 507 employees while a position plan lists 520 authorized roles. The difference of 13 could reflect vacancies, double assignments, timing, excluded worker groups or a mapping problem. A reconciliation requires evidence before selecting the reason.
Illustrative example only; not a validated customer result or a promise of processing speed.Availability and data scope
What is available, and what still requires verification.
Excel/CSV imports and the current comparison views enable initial checks. A complete cross-system transactional evidence ledger and automated two-way enterprise integrations are under development, not a currently certified capability.