Release Notes: Q3 2026

The Prep feature is now available in R365 — a recipe-based workflow for planning and tracking daily food preparation. Previously, prep was set up and tracked through purchase items; now prep is configured and calculated from your recipes.

This update includes the following:

• A new Prep Sheet Wizard guides you through daily prep in three steps: entering on-hand counts, reviewing suggested prep quantities (with the Buffer Tool to adjust for expected demand), and previewing the sheet before printing.

• Prep is set up directly on the recipe record's Prep tab, so prep configuration lives alongside recipe costing instead of on the purchase item.

• Prep Settings let you manage prep configurations, categories, and stations — so prep quantities calculate correctly and prep sheets stay organized the way your kitchen works.

• Enabling Prep on a recipe automatically marks it available in inventory, removing a manual setup step.

• The Prep page and its terminology now reflect the recipe-based model — Prep Recipes and Prep Templates.

Learn more about using Prep.

For users in the Prep beta: the experience above is now the standard, generally available version of Prep — the same wizard and recipe-based setup you've been using. Since beta, remaining purchase-item-based prep records have been automatically converted to Prep Recipes, and any recipes not yet marked available in inventory have been flagged automatically as part of that conversion. Read more about the migration to Prep here.

Acquisition Date and Asset Category now have columns on the Assets grid. Previously, this information was only stored on the asset record and did not display in the grid.

As with all columns, these columns can be sorted, filtered, and exported.

Learn more about the Assets grid.

Restaurant365 is announcing an end-of-life (EoL) date of July 1, 2027 for Compeat Advantage and will begin a planned transition of those customers to the R365 platform.  

Migration support to the Restaurant365 platform is available. Current Compeat Advantage customers will receive additional information via email can reach out to their Account Executive with questions.

Read more about the planned transition.

Introducing the unified AP Credit Memo record! The AP Credit Memo is now the same experience across Accounting and Inventory. Previously, the AP Credit Memo record in Accounting and the AP Credit Memo record in Inventory opened different forms. Now, opening a credit memo from the Accounting app or the Inventory app opens the same AP Credit Memo form.

The new AP Credit Memo has a new look, including a dedicated Alerts tab that flags line items priced outside a vendor's contracted price range. Fields, tabs, and actions depend on Accounting/Inventory access, user permissions, and vendor setup.

Users can try it today by clicking a Try the new credit memo experience button on the classic form, and switch back to the classic view at any time — both experiences are available at this time.

Learn more about the unified AP Credit Memo.

Introducing the unified AP Invoice!

The AP Invoice is now the same experience across Accounting and Inventory. Previously, the AP Invoice record in Accounting and the AP Invoice record in Inventory opened different forms. Now, opening an invoice from the Accounting app and the Inventory app opens the same AP Invoice form.

The new AP Invoice has a new look, and the drag-and-drop-anywhere function enables users to upload documents to the invoice from anywhere on the form. Fields, buttons, and invoice actions depend on Accounting/Inventory access, user permissions, and vendor setup.

Users can try it today by clicking a Try the new invoice experience button on the classic form, and switch back to the classic view at any time — both experiences are available at this time.

Learn more about the unified AP Invoice form.

Introducing the new Create Payment Run experience! The form has a new look — a full-screen view built around the invoice list, with the run's configuration fields tucked into a collapsible panel. Users can try it today by clicking a Try the new payment run experience button on the classic form, and switch back to the classic view at any time — both experiences are available at this time.

This update includes the following:

• Filtering and searching apply across your entire invoice list, not just the rows already loaded on screen.

• R365 Payments setup issues appear as a single warning summary above the list, with the affected fields flagged directly, instead of a series of pop-up messages.

• Draft and Unapproved payment runs can be deleted directly from the form.

• Unapproved payment runs show a new Workflow tab with the approval history and a status control for the run's approver.

• Once payments are created, actions like printing checks, exporting, and sending R365 Payments are all available from a single button in the form header.

Learn more about creating a payment run.

Managers can submit time off requests on behalf of employees directly from the mobile app, just like on web.

