beqom PaySuite 28.0 - Feature release notes
This article details the latest improvements introduced in version 28.0 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Pay Transparency
Configurable Worker information widget in the digital reward statement
So far, the Worker information widget in the digital reward statement has shown a fixed set of details in a specific layout, leaving little room to match it to how an organization presents worker data.
In version 28.0 of the application, we have enabled administrators to control the widget at three levels: the widget as a whole, each of its sections, Details, General information, and Role information, and individual fields within them, from Work country and Worker ID to Job title, Job level, and Cost center name. Configuration is available underWorkbench > Platform Setup > Passport > Compensation > Digital reward statement.
The order of fields can be set by dragging them into place. In addition, section labels can be renamed and localized for each active platform language so that a statement uses an organization's internal terminology. Admins cannot save their changes unless every enabled section keeps at least one enabled field. To avoid manual rework, a Reset to default button restores the original visibility, labels, and order in a single step. Importantly, by default, all Worker information sections and fields are enabled.
With this enhancement, organizations can decide which worker attributes appear in a statement, supporting data governance and local requirements. Wording and structure can also be adjusted to match how workforce populations are addressed.
Field-level visibility settings for the Worker information widget
Demo
HRBP review notifications, with combined notifications for bulk operations
Once a document reached the HRBP review workflow step, an HR Business Partner had no automatic signal that it needed attention.
A Document ready for HRBP review notification is now sent automatically when a document enters that step, whether through an individual update, an import into a workflow-enabled communication round, a bulk update, or automated processing. Administrators can configure it via Workbench > Platform Setup > Email Notifications > Documents. The new notification is delivered both in-app and by email, and addressed only to the HRBPs assigned to the affected workers. Its email content can include the document name, the worker name, and the communication round through configurable variables. Opening a notification leads directly to Planner > Documents > Communication rounds > HRBP review, filtered to the relevant document and worker wherever that information applies. When many documents proceed to HRBP review at once, for example after a large import or a bulk workflow update, a Multiple documents ready for HRBP review setting groups those transitions into a single notification.
As a result, HRBPs are alerted the moment a document is ready, with combined notifications preventing a flood of separate alerts during batch operations.
In-app notifications for documents ready for HRBP review
Notification settings reorganized in Workbench
Notification settings inside Workbench have grown alongside Pay Transparency, without a clear structure separating one kind of notification from another.
We have grouped these settings into two sections, Documents and Pay information request, under Workbench > Platform Setup > Email Notifications. A notification related to document workflows is no longer mixed in with one governing pay information request processing.
This makes the right setting easier to find as Pay Transparency continues to add notification types, without changing how any individual notification is itself configured.
Documents and Pay information request notification settings
Enhanced route protection for Pay Transparency configuration pages
Pay Transparency configuration pages now apply stronger, feature-based access controls. A page tied to a capability that is disabled for an organization is removed from Workbench navigation and blocked from direct access by its URL, across configuration areas including document settings, document templates, pay information requests, and related pages.
This way, the configuration options remain aligned with the Pay Transparency capabilities actually enabled for each organization.
Data Foundation
Configurable month-based time-in-role calculation
Until now, time-in-role was calculated strictly by day, which did not always meet the requirements of compensation policies that operated on monthly cycles.
Thanks to a new Calculation basis setting, available under Workbench > Data Management > Situation & Absence Configuration > Time in role, time-in-role can be calculated using calendar months instead. Days remains the default, so existing configurations and calculations are unaffected unless Months is selected deliberately. When the Months option is chosen, a Month alignment rule determines how a change occurring partway through a month is applied: at the start of the current month, at the start of the next month, or based on a configurable Boundary day, set between 2 and 27, before which a change takes effect from the current month and after which it takes effect from the following month. For example, with a Boundary day of 15, a change on 15 May is effective from 1 May, while a change on 20 May is effective from 1 June. Situations created this way follow calendar-month boundaries instead of exact dates. Several changes resolving to the same month produce a single situation using the latest value, while changes resolving to different months each produce their own, and any associated data or calculated fields use the same month-aligned boundaries. Monthly calculation requires the applicable snapshot period to align to complete calendar months.
This lets time-in-role situations and proration match compensation policies built around monthly periods, rather than forcing a day-based approximation onto a process that runs by month.
Calculation basis and Month alignment for Time in role