Workday Analytics Catalog

The reference for building customer-owned analytics on Workday, by module. People and financial data, accessed through RaaS, WQL, and the APIs, modeled as tables you own, with a daily worker snapshot the source system does not keep. The foundations are live; the people modules are rolling out.

Built on the Worker objectCustomer-ownedDates handled right

◆The spine, built once, used everywhere

Extraction patternLive

The reliable way out: RaaS, WQL, the APIs, and the new Data Cloud, compared, with the traps that break naive extracts.

The object modelLive

Where are the tables in Workday? There aren't any. Objects, instances, and data sources, translated into warehouse terms.

Effective datingLive

The two dates on every change, retro changes that rewrite the past, and how to rebuild history that stops drifting.

WorkerLive

The hub object: employees and contingent workers, the delivered data sources, the reporting traps, and the owned model.

Data sources & WQLLive

What a data source is, how to see its fields in your tenant, and copy-ready WQL queries.

Enterprise data modelLive

How the module stars share one worker, one org, one cost center, one calendar, with the schema diagrams.

Delivered vs ownedLive

Seven structural walls in delivered reporting, and what an owned model changes about each one.

Data CloudLive

The lake, the zero-copy share, and live query, with status as of August 2026 and what to build while you wait.

Calculated fieldsLive

Years of logic computed at runtime and never stored. Which paths carry it out, and the rebuild that upgrades it.

Integration securityLive

The read-only service account, the domain policies that trim silently, and the completeness check every run.

Surviving the refreshLive

Weekly tenant refreshes reset the account, schedules, and endpoint. The health-gated pipeline that expects them.

History before go-liveLive

Prior years arrive as profile text, not transactions. The reconstruction, with the seam kept honest.

Prism pricing realityLive

Capacity licensing, overages, and walled output, labeled honestly, beside the owned alternative.

The change ledgerLive

Deleted records vanish and there is no change feed. Snapshot diffing builds the audit trail.

◆People modules

Core HRLive

Four reports on two facts: headcount, movement, turnover, span of control. With the objects behind them and the module data model.

CompensationLive

Eleven pages complete to plan: ratios, mix, cycle and budget, payouts, promotions, the change ledger, and the reconciliation payroll confirms.

PayrollLive

The line-grain payroll fact, retro pay done right, and the GL reconciliation that joins Workday to the ERP.

AbsenceLive

Balances that derive instead of disagree, and a time-off liability finance can sign.

Time TrackingLive

Overtime as configured, paid hours from the payroll fact, and the pre-deadline approval control.

RecruitingLive

Time to fill with the clock stated, evergreen requisitions handled, and a funnel that ties to headcount.

Talent & PerformanceLive

Ratings as per-cycle rows on configured scales, completion with the chase list, distributions as the audit.

BenefitsLive

Elections, deductions, and the carrier invoice reconciled three ways, with the pre-tax audit built in.

Workday Financials, journals, supplier and customer accounts, follows the people modules on the same methodology.

RuleEvery page maps the report or object to what Workday actually exposes, with the model you own at the endNevertrust a single snapshot. Retro changes rewrite Workday's past silently. See the extraction pattern →

Want a working people module on your cloud in 10 days?

We build the worker dimension with full history, the reports, and the extract pipeline, reconciled against Workday, and you own the code.

Talk to us

Terms on this page

Worker: Workday's hub object, covering employees and contingent workers.
data source: The published set of objects and fields a report or WQL query reads.
RaaS: Report-as-a-Service, a custom report published as a URL you can call for the rows.
WQL: Workday Query Language, queries a data source over REST, with paging.
effective date: The date a change takes business effect.
retro change: A change entered now, effective in the past. It rewrites history behind your extract.
snapshot fact: A table capturing the state of every worker on each day or month. Workday does not keep it; you build it.
star schema: A report-friendly layout: one facts table with lookup tables around it.
customer-owned: The code and data model are yours. No vendor lock-in, no per-seat platform fee.
Data Cloud: Workday's new zero-copy share into Snowflake, Databricks, and others.