beqom PaySuite 23.1 - Detailed release notes
This article lists the new features that have been added to the platform, as well as the bugs that have been corrected in the intermediate 23.1 release of the beqom PaySuite application and in the subsequent patches.
This is an attention message.
The text in this article is AI-generated. A final version will provided shortly.
23.1
Deployment to staging environments: April 21st, 2026
Deployment to production environments: April 28th, 2026
| Type | Issue key | Module | Description | Feature Flag* | |
|---|---|---|---|---|---|
| Zendesk | Jira | ||||
| AC-27431 | Compensation Management | This change is internal and has no direct impact on users. | – | ||
| AC-27206 | Data Foundation | An issue was corrected in Data Management > Data Retention where snapshot data anonymization failed when the hierarchy data strategy was configured, resulting in personal data (PII) not being anonymized as expected. Snapshot data anonymization now completes successfully. | – | ||
| AC-26969 | Authorization | This change is internal and has no direct impact on users. | – | ||
| AC-26964 | This change is internal and has no direct impact on users. | – | |||
| AC-26939 | Data Foundation | In Workbench > Data Management > Custom Entities, the entity detail drawer was updated to include the SPII indicator and Description fields. Users can now view this additional information directly within the drawer without navigating away. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26852 | Pay Transparency | In Workbench > Pay Analysis, the Total Cost of Raises widgets (Model, Recommended, and Final) were not displaying values correctly — numeric precision was not capped at two decimal places, and the currency code was missing from all three widgets. Both issues were corrected. The widgets now display values with up to two decimal places and include the currency code (e.g. '1,000 EUR'). | – | ||
| AC-26818 | Pay Transparency | An issue was corrected in Currency Settings where disabling currency conversion in a data mapping did not prevent currency values from being changed during dataset creation and sync. When no exchange rates existed for the configured global currency, the system silently replaced each worker's original currency without alerting the user. A warning message is now displayed when uploading a snapshot dataset if exchange rates are missing, and workers' original currencies are preserved when currency conversion is disabled. | – | ||
| AC-26799 | Authorization | An issue was corrected where the User Synchronization process failed with an error when attempting to delete a user record during a rollback or cleanup operation. This occurred because the associated name record was not automatically removed alongside the user record due to a missing cascade delete rule in the database. The constraint has been updated so that both records are now removed together, allowing synchronization workflows to recover gracefully. | – | ||
| AC-26794 | Pay Transparency | An issue was corrected in Planner > Pay Analysis where HRBPs received a 403 Forbidden error when clicking the Details tab in the Status widget. This occurred because the action required to retrieve Pay Analysis details was not included in the authorization policy for the HRBP role. The permission has been added, and HRBPs can now open the Details panel successfully. | – | ||
| AC-26769 | Data Foundation | A performance improvement was made to the Analytics Hub embedded reporting experience. Switching between reports now retains shared resources rather than reloading them each time, reducing load times for administrators navigating between reports. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26768 | Performance Management | An issue was corrected where simultaneously disabling an employee and their line manager via a worker provisioning update caused an error and placed the associated message in an error queue. This occurred because the manager reassignment process did not handle cases where no new manager was assigned. The system now correctly ignores these messages when no reassignment is required. | – | ||
| AC-26716 | Pay Transparency | An issue was corrected in Planner > Pay Analysis and Workbench > Model Factory > Pay Analysis where the horizontal scrollbar appeared at the very bottom of the grid content rather than fixed to the bottom of the visible viewport. Users were required to scroll to the last row before being able to scroll horizontally. The scrollbar is now fixed to the bottom of the visible viewport, allowing users to scroll horizontally at any point. | – | ||
| AC-26694 | Compensation Management | An issue was corrected in Payout Curves where the usage status of a curve was not updated after the bonus plan referencing it was deleted. The curve continued to display an 'Active' status even though no entities referenced it. The usage status is now correctly recalculated when a referencing bonus plan is deleted. | – | ||
| AC-26659 | Data Foundation | Translation support was extended to Power BI reports and semantic models in Analytics Hub, covering Adoption & Top-Level Summaries, Career Development, Check-ins, Feedbacks, Goals, Pay Communication, Pay Transparency - Right to Information, Performance Reviews, and Performance Reviews - Goals & Behaviors. Report widget names, titles, page names, and semantic model column names are now translation-enabled and configurable through the existing translation settings. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26602 | Performance Management | An issue was corrected in Passport > Reviews where self-reviewers encountered a 400 error and saw editable comment fields during the Pending Sign-off stage, even after completing and submitting their review. The system was not correctly checking whether the self-reviewer's stage was complete. No error is now displayed, and comment fields are no longer shown to self-reviewers once their stage is complete. | – | ||
| AC-26502 | Authorization | An issue was corrected where tenant database cloning failed following an upgrade to PostgreSQL 15 (the database version used by the platform). The failure occurred because a connection-termination command and a database creation command were being executed in a single call, which PostgreSQL 15 rejects when run inside a transaction. The two operations have been separated, restoring the ability to clone tenant databases as expected. | – | ||
| AC-26489 | Data Foundation | The DataIngestionCompletedEvent (an internal event used to notify other platform services when data has been imported) was updated to include a new optional ActivationFlags property. This property carries activation and deletion state information for each ingested record, allowing downstream services to determine whether an entity is active or deleted without re-querying the data source. Entities governed by effective dates return a null value for this property. This is a backward-compatible addition with no impact on existing integrations. | – | ||
| AC-26486 | Authorization | An issue was corrected in Back-Office where the Clients page took approximately 30 seconds to load when the notifications service was unavailable for a given tenant. The delay was caused by a request waiting the full default timeout before failing. The timeout has been reduced and the error is now handled gracefully, returning default values. The Clients page now loads within a normal response time regardless of whether the notifications service is available. | – | ||
| AC-26481 | Performance Management | The feature flag controlling access to the Career Development HR portal has been removed. The HR portal within Workbench > Performance Management > Career Development is now accessible on all environments without requiring the flag to be enabled. | – | ||
| AC-26478 | Performance Management | This change is internal and has no direct impact on users. | – | ||
| AC-26453 | Data Foundation | This change is internal and has no direct impact on users. | – | ||
| AC-26420 | Compensation Management | A toast notification mechanism was introduced to display backend error messages in a more visible and user-friendly way. When the system returns an HTTP error (such as a 400, 403, or 500 response), a toast notification now appears at the top of the screen with a relevant error title and description. This improvement applies to views using the updated HTTP client introduced in recent platform updates. | – | ||
| AC-26393 | Performance Management | The Review widget was updated to remove the display of the last review's rating. Regardless of the page on which the widget appears, it now shows the text: "Access reviews, monitor their progress, and stay on track with the process." | – | ||
| AC-26345 | Pay Transparency | An issue was corrected in Pay Analytics results where the Currency field was not enabled by default in the Column Config when syncing an analysis for the first time, causing the currency column not to appear in the results view. The Currency field now appears visible by default upon first sync, consistent with the rest of the Dataset Mapping Configuration fields. | – | ||
| AC-26322 | Data Foundation | An issue was corrected in the Pay Communication report where the semantic data model (the structured data layer used to generate report data) could not be refreshed due to a missing record in the live snapshot, which caused an incorrect data source to be referenced. The data model can now be refreshed successfully. | – | ||
| AC-26315 | Pay Transparency | An issue was corrected in Workbench > Pay Intelligence > Pay Analysis where categorical variables in the configuration details view incorrectly displayed auto-generated binary columns alongside the original variable. These redundant fields have been removed, and only the categorical variable itself is now shown. | – | ||
| AC-26312 | Performance Management | A feature toggle for Talent Review was added in Workbench > Platform Setup > Feature Enablement and Workbench > Performance Management > Talent Review Settings. Users with the Support role can enable or disable Talent Review. Users with a Read Only or Configuration Profile role can view the toggle state but cannot modify it. When enabled, the Talent Review Templates menu item becomes visible under Workbench > Performance Management. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26302 | Compensation Management | An issue was corrected in Round Portal > Proposal Management where Data Model Extension fields were not immediately visible in the formula editor field list when a pending draft existed for the round. Fields appeared in other areas of the round configuration but only became visible in the formula editor after navigating away and back. The formula editor now correctly reflects all extended data model fields without requiring additional navigation. | – | ||
| AC-26232 | Performance Management | This change is internal and has no direct impact on users. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26212 | Authorization | An issue was corrected in the authentication service where users were unable to complete login due to errors at the authorization endpoint (the service responsible for verifying identity and issuing sessions). In some cases, requests arrived with a missing client identifier; in others, a PKCE verification failure (a security check used to prevent token interception during login) forced users to restart authentication. Both issues have been resolved and the login flow now completes successfully. | – | ||
| AC-26170 | Data Foundation | A Calculated Fields runner was introduced to the compensation snapshot processing pipeline. Compensation administrators can now define formula-based calculated fields — such as combining name fields, evaluating conditional logic, or performing lookups against external data — and include them in subscription configurations. When a snapshot is executed, the runner evaluates the configured formulas and stores the results for use in downstream compensation processes. A standard FullName calculated field is provided out of the box, with support for additional custom field types. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-26147 | Data Foundation | The ProvisionUserAccount field (a boolean flag indicating whether a worker's user account should be provisioned) was added to the Live Snapshot data payload. This field was previously missing, preventing downstream systems from reliably determining provisioning requirements for worker accounts. Following deployment, the Live Snapshot is automatically rebuilt on the next scheduled cycle with no manual intervention required. | – | ||
| AC-26136 | Data Foundation | In Workbench > Data Management > Custom Entities, the color of the 'Deactivated' status label was updated to Indigo to align with the platform's standardized status color scheme. | – | ||
| AC-26054 | Compensation Management | Validation was added to compensation round step configuration in Workbench > Compensation Round > Workflow to ensure that Step end dates with Time-based progression fall within the round's timeline. When a Step end date is outside the round's start and end dates, Compensation Admins see an inline error on the date field and a banner listing affected steps, with those steps highlighted in red on the workflow diagram. Navigation is blocked until all date conflicts are resolved. | – | ||
| AC-25993 | Compensation Management | The dependency validation service (which detects configuration conflicts when fields are deleted or disabled in a compensation round) was extended to include Proposal Management configurations. Compensation Admins can no longer delete or disable a Data Model field that is actively referenced in a Proposal Management source field or formula expression without receiving a warning. Conflicts surface in the existing 'Dependency conflict' popup with the appropriate context. | – | ||
| AC-25886 | Compensation Management | In Passport > Compensation, the Compensation in Numbers widget now automatically calculates Total Compensation, Total Direct Compensation, and Total Indirect Compensation when a worker opens the Compensation tab. Totals are derived from the worker's compensation element structure and always reflect the logged-in worker's own data. A loading state is shown while data is fetched, and an empty state is displayed when no compensation data is available. | – | ||
| AC-25842 | Pay Transparency | A mapping configuration listing page was added in Workbench > Pay Transparency. Compensation Admins, Global Compensation Admins, Support, and Read-only users can view a paginated table of all Document Generation mappings, with columns for Population, Template, Data Source, Communication Round, Owner, Creator, Usage, and Status. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25839 | Pay Transparency | A new Mapping Configuration page was introduced in Workbench > Pay Transparency. Compensation admins, Global Compensation admins, Support, and Read-only users can navigate to this page from the Pay Transparency sidebar and access mapping configuration settings. The page is only available when both Document Generation and Pay Information Requests are enabled in Document Settings. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25800 | Pay Transparency | An issue was corrected in Snapshot Manager where creating a Pay Analytics dataset from a snapshot that did not include a worker category resulted in an error stating that records were removed due to a null or empty MainEmployeeCharacterizationField value. Pay Analytics Admins can now successfully export snapshots to Pay Analytics even when a worker category is absent from the snapshot. | – | ||
| AC-25791 | Authorization | An issue was corrected where image assets were not loading across the application, resulting in broken images. Requests to the /images/ path were incorrectly reaching the application router instead of being handled by the static asset serving layer, causing 404 errors. The routing configuration was corrected so that image assets are now served properly. | – | ||
| AC-25748 | Performance Management | An issue was corrected in Passport > Goals where large numbers entered as the target value for numeric or financial measurement criteria could not be fully displayed. The input fields for numeric and financial measurement criteria have been widened to accommodate longer values, while the percentage input field has been made narrower to reflect its more limited range. | – | ||
| AC-25603 | Compensation Management | Administrators can now enable or disable the Compensation in Numbers widget from the DRS configuration in Passport > DRS Main Content. When enabled, administrators can control which compensation elements are displayed (Total Compensation, Total Direct Compensation, Total Indirect Compensation) using per-element checkboxes, with at least one element required. When disabled, the widget and all its sub-elements are fully hidden from the employee-facing DRS page. For new DRS configurations, the widget is disabled by default; existing configurations are unaffected. | – | ||
| AC-25594 | Compensation Management | A 'Copy JSON' button was added to the Statement Generation tab in Round Portal. Global Compensation Admins and Compensation Admins can click this button to copy a sample JSON structure to their clipboard, reflecting the current round's configuration with randomized placeholder values and no real worker data. This allows administrators to paste the structure into the Pay Transparency template configuration preview when designing document templates, without running a full round. | – | ||
| AC-25574 | Data Foundation | An issue was corrected where triggering worker anonymization via the anonymization API (a service used to remove or obscure personal worker data) would return a success response but the anonymization would not actually be carried out. This occurred when a worker-referenced Custom Entity was present. The underlying error has been resolved, and worker anonymization now completes as expected. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25571 | Authorization | SSO logout support was added to the Back-Office application. Previously, clicking 'Logout' ended only the local application session while the Azure AD (Azure Active Directory, the identity provider used for single sign-on) session remained active. The logout flow now terminates both the local session and the Azure AD session, and users are redirected to the Azure AD sign-out endpoint. Re-authentication is required to access protected areas after signing out. | – | ||
| AC-25489 | Authorization | A security issue was corrected where any authenticated API client holding the integration scope could retrieve the complete permission matrix for all users in a tenant — including role assignments, organizational assignments, and access flags — without additional access control. The affected endpoints now return a 403 Forbidden response when called without appropriate credentials, and the integration scope is restricted so that it can only be issued to client credentials grant types. | – | ||
| AC-25488 | Authorization | A security vulnerability was corrected in the integration API where any authenticated user could obtain the integration OAuth scope (a permission token used to access integration services) via password-based login and use it to assign elevated access roles to any user in the tenant. The fix restricts the integration scope so that only trusted service accounts using client credentials can obtain it. Unauthorized write attempts are now logged for audit purposes. | – | ||
| AC-25447 | Data Foundation | Compensation admins can now reorder Local Worker Categories using drag-and-drop to define a global priority order. This priority determines which local category is applied first during snapshot generation when multiple categories match the same worker. The reordered list is saved automatically upon each change and applies to future snapshot generations only. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25444 | Data Foundation | A validation rule was introduced for Local Worker Categories to prevent the same population from being assigned to more than one category. When creating or editing a Local Worker Category, the system checks for population conflicts and blocks saving if one is found, displaying an error identifying the conflicting population and its current category assignment. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25443 | Performance Management | An issue was corrected in Passport > Reviews where managers who had been reassigned a review encountered a 400 error when opening that review after it had been completed and signed off. The error occurred because the view mode was incorrectly derived from the review's action-needed status, causing the page URL to be constructed with incorrect parameters. The review now opens successfully without error. | – | ||
| AC-25441 | Pay Transparency | An issue was corrected in Pay Analysis where it was possible to enter a value lower than the current salary in the 'Compensation after recommended raise' column, as well as negative raise and percentage raise amounts. Validation is now enforced in both Workbench > Model Factory > Pay Analysis Results and Planner > Pay Analysis: values smaller than the current salary are automatically reset to the original salary, and invalid negative raise values are rejected. | – | ||
| AC-25427 | Data Foundation | Snapshot generation now supports Local Worker Category configurations that override the global Worker Category configuration for specific worker populations. The system evaluates defined local configurations in priority order to determine which applies to each worker; workers not belonging to any local population use the global configuration. If a worker matches multiple local populations, the highest-priority configuration is applied. Generated snapshot results are not affected by subsequent configuration changes. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25395 | Pay Transparency | An issue was corrected in Planner > Pay Information where filtering Pay Information Requests by alert type (e.g., Overdue, Document Deleted, Not Released to Worker) returned incorrect or missing results for HRBPs. Filters now correctly return only the requests that match the selected alert condition, and the numeric counters on the page accurately reflect the filtered results. | – | ||
| AC-25212 | Data Foundation | An issue was corrected in Workbench > Data Management > Populations where loading population criteria using hierarchical tree fields (such as Legal Entity, Organization, or Cost Center) with an IN or NOT IN operand was excessively slow for trees with a large number of nodes. The performance of this calculation has been optimized to handle large datasets more efficiently. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25186 | Data Foundation | Role-based access control was defined and implemented for Custom Entity management. Custom Entities are structured datasets used to support platform capabilities such as lookup tables, reference data, and calculation inputs. Access is now restricted to DataFoundationAdmin, Configuration, and Support roles, which can manage schemas, publishing, deactivation, and data ingestion. Operational and feature-level roles are denied access to Custom Entity administration, though they continue to interact with workflows that rely on Custom Entities. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25171 | Pay Transparency | In Workbench > Pay Analysis Results, a new option was added to the Publish to Planner modal allowing Compensation admins to pre-populate final raises with the recommended raise values at the time of publishing. When the checkbox is selected, the system automatically stores the final raise values matching the recommended raises, giving HRBPs a pre-filled starting point when they access the analysis in Planner. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25151 | Compensation Management | This change is internal and has no direct impact on users. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25025 | Pay Transparency | Two new calculated columns — Outlier % (after final raise) and Distance from predicted compensation (after final raise) — were added to the Pay Analysis grid in Workbench. These columns apply real-time calculations to final raise amounts using the same approach as for recommended raises. Compensation admins can configure column visibility from the column configuration section in Workbench once an analysis has been published. Both columns are disabled by default and appear at the beginning of the editable column list. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25022 | Pay Transparency | A new 'Submitted' status was added to Pay Analysis, allowing HRBPs and Pay Analysis Admins to formally mark an analysis as complete. In Planner > Pay Analysis, a 'Submit recommendation' button transitions the analysis from 'In Progress' to 'Submitted'. Once submitted, the analysis cannot revert to a previous state, though CSV export remains available. When an analysis is submitted or published, Final Raise columns become visible and editable in Workbench for Pay Analysis Admins. Both Planner and Workbench list pages display an updated insights card showing the count of submitted analyses. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24785 | Authorization | This change is internal and has no direct impact on users. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24356 | Compensation Management | In the compensation round configuration wizard, Compensation Admins and Global Compensation Admins can now navigate freely between any configuration step when editing a round in Pending Draft status. Previously, navigation was restricted to sequential forward or backward movement using the Next and Back buttons. Users can now click directly on any step in the wizard pane to jump to it, with the same validations applied as when using the Next or Back buttons. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24211 | Authorization | An issue was corrected where a user with proxy access rights was unable to find a worker in the proxy access list, even though the worker was correctly visible in the exclusion population. This occurred because organisation data was not properly synchronised, causing the worker to be absent from searchable proxy population results. The proxy access list now correctly reflects all workers within the authorised scope. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24156 | Pay Transparency | In Planner > Pay Analysis, HRBPs and Pay Analysis Admins can now view and add notes directly on worker rows. Pay Analysis Admins can view and create notes without restriction. HRBPs can view admin and HRBP notes, and add their own notes when the relevant permission has been granted to their role in Workbench. Note editing and deletion remain restricted to the original note creator. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-24064 | Data Foundation | A unified audit log for Worker Category configuration changes was introduced. Users can view a chronological list of both Global and Local Worker Category changes, with each entry capturing the timestamp, user, action type, and the target configuration affected. The log supports date range filtering, pagination, and allows users to download the stored configuration state for any entry as a JSON file. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-23555 | Pay Transparency | When currency conversion is enabled in the Dataset Mapping Configuration, users uploading a snapshot dataset to People Analytics will now receive a clear error banner if any required exchange rates are missing. The system displays the message: 'The snapshot you are trying to upload contains unconfigured currency exchange rates. Please update your currency settings.' This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-23405 | Compensation Management | In Workbench, compensation admins can now edit, duplicate, delete, and republish rounds in a Failed status directly without first creating a Pending Draft. Failed rounds now behave like Draft rounds: clicking Edit opens the full round wizard with all steps and fields editable, and duplicating and deleting follow the same behaviour as for Draft rounds. The alert message on Failed rounds has been updated to link directly to the relevant edit flow. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-21754 | Compensation Management | A new notification template type (Type 101) was added to support the sending of compensation round reminders. This template is configured to send emails automatically and is not exposed for manual editing in Workbench > Email Templates. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
| AC-25588 | Data Foundation | New localization keys were added to the localization service and web application to support ongoing development. This change is internal and has no impact on end-users. | – | ||
| AC-23756 | Data Foundation | Administrators can now create, edit, and delete Local Worker Categories as reusable configuration objects within the snapshot configuration workflow. These categories define targeted exceptions to the global worker category behaviour for specific worker populations. Once created, categories are stored centrally and reusable across multiple snapshots. Editing applies changes only to future snapshot generations; deletion is only allowed if the category is not referenced by active snapshot configurations. The platform enforces governance rules including unique category names, mandatory field and population selection, and population exclusivity. This feature is currently behind a feature flag and is not yet available to all customers. | Yes | ||
This is a miscellaneous message.
About Feature Flags
beqom practices continuous development and continuous deployment. According to this method of work, code can be added to the code base but hidden behind a Feature Flag. When features or parts of a feature are hidden behind a Feature Flag, then they are not visible in the application interface even though the code exists in the code base. This is to make sure that new code is included in small increments, which makes it easier to test and guarantees higher code quality, without impacting end-users.
Features that are marked as behind a Feature Flag in this table are not yet available to end-users. Their release will come at a later date when the full scope of the features is done.