beqom PaySuite 30.1 - Feature release notes
This article details the latest improvements introduced in version 30.1 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 Management > Compensation Rounds, is also easier to understand. Once it has passed, the round keeps its current data even if new data is loaded later. Before it, changes are picked up at the next publish. Moving the Freeze Date no longer reloads 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 dialog loads new data when it is needed. 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 the Run History and Round progress show when a republish kept the round's data, with the date and the reason.
Publish updated comp round pop-up window.
Follow round publishing progress from the Compensation Rounds list
Publishing or republishing a compensation round runs in the background, which meant waiting on a blank screen with no sign of progress. When a run stopped, there was no easy way to tell where or why. Compensation Admin and Global Compensation Admin users can now follow each run from the round list under Workbench > Compensation Management > Compensation Rounds.
Once a Publish or Republish is confirmed in the wizard, the list opens again and the round's Status badge shows how far the run has got, for example Publishing · 1/5. A message at the top of the page reports whether the round is being published, has been published, or could not be published, with the reason. It keeps updating after leaving the page. A new Activity section in the row menu opens two panels, through View progress and View run history:
Round progress shows the latest run with its status, the current step out of five, the time elapsed, and an estimate of the time left. While compensation is calculated, a grid shows each batch of up to 2,000 workers with its state, so a failed calculation can be traced to the batch where it stopped.
Run history lists every publish and republish of the round, newest first, each with its steps.
Runs started by the daily automatic refresh appear here too. Runs cannot be cancelled or retried from these panels.
Progress message
Round progress drawer
Round validation rules in Mass update
The Mass update wizard used to check only the rules that apply to each worker, such as guidelines, eligibility, and workflow status. Round-level rules, such as budget pool ceilings or an average merit cap, were not checked, so a mass update across a large selection could push a pool over budget without any warning. Round validation rules are now evaluated across the whole selection when the preview is generated, so Compensation Managers and HRBPs can see the effect on budgets and caps before any change is applied. The wizard is opened with Mass update in a round's Comp review tab, under Planner > Compensation.
The Update rule step now lists these rules under Checked on the whole selection, marked From round setup, alongside the per-worker checks. Only rules that watch the columns being updated are evaluated. On the Review & apply step, banners show which rules were breached and which passed. A hard breach excludes every worker in the breaching pool and moves them to the Workers to skip tab, while a soft breach shows a warning and keeps the workers in Workers to update, so valid updates in pools within budget still go ahead. Rule cards break down each breaching pool by owner, headcount, utilization, and the amount over or short. For each skipped worker, the Reason column and the Change details drawer explain which rule excluded them, with the pool's Already allocated, This update, After update, and Limit figures.
Workers to skip tab
Example of expanded breached and passed cards
Hard rules are checked once more against live data when Apply is selected. If activity by other users has pushed a pool over its limit since the preview was generated, nothing is applied, and the rule and pool concerned are shown so the preview can be generated again. Pools with fewer workers than a rule's minimum headcount are not evaluated against that rule.
Pay Transparency
New Closed without release action status
When a Close & release action could not release a document because its Communication Round has workflow enabled, the action used to be logged as Failed, even though nothing had gone wrong and the document was simply waiting to be released. These actions now show the new Closed without release status, so real failures, such as mapping errors, stand out as Failed.
The status appears in the Bulk Actions details under Planner > Pay Information and in the run details of Workbench > Automated Action Monitoring, with its own filter option. CSV exports show it too, together with a message explaining why the release was not done. The change also applies to past runs, which now show Closed without release where they previously showed Failed for a release blocked by workflow. The request itself stays in Pending Release until its document is released.
Automatic release card
Category averages by gender in Pay Information documents
Answering a pay transparency information request often means giving a worker the average pay in their category, broken down by gender, and these averages had to be calculated outside the platform. Pay Information document templates can now include averages of calculated compensation fields for the worker's Category, by gender, together with the headcount of each gender group.
Averages can be added per compensation element, gender group (all, male, female, other, or unknown), and compensation source (compensation history, contracted compensation, or paid compensation). They are calculated from the same snapshot as the rest of the document, so the figures stay consistent, and are rounded to two decimal places using the tenant's number format. Empty amounts are left out of an average, while the worker is still counted in the headcount. No currency conversion is applied, so all workers in a category are expected to share the same currency.
Sorting, filtering, and pagination in Passport Documents
Workers with many documents in Passport had to scroll through one long list to find the one they needed. The Documents section of Passport now supports sorting by column, filtering, and pagination, so specific documents are quicker to find, and long lists are easier to read and load faster.
Automatic release for Communication Rounds with workflow
Organizations that use an approval workflow on their Communication Rounds could not release Pay Information documents automatically, because closing a request in a workflow-enabled round moves it to Pending Release instead of releasing the document. Automatic close and automatic release are now two separate automations, so documents can be released automatically even when the linked Communication Round has workflow enabled.
A new Automatic release card on the Response automation page releases documents either Immediately after closing or after a set Number of days after closing (from 1 to 299 days). It can be limited to certain request creation types, for example requests created by workers or HRBPs, and set up separately in country local rules. HRBPs without release permission on a round can now close requests and leave the release to the platform. Close and release are recorded as separate actions in the audit trail, and automatic releases are labelled in Automated Action Monitoring. Existing Automatic close & release configurations keep their current behavior, and when automatic release is not enabled, requests stay in Pending Release and can still be released manually.
New Local Pay Analytics Admin role
Delegating pay analysis to local or regional teams used to mean giving them full Pay Analytics admin rights, including access to global settings. The new Local Pay Analytics Admin role lets organizations hand this work to local administrators while global configuration stays protected, in line with the existing Compensation Admin and Global Compensation Admin model.
Local Pay Analytics Admins can create Pay Analysis data sets from Snapshot Manager, open Pay Analysis Results and run the sync, and work with analyses from start to finish, from editing recommended and final raises to publishing, closing, and deleting them. On a synced analysis, they see only the workers within their access scope. They cannot access Data Mapping or tenant and label management. The existing Pay Analytics admin role keeps all its rights and now acts as the global admin, so current role assignments are not affected.