beqomPay Suite 20.1 - Feature release notes
This article details the latest improvements introduced in version 20.1 of the beqomPay Suite application, their benefits for our end-users, and their principles of use.
Pay Transparency
Pay information requests
With release 20.1 of the beqom Pay Suite 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.