beqom PaySuite 29.0 - Feature release notes
This article details the latest improvements introduced in version 29.0 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Experience
Full screen width for Passport and Planner pages
List and table pages in Passport and Planner have been confined to a narrow, fixed content area, leaving sizable margins on the sides of larger screens.
These pages now use the full width available between the side navigation and the window edge. On very wide monitors, the page does not stretch further but centers, so tables and card grids do not spread into unreadable rows. Layouts continue to reflow cleanly at the platform's existing breakpoints, whether the side navigation is expanded or collapsed, and wide tables scroll inside their own containers rather than the page itself scrolling horizontally. Insight rows follow one consistent layout across both Passport and Planner: a fixed-width summary tile beside a card that fills the remaining width and collapses to a single column on narrower screens. Interior forms and reading views, including the feedback view, review forms, and wizards, keep their constrained, readable width. Workbench is unaffected.
By making better use of available screen space while preserving readability, these improvements help users work more efficiently.
Passport page edge to edge across the window
Goals tables aligned with the platform's table styling
Previously, the Goals tables in Passport and Planner had styling that differed from PaySuite's standard table cells.
Currently, workers and managers see goal names rendered in the same clickable cells used throughout the application, with consistent sizing, weight, line height, link color, and states. The Owner column contains smaller avatars and plain text to align with the rest of the platform. The extra spacing above the table is no longer there, and the bottom corners follow the card's rounded corners in every state.
In the Planner, the clickable goal name appears in the first column, and Owner in the second. The Total row is left-aligned beneath the Weight column on its own line. We have also integrated the Approve goals row with its corresponding goal row. Column widths are preserved to keep goal names, owner details, and progress information readable. In Passport, the Goal plan drop-down supports searching and filters results as users type.
These changes eliminate small visual inconsistencies and make the information easier to scan.
Individual goals table in the Planner, matching other tables in PaySuite
Profile photo editing moved to Settings
So far, users have changed their profile photos through Company Network, tying photo editing to a feature that may not be enabled for every tenant.
With this release, the Account card in Settings, accessible from the top navigation under the user's name, displays the current profile photo or an initials avatar if no photo is set. A clearly labeled control opens the existing photo-change pop-up. Uploading, replacing, and removing photos work as before, and changes appear in the top-navigation avatar and everywhere else the photo is displayed without requiring a page reload. The new control has also been verified for keyboard and screen-reader accessibility in both light and dark themes.
This provides a consistent way to manage profile photos, even when Company Network or Passport > Overview is disabled for a tenant. The remaining Settings options, including Account links, the email notification toggle, Language & format, and Time zone, stay the same.
New Change profile photo pop-up in Settings
Compensation Management
Percentage format for Decimal custom and calculated columns
In previous versions of the application, Decimal custom and calculated columns in Planner > Compensation displayed values as plain numbers, requiring administrators to include ×100 logic in formulas or maintain helper columns to present such values as percentages. They also could not change a column's format after saving it.
A Percentage format toggle is now available in the column configuration modal, directly above Currency / Enable currency, within Workbench > Compensation Management > Compensation Rounds > Team planner view. Global Compensation Admins and Compensation Admins can switch between percentage and standard decimal formats even once a column has been saved and put into use. The two toggles are mutually exclusive, so a Decimal column can be formatted as either a currency or a percentage, but not both.
When percentage format is enabled, a stored value of 0.2 is displayed as 20%, rounded half-up to the column's configured display precision. For example, a stored value of 0.12345 at precision 2 appears as 12.35%. Entering 20 in a Planner percentage-formatted cell stores 0.2. Changes take effect when saved and, for an already published round, reach HRBPs and managers when the round is republished.
Formulas, exports, and downstream calculations, including guideline corridors and comparisons, continue to use the raw stored decimal, regardless of its display format. This prevents double counting when the format changes. The feature applies only to Decimal columns, not String, Boolean, or Date columns. The representation of percentage-formatted values in the Planner > Compensation > Audit trail is handled separately.
Thanks to this enhancement, administrators can present ratios and rates as percentages directly and adjust formatting decisions during a compensation round without rebuilding columns.
Percentage toggle for a Decimal custom column
Demo
Drag-and-drop ordering for Planner widgets
Widgets in the Planner > Compensation pane appeared in the order they were added to a compensation round, with no way for administrators to rearrange them. As a result, widgets added later in the setup could remain at the bottom, regardless of their relevance to managers and HRBPs.
In version 29.0 of PaySuite, we have included a drag handle for every widget row in the Widgets tab of the Team planner view step in Workbench > Compensation Management > Compensation Rounds. Administrators can drag rows into a new position, using the same interaction as column reordering. Other rows shift automatically to accommodate the change, and the new order is saved with the Team planner view step.
The saved order determines how widgets appear in the Planner pane for every role with permission to view them. It is also carried over to the Round Management portal and duplicated rounds. Existing rounds retain their current order after release because reordering is opt-in.
Administrators can therefore prioritize the widgets Planner users rely on most, using a familiar interaction to organize the pane around their needs.
Drag handles on widget rows in the Team planner view
Demo
Manager focus in the Population panel
Until now, in worker-to-worker hierarchies, the Population panel in Planner > Compensation combined a checkbox on each node with a separate three-dot menu. The menu's behavior varied depending on the active hierarchy, making worker-tree navigation inconsistent.
With this release, we have removed checkboxes and indeterminate state from every worker-to-worker Browse by option (Line Manager, Matrix Manager, Compensation Manager, and Communication Manager). Selecting a manager's name now focuses the grid and its widgets on that manager's team. By default, the scope includes direct and indirect reports when the manager has indirect reports in the population; otherwise, it includes direct reports only. Selecting the same manager again clears the focus, while selecting another manager replaces the current selection.
An active-context indicator above the grid identifies the focused worker and the selected scope. The same three-dot menu on the focused node provides Select all direct reports and, where applicable, Select all direct & indirect reports. Switching to another Browse by option clears the focus. Enum and organization hierarchy options remain unchanged.
When no other node is selected, a Compensation Manager's own node is focused automatically. HRBP, Compensation Advisory, and Auditor views continue to load without a focused node. An off-population manager can also be focused, scoping the grid to their in-population reports without adding the manager to the grid.
Widgets linked to a Fixed amount per manager budget definition require a focused manager to display a value. Until a manager is selected, the widget displays the message "Select a manager in Population to view the budget" rather than disappearing.
This creates a systematic navigation model across worker hierarchies, making it easier to concentrate on a manager's team and access the relevant budget information.
Three-dot menu for a focused manager, in place of the old per-node checkbox
Demo
Performance Management
Search and filter within the Talent Review 9-box cell drawer
The Planner > Talent Review 9-box cell drawer introduced in the previous release lists everyone placed in a cell, but finding specific workers has meant closing the drawer and working from the calibration page behind it.
The drawer now includes its own search, available to both managers and Talent HRBPs. It matches worker names and Worker IDs, updating results with each keystroke. Results remain limited to the selected cell and the viewer's visibility scope: a manager's direct reports or a Talent HRBP's assigned population.
Talent HRBPs also have three multi-select filters: Filter by Manager, Organization, and Country. Selections combine using OR within each filter and AND across filters and with the search text. Filter by Manager lists only managers with workers in the selected cell within the HRBP's scope, whereas Organization and Country include all available options.
When the drawer opens, its search and Filter by Manager are pre-filled with the settings used to produce the clicked cell on the calibration page. This ensures the controls reflect the workers already displayed. Managers see search only, as their page does not have a filter toolbar. Changes made within the drawer affect only its contents and are discarded when it closes, so the 9-box grid and calibration page remain the same.
This lets managers or Talent HRBPs pinpoint workers inside a crowded cell without leaving the drawer or disrupting their calibration view. As a result, they can focus on the people relevant to their work.
Talent HRBS's view of a 9-box cell drawer, with its worker list narrowed by the manager filter
Manager's view of a 9-box cell drawer with the search field
Pay Transparency
Duration tracking and label clarity for pay information requests
The Since request column in Planner > Pay Information continued counting after a request was closed, making resolved requests appear to have increasingly long durations alongside those still in progress.
We have renamed this column to Open since request across all relevant request management views. Its counter freezes when a request reaches a closed status, displaying the actual time taken to resolve it. If a request moves from closed back to pending release, the counter resumes, reflecting the elapsed time from the original request date to the latest closure date.
Existing closed requests have been migrated to their correct historical durations, calculated from their recorded resolution dates.
This way, managers and HRBPs can see at a glance which requests are active and which have been closed, while benefiting from more reliable time-to-resolution data for reporting.
Renamed Open since request column on the Pay Information page
Audit trail visibility for closed and pending-release documents
Bulk actions and automated triggers on document requests have made it difficult to tell whether a document was fully closed and released or was still awaiting release.
Currently, audit trail entries explicitly distinguish between Closed & released and Pending release outcomes, whether the action was performed manually in bulk or triggered automatically by the system. This distinction is reflected in both the Audit trail tab and the Audit trail drawer in the Requests tab under Planner > Pay Information.
The Audit trail tab includes a new Closed pending release filter, distinct tag colors and styling for each status, and an expanded More details column. The additional context identifies whether a close action was manual, bulk, or automated, and whether documents were involved. In the Audit trail drawer, generic fallback icons have been replaced with dedicated, readable labels and accurate icons for bulk and automated closing and document-generation actions.
These improvements give managers a clearer view of a document's status, helping them identify pending releases, filter audit records, and follow up on outstanding actions during compensation and communication rounds.
Audit trail's automated-action entry marked "Release is pending"
Context-aware deep links for combined document review notifications
Previously, combined notifications about multiple documents pending review, whether received in-app or by email, directed managers and HRBPs to a general starting point. Then, they had to navigate to the relevant communication round and workflow step manually.
Clicking a combined notification now opens the corresponding communication round with the workflow view filtered to the relevant step. HRBPs land on Planner > Documents > [communication round] > HRBP tab, filtered to HRBP Review workflow status. Communication Managers land on the Communication Manager tab, filtered to Document Review. Reviewers who hold both roles are directed to the tab matching the notification's purpose. This behavior is consistent across the in-app notification center and email notifications.
By taking users directly to the relevant workflow step, the deep links eliminate unnecessary navigation and filter adjustments, allowing them to access and process their pending document reviews more efficiently.
Data Foundation
Clearer retention behavior and terminology for uploaded data
So far, uploaded Data Foundation CSV files have accumulated in storage indefinitely. In addition, the retention wording in Workbench > Data Management described the worker anonymization process as hard deletion, even though it only makes personal information non-identifiable.
A new cleanup job automatically deletes ingested CSV files one year after upload. The Data Load page specifies this retention period, and attempts to download files that have already been removed are blocked with a message explaining the policy. We have also corrected the retention wording on the Data Retention page to clarify that anonymization removes identifying information from a worker's records while retaining the records themselves.
These changes help control storage and database growth, support security and compliance goals, and give administrators an accurate understanding of how uploaded files are retained and what anonymization means for worker data.
Data retention policy tooltip in Data Load
Major cryptocurrencies added to the currency list
In Workbench > Data Management > Currency Settings, the standard currency list has covered only traditional currencies.
We have extended this list to support six major cryptocurrencies: Bitcoin, Ethereum, Tether, USD Coin, Solana, and XRP. Users with write access to currencies can enable these options for their tenant through Currency Settings. Once enabled, cryptocurrency codes can be imported into any Data FoundationCurrency field, entered manually or imported into a Business Matrix column that references the Currency enum, and used in exchange-rate imports just like other currencies.
This lets tenants record and calculate cryptocurrency-denominated compensation and payments wherever currency support is available, without requiring a separate mechanism for digital assets.
Bitcoin available in Currency Settings
Authorization
Consistent worker visibility through Security Group ACLs
Until now, worker visibility granted through a security group's access control list (ACL) was not consistently recognized across the platform.
Currently, a user granted access through a Security Group ACL is included wherever the platform determines who can see a given worker. Analytics employee views reflect workers granted through the relevant Security Group ACLs as well. Creating or updating a security group is also more resilient, as valid Worker IDs in the request are saved, while unknown Worker IDs are skipped and reported back rather than blocking the entire request. A request fails only if none of the Worker IDs it contains can be resolved.
This brings worker visibility into closer alignment across PaySuite, helping users see the workers covered by their permissions. It also makes large ACL updates less vulnerable to failure because of a small number of invalid IDs.