Effective dating, in plain English.

The raise was approved on a Tuesday in March. It took effect January 1. Two months of underpayments sat in the books, and every pay stub since the first of the year was wrong.

That gap, between when a change is entered and when it is meant to apply, is where payroll errors accumulate. Not in exotic edge cases. In the ordinary work of promotions, transfers, and raises that never land exactly on a pay period boundary.

What effective dating actually does.

Effective dating stamps every change to compensation, position, or status with the date it takes effect. Not the date someone entered it. The system carries both dates for every record: when it was created, and when it applies. Those two dates are often weeks or months apart.

When payroll runs, it does not read the entry date. It reads what was true on each pay period's start and end dates. A raise effective January 1 lands on the January run, even if HR entered it in March. A transfer effective April 15 moves the cost centre allocation on April 15, not on the day the manager filled out the form.

Historical reporting works the same way. Ask what an employee earned on a specific date in a prior year and the system returns the value that was true on that date. Not the current salary. The value in effect at that moment.

Retroactive changes and arrears.

Future-dating a raise is the easy case. Enter it now, set the date, and payroll picks it up when the period arrives.

Backdating is where most systems fall apart.

Take a raise that should have landed January 1. It is now March. The system must calculate what was owed in each affected pay run, compare it to what was paid, and surface the difference as arrears. Without that core capability, HR teams do this manually, run by run, usually in a spreadsheet. Errors compound. Audits catch them.

Workzoom uses effective dates to know what should happen when. Enter a backdated raise once, on the correct date, and arrears calculate automatically. No re-entry across prior pay periods. No reconciliation spreadsheet to carry into the next quarter.

What shows up in audits.

• Raises applied on the wrong run. The entry date drives the change instead of the effective date. An employee approved for a raise on March 10, effective January 1, sees it land on the March run. The underpayment sits as an unrecorded liability until someone catches it.
• Retroactive corrections entered as current-period adjustments. Without back-dating, teams add a lump-sum to the next run. The T4 reflects the adjustment date, not the period it covers. That mismatch shows up in audits.
• Historical reports that contradict pay stubs. If the system overwrites prior history when a record is updated, a report pulled today shows different figures than the February pay stub. Audit trails break.
• Transfers that miss the right cost centre. A position change entered late without an effective date can split cost reporting between the old and new department across several runs, creating variances that take a full budget cycle to untangle.

Built into the core.

Workzoom is all-in-one, built that way from day one, not bolted together by acquisition. Effective dating is not a module layered on top. It is in the core data model, which means every change to compensation, position, benefit eligibility, or employment status carries its effective date through every downstream calculation without extra configuration.

That single employee record is the whole picture: hire date, every title change, every pay adjustment, every transfer. County of Renfrew, Silvera for Seniors, and Cable Bahamas run payroll on that same record. When Workzoom generates the T4 at year-end, or produces the remittance extract, the figures reflect each effective date as entered, from January 1 forward. The client submits to the CRA. Workzoom makes sure the numbers behind the submission are right.

Operating since 2001, family-owned, with the founder still running it: that history means effective dating has been tested across Canadian public-sector payrolls, Caribbean island runs, and 25 years of real pay periods. Not in a lab. In production.