beqom PaySuite 27.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 27.1 release of the beqom PaySuite application and in the subsequent patches.
27.1
Deployment to staging environments: August 4th, 2026
Deployment to production environments: August 11th, 2026
| Type | Issue key | Module | Description | |
|---|---|---|---|---|
| Zendesk | Jira | |||
| AC-31476 | Compensation Management | Under Workbench > Compensation Management > Bonus Plans, payout curve dropdowns in the Goal plan step (goal rows and the bulk assignment modal) now load their options only when opened, instead of loading the full list on page load. Searching for a payout curve by name now queries the server as the user types instead of filtering a preloaded list, so plans with a large number of curves load and search faster. | ||
| AC-29993 | Data Foundation | In Analytics Hub, the standard Goal Details report now includes a Draft goal progress column alongside the existing Goal progress column, so draft progress entered by managers before publishing can be compared against what has already been published. | ||
| AC-30123 | Data Foundation | Analytics Hub's Compensation Process Status, Salary Increase Allocation Overview, Pay & Performance, and Bonus/Salary Comp Round Export Details reports were migrated onto the centralized lakehouse-based analytics architecture, with report output validated to match the previous implementation. | ||
| AC-30423 | Compensation Management | Under Workbench > Compensation Management > Compensation Rounds, custom drop-down columns in the Team planner view step can now be configured to cascade from other columns: an administrator can narrow a drop-down to only the values that match a combination table based on other columns already filled in a round (for example, narrowing City options once a Country is selected). Cascading only narrows the existing option list, as it never adds new values. Changing a referenced column re-evaluates the drop-down and clears a selection that is no longer valid. | ||
| AC-30834 | Compensation Management | The reference field on a Salary compensation element can now point to any decimal field in the round, including calculated fields, rather than being limited to specific compensation history fields with a matching element code, so compensation elements can be chained together (for example, a merit calculation feeding an adjusted merit element). Calculated fields can now also be used to trigger Planner calculation rules, and a rule can be configured with multiple trigger fields. | ||
| AC-31089 | Compensation Management | Compensation round configuration now lets an admin designate one field per calculation cycle as the anchor (the source-of-truth value that is never overwritten when the rest of the cycle is recalculated), with a system-recommended default that can be overridden. Publishing or re-publishing a round now recalculates every cycle from its anchor across all workers, rather than only the default salary cycle. | ||
| AC-31243 | Compensation Management | Under Actors & round access step under Workbench > Compensation Management > Compensation Rounds, admins can now configure how many hierarchy levels below a manager the Compensation manager indirect actor can see, instead of a fixed one-level-down view. The configured depth determines both the population a manager sees when viewing a round as that actor in the Planner and whether the round and the indirect view option are shown to that actor at all. This depth also carries over to round duplication and pending draft edits. | ||
| AC-31779 | Pay Transparency | HRBPs can now edit the reference number on a pay information request they created while it is still in the New or In progress status. They no longer need to close and reopen the request to correct a mistaken value. The change is recorded in the request's audit history. | ||
| AC-31862 | Pay Transparency | A Show records without documents toggle was added to the communication round view for HRBP review in Planner > Documents, matching the existing Show closed requests toggle in Pay Information. It is off by default, so records without documents stay hidden until switched on. | ||
| AC-31229 | Compensation Management | In Planner > Compensation and Workbench > Compensation Management > Compensation Rounds, calculated fields that look up a custom entity with more than 10,000 rows now show a clear "Unable to calculate" error instead of silently returning an empty value. A transient failure to read the entity's structure no longer gets cached as "no such entity," so calculations recover automatically once the connection is restored. Calculation rules now pick up configuration changes without waiting for a cache to expire. | ||
| AC-31268 | Compensation Management | In Planner > Compensation, changing an input that starts a long chain of calculated fields (for example, a performance rating that feeds a merit calculation, which feeds a differentiated merit amount) now correctly recalculates every field in the chain from a single change. Previously, a field at the end of such a chain could be left blank because an intermediate calculated field was not refreshed. | ||
| AC-30890 | Data Foundation | In the Calculated Fields list under Workbench > Data Management, searching for a calculated field whose name contains an underscore (for example, Test_Calc) returned no results. The search now matches these fields correctly. | ||
| 155840 | AC-31013 | Pay Transparency | Workers were not able to properly open their own digital reward statement and received a 403 Forbidden error, because the page incorrectly required an administrative permission to view it. Workers can now view their statements using their identity from their login session. Access to change digital reward statement settings still requires the Configuration or Support role, and HR users' access is unchanged. | |
| 157223 | AC-31146 | Data Foundation | The Performance Reviews report in Analytics Hub could show data that was a day out of date because the underlying semantic model was not always refreshed after the nightly data job completed. The refresh now triggers automatically every time the nightly job finishes successfully. | |
| AC-31708 | Compensation Management | In the Column configuration tab of a compensation round's Team planner view, Bulk options > Delete stayed disabled for a newly selected set of custom or calculated columns after a first successful bulk delete, requiring a page reload to delete again. The header select-all checkbox also stayed checked with no rows selected. Selection now resets automatically after a successful bulk delete, so further deletions work without reloading the page. | ||
| 154050, 156967 | AC-31833 | Authorization | Exporting Professional Roles data from Access as a CSV could drop the UTF-8 marker needed for Excel to correctly display accented characters, so names with characters such as é or ü could appear garbled for some customers depending on their Excel version and regional settings. The exported file now includes the marker, so accented characters display correctly regardless of the Excel version or locale. | |
| AC-32016 | Data Foundation | For some tenants with large data volumes, a stalled or memory-limited step in the nightly data ingestion job could sit for up to 12 hours before failing, delaying that day's reports. Ingestion steps now fail fast and retry automatically, so a transient issue no longer holds up the full daily run. | ||
| AC-32046 | Data Foundation | Downloaded custom localization templates were missing the UTF-8 marker needed for Excel to display special characters correctly, so accented characters in files such as the French template appeared garbled. Downloaded templates now include the marker, so special characters display correctly without needing a text editor. | ||
| 157078 | AC-32200 | Compensation Management | Previously, a compensation round with a bonus plan could publish with every bonus datapoint unassigned and blank, while salary datapoints published correctly. Also, a bonus-only round (with no salary compensation element) could not be created at all. Bonus datapoints now publish with correct values for both bonus-only and salary-and-bonus rounds, and a round can be created using only a bonus plan. | |
| AC-32111 | Pay Transparency | Searching the Pay information requests list in Planner > Pay Information only matched workers who also have a user account, so a request created for a worker without one could not be found by search. Search now matches any worker regardless of whether they have a user account. | ||