beqom PaySuite - Pay Transparency feature release notes

beqom PaySuite 28.2

New worker work country field in Pay Information Request API responses

Retrieving a pay information request through the Integration Hub API has not indicated which country a worker is based in. As a consequence, integrations have lacked a direct means of applying the country-specific handling that Pay Transparency work often depends on.

With this release, both the single and the bulk Pay Information Request endpoints return a worker's work country as a code and as a full country name, read from the worker's current record rather than a fixed value captured at the time of the request. This also brings the single-request endpoint's alert handling in line with the bulk endpoint, so overdue and approaching-deadline alerts now follow the same country-specific rules wherever a pay information request is retrieved.

Enhanced document export API with communication round listings

Before a communication round's documents can be exported through the API, the round itself must be identified by its code. So far, obtaining that code has required turning to the web app or the database, since the Integration Hub offered document lookup and download but no way to find the round itself.

Integration users can now retrieve the list of published communication rounds, including their codes, directly from the Integration Hub, covering rounds that are in progress, open, or closed; draft rounds are excluded regardless of whether a status filter is applied. Access to the new endpoint is protected by the same documents permission scope as the other document endpoints.

With this addition, the full document-export flow can run through the API from end to end: listing the published rounds, looking up a round's document details, and then downloading the documents themselves.

Refreshed email notification settings

Previously, the Documents and Pay information request sections on the Email Notifications page under Workbench > Platform Setup used toggle switches for each notification type.

We have replaced these toggle switches with checkboxes, so that Documents and Pay information request match the rest of the notification configuration screens. We have also added a new Cancel option in the upper-right corner of the page to let administrators discard unsaved changes in a single action. A sticky header keeps the Cancel and Save buttons visible while scrolling through a long list, and both now stay reachable by keyboard whether or not there are changes to save.

The underlying notification behavior itself remains unchanged. Only the page's layout and controls have been updated.

Notification checkboxes for pay information requests

CSV export for the Pay Information Audit trail

Until now, changes made to a pay information request were visible only in Planner > Pay Information > Audit trail, with no option to save it for offline use.

In version 28.2 of the application, we have enabled HRBPs to export the audit trail as a CSV file, covering up to the 30,000 most recent matching entries. The new capability is available via an Export button above the Request activity section. The export reflects filters applied on the page, as well as the HRBP's own worker access, so two HRBPs with different assignments receive different files.

Each changed row's before and after values are captured together in a single details field. The exported file itself is password-protected to keep its contents secure once outside the application.

This gives HRBPs a complete, portable record of a pay information request's history, supporting audits and compliance reviews without depending on the on-screen table alone.

Export button on the Audit trail page

Redesigned Documents page

In previous versions of PaySuite, viewing communication rounds and their documents in Planner > Documents was split across two separate tabs, Communication manager review and HRBP review.

These tabs are now consolidated into one page, listing every accessible communication round along in a single view. The page specifies the roles with which a user can access each round. It also provides a clearer view of the round's visibility start and end dates, making it easier to confirm access and timing without opening each round individually. Tiles at the top of the page give a quick overview of how many communication rounds are currently accessible and how many of those are Open or In progress.

The page keeps the familiar search, filtering, advanced filtering for HRBPs, and bulk actions for downloading, releasing, and unreleasing documents. We have additionally included insights covering the documents in scope, read status, release status, and workflow step, based on the user's own access and selected role. This way, communication managers and HRBPs have a fuller picture of where a round stands without leaving the page to check each detail separately.

A new View as selector lets anyone with more than one applicable role choose which role's view to see, defaulting to Communication manager. When only one role applies, the selector shows a fixed label. Role handling has also been simplified: a role is now selected explicitly from within the communication round itself, reducing the number of clicks needed to switch between viewing roles.

Consolidated list of accessible communication rounds

View as selector for switching between roles

beqom PaySuite 28.1

Default multi-level sorting for the communication round record list

Under Planner > Documents, communication round records with no document attached have so far had no defined sort order, and appeared in whatever sequence they were created, which could vary between one viewing and the next.

With this release, the record list applies a default order based on three criteria: first Status, then Generation date, and finally Document recipient, so records appear in a consistent and meaningful sequence even before a document exists. Every column can be sorted manually by clicking its header. The default ordering shows no sort arrows on any column, since it reflects more than one criterion at once; an arrow becomes available only after a column has been selected for sorting.

This capability gives HRBPs and Communication Managers a consistent starting order instead of a list that reshuffles unpredictably each time it loads. At the same time, it preserves the flexibility to sort by any column when a different view is needed.

Communication round records with a new default sort order

beqom PaySuite 28.0

Configurable Worker information widget in the digital reward statement

So far, the Worker information widget in the digital reward statement has shown a fixed set of details in a specific layout, leaving little room to match it to how an organization presents worker data.

In version 28.0 of the application, we have enabled administrators to control the widget at three levels: the widget as a whole, each of its sections, Details, General information, and Role information, and individual fields within them, from Work country and Worker ID to Job title, Job level, and Cost center name. Configuration is available underWorkbench > Platform Setup > Passport > Compensation > Digital reward statement.

The order of fields can be set by dragging them into place. In addition, section labels can be renamed and localized for each active platform language so that a statement uses an organization's internal terminology. Admins cannot save their changes unless every enabled section keeps at least one enabled field. To avoid manual rework, a Reset to default button restores the original visibility, labels, and order in a single step. Importantly, by default, all Worker information sections and fields are enabled.

With this enhancement, organizations can decide which worker attributes appear in a statement, supporting data governance and local requirements. Wording and structure can also be adjusted to match how workforce populations are addressed.

Field-level visibility settings for the Worker information widget

Demo

HRBP review notifications, with combined notifications for bulk operations

Once a document reached the HRBP review workflow step, an HR Business Partner had no automatic signal that it needed attention.

A Document ready for HRBP review notification is now sent automatically when a document enters that step, whether through an individual update, an import into a workflow-enabled communication round, a bulk update, or automated processing. Administrators can configure it via Workbench > Platform Setup > Email Notifications > Documents. The new notification is delivered both in-app and by email, and addressed only to the HRBPs assigned to the affected workers. Its email content can include the document name, the worker name, and the communication round through configurable variables. Opening a notification leads directly to Planner > Documents > Communication rounds > HRBP review, filtered to the relevant document and worker wherever that information applies. When many documents proceed to HRBP review at once, for example after a large import or a bulk workflow update, a Multiple documents ready for HRBP review setting groups those transitions into a single notification.

As a result, HRBPs are alerted the moment a document is ready, with combined notifications preventing a flood of separate alerts during batch operations.

In-app notifications for documents ready for HRBP review

Notification settings reorganized in Workbench

Notification settings inside Workbench have grown alongside Pay Transparency, without a clear structure separating one kind of notification from another.

We have grouped these settings into two sections, Documents and Pay information request, under Workbench > Platform Setup > Email Notifications. A notification related to document workflows is no longer mixed in with one governing pay information request processing.

This makes the right setting easier to find as Pay Transparency continues to add notification types, without changing how any individual notification is itself configured.

Documents and Pay information request notification settings

Enhanced route protection for Pay Transparency configuration pages

Pay Transparency configuration pages now apply stronger, feature-based access controls. A page tied to a capability that is disabled for an organization is removed from Workbench navigation and blocked from direct access by its URL, across configuration areas including document settings, document templates, pay information requests, and related pages.

This way, the configuration options remain aligned with the Pay Transparency capabilities actually enabled for each organization.

beqom PaySuite 27.3

Global audit trail for pay information requests

In previous versions of PaySuite, an audit trail for a pay information request existed only at the level of a single request, so reviewing activity across many requests required opening each one in turn.

To consolidate that activity into a single, searchable view, we have introduced an Audit trail tab, alongside the existing Requests and Bulk actions tabs in Planner > Pay Information. Entries can be filtered by the person who performed the action, the worker involved, the action type, a request ID, or a date range, and then sorted, with results paginated at 25 entries per page by default. Clicking a request ID opens the request itself, and a dedicated detail drawer for update actions provides greater visibility into what was changed. The view applies the same permissions already used elsewhere in Pay Transparency, so a user continues to see only the workers within their scope.

Investigations that once meant checking requests individually can now be carried out from a single screen, with no change to access controls.

New Audit trail tab in Pay Information

Demo

New notification types

Notifications for Communication Managers at document review