• A new + button on the Time off tab opens the Request time off screen, where managers can submit a request for any employee at their assigned locations.

• Selecting an employee automatically loads that employee's time off types, accrual balances, blackout dates, and date restrictions, so the request reflects their specific rules.

• If the employee has reached their time off request limit, a confirmation dialog opens with the option to override the limit or cancel and return to the form.

This feature is available to users with scheduling permissions in the mobile app and requires no setup.

Partially retiring a fully depreciated fixed asset now succeeds instead of being blocked. Previously, attempting to partially retire an asset once its life-to-date depreciation reached its cost basis returned an error, even though disposing of a portion of a fully depreciated batch asset is a legitimate scenario, such as retiring 10 of 30 fully depreciated chairs recorded as a single asset.

This update includes the following:

• Accumulated Depreciation is reduced proportionally to the retired percentage of Acquisition Cost, so life-to-date depreciation never exceeds the asset's new, lower cost basis.

• Salvage Value is reduced proportionally to the retired percentage of Acquisition Cost on every partial retirement — not only when the asset is fully depreciated. Undoing a partial retirement restores the asset's original Salvage Value exactly.

• The depreciation schedule recalculates from the reduced Acquisition Cost, Accumulated Depreciation, and Salvage Value after each partial retirement.

Learn more about partially retiring a fixed asset.

We've made it easier to set up and manage workers' compensation (WC) coverage across your restaurants.

Head to Admin > Payroll > Workers' Comp to find a redesigned page for creating and managing your WC codes and rates in one place — so payroll admins no longer have to track this information across multiple screens.

You can see your rates by Current, Future, or Past status (or view them all together), add a new rate with a short guided form (pick your state, choose a class code, and enter your rate details), and schedule a rate change ahead of time — you'll see a note on the record letting you know when the new version takes effect. If a record is missing required information or needs a second look, you'll get a heads-up right on the page.

Workers' comp codes are now set at the job title level instead of for each employee, so payroll admins only have to assign a code once per job rather than repeating the setup for every person who holds it. Go to Workforce > Employees > Jobs to assign a WC code to a job title, and it automatically applies to everyone in that job. On individual employee job records, the WC code now displays automatically based on the employee's job title, so there's nothing to set there directly — and labor admins can see WC code coverage across every job title right from the Jobs list.

If you import your jobs, the job import file now includes a WC Code column, so you can assign codes to many job titles at once instead of updating them one by one — saving time when you're rolling out or adjusting coverage in bulk.

R365 Payroll now supports configuration of Paid Family and Medical Leave (PFML) contribution settings directly from the Company Tax Profile page. Payroll admins can set employer and employee FLI contribution percentages and manage subject employee headcount for PFML compliance reporting across supported states, including Colorado, Delaware, and Minnesota.

Headcount for PFML purposes is now calculated and refreshed automatically, with state-specific rules enforced during payment processing. Delaware's rolling 12-month headcount lock and Minnesota's end-of-year headcount lock are applied automatically. A manual override is available when the system-calculated value requires adjustment.

Delaware payroll companies also have a new per-employee PFML waiver option. The Exclude from Delaware Paid Family Leave employer headcount calculation toggle is available on individual employee records for eligible employees, allowing per-employee waiver elections.

Learn more about PFML contribution setup and the Company Tax Profile.

Month-to-date, quarter-to-date, and year-to-date totals for paycheck deductions — such as 401(k) contributions, insurance, and garnishments — are now calculated based on the date an employee was paid, rather than the pay period's end date. This brings deduction totals in line with how earnings and taxes have always been calculated.

Previously, if a pay period ended in one month but the paycheck was issued the next, the deduction counted toward the month the work was performed. It now counts toward the month the paycheck was issued.

This update includes the following:

• Applies to deduction and employer contribution totals on the My Account → Earnings page, pay stub details (web, mobile, and PDF), the Payment Details → Deductions tab, and the Benefits & Deductions and Negative Balances reports.

