Payroll Result

The gross-to-net record: what each worker was paid, component by component, per pay period. Committed results are kept forever in the tenant, and they are the only true source of what payroll actually cost.

RuleLand at the result-line grain, one row per worker, period, and pay component, with both the paid-in and earned-for periodsNeverextract YTD balances as facts. Accumulations are derived; land the lines and compute the balances yourself.

◆ What a result is— the run, the result, and the lines. The line is the grain everything else derives from.

Piece	What it is	Note
Pay group & period	Who gets calculated together, and for which slice of the calendar.	Periods differ per pay group; weekly and semi-monthly coexist. Reporting normalizes to months later, in the model.
Payroll result	One worker's gross-to-net for one period: earnings, then pre-tax deductions, taxes, post-tax deductions, to net.	Draft until the run commits; extract committed results only.
Result line	One pay component with its amount inside a result.	The atomic grain. Regular pay, overtime, a tax, a benefit deduction, an employer match: each is a line.
Pay component	The earning or deduction code a line carries.	Classified in the model as earning, employee deduction, or employer cost. The classification is the whole reporting layer.
Balances	Period, month-, quarter-, and year-to-date accumulations per component.	Derived from lines. The rulebar's Never: compute them in the warehouse where they are always consistent with the detail.

◆ Reporting traps— retro pay's two periods, off-cycle payments, and the employer costs gross-to-net does not show.

Trap	What goes wrong
Retro pay has two periods	A backdated raise is recalculated by the retro engine and paid in the current period for prior ones. Every line therefore has a paid-in period and an earned-for period, payroll's version of effective dating. Cash questions use paid-in; cost-of-labor questions use earned-for. Land both keys or you can answer only one.
Off-cycle payments	On-demand and manual payments happen outside scheduled runs. Period totals that read only scheduled runs understate cost; include every committed result regardless of run type.
Employer costs are separate	Gross-to-net is the worker's view. Employer taxes, benefit premiums, and retirement match are their own lines, and fully loaded cost is gross plus employer lines. A labor-cost report built on gross alone understates by the burden.
Component classification	Hundreds of tenant-specific codes reduce to three classes: earning, employee deduction, employer cost. Deductions are not costs; employer lines are. Classify once in dim_pay_component and every report inherits it.

◆ How we model it— fct_payroll_result at the line grain, and dim_pay_component, the small table that does the heavy lifting.

The fact lands one row per committed result line, with both period keys and the worker's organization assignments as of the earned-for period:

-- fct_payroll_result: the line grain, both periods, classified by the component dimension
SELECT r.worker_key,
       r.paid_in_period_key,
       r.earned_for_period_key,
       r.pay_component_key,
       r.cost_center_key,
       r.amount
FROM stg_payroll_result_line r
WHERE r.result_status = 'Committed'

dim_pay_component is where hundreds of codes become three answers. Sample rows:

component_code	component_name	class	in_gross	in_fully_loaded
REG	Regular Pay	Earning	Yes	Yes
OT_150	Overtime 1.5x	Earning	Yes	Yes
FED_WH	Federal Withholding	Employee deduction	No	No
ER_401K	Employer 401(k) Match	Employer cost	No	Yes

Gross sums the earning lines; fully loaded cost sums earnings plus employer costs; net is gross minus employee deductions. Three flags, every payroll metric. The cost_center key joins the mapped dimension, which is what makes the GL reconciliation one query. Sample values are illustrative, never client data.

Want payroll cost you can trust to the line?

We build the line-grain fact, both period keys, and the component classification, reconciled against Workday's own registers, and you own every line.

Talk to us

Terms on this page

payroll result: One worker's gross-to-net for one pay period. Committed results persist in the tenant.
result line: One pay component and amount inside a result. The atomic grain.
pay component: An earning or deduction code. Classified once: earning, employee deduction, employer cost.
gross-to-net: Earnings, minus pre-tax deductions, taxes, and post-tax deductions, to net pay.
fully loaded cost: Earnings plus employer costs. What labor actually costs.
retro pay: Recalculated prior periods paid now. Two period keys per line.
paid-in vs earned-for: The cash period versus the labor period. Land both.
off-cycle: On-demand or manual payments outside scheduled runs. Committed results all the same.
balance: A to-date accumulation per component. Derived in the warehouse, never extracted as fact.
pay group: Workers calculated together on one period schedule.