Previously, Communication Managers could learn that a document had reached the Document review workflow step in a communication round only by checking the round directly.

A new notification, Document ready for communication manager review, set in Platform Setup > Email Notifications > Documents, is triggered the moment a document reaches that step in an eligible communication round. It is delivered both in-app and by email. It reaches both the primary and the secondary Communication Manager assigned to the round. Clicking the notification opens Planner > Documents > Communication rounds with the relevant filters already applied, so the documents requiring attention appear immediately.

This reduces the manual coordination previously needed between contributors and Communication Managers. As a result, documents move through review without unnecessary delay.

Document ready for communication manager review toggle

Notifications for failed automated executions

Until now, a failed automated document generation or close and release action went unnoticed unless someone was actively reviewing the Automated Action Monitoring page or its execution logs.

With this release, a new notification type, Automated action failures, is available under Platform Setup > Email Notifications > Documents. Administrators choose who receives it, independent of that person's own Pay Transparency role, and set a delivery schedule of daily, weekly, or monthly, with the delivery time defined in UTC. Both the subject and body of a notification can be edited and translated. Notifications separate document generation failures from close and release failures and state how many of each occurred, so recipients can immediately see where attention is needed. Additionally, each notification links directly to the Workbench > Pay Transparency > Automated Action Monitoring page with the matching error filters already applied, skipping the need to rebuild that filtering by hand.

Rather than being tied to a specific role, monitoring responsibility can now be assigned to whichever person or team an organization designates, and failures are surfaced on a schedule instead of depending on someone remembering to check.

Automated action failure notification configured

Demo

beqom PaySuite 27.2

Response Automation for pay information requests

Processing pay information requests has moved from something handled one at a time to something done through bulk actions, like generating documents and closing and releasing several requests together. Even with bulk actions, an HRBP still had to decide when to run them.

Our new page, Response Automation, adds a further step. Under Workbench > Pay Transparency > Pay Information > Response Automation, administrators can configure automatic document generation and automatic close and release independently of each other: an organization might automate document generation while still closing and releasing requests through an HRBP decision, or enable both together for a fully automated flow. The capability remains inactive until an organization chooses to configure it, since response automation is disabled by default.

Automatic document generation can be scoped to how a request originates, for example, one submitted by a worker, imported through an API, or created directly by an HRBP, and administrators decide whether a newly generated document should replace one that already exists or leave it in place. Generation can begin immediately or after a set number of days following the request date, giving a short window for manual intervention before automated processing begins. A mapping configuration must already be in place for a worker, tying together the pay data snapshot, the document template, and the communication round the response should go to. Without mapping, automated generation cannot complete.

Automatic close and release follows once a document becomes available, whether generated automatically or attached another way; closing a request without a document remains a deliberate manual action outside automation's scope. Response automation also respects each communication round's workflow: where no review is required, an eligible request can be generated, closed, and released without any HRBP involvement, while a round with a required workflow still automates generation and closing but holds the document at pending release until an HRBP completes the review and releases it. Country-specific rules, based on a worker's work country, take precedence over the global configuration. Therefore, an organization can run automation everywhere while disabling automatic generation or automatic close and release for workers in a specific country, adopting automation gradually as local policies or requirements allow.

Failed automated actions are retried once per day, either without limit or up to a configured number of attempts, giving time to correct an underlying problem before the next attempt runs. A dedicated Automated Action Monitoring page shows the outcome of each run, with exportable logs for troubleshooting. To increase transparency, every automated action is marked as such in the request's audit trail in Planner > Pay Information, so it stays distinguishable from anything done manually.

Response Automation configuration page

Automated Action Monitoring

Demo

Simplified Workbench navigation

As Pay Transparency has grown, its Workbench navigation grew alongside it, reaching four separate sections that made related settings harder to locate.

We have reorganized the left-hand navigation into two sections, Documents and Pay Information, with monitoring for compensation round document generation moved under Documents as Comp Round Documents, alongside the other document-related settings. Several menu items have shorter names: Document Settings is now Settings, Document Templates – Templates, and Mapping Configuration – Mapping. We have added two new pages: Response Automation and Automated Action Monitoring. The order of items within each section has also been adjusted, so related settings sit closer together.

The result is the Workbench that is quicker to navigate day to day and scales better as Pay Transparency expands.

Workbench's Documents and Pay Information menu

Demo

Explicit access control for Communication Managers

Previously, controlling whether Communication Managers could see a particular communication round depended on how its hierarchy was set up. Organizations that wanted to block that access altogether had to work around it, configuring a hierarchy with no worker-manager mappings rather than switching access off directly.

Currently, the configuration step once called Hierarchy is Communication manager access under Workbench > Pay Transparency > Communication Rounds. It includes a Grant access to communication manager checkbox. Disabling it hides the hierarchy configuration and removes it as a requirement for publishing the round; Communication Managers can then no longer open the round from Planner > Documents. Enabling it restores hierarchy-based access exactly as before. Administrators can grant or remove that access directly, without maintaining a placeholder hierarchy to keep Communication Managers out. The setting governs Communication Manager access specifically and has no effect on HRBP access to the round.

Existing communication rounds that already have a hierarchy configured keep Communication Manager access by default, so nothing changes for them. Newly created rounds start with access disabled, to be enabled deliberately when appropriate.

Communication manager access step, with hierarchy enabled

Demo

Worker ID shown and searchable in communication rounds

In Planner > Documents, distinguishing between workers who share a similar or identical name, or locating one by an external identifier rather than a name, meant switching to the advanced recipient filters.

With this release, communication round document tables display each worker's ID directly beneath their name, and the search field accepts either the worker's name or this ID. Both changes apply across the relevant Communication manager review and HRBP review tabs, so searching by ID no longer requires leaving the main table, and the right worker is easier to confirm even when names repeat or look alike.

Worker ID shown beneath the recipient's name

Demo

Pay Information enhancements

Request date without a timestamp

In Planner > Pay Information, Request date represents a calendar date. However, until now, the interface displayed it with a time component that was always midnight, which could read as more precise than it actually was.

In version 27.2 of the application, Request date appears as a date only, both in the Pay information requests list and on an individual request's details page. Fields that genuinely carry a date and time remain unchanged.

Request date column shown as a date only

Sorting extended across bulk-action screens

In Planner > Pay Information, sorting was only available for a limited set of columns.

Every supported column in the Bulk actions tab can now be sorted, along with the columns in the Generate documents and Close & release screens, one column at a time. This makes it easier to find a specific execution or check results before acting on a large batch. Sorting follows the meaning of each column: text sorts in the usual way, while status columns follow their defined business sequence rather than a plain alphabetical order.

Bulk actions list sorted by request count, descending order

Smarter reminder notification deep links

Clicking a reminder about pay information requests used to land on the general Planner > Pay Information page, leaving the matching filter to be applied by hand before the referenced requests were visible.

Currently, incoming, approaching-deadline, and overdue reminders open the Pay information requests page with the corresponding filter already applied, so an overdue reminder, for instance, leads straight to the overdue list rather than the full page. The number of requests shown may not exactly match the notification's original count, since a request can change between the moment a notification is generated and the moment it is opened, but the reminder still takes an HRBP directly to the requests that need attention, saving a manual filtering step every time.

Demo

beqom PaySuite 27.1

Editable reference number on HRBP-created pay information requests

Until now, an HRBP who noticed a mistake in a pay information request's reference number could only fix it by recreating the whole request from Planner > Pay Information.

With this release, the reference number can be edited directly, as long as the request is still in the New or In progress status. This lets HRBPs correct manual entry mistakes or align a request with an internal case management system without starting over. This only applies to requests HRBPs create themselves; requests submitted by workers through the digital reward statement or imported via an API stay read-only, and once a request reaches Pending release, Closed, or Closed without document, its reference number becomes read-only as well. Every edit is recorded in the request's Audit trail, including the previous and new values, so full traceability is preserved.

Editing a request's reference number

New toggle to show records without documents in communication rounds

In large communication rounds, documents are often generated in phases, which used to leave the HRBP review list cluttered with records that were not yet ready for validation.

For a cleaner experience, we have introduced a Show records without documents toggle in the HRBP review view, available under Planner > Documents. It is off by default, so records without a generated document stay out of view and HRBPs can focus on what can actually be reviewed. Switching it on brings back the full list, including records still waiting on a document. The toggle only changes what is shown in that view and does not affect the underlying communication round data.

