Skip to content
KiweelyKiweelyKiweely

How to Build a Workday Payroll Summary Report by Worker and Earning Code Over Any Date Range

Build custom date-range payroll summary reports as a Matrix Report on the indexed Payroll Result Lines data source rather than Worker or Payroll Results. Group rows by Worker and Pay Component, sum Result Line Amount, and filter via an indexed payment-date data source filter.

  • Checked against Workday on
  • Applies to Workday Payroll
  • 7 min read
  • Published
  • By Kiweely
On this page

To aggregate earnings, deductions, and hours by worker across an arbitrary date range, build a Matrix custom report on the indexed Payroll Result Lines data source—not an Advanced Report on Worker or Payroll Results. Grouping Payroll Result Line instances by Worker and Pay Component Code while summing Result Line Amount lets Workday aggregate millions of paycheck lines in seconds without writing a separate calculated field for each earning code.

Why Do Standard Payroll Registers and Worker-Based Reports Fall Short?

Workday ships strong period-based payroll reports—including Pay Calculation Results - Earning Register, Pay Calculation Results - Deduction Register, Payroll Register by Period, and Pay Balance Summary—but each carries structural constraints when Finance or external auditors ask for worker-by-code totals across non-standard date windows (such as an off-calendar fiscal year, a collective bargaining look-back window, or a six-month M&A diligence period).

Reporting Approach Primary Business Object What Goes Wrong Over Arbitrary Date Ranges
Reporting ApproachStandard Pay Balance Summary Primary Business ObjectWorker / Balance Period What Goes Wrong Over Arbitrary Date RangesBound to preconfigured balance periods (MTD, QTD, YTD); cannot sum arbitrary day-to-day check date spans on demand.
Reporting ApproachCustom Advanced Report on Worker Primary Business ObjectWorker What Goes Wrong Over Arbitrary Date RangesRequires one Sum Related Instances calculated field per earning or deduction code; times out across large headcounts.
Reporting ApproachCustom Report on Payroll Results Primary Business ObjectPayroll Result What Goes Wrong Over Arbitrary Date RangesReturns one row per paycheck header rather than per earning line, preventing native row-level grouping by earning code.
Reporting ApproachMatrix Report on Payroll Result Lines Primary Business ObjectPayroll Result Line What Goes Wrong Over Arbitrary Date RangesRecommended: Indexed data source with one instance per pay component line; groups and sums any date range natively.

Because Payroll Result Lines is an indexed data source, Workday evaluates date ranges, pay groups, and result statuses inside the search index before aggregating rows. That is the same architectural guidance Workday gives for high-volume custom pay balance reporting, and it prevents the 30-second worklet timeout and multi-minute background queues discussed in custom report performance tuning.

Which Data Source Filter Should You Pick: Payment Date vs. Period End Date?

Payroll Result Lines requires a built-in Data Source Filter (filterIsRequired is enforced on the data source). Selecting the wrong filter is the number-one reason a custom summary report disagrees with either General Ledger journals or quarterly tax filings.

Choose between the two primary date-range filters based on your reconciliation target:

  1. Tax, W-2, 401(k) Census, and Cash Audits (Payment Date): Select Pay Calculation Result Lines for Organizations, Periods, Pay Groups, Workers, Statuses, Pay Calculations, On/Off cycle Types, Payment Date range and Process Entry range. This filter exposes start and end prompts for Payment Date, Statuses, Pay Groups, Workers, Pay Calculations (individual earnings and deductions), and On/Off-Cycle Types. Constructive receipt rules govern US W-2s and 941s: a December 16–31 pay period paid on January 3 belongs in the new tax year’s Payment Date range.
  2. Accrual Accounting and Labor Costing Audits (Period End Date): Select Earnings/Deductions for Organization, Worker, and Period or Date Range (As of Sub Period End Date). This filter selects lines by when the hours or salary were earned rather than when settlement paid the check.

Watch the Midnight (`00:00:00`) Cutoff Trap on Processed-By Prompts

