beqom PaySuite 29.1 - Feature release notes

This article details the latest improvements introduced in version 29.1 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.

Compensation Management

Mass update across the Planner grid

So far, applying the same value to multiple workers in a compensation round has required editing each worker's cell individually, with no way to preview the broader impact before committing the change.

With this release, we have included a Mass update action in the Planner > Compensation grid toolbar. The action opens a wizard consisting of three steps: Population, Update rule, and Review and apply. The wizard can use the grid's current selection, the round's entire population, or a custom group based on the grid's filters. A live count shows how many workers will be affected.

Each run updates or clears one field at a time. The value editor matches the field type, and a note can be optional or required depending on the column configuration. Before applying the change, the system validates every worker in the target population against workflow state, eligibility, guideline ranges, and drop-down validity. It also runs a background preview that simulates the update across the entire population.

The review step separates workers who will be updated from those who will be skipped and gives a reason for every skip, such as a locked or already approved row, missing eligibility, an unchanged value, or a hard guideline breach. Each worker also has a full before-and-after breakdown. Soft guideline breaches do not block the update; instead, they appear as warnings in the review step and the worker's detail view. This allows managers and HRBPs to deliberately apply an out-of-guideline value while keeping the exception visible.

Cascaded values that would become invalid are cleared automatically, following the same logic as a single-worker save. To keep traceability intact, every mass update is also recorded in the audit log.

The feature replaces cell-by-cell editing for large populations with a controlled, previewable workflow that retains the established governance of compensation round changes.

Scope selection for a mass update

Rule behind a mass update, with validation checks included

Affected values previewed side by side

Demo

Copy JSON sample aligned with the real payload

In the Round Management portal within Workbench > Compensation Management > Compensation Rounds, the Copy JSON sample in the Statement generation tab has not reflected the payload generated by a real round. It was also only available after the creation of a statement generation rule.

Currently, template authors can access Copy JSON directly from the Statement generation empty state, before creating a generation rule or running a round. We have also aligned the sample with the actual payload structure.

A custom input field with currency enabled is represented as a monetary object. In a template, it is referenced as {{RoundData.<Code>.Value}} rather than {{RoundData.<Code>}}, alongside Currency, the resolved currency code, and ConvertedValue, the amount converted to the compensation round's currency. Value represents the amount in the currency configured for the field, whether that is the worker's local currency, the round's currency, or a fixed code.

In addition, the sample includes the bonus comp element amount, identified by the code of the comp element configured as the round's Bonus element, under RoundData and using the same monetary structure. Which fields appear continues to follow the round's column configuration, so fields with visibility disabled remain excluded.

The payload generated by a real round is unchanged; only the sample has been corrected to represent it accurately. Custom input fields without currency enabled retain their plain-number representation, while other Bonus fields, including Calculated Bonus, Target Bonus, and Prorated Target Bonus, are unaffected.

The Statement generation tab and its Copy JSON option remain available only for published rounds and to Global Compensation Admin and Compensation Admin roles.

This way, template authors can start from an accurate payload structure immediately, reducing the risk of silent template errors involving currency fields or the previously missing Bonus amount.

Demo

Freezing worker-level budgets

Freezing a budget's calculated amounts in place prevents publishing a round from re-running its budget rules. The capability has been limited to fixed-per-manager pools and could only be enabled after a round's first publish.

Under Workbench > Compensation Management > Compensation Rounds > Budget, worker-level budget definitions can now also have their calculated amounts frozen, and the setting can be enabled before the first publish. The earlier restriction and its banner have been removed, and changing a budget's aggregation between fixed-per-manager and worker level no longer resets the freeze toggle.

A draft round with a frozen budget still runs its budget rules once, during the first publish, to establish the baseline. Subsequent publishes leave each worker's amount exactly as it was at the last calculation before the freeze.

Population changes continue to affect frozen worker-level budgets. A worker who joins after the freeze receives zero, while a worker who leaves the population is removed from the total. This differs from a fixed-per-manager pool, whose amount remains fixed regardless of population changes.

