beqomPaySuite 23.1 - Feature release notes
This article details the latest improvements introduced in version 23.1 of the beqomPaySuite application, their benefits for our end-users, and their principles of use.
Compensation Management
Auto-calculation of compensation in the Compensation in Numbers widget
With this release, we have enhanced the Compensation in Numbers widget, available in Passport > Compensation. It now calculates Total compensation, Total direct compensation, and Total indirect compensation on the fly, which eliminates the need to rely on static values. Previously, these totals were sourced from figures loaded manually by customers into fixed compensation elements (BQTCM1000, BQDC1000, BQIC1000). Currently, the widget computes them dynamically: it aggregates values from the full compensation hierarchy at the time the tab is opened. This feature completes the Compensation Management 23.0 release.
When a worker opens the Compensation tab, the widget automatically sums child elements under Total direct and Total indirect parent nodes to compute the overall Total compensation, with all values sourced directly from Data FoundationCompensation fields. All amounts are assumed to be in the same currency as the worker's primary currency, and calculations exclude compensation elements in a different currency, since currency conversion is not performed. The widget always displays the logged-in worker's own compensation data, which means that managers do not see their reports' data there. Recalculation occurs on tab open only; therefore, the system does not show mid-session data changes until the tab is reloaded. If the compensation tree cannot be built or if currency mismatches are detected, the system falls back to retrieving values from the existing fixed compensation elements. The widget also appropriately handles cases where compensation values are missing or not configured.
Total compensation, Total direct compensation, and Total indirect compensation auto-calculated in Passport
This is an note/information message.
The feature does not support editing compensation values from within the widget.
Enabling/disabling the Compensation in Numbers widget for the digital reward statement
In version 23.1 of the application, administrators can now control the visibility of the Compensation in Numbers widget directly from Workbench > Platform Setup > Passport > Compensation > Digital reward statement. This lets them decide whether workers see consolidated compensation data in their Digital Reward Statement (DRS) without requiring a system restart or redeployment.
A new toggle to enable or disable the widget is available under the Main content section of the Edit digital reward statement page.
When disabled, the widget, including Total compensation, Total direct compensation, and Total indirect compensation, is fully hidden from the worker-facing DRS page, with no empty space or placeholder shown in its place. Importantly, disabling the widget does not affect the underlying data – other widgets that depend on the same compensation codes continue to function normally. When enabled, the widget works as usual. The toggle state takes effect immediately, with visibility enforced securely on the server side. The toggle setting is saved within the DRS configuration, which ensures it persists across sessions.
If a worker has compensation elements in multiple currencies, the existing behavior of hiding the consolidated chart and ratio is preserved regardless of the toggle state. Currency conversion logic within the widget remains unchanged. Compensation in Numbers relies on the auto-calculation described above.
Toggle for the Compensation in Numbers widget
Enabling/disabling the Compensation Breakdown widget for the digital reward statement
From now on, administrators can also control the visibility of the Compensation Breakdown widget using the same configuration area. They have the option to choose whether to show a detailed breakdown of individual compensation elements in the worker's DRS.
The Main content section of the Edit digital reward statement page includes a new toggle, as well as a field to customize the Compensation Breakdown header.
Toggling off hides the entire widget from the DRS page, leaving no empty space or placeholder. However, it does not interfere with compensation codes used by other widgets. After toggling on, the widget displays individual compensation elements as before. The system implements the toggle state instantly and retains it across sessions within the DRS configuration. Visibility is managed securely on the server side.
The toggle applies to the Compensation Breakdown widget as a whole – it does not allow for controlling the visibility of specific compensation elements in the widget.
Toggle for the Compensation Breakdown widget
This is an note/information message.
Changes to the content or data logic of the widget are out of scope for this release.
Enabling/disabling the Historical Compensation widget for the digital reward statement
With the new release, administrators can enable or disable the Historical Compensation widget. They can also configure its content within Workbench > Platform Setup > Passport > Compensation > Digital reward statement. In this way, they gain granular control over whether workers see their historical salary data in their DRS.
A master toggle is available under the Main content section of the Edit digital reward statement page.
Once the toggle is on, several sub-configuration options become available: a customizable Section header (defaulting to Historical Compensation), the Number of years of compensation history to display (default: 3), a selection of Compensation elements (default Salary, as well as Bonus, where at least one must be enabled), and the configurable Number of events shown for both base salary and bonus (default: 5). Adding compensation types beyond these two and currency conversion for multi-currency historical data are out of scope for this release.
On the worker-facing DRS page, the widget displays the Comp element drop-down list allowing workers to switch between enabled compensation types, the Events history bar chart showing compensation values over the configured number of years, and a change events table listing individual events with Date, Contracted Salary, Currency, and % Change, where the number of rows matches the configured Number of events for the selected type.
When the toggle is off, the DRS page does not display the widget and does no replace it with an empty space or placeholder. All configuration values take effect without a restart, and server-side enforcement ensures secure visibility control.
Thanks to these four improvements, compensation data is always accurate and up to date. Administrators have flexibility to tailor the Passport experience to organizational needs. They can also see the results of their configuration immediately. Workers, on the other hand, benefit from a clear, personalized view of their compensation package.
Toggle for the Historical Compensation widget
Performance Management
Extended search on shared goals
The Goals tab in Passport now offers an extended search functionality. The update makes it easier and faster to find relevant goals in the Shared goals category. Users can search not only by goal title, but also by the goal owner's name, including first name and last name. This allows them to quickly locate goals associated with a specific person.
This enhancement improves search accuracy and flexibility, reduces time spent navigating large goal lists, and aligns with user expectations to search by both content and people.
Shared goals searched by name
Reviews widget update – removal of rating display
With this release, we have simplified the Reviews widget in Passport and Planner by removing the display of the last review rating. Previously, the widget showed the rating from the latest completed review (for example, "Right on track"). Instead, the widget now displays a static, guidance-focused message. The message is neutral and consistent across Passport and Planner.
This change improves clarity and user experience, as it eliminates potentially confusing historical ratings. It also encourages users to engage in and focus on active review processes rather than past results.
New message in the Reviews widget
Data Foundation
Custom entities in Data Management
Version 23.1 of our application introduces custom entities, which allow administrators to define and manage their own structured datasets directly in Data Management. This enables extending the data model with customer-specific data that does not exist as a standard entity.
A custom entity is essentially a custom table that helps organizations store additional business data in a governed way. Internal mapping tables, organization-specific reference datasets, worker-linked enrichment data, and additional criteria for segmentation or classification illustrate what custom entities can represent. Unlike custom fields, which extend an existing standard entity, custom entities create an entirely new entity with its own schema.
This release makes it possible to work with custom entities in a clear workflow. Users can access the Custom Entities section under Workbench > Data Management to view all existing entities, search and filter them, understand their status (Draft, Active, or Deactivated), and navigate into entity details. Administrators can create new custom entities and define their full schema in one flow, including entity properties (such as Name and Effective dating), field definitions, data types (for example, String, Number, or Boolean), required and optional fields, business keys for record uniqueness, and references to existing entities and enums. Entities are created and saved in the Draft state, giving administrators time to fully configure them before activation.
Custom entities have a controlled lifecycle: the Draft state allows for configuration and editing, Active makes the entity ready for use after publishing, and Deactivated retains the entity for reference without keeping it active. Once the schema has been finalized, entities are published and become available across the platform. Publishing is a direct action and locks the entity structure. After publishing, administrators upload data through CSV or API. They can use templates provided to guide the correct data structure. Then, they access and review custom entity data in the Data Viewer, where entities appear clearly identified as custom.
Custom entities also play a role in supported downstream scenarios. When linked to worker data, they can be leveraged in population filtering and selection, worker category configuration, snapshot generation, and data modeling.
As part of the Data Foundation layer, custom entities respect strict governance rules. Access remains limited to configuration roles like Data Foundation Admin and Configuration. Operational roles such as HRBP and Compensation users do not have direct access. To ensure data stability, schema changes are restricted after publishing, and all changes follow platform-level access controls.
New Custom Entities section