• Deduction totals for already-issued 2026 paychecks have been recalculated to reflect this change, so employees and employers may notice a change in year-to-date deduction amounts.

• Garnishment totals are included in this update.

Learn more about deduction totals on the Payment Details page.

The Daily Operations Report is a new report that brings daily and weekly operations data into a single view, with a built-in comparison to the same day last year. Previously, getting this full picture required running several separate reports, including the Flash Report and separate labor, payment, service, and day-part breakdowns.

This report includes the following:

• Presentation view shows KPI scorecard tiles; Grid view shows the same metrics as a spreadsheet-style table, optionally grouped by location, day, or both.

• Optional prior period or prior year comparison columns for Net Sales, Labor %, Guest Count, and Avg Check.

• Optional sections for Labor Amount, Advanced Metrics, Sales by Day Part, Payment Type, Service Type, and Server Analysis, each of which can be turned on or off.

• Clicking a KPI number drills through to the underlying transaction or employee detail.

The Pre-Check Earnings report is now available for customers with HCM Payroll enabled. This report:

• Shows every earning tied to employees in an open pay run, before payroll is finalized.

• Filters by pay run, location, employee status, FLSA status, and employment type.

• Offers a detailed or summary view, with grouping by earning type, location, employee status, or FLSA status.

• Exports to PDF or Excel.

The report is read-only and does not include closed or finalized pay runs.

Payroll Hub is a new landing screen for running payroll, replacing the legacy Payroll Overview page. This rollout is controlled by R365 as part of a phased release; there is no self-service opt-in or opt-out. An organization's rollout tier determines which screen it sees and which readiness cards appear once it has Payroll Hub:

• At the base tier, the organization sees the legacy Payroll Overview page.

• At the enabled tier, the organization sees Payroll Hub with the pay-run card and the Unpayable Employees readiness card.

• At the higher tier, the organization additionally sees readiness cards for PTO, Daily Sales Summaries, timecards, and tip distributions, for each feature it already has enabled.

Payroll Hub is expected to become the default landing screen for every organization as the rollout completes.

What's New

• The Payroll page now opens to Payroll Hub, a single screen that shows readiness checks

• Selecting a readiness card opens a side panel with an inline approve or deny option, or a review-form path into the existing approval workflow.

• The pay-run card's View action launches the payroll approval wizard once every readiness item clears.

• A new Historical Pay Runs page lists a legal entity's past pay runs, reached from Payroll Hub.

Why It Matters

• Users who process payroll see everything blocking a pay run in one screen and resolve it without navigating away.

• Card counts and readiness state update automatically after an in-Hub resolution, so processors do not need to refresh or verify elsewhere.

The new SMS Log page lists SMS messages sent by Announcements, Manager Log, and other SMS-enabled features. Each entry also shows the message's delivery status and failure reason. Selecting an entry opens a detail panel showing the sent time, status, recipient, source, and message content.

The Daily Sales Summary now shows dedicated status indicators while labor is still calculating.

• The Total Labor card, the Labor section header, and each employee's Hours worked, Break, and Variance columns may show a loading state until the system calculates the values.

• A dismissible banner explains which values are still calculating. A separate alert flags issues that need attention.

• Issue icons now appear only for problems that need attention: unpayable employees, failed calculations, no labor, or a missing fiscal period. Each icon includes its own explanation.

With the appropriate permissions, use the new Bulk edit items wizard to add or remove vendor items across multiple purchase order templates at once.

Before this release, updating vendor items on PO templates required opening and editing each template individually. This was especially time-consuming when rolling out seasonal items or limited-time offers across many locations.

With this release, the Bulk edit items wizard walks users through selecting a vendor, choosing the items to add or remove, and picking the templates to update. Users then apply all changes in a single operation. The wizard shows a full preview of which templates and locations the changes affect before you commit them.

The Prep section on purchased item records is now read-only. The path for creating prep items from the purchased item record is no longer available.

What changed:

• The Prep section on purchased item records is now locked. If prep was previously off for an item, the toggle stays locked in the off position. If prep was previously on, you can turn off the toggle. This action is permanent. Once you turn off prep for a purchased item, you cannot re-enable it.

