• 19 Aug 2026

Oracle HCM Benefits Paid Report – Canada

When a legacy payroll report is retired during a PeopleSoft-to-Oracle Fusion HCM transition, replacing the file is only part of the requirement. Payroll and benefits teams also need to preserve the calculations, employee-level detail, grouping structure, control totals, and review process that support recurring reconciliation.

DataTerrain developed a customized Oracle HCM Benefits Paid Report - Canada to recreate the core reporting requirements of the PeopleSoft PAY021CN Benefits Register in Oracle Fusion HCM. The report provides employee-level taxable and non-taxable benefit amounts, benefit-related taxes, calculated benefit base, month-to-date (MTD), quarter-to-date (QTD), and year-to-date (YTD) values, together with multi-level totals for reconciliation and audit review.

The Benefits Reporting Challenge

A Canadian enterprise transitioning payroll reporting from PeopleSoft to Oracle Fusion HCM needed to maintain a familiar benefits register after the retirement of the PeopleSoft PAY021CN report.

The existing process depended on the PAY021CN Benefits Register to review benefit amounts, benefit-related taxes, accumulated balances, and reconciliation totals across employees and organizational structures.

The replacement report needed to provide the same practical reporting capability using Oracle Fusion HCM payroll, benefits, element, and balance data.

Without a purpose-built report, the review process could require:

• Extracting payroll and benefit balances for the required pay period and pay group
• Identifying the applicable deduction type, deduction code, deduction name, and deduction class
• Separating current taxable and non-taxable benefit amounts
• Reviewing current benefit taxes and calculated benefit base
• Validating MTD, QTD, and YTD values
• Consolidating employee-level results into spreadsheets
• Rebuilding deduction, pay group, pay period, company, and grand totals manually

This creates additional reconciliation work and makes it harder to maintain a consistent reporting process after a legacy payroll platform is retired.

The DataTerrain Solution

DataTerrain developed a customized Benefits Paid Report - Canada in Oracle Fusion HCM to reproduce the core business requirements of the PeopleSoft PAY021CN Benefits Register.

The solution uses Oracle HCM data to retrieve the applicable payroll, benefits, deduction, element, and balance information for the selected reporting scope.

The report then:

• Identifies the applicable deduction and deduction class
• Separates current taxable and non-taxable benefit amounts
• Presents current benefit taxes
• Displays the calculated benefit base
• Retrieves MTD, QTD, and YTD values
• Groups employee records by the required reporting dimensions
• Generates deduction, pay group, pay period, company, and grand totals

Because the report is parameter driven, the same solution can be reused across payroll cycles, pay groups, companies, and authorized employee populations without changing the underlying extraction logic.

Report Parameters

Depending on the organization's Oracle HCM configuration, runtime parameters can include:

Users can therefore run a focused employee or deduction review or generate a broader benefits register for the authorized population.

Parameter availability and defaulting can be configured according to the organization's Oracle HCM reporting requirements.

Report Header and Control Information

The report preserves the control information needed to make each Benefits Register traceable and review ready.

The output can include:

• Report ID, such as PAY021CN
• Company
• Pay Period End Date
• Pay Group
• Deduction Code
• Deduction Name
• Deduction Type
• Deduction Description
• Page Number
• Run Date
• Run Time

This information helps payroll and benefits teams identify the reporting scope and validate the report during reconciliation or audit review.

What the Benefits Paid Report Captures

The report provides employee-level benefit and balance information required for payroll and benefits validation.

Employee and Deduction Context

The report can display:

• Employee ID
• Employee Name
• Deduction Class
• Deduction Type
• Deduction Code
• Deduction Name

These fields identify the employee and the benefit or deduction being reported.

Current Benefit Values

The report includes:

• Current Taxable
• Current Non-Taxable
• Current Benefit Taxes
• Calculated Benefit Base

These values provide the current-period benefit information required for payroll and benefits reconciliation.

Accumulated Balance Values

The report also provides:

