beqom PaySuite 27.1 - Feature release notes

This article details the latest improvements introduced in version 27.1 of the beqom PaySuite application, their benefits for our end-users, and their principles of use.

Compensation Management

Full recalculation of formula chains in the Planner

Previously, when several calculated fields fed into one another, updating one value did not always update all the others in the same pass. For example, selecting a performance rating in Planner > Compensation would correctly fill in a merit amount, but a differentiated merit amount further down the chain could stay blank, because the calculated field feeding it had not yet been refreshed as part of that same update.

With this release, the Planner recalculates every field in the chain as soon as one input changes, so a single selection, like a performance rating, updates the whole chain at once, including multi-step chains that combine merit and differentiated merit calculations. Fields that already worked both ways, such as an amount and its matching percentage, continue to behave as before.

Cascading custom drop-down columns

Until now, custom drop-down columns could already pull their values from a data source, but managers or HRBPs would still see all available options in Planner > Compensation regardless of context, for example every city in the list even after a country had already been chosen.

This release allows administrators to turn on cascading for any custom drop-down column in the Team planner view step under Workbench > Compensation Management > Compensation Rounds. As a result, its list narrows down to only the options that make sense given what has already been filled in elsewhere, based on a table of valid combinations, like limiting city choices to the ones that belong to the selected country. Up to five matching conditions can be combined for a single column, and the list updates automatically as related columns change, clearing a selection that is no longer valid.

Cascade settings for a custom drop-down column

Broader reference-field choices for salary compensation elements

The reference field used to calculate a salary compensation element's increase, known as Current Salary, could previously be chosen only from a limited set of historical salary fields tied to the same element.

In the Team planner view's Column configuration tab under Workbench > Compensation Management > Compensation Rounds, Global Compensation Admins and Compensation Admins can now choose any decimal field in the round as the reference field, whether a calculated field, a custom column, or a currency field, with no restriction on its source or matching code. Also, in the Planner calculations tab, calculation rules can use a calculated field, or multiple fields, as a trigger. This way, a rule runs whenever any of its trigger fields changes. These improvements make it possible to chain compensation elements together, for example basing one element's increase on a calculated value derived from another element.

Flexible visibility depth for indirect compensation managers

In the Actors & round access step under Workbench > Compensation Management > Compensation Rounds, the Compensation manager indirect actor was previously fixed to seeing a single level below a manager, leaving administrators no way to adjust that reach.

Version 27.1 of the application lets Global Compensation Admins and Compensation Admins set a hierarchy depth of one, two, three, or all levels below for this actor, with a preview showing the resulting hierarchy tree before saving. After a round is published, Planner > Compensation reflects this depth for a manager viewing as Compensation manager indirect, limiting both the worker grid and the manager filter to the configured levels. The round and the indirect view option appear only when at least one worker actually falls within range. The configured depth carries over when a round is duplicated, and can be adjusted on a published or in-progress round through a pending draft.

Setting a manager's Hierarchy levels

Configurable Anchor field for Planner calculation cycles

In cases where a group of fields derived one another in a calculation cycle, for instance a new value, increase amount, and increase percentage, it was not always clear which field should be treated as the source of truth when the whole cycle needed to be resolved at once.

Currently, administrators can choose an Anchor field for each cycle in the Team planner view's Planner calculations tab under Workbench > Compensation Management > Compensation Rounds. The system recommends a default based on the fields' relationships, though a different field can be selected instead. The anchor's value is never overwritten when the cycle is recalculated, whether triggered by a related field elsewhere in the round or by publishing. On publish and re-publish, Planner calculations now run for every cycle across all workers in the round, deriving every other field in the cycle from the anchor. If the calculation fails for any worker, the publish stops and no partial changes are saved.

Choosing a cycle's Anchor field

Clearer errors for oversized lookup tables in calculated fields

A calculated field that looked up values in a large custom entity, such as a merit matrix with more rows than the system could support, used to fail silently, returning an empty value with no explanation.

Calculated fields that reference a custom entity of more than 10,000 rows now show a clear "Unable to calculate" error, both in Planner > Compensation and in the published round under Workbench > Compensation Management > Compensation Rounds. Entities within the limit continue to calculate normally. The underlying calculation engine has also been made more resilient: a temporary failure to reach the data source is no longer treated as an empty result, and changes to bonus plans or datapoints now take effect immediately instead of waiting for old, cached data to clear.

Pay Transparency

Editable reference number on HRBP-created pay information requests

Until now, an HRBP who noticed a mistake in a pay information request's reference number could only fix it by recreating the whole request from Planner > Pay Information.

With this release, the reference number can be edited directly, as long as the request is still in the New or In progress status. This lets HRBPs correct manual entry mistakes or align a request with an internal case management system without starting over. This only applies to requests HRBPs create themselves; requests submitted by workers through the digital reward statement or imported via an API stay read-only, and once a request reaches Pending release, Closed, or Closed without document, its reference number becomes read-only as well. Every edit is recorded in the request's Audit trail, including the previous and new values, so full traceability is preserved.

Editing a request's reference number

New toggle to show records without documents in communication rounds

In large communication rounds, documents are often generated in phases, which used to leave the HRBP review list cluttered with records that were not yet ready for validation.

For a cleaner experience, we have introduced a Show records without documents toggle in the HRBP review view, available under Planner > Documents. It is off by default, so records without a generated document stay out of view and HRBPs can focus on what can actually be reviewed. Switching it on brings back the full list, including records still waiting on a document. The toggle only changes what is shown in that view and does not affect the underlying communication round data.

HRBP review with the Show records without documents toggle

Pay Intelligence

New Draft goal progress column in the Goal Details report

The Goal Details report has always displayed published goal progress, but not any progress a manager had saved as a draft and not yet published. That gap made it difficult to report on where goals actually stood while results were still being finalized.

From now on, the Goal Details report, available under Analytics Hub > Goals, includes a new Draft goal progress column next to the existing Goal progress column. Goal progress continues to show the currently published value, while the new column presents progress saved as a draft but not yet published; it stays blank when no draft exists for a goal. This enhancement allows HR users to compare published and draft progress side by side, and report on draft values before managers publish their changes. Everything else in the Goal Details reports works exactly as before.

Goal progress and draft progress columns side by side

Data Foundation

Historical export and re-upload for the Data Viewer

When exporting data from Workbench > Data Management > Data Viewer, administrators could obtain current data, but not historical revisions, and there was no supported way to update an export and bring it back into the platform.

We have covered both of these gaps. Historical export is now available directly from the Data Viewer, letting the Data Foundation Admin, Configuration, and Support roles export revision-based data for selected entities rather than just the current state. Exported files can also be updated externally and re-uploaded through Workbench > Data Management > Data Load, which enables a controlled export, edit, and re-upload cycle. Exports continue to be delivered as ZIP archives, with optional password-protected encryption when enabled for the tenant.

Together, these changes make it easier to validate and reconcile data by comparing exports against source files, and to manage the update process.

History export type selected in the Data Viewer