HRBP review with the Show records without documents toggle

beqom PaySuite 27.0

Sortable Pay information requests list

Version 27.0 of PaySuite supports interactive column sorting under Planner > Pay Information > Requests, making it easier to locate, prioritize, and review requests, particularly when working through a large volume of them. HRBPs can sort the list of Pay information requests by clicking any column header to cycle between ascending, descending, and the default order. To keep the ordering clear and predictable, only one column can be sorted at a time.

The Alert column sorts by urgency rather than alphabetically, moving from no alert through Approaching deadline, Overdue, and Document deleted. This way, the most pressing requests can be easily identified. Sorting works alongside all currently applied filters, and changing the sort returns the list to the first page while keeping the selected page size. Left untouched, the list still defaults to showing the newest requests first.

Column sorting on Pay information requests

Automatic exclusion of snapshots missing a worker category

Since Pay Transparency comparisons depend on workers being grouped within the same worker category, a snapshot missing that category could result in incomplete or unreliable comparisons. Snapshots without a defined worker category are now automatically excluded, both when mapping configurations are set up in Workbench > Pay Transparency > Pay Information > Mapping Configuration and when requests are managed under Planner > Pay Information > Requests. Only snapshots capable of producing a valid comparison remain available for selection. This reduces configuration errors before request processing and improves the accuracy and reliability of generated pay information letters.

beqom PaySuite 26.2

New "Not Generated" status in bulk action details

Bulk Action Details previously showed a document as Failed whether generation was attempted and failed, or never attempted at all because required setup was missing. This made it hard to tell a genuine error apart from a configuration gap. A new Not Generated status now appears in Bulk Action Details for documents that were skipped due to missing prerequisites, such as a missing mapping, template, or document configuration, an ineligible worker, or an ambiguous mapping selection. Failed continues to indicate that generation or upload was attempted but ran into an error. Existing items already marked as Failed will keep that status, since the error detail is still available for those. Any status filters or counts on this screen may shift slightly as newly recognized cases move from Failed to Not Generated.

Filter persistence on the pay information request list

Filters applied on the pay information requests list, such as status, search terms, pagination, and sort order, were previously lost whenever a reviewer moved into a request and came back, unless they used the back action. Filters now persist when returning from the Create, View, or Edit pages through Cancel, Close, Save & exit, or Send & close, so the list looks the way it was left instead of resetting. This also holds across multi-step navigation, for example moving from View to Edit and back. Opening a request directly from the sidebar or a deep link still shows the list with no filters pre-applied, so that flow is unchanged.

New "HRBP" option in the Creation type filter

HRBPs (HR business partners) and read-only users could not previously filter pay information requests by whether they were created by an HRBP. The Creation type filter now includes an HRBP option, making it possible to quickly find and manage requests created by HRBPs. The option is available in the Pay Information Requests list under Planner > Pay information > Requests, as well as in the bulk actions view, the Generate documents modal, and the Close & release modal.

RequestDate now date-only, with new RequestTime variable

The RequestDate variable used in generated letters previously included a time stamp even when only the date was needed. RequestDate now displays only the date of the request, and a new RequestTime variable is available for cases where the time is also needed. Both variables follow the date and time format set on the template used, giving more control over what appears in generated letters.

beqom PaySuite 26.1

Annual limits for worker-initiated pay information requests

In version 26.1, Pay Transparency allows administrators to limit the number of pay information requests that workers can submit through the digital reward statement in a single calendar year. The aim is to help organizations comply with the EU Pay Transparency Directive (EUPTD), prevent excessive requests, and reduce unnecessary administrative workload. Limits are managed under Workbench > Pay Transparency > Pay Information > Pay Information Requests. They can be configured globally or overridden at country level to accommodate local legislation or specific business requirements. Once a limit has been reached, the Request pay information action in the Pay information widget within Passport > Compensation is hidden and workers see the count of submitted and remaining requests directly in their digital reward statement. Counters reset automatically on January 1 each year.

The limit applies only to worker-initiated requests. Requests created by HRBPs or imported through APIs are not counted or restricted. Existing requests remain visible after reaching the limit.

Global configuration of the annual request limit per worker

Submitted and remaining request count in the digital reward statement

Demo

Configurable document file naming

With this release, administrators can define custom filename patterns for documents generated for pay information requests, configured in the Generated file name section under Workbench > Pay Transparency > Pay Information > Pay Information Requests. Instead of relying on a fixed naming convention, patterns combine static text with supported variables, including the worker identifier and full name, request identifier, snapshot effective date, file generation date (year, month, and day), and worker category. The configured pattern is applied automatically and consistently across all generated documents, eliminating the need for manual renaming, simplifying file identification, and improving compatibility with internal and external document management systems.

Custom file naming configuration using variables

Demo

Pay Information improvements in the Planner

We have introduced two improvements to Planner > Pay Information for a cleaner, more efficient user experience.

There, the Bulk actions tab includes a new Show my executions only toggle, enabled by default. The toggle filters the execution history to show only bulk actions initiated by the logged-in HRBP, based on the Executed by column. This shortens the time spent searching through bulk actions when multiple HRBPs are engaged. Disabling the toggle reveals the complete history of actions executed by all authorized HRBPs.

Show my executions only toggle for bulk actions

Demo

In addition, reminder notifications sent to HRBPs for incoming, approaching, or overdue pay information requests now contain a direct link to Planner > Pay Information, allowing immediate access to the queue without manual navigation. This also lets HRBPs be more responsive to time-sensitive requests.

Notably, the link opens the Pay Information page without applying filters based on the notification context. Contextual filtering is planned for a future release.

Reminder notification for overdue pay information requests

Demo

Enhanced pay remediation cost insights

We have enhanced pay remediation to increase visibility of salary recommendations throughout the process. Selected pay analyses in both Workbench and Plannerdisplay the percentage of current total compensation represented by salary adjustment amounts alongside the existing monetary figures. As a result, Compensation Administrators and HRBPs can better evaluate the budget impact of remediation activities and make more informed decisions.

In Workbench > Pay Intelligence > Pay Analysis > Pay Analysis Results, the Total cost of raises insight shows percentages for the model prediction, recommended adjustments after administrator review, and finalized adjustments after HRBP review. In Planner > Pay Analysis, HRBPs see percentages for recommended and final raises only, reflecting the scope relevant to their role. All percentages are calculated against the current total compensation of the selected analysis.

Model, Recommended, and Final raise percentages in Workbench

Recommended and Final raise percentages in the Planner

Demo

Reorganized navigation for Pay Transparency in Workbench

We have reorganized the Workbench > Pay Transparency navigation into four functional categories: Documents, Communication Rounds, Document Templates, and Pay Information. Related configuration pages are now grouped within each category. For example, Pay Information brings together Pay Information Requests, Alerts & Anonymization, Mapping Configuration, and Document Generation in one place. Such an arrangement speeds up finding features and makes onboarding easier for new administrators. No existing functionality or configurations have changed.

New navigation in Workbench > Pay Transparency

beqom PaySuite 26.0

Aggregated reminder notifications for HRBPs

We have enabled configurable reminder notifications to provide an aggregated summary of pay information requests that require attention. Unlike instant notifications, which trigger on each individual request submission, reminders summarize pending work across three categories: new requests, requests approaching their deadline, and overdue requests. This helps HRBPs proactively manage their workload and maintain Service Level Agreement (SLA) compliance without manually monitoring the queue.

Notifications are delivered both in-app and by email, and are sent only when at least one request matches the configured criteria. When the queue is clear, the system does not generate any reminders. It determines recipients automatically based on existing role assignments and attribute-based access control, ensuring each HRBP receives notifications only for workers within their area of responsibility. Administrators can configure the reminder frequency independently as daily, weekly, or monthly under Workbench > Platform Setup > Email Notifications > Documents > Reminders. Reminder calculations respect both global SLA settings and any country-specific SLA overrides.

In-app notification for overdue requests

Demo

Improved pay information experience

We have implemented several usability improvements to simplify the daily management of pay information requests in Planner > Pay Information and documents in Planner > Documents:

• Closed requests are now hidden by default, with a toggle to show them when necessary, helping HRBPs focus on active work without visual clutter.

• Sorting is currently available in any field in the pay information request grid, with the Status column sorted by workflow order (New, In progress, Pending release, Closed, Closed without document) rather than alphabetically, offering a more intuitive representation of request progression.