• Month-To-Date
• Quarter-To-Date
• Year-To-Date

These accumulated values give payroll and benefits teams additional context when validating benefit balances across payroll periods.

The exact benefit plans, deduction types, balance definitions, and calculation rules depend on the organization's Canadian payroll and benefits configuration.

Built-In Reconciliation Totals

A key requirement of the legacy PAY021CN Benefits Register was the ability to review totals at multiple levels.

The Oracle HCM report can therefore provide:

• Deduction Total
• Pay Group Total
• Pay Period Total
• Company Total
• Grand Total

This hierarchy allows reviewers to move from individual employee records to broader control totals without manually rebuilding the totals in a spreadsheet.

Why HCM Extracts Fits the Requirement

Oracle HCM Extracts is well suited to the requirement because the Benefits Paid Report involves payroll and benefit balances across potentially large employee populations, reusable runtime parameters, and recurring scheduled execution.

The extraction framework supports:

• Retrieval of required benefit and deduction balances
• MTD, QTD, and YTD balance retrieval
• Employee and payroll population filtering
• Parameter-driven execution
• High-volume payroll processing
• Scheduled and recurring report execution
• Oracle HCM data-access controls

The extract can be configured to retrieve the required payroll elements and balances while limiting the data to the reporting scope required by the business.

BI Publisher and Reporting Options

BI Publisher

BI Publisher complements HCM Extracts when a controlled, register-style output is required.

It can support:

• Fixed report layouts
• Multiple subtotal levels
• Custom formatting
• Excel output
• PDF output
• CSV or other configured formats
• Business-specific report headers and control information

For the PAY021CN-equivalent requirement, BI Publisher provides the presentation layer needed to reproduce the structured Benefits Register experience.

OTBI

OTBI may be appropriate when users primarily need interactive analysis, dashboards, or ad-hoc reporting and the required fields are available in the relevant subject areas.

For this requirement, HCM Extracts with BI Publisher is the stronger fit because the report requires high-volume payroll and balance retrieval, controlled grouping, multiple subtotal levels, and a repeatable register-style output.

How the Report Works

The Benefits Paid Report follows a parameter-driven reporting process:

• An authorized user runs the report directly or starts a scheduled execution.
• The user enters the applicable legislative, payroll, pay-period, organizational, employee, and deduction parameters.
• Oracle HCM retrieves the authorized payroll, benefits, element, deduction, and balance data.
• The report groups the applicable records by deduction and deduction class.
• Current taxable, non-taxable, benefit-tax, and calculated benefit-base values are prepared.
• MTD, QTD, and YTD balances are retrieved according to the configured balance definitions.
• Deduction, pay group, pay period, company, and grand totals are generated.
• BI Publisher produces the final structured Benefits Paid Report in the required output format.
• For large populations or broad reporting periods, scheduled background execution can be used to reduce the risk of interactive processing timeouts.

Data Flow

Input: Legislative Data Group, Pay Period, Employee, Payroll, Payroll Relationship Group, Payroll Statutory Unit, Tax Reporting Unit, Company, Pay Group, and optional deduction filters

Source: Oracle Fusion HCM Payroll, Benefits, element, deduction, and balance data

Processing: Runtime filtering, deduction classification, taxable and non-taxable classification, benefit-tax and benefit-base preparation, MTD/QTD/YTD balance retrieval, and multi-level total generation

Output: Structured Oracle HCM Benefits Paid Report equivalent in purpose to the PeopleSoft PAY021CN Benefits Register

Expected Business Impact

Replacing a legacy PeopleSoft Benefits Register with an Oracle HCM equivalent helps preserve an established payroll control process while reducing dependence on manual extraction and spreadsheet reconciliation.

Illustrative planning estimate: A benefits register that previously required 12–15 or more hours of extraction, spreadsheet calculation, and reconciliation could potentially be reduced to approximately 10–30 minutes of report execution and validation.

