beqomPay Suite 17.1 - Feature release notes

This article details the latest improvements introduced in version 17.1 of the beqomPay Suite application, their benefits for our end-users and their principles of use.

Product Labeling

In this release, we have renamed the Pay Management pilar Compensation Management. All instances of Pay Management have been replaced in the platform and will be shortly changed in this Help Center as well.

Compensation

Configurable worker compensation history in the Planner drawer

Compensation administrators can now configure which compensation elements are displayed in the Worker compensation history section within the Planner drawer.

Previously, the compensation history view in the Planner drawer was preconfigured by the system and could not be customized. With this release, Compensation admins and Global compensation admins can define which compensation elements (such as Base Pay, Bonus, Life Insurance, etc.) should appear in the history view, and how many historical events to display (by default, 5 events are displayed, with the possibility to display 10, 15, or 20).

The configuration of the feature is available within Workbench > Compensation Management > Team planner view > Edit > Feature enablement > Worker compensation history/

History events are triggered by changes in amount (based on the effective date of change) in the corresponding compensation elements. Static reloads without data change do not create new events.

This feature offers greater flexibility for customers with frequent salary or element changes and improves the Planner experience with clearer, more relevant history data.

Compensation history display in the Planner drawer

Decimal precision standardization in statement generation

Version 17.1 of Pay Suite introduces consistent decimal precision in numeric fields in generated compensation statements.

All numeric fields in statement templates now have a default precision of two decimals, improving data readability and presentation consistency across all documents. This update applies automatically to all templates and generated statements.

This change delivers a cleaner presentation and ensures consistent, professional formatting across all customer-facing documents.

Decimal precision harmonization in compensation statements

Unified application theme configuration

Administrators can now define a global theme (i.e., application color theme) for the entire application under Workbench > Platform Setup > Appearance.

Theme configuration is now applied at system-level rather than per user. Any color theme selected by an Administrator automatically applies to all users within the tenant, independent of personal preferences or browser settings.

This update ensures a consistent look across the organization, simplifies interface management through centralized control, and improves reliability by removing browser-level dependencies.

Theme definition

Platform

Data Modeler enhancements

This release introduces major improvements to the Data Modeler experience, enabling admins to extend published models, improving usability, and introducing a new model extension flow. These updates enhance flexibility, reduce rework, and make data modeling more intuitive for administrators.

Additive data model updates

Administrators can now extend existing data models even after they’ve been selected in one or several compensation rounds or used in snapshots.

Previously, once a compensation round subscribed to a published data model, it was no longer possible to add more fields to a data model. To make changes, administrators needed to create a new model, reconnect compensation rounds, and regenerate snapshots—causing data fragmentation and operational overhead.

A new Extend model action has been added for data models marked as In use, accessible from the three-dot (⋮) menu.

This enhancement allows admins to evolve data models without recreating them, offering greater flexibility, clearer navigation, backward compatibility, and reduced administrative effort.

Data model extension

Data Modeler UX & labeling improvements

The Data Modeler interface was refreshed for clarity and ease of use, helping admins navigate and configure models with greater confidence. The purpose of these changes is to simplify navigation in the interface, reduce visual clutter and introduce naming conventions that are easy to recognize by users.

The following labeling modifications were performed for clarity:

• HRCore -> Core HR Entities

• TCM -> Compensation Entities

• CPM -> Performance Management Entities

Additionally, the expand/collapse behavior was improved:

• For new models, only primary sections such as Core HR, Compensation, and Performance Management are expanded by default, while entities within each section remain collapsed for a cleaner view.

• For existing models, only entities with previously selected fields expand automatically, keeping all others collapsed to simplify navigation.

Finally, CompensationHistory ExternalIds (such as C1, C2, etc.) were replaced with descriptive compensation element names such as Base Salary CompensationHistory or Bonus CompensationHistory.

This is an note/information message.

The backend continues using IDs for data integrity, but the user interface now exposes user-friendly labels.

Data upload: conditional validation for Min/Max and Currency fields

This release enhances data quality across Data Foundation entities by introducing conditional validation logic for Min/Max and Currency fields during ingestion.

Previously, these fields were not validated, allowing incomplete or inconsistent data to pass through ingestion. This created downstream issues for dependent modules such as Pay Transparency, Compensation Analytics, and Pay Range reporting.

The new ingestion validations ensure logical and consistent relationships between numeric ranges and currencies, while keeping these fields optional when not applicable.

With this new implementation:

• Conditional presence rules are enforced between related fields (Min, Max and Currency).

• Ordering is validated to ensure that Min is always inferior to Max when both exist.

• Clear, actionable error messages with error codes are delivered.

• Flexibility is maintained without enforcing mandatory fields when values are intentionally omitted.

The following entities and fields are impacted:

Entity	Fields
InvididualPayRange	PayRangeMin, PayRangeMax, BenchmarkRangeMin, BenchmarkRangeMax, Currency
PayScale	PayRangeMin, PayRangeMax, PayRangeCurrency
CompensationHistory	ContractedAmount, ActualizedAmount, Currency

This update improves data consistency by preventing incomplete or invalid pay range configurations and ensures downstream systems such as Pay Transparency receive valid, structured data. It also enhances error messaging with clear, actionable feedback for administrators while retaining flexibility by keeping fields optional unless logically required.