• Planner also remembers previously applied filters between sessions, automatically restoring them when users return to the page, reducing repetitive filtering, and increasing navigation efficiency.

• When HRBPs have multiple documents selected for a bulk action and apply a filter change that would clear their selection, a warning is displayed before proceeding, preventing accidental data loss. Users can choose to continue and clear the selection or cancel the filter change to preserve it.

Show closed requests toggle

Demo

Flexible document template formatting

Document templates in Workbench > Pay Transparency > Document Templates now support configurable formatting settings that control how numeric and date values are rendered during document generation. Each template can define its own thousands separator, decimal separator, decimal precision, and date format, allowing organizations to follow regional conventions within the same tenant without requiring separate system configurations. For example, a template for France can use French formatting while one for Switzerland uses Swiss conventions.

Formatting settings apply only during document generation. The document preview continues to display raw source values to assist administrators during template design and validation.

New configurable section in the Document template details step of document template creation

Demo

Enhanced bulk operations

Two enhancements bring greater transparency and control to bulk operations. In Planner > Documents, the size of each document is now displayed directly in the document list. Before generating a ZIP archive, the system calculates the total size of the selected documents and alerts the user when the combined size exceeds the 1 GB limit. This allows for better selection management, preventing the unnecessary processing of oversized downloads.

Moreover, in Planner > Pay Information, Bulk actions also include downloadable execution logs whenever processing completes with errors, such as non-unique mapping configurations, missing template variables, or lack of permissions for the selected communication round. These logs are available when viewing a specific action in a drawer. With the Export log details button, administrators can export a CSV file containing detailed information for every failed request, making it significantly easier to identify and resolve individual issues.

Document size displayed in the Planner > Documents > Document name column

Bulk action details drawer with an option to export log details

Demo

beqom PaySuite 25.1

Instant notifications for new pay information requests

HRBPs can now receive immediate notifications when a new pay information request is submitted for a worker within their area of responsibility. Notifications are delivered through both in-app and email channels as soon as a request is created or imported via API. They include details such as the request ID, worker name, request creator, and submission date. As a consequence, response times become shorter and requests are less likely to be missed.

Administrators enable and configure the feature under Workbench > Platform Setup > Email Notifications > Documents, where a new Instant notification toggle is available under the New pay information request submitted section.

In-app notification for a new request

Demo

New pay information request workflow statuses

We have added two new workflow statuses for pay information requests, such as those appearing in Planner > Pay Information. The statuses replace the previous alert-based indicators for better visibility into the lifecycle of such requests. Pending release applies when a request is closed with an attached document that cannot yet be released to the worker, either because a release approval workflow is enabled for the selected communication round or the HRBP does not have release permission for it. Closed without document applies when an HRBP closes a request without providing a pay information document.

Statuses update automatically as users act on requests: releasing a document sets the status to Closed; unreleasing one reverts it to Pending release; deleting an attached document returns it to In progress; and closing without a document sets it to Closed without document. This enhancement makes it easier to identify requests requiring action and improves the accuracy of SLA monitoring and reporting.

Pending release and Closed without document statuses for pay information requests

Demo

Dynamic Communication Manager role assignments

With this release, Communication Manager access within communication rounds can be assigned dynamically based on hierarchy configuration. This change removes the previous requirement to populate assignments manually through security import files. Under Workbench > Pay Transparency >Communication Rounds, in the Hierarchy step of the communication round configuration wizard, administrators select a hierarchy to drive round access and scope. The result is simpler administration, a more convenient setup process, and a lower risk of errors in security assignments.

Communication Manager access defined in the communication round configuration wizard

Demo

Role-specific notes in pay gap remediation

In PaySuite 25.1, we have enhanced auditability: users who hold multiple roles in the pay gap remediation process can clearly identify which role was active when a note was created. In Planner > Pay Analysis, the system distinguishes between notes created by an HRBP in the Planner and notes created by a Pay Analytics Administrator in Workbench, ensuring that note visibility rules are correctly applied. The role label, HRBP or PayAnalyticsAdmin, is displayed under the author's name in each note, and users only see comments relevant to their assigned role. Collaboration between the two roles improves thanks to better separation of responsibilities, sensitive comments remain appropriately contained, and each note provides clear context for discussions, reviews, and remediation decisions.

Notes labeled by author role

Demo

Bulk download of communication round documents

From now on, multiple communication round documents can be downloaded as a single ZIP file. This makes the retrieval of large document volumes more efficient, simplifying preparation for audits and compliance activities. To use the feature, HRBPs and managers should go to Planner > Documents, check the relevant boxes next to their chosen documents, click the Bulk actions drop-down above the document table, and select Download. When configuring the download, users provide a file name and password. If duplicate file names exist, the worker identifier is automatically appended for uniqueness. The system then processes document packaging asynchronously, and it sends an in-app notification when the file is ready for download. Each document downloaded as part of a bulk operation remains individually traceable through the Audit trail.

Importantly, the maximum combined size of documents in a single bulk download is 1 GB, and generated files are available for 24 hours after creation.

Downloading documents in bulk in the Planner

Demo

Bulk actions for pay information requests

We have enabled the simultaneous processing of numerous pay information requests through the new Bulk actions workspace. The workspace takes the form of a dedicated tab under Planner > Pay Information, located next to the Requests tab, which remains the primary area for managing individual requests. The Bulk actions tab supports bulk document generation (Generate documents button) and bulk close and release (Close & release button), which saves time and eliminates repetitive manual work. When launching a bulk action, HRBPs are presented with a selection window that shows only the requests eligible for that action: New or In progress requests for document generation, and New or In progress requests with an attached document for close and release. Users can select individual requests or all eligible ones, apply additional filters to refine the selection, and choose whether to regenerate documents for requests with an attachment or skip them. Bulk operations are then processed asynchronously.

In addition, for increased transparency, the Bulk actions tab provides a dashboard with the total number of actions and their statuses: Not started, In progress, Completed, and Completed with errors. It also includes the Actions summary table recording the action type, the user who executed it, the number of requests included, initiation, start, and completion timestamps, the status, and the number of successful and failed requests. When a request is processed through a bulk action, its audit trail entry identifies it as part of a bulk operation, distinguishing it from individually processed requests.

New Bulk actions tab

Request selection window for bulk document generation

beqom PaySuite 24.1

New variables for document generation

With this release, document generation templates support new snapshot-related variables. Organizations can dynamically include the snapshot effective date and other snapshot data, along with the document generation date in DOCX communication templates used for pay information requests.

These variables prove especially valuable for EUPTD Article 7 pay information letters, as they increase traceability by showing when the underlying compensation data was captured and when the document itself was generated. They also help organizations ensure consistency and compliance in worker-facing communications.

Mapping configuration for pay information requests

A new Mapping configuration capability, available within Workbench > Pay Transparency, lets administrators define mappings between populations, document templates, data snapshots, and communication rounds. During pay information request processing, these mappings automatically restrict and guide the options shown to HR users, and the system auto-selects the template, snapshot, and communication round when a worker belongs to a single mapping. The page provides a list view of all mappings, individual mapping configuration, and bulk actions to activate, deactivate, or delete mappings. Multiple mappings can apply to the same worker population.

Instead of manually identifying valid templates, snapshots, or communication rounds for each worker request, HR users see only the relevant configurations. This reduces user errors, incorrect document generation, misaligned snapshot selection, and administrative overhead, and simplifies overall request processing workflows.

Individual mapping configuration for pay information requests

Enhanced email notifications with dynamic CC support

Document email notifications, configured under Workbench > Platform Setup > Email Notifications > Documents, can now automatically CC communication managers. The manager is determined dynamically from the hierarchy defined in the communication round configuration wizard, and when secondary hierarchies are set, managers from both primary and secondary hierarchies can be added in CC.

The new capability improves communication visibility and collaboration during document review and distribution workflows. As a result, relevant managers stay informed throughout the process without requiring manual email management or coordination.

Email notification settings including communication managers in CC

Workflow release and unrelease permissions

We have added new permission controls for release and unrelease actions to the Workflow step of communication round configuration. Administrators can independently configure which roles (HRBPs and communication managers) are allowed to release a document and which are allowed to unrelease one. To do so, they need to check relevant boxes under Workbench > Pay Transparency > Communication Rounds > Workflow > Permissions.

This enables more granular governance and approval controls during document review and distribution workflows, fostering alignment with internal processes and compliance standards.

