beqomPay Suite - Data Foundation feature release notes

beqomPay Suite 22.0

New worker view in Data Management

Version 22.0 of the application introduces a new worker view in Data Management. With the Consolidated Contextual Data Viewer, users who have permission to access worker data can explore such information in a clear and intuitive way. Previously, validating this data required relying on entity-based views and interpreting technical identifiers. The new view offers a people-centric entry point to locate and review workers using familiar attributes, which makes it easier to understand worker context at a glance.

Users can now view a grid that displays all workers they are authorized to see. The grid presents information in a business-friendly format that eliminates the need to navigate schema-level entities. It is modeled around the Worker as the primary object and surfaces relevant contextual information such as employment and organizational attributes.

New worker grid

To quickly find workers, the grid includes a search bar that supports flexible matching by first name, last name, or full name, returning relevant results even when only part of a name is entered or when the match occurs within the name. Additional attributes such as worker ID, email, and other worker fields can be used through the filter options. Columns can also be sorted to organize the list based on available attributes. This allows users to efficiently locate workers, even with partial information at hand.

Search results with part of a name entered in the search bar

Moreover, the worker grid supports configurable columns, allowing users to tailor the view to their needs. All available attributes are organized by domain, for instance Worker, Employment, or Demographics, and can be individually toggled on or off. For example, within the Worker group, users can choose to display or hide attributes such as FirstName, LastName, or WorkEmail. Additionally, it is possible to reorder columns within their respective groups to personalize the grid layout.

To maintain clear identification, the worker's name and ID remain visible and fixed in the grid.

Column configuration option

Importantly, the worker view automatically remembers the last grid configuration in the same browser, including selected columns, applied filters, sort order, and search input, so users can pick up right where they left off.

Worker visibility respects user permissions, ensuring each user only sees workers they are authorized to access.

Overall, the new view enables faster worker discovery. It reduces reliance on schema-based data views and improves usability for users who manage or validate worker information. It also provides a strong foundation for future worker data management capabilities.

Demo

Enhanced custom label management via CSV

This release enhances the Custom Labeling CSV import, providing administrators with clearer control over applying and removing custom labels. We have added a new column, is_custom_value, to the CSV template. The column allows administrators to explicitly revert custom labels back to the system's standard value without needing to manually re-enter the original translation.

Changing the value in the custom_value column automatically applies the custom label during the upload, while setting is_custom_value to FALSE removes the custom override and restores the standard system label. If the user removes all custom labels for a language, the Translation source in the UI automatically changes from Custom back to Standard. The Audit trails show the number of labels reverted during each upload.

Information on label reversion in the Audit trails

For example, to apply a custom label, users can set a custom value in the CSV by changing the standard Home to Start for the nav_home key. To revert back to the standard label, they simply need to set is_custom_value to FALSE and upload the file. This removes the custom override and restores the original Home label.

It is worth noting that when reverting a label, the previously used translation may remain in the custom_value column of the CSV template. In this way, administrators can easily reuse the translated value later by setting is_custom_value back to TRUE.

This enhancement facilitates bulk management of custom labels. It gives users explicit control to revert labels to standard values, as well as the ability to reuse previously translated custom values. It additionally improves transparency through audit logging.

Demo

beqomPay Suite 21.1

Snapshot Manager access and data security improvement

Version 21.1 of the Pay Suite application improves Snapshot Manager access and data security for better alignment with role responsibilities and users' expectations toward data access. This ensures that snapshot data is available only to appropriate roles and that exported data always respects access permissions.

Only roles that require technical or administrative control can now access the Snapshot Manager:

The PayAnalytics Editor and Compensation Manager roles no longer have access to the Snapshot Manager, as these roles should use planner-based and workflow-driven features instead.
The Global Compensation Admin, Pay Analytics Admin, Data Modeler Admin, and Configuration roles retain full Snapshot Manager access, including the ability to view, create, and export snapshots.
The Data Foundation Admin role now has limited access, allowing users to create snapshots and export snapshot data without broader snapshot management or administrative capabilities.