The Recalculation section and How this budget behaves preview include a note explaining that budget rules do not run on publish while the definition remains frozen. Freeze behavior for fixed-per-manager budgets is unchanged, and the Frozen tag in the Planner still follows the existing recalculation setting.

The Freeze the calculated amounts toggle is available to Compensation Admins and Global Compensation Admins, extending predictable, freeze-in-place amounts to worker-level budgets and allowing the decision to be made during round configuration rather than after the round goes live.

Toggle for freezing calculated amounts, with a budget-behavior preview

Demo

Visible limit on Planner sorting

Until now, sorting the Planner by too many columns at once resulted in a generic validation error, without indicating in the interface how many sort criteria were allowed.

In version 29.1 of the application, the Planner > Compensation grid supports up to ten sort criteria at a time, including criteria already applied when the grid loads, such as an actor's default sorting.

When all ten criteria are in use, clicking an unsorted column displays a "You have reached the sorting limit" popover with Manage sorting and Cancel buttons. The clicked column is not added and the grid is not re-sorted. Manage sorting opens the Sort drawer with the existing criteria, without adding the clicked column. At the limit, + Add sort criteria is replaced by an "Up to 10 levels" hint.

Columns already included in the sort continue to cycle through their sort directions, allowing a criterion to be freed when needed. Removing a criterion restores + Add sort criteria and the standard column-header behavior once fewer than ten criteria remain.

Because the limit is enforced in the interface, worker search requests are never sent with more than ten sort criteria. Therefore, managers and HRBPs see and can act on the limit directly instead of encountering a failed grid load.

Sorting-limit popover

Demo

Performance Management

Tag and tag-library descriptions on goal forms

Tag libraries and individual tags have always supported optional descriptions in Workbench, but workers selecting tags on the goal form could not see what each library contained or what an individual tag represented.

Now, when the Tag library toggle is enabled for a goal type, the Create and Edit goal forms in the Goals tab of both Passport and Planner contain a Tag library section. Each available library shows its name and description as plain text, followed by a checkbox grid containing all enabled tags. A description panel accompanies each library. The grid replaces the previous tag search field, including its pre-populated chip and per-tag remove icon. Tags already assigned to an existing goal appear pre-checked, and workers can select any number of tags across one or more libraries. Selections are saved with the goal on Save and Publish.

Each library's description panel initially prompts the user to hover over or focus a tag. When a tag is hovered or receives keyboard focus, the panel displays its description. Moving the pointer or focus away restores the idle prompt. Selecting a checkbox does not affect the panel, which responds only to tags within the same library.

On the read-only goal view, the section previously called Strategic priorities is renamed Tag library. It lists only the tags selected for that goal. Each tag includes its name, a description label, and a description in a read-only box, so no hover interaction is required.

Library and tag names and descriptions are displayed in the worker's configured language. When a translation is unavailable, the complete item falls back to the system default language rather than combining translated and default-language text. Managers and Goals professional users creating or editing a goal on someone else's behalf see this content in the system default language, regardless of their language setting. When viewing a goal, including a manager viewing a direct report's goal in the Planner, users see names and descriptions in their own language.

Tag library form, Employee Development tag with its description field

Tag library list, each tag's description alongside its name

Pay Transparency

Finer anonymization thresholds, with protection against indirect disclosure

Anonymizing pay information requests has relied on a single population threshold, applied both to a worker category as a whole and to each gender within it. There has also been no separate safeguard against reconstructing an anonymized figure from other aggregated values that remain visible.

We have split the population threshold into two independent settings: Worker category headcount threshold, which defines the minimum number of workers required before aggregated information for a worker category can be disclosed, and Gender headcount threshold, which specifies the minimum number of workers of a given gender within that category. A new Prevent indirect disclosure option can also be enabled. When at least one gender population, or the worker category as a whole, falls below its threshold, population counts across genders are anonymized as well, preventing the withheld value from being derived from the other disclosed figures.

Both thresholds and the indirect-disclosure setting can be configured globally and overridden by a local rule for a specific country or population. Where a local rule exists, its configuration takes precedence. For tenants already using anonymization, Gender headcount threshold is initialized from the previous population threshold, preserving the existing behavior until an administrator changes the settings independently. The Alerts & Anonymization settings page and its Local rule definition section within Workbench > Pay Transparency have been updated accordingly.