Release and unrelease permissions in the communication round's workflow

Real-time adjusted pay gap calculations during pay gap remediation

Pay Transparency now supports automatic real-time recalculation of adjusted pay gap metrics during pay gap remediation. As users update recommended raises or final raises within pay analysis remediation workflows, the metrics refresh dynamically, and new insights show the adjusted pay gap after recommended and final raises are applied. The capability is available for administrators in Workbench > Pay Intelligence > Pay analysis results. HRBPs see it in Planner > Pay Analysis.

As a consequence, HR and compensation teams can instantly evaluate how proposed raises influence adjusted pay gaps while remediation decisions are being made. This gives immediate visibility into remediation impact on pay equity, improving transparency, decision-making efficiency, and analysis accuracy.

Adjusted pay gap metrics with real-time recalculation in the Planner

beqom PaySuite 24.0

Audit trail for pay information requests

The new version of the application offers a complete audit trail for pay information requests in Planner > Pay Information. It provides a full chronological history of all actions performed throughout the request lifecycle. Users gain visibility into request creation and submission, status updates, document generation and preview, attachments, communication round assignment, and request closure, with user-level traceability showing who did what and when. The audit history is available retroactively, including events from before release 24.0. The system was already logging these events, and they are now exposed in the UI.

This feature fosters compliance and audit readiness, which is critical for the EU Pay Transparency Directive. It supports HRBP accountability, simplifies issue investigation, and ensures full coverage of how requests are handled from start to finish.

Pay information request audit trail

Demo

Alert and anonymization enhancements

With this release, we have centralized all alert and anonymization settings in a dedicated page accessible via Workbench > Pay Transparency > Alerts & anonymization. There, users can manage warning periods, overdue thresholds, and anonymization rules. The system has automatically migrated the existing configurations and all current setups remain intact.

In addition to global settings for alerts and anonymization, administrators can now define local rules per country. What is important, local rules always override global ones. Configuration options in this regard include warning and overdue periods, anonymization thresholds, and placeholder values. There is also an option to disable rules entirely. If the user does not provide values for warning or overdue periods, no alerts are triggered. If they do not set anonymization thresholds, the system does not anonymize data. In such cases, the rule is interpreted as disabled for the selected country.

As a result, alerts for pay information requests now reflect country-specific rule definitions – requests created on the same date can have different alert statuses depending on the worker's country configuration. Similarly, anonymization rules operate on a per-country basis. When generating an Article 7 letter to respond to a pay information request, the system computes counts and average amounts per worker category, gender, and compensation elements within the source data snapshot. Administrators can enforce a minimum population threshold and define placeholder text to mask averages below the configured threshold. If the population headcount falls below the threshold, values are anonymized and placeholder text is applied dynamically.

Overall, the new Alerts & anonymization page improves usability of the application and gives administrators full control over country-specific behavior. It also facilitates adherence to local regulations, timelines, and privacy requirements across jurisdictions.

Alerts & anonymization page

Demo

Pay equity data sync and pay gap remediation

We have made a major step forward in connecting Pay Transparency and PayAnalytics into a single workflow spanning data preparation, analysis, and pay gap remediation.

The process begins with data preparation in Workbench > Data Management, where administrators configure Pay Analysis Data Mapping for the data model – a mandatory action covering worker identification, currency settings, compensation data, and demographic variables. Administrators then generate a data snapshot using the configured data model and create a pay analysis dataset by defining the target PayAnalytics tenant and dataset labels. Next, the snapshot is synchronized to the PayAnalytics tenant and a dataset is created there. Once pay gap analysis is completed in PayAnalytics, a Pay Analysis Admin triggers synchronization back to Pay Transparency. Admins can do so manually via Workbench > Pay Intelligence > Pay analysis results > Sync analysis, using the customer-defined label configured in the Pay Analysis Data Mapping settings. The synchronization enables the use of pay gap analyses in remediation processes.

Pay gap remediation follows in two stages. In the preparation stage, a Pay Analysis Admin reviews and validates the analysis results in Workbench, adjusts recommended raises, configures the remediation process, and publishes the analysis to the Planner for HRBPs. This establishes a clear transition from analysis to execution. In the execution stage, HRBPs access the published analysis in Planner > Pay Analysis, review their assigned population, and enter final pay decisions, with real-time visibility into the impact of their choices. Recommended raises remain read-only for HRBPs, while final offers are entered locally. This clearly separates central recommendations from local decision-making.

In short, Pay Transparency owns the data through snapshots, PayAnalytics consumes it through datasets and analysis, and Pay Transparency orchestrates the pay gap remediation process. Such a workflow supports decentralized execution at scale, drives data-driven, secure, and fully traceable decisions, and establishes end-to-end governance.

Pay Analysis Data Mapping

Pay analysis results and the Sync analysis option

Pay analysis details in the Planner

beqom PaySuite 20.1

Pay information requests

With release 20.1 of the beqom PaySuite application, we have made the pay information request feature available to all users, who can now access it by default as part of their standard platform experience in the platform.

The feature provides a complete, compliant, and auditable workflow for managing workers' pay information requests, including those under Article 7 of the EU Pay Transparency Directive (EUPTD). With this feature, all pay information requests become centralized. It also allows HR teams to prepare, generate, review, and release pay information statements in a controlled and traceable process.

In particular, the feature offers:

• A standardized capability for workers to formally request pay information.

• HRBP-driven request management, aligned with their scope of responsibility.

• Secure document generation and release, using compliant templates and validated compensation data.

• Seamless integration with HRIS systems, ticketing systems, and worker portals via inbound and outbound APIs.

Ultimately, the feature helps employers meet their legal obligations under the EUPTD, it reduces compliance and litigation risks through consistent, validated responses to workers' pay information requests, scales efficiently across large worker populations, eliminating manual request handling, and strengthens trust and transparency in pay practices. Finally, it protects HR teams through controlled workflows, clear responsibilities, and full traceability.

Pay information request feature in Passport

Configuration

Before using pay information requests in production, feature enablement and entry points should be reviewed and configured. This includes enabling the pay information requests sub-feature and setting the allowed request creation channels (API, HRBP, or Worker).

Alerts and SLA monitoring can also be configure to fit the needs of each company. This can be done by specifying warning and overdue thresholds and verifying alert behavior: Alerts tile visibility as well as Status and Alert columns in the Pay Information workspace.

In addition, the feature offers data privacy settings that lets admins configure anonymization thresholds and placeholder values. When the system generates an Article 7 letter in response to a pay information request, it computes counts and average amounts per worker category × gender across compensation elements within the source data snapshot. Administrators can enforce a minimum population threshold and placeholder text to mask averages below the configured threshold.

The following figure illustrates the configuration parameters of the feature within Workbench > Pay Transparency.

Feature enablement in Workbench

Functional scope

Request creation

Organizations can capture pay information requests via multiple, configurable entry points, such as:

• API import, where external systems, for example HRIS, ticketing tools, or worker portals, can create requests programmatically via inbound APIs.

• Worker submission, where workers can submit a formal pay information request using the digital reward statement directly.

• HRBP creation, where HRBPs can manually create requests on behalf of workers when needed.

All requests are centralized and tracked through a single, auditable process.

HRBP triage

HRBPs can manage pay information requests from the Planner > Pay Information workspace. There, they can view all requests for workers within their scope of responsibility, edit request details and track the request status, monitor deadlines, warnings, and overdue requests, and maintain internal notes for coordination and follow-up. Because visibility is dynamic, HRBPs automatically see all relevant requests, including historical ones, without manual assignment.

The following figure illustrates the HRBP view of pay information requests under Planner > Pay Information:

Pay information request list in Planner

Document preparation

For each request, HR teams can prepare the required pay information documentation. Specifically, they can generate pay information letters with compliant document templates, use validated compensation data snapshots to ensure accuracy at the time of response, and preview documents before closing the request.

With this method, responses remain consistent, explainable, and compliant with regulations.

Request closure and communication round integration

Once the response is ready, HRBPs close the request, and the finalized document is attached to a communication round. Depending on workflow configuration, documents are then reviewed and released or automatically delivered to the worker. All closure actions, timestamps, and release events are logged for audit purposes.

Outbound API

External systems can retrieve request outcomes and supporting data via outbound APIs, including:

• An updated request status

• Closure timestamps

• HRBP notes

• The final PDF document attached

• Metadata required for downstream processes or ticket closure

Alerts for pay information requests

