HRYEUS
ForumExpertsArticlesKnowledgeJobs

Spaces

  • All8
  • ORAOracle HCM2
  • WKDWorkday1
  • SFCSAP SuccessFactors1
  • DWBDarwinbox1
  • SMBBambooHR & SMB0
  • PAYPayroll Systems1
  • INTIntegrations & Data1
  • GENGeneral HRIS1

Forum

Start a thread
ALLORAWKDSFCDWBSMBPAYINTGEN
ALLTHREADS

About this community

A practitioner network for the experts behind Oracle HCM, Workday, SuccessFactors, Darwinbox and more — real questions, real answers, no vendor spin.

13 members joined

Browse experts
ARTICLES
TF
Tomás FerreiraFounding Member
2 months ago·INTIntegrations & Data

Headcount drift between core HR and the BI warehouse — 30-40 heads every month

Finance and HR argue about headcount every month because the number in the BI warehouse is 30-40 off from the core HR system. The warehouse loads from a nightly extract. When I reconcile, the drift is always a mix of: employees on unpaid leave, employees pending a future-dated termination, and a few contingent workers. Everyone counts these differently. Before I go define 'headcount' for the fourth time — is there a standard the GCC crowd actually agrees on?

LikeFollow3 replies
  • KH

    Karim HaddadFounding Member There's no universal standard, but the pattern that ends the argument: publish three numbers, not one. Active headcount (paid + on paid leave), total workforce (adds unpaid leave + notice period), and FTE. Finance picks which one they budget against and you stop reconciling to a moving target.

  • DN

    Deepa NairFounding Member And put future-dated terminations in their own bucket until the date passes. The warehouse extract should snapshot as-of the run date and ignore anything effective in the future, otherwise the number changes retroactively when you look at last month.

  • View all 3 replies →
Sign in to reply.