beqom PaySuite 27.2 - Feature release notes
This article details the latest improvements introduced in version 27.2 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.
Compensation Management
Eligibility, Budget, Guidelines, and Required notes for custom input columns
Compensation elements have long supported rules that determine who is eligible for them and how much can be allocated against them. They can also flag values that fall outside an acceptable range and require a justification for such cases. Until now, custom input columns had no such equivalent. A compensation round with a custom column let any value be entered for a worker, with no way to keep it in check.
With this release, custom input columns work the same way compensation elements do. In the Team planner view step under Workbench > Compensation Management > Compensation Rounds, Global Compensation Admins and Compensation Admins can configure Eligibility rules that exclude specific workers from a column, assign the column a Budget with a corresponding entry in the Budget widget, define Minimum and Maximum Guidelines that warn users or block values outside the permitted range, and enforce a note whenever a value is entered, either every time or only when it falls outside guidelines.
Compensation Managers and HRBPs see the outcome directly in Planner > Compensation. An ineligible worker's cell becomes read-only. Also, a column's budget appears alongside the compensation elements it is grouped with, and a note is required precisely as configured.
Not every column qualifies for every rule. Eligibility can be set on any editable column. Budget, Guidelines, and Required notes are limited to Decimal columns. Budget further excludes columns configured as a percentage, since summing percentages across a population does not currently have a defined business meaning. All four are configured from the same window used to set up a custom column. The same configuration remains visible, in read-only form, to anyone reviewing the round later in the Round Management portal, which always reflects what was actually saved.
Thanks to these enhancements, a round no longer needs compensation elements just to provide eligibility, budget control, or guidelines. Custom columns can now carry that logic themselves.
Eligibility rules for a custom input column, with Budget and Guidelines listed in the configuration menu
Custom column configuration with the Required notes toggle
Search in the Population panel
Previously, finding a specific group, organizational chart branch, or worker in the Population panel of Planner > Compensation required scrolling through a long list or tree manually.
The Population panel now includes a search field, placed below the View as and Browse by drop-downs. Typing a term filters the panel immediately, regardless of how the population is currently being browsed. In a tree view, every match keeps its full chain of parent nodes visible, so a result never appears out of context, and the tree expands automatically to reveal it. Matches are highlighted. Any groups or workers already selected remain so while searching, so narrowing the list to find one more item does not undo earlier choices. The panel returns to its full, unfiltered state once the search is cleared. Switching the Browse by option or the audience being viewed has the same effect.
Compensation Managers and HRBPs have this available in every compensation round's Planner, with no configuration required.
Population panel's worker tree filtered using a search field
Performance Management
New bulk ratings upload for performance reviews
Setting an overall performance rating used to mean opening each worker's review individually. This made a full review cycle slow to complete.
In version 27.2 of PaySuite, performance review administrators with Owner or Local Owner rights can handle this in one operation under Workbench > Performance Management > Performance Review Templates. A new Upload performance ratings tab on the review template's Manage page, available once a template is published, lets an admin download a CSV file pre-filled with every review in their scope. The ratings can then be updated offline and the completed file uploaded.
The system checks each row independently. Rows that pass are applied. Rows with a problem, such as a mismatched manager or a review in a non-editable stage, are skipped without stopping the rest of the file from processing. A downloadable result log then provides a full account of the outcome. It shows which ratings changed and which were rejected, with a reason for each. Rows that needed no modifications are logged as well. This matters, since it allows the same file to be uploaded twice without risk. Rows already applied are reported as no change, not overwritten a second time.
As with editing a review directly, an administrator can change a rating but cannot clear it through this route, since submitting a blank value over an existing one fails rather than removing it. The tool also maintains a durable upload history, recording who uploaded each file and when, together with the result. Therefore, a full review cycle can be updated and checked in one place instead of one record at a time.
Upload performance ratings tab on the Manage Performance review page
Demo
Pay Transparency
Response Automation for pay information requests
Processing pay information requests has moved from something handled one at a time to something done through bulk actions, like generating documents and closing and releasing several requests together. Even with bulk actions, an HRBP still had to decide when to run them.
Our new page, Response Automation, adds a further step. Under Workbench > Pay Transparency > Pay Information > Response Automation, administrators can configure automatic document generation and automatic close and release independently of each other: an organization might automate document generation while still closing and releasing requests through an HRBP decision, or enable both together for a fully automated flow. The capability remains inactive until an organization chooses to configure it, since response automation is disabled by default.
Automatic document generation can be scoped to how a request originates, for example, one submitted by a worker, imported through an API, or created directly by an HRBP, and administrators decide whether a newly generated document should replace one that already exists or leave it in place. Generation can begin immediately or after a set number of days following the request date, giving a short window for manual intervention before automated processing begins. A mapping configuration must already be in place for a worker, tying together the pay data snapshot, the document template, and the communication round the response should go to. Without mapping, automated generation cannot complete.
Automatic close and release follows once a document becomes available, whether generated automatically or attached another way; closing a request without a document remains a deliberate manual action outside automation's scope. Response automation also respects each communication round's workflow: where no review is required, an eligible request can be generated, closed, and released without any HRBP involvement, while a round with a required workflow still automates generation and closing but holds the document at pending release until an HRBP completes the review and releases it. Country-specific rules, based on a worker's work country, take precedence over the global configuration. Therefore, an organization can run automation everywhere while disabling automatic generation or automatic close and release for workers in a specific country, adopting automation gradually as local policies or requirements allow.
Failed automated actions are retried once per day, either without limit or up to a configured number of attempts, giving time to correct an underlying problem before the next attempt runs. A dedicated Automated Action Monitoring page shows the outcome of each run, with exportable logs for troubleshooting. To increase transparency, every automated action is marked as such in the request's audit trail in Planner > Pay Information, so it stays distinguishable from anything done manually.
Response Automation configuration page
Automated Action Monitoring
Demo
Simplified Workbench navigation
As Pay Transparency has grown, its Workbench navigation grew alongside it, reaching four separate sections that made related settings harder to locate.
We have reorganized the left-hand navigation into two sections, Documents and Pay Information, with monitoring for compensation round document generation moved under Documents as Comp Round Documents, alongside the other document-related settings. Several menu items have shorter names: Document Settings is now Settings, Document Templates – Templates, and Mapping Configuration – Mapping. We have added two new pages: Response Automation and Automated Action Monitoring. The order of items within each section has also been adjusted, so related settings sit closer together.
The result is the Workbench that is quicker to navigate day to day and scales better as Pay Transparency expands.
Workbench's Documents and Pay Information menu
Demo
Explicit access control for Communication Managers
Previously, controlling whether Communication Managers could see a particular communication round depended on how its hierarchy was set up. Organizations that wanted to block that access altogether had to work around it, configuring a hierarchy with no worker-manager mappings rather than switching access off directly.
Currently, the configuration step once called Hierarchy is Communication manager access under Workbench > Pay Transparency > Communication Rounds. It includes a Grant access to communication manager checkbox. Disabling it hides the hierarchy configuration and removes it as a requirement for publishing the round; Communication Managers can then no longer open the round from Planner > Documents. Enabling it restores hierarchy-based access exactly as before. Administrators can grant or remove that access directly, without maintaining a placeholder hierarchy to keep Communication Managers out. The setting governs Communication Manager access specifically and has no effect on HRBP access to the round.
Existing communication rounds that already have a hierarchy configured keep Communication Manager access by default, so nothing changes for them. Newly created rounds start with access disabled, to be enabled deliberately when appropriate.
Communication manager access step, with hierarchy enabled
Demo
Worker ID shown and searchable in communication rounds
In Planner > Documents, distinguishing between workers who share a similar or identical name, or locating one by an external identifier rather than a name, meant switching to the advanced recipient filters.
With this release, communication round document tables display each worker's ID directly beneath their name, and the search field accepts either the worker's name or this ID. Both changes apply across the relevant Communication manager review and HRBP review tabs, so searching by ID no longer requires leaving the main table, and the right worker is easier to confirm even when names repeat or look alike.
Worker ID shown beneath the recipient's name
Demo
Pay Information enhancements
Request date without a timestamp
In Planner > Pay Information, Request date represents a calendar date. However, until now, the interface displayed it with a time component that was always midnight, which could read as more precise than it actually was.
In version 27.2 of the application, Request date appears as a date only, both in the Pay information requests list and on an individual request's details page. Fields that genuinely carry a date and time remain unchanged.
Request date column shown as a date only
Sorting extended across bulk-action screens
In Planner > Pay Information, sorting was only available for a limited set of columns.
Every supported column in the Bulk actions tab can now be sorted, along with the columns in the Generate documents and Close & release screens, one column at a time. This makes it easier to find a specific execution or check results before acting on a large batch. Sorting follows the meaning of each column: text sorts in the usual way, while status columns follow their defined business sequence rather than a plain alphabetical order.
Bulk actions list sorted by request count, descending order
Smarter reminder notification deep links
Clicking a reminder about pay information requests used to land on the general Planner > Pay Information page, leaving the matching filter to be applied by hand before the referenced requests were visible.
Currently, incoming, approaching-deadline, and overdue reminders open the Pay information requests page with the corresponding filter already applied, so an overdue reminder, for instance, leads straight to the overdue list rather than the full page. The number of requests shown may not exactly match the notification's original count, since a request can change between the moment a notification is generated and the moment it is opened, but the reminder still takes an HRBP directly to the requests that need attention, saving a manual filtering step every time.