Pay information request alerts support HRBPs throughout the request's full lifecycle. They are intentionally divided into two categories, each serving a different operational and compliance purpose.

For new and in-progress requests, alerts are time-based indicators visible in the Alert column of the Pay information requests list. They reflect how close a request is to its regulatory response deadline. Alert states include No alert (with alerts disabled or enabled but no threshold reached), Approaching deadline (when the request has passed the warning threshold but is not yet overdue), and Overdue (with the configured response deadline exceeded). Driven by configurable warning and overdue thresholds, these alerts help HRBPs stay compliant with statutory response timelines, such as Article 7 deadlines, prioritize urgent requests, and manage large volumes of requests while avoiding missed deadlines.

For closed requests, alerts are non-time-based consistency and integrity indicators. They highlight situations where a request has been technically closed but may still require a follow-up or corrective action. We identify three types of such alerts: Closed without document (with the request closed without an attached document), Not released to worker (with the attached document not released to the worker in a workflow-enabled communication round), and Document deleted (with the attached document deleted after the request closure). Thanks to these alerts, HRBPs can ensure response completeness after closure, detect document handling issues, maintain auditability and transparency, prevent compliance gaps resulting from missing or unreleased documents, and save time by surfacing issues automatically.

beqom PaySuite 15.1

With the 15.1 release, we've extended the Digital Reward Statement to give organizations more flexibility in how they communicate compensation and to provide employees with a clearer understanding of their pay. The overview of our enhancements is shown int he following picture:

Digital Reward Statement overview

Show/hide sensitive data toggle

This feature gives employees better control over their privacy when accessing their digital reward statement.

A new toggle buttons, shown in the following pictures, on top of the digital reward statement, allow users to switch between Show and Hide sensitive data:

"Show sensitive data" button

"Hide sensitive data" button

Sensitive compensation information—such as total, direct, and indirect compensation, and breakdown values—is now hidden by default when an employee opens their Digital Reward Statement. When this information is hidden, numeric values are replaced with placeholders (•••••), and certain compensation widgets (e.g., historical compensation, recent salary changes) are not displayed, as illustrated in the following image:

Overview of Compensation tab with hidden information

When user reveals the information, all actual values and widgets become visible.

The toggle resets to Hide on every page load, ensuring sensitive data remains protected in shared or public environments.

Pay information card

This feature enables employees to request access to their pay information in compliance with regulations. It is a configurable card that allows companies to provide employees with access to pay-related information.

The card can be configured in Workbench > Platform Setup> Passport > Compensation > Digital reward statement after clicking the Edit button. By default, the card is disabled and hidden from end users in the Digital Reward Statement. Users with Configuration role can enable/disable the card, add rich text content (up to 500 characters), and decide whether to allow "Pay Information requests" for workers, as shown in the following picture:

Pay information card

If enabled, the card appears in the Digital Reward Statement's right-side panel. It displays the configured text and, if requests are enabled, a Request pay information button (Note: This button is currently non-clickable and is part of a future update), as shown in the following illustration:

Pay information card in the Digital Reward Statement panel

Position in pay range widget

This feature displays an employee's position relative to their pay range in a clear and visual way, showing the minimum, median, and maximum of the employee’s pay range, along with their current pay position.

This gives employees a clear, visual understanding of their pay position within the defined range while providing administrators with flexible configuration options. It helps employees understand where their salary sits in the defined range, promoting fairness and transparency.

By default, the widget is disabled. Users with Configuration role can enable/disable it in Workbench > Platform Setup> Passport > Compensation > Digital reward statement after clicking the Edit button and clicking on the toggle, as shown in the following picture:

Position in pay range section

Admins can edit the section header (mandatory, up to 50 characters) and description (optional, up to 100 characters). A Compensation Policy link can also be configured with a custom label and URL.

The widget appears in the Digital Reward Statement below the Compensation Breakdown section. It can show an optional section header, description, and compensation policy link, all configured by admins.

The widget displays a graphical pay range bar showing the employee’s current salary position against the Min, Median, and Max values of their individual pay range. It fully respects the Hide/show sensitive data toggle, masking the widget when sensitive data is hidden. It also handles out-of-range salaries gracefully by placing the marker within margins outside the Min/Max boundaries.

Empty States:

• If the salary currency differs from the pay range currency, the range values are shown, but the salary is hidden.

• If the minimum and maximum values are missing, or if the minimum is greater than or equal to the maximum, an empty state icon replaces the range bar.

Compensation philosophy card

We're introducing a new Compensation Philosophy widget in the Digital Reward Statement. This widget allows organizations to share a meaningful message about their approach to compensation directly with employees, positioned right after the "Position in pay range" widget.

This feature allows companies to communicate their compensation philosophy, guiding principles, or policies directly within the statement. It provides valuable context to employees about the company’s approach to pay, reward, and recognition, helping them better understand the rationale behind pay structures and policies.

Users with Configuration role can enable/disable it in Workbench > Platform Setup> Passport > Compensation > Digital reward statement after clicking the Edit button and clicking on the toggle, as shown in the following picture:

Compensation philosophy section

Admins can edit the section header (up to 50 characters) and description (mandatory, editable rich-text editor with a 3,000-character limit that supports rich formatting).

The workers are able to see the card displaying a section header (e.g., “Our Compensation Philosophy”) and a rich-text formatted description below it, reflecting the exact content configured by the administrator. All formatting options (bold, italic, lists, links, etc.) are preserved for clear and engaging communication. If the widget is disabled in the configuration, it will not be shown to the worker.

beqom PaySuite 15.0

Digital reward statement

With release 15.0, we are excited to introduce the Digital reward statement, a brand-new page in Passport that provides workers a clear and transparent view of their full compensation package.

It also provides quick access to worker information, latest released documents and useful links to internal resources.

Digital reward statement overview

The Digital reward statement contains various sections that offer helpful information:

• Clear and transparent compensation summary: this section display consolidated compensation elements:

  • Total compensation

  • Total direct compensation

  • Total indirect compensation

Compensation summary

• Compensation breakdown: allows workers to see the distribution of each element within their total compensation package, including:

  • Base pay, incentives, benefits, and allowances

  • Any imported compensation elements

Compensation breakdown

• Historical view of the base salary over five years, highlighting salary changes and percentage increases year-to-year:

Salary history

• On the right side of the statement, several widgets are available:

  • Worker information: displays worker-specific details sourced from imported data.

  • Documents widget: provides access to the latest released documents with options to preview, download or open the full document page.

  • Resources widget: offers quick links to internal or external resources (such as SharePoint, Teams, intranet pages, or uploaded files) that HR teams can configure to support employees with additional context such as benefits information.

On the configuration/administration side, users with the Configuration role can enable or disable the Digital reward statement from Workbench> Platform setup> Worker & Manager Pages > Passport. When the digital reward statement is disabled, the Compensation tab is hidden from Passport.

The resources can be turned on/off by users with the Configuration role, and these users can add, remove or edit resource links and labels.

This feature improves worker engagement by providing self-service access to comprehensive compensation details and resources, while reducing administrative overhead through decreased HR inquiries.

Demo

beqom PaySuite 14.0

Version 14.0, Pay Transparency introduces powerful new features designed to enhance document management and synchronization. These updates provide greater control and visibility over document processes, from automated exports to real-time generation monitoring.

Document generation monitoring

A new Documents Generation page is now available in Workbench to help tracking all document generation activities from a single location. This feature provides complete visibility over documents generation jobs, including status updates, key metadata, and error tracking, making it easier to ensure traceability, visibility, and control over document generation processes.

This monitoring tool provides admins and support teams with full traceability of document generation jobs, improved error detection (especially in large-scale or urgent rounds), and faster troubleshooting with real-time access to source and requester details.

This new page is available in Workbench > Pay Transparency > Document Generation, as illustrated in the following figure:

Document generation page overview

This page can be accessed by:

• Users with the Global compensation admin professional role

• Users with the Compensation admin professional role

• Users with the Read-only professional role

Key Capabilities

• Centralized view of all document generation requests, regardless of their source (e.g., compensation rounds).

• Live status tracking showing whether a request is pending, in progress, completed successfully, or completed with errors.

• Detailed metadata for each request, including:

  • Communication round and document template

  • Source and requester

  • Request, start, and completion timestamps

  • Number of generated documents

  • Number of documents successfully imported to communication round

  • Number of errors (if any)

Export document generation logs details

