This release focuses on improving reporting automation, increasing configuration flexibility, and reducing manual post-processing for payroll and finance teams.

The key updates include:

Pay Date Display Improvements in the Payroll Dashboard
GL – Employee Number String Token
GL – Conditional Value Override (IF/THEN Logic)
Custom Period Calendar Dates for Manifest and Time/Unit Reporting

Pay Date Display in Payroll Dashboard

Overview

The Payroll Dashboard has been enhanced to ensure that payroll periods are displayed according to the intended reporting month, even when pay dates fall in the following month.

This update resolves confusion for organisations that process payroll in arrears, where payroll activity is completed in one month but the pay date occurs in the next.

Background

Previously, the Payroll Dashboard grouped payroll periods based on the actual pay date month.

For organisations that pay in arrears, this created confusion.

Example:

November payroll tasks are completed in November
Employees are paid on 5 December
Filtering to November did not show November payroll tasks
Users had to filter to December to view that activity

This behaviour has now been improved.

What’s New

A new Pay Date Override field has been added within:

Payrolls → Payroll Configuration → Periods Calendar

For each payroll period, users can optionally define the month and year under which that period should appear on the dashboard.

Key characteristics:

An editable Pay Date Override field is available for every payroll period row
The number of override fields aligns with payroll frequency
The override value displays in Month Year format (e.g. January 2025)
Overrides can be applied to past periods
Overrides are optional
Changes take effect immediately

The override is display-only and does not impact payroll processing.

Dashboard Behaviour

When an override is set, the payroll period appears under the specified month
Associated tasks automatically display in that month
When no override is set, grouping continues based on the actual Pay Date

A Clear action is available to remove overrides for the active payroll year.

Weekend, bank holiday, or roll-forward rules remain unchanged.

GL – Add Employee Number String Token

Overview

A new string token has been introduced for use within configurable reports and GL Journal outputs:

%%EmpNo%%

This token allows the Employee Number to be dynamically included in constant columns.

Availability

The token can be used in:

GL Journal
All relevant configurable reports supporting string tokens

Resolution Behaviour

If a report row represents a single employee, the token resolves to that employee’s number
If a report row represents multiple employees (e.g. grouped rows without Employee-level columns), the token resolves to an empty string

This ensures reporting accuracy and prevents incorrect aggregation.

GL – Conditional Value Override (IF/THEN Logic)

Overview

A new Conditional Value Override feature has been added to the GL Report Builder.

This allows users to substitute output values in one column based on the value of another column — eliminating manual Excel manipulation.

Configuration

Users can create a Conditional Substitute Column that:

References any existing report column as a Source Column
Defines Source Value → Output Value mappings
Applies substitutions during report generation

Matching is case-sensitive.

Report Behaviour

For each row:

The system evaluates the Source Column value
If it matches a configured Source Value, the defined Output Value is written
If no match exists, the column outputs blank

The column is automatically named:

<Source Column Name> – Overrides

Example:

Pay Element Group → Pay Element Group – Overrides

Custom Period Calendar Dates

Overview

Two new custom date fields are now available per payroll period:

Custom Date 1
Custom Date 2

These dates are configurable within:

Payrolls → Payroll Configuration → Periods Calendar

They can be used for:

Outbound SFTP Manifest file configurations
Time/Unit reporting period calculations

Configuration & Entry

Available for every payroll period row
Fully editable, including historical periods
Weekends and holidays are permitted
Bulk-population available via Day Picker (1–31 or End of Month for monthly payrolls)

If a custom date column is partially populated, validation will require completion before saving.
A Clear action allows removal of all values in a column.

Use Case 1 – Manifest Configuration

Custom Date 1 and Custom Date 2 are now available as selectable column types in:

Administration → SFTP → Manifest Configurations

When selected:

The system retrieves the relevant custom date for each payslip’s payroll period
Applies the configured date format
Outputs the formatted value in the manifest

If no value exists, the field remains blank and file generation is not blocked.

Use Case 2 – Time/Unit Reporting

A new field labelled Period Date Source has been added in:

Payrolls → Reporting → Configurations → Time/Unit Report

Available options:

Pay Date (default)
Custom Date 1
Custom Date 2

The selected option determines the boundary dates used to calculate reporting periods.

Existing Created this period, Active this period, and Active previous period logic remains unchanged.

If required boundary dates are missing, the system falls back to Pay Date logic to prevent reporting failure.