ROE, in plain English.

How ROE works.

ROE is one of the operating concepts behind a modern Canada platform. In practice, the term names a specific outcome: an employer can prove the calculation, automate the workflow, and audit the result without an intermediate spreadsheet or third-party tool. Workzoom treats ROE as a first-class function of the single employee record, which means every dependent module, HR, payroll, workforce, and talent, reads from the same source of truth.

Why mid-market HRIS buyers care about ROE.

Mid-market employers feel the cost of ROE differently than small businesses or global enterprises. Below 50 employees the workload is small enough that a manual process survives. Above 5,000, the budget tolerates a multi-system stack with specialist consultants. Between those, the employer carries enterprise-grade complexity on a small-business administrative team. That is the size band Workzoom is built for. Concretely, that means three things: every concept on this page is automated by default; statutory rates refresh inside the platform without a re-implementation; and the same employee record drives reporting, audits, and decisions across every suite.

How Workzoom does ROE differently.

Workzoom encodes ROE as a deterministic calculation tied to the employee's position, jurisdiction, and effective dates. Statutory rates are maintained by Workzoom and pushed to the platform automatically, so employers never copy a rate card or re-key a percentage. Reports, audits, and exception alerts read from the same record, so there is no reconciliation between an HR database and a payroll database.

Where ROE sits between HR and payroll.

ROE does not stand alone. The concepts most often paired with it on a Canada run are EI, Offboarding. Each is defined elsewhere in this glossary so you can trace the full chain without leaving the site.

The ROE mistakes that show up in audits.

• Treating ROE as a one-time setup rather than an ongoing calculation that has to refresh each pay cycle, position change, or rate update.
• Maintaining the rule in a spreadsheet outside the payroll system. The spreadsheet drifts within a quarter, and the audit trail disappears.
• Letting the system of record diverge from the system of calculation. Two databases means two truths, and the discrepancy surfaces on the year-end filing.

ROE questions to put in your RFP.

• Does the platform handle ROE on the same employee record as HR and time, or via a downstream integration?
• Who maintains the underlying rate or rule, and how is it updated when the authority publishes a change?
• Can the platform produce an audit-ready report for ROE across any date range without exports?
• What does the failure mode look like when an employee crosses a threshold mid-pay-period?