To enhance traceability and debugging capabilities, and to provide significant business value by enabling Global compensation admins to quickly audit document generation results, troubleshoot issues using detailed technical feedback, identify patterns in errors across workers, templates, or datasets, and maintain traceability for compliance or operational transparency, a new, powerful capability, Export log details, was added to the Document Generation page. This feature allows Global compensation admins to export the full set of document-level logs for any document generation job listed in the table. Each row in the Document Generation table represents a single generation job (e.g., triggered from a compensation round), which may include the generation of multiple documents for different workers. Global compensation admins can now download a CSV file for any document generation entry, providing full visibility into each document’s generation and import status, as illustrated in the following figure:

Export log details action

For any selected generation job, it is possible to download a CSV file that contains one row per document generation attempt within that job. This detailed log includes all relevant metadata and error flags to support auditing, analysis, and troubleshooting.

API to delete all documents of a communication round

It is now possible to delete all documents associated with a specific communication round via a dedicated API endpoint. This action can only be performed by the beqom support team. To request this action, a support ticket must be opened with the beqom support team.

Public API to export all documents of a communication round

A public API is now available to export all documents associated with a specific communication round. This feature allows for full document retrieval per worker using the API, making it possible to automate large-scale exports through scripts or integration tools.

This feature is active for users with the following roles:

• Users with the Global compensation admin professional role

• Users with the Compensation Admin professional role who own the communication round

This is an note/information message.

A dedicated Knowledge Base article is currently being written to explain how to use this API.

On-demand v10 sync execution

Customers using the v10 application for document generation but managing their communication process in Pay Transparency can now manually control synchronization processes between v10 and PaySuite. This includes triggering on demand synchronizations to address urgent situations or to avoid waiting for scheduled automatic runs. Additionally, syncing can be paused when needed, providing greater operational flexibility.

You can now independently trigger synchronization for the following data types:

• HrData :

  • Changes in worker attributes (e.g., org unit, manager)

  • Addition of new workers

  • Organization entity update

• Documents:

  • Newly generated documents post-adjustments requiring immediate sync

• Security:

  • Updates to Primary/Secondary Communication Managers

  • Adding/removing HRBP or Compensation Admin access

Audit & history tracking

Every sync action change is recorded in the [acc].[synch_actions_history] table with the following fields:

• Timestamp: When the action change occurred

• Type: Type of data (HrData, Documents, etc.)

• FromAction: Previous action

• ToAction: New action

Entries in the history table are automatically inserted via a SQL trigger.

This is an attention message.

Only valid values from locked reference tables can be inserted in [acc].[synch]. This ensures data integrity and prevents typos or misconfiguration.

beqom PaySuite 13.1

This is an note/information message.

Following an error in the documentation, please note that a feature released in 13.0, Templates for document generation, was missing from the version release notes and has now been added. Click here to read more about this feature.

Export recipient details from imported documents

To increase transparency and traceability in document distribution, we're introducing a new feature that allows compensation admins to export the list of recipients for each imported static document within a communication round, regardless of whether the document was assigned to all employees, a population, or individual workers.

When a document is imported into a communication round, regardless of the audience type, it is now possible to view the number of recipients per imported document and export a detailed CSV file listing all individual recipients tied to that import.

The following figure illustrates the import action form the comp round configuration wizard interface:

Export action from the interface

The exported file includes important metadata such as:

• Communication round name

• Audience type and selection

  • All Company (no selection for All company)

  • Population name

  • Individual workers (for example: W010 | W027 | W089)

• Document name

• Import date and time

• Name of the user who performed the import

• Total number of recipients

• Detailed recipient list (WorkerID and WorkerName)

This feature covers comprehensive use cases for each type of document import:

• All workers: confirm that documents reached workers across the entire organization,

• population-based validation for targeted groups like regional teams or bonus-eligible populations

• individual worker imports to ensure that exception handling or one-off communications were properly assigned.

This audit-ready and actionable feature supports audit requirements, improves clarity for document tracking, and enables better cross-team coordination by allowing administrators to easily share recipient lists with internal stakeholders or use the exported data for downstream validations.

With this update, compensation and HR teams gain the confidence and control needed to manage complex document delivery scenarios with full visibility, precision, and accountability across all worker communications and documentation processes.

The following figure illustrates the recipient details for the individual worker import:

Recipient details for individual worker import

beqom PaySuite 13.0

This is an note/information message.

Please note that the feature "Export recipient details from imported static documents" was mistakenly included in this release note. This feature was actually released in version 13.1. For more information, refer to beqom PaySuite 13.1 - Feature release notes.

In addition, one feature was missing from the 13.0 release note: Templates for document generation.

Enhanced static document import capabilities

Following the initial release of the static document import for all employees in release 1.11, release 13.0 now brings two powerful enhancements that significantly increase flexibility and control when distributing documents within a communication round:

• Population-based static document import

• Worker-based document import for exceptions

Population-based static document import

It is now possible to upload and assign static documents to a specific population within your organization based on attributes such as language, location, bonus eligibility, or other criteria.

This enhancement enables organizations to tailor messaging and content to meet the needs of specific worker groups, ensure policy and regulatory compliance across different regions or worker segments, and simplify localization efforts with targeted document delivery.

The following figure illustrates the import of a static document for a population:

Document upload for a population

Worker-based document import for exceptions

In addition to group-based distribution, it is now possible to assign individual static documents to specific workers to handle exceptions or unique communication needs.

This solution addresses edge cases and special scenarios without disrupting population-wide distribution, and enables organization to deliver personalized content where necessary (such as custom compensation letters, contract addenda, etc.), while maintaining full audit capabilities and integration with the communication round’s release workflow.

Document import for an individual worker

Templates for document generation

A new feature that simplifies and enhances the process of generating personalized PDF documents using configurable Word templates is being introduced in version 13.0. This release enables Compensation administrators to streamline document production at scale while maintaining accuracy and consistency.

This powerful new feature streamlines your document creation process. With Document Templates, you can now create reusable templates by uploading Word (.docx) files and dynamically inserting merge variables that automatically populate with your system data. The feature includes built-in preview and validation capabilities to ensure your templates are perfect before publishing, enabling seamless document generation at scale. Once published, you can easily access the complete history of all .docx files associated with each template, giving you full visibility into your document workflow.

This new functionality is available in the Document Templates section under Workbench > Pay Transparency, ready to help you create consistent, professional documents with just a few clicks.

The following figure illustrates the section Document Templates in Workbench:

Document templates page

beqom PaySuite 1.12

Transparent manual document import tracking

This release introduces a new level of visibility for manually imported documents within communication rounds. Global compensation administrators and communication round owners can now view a detailed list of all manually imported documents, offering greater transparency and control over content that is distributed manually, particularly for one-off exceptions or targeted communications.

The detailed list of imported documents includes crucial information such as the document name, the date and time of import, the user who imported the document, the intended audience, and the number of recipients, as illustrated in the following figure:

PDF document import interface

For each record in this import list, users have convenient access to actions, making it possible to both view and download the imported document directly, as illustrated in the following figure:

Imported PDF available options

This feature provides several key benefits: it significantly improves observability and accountability, makes troubleshooting easier for support or compliance purposes, and offers clearer traceability of all content manually shared from the communication round import. It's important to note that only documents imported through the Communication Round Import section will be listed in this table; documents imported via SFTP or API, or manually by HRBPs from the planner, will not be visible here.

Enhanced dropdown list in advanced filters

We've significantly improved the advanced filtering interface within the Planner, specifically in the Document and Communication Round sections. The drop-down lists for filtering values now fully support larger sets of options without truncating their names, as illustrated in the following figures:

Updated drop-down list in the Document section

Updated drop-down list in the Communication Round section

This enhancement greatly improves readability and selection accuracy, particularly for entities with longer names, ensuring you can quickly and precisely locate the data you need.

Centralized V10 synchronization log storage

Synchronization logs related to Pay Transparency data exchange with the TCM v10 core platform are now directly saved in the TCM v10 database. This crucial update offers complete visibility into all synchronization operations, making auditing and debugging much more robust and straightforward.

This change is important because it establishes a single, reliable source of truth for all synchronization activity, making it easier to track and report on operations in detail. It also allows for comprehensive tracking of successes and errors, with the ability to drill down into specific details for troubleshooting.

The system now stores various key components for detailed logging:

