Workday HCM connects the worker to positions or jobs, job profiles, organizations, compensation and locations, and keeps effective dates for changes. Reports and Workday Query Language read permitted data sources and fields. Build the warehouse around those relationships and their history, so each report uses the assignments valid on the date it measures.
HR and finance have different headcount totals for the board pack. HR ran the report in Workday, finance queried the warehouse, and both selected the same date. To resolve the difference, they need to compare the population, the department grouping and the dated assignments behind each total.
To explain the difference, follow a worker through the Workday data structure. Check the assignment, the organization and the dates used in each report. Once you can see where each worker was counted, you can find the rows behind the difference.
Workday stores HCM data as related business objects
An extract of workers needs related records to answer questions about assignments, pay and management. Position, Compensation and Organization supply that detail. A report that follows a different link from Worker can place the same person in a different group.
Workday Query Language, or WQL, queries data sources and fields with SQL-like syntax. The syntax will be familiar to a SQL developer. The returned fields still need mapping to their objects before the developer can decide how to join them in warehouse tables.
The account running a WQL query can use only the data sources and fields it has permission to see. If a field is absent, check that access before interpreting the result. The warehouse cannot infer a business value from a field the caller could not read.
In a headcount report, compare the route from worker to assignment to organization with the route used in Workday. A missing relationship and an excluded worker need different fixes. The comparison needs to show which of those happened before anyone changes the count.
The worker sits at the centre of HCM
The worker identifies the person being counted. Related objects supply the title, management assignment and pay information used to describe that person. Keep the source object visible when choosing those fields for a report.
Workday's Human_Resources service exposes workers, job profiles, job families, organizations and locations. Its employee operations also cover employment and compensation information. The Staffing service exposes positions and identifies the worker occupying a filled position under position management.
For warehouse design, record the object behind each field before choosing a table. A worker and a position answer different questions. The worker identifies the person in the report's population, while the position describes an assignment that the staffing model manages.
Use the objects below to trace where a headcount report gets its fields. The links need to match the tenant's organization structure. The last column identifies the choice that affects how each object contributes to the report.
| Object | What it holds | Links to | Watch for |
|---|---|---|---|
| Worker | Employee or contingent worker records | Assignments and organizations | Population and status |
| Position or job | The assignment a worker fills | Worker and organization | Staffing model |
| Job profile | Job classification and family | Worker assignment | Required job detail |
| Supervisory organization | Management grouping | Workers and positions | Reporting hierarchy |
| Cost center, company and region | Finance organization groupings | Worker assignments and Financials | Organization type |
| Location | Location reference records | Worker assignments | Location used by the measure |
| Compensation | Pay assignments | Worker | Effective dates |
Each worker belongs to several organization hierarchies
A request for headcount by department needs a named organization hierarchy before it needs a count. The management line and finance's allocation of workers can group the same people differently.
Workday's Staffing service returns organizations by type, including supervisory organizations. The supervisory organization supplies the management grouping. Cost centers, companies and regions supply other ways to group the worker's assignment for finance and organizational reporting.
A report should identify which of these groupings it uses. If HR groups workers by supervisory organization while finance groups them by cost center, matching the totals alone does not establish that the reports agree. The rows can represent different questions even when the overall population matches.
Organizations, locations and currencies provide reference records that HCM and Financials can share. When a measure combines the two, its join needs the relevant organization. Keep that type visible in the warehouse so the report writer can distinguish the management grouping from finance's grouping.
Your staffing model decides what a position means
A vacancy report needs to know how the supervisory organization manages its seats. Check the staffing model before interpreting the position records. Without that information, a missing record cannot reliably identify an open seat.
Workday's Staffing documentation names position management, job management and headcount management. Its Get_Positions operation returns position management positions and identifies the worker when a position is filled. The Create_Position operation creates or opens a position for a supervisory organization using position management.
That gives a warehouse designer a specific meaning for the records returned by Get_Positions. It does not establish that the same result represents every staffing model. Keep the organization's staffing model alongside the decision about how to represent positions and vacancies.
For a headcount measure, follow the worker's assignment under that model. For a vacancy measure, establish which source records describe the available seats. These questions need separate answers before a position table can support both reports.
Effective dates turn every link into a timeline
A worker can change manager, salary, grade or cost center while retaining the same identity. A historical report needs the assignment valid in its reporting period, including changes entered later with an earlier effective date.
A current-values load gives the warehouse today's manager and salary. Applying those fields to an earlier period can leave the worker in the count but put that person under the wrong manager, or associate the count with the wrong pay value.
Keep the effective dates with the relationships that can change. A quarter-end count needs the worker's organization on the quarter-end date. A current organization field cannot supply that answer merely because the worker identifier matches.
The distinction between effective dates, entry dates and later corrections belongs in the historical reporting rules. The Workday reporting history guide explains those rules. For the data model, the essential requirement is to preserve dated versions so the report can choose the intended assignment.
A warehouse model rebuilds the links as dimensions
A worker dimension needs dated versions, as do the dimensions for positions, job profiles and organization hierarchies. Headcount and movement facts use those dates when they join. This lets the report retrieve the assignment that belonged to the worker in the period being measured.
With a Type 2 slowly changing dimension, a changed assignment produces another dated version. Earlier versions remain available. When the report runs, it resolves the as-of value against those dates and can recover the assignment used in an earlier period.
Keep the management and finance hierarchies in separate organization dimensions. A headcount fact can then select the supervisory organization and cost center that were valid together. Someone reading the query can follow both the grouping and the date rule.
Calculated fields require their own review. Many contain business logic that cannot cross object boundaries or be used outside Workday. Extract the fields available outside Workday and rebuild the remaining logic in the prepared tables. Compare the resulting measure with Workday at worker level before treating an equal grand total as agreement.
Databasin maps the Workday model as it extracts
Our native connector follows primary and related business objects and preserves their effective-dated history. Our team builds the joins and calculated-field logic that turn those records into measures finance and HR can use.
The connector covers 39 Workday feeds across HCM, Financial Management, Resource Management and Higher Education, with a Workday semantic layer included. It lands the prepared data in your lakehouse, Databricks, Snowflake or Fabric.
The connector keeps history as Type 2 versions back to Workday go-live, subject to access to those historical records. Approved Workday permissions determine which records it can read. Our team rebuilds calculated fields that cannot be extracted and checks the resulting measures against Workday.
The technical Workday page explains the connector's model and history. The Workday integration page covers its scope, while the extraction guide covers the methods for getting records out. Together, they connect the model described here to the route that supplies it.
Example: headcount by supervisory organization at quarter end
This illustrative headcount report follows workers through their assignments to count them by supervisory organization and cost center on 30 September.
| Step | Workday objects | Warehouse table |
|---|---|---|
| Pick the population | Worker active on 30 September | Worker dimension valid on the date |
| Place each worker | Position or job and supervisory organization on the date | Position and supervisory organization dimensions |
| Add finance's view | Cost center assignment on the date | Cost center dimension |
| Add job detail | Job profile and job family | Job profile dimension |
| Count | Headcount by supervisory organization and cost center | Headcount fact |
| Check | Workday headcount report for the same date | Reconciliation by worker |
The joins must all use the versions valid on 30 September to match Workday. Checking the workers and their assignments explains any difference behind the total.
Five checks before you model Workday
- Confirm each organization's staffing modelEstablish how each supervisory organization manages staffing before treating its positions and vacancies as equivalent records in the warehouse.
- Choose the hierarchy for each reportAgree whether the report groups workers by supervisory organization, cost center, company or region, and preserve that choice in its joins.
- List the objects each measure needsTrace each measure from Worker to its related objects so the model includes the assignments and reference records it uses.
- Find the calculated fields that stay in WorkdayIdentify which calculated fields can be extracted and which require rebuilt logic, then compare the resulting measures with Workday.
- Decide how much history you needSpecify the reporting dates the model must answer and confirm access to the historical assignments needed for those dates.
Sources
Workday, Human_Resources web service v45.0, 2026 · community.workday.com/sites/default/files/file-hosting/productionapi/Human_Resources/v45.0/Human_Resources.html
Workday, Staffing web service v45.0, 2026 · community.workday.com/sites/default/files/file-hosting/productionapi/Staffing/v45.0/Staffing.html
Workday, Concept: Workday Query Language, 2026 · developer.workday.com/doc/GUID-6546152a-bcf0-447d-8d64-230f9e2ac291-enHYPHENus.md
Plan your Workday data model with us
Talk with us about the headcount and cost reports your team needs, including questions about earlier periods. We can show the model in a working example and discuss how we would implement it on your platform.