beqom PaySuite 25.1 - Feature release notes

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

Compensation Management

Date inputs for Planner calculations

Planner calculations now support Date custom columns. This capability extends real-time recalculation to scenarios driven by effective dates, review dates, or deadlines. It lets administrators define rules that target date columns directly, or that trigger recalculations when a date column changes.

Configuration follows the same path as other Planner calculation rules: Workbench > Compensation Management > Compensation Rounds > Create/Edit comp round > Team planner view > Planner calculations > Add rule / Edit. When the user selects a DateCustomColumn as a Target field, the formula editor sets the expected return type to Date and validates the formula on Apply; a type mismatch is rejected with an inline error. Date custom columns can equally be used as a Trigger field or as inputs within a Formula.

Planner > Compensation displays recalculated date values according to each user’s global or personal date-time formatting settings, which maintains consistency. Target cells remain editable after a rule runs, and values are suggested rather than enforced, so managers can always override them. As with other column types, a Date custom column referenced by a rule is protected from deletion until the user removes or updates the referencing rule.

DateCustomColumn as a Trigger field in the Add rule drawer

LOOKUP function helper in the Formula builder

We have introduced a visual helper in Workbench > Data Management > Calculated Fields > Formula builder. The feature facilitates building and modifying LOOKUP formulas without having to memorize source table names, key names and types, or return columns. An icon appears next to the LOOKUP function in the builder, opening a dialog that walks users through the process in three steps: selecting the source table to look in, specifying how to find the right row, and choosing what to return.

The Source drop-down lists all reference tables available in the current formula context. Once a source is selected, its identifying fields are rendered as key inputs. For each field, users can choose a matching property from a filtered list that shows only properties whose return type matches the key's type, grouped by namespace with type indicators. Alternatively, they can write a custom expression directly. The return column is optional, and leaving it empty returns the entire matched row. A live Generated formula preview updates in real time as selections change, giving users confidence that the formula matches the intended lookup.

The helper works for both creating new LOOKUP formulas and editing existing ones. When opened on an already configured lookup, it pre-fills all fields automatically. If the existing formula proves too complex to read, the helper opens blank so the user can start fresh. All required fields must be completed before the formula is applied, with a clear error banner listing any gaps.

LOOKUP function in the Formula builder with the function builder prompt

Demo

Planner grouping and views

With this release, the Planner offers a new browse-by capability. Administrators control which grouping dimensions are available; managers and HRBPs use a dedicated Population panel to browse workers by enum fields, organizational hierarchies, or reporting chains, and then filter the worker grid to the groups they select.

Administrators configure Browse-by options under Workbench > Compensation Management > Compensation Rounds > Create/Edit comp round > Team planner view > Planner add-ons. Seven system options are available: Line Manager, Matrix Manager, Compensation Manager, Communication Manager, Organization, Legal Entity, and Cost Center, with only Line Manager enabled by default. Custom options can be built from any enum in the round’s data model, with auto-filled display names, drag-and-drop reordering, and enable/disable toggles. At least one option must be enabled to save the configuration. For rounds in the Ready, In progress, or Closed status, the configuration remains read-only.

In Planner > Compensation, the Population panel with View as and Browse by drop-downs appears on the left, expanded by default and collapsible to maximize the grid's width. Depending on the selected browse-by dimension, the panel renders differently: enum fields as a flat alphabetical list of groups with worker counts; organizational hierarchy fields as a collapsible nested tree scoped to the relevant part of the organization; and employee link fields as a worker-to-worker tree following the management structure. Workers with missing or unresolved values are grouped under the Unassigned row, which is hidden when empty, as are all other empty groups.

Checking one or more groups filters the worker grid to the matching workers. For enum groups, any worker matching a checked value is included; for organizational hierarchies, selecting a node includes everyone beneath it; for employee links, only the directly checked workers are included. These selections combine with any other active filters, enabling precise, targeted views of the workforce.

Browse-by options in Planner add-ons

Population panel with Browse byCost Center

Demo

Budget widget with applied active filters

In version 25.1 of the application, the budget widget in Planner > Compensation respects the active filters, corresponding to the worker population shown in the grid. In this way, the numbers stay trustworthy and consistent as managers and HRBPs narrow their view using Browse by groups, the Filters, or the worker search box. The three sources are combined with AND logic: a worker contributes to the budget only if they satisfy all active criteria simultaneously; a source with no active criteria does not restrict the others. When no filters are active, the widget reverts to full-population aggregation.

Filtering applies the same rules as the Population panel described above. The per-element budget popover reflects the active filter set across all four values: Budget, Allocated, Eligible workers, and Remaining. Worker value updates recalculate against the currently filtered population, with budget consumption determined by the compensation element configuration. Aggregates span the full matching population regardless of the current page.

