---
title: "Toast POS Integration"
slug: "toast-pos-integration"
description: "R365 and Toast POS integration: connection requirements, data flow, and configuration details."
status: "update"
updated: 2026-10-14T19:24:04Z
published: 2026-10-14T19:24:04Z
canonical: "docs.restaurant365.com/toast-pos-integration"
---

> ## Documentation Index
> Fetch the complete documentation index at: https://docs.restaurant365.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Toast POS Integration

Restaurant365 integrates with Toast POS, enabling seamless data flow between a location's POS and the R365 platform. This allows daily sales, labor, and payment information to automatically drive reporting and accounting processes in R365. [Learn more about POS integrations](/doc/docs/pos-integration-overview).

## Data Transfer from Toast to R365

R365 connects directly to Toast POS's cloud service through an API. Once authorized, data flows automatically into R365. Learn more about [connecting Toast](/doc/docs/toast-pos-integration#connect-a-toast-pos-to-r365) below.

The POS system is the source of record for all daily sales and labor activity. R365 reports on, *but does not alter*, the information recorded in the POS.

The daily polling cycle imports Toast data from the previous business day and creates corresponding records in R365 for financial and operational reporting, including the [Daily Sales Summary (DSS)](/doc/docs/daily-sales-summary).

### Sales Data from Toast

When sales data is imported, R365 creates detailed records based on the information received from the POS. [Learn more about **POS Sales integrations**](/doc/docs/pos-sales-integrations).

*Click to expand for additional information.*

****Sales ticket** records generated from Toast data include:**

- Receipt number (display number in Toast)
- Date (opened date)
- Server
- Service type/revenue center.
- Guest count
- Menu items, including modifiers.
- Tax
- Charge tips
- Payments
- Discounts.
- Credit card fees
- Voids

