beqomPay Suite 16.0 - Feature release notes
This article details the latest improvements introduced in version 16.0 of the beqomPay Suite application, their benefits for our end-users and their principles of use.
Compensation
Collaborative workflow
A new Collaborative workflow feature has been introduced in Compensation, offering greater flexibility and control in managing compensation rounds. This enhancement enables dynamic adjustments to permissions and access for key roles—such as HRBP, Manager, and Manager+1—even while a compensation round is in progress. The feature provides increased flexibility in handling in-progress compensation reviews, improves collaboration across multiple roles without disrupting the ongoing workflow, and gives administrators enhanced control over access, visibility, and contribution rights.
Administrators can assign Read & Write, Read-Only, or No Access to each role, as shown in the following illustration:
Collaboration settings
Permissions can be changed at any stage of a compensation round, even while it is in progress. For role visibility, Read & Write allows users to submit proposals; Read-Only grants visibility without the ability to make proposals; and No Access hides the round from the role entirely.
Key dates can now be defined for permitted edits. Collaboration settings can also be tailored for each role to align with organizational needs.
From the HRBP view, HRBPs can view compensation rounds and submit proposals for their assigned workers. In the Manager view, managers are empowered to submit proposals for both direct and indirect reports within the collaborative workflow. The experience is consistent with existing workflows for salary and bonus reviews. All proposals are tracked in the Audit trail in Planner.
Demo
Conditional formatting in compensation rounds
A new Conditional formatting feature has been added to Compensation Management, enhancing the Planner experience. This functionality allows administrators to highlight important data points, bringing visibility to exceptions or key values through configurable rules. This improves visibility for managers on key compensation elements, offers flexible and configurable rules to match organizational needs, and provides an enhanced user experience with clear visual indicators for data-driven decision-making.
Compensation administrators can define custom formatting rules for individual columns directly in the Team Planner.
Rules can be based on fixed values, formulas, or comparisons with other fields, and they support logical operators and mathematical expressions. These rules allow for the assignment of a background color to highlight cells that meet specific conditions, as illustrated in the following picture:
Rule formatting drawer
Each rule can have a name and an optional description for clarity. Rules can be prioritized by dragging and dropping them, ensuring that higher-priority rules override lower ones when conditions overlap, as shown in the following image:
Rules drawer
The highlighting is applied immediately in the Planner for users whose data matches the conditions.
The feature is available to Compensation Admins and Global Compensation Admins under the “Conditional Formatting” option in the three-dot menu next to each column, as presented in the following image:
Conditional formatting button
Managers benefit from the highlighted cells in the Planner view, which improves visibility into critical data during compensation reviews, as shown in the following picture:
Grid view with conditional formatting
Demo
Performance Management
Score calculation feature
The Score Calculation feature enables organizations to rate goals and custom widgets during the performance review process, which then automatically generates a final weighted employee score. This capability, initially developed for a specific client, is now available to all clients. It is particularly useful for bonus calculation, dashboards and analytics, and talent calibration for year-end rankings.
Administrators can now enable score calculation while creating or editing a review template, as illustrated in the following image:
Score calculation check box
Once enabled, the system will automatically calculate a total score at the end of the review form.
Within a score-enabled template, administrators define which sections will contribute to the total score. Common sections include Goals and custom widgets that contain rating questions. Each of these sections must be assigned a weight (e.g., 33.3% each), with the total weight for all sections equaling 100%. The system will validate this total before allowing the template to be published, as illustrated in the following picture:
Section weights
When a manager uses a score-enabled template to complete a performance review, they rate the goals and any custom widget questions. The system then dynamically calculates the scores in a new widget called Achievement Summary, located at the bottom of the review form.
Achievement Summary Includes:
| Field | Description |
|---|---|
| Average Score | Based on manager’s responses within the section |
| Max Score | Highest possible score in that section |
| Weight Factor | Section weight as defined by admin |
| Weighted Score | Section’s contribution to the final score |
This widget updates automatically as the manager modifies ratings.
Employees cannot see this widget while the form is still in progress. Once the manager submits the form and it moves to the "Employee Sign-Off" step, the employee can then see the same Achievement Summary section, ensuring full transparency after the evaluation is complete.
Team Planner & Dashboard enhancements
We've redesigned key parts of the Planner to improve usability, streamline team navigation, and surface insights more intuitively.
Clickable user summary
You can now click on an employee's name directly from the Team Dashboard to open their full summary view. This new feature provides faster access to individual review data and allows for a one-click drill-down into key performance insights, as shown in the following picture:
Employee's full summary view
Employee Selection Redesign
The multi-select panel on the left side, previously used for selecting employees, has been removed. A new, cleaner drop-down menu now allows users to quickly select and switch between employees in a more compact layout, as illustrated in the following image:
Workers drop-down menu
Platform
Snapshot Manager: export snapshot as CSV
A new enhancement has been added to the Snapshot Manager in the Data Management section of the Workbench: users can now export snapshots as CSV files. This improvement makes it easier to work with snapshot data outside the platform while prioritizing security.
To export a snapshot, user must first select the snapshot and click Download CSV button, as shown in the following image:
Snapshot details drawer
Then, user will be prompted to define a password that must meet the following requirements:
Minimum length: 5 characters
Maximum length: 15 characters
At least one uppercase letter
At least one lowercase letter
At least one number
The snapshot will be downloaded in a password-protected ZIP folder, ensuring the secure handling of sensitive data.
GrantFullAccess ABAC subject attribute
We've introduced a new GrantFullAccess subject attribute to simplify and standardize how administrators grant full data visibility across the product.
GrantFullAccess is a boolean attribute (TRUE / FALSE). When set to TRUE, the user gains visibility to all workers. Other scoping attributes, such as WorkCountry, OrgItem, and cohorts, are ignored. However, exclusions always apply, meaning any excluded employees or organizational items will still be filtered out. When set to FALSE, standard ABAC/RBAC rules, cohorts, and overrides apply as usual.
The attribute can be managed through a Professional Roles CSV upload, which includes a new GrantFullAccess column that supports TRUE/FALSE values, or through the Authorization API, which accepts a GrantFullAccess boolean field in the payload.
Example Scenarios
Grant full access with exclusions: A user with GrantFullAccess=TRUE and ExcludeEmployeeIds=[101,202] will see all workers except employees 101 and 202.
Other attributes ignored: A user with GrantFullAccess=TRUE and WorkCountry=IE will see all workers globally, not just those in Ireland.
Fallback: A user with GrantFullAccess=FALSE continues to follow normal ABAC/RBAC logic.