beqom PaySuite 26.0 - Feature release notes
This article details the latest improvements introduced in version 26.0 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Compensation Management
Custom entity display names in data point tables
Data point tables in compensation rounds now display human-readable names of custom entities instead of their technical schema names. This makes configuration screens clearer and more consistent with how entities are defined in Data Management. For example, a field previously shown as WorkerExtension - ExternalId now appears as Worker Extension - External Id. The same resolved names apply to Entity filter tags; duplicate entity entries no longer appear, and platform-calculated fields display a calculated field label. No additional configuration is required, because display names follow the Data Management naming.
The change covers the Column configuration tab in the Team planner view step and the Payroll data drop's Data entities & sources panel within Workbench > Compensation Management > Compensation Rounds. Both of these spaces share the same data point table. Standard system-provided entities have been unaffected and continue to display as before.
Importantly, the custom entity must be published (Active) and added to the round's data model for its display name to appear.
Calculated fields from the data model in compensation rounds
With this release, compensation rounds support calculated fields, which are formula-based fields created and managed in Data Management. Once the administrator attaches a data model to a round, calculated fields become available end-to-end as first-class data points. They behave identically to standard data model fields across every feature in Compensation Management.
In Column configuration under Workbench > Compensation Management > Compensation Rounds > Team planner view, calculated fields offer the same options as other data model fields: a visibility toggle, display name editing, and conditional formatting. They are available in the autocomplete feature of all calculation editors, including calculated columns, proposal management, eligibility, and the calculation workspace. Calculated fields also appear in validation reports, Planner and Payroll data drop exports, and the Round Management portal. Duplicating a round copies the Calculated Field column configuration from the source round.
In Compensation Management, calculated fields are disabled by default. The Compensation Admin enables them and can edit their display names to match internal terminology. The system pre-computes values at snapshot creation; managers and HRBPs see the results in Planner > Compensation but cannot edit them, preserving the underlying data model logic. This gives Compensation Administrators a single, centrally governed source of data driven by formulas across every aspect of the round, with no duplication of configuration.
Calculated field available for use in Column configuration
Demo
New Compensation Advisory and Auditor roles
We have added two new operational roles in Compensation Management: Compensation Advisory and Auditor. Both are attribute-based roles scoped via security groups rather than the organizational hierarchy, enabling compensation responsibility to be delegated based on attributes such as country or legal entity. Within their defined scope, users holding either role can edit compensation proposals, approve, reject, and add notes, subject to the workflow step configuration.
In Workbench > Compensation Management > Compensation Rounds, both roles are selectable as actors in round access, stage, and workflow step configuration, alongside HRBP, Comp Manager, and Comp Manager +1. In Planner > Compensation, the roles appear in the View as drop-down list only when they belong to the current active stage, with the worker list, Audit trail, and Individual view filtered to the user's scoped population. Notes are visible whenever the user has Planner access, including in read-only steps. However, a role not configured as an actor in the round cannot see the relevant workers and therefore cannot add or delete notes for them.
Both roles follow the existing CSV upload mechanism and behave consistently across the full round lifecycle.
Notably, in rounds that exist at the time of deployment, the Compensation Advisory and Auditor roles are present but disabled as actors, with no permissions granted retroactively. In rounds created after this release, both roles are enabled by default.
Selectable Compensation Advisory and Auditor roles in the round editing form
Demo
Browse by selection applied to the Planner Excel export
In version 26.0 of the application, the Planner Excel export respects the Browse by option selected in the Population panel. This way, the exported file matches exactly what the user sees in the worker grid within Planner > Compensation.
Previously, the export reflected the grid filters but not the Browse by drop-down, which could result in the exported data including workers not visible in the grid. Currently, the export combines both grid filters and the active Browse by selection when generating the file, and applies to both Export current page and Export all pages. The feature is available to any role with Planner access.
Date type for calculated columns
Calculated columns now support a Date return type, completing the set of available types alongside Decimal, String, and Boolean within Workbench > Compensation Management > Compensation Rounds > Team planner view. Global Compensation Admins and Compensation Admins can create calculated columns whose formula evaluates to a date – for example, a computed effective date, anniversary date, or target review date – without encoding dates as strings. When Date is selected as the column type, the formula builder validates the return type on Apply; a type mismatch is rejected with an inline error. As with all other types, the column type cannot be changed once saved.
In Planner > Compensation, Date calculated columns are read-only and display values using each user's date formatting settings, which is consistent with all other date fields. No time component is shown; null or unevaluated results render as an empty cell. The columns support filtering and sorting: ascending order sorts oldest to newest, descending – newest to oldest, with null values sorted lowest. Date calculated columns are available as a source field in conditional formatting and as a reference in other calculated column formulas and eligibility formulas. They are also included in Payroll data drop and Planner Export outputs. Dependency protection applies: a Date calculated column cannot be deleted while referenced by another formula or rule.
Percentage format for Decimal custom and calculated columns
Global Compensation Admins and Compensation Admins can currently flag Decimal custom and calculated columns as percentage fields in Workbench > Compensation Management > Compensation Rounds > Team planner view. With the Percentage toggle enabled, values display with a %, and when a manager or HRBP types 10 in the Planner to mean 10%, the value continues to be stored as a decimal (0.1). This makes percentage-type compensation values far more readable and eliminates manual conversion. The toggle is off by default and existing Decimal columns are unaffected.
Percentage and Currency are mutually exclusive: enabling one disables the other. In Planner and Payroll data drop exports, values always appear as decimals regardless of the toggle, so any systems or calculations that consume the exported data continue to work as before.
Proposal management for custom input columns
With this release, proposal management targets custom input columns, not just compensation elements. In Workbench > Compensation Management > Compensation Rounds > Team planner view, administrators can configure a rule that pre-populates a custom input column with a proposed value. Compensation managers and HRBPs can then review and adjust this value in the Planner. Both existing configuration methods are supported: Use an existing value and Calculate using a formula. The source field or formula must resolve to the target column's type, or a validation error will block the save.
Pre-populated custom input cells behave exactly like compensation element proposal cells, with a proposal icon, tooltip, and a restore-to-proposed action. Managers and HRBPs can keep, edit, clear, or restore the proposed value within their existing edit scope, and edits follow the same Draft and Pending draft workflow as other custom input changes. If the source field is empty or the formula fails, the cell stays empty and the user can enter a value manually. A custom input column used as a proposal management target cannot be deleted and its type cannot be changed while the rule references it.
Crucially, proposals are calculated once at publish or republish and do not update automatically when source data changes mid-round.
Advanced calculation engine for Budget rules
From now on, Budget rules run on the same advanced calculation engine used for calculated columns and Eligibility in Workbench > Compensation Management > Compensation Rounds. We have replaced the previous two-block builder with a single formula editor that supports the full calculation workspace. Per-worker filtering now lives inside the formula itself, using conditional expressions. In budget formulas, Global Compensation Admins and Compensation Admins can reference a far broader field set than before, including data model fields, compensation element input fields, custom input fields, calculated fields, and the outputs of other rules such as Guidelines, Guaranteed amounts, Eligibility, and other Budget rules, as well as conditional formatting outputs.
Budget allocation re-evaluates in real time when any referenced field changes value in Planner > Compensation, keeping budget figures accurate as managers or HBRPs edit data. Existing budget rules are automatically migrated to the new engine, preserving their original behavior. Dependency protection extends to budget formulas: any field or rule output referenced in an active budget formula cannot be deleted or disabled.
Using advanced calculations in the Budget step of the compensation round configuration wizard
NULL() function in the calculation engine
In PaySuite version 26.0, the advanced calculation engine includes a NULL() function that lets a formula return an explicit no-value result. This is especially useful in the Guidelines step within Workbench > Compensation Management > Compensation Rounds, where returning NULL() causes the system to fall back to the guideline's configured default value rather than treating 0 or an empty string as a real result. NULL() requires no input, is compatible with any expected return type, and works seamlessly with existing null-handling functions such as ISNULL and COALESCE. It is available across all compensation round formula steps (Eligibility, Budget, Guidelines, and Bonus calculation equation) in the Conditional category of the formula editor.
"Unable to calculate" state in the Planner
We have introduced a clear, consistent error state in Planner > Compensation whenever a Planner calculation fails to produce a result, for example, due to a division by zero, missing referenced data, or a type mismatch. This allows compensation managers and HRBPs to distinguish a genuine calculation failure from an empty cell. It also provides guidance on how to resolve a given issue.
Read-only cells display "Unable to calculate" in red with a tooltip explaining that the field is calculation-driven but could not produce a result. Editable cells show a red #ERROR! indicator and can still be edited, with a tooltip prompting the user to enter a value manually. Typing a value into an error cell immediately replaces the indicator. Errors cascade through dependent calculations, so any field that references a failed cell also resolves to the error state. Column aggregates and rollups exclude affected rows, showing the partial result from valid rows rather than treating failures as zero.
Usability enhancements
This release includes three usability enhancements to the Planner > Compensation and Column configuration in Workbench > Compensation Management > Compensation Rounds:
When a column group is deleted in Column configuration, its member fields now stay in the position the group previously occupied rather than moving to the end of the column list. This eliminates manual rework when reorganizing columns after removing a group.
The guideline validation icon in the Planner grid has moved from the right of the cell to the left. Numbers now keep a consistent position whether or not a guideline flag is present, making values easier to scan and compare down the column.
In the Planner, the Budget panel's expand/collapse icon is currently fixed in its top-right corner and remains visible regardless of horizontal scroll, keeping it reachable at all times.
Demo
Pay Transparency
Aggregated reminder notifications for HRBPs
We have enabled configurable reminder notifications to provide an aggregated summary of pay information requests that require attention. Unlike instant notifications, which trigger on each individual request submission, reminders summarize pending work across three categories: new requests, requests approaching their deadline, and overdue requests. This helps HRBPs proactively manage their workload and maintain Service Level Agreement (SLA) compliance without manually monitoring the queue.
Notifications are delivered both in-app and by email, and are sent only when at least one request matches the configured criteria. When the queue is clear, the system does not generate any reminders. It determines recipients automatically based on existing role assignments and attribute-based access control, ensuring each HRBP receives notifications only for workers within their area of responsibility. Administrators can configure the reminder frequency independently as daily, weekly, or monthly under Workbench > Platform Setup > Email Notifications > Documents > Reminders. Reminder calculations respect both global SLA settings and any country-specific SLA overrides.
In-app notification for overdue requests
Demo
Improved pay information experience
We have implemented several usability improvements to simplify the daily management of pay information requests in Planner > Pay Information and documents in Planner > Documents:
Closed requests are now hidden by default, with a toggle to show them when necessary, helping HRBPs focus on active work without visual clutter.
Sorting is currently available in any field in the pay information request grid, with the Status column sorted by workflow order (New, In progress, Pending release, Closed, Closed without document) rather than alphabetically, offering a more intuitive representation of request progression.
Planner also remembers previously applied filters between sessions, automatically restoring them when users return to the page, reducing repetitive filtering, and increasing navigation efficiency.
When HRBPs have multiple documents selected for a bulk action and apply a filter change that would clear their selection, a warning is displayed before proceeding, preventing accidental data loss. Users can choose to continue and clear the selection or cancel the filter change to preserve it.
Show closed requests toggle
Demo
Flexible document template formatting
Document templates in Workbench > Pay Transparency > Document Templates now support configurable formatting settings that control how numeric and date values are rendered during document generation. Each template can define its own thousands separator, decimal separator, decimal precision, and date format, allowing organizations to follow regional conventions within the same tenant without requiring separate system configurations. For example, a template for France can use French formatting while one for Switzerland uses Swiss conventions.
Formatting settings apply only during document generation. The document preview continues to display raw source values to assist administrators during template design and validation.
New configurable section in the Document template details step of document template creation
Demo
Enhanced bulk operations
Two enhancements bring greater transparency and control to bulk operations. In Planner > Documents, the size of each document is now displayed directly in the document list. Before generating a ZIP archive, the system calculates the total size of the selected documents and alerts the user when the combined size exceeds the 1 GB limit. This allows for better selection management, preventing the unnecessary processing of oversized downloads.
Moreover, in Planner > Pay Information, Bulk actions also include downloadable execution logs whenever processing completes with errors, such as non-unique mapping configurations, missing template variables, or lack of permissions for the selected communication round. These logs are available when viewing a specific action in a drawer. With the Export log details button, administrators can export a CSV file containing detailed information for every failed request, making it significantly easier to identify and resolve individual issues.
Document size displayed in the Planner > Documents > Document name column
Bulk action details drawer with an option to export log details
Demo
Analytics
The EU Pay Transparency Directive gives workers the right to ask how their pay compares to peers doing the same or equivalent work. Answering those requests consistently, and backing each answer with sound figures, has been hard to do at scale.
This release adds a set of Pay Transparency reports built around that right. Comparison metrics are standardized using averages, medians, and categorized distance indicators across compensation components, and they follow the same calculation logic as Pay Analytics Pay Explainability, so figures stay consistent across products.
Phase 2 brings three reports:
A Pay Explainability report that shows how a worker's pay sits against male, female, and overall group averages and medians, with the percentage difference and a standardized distance category.
A bulk data report giving a single tabular view of pay transparency metrics across workers and compensation components, with filtering and export for analysis, compliance, and auditing.
A Right to Request report (Article 7) that lets organizations respond to a worker's request with their own pay information alongside aggregated comparison metrics for peers performing equal or equivalent work.
Every report uses the most recent pay record per worker, recalculates metrics consistently when filters are applied, and respects role-based access and confidentiality rules. All three are read-only, so compensation data is never changed.
This gives HR and compliance teams a clear, repeatable way to meet Article 7 obligations and to explain pay decisions with confidence.
Data Foundation
This is an note/information message.
Please note that the feature "Calculated fields" was not included in the 25.1 release notes by mistake. For more information, refer to beqom PaySuite 25.1 - Feature release notes.