[Learn about alternative polling configurations which change the way sales data is imported below](/doc/docs/toast-pos-integration#toast-pos-integration-configurations).

****Paid outs** and **paid ins** are imported to R365.**

By default, paid outs in R365 are named by the **reason** entered in Toast. [Learn about alternative polling configurations below](/doc/docs/toast-pos-integration#toast-pos-integration-configurations).

****Deposits** entered in the POS are imported to R365.**

Multiple deposits can be configured to import as a single deposit in R365. [Learn about alternative polling configurations below](/doc/docs/toast-pos-integration#toast-pos-integration-configurations).

### Labor Data from Toast

When labor data is imported, R365 creates employee-related records derived from POS data. [Learn more about **Labor integrations**](/doc/docs/labor-integrations).

*Click to expand for additional information.*

****POS employee** **records** are created in the next polling cycle after an employee is added to Toast POS whether or not they have clocked in.**

If a new Toast employee needs to be imported immediately, [repoll](/doc/docs/toast-pos-integration#repolling-data) the latest DSS.

****Employee records** created from Toast include:**

- Hire date (created on date in Toast)
- Payroll ID (external ID in Toast)
- Email address

****Job records** created from Toast include:**

- Payrate (default wage in Toast)

****Labor details** created from Toast time punches are polled with a **14 day labor lookback** window to capture updates made in the POS after the initial import.**

This means that changes made in Toast to labor data from the last 14 days will automatically import with the next regular polling cycle, or by repolling a DSS within the lookback period for a date after the adjusted business day.

For example, if a shift from Monday is edited in Toast on Tuesday, the shift in R365 will automatically update on Wednesday when the DSS imports, or by repolling the Monday DSS.

****Labor detail**s created from Toast time punches include **breaks**.**

- **Paid breaks** count toward worked hours
- **Unpaid breaks** cause the time punch to be split into separate pairs

****Declared** cash tips are imported to R365.**

R365 does not import **undeclared cash tips**.

### Repolling Data

When changes are made within the POS to correct missing or inaccurate data, the DSS must be repolled to transfer the updated data to R365.

Locations that have a **Sync** button on the Locations tab of the [Integrations Dashboard](/doc/docs/integrations-dashboard-locations-tab) can be repolled from that tab. An approved DSS must be unapproved first. Learn more about [re-syncing POS data from the Dashboard](/doc/docs/re-sync-pos-data-from-the-dashboard).

For other locations, if the affected DSS is less than 30 days old, the fastest way to trigger a repoll is to delete the DSS record from the Daily Sales Summary (Classic) page. R365 regularly checks for missing DSS dates, and a deleted DSS will automatically repoll with the most current POS data within about 30 minutes..

For DSS older than 30 days, please [contact R365 Support](https://help.restaurant365.net/en/support/home#contact) to assist with repolling the data.

---

## Customization

### Toast POS Integration Configurations:

R365 Support uses the default polling configuration when setting up a new location. If other Toast integrations exist in the system, R365 will use the same configuration in use at the existing locations.

*Click to expand for additional information and images.*

**The **default** Toast configuration imports **discounts** as they are named in the POS. This can be changed to import discounts grouped by **sales category**:**

The below examples show the discounts section of the same DSS, originally polled with the default configuration and repolled with the discounts by sales category configuration.

| Default configuration | Import by sales category |
| --- | --- |
| ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-H15PT6DS.png?sv=2026-02-06&spr=https&st=2026-11-09T17%3A09%3A35Z&se=2026-11-09T18%3A09%3A35Z&sr=c&sp=r&sig=lvjb1DYE2Svj11gEKFL5dZPopXojXIlvGEFjbTMQ50o%3D) | ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-N4ZW3V5V.png?sv=2026-02-06&spr=https&st=2026-11-09T17%3A09%3A35Z&se=2026-11-09T18%3A09%3A35Z&sr=c&sp=r&sig=lvjb1DYE2Svj11gEKFL5dZPopXojXIlvGEFjbTMQ50o%3D) |

**The **default** Toast configuration imports sales items grouped by **minor categories** (menu group in Toast). This can be changed to import sales items grouped by **major category** (sales category in Toast):**

The below image shows an example Toast menu. **Major** categories are in blue. **Minor** categories (the default polling option) are in red.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-SJVPHW9K.png?sv=2026-02-06&spr=https&st=2026-11-09T17%3A09%3A35Z&se=2026-11-09T18%3A09%3A35Z&sr=c&sp=r&sig=lvjb1DYE2Svj11gEKFL5dZPopXojXIlvGEFjbTMQ50o%3D)

**The **default** Toast configuration includes the following setting:**

| **Name** | **Description** |
| --- | --- |
| Block special request menu items | Blocks the import of 'special request' additions which prevents R365 from creating new menu item records for these requests. |

**The following **alternative** polling configurations are available for **all** POS:**

| Name | Description |
| --- | --- |
| Specify business day start time | Imports data from a specific time forward for the previous business day. |
| Trim service type name | Removes double spaces from service type category names. |
| Split sales detail | Splits a sales detail into two entries: the original and a new one with a specified name and optional category. |
| Use revenue centers | Specifies a list of Revenue Center names to import. For hospitality locations such as hotels and casinos that manage separate facility areas as distinct locations. |
| Menu item category override | Maps menu items to a specified category, overriding the POS category mapping. |
| Disable deposits import | Disables deposits polling. |
| Number of lookback days | Sets the number of days to look back when matching deposits by creation date to the import date. |
| Custom payroll ID field | Substitutes a custom field into the Payroll ID polling. |
| VSD for actual enabled | Splits shifts that span the start-of-day time and assigns them to their respective dates. |
| Allow 24 hour punches | Allows 24-hour shifts to bypass the import filter so the Labor Rules Engine can process them, and enables managers to correct punches for shifts with no clock-out recorded. |
| Observes daylight savings time | By default, locations are assumed to observe Daylight Saving Time. Set to `false` for locations that do not observe it, such as those in Arizona. |
| Offset time zone | Adds a time zone offset to correct for an inaccurate time zone on the location record. |
| Use consolidate API | Sends sales and labor data through two consolidated API endpoints as zipped and encrypted files. |

**The following **alternative** polling configurations are available for Toast POS:**

| Name | Description |
| --- | --- |
| Block deferred revenue | Blocks deferred revenue of any name from Toast summary DSS. |
| Use close time for ticket time | Sets the ticket time in R365 to the Toast ticket close time instead of the open ticket time. |
| Include excess waste order | Imports the daily $0 Toast waste order as a sales ticket and includes a 'Waste' payment type to offset the ticket amount without creating a waste log entry. |
| Menu tree | Checks all paths in Toast menu groups and uses the lowest-level result in each sequence as the category when minor categories are enabled. |
| Import open item sales categories | Uses the category name instead of the menu item name if a menu item contains "ADD" and is not a food item. |
| Open items categories | Imports open items using the name "Open" plus the category name. |
| Main item price | Imports the 'main item price' on sales details instead of the modifier price replacement. |
| Use receipt line price | Imports the 'receipt line price' for modifiers. |
| Prefix PLU to menu item | Adds the price look-up (PLU) value to menu item names. |
| Strip "amount" from redeem points | Removes the dollar amount prefix from 'Redeem Points' menu item names. |
| Ignore pay balance details | Imports house account 'Pay Balance' menu items without check number and date in display name. |
| Append fulfillment details | Appends fulfillment details to the menu item name in the format "item name - quantity unit" (for example, "Pepperoni - 10.0 Slices"). |
| Import Toast sub category in modifier group name | Imports modifier group names with subcategory names to support full modifier group imports within major categories. |
| Modifier group category override | Overrides the sales category for all items imported under a specified modifier group name to a custom sales category name. When combined with menu item category override, Menu item category override takes precedence for items that match both settings. |
| Enabled option group pricing mode modifier | Uses Toast 'OptionGroupPricingMode' when calculating modifier selections. |
| Use menu item config for modifier name | Resolves each modifier's name from its menu item configuration, replacing generic group names with the full configured name. |
| Prefix portion | Prefixes the display name of a portioned item to all subsequent modifiers when the item's selection type is "Portion." |
| Split facilitator taxes | Imports Toast 'Marketplace Facilitator Taxes Paid' as a separate line on the DSS. |
| Append tax exempt to Toast sales category | Appends ' - Tax Exempt' to the sales category of items flagged as tax exempt in Toast. |
| Applied discount concatenation | Adds discounts to the payment type. |
| Discount names | Imports value-added tax (VAT) from Digital Dining comp certificates. |
| Discounts/comps by category | Renames applied discounts using the format '{discountName} - {salesCategory}'. |
| Captured payments | Includes payments with a status of "PROCESSING". |
| Append card type to credit card fee | Adds the credit card type to the payments types 'Credit Card Fee' and 'Refund Credit Card Fee' and to the menu item 'Refund Credit Card Fee'. |
| Ignore close out imbalances for tills | Ignores the cash entry types 'CLOSE_OUT_OVERAGE' and 'CLOSE_OUT_SHORTAGE.' |
| Negate refunded tip | Imports a tip-only refund on Toast checks as a negative payment paired with the original tip, preventing a stray balancing adjustment. |
| Convert cash entry type to PIPO | Polls specific cash entry values as paid outs or paid ins. |
| Do not use reasons for cash entry PIPO | Ignores the 'reason' given in the cash entry details for paid outs and paid ins. |
| Single deposit | Combines deposit details into a single deposit. |
| Combine paid out types | Combines a list of paid out types into single imported paid out by type. |
| Fetch refund for empty sales dates | Imports refunds for days with no sales data. |
| Block process day tips for future orders | Blocks tips from importing on the process date of future order sales. |
| Disable paid outs import | In combination with "Use revenue centers," blocks paid out and paid in entries from importing to this location; use on secondary Revenue Center Split locations where paid out entries should not flow. |
| Override wage values | Uses wage override values instead of default employee wage values. |
| Import employee jobs on assignment | Imports employee jobs and pay rates when they are assigned in Toast, so they are available before the employee's first clock-in. |
| Ignore capital reporting | Ignores the "mcaRepaymentAmount" field retrieved from the Toast API. |
| Use rate limit handling | Waits for the reset time Toast returns after a rate limit (429) response and pauses all requests for that import until it passes, so retries are not rejected. |

### Add On Integrations

The Toast POS integration supports the following add on integrations:

- **[Intraday Polling](/doc/docs/intraday-polling)**

Intraday Polling is an add-on feature that collects current sales and labor data from compatible POS systems every 15, 30, or 60 minutes, depending on the POS system's capabilities, allowing the [Operations Dashboard](https://docs.restaurant365.com/doc/docs/smart-ops-release-operations-dashboard) and [R365 Intelligence Dashboards](https://docs.restaurant365.com/doc/docs/r365-intelligence-creating-a-dashboard) to display real-time performance alongside forecasted values

> [!NOTE]
> Data imported through Intraday Polling does not produce a DSS, or update other reports that pull data from the DSS. The DSS will continue to be created as scheduled with the previous day's complete data to populate these reports.
- **[Schedule Writeback](/doc/docs/scheduling-schedule-writeback)**

Schedule Writeback sends schedules that are created in R365 to the POS when published, providing a time frame for employees to clock in for their Scheduled start time. This allows locations to use the schedule enforcement features in their POS system to prevent employees from clocking in early.

> [!NOTE]
> - The scheduling feature in Toast must be enabled to use R365 Schedule Writeback. Contact your POS representative to confirm scheduling is enabled.
> - Schedule enforcement settings are managed in Toast.
- **[Till Management](/doc/docs/tills)**

Till Management provides a complete workflow from till monitoring to deposit verification, ensuring cash is properly tracked, balanced, and recorded each day.
- **[Revenue Center Splits](/doc/docs/revenue-center-split)**

Revenue Center Split enables businesses with distinct service areas — such as bars, dining rooms, or patios— to treat each area as a separate location in R365. This allows for more accurate reporting and improved sales tracking by isolating data by service area.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-AZ2U4603.png?sv=2026-02-06&spr=https&st=2026-11-09T17%3A09%3A35Z&se=2026-11-09T18%3A09%3A35Z&sr=c&sp=r&sig=lvjb1DYE2Svj11gEKFL5dZPopXojXIlvGEFjbTMQ50o%3D)
- **[Menu Item Modifier Management](/doc/docs/pos-menu-item-modifier-management) *(beta)***

The POS Menu Item Modifier Management POS integration configuration allows for menu items to be created in R365 based on the combination of parent menu items and their associated modifiers.

> [!NOTE]
> **In Beta**
> 
> Menu Item Modifier Management is currently in beta and is only available for select POS systems and customers. It is not fully supported across all environments. Contact your CSM for more information.
- **[POS Employee Management](/doc/docs/pos-employee-management-integrations) *(beta)***

POS employee management integrations send employee records from R365 to the POS. Employees created or updated in R365 are pushed to the POS with their mapped jobs and locations, reducing manual entry and aligning employee details across systems. Adding this to an existing [standard POS sales and labor integration](https://docs.restaurant365.com/doc/docs/pos-integration-overview) allows R365 to become the **source of record** for employee data in the POS.

**Creating Employees in Toast**

To successfully push R365 employee records to Toast, the [employee record](/doc/docs/employee-record) must:

  - Have a payroll ID
  - Be active
  - Be assigned to an R365 location with an active Toast POS sales & labor integration
  - Have R365 jobs which are [mapped to POS system jobs](/doc/docs/connect-a-toast-employee-management-integration#initial-mapping) (if assigning jobs)

Learn more about [creating employees with a POS employee management integration](/doc/docs/map-employees-pos-employee-management-integrations).

**Updating Employee Information**

The following [employee details](/doc/docs/employee-record) can be updated in the POS from changes made in R365:

  - Email address
  - Phone number
  - Address
  - Active/inactive status
  - Job assignments

Learn more about [syncing a POS employee management integration](/doc/docs/connect-a-toast-employee-management-integration#manually-sync-employee-details).

In Beta

This feature is in [beta](/doc/docs/user-research). Contact your CSM to learn more.

---

## Connect a Toast POS to R365

Follow these steps to connect a Toast POS to R365:

*Click steps to expand for additional information and images.*

****1)** Add the **Restaurant365** integration to 'My Integrations' in **Toast****

Search for "Restaurant365" on the 'Add Integrations' page in 'My Integrations' and click **Add Now**.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-HGVSEYDO.png?sv=2026-02-06&spr=https&st=2026-11-09T17%3A09%3A35Z&se=2026-11-09T18%3A09%3A35Z&sr=c&sp=r&sig=lvjb1DYE2Svj11gEKFL5dZPopXojXIlvGEFjbTMQ50o%3D)

> [!NOTE]
> - Leave the 'Partner Location ID' and 'Group ID' **blank**.
> - If you cannot see the 'My Integrations' section in Toast, please reach out to Toast Support.
> - If you are not currently subscribed for Toast API access, you can submit a request to Toast to subscribe.
> 
> For more information, please see the links below:
> 
> - [Toast Partner Connect](https://central.toasttab.com/s/article/Toast-Partner-Connect-Setting-Up-Integrations-with-Toast)
> - [Using Restaurant 365 with Toast](https://central.toasttab.com/s/article/Using-Restaurant365-with-Toast-POS)

****2)** Receive **location GUIDs** from **Toast****

Toast will send the 'Restaurant Toast User' and R365 an email like the one pictured below containing the required **globally unique identifiers (GUIDs)**.

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-7TLQC4AL.png?sv=2026-02-06&spr=https&st=2026-11-09T17%3A09%3A35Z&se=2026-11-09T18%3A09%3A35Z&sr=c&sp=r&sig=lvjb1DYE2Svj11gEKFL5dZPopXojXIlvGEFjbTMQ50o%3D)

****3)** Follow the instructions to [**Connect a Cloud POS**](/doc/docs/connect-a-cloud-pos).**

Include the location GUIDs from step 2 in the 'Customer Notes' field of the Location Add-On Form (step 5).

![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-2CQLO3MM.png?sv=2026-02-06&spr=https&st=2026-11-09T17%3A09%3A35Z&se=2026-11-09T18%3A09%3A35Z&sr=c&sp=r&sig=lvjb1DYE2Svj11gEKFL5dZPopXojXIlvGEFjbTMQ50o%3D)

---

### FAQ

****How do I get a new Toast employee into R365 right away?****

R365 creates the employee record in the next polling cycle after you add the employee in Toast, whether or not they've clocked in. To import a new employee sooner, repoll the latest DSS. If the DSS is less than 30 days old, delete it and R365 repolls it automatically with the most current POS data in about 30 minutes. See [Manually delete a DSS](https://docs.restaurant365.com/docs/en/manually-delete-a-dss).

****How do I fix R365 data after I correct it in Toast?****

Repoll the DSS so R365 picks up the updated data. If the DSS is less than 30 days old, delete the DSS record from the Daily Sales Summary (Classic) page. It repolls automatically in about 30 minutes. For a DSS older than 30 days, [contact R365 Support](https://help.restaurant365.net/en/support/home#contact). See [Manually delete a DSS](https://docs.restaurant365.com/docs/en/manually-delete-a-dss).

****I edited a time punch in Toast. When does R365 update?****

R365 polls labor details with a 14-day lookback window. Edits made in Toast within the last 14 days import with the next regular polling cycle, or when you repoll a DSS for a date after the adjusted business day. For example, if you edit Monday's shift on Tuesday, R365 updates the shift on Wednesday when the DSS imports, or when you repoll the Monday DSS. See [Labor integrations](https://docs.restaurant365.com/docs/en/labor-integrations).

****How does R365 handle breaks and cash tips from Toast?****

Paid breaks count toward worked hours, and unpaid breaks split the time punch into separate pairs. R365 imports declared cash tips and doesn't import undeclared cash tips. See [Labor integrations](https://docs.restaurant365.com/docs/en/labor-integrations).

****Can I change how R365 imports discounts or sales items from Toast?****

Yes, through alternative polling configurations. By default, R365 imports discounts as they're named in Toast and groups sales items by minor category (menu group in Toast). You can instead import discounts by sales category or group sales items by major category (sales category in Toast). R365 Support uses the default configuration when it sets up a new location, so [contact R365 Support](https://help.restaurant365.net/en/support/home#contact) to ask about a different one. See [Toast POS integration configurations](https://docs.restaurant365.com/docs/en/toast-pos-integration#toast-pos-integration-configurations).

****What do I do if I can't see My Integrations in Toast or don't have Toast API access?****

If you can't see the My Integrations section in Toast, contact Toast Support. If you aren't subscribed to Toast API access, submit a request to Toast to subscribe. Then follow the steps in [Connect a cloud POS](https://docs.restaurant365.com/docs/en/connect-a-cloud-pos).

POS (Point of Sale)

A system used by businesses to process sales transactions and manage customer payments. Connected to R365 through a [POS integration](/doc/docs/pos-integration-overview).

Restaurant365

API (Application Programming Interface) Interface that allows external systems to retrieve or send R365 data.

Process of importing data from the POS into R365.

The 24-hour period from a location's [start of business day time](/doc/docs/location-hours-overview#business-days-vs-calendar-days) that makes up a ‘day’ in R365. For the most accurate sales and labor reporting, a location's R365 business day should match the POS EOD.

Tips paid by the customer in cash.

Customer account used to track charges that will be billed later through invoicing.

Custom groupings assigned to menu items for product mix reporting.

A database entry that contains detailed info about an employee, including personal details and employment history.

Process of retrieving and updating prior-day POS data to replace existing DSS information.