These changes give administrators more precise control over disclosure thresholds while reducing the risk of reconstructing anonymized information from related population data.

Global anonymization, with separate thresholds for worker category and gender

Local rule table, with per-country thresholds overriding the global anonymization settings

Consolidated audit trail across a communication round

So far, document activity within a communication round has required opening individual documents to inspect their audit information, rather than providing a consolidated view at the round level.

An Audit trail tab now appears alongside Round details under Planner > Documents > [communication round]. It brings tracked document activity into one searchable and sortable view, including imports, overrides, views, workflow step changes, releases, deletions, and other lifecycle events. Each entry records the timestamp, editor, action, document name, recipient, and event-specific metadata.

Entries can be filtered by editor, recipient, action type, document name, and execution date, and any column can be sorted. Selecting an entry for a document that still exists opens the Round details tab with the corresponding search criteria already applied.

The audit trail follows the existing security model and row-level access controls, so users see only events for workers and documents they are authorized to access. It expands the audit view without expanding access. HRBPs and Communication Managers can therefore investigate and monitor document activity across a communication round from a single, security-aware view.

Global Audit trail tab available for a communication round

Combined notifications and review queue access

Combined document notifications have opened to a general document view, so HRBPs and Communication Managers have had to locate the relevant communication round, workflow status, and document population themselves.

With this release, combined notifications open directly in the corresponding workflow context. For an HRBP, a notification for documents ready for HRBP review opens Planner > Documents > [communication round] > HRBP, filtered to the HRBP Review status. For a Communication Manager, a notification for documents awaiting communication review opens Planner > Documents > [communication round] > Communication manager, filtered to the Document Review status.

When a user has both roles, the destination is determined by the notification they open, taking them to the appropriate workflow view and document population without requiring manual filter selection.

This makes combined notifications directly actionable by taking users to the communication round and review queue relevant to the notification.

Consistent filter-clearing and empty states across document views

Until now, filtering and search behavior across Documents and Communication rounds was inconsistent in the Planner, with no standardized way to return a view to its default state.

A standardized Clear filters action is now available in the communication round selection, HRBP communication round, and communication manager communication round views. It resets both applied drop-down or tag-based filters and active search keywords in a single step, regardless of how the view was narrowed.

We have also standardized empty states for searches and filters. When no documents match the current criteria, the interface makes clear that the result comes from the active filters or search rather than from an empty dataset.

Together, these improvements make document views easier to reset and provide clearer feedback when no matching records are found.

Data Foundation

Currency on calculated fields and referenced entity details

In previous versions of PaySuite, calculated fields with numeric results did not carry their own currency, so a compensation round consuming the result required a separate Currency column. Additionally, the details drawer did not show the configuration of entities referenced by a calculated field.

We have enabled administrators to configure numeric calculated fields as monetary amounts in Workbench > Data Management > Calculated Fields. In the calculation workspace, there is a Number (currency) drop-down option, with the following currency sources: Fixed currency, applying the same currency to every worker; Entity field, which takes the currency from a worker's ContractedCompensation or PaidCompensation element; or Reference based, meaning the currency provided by the snapshot. The resulting snapshot value includes both the calculated amount and its currency. The calculated field details drawer also displays the configuration of its referenced entities.

These changes simplify the setup of monetary calculations and make it easier to trace how a calculated field gets its values, particularly when those values are consumed by compensation rounds.

Calculated Fields currency drop-down

Audit logging for revision cleanup

Revision cleanup runs have not generated audit records, making it impossible to trace a deleted revision or the cleanup run that removed it after the fact.

An audit event is now created when a revision cleanup run reaches a terminal state, including successful, failed, errored, and canceled runs. Each event logs the tenant, timestamp, affected entities, number of rows deleted, run result, and job status.

This enhancement provides administrators with a traceable record of cleanup activity. It also helps investigate unexpected data removal and supports operational and compliance monitoring.