beqom PaySuite 26.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 26.1 release of the beqom PaySuite application and in the subsequent patches.
This is an attention message.
The text in this article is AI-generated. A final version will provided shortly.
26.1
Deployment to staging environments: July 14th, 2026
Deployment to production environments: July 21st, 2026
| Type | Issue key | Module | Description | Feature Flag* | |
|---|---|---|---|---|---|
| Zendesk | Jira | ||||
| AC-25073 | Data Foundation | Under Platform > Data Management Settings, users with the Support role can now enable or disable Data Viewer Export at the tenant level. This lets customers control whether data export is available in their environment, limiting exposure of sensitive data for tenants that do not need the feature. | Yes | ||
| AC-25082 | Data Foundation | In the Data Viewer, users with the DataFoundationAdmin, Configuration, or Support role can now export PaySuite data as a CSV file. This allows customers to validate and reconcile ingested data against what is currently stored in the system. | Yes | ||
| AC-25085 | Data Foundation | Data Viewer export now offers a revision (historical) mode in addition to the current-data snapshot, letting authorized users export all updates to worker records over a selected date range. This supports audit trails and validation of how data changed across ingestions. | Yes | ||
| AC-25094 | Data Foundation | Data Viewer export actions are now recorded in the platform's backend audit system, including details such as the user, tenant, export mode, entities exported, filters applied, and row count. This gives security and compliance officers full traceability over who exported data, when, and what was included. | Yes | ||
| AC-25095 | Data Foundation | Users are now notified in-app and by email when a Data Viewer export completes, with a link to download the file so the export is not lost if the browser is closed while processing. The download link expires after a preconfigured period. | Yes | ||
| AC-25100 | Data Foundation | In Data Viewer settings, authorized users can now enable a tenant-level Encryption option that password-protects exported files, reusing the password-protected export capability already available elsewhere on the platform (such as in TCM). The setting is disabled by default and helps exported data meet company security and compliance requirements. | Yes | ||
| 151951 | AC-25835 | Data Foundation | Under Custom Labeling, users with the Configuration or Support role can now reset custom labels in one or more languages back to their standard values in bulk, instead of exporting, editing, and re-uploading a CSV file. The action requires confirmation to prevent accidental resets and does not delete data, preserving the existing audit trail and version history. | – | |
| AC-26105 | Data Foundation | Under Custom Labeling, users with the Configuration or Support role can now view the version history of Custom Labels for each language, including when changes were made and by whom. This covers actions such as uploading custom label files or resetting labels to standard values, giving administrators visibility into non-destructive changes over time. | – | ||
| AC-26108 | Data Foundation | Under Custom Labeling, users with the Configuration or Support role can now restore a previous version of Custom Labels for a language directly from the version history, avoiding the need to manually correct and re-upload label files after a mistake. A confirmation step is required before a previous version is restored. | – | ||
| AC-26150 | Pay Transparency | In Workbench, under Pay Information Request settings, administrators can now configure how generated document file names are built—either using a single fixed name or a customizable name assembled from variables such as worker details, request ID, dates, and worker category. By default, file names follow the format WorkerFullName_RequestId. Existing tenants without custom settings continue to receive the previous default naming behavior. | – | ||
| AC-26634 | Compensation Management | Statement Generation now enriches the underlying data with Minimum (Threshold), Target, and Maximum payout curve results, along with goal descriptions, for each goal. This allows Compensation Admins to include Threshold/Target/Cap columns and goal descriptions in bonus statement templates (DOCX), with bonus amounts shown in both local and converted currency. | – | ||
| AC-27875 | Compensation Management | In Workbench, under Compensation builder > Compensation rounds > Guidelines, Global Compensation Admins and Compensation Admins can now define Minimum and Maximum guideline rules using a formula-based editor with an expanded calculation workspace, replacing the legacy criteria configuration. Each Minimum and Maximum rule can independently be set as Soft or Hard, and existing guidelines are automatically migrated to the new format. | – | ||
| AC-27887 | Compensation Management | In Workbench, wherever the advanced formula editor is available in the Compensation module (eligibility, budget, calculated columns, and on-change calculations), Global Compensation Admins and Compensation Admins can now reference customer-defined Custom Entities using a new LOOKUP function. Custom Entities defined under Data Management are automatically available for use in round calculations, with results evaluated when Team Planner calculations run. | – | ||
| AC-28081 | Compensation Management | Under Workbench > Round Management Portal and Team Planner View, Data Foundation Admins can now extend the Data Model with calculated fields that are automatically added to affected Draft rounds' Team Planner View, with visibility disabled by default. Global Compensation Admins and Compensation Admins receive a "Last updates" notification alerting them to apply the new fields via the pending draft version. | – | ||
| AC-28084 | Compensation Management | In Round Portal > Statement Generation, Data Model calculated fields are now included in the statement generation JSON under ModelData, using the computed values stored in the round snapshot. Global Compensation Admins and Compensation Admins can view these fields in generated statements and in the "Copy JSON" sample, which reflects each field's Column Configuration visibility setting. | – | ||
| 153348 | AC-28324 | Data Foundation | In Analytics > No Goal Details, the Managers with no goals, Users with no goals, and Workers with no goals widgets displayed no data. The underlying goal report was corrected so administrators now see the expected data in each widget. | – | |
| AC-28836 | Pay Transparency | In the Pay Analysis view, available in both Model Factory and Planner, the Total Cost of Raises insights for Model, Recommended, and Final now display the percentage change between total salaries and total salaries after raises, matching the existing behavior already available in Pay Analytics. | – | ||
| AC-29203 | Data Foundation | Under Data Foundation > Workers, Data Foundation Admin, Configuration, and Support roles can now export PaySuite worker data shown on the Workers screen as a CSV file, to validate and reconcile ingested data against the current system state. | Yes | ||
| AC-29237 | Compensation Management | In Planner, Increase Amount and Increase % are now automatically derived from New Value and saved whenever a compensation round is published or re-published, for every Salary compensation element with Proposal Management enabled. This matches the calculation already applied during in-session edits, and any previously stored Increase Amount/% values are recalculated and overwritten accordingly. | – | ||
| AC-29352 | Compensation Management | Statement Generation now includes per-goal bonus payout amounts and per-situation bonus amounts that were already calculated in the Planner, enabling Compensation Admins to reference these figures directly in statement templates without recalculating them. | – | ||
154315 154426 | AC-29356 | Pay Transparency | PayAnalytics dataset creation could fail with a duplicate employee ID error when a worker had more than one situation record in a snapshot. Dataset uploads now use only the latest situation per worker, and the same fix was applied to Article 7 aggregation and to document generation for Statement Generator and Pay Information Requests, preventing these duplicate-ID failures. | – | |
| AC-29474 | Authorization | In Authorization > Professional Roles, CSV template downloads and uploads now include a UTF-8 byte order mark (BOM) and use the CSV separator configured at the tenant level. This ensures that files containing accented characters, such as French text, display correctly when opened in Excel. | – | ||
| AC-29861 | Compensation Management | In Statement Generation, generated statements now include the payout curve name for each goal through a new PayoutCurveName field, and all date fields are output without the time component. Compensation Admins can reference PayoutCurveName inside DOCX templates alongside the simplified date formatting. | – | ||
| AC-29931 | Pay Transparency | In Planner > Pay Information, the bulk action filters for Close & Release and Generate Documents previously displayed options that did not apply, including a 'New' status, 'Closed without documents' and 'Not released to worker' alerts, and an 'Empty' attached-documents filter for Close & Release. These irrelevant options were removed so only applicable filters are shown. | – | ||
| AC-29933 | Pay Transparency | In Planner > Pay Information, the empty states shown for the Generate Documents and Close & Release bulk actions were updated, including the state displayed when a filter search returns no results, to provide clearer messaging. | – | ||
| AC-29936 | Pay Transparency | In Planner > Pay Information bulk actions, the Refresh button did not update the status insight counts shown in the tiles after generating or closing pay information requests. The Refresh button now correctly updates these counts. | – | ||
| AC-30012 | Authorization | Synchronization logging was improved so that duplicate key and uniqueness conflicts during data ingestion clearly identify the conflicting record and field, rather than surfacing generic database errors. These detailed conflict messages, including the incoming and existing record identifiers and the conflicting field and value, are now visible in the synchronization logs UI, helping integration teams diagnose failures without direct database access. | Yes | ||
| AC-30083 | Pay Transparency | Under Planner > Pay Information > Bulk Actions, users now have a "Show my executions only" toggle to filter the execution list to their own submissions, enabled by default. Existing filters continue to work, and applying an "Executed by" filter automatically turns the toggle off. | – | ||
| AC-30089 | Pay Transparency | Admins with the Configuration role can now set a yearly limit on the number of pay information requests a worker may submit, with a global default and optional country-specific overrides. This limit applies only to worker-submitted requests; HRBP-submitted requests are not restricted. | – | ||
| AC-30163 | Pay Transparency | The left panel menu in Workbench > Communication (Pay Transparency Workbench) was reorganized into a more logical structure, grouping Documents, Communication Rounds, Pay Information, and Monitoring settings for easier navigation. | – | ||
| AC-30290 | Pay Transparency | In Planner > Documents, the active tab, selected communication round, filter selections, search term, and pagination now persist in the URL instead of being lost on navigation. This allows filtered views to be shared as direct links and restored when returning to the page or using the browser's Back button. | – | ||
| AC-30319 | Data Foundation | In Data Modeler, deactivating a calculated field still used by a published model displayed a raw technical conflict message instead of a clear explanation. The system now shows a clear message informing the user that the field cannot be deactivated because it is in use by a data model. | – | ||
| AC-30405 | Pay Transparency | In Planner > Pay Information > Bulk Actions (Generate Documents and Close & Release), the "Alert: Document deleted" filter previously failed silently and returned all requests instead of only those with a deleted document. The filter now correctly returns only requests flagged with a deleted document alert. | – | ||
| AC-30447 | Pay Transparency | HRBPs who receive the daily 'Incoming requests' reminder notification previously received the same reminder repeatedly, showing an unchanged count, even when no new pay information requests had been created since the last notification. The reminder is now only sent when new requests have been created since the previous notification, reducing duplicate alerts. | – | ||
| AC-30455 | Pay Transparency | In Pay Information > Bulk Actions, the Refresh, Generate Documents, and Close and Release buttons were previously hidden when an applied filter returned no results. These buttons now remain visible in the empty state, so HR administrators can refresh the list or create a new bulk action even when no rows match the current filter. | – | ||
| AC-30480 | Pay Transparency | Clicking an HRBP reminder notification (Incoming requests, Approaching deadline, or Overdue) in the notifications bell or the full notifications page previously did not navigate anywhere. Clicking these notifications now redirects HRBPs to the Pay Information requests page. | – | ||
| AC-30557 | Data Foundation | Uploading an empty or header-only CSV file for data ingestion previously triggered a generic, technical error message. Empty uploads now return a clear validation message indicating there was no data to ingest, while non-empty and other malformed uploads continue to be handled as before. | – | ||
| 155243 | AC-30578 | Performance Management | Feedback email notifications in English and Turkish displayed technical placeholder text instead of the predefined message configured in the platform's notification settings. This was a regression from the previous setup; notifications now correctly display the configured content. | – | |
| AC-30597 | Pay Transparency | In Documents, pay-information reminder emails (Incoming, Approaching Deadline, and Overdue) were previously enabled by default. Reminders are now disabled by default for new and unconfigured tenants, while any tenant's existing configuration is preserved. When an HRBP enables a reminder, it is now created with default settings (daily frequency, delivered at 9:00 AM). | – | ||
| 155570 | AC-30719 | Data Foundation | In Analytics Reports, widgets under Pay Transparency - EUPTD reports failed to load with a "fetching visual" error when no local rule was configured in Workbench > Pay Transparency > Alerts and Anonymization. The report model now refreshes correctly even when no local rule is present, resolving the display issue. | – | |
| 155251 | AC-30764 | Authorization | A cookie length error affecting the production environment was reported and investigated. Further details on the cause and resolution were not fully documented in this ticket. | – | |
| AC-30932 | Compensation Management | In Compensation Planner, values updated by Real-Time Calculation (RTC) rules were not flagged as overridden when written to fields with proposal management (input defaults) enabled. As a result, republishing a round with "keep entries" incorrectly reset these values to their default, and the "Restore to default value" tooltip did not appear. RTC-calculated values are now treated the same as manual entries, and this fix now also extends to bonus and custom column fields. | – | ||
| AC-30964 | Data Foundation | In Data Viewer, DataFoundationAdmin, Configuration, and Support roles can now export entity data to a CSV file, letting them validate and reconcile ingested data against the current system state without pulling historical revisions. Users without one of these roles have no access to this export capability. | Yes | ||
| 155849 | AC-30967 | Data Foundation | Creating situation snapshots for data models with a small number of fields could fail after about 20 seconds with an out-of-memory error, blocking snapshot creation entirely. Snapshot creation now completes successfully even with multiple effective-dated records and dozens of compensation elements. | – | |
| 155978 | AC-31083 | Data Foundation | In certain circumstances, the live snapshot could incorrectly create two records for the same worker when an effective-dated entity, such as Employment, had a change effective on the current day. Because user service synchronization relies on the live snapshot as its data source, this could cause duplicate worker data to propagate downstream. The live snapshot now generates a single record per worker in this scenario. | – | |
| AC-31149 | Data Foundation | In the Goals Direct Lake report, the No Goals Detail page displayed all widget titles as blank, such as "Total users with no goals" and "Managers with no goals", making the KPIs hard to interpret. The missing measures were added to the shared semantic model, so titles now render correctly in the user's language, matching the legacy Goals report. Other pages and reports were unaffected. | – | ||
156130 156191 | AC-31225 | Compensation Management | Creating a pending draft for a compensation round could fail with a server error when the round included goal payout curve assignments, because the process used to copy the round's data was copying far more information than needed and consuming excessive memory. This has been corrected so that only the required data is copied, allowing pending drafts to be created successfully. | – | |
| AC-31329 | Data Foundation | In Analytics Hub, the No Goals Details report failed to display data for managers, users, and workers who had no goals assigned. This has been corrected so that all widgets in the report now display the expected data. | – | ||
| AC-31414 | Compensation Management | Publishing a Bonus Plan or Compensation Round with a very large number of goals (around 10,000) and extensive data configuration could fail due to timeouts or memory errors, since the round was being duplicated in memory during processing. This has been corrected so that large bonus plans and compensation rounds can be saved, drafted, and published successfully. | – | ||
| 149014 | AC-31415 | Data Foundation | A scheduled data pipeline job that updates Performance Reviews data failed during execution, preventing performance review data from refreshing as expected. This has been corrected so that the pipeline completes successfully and performance review data updates reliably. | – | |