Release Notes: New Releases

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 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?

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.

Previously, the Modified By column in the Daily Sales Summary grid appeared blank or displayed "R365" when the record was last edited by a user who has since been deactivated. The Modified By column now correctly displays the name of the user who last edited a Daily Sales Summary record, even if that user is no longer active in the system.

A new system preference, Require location selection on upload, is now available for organizations using AP Capture AI. When enabled, users must select a location before a manual AP invoice or credit memo upload can be submitted.

If a user clicks Upload without selecting a location, a "Location is required" error displays inline. Once a location is selected, the upload proceeds as normal. Users with access to only one location are not affected — their location is pre-filled automatically.

This setting applies to manual uploads from Documents to Process and the Create Menu. Email and FTP uploads are not affected.

For organizations newly activating AP Capture AI, this setting is enabled by default. For existing organizations, it is disabled by default and can be turned on in Administration > System Preferences > Miscellaneous.

For more information, see Require Location Selection on Upload.

Report subscriptions that generate files larger than 10 MB now deliver via a download link included in the email rather than as a file attachment. Reports under 10 MB continue to deliver as attachments. Previously, subscriptions with large report files either arrived without attachments or failed to send entirely.

No configuration changes are required. All existing subscriptions run as scheduled with reliable delivery regardless of report file size.

Learn more about report subscriptions.

Logged-in readers can now mark articles, decision trees, API endpoints, and page categories as favorites using the heart icon, and access all saved items from a dedicated Favorites section in the left panel or via their profile.

When printing checks locally from a Bank Expense or AP Payment transaction, the From address on the check now reflects the Billing Address of the Location or Legal Entity record, based on your Print Checks From setting in System Preferences. If no Billing Address is defined on the record, the Shipping Address is used as a fallback.

Previously, the Shipping Address was always used as the From address, even when a Billing Address was defined.

To verify or update the addresses on your Location or Legal Entity records, see To and From Addresses in R365 Payments.

Restaurant operators can now access AI-powered labor insights directly in the DSS, replacing static reports with dynamic trend analysis informed by Snowflake data.

Labor Insights introduces an AI-driven analytics experience that surfaces patterns and trends over time across multiple dimensions — including labor vs. guests, scheduled vs. actual hours, and overtime vs. scheduling patterns. Key capabilities include:

• Trend analysis across weekly, monthly, and yearly time horizons to surface longer-term labor patterns and seasonality.

• Turnover trend exploration with correlation to overwork and scheduling imbalance, helping identify at-risk teams or locations earlier.

• Multi-location comparisons to benchmark staffing performance across sites (additional comparison views planned).

• In-product feedback loops and targeted in-app messaging so users can act on insights and share feedback without leaving the product.

• Planned support for additional context such as weather data and cohort segmentation to better explain external drivers of labor performance.

Learn more about opting-in to Labor AI insights.

Break information is now available directly in Timecards, giving managers greater visibility and control over employee breaks. Breaks are out of beta and available to all Timecard users.

• View breaks on the Timecard grid — Break details appear as a column on the Timecard grid and on individual employee timecards. → [Timecard Page]

• Add, edit, or delete breaks — Managers can make corrections directly in the timecard without leaving the page. → [Manage Breaks on Timecards]

• Audit log tracking — All break changes are captured in the timecard audit log for accountability and record-keeping. → [Timecard Shift Record]