If you use a balance filter or add Include Results Processed By (or an As Of timestamp) on the Prompts tab, Workday defaults the time portion to 00:00:00 (start of day). Entering 2026-12-31 silently drops every payroll completed during business hours on December 31. On the Prompts tab, set Default Value for Include Results Processed By to Today (End of Day) (23:59:59) or Equal to As of Date.

Step-by-Step: Configure the Matrix Report in Create Custom Report

Before starting, confirm you hold the Custom Report Creation domain in the System functional area, and that everyone who will run the report holds Reports: Pay Calculation Results (Reports: Indexed Data Source Filters) (and Reports: Pay Calculation Results for Pay Group (Results)) in the Core Payroll or country-specific Payroll functional area.

Run Create Custom Report and enter this configuration:

text
Report Name:         CR - Payroll Summary by Worker and Pay Component (Date Range)
Report Type:         Matrix
Optimized for Perf:  Checked (keeps only indexed fields available for fast grouping)
Data Source:         Payroll Result Lines
Data Source Filter:  Pay Calculation Result Lines for Organizations, Periods,
                     Pay Groups, Workers, Statuses, Pay Calculations,
                     On/Off cycle Types, Payment Date range and Process Entry range

1. Configure Row and Column Groupings on the Matrix Tab

A Workday Matrix Report only allows fields that live directly on the Primary Business Object (Payroll Result Line). Configure the Matrix tab according to how your stakeholders consume the output:

  • Flat Audit Table (Best for Excel Pivots and Census Feeds): Add Worker, Employee ID, Pay Component Category (separates Earnings from Employee Deductions and Employer Contributions), and Pay Component Code (or Pay Component Name) under Row Grouping, leaving Column Grouping empty. Increase Maximum Number of Rows well past your worker-by-code row count so Workday does not collapse rows into Other.
  • Crosstab View (Workers Down, Earning Codes Across): Place Worker in Row Grouping and Pay Component Code (or Earning) in Column Grouping. Raise Maximum Number of Columns above your active earning code count; otherwise Workday displays only the top N codes and dumps the rest into an Other column on the far right.

If you need to group or filter by a worker attribute that is not delivered directly on Payroll Result Line—such as a custom Supervisory Organization attribute or Compensation Grade—create a single Lookup Related Value (LRV) calculated field on Payroll Result Line using Worker as the Lookup Field. Keep calculated fields on Payroll Result Line to a minimum so the Indexed checkbox on your Matrix grouping row stays selected.

2. Configure Summarization Fields and Drill-Down Columns

In the Define the Field(s) to Summarize grid on the Matrix tab, add:

  1. Summarization Type: Sum | Summarization Field: Result Line Amount (or Result Line Amount in USD if your report spans multiple countries and currencies—never enable Show Currency Symbol on Result Line Amount across mixed currencies, or Workday outputs *Invalid* in cells combining USD and CAD/GBP).
  2. Summarization Type: Sum | Summarization Field: Total Hours Related Calculation (or Hours Prorated Related Calculation for Result Line when auditing hourly and overtime codes).

On the Drill Down tab, add Payroll Result, Period, Coverage or Sub-Period End Date, Run Category, and Payroll Worktags. When an analyst clicks any worker’s summarized bonus or overtime total, Workday opens the exact on-cycle, off-cycle, or retro pay result lines that produced that sum.

3. Lock the Statuses Prompt Default to Completed

On the Prompts tab, click Populate Undefined Prompt Defaults and inspect the Statuses prompt:

  • Set Default Type to Specify default value and select Completed.
  • Leaving Statuses blank pulls In Progress, Requires Recalculation, or Held pay calculation lines into your totals whenever an open pay run is underway in the tenant.
  • Optionally pre-populate Pay Calculations if the report is dedicated to a specific set of earnings (such as W-2 bonus codes or 401(k)-eligible earnings), or leave it open as a user prompt for ad-hoc queries.

Can You Query the Same Aggregation Directly with WQL?

If you are building a Workday Extend app, Orchestration, or external reconciliation check via the Workday Query Language REST endpoint rather than the report UI, query the payrollResultLines data source alias directly. Because payrollResultLines requires a data source filter, omitting PARAMETERS fails validation:

