Release Notes: Q3 2026

The Employees area in Workforce includes a new Match + Merge experience that identifies duplicate employee records and combines them into a single primary record. When an employee record has a likely duplicate, a Suspected duplicate records banner appears on the record. Selecting Review + Merge opens a wizard that recommends a primary record, either the most complete record or the record that has received an R365 Payroll payment, and steps through which duplicate records to merge. The previous View Proposed Merges button is removed.

A Merge History tab on the primary record lists the records merged into it and provides a Restore action to separate a record that was merged in error. This gives Workforce and Payroll admins one accurate record per employee across locations, with a clear audit trail and a reliable way to recover from a mistaken merge. The experience is available to users with the Merge Employees permission.

A few behaviors to note:

• The record that has received an R365 Payroll payment is always the primary record and cannot be changed.

• Selecting Ignore Merge Recommendation dismisses a suspected match and removes the banner from the record.

• Personally identifiable information on a merged record is removed during the merge, so it must be re-entered if the record is later unmerged.

• Merges completed through the manual or bulk merge tools use the previous wizard and do not appear in the Merge History tab, so they cannot be unmerged.

The POS Accounts tab in the Mapping Tool has a new look! The updated layout includes a Views bar, Search, and grid options for filtering and managing columns.

A Classic view toggle is available in the upper-right corner of the tab for users who prefer the previous layout. Toggling it on switches back to the classic list view.

Learn more about the Mapping Tool Page.

The R365 Public API is now fully documented in the R365 Developer Hub, covering 68 endpoints across eight areas of the platform: Accounting, Inventory, Brand Management, Core, User Management, Sales, Labor, and POS. Each endpoint follows a consistent URL convention with complete request and response references, parameter details, and error documentation.

The Public API supports both reading and writing data and covers significantly more of the platform than OData, including new endpoints in this release for Daily Sales, Labor Punches, Labor Jobs, Labor Employees, Journal Entry creation, and Legal Entity. Existing integrations continue to work during the transition, and both the new and current ("Connector") endpoints are documented under the same hub. For new integrations or updates to existing ones, the Public API is the recommended path forward. To request credentials and access scopes, contact your CSM.

Learn more about R365 Public API documentation.

Not sure which to use?