• The Add Items sheet in Create Prep Items now shows recipe items only. Purchased items no longer appear in the list.

• For prep items that were created from purchased items, the Available toggle locks permanently once you turn it off. You must confirm the change before it takes effect. This applies to the Prep Items list and the prep item record.

The [AP Transactions page](/doc/docs/ap-transactions) has a new look and a new [Memorized AP Transactions tab](/doc/docs/memorized-ap-transactions-page). This page brings AP invoices, credit memos, and payments together in one searchable, filterable list. It replaces the separate legacy views. The Memorized AP Transactions tab replaces the standalone Memorized AP Transactions page. It adds schedule status and template management directly in the grid.

This update includes the following:

- A new [AP Transactions grid](/doc/docs/ap-transactions)

- A bulk action toolbar for Approve, Unapprove, Print Checks, Delete, and Send to R365 Payments, with additional actions for payment holds, check stubs, transaction summary, and 1099 updates

- A [Memorized AP Transactions tab](/doc/docs/memorized-ap-transactions-page) on the AP Transactions page, replacing the standalone page

- Status badge, next run date, and repeat count visible for each memorized template directly in the grid

- Pause and resume for memorized templates, individually or in bulk across multiple selected rows

- Quick filters on the memorized tab: Active, Completed, Paused, Due this week, and Expiring soon

The rule condition editor in the Rule Vault now includes an Ends With function. This function joins Equal To, Contains, and Starts With in the Function dropdown. It matches values that end in a known pattern, such as a vendor code or account suffix. Unlike Contains, it will not over-match broader text.

Ends With is available in the following contexts:

- For *Bank Activity* sources, on the Name and Comment fields.

- For *R365 transaction* sources, on the Location, Comment, Check Memo, and Vendor fields.

- Across all rule types that support string conditions: Matching, Payment Group Matching, Create Transaction, and Custom Matching.

Learn more about [creating matching rules](/doc/docs/create-a-matching-rule) and [transactions rules](/doc/docs/rule-vault-create-a-rule) in the Rule Vault.

A new [Edit Guest Count](/doc/docs/daily-sales-review-a-dss#guest-count-review) permission is now available. This permission controls edit access to the Guest Count field on the [Daily Sales Summary (DSS)](/doc/docs/daily-sales-summary). When you disable the permission for a role or user, the Guest Count field on Daily Sales Summary records is read-only. The permission applies to both New DSS and Classic DSS.

POS integrations continue to write to Guest Count regardless of how you configure this permission.

At release, the permission defaults to off for all roles except Full Access and Admin, which default to on.

A new Edit Users in Bulk permission is now available. This permission controls access to two bulk-editing entry points: the [Mass Role Update page](/doc/docs/mass-role-update) and the [bulk-edit checkboxes on the Users table](/doc/docs/bulk-edit-users-page).

The two permissions are linked. Edit Users in Bulk requires Edit Users to be active. Enabling Edit Users in Bulk automatically enables Edit Users. Disabling Edit Users automatically disables Edit Users in Bulk.

The first time this feature is enabled, the system automatically grants Edit Users in Bulk *to any role or user that already has* Edit Users. This preserves existing access without manual reconfiguration.

Roles without Edit Users in Bulk cannot access the Mass Role Update page, including via direct URL navigation. The bulk-edit checkboxes on the Users table also do not appear for these roles.

Permissions now control integration type visibility in Admin → Integrations. The system hides HR, Payroll, Invoices, and POS integration cards for users without a view, sync, or admin permission for that integration type. The system now scopes security roles at the integration type level. This supports least-privilege access to sensitive integration configuration.

When a user has no integration type permissions and no Mapping Tool access, the system hides the Integrations menu item in the left navigation entirely.

Each integration type supports three permission tiers:

- View Only: read-only access to integration cards and connection status

- Sync or Polling: ability to trigger sync and polling operations

- Admin: full control, including connect, disconnect, and settings management

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?