beqom PaySuite 30.2 - Feature release notes
This article details the latest improvements introduced in version 30.2 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Compensation Management
Faster republishing of compensation rounds
Republishing a compensation round used to reload the round's whole population every time, even when none of its data could have changed. In large rounds, with 200,000 to 300,000 workers per hierarchy, this was a major reason a single publication could take more than 30 minutes. Compensation rounds now keep their existing data when nothing has changed, so republishing is much quicker.
A round now refreshes its data only on its first publish, after new data has been loaded or the data model has been extended, or when its data setup changes (for example its population or hierarchy). The Freeze Date, set in the Key dates step under Workbench > Compensation Rounds, is also easier to understand. A round counts as frozen from the day after its Freeze Date. From then on, it keeps its current data even if new data is loaded later, while before that date any changes are picked up at the next publish. Moving the Freeze Date does not reload any data on its own, and a Freeze Date more than one year in the past no longer causes publishing to fail.
It is now clear before publishing what will happen to the data. The Republish dialog states whether the round's data will be kept or refreshed, the date of the current data, and the reason. A Refresh data option, off by default, in the Republish and Generate report dialogs loads new data when it is needed (on a report, it affects only the report). Changing the population, hierarchy, Cut-off-Date, bonus plans, or compensation elements of a frozen round in its pending draft now asks for confirmation before the round's data is refreshed. Validation reports use the same data a publish would and never change the round, and Run history and Round progress show when a republish kept the round's data, with the date and the reason.
Frozen rounds are still included in automatic refreshes. They keep their current data, only recalculate compensation, and the run is shown as succeeded. Rounds with no saved Freeze Date, such as rounds created through the API (the platform's programming interface) or before this change, are never treated as frozen.
Publish updated comp round window.
Data Foundation
Custom fields on referenced entities in Data Modeler
Custom fields added to referenced Data Foundation entities, such as JobArchitecture, could not be selected in Data Modeler, even though the standard fields of those same entities were available. To use this information in models and snapshots, some organizations had to copy it to the worker level or maintain extra structures simply to make it reachable.
Data Modeler now offers the active custom fields of a referenced entity alongside its standard fields, wherever that entity is already supported. For example, custom fields added to JobArchitecture (the entity that holds job architecture data) can now be selected through the existing relationship from Employment to JobArchitecture and included in generated snapshots. Information can stay at the level of the Data Foundation data model where it belongs, and still be available for reporting and downstream use.
New Talent reviews report in Analytics Hub
Until now, Talent Review results could only be viewed inside each review in the Planner, one review at a time, which made it hard for HR teams to follow progress or compare outcomes across the organization. The new Talent reviews report in Analytics Hub brings every Talent Review template together in one place. It covers both the talent grid (Performance × Potential) and the optional second grid, Retention Risk (Risk of Loss × Impact of Loss).
The report shows how far each review has progressed, how workers are distributed across the 9-box grid, how closely managers and HRBPs agree on their ratings, and how the questionnaires were answered. Submission status is broken down by organizational unit, so HR can see at a glance which parts of the organization still have to act. The grids follow the axis names, box labels, and colors configured in each review template. The eight pages of the report cover:
Talent Review Overview and Talent Review Status: headline figures and the submission progress of managers and HRBPs.
Talent Grid Matrix and Retention grid matrix: the 9-box grids, with rating distributions and a breakdown by organizational unit.
Talent Grid Rating Alignment and Retention grid rating alignment: the share of reviews where the manager and the HRBP gave the same rating, and where they differ.
Talent Review Questionnaire Answers: questionnaire completion by role and by question.
Talent Review Export Details: one row per worker per review template, with final ratings for both grids, ready to export for use elsewhere.
The report is available under Analytics Hub > Talent reviews to users with the Analytics role (HR profile) and to managers (Manager profile), like other standard Analytics reports, once the Talent Review module is enabled for the tenant. In this release, the titles, filters, and table headers of the report are shown in English only, and translations will follow in a later release.
The Talent reviews report in the Analytics Hub