Moreover, snapshot CSV exports now respect data access permissions. Exported files will only include workers that the user is authorized to see based on their role and access permissions. This applies to all roles that can export snapshot data. If a user's access is restricted, for example by country or organizational scope, the CSV export may contain a subset of the snapshot population, and a warning message will be displayed to indicate this limitation.

Snapshot CSV export warning message

Thanks to these changes, worker data can be handled in a consistent and secure way while maintaining the existing snapshot functionality.

beqomPay Suite 19.1

Custom labeling management in the Workbench

In version 19.1, we're introducing the Custom Labeling feature in the Data Management section of the Workbench. Available to the Configuration and LocalizationAdmin (new role) role, this feature offers customers control over labels across their tenants per language.

When this feature is used to define organization-specific terminology, the standard labels of the platform are overridden, ensuring that the product reflects the internal language, branding, and regional conventions of individual customers.

The new LocalizationAdmin role is designed specifically for managing localization and translation-related configuration within the Workbench, without requiring broader configuration permissions.

Overall, this new feature provides fine-grained control over product terminology across languages, a dedicated role for localization management, clear visibility into customized languages, full auditability of labeling changes, and ensures standard labels remain unaffected unless explicitly overridden.

Here are the main capabilities of the custom localization management feature:

Manage labels per language: users can view all the languages available in their tenant, clearly identify the languages for which custom labels have been applied, and select one or several languages to manage in a single action:

Label management interface in the Workbench

Download & edit CSV templates: for each selected language, a CSV file containing all customizable labels can be downloaded. Each file contains three columns:
- Key: unique identifier of the label within the system
- Standard_Value: default platform label
- Custom_Value: location in which to enter custom labels. Only the changes made in this column are applied; any changes to the values in the other two columns are disregarded to preserve system integrity.
Downloaded files are automatically named using the relevant language code. For example, en-US.csv for United States English, fr-FR for French, de-DE for German, etc.
Upload updated labels: at each upload, it is possible to select one or multiple files to be processed simultaneously. During upload, the system automatically performs a number of validation checks and successfully processed files are immediately applied to the tenant.

File upload window

Language file template selection

File upload process

Upload outcome

Audit trail & observability: clicking any of the languages in the language list opens a drawer containing information such as the last update date, the user who made the last update, and the translation source (standard or custom). In addition, a full audit trail is available per language, including the upload history, the number of labels created or skipped, and the import metadata for observability and compliance.

Language details

Audit trail

beqomPay Suite 19.0

Notifications for failed data upload requests

Data foundation admins can now configure automated notifications for failed data upload requests directly from the Data Upload section of the Workbench.

When an upload request fails, configured recipients will receive an email and an in-app notification containing a deep link to the Data Upload view for quick investigation. This ensures ingestion failures are surfaced proactively without the need for manual monitoring.

Previously, admins had to repeatedly check the Workbench UI to monitor ingestion request statuses, which was inefficient, time-consuming, and error-prone. Failures could be missed, delaying issue resolution. Automated notifications improve visibility, reduce time to resolution, and increase confidence in upload reliability.

Notification configuration entry point

Upload failure email notification

beqomPay Suite 18.1

Improved hierarchy selection for population criteria

We have significantly improved the population definition process by introducing hierarchy-aware selection capabilities for organizations, legal entities, and cost centers.

Instead of manually typing External IDs, users can now select values from an intuitive visual pop-up that displays both the ID and name of each entity, making selection more user-friendly and accurate. The new interface offers full hierarchy awareness, allowing users to select parent entities and automatically include all sub-entities, with expandable/collapsible hierarchical structures for easier navigation. Population previews were also enhanced to explicitly show which entities and sub-entities are included, providing greater transparency and reducing configuration errors.

The system now intelligently adapts to different operators:

IN / NOT IN: supports multi-select
EQUAL TO / NOT EQUAL TO: enforces single-select only

These enhancements significantly improve usability, reduce the likelihood of configuration mistakes, and make population creation more intuitive for all users.

Hierarchy selection for population definition

New compensation data schema

We have redesigned our compensation data architecture to address significant challenges with the previous single-entity approach.

Previously, all worker compensation records were stored in a unified CompensationHistory entity, which forced users to fit both contracted and paid compensation data into a single structure. This design created multiple operational inefficiencies:

It required effective date ranges even for point-in-time events like salary changes
Necessitated the use of arbitrary far-future end dates (such as 2099-12-31) to maintain current records
Imposed substantial change management overhead. When compensation changed, existing records needed to be closed by updating end dates and insert new records with updated rates.
Because the business key couldn't be updated incrementally, any changes required full historical re-ingestion, making the system difficult to maintain and creating unnecessary complexity for what should have been straightforward compensation updates.

The new schema introduces two separate entities, each serving a clear and distinct purpose.

ContractedCompensation entity

Used to store what is contracted for a worker (such as salary, pension, allowances, on-target bonus). This entity uses a single effective date per record - no end date required.

It is ideal for base salary, on-target bonus (OTB), pension contribution and fixed or recurring allowances.

Here are the key fields of this entity:

WorkerExternalId: unique worker identifier
CompensationElementExternalId: Links to the relevant compensation element
AmountSource: enum value indicating how the amount is derived: FixedAmount (for example, base salary) or Percentage (for example bonus as % of base pay)
Currency: currency of the contracted amount
ContractedAmount: agreed amount
Percentage: percentage of the element. (for instance, 15 for an OTB record)
PercentReferenceCompElementExternalId: If AmountSource = Percentage, this links to the referenced compensation element (for example Base Pay for OTB)
CompensationReason: reason for the update (optional)
EffectiveDate: date the record becomes effective

PaidCompensation entity

Used to store what has been paid to workers. This entity uses effective date ranges (start and end) - making it ideal for payments that occur over a period.

It is ideal for actual bonus payments and historical compensation payments.

Here are the key fields of this entity:

WorkerExternalId: unique worker identifier
CompensationElementExternalId: Links to the relevant compensation element
Currency: currency of the contracted amount
PaidAmount: amount paid to the worker
PaymentDate: specific date the payment was made
DerivedFromCompElementExternalId: new field that links the payout to the related contracted element (for example, Bonus Payout derived from on-target bonus)
CompensationReason: reason for the payment
EffectiveRangeStartDate: defines the start of the payment period
EffectiveRangeEndDate: defines the end of the payment period

Benefits of the new structure

Both ContractedCompensation and PaidCompensation entities now reference a shared CompensationElement entity, which defines the structure and characteristics of each compensation type (such as base pay, bonus or allowance). This architectural separation enables simpler ingestion logic without requiring future-dated end dates, provides cleaner business logic with dedicated entities for contracted terms versus paid history, and facilitates easier incremental updates without full historical reloads. The new schema delivers significant operational improvements:

Simpler data management: update single effective-dated records instead of managing open date ranges
Better data clarity: clear distinction between contracted and paid compensation
Faster and safer ingestion: smaller, incremental updates reduce complexity and processing time

This redesigned approach eliminates the complexity of the previous unified model while providing a more intuitive and maintainable compensation data structure.

beqomPay Suite 17.1

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 Management Entities
CPM -> Performance Management Entities

Additionally, the expand/collapse behavior was improved:

For new models, only primary sections such as Core HR, Compensation Management, 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.

beqomPay Suite 17.0

Gender enum update

The Gender enum, which is referenced in the Demographics entity has been updated from a standard enum to a predefined enum with standard values. This change standardizes gender data across the platform, enabling more consistent categorization and improved analysis of worker demographics in Pay Suite.

By moving to a standardized set of gender values, customers can benefit from enhanced reporting accuracy and alignment with best practices in workforce analytics.

The standard values for the Gender are the following:

Male
Female
Other
Unknown

beqomPay Suite 16.1

Population criteria update

In this version, the logical operator used between criteria blocks in the Population Builder, within the Data Management section of the Workbench, was updated.

Previously, criteria blocks were joined using the AND logic (i.e. a restrictive logic where all criteria must be true); they are now joined using the OR logic (i.e. an inclusive logic where at least one of the criteria must be true), aligning with how criteria blocks function in other areas of the product (such as the compensation round eligibility criteria).

This change makes the behavior consistent across the platform and easier to understand when defining complex populations.

Effective dates in the Data Viewer

