PayAnalytics - July 2026 detailed release notes
Release v2026-07-28_01
| Type | Jira | Description |
|---|---|---|
| PA-8485 | The analysis engine now computes and stores each group's statistical significance and standard errors as they would stand after recommended raises are applied, along with the standard errors of the current pre-raise model. This is groundwork only: no report or screen surfaces these values yet, but analyses that recommend raises now carry this data for future use in showing how statistically reliable the post-raise picture is. When no raises are recommended, no after-raises statistics are included. |
Release v2026-07-21_01
| Type | Jira | Description |
|---|---|---|
| PA-7783 | On-screen wording for closing pay gaps on a per-group basis was standardized across the platform. The employee pay transparency report (both tabs, plus print and Excel exports), the run-analysis form, and system settings now use consistent terminology, including "Employee category," "Category comparison," "Pay band positioning," and "Predicted compensation range." This is a wording-only change; no calculations or underlying data were affected. | |
| PA-7924 | In the Compensation Model page, an issue was corrected where the explanatory text above a categorical factor's driver graph could name the wrong category as the "Base Value" whenever that category's bar fell below zero. The label now always matches the base group shown by the graph's zero-point and the Compensation for Base Values summary table. The English wording was also clarified. | |
| PA-8176 | In the Pay Equity overview report, long axis labels beneath the bars in the pay-gap chart previously overlapped and became unreadable, most noticeably in German and other languages with longer wording. Labels that don't fit now wrap onto multiple lines instead of overlapping, which may make the chart slightly taller when needed; shorter labels are unaffected. | |
| PA-8179 | In the report text editor's template expression wizard, inserting an analysis value after a percentage-based value could produce a formatting error and prevent the text section from being built. Percentage formatting is now applied only to genuinely percentage-based values, such as adjusted and unadjusted pay gaps, while group-name descriptions and headcount values are no longer mistakenly formatted as percentages. | |
| PA-8185 | An issue was corrected where users with data access restricted to a subset of the dataset (for example, only their own country) were incorrectly blocked from generating the Pay Transparency statement or Pay Explainability report for employees in a sub-group analysis they otherwise had full access to. Access is now evaluated within the sub-group being viewed rather than against the entire dataset, so these users can view results for sub-groups they fully have access to. | |
| PA-8342 | Applying a saved preset or recent configuration to a different dataset could silently carry over a reference group selection that no longer matched the dataset's fields, changing which group pay gaps were measured against without warning. Reference group selections are now validated against the target dataset when a preset is applied: unsupported selections are reset to "Automatically select" with a warning, and mismatched configurations leave the demographic variables section marked incomplete until corrected. | |
| PA-8356 | An issue was corrected where users who receive access through an assigned role, rather than individual permissions, saw an "Operation failed" error when creating a new employee group marked "Visible to others" from the employee list, and the group was not saved. These users can now successfully create shared employee groups. Creating private groups and editing existing groups to make them visible were already working and remain unchanged. |
Release v2026-07-14_01
| Type | Jira | Description |
|---|---|---|
| PA-7783 | On-screen wording for closing pay gaps on a per-group basis was standardized across the platform. The employee pay transparency report (both tabs, plus print and Excel exports), the run-analysis form, and system settings now use consistent terminology, including "Employee category," "Category comparison," "Pay band positioning," and "Predicted compensation range." This is a wording-only change; no calculations or underlying data were affected. | |
| PA-7924 | In the Compensation Model page, an issue was corrected where the explanatory text above a categorical factor's driver graph could name the wrong category as the "Base Value" whenever that category's bar fell below zero. The label now always matches the base group shown by the graph's zero-point and the Compensation for Base Values summary table. The English wording was also clarified. | |
| PA-8176 | In the Pay Equity overview report, long axis labels beneath the bars in the pay-gap chart previously overlapped and became unreadable, most noticeably in German and other languages with longer wording. Labels that don't fit now wrap onto multiple lines instead of overlapping, which may make the chart slightly taller when needed; shorter labels are unaffected. | |
| PA-8179 | In the report text editor's template expression wizard, inserting an analysis value after a percentage-based value could produce a formatting error and prevent the text section from being built. Percentage formatting is now applied only to genuinely percentage-based values, such as adjusted and unadjusted pay gaps, while group-name descriptions and headcount values are no longer mistakenly formatted as percentages. | |
| PA-8185 | An issue was corrected where users with data access restricted to a subset of the dataset (for example, only their own country) were incorrectly blocked from generating the Pay Transparency statement or Pay Explainability report for employees in a sub-group analysis they otherwise had full access to. Access is now evaluated within the sub-group being viewed rather than against the entire dataset, so these users can view results for sub-groups they fully have access to. | |
| PA-8342 | Applying a saved preset or recent configuration to a different dataset could silently carry over a reference group selection that no longer matched the dataset's fields, changing which group pay gaps were measured against without warning. Reference group selections are now validated against the target dataset when a preset is applied: unsupported selections are reset to "Automatically select" with a warning, and mismatched configurations leave the demographic variables section marked incomplete until corrected. | |
| PA-8356 | An issue was corrected where users who receive access through an assigned role, rather than individual permissions, saw an "Operation failed" error when creating a new employee group marked "Visible to others" from the employee list, and the group was not saved. These users can now successfully create shared employee groups. Creating private groups and editing existing groups to make them visible were already working and remain unchanged. |
Release v2026-07-07_01
| Type | Jira | Description |
|---|---|---|
| PA-8183 | An issue was corrected where exporting the Pay Explainability report to PDF omitted categorical compensation driver details. Users can now expand multiple categorical drivers at once using a new Expand all / Collapse all option, and the exported PDF matches exactly what is shown on screen. | |
| PA-8184 | An issue was corrected where printing or exporting the Pay Explainability report to PDF caused chart elements such as bars, markers, and the average line to disappear, leaving only text labels. The Pay range positioning and Employee group positioning charts now print and export with their full visuals. | |
| PA-8304 | An issue was corrected where typed free-text in a column search box was applied to server-computed results, so the on-screen table narrowed but the calculated output did not match. Free-text search is now treated only as a helper for finding options, and Workforce Analytics KPIs, group reporting, and Compensation Assistant comparison results are computed from the applied filter selections only. | |
| PA-8312 | An issue was corrected in the Workforce Analytics view where an empty filter (one created but selecting nothing) returned all employees instead of none. An empty selection now correctly returns no employees, while applying no filter still includes everyone. | |
| PA-8315 | An issue was corrected in the EU Pay Transparency Directive (EUPTD) employee right-to-request report where a comparison group that was too small to display was shown as an access-denial message. Users with restricted data access now see the accurate reason: that the employee category is too small to display while protecting individual privacy. | |
| PA-8326 | In the Pay Adjustments area, when a pay equity analysis is split into subgroups, an employee's right-to-request report link now opens the report scoped to the employee's own child subgroup analysis rather than the parent analysis, reflecting their actual comparison group. Employees whose subgroup has no child analysis continue to open the parent-scoped report. |