Monetary type for Decimal custom columns

We have provided full currency context for Decimal custom columns. Consequently, administrators can create monetary columns that store and display amounts alongside a currency, which proves ideal for one-off adjustments, manual bonuses, and stipends. This mirrors the currency capability already available for calculated columns, ensuring a consistent experience across column configuration.

The capability is available in Workbench > Compensation Management > Compensation Rounds > Create / Edit comp round > Team planner view > Column configuration. With the Currency toggle on during Decimal custom column creation or editing, the Currency source selector appears with three options: Data model (per-worker currency drawn from a referenced field), All currencies (a single fixed currency applied to everyone), or Comp round currency. The toggle and source become read-only after saving, in line with the calculated column logic. Existing Decimal columns are automatically migrated, and their Currency toggle is set to off. To add monetary behavior in such cases, a new column must be created, with data migrated manually.

In Planner > Compensation, monetary custom column cells display an amount with its currency and participate in the existing round currency display toggle, switching between the worker local currency and the comp round currency. Filtering and sorting respect the active currency view. Monetary custom columns are also available as a referenced field in conditional formatting rules, calculated column formulas, eligibility formulas, and proposal management, and are rendered in Payroll data drop and Planner exports as a currency code followed by an amount in a single cell.

Currency configuration for a Decimal custom column

Demo

Dynamic compensation elements in the Historical compensation widget

We have improved the Historical compensation widget in the digital reward statement (DRS). Currently, it sources its compensation elements dynamically from Data Foundation, replacing the previously hardcoded Salary and Bonus options. The widget reflects the organization’s actual compensation structure, both in the Workbench configuration and in the worker-facing statement.

In the DRS configuration under Workbench > Platform Setup > Passport > Edit digital reward statement, the Compensation elements drop-down in the Compensation history section now lists all elements loaded into Data Foundation, using a given element’s name as configured there. Selected elements appear as removable tags, each adding its own per-element configuration sub-section with the Number of events setting (5, 10, 15, or 20). The Number of years setting remains shared across all selected elements, and at least one element must be selected to save. Saved entries for elements that have since been removed from Data Foundation are automatically cleaned up and no longer appear in the configuration or in the worker's DRS.

In Passport > Compensation, the Comp element drop-down is populated with the enabled elements. Selecting an element updates the Events history bar chart and the change events table. If an element has no data for a given worker, the widget shows its empty state.

Compensation elements sourced dynamically from Data Foundation in the DRS configuration

Demo

Pay Transparency

Instant notifications for new pay information requests

HRBPs can now receive immediate notifications when a new pay information request is submitted for a worker within their area of responsibility. Notifications are delivered through both in-app and email channels as soon as a request is created or imported via API. They include details such as the request ID, worker name, request creator, and submission date. As a consequence, response times become shorter and requests are less likely to be missed.

Administrators enable and configure the feature under Workbench > Platform Setup > Email Notifications > Documents, where a new Instant notification toggle is available under the New pay information request submitted section.

In-app notification for a new request

Demo

New pay information request workflow statuses

We have added two new workflow statuses for pay information requests, such as those appearing in Planner > Pay Information. The statuses replace the previous alert-based indicators for better visibility into the lifecycle of such requests. Pending release applies when a request is closed with an attached document that cannot yet be released to the worker, either because a release approval workflow is enabled for the selected communication round or the HRBP does not have release permission for it. Closed without document applies when an HRBP closes a request without providing a pay information document.

Statuses update automatically as users act on requests: releasing a document sets the status to Closed; unreleasing one reverts it to Pending release; deleting an attached document returns it to In progress; and closing without a document sets it to Closed without document. This enhancement makes it easier to identify requests requiring action and improves the accuracy of SLA monitoring and reporting.

Pending release and Closed without document statuses for pay information requests

Demo

Dynamic Communication Manager role assignments

With this release, Communication Manager access within communication rounds can be assigned dynamically based on hierarchy configuration. This change removes the previous requirement to populate assignments manually through security import files. Under Workbench > Pay Transparency >Communication Rounds, in the Hierarchy step of the communication round configuration wizard, administrators select a hierarchy to drive round access and scope. The result is simpler administration, a more convenient setup process, and a lower risk of errors in security assignments.

Communication Manager access defined in the communication round configuration wizard

Demo

Role-specific notes in pay gap remediation