• acc.synch_logs records high-level synchronization runs, including their run ID, action type (like TransferHrData or TransferNewStatements), start and completion times, counts of successes and failures, and the overall execution result or any error messages.

• acc.synch_logs_documents tracks each document transferred, noting the worker ID, document name/type, import time, whether it was overridden, and the transfer result.

• acc.synch_logs_hr_entities logs paginated HR data, such as workers, employments, and organizations, detailing the entity type, page information, and transfer and ingestion results.

• acc.synch_logs_security tracks security role updates at the worker level, including the action performed (Added, Modified, or Removed), details of role-level security mapping, and the result of each transfer.

beqom PaySuite 1.11

Static document import for all workers

We've just released a new feature designed to revolutionize how documents are distributed. It is now possible to import a single static document from the communication round builder and automatically send it to all workers in a communication round. This update is designed to simplify the document distribution process, reduce administrative workload, and optimize storage efficiency.

• Upload one document once, and we'll deliver it to everyone, as illustrated in the following picture:

Sending the document to "All company"

• Deliver the right information, uniformly, across your entire workforce.

• Eliminate repetitive, manual distribution tasks.

• The new feature works directly within your existing communication round process, as shown in the following picture:

Import PDF documents step

• Import is available as soon as you publish a communication round.

• The imported document follows your established communication round workflow, including visibility rules, timeline, and release steps.

beqom PaySuite 1.9

Enforcement of configurable hierarchies for communication manager access

Starting in Release 1.9, the hierarchy configured in communication round settings now fully controls communication manager access. This replaces the previously fixed line manager hierarchy and allows organizations to define custom access based on their specific needs. Both primary and secondary hierarchies, if set, are applied to determine which workers Communication Managers can view and manage. This update gives greater flexibility in deciding who can communicate with which workers during a communication round.

Secondary communication manager

This release introduces the ability to configure secondary communication managers within a communication round, giving organizations more flexibility in managing access. In addition to managers defined by the primary hierarchy, administrators can now assign additional managers through a secondary hierarchy to ensure broader coverage in the communication process.

The primary hierarchy remains mandatory, while the secondary hierarchy is optional and available when needed. Communication manager access is now fully enforced based on the selected hierarchies, ensuring that only designated managers can view and manage worker documents.

This improvement supports complex organizational structures where multiple managers may need access to worker communications and helps streamline workflows by allowing several managers to oversee and support employees.

Multiple communication managers for a single worker

Enable/Disable Summary Documents for Communication managers

Release 1.9 introduces a configurable option to enable or disable summary documents for communication managers in the communication round configuration wizard. This feature gives organizations more control over document visibility and helps simplify the review process when summary documents are not required.

A new checkbox, labeled Include summary documents is now available when creating or editing a communication round. The setting is disabled by default but can be enabled if necessary.

When summary documents are disabled, API and SFTP imports marked as "summary" are blocked or logged as errors, preventing these documents from being added to the round. The HRBP review screen are automatically exclude summary records, showing only one document per worker, and both the Role” column and filter are hidden.

On the communication manager review screen, the My document section no longer appears, ensuring a simplified view.

This improvement reduces confusion by eliminating unnecessary document placeholders, prevents unwanted document imports, and allows organizations to adjust communication round settings to match their processes.

The following figure illustrates the summary document inclusion setting in the communication round configuration wizard:

Include summary documents checkbox

Advanced filters for HRBPs

This release introduces advanced filters in Planner > Documents, giving HRBPs the ability to filter documents based on recipient and communication manager attributes. These filters improve search precision and bulk action execution, allowing HRBPs to manage document workflows more efficiently for targeted populations.

This is an note/information message.

Advanced filters are available exclusively to HRBPs in this release.

In addition to existing document filters such as Recipient, Communication manager, Read status, Release status, Workflow step, Filename, Role, and Generation date, HRBPs can now filter by attributes including Worker ID, Organization, Region, Country, State, City, and Cost center, using multi-select lists for each, as illustrated in the following figures:

Advanced filter definition

Applied advanced filter

These filters improve the ability to quickly locate specific groups and apply bulk actions like changing workflow steps or releasing and unreleasing documents. This enhancement increases efficiency, reduces manual work, and sets the foundation for expanding these filters to communication managers in upcoming releases.

beqom PaySuite 1.8

HRBP Ability to manually import document for a worker

Users with the HRBP professional role now have the ability to manually upload documents for workers within a specific communication round, ensuring greater flexibility in document management. This option is available only for workers who do not already have any existing document for the round. Files can be uploaded either by browsing or using drag-and-drop, simplifying the process.

If a document needs to be replaced, HRBPs must first delete the existing file before uploading a new one. Deletion is only possible during the HRBP Review workflow step. The upload feature supports only PDF files, with a maximum file size of 20MB. These enhancements provide a structured approach to document handling, ensuring consistency and control within the communication process.

The following figure illustrates the upload interface within a communication round:

Document upload in communication round

Configurable hierarchy for communication manager access

Compensation admins can now define the hierarchy that determines communication managers' access within a communication round. This configuration allows flexibility in structuring managerial access, with available hierarchy options including line manager, matrix manager, communication manager, and compensation manager.

After selecting a hierarchy, users can preview the structure before finalizing the configuration. Defining a primary hierarchy is mandatory, while an optional secondary hierarchy can be set up if additional communication managers are needed.

In this release, the configuration feature is available, but communication manager access remains based on the line manager hierarchy by default. The selected hierarchy will not yet impact access permissions, with full enforcement planned for the next release.

The following figures illustrate the hierarchy selection and preview in the communication round configuration:

Hierarchy selection

Hierarchy preview

TCM V10 Synchronization: HRBP Security enhancements

HRBP security access can now be configured with greater flexibility, allowing for inclusion and exclusion based on organizational units or specific workers. This enhancement ensures more precise control over access permissions, enabling tailored security settings that align with organizational needs.

beqom PaySuite 1.7

Redesign of the "Documents" page in Passport

In version 1.7 of the beqom PaySuite application, the Documents page of Passport was redesigned for improved usability. Tiles now display key metrics, including the total number of documents available, the number of documents read, and the number of new documents for each worker. Additionally, document statuses, such as New or Read, are displayed as tags within the table, allowing users to quickly identify and differentiate between new and read documents.

The following figure illustrates the new design of the Documents page:

New Documents page

Bulk workflow step change

Before 1.7 release, the action Change workflow step was only possible at individual document level. From now on, users with the HRBP professional role are able to apply Change workflow step in bulk.

As of the 1.7 release, it is now possible for the HRBP professional role to change the workflow step of documents in bulk (in previous versions, this operation could only be performed at individual document level), as illustrated in the following figure:

Mass changing document workflow step

Allow selection across multiple pages for all bulk actions

Users with the HRBP and communication manager professional roles can now apply all bulk actions across all available pages of the list of documents in Planner > Documents (before 1.7, bulk release and bulk unrelease were restricted to one page and users needed to go through the pages one by one).

Documents audit trail

With the 1.7 release, users assigned the HRBP and communication manager professional roles now have access to the audit trail for any document within their scope. This enhancement provides a complete history of actions performed on a document, including the date and time of each action and the user responsible for it, as illustrated in the following figure:

Document audit trail

beqom PaySuite 1.6

TCM v10 synchronization

In 1.6 release we introduced audit of TCM v10 synchronization. This enhancement keeps trace of all the activities performed by the TCM v10-PaySuite synchronization on workers, roles, and documents. Additionally, it is also be responsible for error handling. The audit increases the control over TCM v10 features and speeds up the fixing progress should any error occur.

Redesign of the Documents section

• After the redesign, filter tags are now visible for users with HRBP and Communication manager professional roles, as illustrated below:

Filter tags

• The visibility of the communication rounds in Planner > Documents is now based on the start and end dates defined for the rounds. The communication rounds are hidden for bith HRBPs and communication managers outside of the period defined by the start and end dates.

• Users with the communication manager professional role are also able to see the summary document displayed outside of the document table. It isnow displayed in the My summary document section located above the document table, as illustrated in the following figure:

  

  My summary document

Communication round - Workflow configuration

From the 1.6 release, users with the compensation admin professional role can configure workflows when creating a communication round.

By default, when creating a communication round, workflow steps are enabled, as illustrated in the following figure:

Default workflow settings

Compensation admins can disable the workflow, as illustrated below:

Disabled workflow

Compensation admins may also choose to enable workflow, but disable one or both steps.