beqom PaySuite 30.0 - Feature release notes
This article details the latest improvements introduced in version 30.0 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Compensation Management
Views in the Planner
Planner configurations can expose hundreds of columns, and managers working with large populations have had to recreate filters, sorting, and display settings each time they return to a compensation round. Views in the Comp review grid under Planner > Compensation lets Compensation manager direct, Compensation manager indirect, HRBP, and Compensation Advisory roles save and reopen their own working layouts in one click. Each view can store:
Visible columns, their order, and which ones are pinned
Standard and advanced filters, including ALL/ANY logic
Sorting, items per page, and row size
The order and visibility of budget widgets
The new feature allows users to create multiple views per compensation round and designate one as their default. That view is applied automatically when they enter the round, with Planner default remaining available as a fallback. A status dot on the Views control shows when the applied view has unsaved changes. Additionally, a Manage views option brings all views together for editing, renaming, deleting, and choosing the default. Saved filters run against current Planner data each time, keeping the resulting population up to date as compensation data changes. We have also redesigned the Comp review toolbar as a single row that adapts to the available width without removing any controls.
Views are private to each user and scoped to one compensation round and one Planner actor. They include only columns the Compensation Admin has made available and respect all worker, data, and population permissions. Therefore, administrators retain control over the Team planner view configuration. Views can be used while a compensation round is In progress, with no setup required.
Views in the Comp review toolbar, with a default view and the system Planner default
Budget worksheet in the validation report
For compensation rounds with budgets set to a fixed amount per manager, each manager has a separate budget pool. Previously, the validation report showed only per-worker budget contributions, leaving compensation administrators without a way to check these pools before publishing the round. With this release, we have included a Budget worksheet in the validation report export whenever the round contains at least one budget definition of this type.
The worksheet lists managers by hierarchy, including their reporting line and level, and shows the direct, indirect, and full branch budget and headcount for every applicable budget definition. Amounts are converted to the round's reference currency for direct comparison. Administrators see only managers within their authorized scope, while totals always cover each manager's full branch. The report is available for download from the Validation step of the round under Workbench > Compensation Management > Compensation Process > Compensation Rounds. Budget definitions aggregated at worker level do not appear in the worksheet.
Manager-level budget pools in the validation report
Browse by tree based on the round's hierarchy source
Managers browsing Planner > Compensation need reporting lines that match the hierarchy governing their access. However, although a compensation round can use either the round key dates or the live hierarchy, the Browse by tree in the Population panel has always relied on the cut-off date snapshot. As a result, reporting lines in the tree could differ from the current structure used to determine which workers a manager is allowed to manage.
With a round set to Live hierarchy, the Browse by option corresponding to the round's configured hierarchy now builds its tree from the current organization structure. Workers appear under their current managers with up-to-date job titles, and mid-cycle reorganizations are reflected without changing the round configuration. The round population itself remains governed by the round's population rules. Rounds set to Round key dates continue to use the snapshot, as do the other Browse by options.
The tree is rebuilt when the round is opened, when switching between tabs, or when changing the Browse by option. The Refresh option does not trigger a rebuild.
Single size control for the budget band
Expanding budget widgets individually in the Planner > Compensation produced cards of mixed sizes, uneven gaps, and a compensation grid that shifted with each change. Version 30.0 of the application introduces a single size control. It sets all widgets in the budget band to collapsed, medium, or expanded states. A collapsed state shows each widget's name, spent and budget amounts, and utilization; an expanded one displays the full allocation table.
Each size has a fixed height, keeping the grid in place. The band remains on one row and scrolls horizontally when its widgets exceed the available screen width. The selected size is remembered in the browser and applied across rounds, with medium as the default for a new browser or private session. An information icon beside the Population panel title also explains how the panel controls the grid and budgets.
Expanded budget band, showing the allocation by scope for each widget
Create group action for Planner columns
Previously, grouping columns in the Team planner view's Column configuration table required opening the Manage column groups modal, creating a group, and adding each column individually. Administrators can now select ungrouped columns directly in the table and create a group through the Bulk options menu, under Workbench > Compensation Management > Compensation Process > Compensation Rounds.
The new group appears at the top of the table, with the selected columns in their existing order. Administrators can then move, rename, or recolor it through Manage column groups as before. The action is available only when none of the selected columns already belongs to a group. A tooltip explains why it is unavailable otherwise.
Create group in the Bulk options menu of the Column configuration table
Performance Management
Work country used consistently in country filters and columns
The country filter in the Career Development Plans and Performance Review Templates management lists underWorkbench > Performance Management could return no results for any country, even when other filters worked correctly. This happened because worker records contain both a home country and a work country, but the lists displayed one and filtered by the other. One of the management tables also lacked a Country column, making it impossible to see the value used for filtering.
Currently, both areas display and filter by the worker's work country, and the Country column in the Talent Review follows the same rule. The missing Country column has also been added, so both management tables include it. Workers with only a home country recorded have no country displayed and are not matched by a country filter. Their work country must be provided at data ingestion for it to appear in the column and be available for filtering. A country with no workers based there correctly returns an empty list. All other filters remain unchanged.
Pay Transparency
Pay information request details in a side drawer
In previous versions of PaySuite, HRBPs who reviewed multiple pay information requests had to leave the Pay Information table in the Planner to open each one. With this release, we have provided a new Details action. It displays the request in a side drawer, keeping the table in view so that HRBPs can work through requests one after another. The drawer contains the same information as the existing view mode, with an Edit button when the user's permissions and the request status allow changes. The full-page view is still available.
View request drawer, open beside the Pay Information table
Category averages for calculated fields in pay information documents
Pay transparency rules often require workers to see how their pay compares with others in the same category. Pay information document templates can currently include the average of a calculated compensation field for the worker’s category, broken down by gender, alongside the category headcount. This extends the calculated-field support introduced in release 29.3 and removes the need to calculate and maintain these averages outside the platform.
The averages are added to a template with new placeholders that follow the pattern {{category_avg_<elementId>_<gender>_<source>_amount}}, where:
<elementId> is the External ID of the compensation element (for example, BQBP1001)
<gender> is all, male, female, other, or unknown
<source> is CompensationHistory, ContractedCompensation, or PaidCompensation
The category headcount uses its own placeholders, for instance {{category_count_all}}.
Averages are calculated from the snapshot linked to the pay information request when the document is generated, with workers grouped by category and gender. Empty amounts are excluded from the average but still count toward the headcount; zero amounts are included. The application rounds averages to two decimal places and formats them according to the tenant’s number and separator settings. No currency conversion is applied, so all workers in a category are expected to share the same currency.
Show sensitive data toggle displayed only when relevant
In Passport > Compensation, the Show sensitive data toggle now appears only when the digital reward statement includes at least one block containing sensitive compensation information: Compensation in numbers, Compensation breakdown, Position in pay range, or Compensation history. If an administrator disables these blocks in Workbench > Platform Setup > Worker & Manager Pages > Passport > Compensation > Digital reward statement, the toggle is hidden for a worker in Passport because it would have no effect. Other blocks, such as Compensation philosophy, Pay information, and Resources, remain unaffected, and the page layout is intact. When sensitive blocks are enabled, their data stays hidden by default until the toggle is turned on.
Authorization
Security Groups for role-specific worker access
Access in the platform combines two elements: a role, which defines what a user can do, and a data scope, which defines which workers the user can access. Until now, both were assigned individually to each user as direct attributes, so a single data scope applied to every role the user held. A user acting as HRBP for France and as Compensation Admin for Germany could not be given a different worker population for each role.
Security groups remove this limitation. Each group combines one or more roles with its own data scope and can be assigned to one or more users. A user who belongs to both a France HRBP group and a Germany Compensation group sees French workers when acting as HRBP and German workers when acting as Compensation Admin.
Users with the Security role manage security groups under Workbench > Data Management > Access Management > Security Groups. The administration pages offer:
An overview of all security groups, with search by name and filters by role and authorization attribute
Group creation, including a name, one or more roles, and a data scope built from worker attributes and values
A details view showing each group's roles, data scope, and number of assigned users
User assignment, either from the security group itself or from the user's entry in Workbench > Data Management > Access Management > User Roles & Permissions
CSV download and import for creating or updating multiple groups, with valid rows still processed when others contain errors
Existing users can be migrated gradually. While a user still has direct attributes, those remain in effect and security group assignments are ignored until the direct attributes are cleared. User Roles & Permissions indicates each user's permission source and flags conflicts, and the Scope review action shows which workers a user can see under each role.
Administrators can also review security groups that are based on an explicit list of workers (an access control list, or ACL), and search that list by worker name or Worker ID. The list is read-only in the platform and is maintained through the Security Group Integration API.
Filterable security groups with their roles and attributes
Roles and data scope in a new security group
Permission source for each user in User Roles & Permissions
Workers visible to a user under a selected role