These figures are planning estimates rather than measured customer results. Actual results depend on employee population, pay groups, companies, deduction complexity, payroll elements, balance definitions, report runtime, and review requirements.

Potential outcomes include:

• Continuity of a critical Canadian benefits register after PeopleSoft retirement
• Reduced manual benefits reporting effort
• Faster access to taxable and non-taxable benefit information
• Clear visibility into benefit-related taxes and calculated benefit base
• Consistent MTD, QTD, and YTD reporting
• Automated control totals at multiple reporting levels
• Reduced spreadsheet and manual roll-up errors
• Improved support for benefits reconciliation, tax review, and audits

Security and Responsible Access

The report operates within the Oracle Fusion HCM role-based security model.

Users can retrieve only the employee, payroll, benefits, and organizational information permitted by their:

• Security profiles
• Legislative Data Groups
• Legal-employer access
• Data-access roles
• Company or pay-group permissions

Because the report contains employee-level payroll, benefits, and tax information, access should be restricted to authorized payroll, benefits, HR, finance, tax, compliance, and audit users.

Runtime parameters narrow the requested reporting population; they do not expand the user's underlying Oracle HCM data authorization.

Typical Implementation Approach

A Benefits Paid Report -Canada implementation generally includes:

1. Legacy report analysis:Review the PeopleSoft PAY021CN layout, fields, grouping, calculations, and business rules.
2. Oracle HCM data mapping : Map legacy fields to Oracle HCM payroll, benefits, deduction, element, and balance data.
3. Deduction and balance mapping: Identify deduction types, codes, classes, taxable/non-taxable values, benefit taxes, and benefit-base logic.
4. To-date balance validation: Map and validate MTD, QTD, and YTD balance definitions.
5. Subtotal design Configure deduction, pay group, pay period, company, and grand-total requirements.
6. HCM Extract development: Build and optimize the extraction logic.
7. BI Publisher development: Create the register-style report layout and required output formats.
8. Security and performance validation: Validate data access, high-volume processing, and scheduled execution.
9. User acceptance testing: Reconcile sample results against the expected business rules.
10. Production deployment: Deploy and configure recurring execution where required.

Typical implementation effort is approximately 1–3 weeks, depending on the number of deduction types, pay groups, companies, payroll elements, balance definitions, subtotal rules, and legacy-report behaviors involved.

The estimate should be confirmed after detailed requirements review.

A Configurable Canadian Benefits Reporting Foundation

Canadian payroll and benefits configurations vary across organizations. Benefit plans, deduction types, payroll elements, companies, pay groups, balance definitions, and reconciliation requirements may differ significantly.

DataTerrain can configure the Benefits Paid Report with:

• Company and pay-group filters
• Pay-period parameters
• Employee-level filtering
• Custom deduction selection
• Taxable and non-taxable benefit logic
• Benefit-tax and benefit-base calculations
• MTD, QTD, and YTD tracking
• Multi-level subtotal and grand-total logic
• Scheduling for recurring reporting
• Organization-specific security rules
• Excel, CSV, PDF, or other required output formats

This allows the Oracle HCM report to preserve the business requirements of a legacy report while adapting the underlying data and reporting framework to Oracle Fusion HCM.

Conclusion

The Oracle HCM Benefits Paid Report - Canada demonstrates how a business-critical PeopleSoft payroll report can be recreated in Oracle Fusion HCM without losing the employee-level detail, accumulated balances, grouping, and control totals required for recurring benefits reconciliation.

By reproducing the core PAY021CN Benefits Register experience including taxable and non-taxable benefits, benefit taxes, calculated benefit base, MTD/QTD/YTD values, and multi-level totals the solution provides payroll and benefits teams with a consistent, parameter-driven, and audit-ready reporting process after PeopleSoft retirement.

Related Resources

• Oracle HCM Pre-Built Reports
• Oracle HCM Analytics
• Any-to-Any BI Reports Migrations
• ETL Migration Solution
• Oracle Health Analytics