Fails
SELECT worker, payComponentCode, SUM(resultLineAmount) AS totalAmount
FROM payrollResultLines
WHERE cf_PayComponentIsEarning = true
GROUP BY worker, payComponentCode

Pass the indexed data source filter alias inside PARAMETERS (or bind your custom report’s filter parameters) so the query engine scopes the index scan before grouping:

Works
SELECT worker,
       cf_EmployeeID AS employeeId,
       payComponentCode,
       payComponentName,
       SUM(resultLineAmount) AS totalAmount,
       SUM(totalHoursRelatedCalculation) AS totalHours
FROM payrollResultLines (
  dataSourceFilter = payCalculationResultLinesForOranizationsPeriodsPayGroupsWorkersStatusesPayCalculationsOnOffCycleTypesPaymentDateRangeAndProcessEntryRange,
  startPaymentDate = '2026-01-01',
  endPaymentDate = '2026-06-30'
)
WHERE cf_PeriodResultLineIsNotCompleted = false
  AND cf_PayComponentIsEarning = true
GROUP BY worker, cf_EmployeeID, payComponentCode, payComponentName

How Do You Verify the Report Matches Workday Payroll to the Penny?

Before sharing the custom report with Finance or Payroll, run a two-step tie-out in Sandbox or Implementation:

  1. Single-Period Tie-Out: Run your new Matrix Report for a single closed pay group and payment date, filtered to Completed status. Run the delivered Pay Calculation Results - Earning Register and Pay Calculation Results - Deduction Register for that exact same pay group and period. The grand totals by earning code and worker must match to the cent.
  2. Retro and Off-Cycle Check: Pick one worker who had a prior-period retroactive pay adjustment or an off-cycle manual check/reversal during your date window. Drill into their Matrix cell and confirm both the on-cycle line and the off-cycle/reversal adjustment appear with the expected signs so net cash and YTD wage accumulators reconcile cleanly.

If you need to spin up multi-period payroll reconciliation reports, trace which Pay Component Groups feed a specific W-2 box, or promote worker worktags onto Payroll Result Line without trial-and-error in the report writer, Kiweely Vine inspects your tenant’s live Payroll Result Lines metadata and builds the custom report and calculated fields with your explicit approval.

Frequently asked questions

Why should I use Payroll Result Lines instead of Payroll Results or Worker for a payroll summary report?

Payroll Result Lines is an indexed report data source whose primary business object is Payroll Result Line, returning one row per earning or deduction line. Reporting from Worker or Payroll Results forces Workday to traverse one-to-many relationships across dozens of pay periods and requires separate Sum Related Instances calculated fields for every earning code.

Should I filter a Workday payroll summary report by Payment Date or Period End Date?

Use Payment Date whenever reconciling to W-2s, Form 941 quarterly tax filings, or cash disbursements, because tax authorities recognize wages on constructive receipt (check date). Use Sub-Period End Date when reconciling accrued labor expenses to general ledger accounting periods.

Why is my custom pay balance report missing payroll results completed on the final day of my date range?

Workday defaults As Of and Include Results Processed By prompts to the beginning of the day (00:00:00), which excludes any payroll completed later that calendar day. Set the Default Value on Include Results Processed By to Today (End of Day) (23:59:59) or Equal to As of Date.

Why did Workday collapse half of my earning codes into an Other column on my Matrix Report?

Matrix Reports enforce a Maximum Number of Columns and Maximum Number of Rows setting on the Matrix tab. Any distinct Pay Component values beyond that limit roll into an Other bucket. Increase Maximum Number of Columns or move Pay Component Code into Row Grouping for flat spreadsheet exports.

Sources checked

Related guides

All guides

Let Workday check the work.

Kiweely writes WQL and builds orchestrations in your own tenant, and Workday, not Kiweely, says whether they passed.

Get the next guide in your inbox.

One email a month with new guides and one Extend tip. Nothing else.

We’ll email you once to confirm. Unsubscribe in one click from any issue.