The Data Viewer, under Workbench > Data Management > Data Foundation, now displays EffectiveDate columns for all effective-dated entities.

This enhancement allows users to:

View effective dating directly in the Data Viewer.
Track data validity across different timeframes more efficiently.
Improve confidence in reviewing and validating effective-dated records.

Data Modeler - Remove "Preview grid"

The Preview grid action was removed from the Data Modeler. Instead, users can now leverage the new Snapshot Manager, available in the Data Management section of the Workbench.

Using the Snapshot Manager, it is possible to create a snapshot based on a data model and then export it for detailed review.

This change provides a more consistent and powerful way to validate and analyze data models before they are used in compensation rounds or other processes.

This is an note/information message.

For more information on the Snapshot Manager and how to export, see Snapshot Manager and Snapshot manager: export snapshot as CSV.

beqomPay Suite 16.0

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.

beqomPay Suite 15.1

Incremental data upload for CSV (UI & SFTP)

We're excited to announce the addition of a new Incremental data upload method for CSV files, available through both the UI and SFTP.

We now support two upload modes:

Full data upload (existing option): Upload the complete effective-dated history for each worker included in the file. Any previously uploaded worker records missing from the file are treated as soft deleted.
Incremental data upload (new option): Upload only what has changed. New effective-dated records are added, and existing records are updated when field values change. Records not included remain unchanged.

The Full data upload view is illustrated in the following picture:

Full data upload overview

This update offers greater flexibility, allowing users to choose between sending complete history files or just the latest changes. This improves efficiency, as users no longer need to resend large history files when only a small number of records have changed. It also supports different customer feeds, working with both one-time historical backfills and ongoing change feeds.

It is available in:

UI Uploads: A new configuration option is available when customer sets up their data upload behavior. It is possible to select either Full data upload or Incremental data upload.
SFTP Uploads: The chosen configuration automatically applies to files sent through SFTP.

This is an note/information message.

This is a global setting, meaning your chosen behavior applies to both CSV uploads via UI and SFTP.

Review your current upload process and select the method that best matches your source system. If you generate full history extracts, continue using Full data upload. If you generate change-only feeds, switch to Incremental data upload for better efficiency.

Snapshot Manager

Release 15.1 introduces Snapshot Manager, a new capability within the Data Management section of the Workbench. Snapshot Manager provides admins with greater control and visibility over how data snapshots are created and managed. It ensures data consistency by capturing point-in-time records tied to compensation and performance processes.

Create data snapshots: It is now possible to generate new snapshots directly from the Workbench. User can select a data model, set an effective date, and optionally choose a population to capture a precise snapshot of worker data.

Worker categories for analysis: Define specific fields (e.g., gender, country, language) as worker categories. These categories enable deeper insights and analytics on snapshots, such as monitoring the gender pay gap or comparing compensation by location.

This is an note/information message.

The order you define in this section will reflect the final order of the fields used for categorization.

The Create snapshot window is illustrated in the following image:

Create snapshot window

View & manage snapshots: Browse all previously created snapshots with full details, including the snapshot name, data model, effective date, creation date, owner, and status (e.g., Pending, Published, Failed). You can also drill into snapshot details to see included fields and worker categories, and download snapshot logs for auditing and troubleshooting.

The overview of the Snapshot Manager is shown in the following illustration:

Snapshot Manager overview

Status Tracking: Snapshots now display real-time progress indicators to track their lifecycle:

Pending: waiting to start
Started: snapshot generation in progress
Published: snapshot successfully created and available
Failed: snapshot generation was unsuccessful
Stale timeout: snapshot creation did not complete within the allowed time

Search & Filter: Quickly locate snapshots using filters for snapshot name, data model, and status.

The Snapshot Manager can be accessed by users with the following roles: Data Modeler Admin, Compensation Admin, and Global Compensation Admin.

beqomPay Suite 15.0

Data viewer enhancements

A series of powerful enhancements have been implemented to the Data viewer, located within the Data Management section of the Workbench. These updates are designed to streamline the exploration, navigation, and analysis of your uploaded data.

Key enhancements:

Entity & enum navigation: users can now browse data uploaded into both entities and enums. The improved navigation allows for seamless switching between these data types without having to return to the main page.
Homepage overview: the homepage now provides a comprehensive overview of all accessible entities and enums, including high-level record counts. A search function has been added to locate specific entities or enums, with the option to filter by type.
Improved data exploration:
- Pagination: users can select the number of records displayed per page and navigate efficiently between pages.
- Data refresh: the view can be updated to reflect the most recent data ingestions.
- Filtering: the system now supports the application of criteria, operators, and values to locate specific records. Filtering options dynamically adapt to the data type, ensuring more precise results.
- Column sorting: data can be sorted in ascending or descending order by simply clicking the column header.

These enhancements significantly improve the usability of the Data viewer, providing a faster, more intuitive, and more efficient method for exploring data within the Data Foundation.

Demo

beqomPay Suite 14.1

Compensation round statement generation enhancement in Data Foundation

A new enhancement to the Statement Generation feature in compensation rounds gives administrators more flexibility and control over file naming and rule management.

This feature is available for Configuration, Compensation Admin and Global Compensation Admin professional roles

Custom File Naming

Users can now create dynamic and personalized file names for employee statements by combining field variables and free text.

Field Dropdown: Choose from a list of available fields from the compensation round (e.g., WorkerFirstName, WorkerLastName, etc.).
Text Dropdown: Add custom text (e.g., year, document type).
Expression Builder: Use a visual interface to build the file name structure.
Expression Formula Preview: See a preview of the generated format before you apply it (e.g., "John-Doe-2024").

File name section

The total file name is capped at 256 characters. This enhancement helps create clear and organized statement files.

Rule Management

Users can now more easily manage statement generation rules with two new options:

Delete Statement Generation Rules: Users can delete a Statement Generation Rule that is in "Draft" status. Use the contextual menu (⋮) to find the delete option.
Duplicate Statement Generation Rules: Quickly replicate a rule by using the new Duplicate action to create a copy of an existing rule, saving time when setting up similar rules.

These enhancements make statement generation more flexible, intuitive, and efficient for administrators.

beqomPay Suite 13.1

Data upload from Workbench

A new, much anticipated capability is now available in Workbench: data upload. Using a dedicated interface available under Workbench > Data Management > Data Upload, CSV files can now be uploaded from the application user interface to populate the data foundation. This feature streamlines how data is uploaded into entities and enums, and provides a clear, centralized view of all upload activities across a tenant.

CSV upload support

Data is easily uploaded using CSV files, via drag-and-drop or file selection. Data foundation administrators can upload up to 50 files at once, with a combined maximum size of 10MB.

The following figure illustrates the data upload interface:

CSV selection window

Upload activity overview

Upon opening the data upload interface, data foundation administrators are presented with a dedicated table that displays executed and ongoing uploads. For each upload, the table lists:

The name of the entity or the enum
The upload status
The upload source (CSV or API)
The start time and the completion time

The following figure illustrates the upload table:

Upload table

Detailed upload view

In the upload table, clicking any upload will open a convenient drawer on the right side of the application window in which the user can download the upload log file or download the original CSV file (if the upload was done from a CSV file).

Powerful search & filter options

The new interface comes with powerful search and filter options that enable users to retrieve uploads by their name and filter uploads by status, source and start date and time, as illustrated in the following figure:

Data upload filtering

Downloadable CSV templates

Templates for all supported entities and enums can be downloaded from the Data Upload page to ensure that data is correctly structure before upload, thus eliminating a large number of upload errors.

beqomPay Suite 1.12

Benchmarking data integration in IndividualPayRange

The IndividualPayRange entity was improved to directly support and manage benchmarking data for each individual worker.

Three new optional fields, BenchmarkRangeMin, BenchmarkRangeMid, and BenchmarkRangeMax, have been added to the entity, all supporting numeric values. These new fields enable admins to upload, store and analyze external market benchmarking ranges right alongside their company's own pay data for a more precise pay benchmarking at the individual level, and increased visibility for all your compensation planning and analysis needs.

Efficient incremental uploads for effective-dated data

We've made updating your effective-dated data much faster and easier with our new Incremental upload API. It is now possible to submit only new or changed records, rather than the entire history, drastically cutting down on upload times and boosting efficiency. This is made possible through a powerful new API endpoint, designed to make data ingestion more efficient and flexible.