In PaySuite 25.1, we have enhanced auditability: users who hold multiple roles in the pay gap remediation process can clearly identify which role was active when a note was created. In Planner > Pay Analysis, the system distinguishes between notes created by an HRBP in the Planner and notes created by a Pay Analytics Administrator in Workbench, ensuring that note visibility rules are correctly applied. The role label, HRBP or PayAnalyticsAdmin, is displayed under the author's name in each note, and users only see comments relevant to their assigned role. Collaboration between the two roles improves thanks to better separation of responsibilities, sensitive comments remain appropriately contained, and each note provides clear context for discussions, reviews, and remediation decisions.

Notes labeled by author role

Demo

Bulk download of communication round documents

From now on, multiple communication round documents can be downloaded as a single ZIP file. This makes the retrieval of large document volumes more efficient, simplifying preparation for audits and compliance activities. To use the feature, HRBPs and managers should go to Planner > Documents, check the relevant boxes next to their chosen documents, click the Bulk actions drop-down above the document table, and select Download. When configuring the download, users provide a file name and password. If duplicate file names exist, the worker identifier is automatically appended for uniqueness. The system then processes document packaging asynchronously, and it sends an in-app notification when the file is ready for download. Each document downloaded as part of a bulk operation remains individually traceable through the Audit trail.

Importantly, the maximum combined size of documents in a single bulk download is 1 GB, and generated files are available for 24 hours after creation.

Downloading documents in bulk in the Planner

Demo

Bulk actions for pay information requests

We have enabled the simultaneous processing of numerous pay information requests through the new Bulk actions workspace. The workspace takes the form of a dedicated tab under Planner > Pay Information, located next to the Requests tab, which remains the primary area for managing individual requests. The Bulk actions tab supports bulk document generation (Generate documents button) and bulk close and release (Close & release button), which saves time and eliminates repetitive manual work. When launching a bulk action, HRBPs are presented with a selection window that shows only the requests eligible for that action: New or In progress requests for document generation, and New or In progress requests with an attached document for close and release. Users can select individual requests or all eligible ones, apply additional filters to refine the selection, and choose whether to regenerate documents for requests with an attachment or skip them. Bulk operations are then processed asynchronously.

In addition, for increased transparency, the Bulk actions tab provides a dashboard with the total number of actions and their statuses: Not started, In progress, Completed, and Completed with errors. It also includes the Actions summary table recording the action type, the user who executed it, the number of requests included, initiation, start, and completion timestamps, the status, and the number of successful and failed requests. When a request is processed through a bulk action, its audit trail entry identifies it as part of a bulk operation, distinguishing it from individually processed requests.

New Bulk actions tab

Request selection window for bulk document generation

Analytics Hub

Pay Transparency - New worker right to request report (Article 7)

Under the EU Pay Transparency Directive, workers have the right to ask how their pay compares to peers doing the same or equivalent work. Answering those requests used to mean gathering figures by hand and assembling each response from scratch.

We have added an Individual Worker Report that produces this information in one place. For a given worker, the report shows their own pay for each compensation component alongside aggregated comparison figures for the relevant peer group: averages and medians for male, female, and overall groups, the percentage difference between the worker's pay and each benchmark, and a category showing how far their pay sits from it.

The report draws on the most recent pay record for each worker and recalculates consistently when filters are applied. It is read-only, so compensation data cannot be changed from it, and it respects existing role-based access and confidentiality rules so figures stay visible only to those permitted to see them. This gives HR and compliance teams a reliable way to meet Article 7 requests with consistent, defensible numbers.

Demo

Data Foundation

Calculated fields

The Data Management module in PaySuite now includes a Calculated Fields feature, available in Workbench > Data Management > Business Logic > Calculated Fields. Calculated fields let the Data Foundation Admin, Configuration, and Support professional roles define reusable formulas that derive new values from worker data and reference datasets directly within the Data Foundation. A calculated field can represent any derived attribute (eligibility flags, full names, prior-year compensation, etc.) without the need to rebuild the same logic for every use.

Formulas are built in a dedicated editor with the Return type selector, the Element library for inserting worker fields, other calculated fields, and reference entities, and a function library covering Math, String, Aggregation, Conditional, Date/Time, and Array operations. Continuous validation provides specific messages for invalid expressions, missing references, or type mismatches before publishing. Formulas can also look up values from reference tables using a guided LOOKUP helper.

For easy management, calculated fields follow a controlled lifecycle: Draft for active configuration, Published for use, and Deactivated to retire a formula without removing the historical record. Once published, a calculated field can be added to new or existing data models. When a snapshot runs, each formula in the data model is evaluated for every worker in scope and the results are stored as part of the snapshot output alongside standard worker data, ready for use in compensation rounds and other downstream processes.

Calculated Fields page in Data Management