beqom PaySuite 25.0 - Feature release notes
This article details the latest improvements introduced in version 25.0 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Compensation Management
Boolean type for calculated columns
We have introduced a Boolean return type for calculated columns in the compensation round configuration wizard. This allows Global Compensation Admins and Compensation Admins to create indicator columns in the Planner that flag whether a worker’s proposed increase falls outside a guideline or whether any custom condition is met. Previously, only Decimal and String could be selected as column types, even though the underlying calculation engine already supported Boolean outputs.
To configure a Boolean calculated column, administrators should go to Workbench > Compensation Management > Compensation Rounds > Create/Edit comp round > Team planner view > Create > Calculated column, choose Boolean from the Type drop-down list in the Column details section, and build the formula as usual.
With the Boolean type selected, currency and decimal precision options become automatically hidden, keeping the configuration drawer unambiguous. Admins can then define a formula using the formula builder. On applying the formula, the engine validates that its resolved return type matches Boolean. If it does not, the application displays an inline error. As with Decimal and String columns, the Boolean type cannot be changed after the user saves a calculated column.
In the Planner, Boolean calculated columns appear as read-only checkbox cells: checked when the formula evaluates to true, unchecked when it evaluates to false, and empty when the result is null or cannot be evaluated. For improved decision-making during planning, managers can filter rows by true or false values and sort the column in ascending or descending order, with null values treated as the lowest value.
Boolean calculated columns integrate fully with the existing feature set. They are available as a source field in conditional formatting rules and can be referenced in other calculated column formulas or eligibility formulas across the round.
Boolean drop-down option for a calculated column
Increased calculated columns limit per compensation round
With this release, we have raised the maximum number of calculated columns allowed per compensation round from 20 to 50. This supports large organizations with sophisticated compensation models and complex calculation logic, while keeping the familiar column configuration experience unchanged.
The new limit applies automatically to both existing and newly created compensation rounds, with no migration or reconfiguration required. When a round reaches 50 calculated columns, the Calculated column option in the Create drop-down list is grayed out and a tooltip mentions the new limit. Enforcement is consistent across both the front-end UI and back-end validation.
Permissions remain unchanged, and only Compensation Admins and Global Compensation Admins can create calculated columns.
Display of invalid stored values in custom drop-down cells
The Planner now clearly communicates when a worker’s custom drop-down cell holds a value that was removed from the column’s option list after republishing the compensation round. Previously, such cells appeared empty, giving the impression that data had been lost. Currently, the stored value remains visible with a clear indication that it is no longer available, increasing transparency and offering users a clear, guided path to resolution.
The enhancement applies to single-select, String-type columns. To maintain data integrity, the back-end stored value remains untouched until the user explicitly edits the cell, and all edits follow the standard pending draft and approval workflow for the round.
The workflow is as follows: a Compensation Admin or Global Compensation Admin removes one or more options from a custom drop-down column via a pending draft and republishes the round. Workers whose stored value matches a removed option are detected automatically when the Planner renders the cell, and a warning icon and the stored value in strike-through styling are displayed. Hovering over the cell shows a tooltip with the relevant explanation. When Compensation Managers or HRBPs open the drop-down on an impacted cell, the invalid value appears at the top as a disabled, non-selectable entry, with all currently valid options listed below. They can resolve the cell by selecting a valid option or clearing the value. Once resolved, the invalid value is permanently locked out of that specific cell, preventing accidental reselection. Lock-out applies per cell and does not affect other workers.
Planner calculations
Planner calculations is a new capability that links editable Planner fields via formulas, enabling the system to automatically recalculate dependent values in real time whenever the user edits a connected field. Unlike standard calculated fields, Planner calculation fields remain directly editable while adhering to the configured recalculation rules. This gives Compensation Admins and Global Compensation Admins precise control over how fields interact during the planning process.
The feature is accessible via a new Planner calculations tab under the Team planner view step in the compensation round configuration wizard. Via the Add rule button, administrators define rules in the Add rule drawer, specifying a rule name, a target field to be recalculated, a trigger field whose edit initiates recalculation, and a formula whose result type matches the target field. Custom columns of input type and advanced calculation components are supported in formula definitions. Saved rules become automatically grouped into cycles based on the target field to ensure cohesive behavior, and the system prioritizes the most recently applied rule when multiple rules affect the same field.
A Coverage map is available on any target column, visualizing which trigger fields are covered and highlighting gaps in recalculation logic. New rules can be created directly from the Coverage map to fill identified gaps. Where compensation elements include both Increase Amount and Increase Percentage, the system auto-creates the corresponding rules to maintain consistency.
After round publication, Planner users can edit linked fields, and the system automatically recalculates the related target fields in real time, reducing manual effort and the risk of inconsistent values across associated compensation fields.
Planner calculations tab
Planner calculations rule editing
Demo
Localization in the digital reward statement
We have enabled granular localization for the digital reward statement (DRS). As a consequence, administrators can deliver translated compensation content to workers based on their preferred language, which improves user engagement and comprehension.
To configure translations, admins should navigate to Workbench > Platform Setup > Passport > Edit digital reward statement, click Manage translations under Settings, and then click Add translation to add a new language. English (United States) is the default language, and additional languages are selectable from a drop-down. Translations can be applied to widget headers, section descriptions, and drop-down options, like the ones available in the Pay information and Compensation history widgets. Any element left without a translation automatically displays in the default language, so administrators can translate only the elements that matter without disrupting the rest of the DRS.
When the user updates their language setting, widgets are rendered in the translated language. Drop-down options within the widgets follow the same translation logic, ensuring a consistent localized experience across the entire statement.
Language configuration for the DRS
Demo
Data Foundation
Global and local worker categories
In version 25.0 of the application, we have expanded the Workbench > Data Management module with the Worker Category Management section under User Segmentation. As dynamically generated classification strings built by combining selected worker attributes, worker categories provide a consistent, configurable basis for grouping and segmenting workers. Importantly, only configuration-level administrative roles have access to this new feature.
The foundation is the global worker category, a tenant-level default configuration that most workers use. With all configuration changes tracked in the Audit trail, administrators select the worker fields to include, choose a separator character (such as |, _, -, /, or :) to join the values, and define how blank values are handled: skipped, retained, or replaced with a custom one.
Where the global configuration is not sufficient for a diverse workforce, administrators can define local worker category overrides that apply different field selections, separators, and blank value handling to specific worker populations. A population can only be assigned to a single local worker category configuration, and populations should not overlap. When local configurations exist, they automatically take precedence over the global configuration for workers who match the linked population; all other workers fall back to the global configuration.
In addition to the global and local configurations, users who create snapshots can define a custom worker category directly during snapshot creation via Workbench > Data Management > Data Modeling > Snapshot Manager. This custom mode allows users to select fields specifically for that snapshot, generating a snapshot-specific category structure while bypassing both the global and local configurations. This is intended for one-off analytical scenarios where the standard configuration does not apply.
Because categories are calculated at snapshot creation, existing snapshots stay unchanged and past analysis remains reproducible. This ensures historical consistency and auditability of analytical results. Also, generated categories can be used in reporting tools, CSV exports, downstream analytics, platforms such as Power BI, snapshot comparisons, and filtering and grouping scenarios.
Worker Category Management section
Edit local worker category form
Demo
Pay Intelligence
New Pay Transparency Bulk Data report
Looking at pay transparency one worker at a time is fine for answering a single request, but it does not help when the question is about the whole workforce. Regulatory submissions and broad analysis need every figure in one dataset, not a report opened person by person.
The platform now offers a Pay Transparency Bulk Data report: a single tabular dataset covering all pay transparency metrics across workers and compensation components. For each component it brings together the worker value, the male, female, and overall group averages, and the percentage difference between the worker value and those group averages. The figures can be filtered and exported, which makes the report suited to large-scale analysis, regulatory submissions, and auditing.
The report uses the same calculation logic as the individual Pay Transparency reports, so the numbers match across both. It is read-only, with no way to change compensation data, and it follows existing role-based access and confidentiality rules. This gives HR and compliance teams one consistent source for pay transparency reporting at scale.