This new API endpoint: POST /v1/api/data-foundation/ingestion/{dataTypeName}/incremental enables data admins allows to upload only new or modified records for effective-dated entities, such as updated employment data for a worker. This endpoint specifically applies to effective-dated entities within Data Foundation.

The request accepts a JSON array containing only the new or modified records. There are limits: a maximum file size of 10 MB and a maximum of 30,000 records per request.

Upon successful submission, the system will return a "202 Accepted" status, indicating that your request has been queued for processing. No validation or commitment occurs at this stage. If another ingestion request for the same data type is already in progress, a "409 Conflict" response will be returned.

beqomPay Suite 1.10

Situation and Absence Configuration

This release introduces a new feature within the Workbench: Situation and Absence Configuration. This enhancement provides greater flexibility and control over how Time in Role (TiR) and Leave of Absence (LOA) are managed and calculated within your organization.

We've added a new feature within the Workbench called Situation and Absence Configuration to make managing employee time and leave easier. You can find it in the Workbench section under Data Management.

This tool helps you control how things like Time in Role (TiR) and Leave of Absence (LOA) are calculated. Time in Role refers to how long an employee has been in their current position. It’s a crucial metric used to evaluate eligibility for career advancements, role changes, or additional responsibilities. Now you can set rules for when job situations change, like when someone changes jobs. This helps you get correct Time in Role calculations.

You can also manage Leave of Absence which allows employees to take extended leave beyond regular paid time off. Proper handling of LOAs is critical for compensation like maternity or medical leave. You can set how long these leaves last and make sure they're used in pay calculations. This makes pay more accurate and helps with complex employee situations. You'll have one place to set all these rules, giving you more control and making things easier to understand.

The following figure illustrates the placement of the new setting option:

Situation and Absence Configuration page

Schema Changes

We've made changes to the "Worker" part of the system to make adding employee data easier. The "PreferredLanguage" and "Timezone" fields are now optional. You don't have to fill them in when adding an employee. If you leave them blank, the system will use the company's default settings.

This change makes it easier to upload employee data, especially if you don't have all the information right away. It also makes the system more reliable when dealing with incomplete data.

beqomPay Suite 1.9

Organization Entity Update

New field added to the Organization entity: OrganizationType [Enum, Optional]

New enums

OrganizationType: defines categorization of organizations.

This update offers greater flexibility in defining and managing organization structures within the platform.

beqomPay Suite 1.8

Enhancements to population criteria definition

Version 1.8 introduces exciting changes in the population builder which will make it easier and more efficient to build population criteria, specifically:

IN and NOT IN operators are now supported, making it possible for users to assign multiple values to a given field.
Drop-down lists are now available for value selection in enums, with multiple selection supported for IN and NOT IN operators.

The following figure illustrates a drop-down list with multiple selection:

Multiple selection in an enum field

Defining populations is now faster and more intuitive with simplified criteria definition and operator support, ensuring a smoother selection process. The improved user experience streamlines configuration, increasing efficiency and making population management clearer and more user-friendly.

Data foundation schema updates

Worker entity update:
- New field: WorkRegion (string, optional)
New goal-related entities:
- GoalPlan: represents structured goal-setting plans.
- GoalPlanTypeAssignment: defines associations between goal plans and their respective types.
- GoalAchievement: captures goal completion and performance metrics.
IndividualPayRange entity update
- New field: LocalGrade (enum, optional)
- New field: GlobalGrade (enum, optional)
New enums:
- IndividualPayRangeGlobalGrade: defines standardized global grading for pay ranges.
- IndividualPayRangeLocalGrade: defines localized grading structures for pay ranges.
- GoalType: categorizes different goal types for structured goal management.

beqomPay Suite 1.7

Custom fields in standard entites

With custom fields, customers can now to extend standard entities within their accounts to better align with their unique business requirements. It is notably possible to select the standard entity to which a custom field will be added, tailoring data structures to the custiomer's specific needs.

Custom fields can be defined with several attributes. Users can assign a clear and descriptive name for easy identification and add a description to provide context about the field’s purpose or usage. Supported data types include:

Name: assign a clear, descriptive name for easy identification.
Description: provide context about the field’s purpose or usage.
Data Type: select from supported types, including String, Number, Integer, Date, and Boolean.
PII Marking: designate fields containing Personally Identifiable Information (PII) to comply with data protection regulations. These fields will be included in anonymization processes during data retention events.
Required Fields: specify mandatory fields to maintain data integrity.
Default Value: set optional default values to streamline data entry and reduce manual effort.

This feature enhances the flexibility and configurability of the platform, empowering customers to capture, manage, and utilize data more effectively while meeting compliance needs.

Population builder

The population builder is a powerful feature that enables customers to create and manage tailored populations to meet their specific business needs.

Custom populations can be created with unique names and descriptions, ensuring easy identification and organization. Populations are defined using multiple criteria, allowing precise filtering of data. Each criterion is built by selecting a field from an entity, choosing an operator (such as Equal To, Not Equal To, or Contains), and providing a value. For example, a population could be defined by selecting the Worker Entity, the WorkCountry field, the Equal To operator, and the value "Ireland".

The population builder also supports complex logic, allowing users to group multiple criteria blocks together. This makes it possible to build sophisticated, multi-layered populations with flexibility and granularity.

This feature streamlines the creation of tailored groups, helping customers align their data management with their specific business requirements.

beqomPay Suite 1.6

GoalsAchievement Entity

In the 1.6 release, a new entity was added to the standard entities in beqom. The GoalsAchievement entity is designed to track goal achievement data for workers.

With this entity, the tracking of individual and team achievements will be much improved. It also enhances the alignment of goals with compensation and bonus calculations, while giving more flexibility to goal plan mapping for diverse use cases.

beqomPay Suite 1.5

Data Ingestion via API

We are excited to announce the release of our new Data Ingestion API, designed to streamline the data import process for beqom customers. This powerful API enables customers to securely ingest essential data, directly integrating with their Pay Suite platform.

Key features of this new solution are:

Data upload via API - customers can now upload data to beqom directly through API requests, simplifying data management and reducing reliance on manual uploads.
Real-time status tracking - the ingestion process has two steps. Upon submitting an ingestion request, customers receive an Ingestion ID to track status and progress through a dedicated endpoint. This enables transparency, with real-time updates on data ingestion status.
Comprehensive error handling and validation - the Data Ingestion API performs full validation over all submitted data.
Enhanced security - the API is secured via bearer tokens, which expire hourly, ensuring a secure and time-bound access.

For further guidance on using the Data Ingestion API, please refer to our API documentation or contact our support team.

Data Retention for CPM

We have introduced a flexible Data Retention feature for CPM customers, allowing users with compensation admin professional role to configure customized retention settings to meet their organization’s data management needs. This enhancement supports compliance and data management practices tailored to diverse regulatory environments. This feature is located under Workbench > Data Management section and it enables:

Default retention period - users with compensation admin professional role can set a default retention period, specified in years and months, for storing Personally Identifiable Information (PII).
Country-based exceptions: users with compensation admin professional role can configure exceptions to the default retention period based on specific country requirements, allowing flexibility across different data jurisdictions.

Create Data Models

In 1.5 release we introduce the Data Modeler, a powerful new tool in the Data Management section of the Workbench. This feature enables user with compensation admins professional role to create custom data models tailored for processes such as compensation rounds. The Data Modeler empowers users to streamline and customize data structures to meet their unique process needs. The key capabilities of this feature include:

Model customization - admins can assign a name and description to each data model and select the specific data fields to include
Future flexibility - the Data Modeler will continue to evolve over the coming months, adding greater flexibility and configurability.

Partial Data Upload

We have upgraded our data ingestion process to support both full and partial data loading, offering greater flexibility and efficiency in data management. Customers can now choose to upload only a subset of data, focusing on updates or specific data changes without having to upload the entire dataset each time. This is particularly useful for ongoing data maintenance, allowing faster processing times and minimizing potential disruptions.

With this enhancement, customers gain more control over their data ingestion strategy, reducing upload times and optimizing data accuracy by targeting only the necessary updates.