beqom PaySuite 27.0 - Feature release notes
This article details the latest improvements introduced in version 27.0 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Experience
Redesigned Behaviors page in Passport
The Behaviors page in Passport has been brought in line with beqom's current design system, replacing an older layout that had drifted from the rest of the product and made behaviors hard to scan.
Each behavior library now appears as its own section, with its name, a short description, and a completion chart showing the percentage of behaviors received. The chart uses the same behavior wheel already found in Passport > Overview, so the two views stay consistent, and a library with no received behaviors yet shows in gray with "0 received behaviors". Behaviors are presented as individual, clickable items rather than a table, and selecting one opens its full description below the list. Longer library and behavior descriptions are shortened with a Show more and Show less control, so a section stays easy to read without losing any detail.
A refreshed empty state and updated visuals carry the new look across the whole page. Which libraries a worker sees, whether assigned company-wide, by org unit, or individually, is unchanged. The redesigned page is available under Passport > Behaviors. The insights area at the top of the page is not part of this update.
New Behaviors page
Compensation Management
New per-role visibility in the Planner
Previously, everyone taking part in a compensation round saw an identical Planner. A compensation manager, HRBP, and auditor all looked at the same columns and budget widget in Planner > Compensation, whether or not each was relevant to their role. They could not tailor the view, so the Planner often included more than a specific role needed.
We have added per-role visibility control to compensation rounds. Administrators can now shape what each role sees and does from the Actors & round access step under Workbench > Compensation Management > Compensation Rounds, both during setup and after a round has been published:
Column visibility per role. Each role (Auditor, Compensation advisory, Compensation manager direct, Compensation manager indirect, and HRBP) can keep the default set of columns or be given a custom one. The Preview grid mirrors the Planner, so it is clear what a role will see before round publication, and at least one column always stays visible.
Budget widget per role. The budget widget can now be shown or hidden for each role on its own, in place of the single setting that used to apply to everyone.
Round access per role. A whole round can be hidden from a role, and the role's visibility settings are kept and restored if access is turned back on.
Hidden columns remain hidden everywhere, with filtering, sorting, export to Excel, and the audit trail respecting a role's visible set. The Worker, Manager, Notes, and Eligibility columns are always visible to every role. For published rounds, the full per-role configuration can also be reviewed, read-only, in the Round Management portal.
The result is a focused, relevant Planner, giving each role the data that matters to it.
Configuring column visibility, budget widget, and access per role
Choosing which columns the HRBP role can see
Redesigned custom columns and column configuration
Setting up columns for a compensation round used to mean moving across several wizard steps and separate drawers, with custom drop-down options typed in one at a time. As rounds came to depend on more custom columns, this setup became slower and fragmented.
Version 27.0 of the application reworks how columns are configured in two parts.
The first is richer custom drop-down columns. A custom drop-down no longer has to be a hand-typed list. Compensation Admins can now populate its options from live data instead, either a shared reference list such as Country or Currency, or a custom data entity, so the options remain aligned with the source. Options can also cascade, narrowing to the values that match other columns the Planner has already filled, for example filtering the list of grades by a worker's country and job level. Hand-typed lists are still available for cases where a short, fixed set of options is sufficient.
The second is a single place to configure each column. The Team planner view's Column configuration now gathers every per-element setup into one hub, showing at a glance which settings already have rules applied and listing all options for a column. Budget, Eligibility, and Guidelines, which used to be separate steps in the configuration wizard, are now set per element from this hub, so the wizard itself is shorter. Conditional formatting has also moved to a list-and-detail layout, where the column's rules are managed and saved together.
As before, columns are set up under Workbench > Compensation Management > Compensation Rounds, and the same layout is mirrored as read-only in the Round Management portal, so administrators can review a published round's configuration without changing anything.
All these improvements make column setup quicker to reach and easier to follow.
Setup icons showing rules already applied to columns
New column configuration panel
All configuration options for a column in one place
Full-width layout for the compensation round setup wizard
On large monitors, the compensation round setup wizard left considerable empty space, and the step list beside it shifted width from one step to the next.
We have made the wizard use the full width of the screen, with the content centered and capped on very large displays so that it does not extend too far. The step roadmap now keeps a constant width across every step, and on narrower screens it moves above the content instead of compressing it. Back and Next buttons are accessible at any screen size.
The wizard opens in Workbench > Compensation Management > Compensation Rounds when creating a round or editing a draft one.
The layout has become steadier and easier to navigate, thanks to how the space is used. The steps, fields, and order remain unchanged.
Wider view of a round configuration step
Performance Management
Draft mode introduced for goal results
Until now, managers had no way to prepare goal achievement results before workers saw them. With this release, a new goal plan setting, Hide goal results until published, introduces a draft mode for goal progress. The setting is available in the Goal plan details step when creating or editing a goal plan under Workbench > Performance Management > Goals > Goal Plans. Goals and Configuration professional roles have access to it. Off by default, the setting can be enabled or disabled at any time.
Once enabled, managers can enter and refine measurement criteria and progress values privately. Those edits are saved as drafts rather than published immediately, and are shown to the manager in a lighter shade alongside the current published value. Workers continue to see only the last published result and are not notified that a draft exists. Managers can publish draft results in one action when ready, either directly from the goal page or when saving and exiting an edit.
The same rule extends to reviews, where managers, reassigned managers, and additional reviewers can see draft values, though only the assigned manager can edit them, and to organizational goals, where editing follows the goal's owner. Across all of these, workers never see draft values until they have been published. Draft saves do not appear in the Audit trail.
This allows managers to validate goal results before they become visible to workers, rather than exposing progress as soon as it is entered.
Draft mode setting during goal plan creation
Draft and published progress on the goal view
Corrected start dates for individual goals in Compensation Management
Compensation Management's bonus calculations only work correctly when a goal falls within its plan period. Individual goals created before their goal plan started did not always meet that condition, as they were previously sent to Compensation Management using the goal's publish date as the start date, rather than a plan-relative one. This excluded some individual goals from bonus calculations, leading to inconsistencies in the underlying compensation data.
Individual goals now follow conditional start-date logic that mirrors what organizational goals already use. A goal created before the plan start date takes the plan's start date as its own; a goal created on or after the plan start date keeps the goal's publish date. The end date is always the goal's due date. This is applied at the Data Foundation level, in the goal_achievement_new table that feeds all Compensation Management calculations.
With this change, bonus calculations correctly include every individual goal, improving the accuracy of compensation outcomes tied to goal achievement.
Pay Transparency
Sortable Pay information requests list
Version 27.0 of PaySuite supports interactive column sorting under Planner > Pay Information > Requests, making it easier to locate, prioritize, and review requests, particularly when working through a large volume of them. HRBPs can sort the list of Pay information requests by clicking any column header to cycle between ascending, descending, and the default order. To keep the ordering clear and predictable, only one column can be sorted at a time.
The Alert column sorts by urgency rather than alphabetically, moving from no alert through Approaching deadline, Overdue, and Document deleted. This way, the most pressing requests can be easily identified. Sorting works alongside all currently applied filters, and changing the sort returns the list to the first page while keeping the selected page size. Left untouched, the list still defaults to showing the newest requests first.
Column sorting on Pay information requests
Automatic exclusion of snapshots missing a worker category
Since Pay Transparency comparisons depend on workers being grouped within the same worker category, a snapshot missing that category could result in incomplete or unreliable comparisons. Snapshots without a defined worker category are now automatically excluded, both when mapping configurations are set up in Workbench > Pay Transparency > Pay Information > Mapping Configuration and when requests are managed under Planner > Pay Information > Requests. Only snapshots capable of producing a valid comparison remain available for selection. This reduces configuration errors before request processing and improves the accuracy and reliability of generated pay information letters.
Data Foundation
Legacy goal entities removed and CompensationHistory deprecated
Over time, a couple of older goal entities and the original compensation data structures became out of date and mismatched with how the platform works today. With release 27.0, we have cleaned these up so that the Data Foundation schema stays consistent and aligns with the current data model.
Specifically, we have removed the legacy GoalAchievement and GoalPlanTypeAssignment entities. Both were already deprecated and are no longer used in active integrations, so no impact is expected. Going forward, GoalAchievementNew, along with Goal and GoalPlan, should be used instead.
In addition, CompensationHistory is now deprecated. No new data can be ingested into it, and it does not appear in the Data Viewer, Data Modeler, or Populations under Workbench > Data Management, though existing models and snapshots built on it will keep working for now. The entity will eventually be removed altogether, so any team still relying on it should plan a move to the two entities that replace it: ContractedCompensation for planned or awarded values and PaidCompensation for actual payouts. Anyone using CompensationHistory today should review current models and configurations and schedule that migration before it is fully retired.