Finance and HR usually count different things on different dates. Finance means budgeted positions or FTE by cost center; HR means people by supervisory organization. Fix it by agreeing four definitions, one as-of rule (effective date at month end, using data entered by the close date) and a maintained map between cost centers, supervisory orgs and positions, then producing both views from the same governed table with an exceptions list instead of hand-reconciled Excel exports.
Every month the controller pulls headcount for the board pack from Workday Financials, HR pulls it from Workday HCM, and the two numbers differ. A day goes into reconciling line by line, and leadership still asks why cost per head moved.
Which headcount does each team mean?
Four numbers travel under the same word:
- Headcount: people employed on the date.
- FTE: the sum of scheduled hours as a share of full time.
- Filled positions: positions with an incumbent.
- Budgeted positions: positions in the plan, filled or not.
Finance usually reports positions or FTE because cost follows them. HR usually reports people. Label every report with the number it shows and keep the four side by side, so a difference is a definition, not an error.
Which date does the number use?
Workday records when a change takes effect and when it was entered. A termination effective 30 June but entered on 3 July is in June's corrected history and missing from a report run on 1 July.
Pick one rule: effective date at month end, using data as entered by the close date. Changes entered after close show up as next month's variance, with the reason, rather than silently restating a board number.
Who counts: contractors, leaves and second jobs?
Write down the treatment of contingent workers, people on leave, interns, workers with additional jobs and leavers who stay active until their final pay. Most mismatches trace to one of these. Each choice is defensible; the problem is making it differently in two places.
How do positions, cost centers and supervisory orgs line up?
HR organizes people by supervisory organization; Finance budgets by cost center. Positions connect the two, but the mapping drifts: a reorganization moves people while cost centers stay, a position is created without a cost center, a cost center closes with people still assigned.
Keep the map as a table someone owns, with effective dates, and report its exceptions every month: positions without a cost center, workers in an inactive organization, cost centers with no positions.
What can Workday do on its own?
Workday can do a lot of this inside the system, and some teams never need more.
- Composite and matrix reports can show positions and workers side by side for a period.
- Workday Prism Analytics can bring other data in and stage snapshots, with pricing by published rows and a daily refresh.
- Workday Adaptive Planning handles workforce planning and budget versus actual.
- OfficeConnect brings Workday Financials data into Excel with a live link, though it does not cover HCM.
These work well when the answer stays inside Workday. The board pack usually also needs payroll, the general ledger detail and plan data from other systems, which is where exports start.
How do you close without Excel exports?
Load Workday HCM and Financials, with their effective-dated history, into one governed place next to the other systems the board pack uses. Apply the four definitions and the as-of rule once. Both teams then read their view from the same table, and the reconciliation becomes a short exceptions report.
Databasin does this for finance and HR teams on Workday. Its connector extracts the full effective-dated history, the shared definitions live in one governed layer, and the month-end exceptions list can run on a schedule and arrive by email or in Teams. People can ask follow-up questions in plain English and check the SQL. Our team implements the connection, the org map and the first reconciled close with your finance and HR staff.
Example: one month's difference, explained
An illustrative reconciliation for 31 March:
| Item | Effect on the gap | Treatment agreed |
|---|---|---|
| Finance counts 412 filled positions | Starting point | Positions view |
| Four workers hold two positions | People count is four lower | Count people once in headcount |
| Three contingent workers in HR's count | People count is three higher | Report contingent workers separately |
| Two terminations entered after close | Corrected history differs from the issued number | Show as April variance |
| One position without a cost center | Missing from Finance's department view | Exceptions list, fixed in Workday |
Checks for a headcount both teams sign
- Agree the four definitionsHeadcount, FTE, filled positions and budgeted positions, each labelled on every report.
- Fix the as-of ruleEffective date at month end, data as entered by close, late changes as next month's variance.
- Own the org mapCost center, supervisory org and position links with an owner and effective dates.
- Report exceptions, not totalsClose on the exceptions list and leave the totals to the shared table.
Sources
Workday, How to solve the challenges of headcount reconciliation, accessed 2026 · blog.workday.com
Workday, Concept: Effective and Entry Dates, accessed 2026 · doc.workday.com
Talk about your month-end close
We can walk through where your headcount numbers diverge today and how a shared table would change the close.