--- title: "POSitouch POS Integration" slug: "positouch-pos-integration" description: "R365 and POSitouch integration: connection requirements, data flow, and configuration details." updated: 2026-07-01T18:47:37Z published: 2026-07-01T18:47:37Z canonical: "docs.restaurant365.com/positouch-pos-integration" stale: true --- > ## 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. # POSitouch POS Integration Restaurant365 integrates with POSitouch 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 POSitouch to R365 R365 uses an application installed on a local POSitouch POS computer or back-office server to poll and transmit data. This requires the local device to remain powered and connected to the internet for polling. Learn more about [connecting](/doc/docs/vendor-pos-integration-7#connect-a-positouch-pos-to-r365) POSitouch 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 POSitouch 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 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 POSitouch data include:** - Receipt number - Date - Server - Service type (cost center) - Guest count - Menu items, including modifiers - Tax - Charge tips - Payments - Discounts Learn about [alternative polling configurations](/docs/positouch-pos-integration#vendor-pos-integration-configurations) which change the way sales data is imported below. - **Paid outs** and **paid ins** are imported to R365. - **Deposits** entered in the POS are imported to R365. ### Labor Data 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 the POS whether or not they have clocked in.** If a new POSitouch employee needs to be imported immediately, repoll the latest DSS. ****Employee records** created from POSitouch include:** - First and Last name - Address - Phone number - POS ID (Employee number) - Hire date - Payroll ID (Alt number) ****Job records** created from POSitouch include:** - Job code - Pay rate **Labor details created from POSitouch time punches are imported **per business day with no labor lookback window**.** Each import reads the local POSitouch labor files for the specific business date being polled and brings in whatever data is in those files at that time. Changes made in POSitouch after the initial import are **not** automatically imported on subsequent days. To capture updates to a prior business day, repoll the DSS for that exact date. For example, if a shift from Monday is edited in POSitouch on Tuesday after Monday's DSS has already imported, repolling the Monday DSS will update the shift in R365. - Declared tips are imported to R365. ### 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 ### POSitouch POS Integration Configurations R365 Support uses the default polling configuration when setting up a new location. If other POSitouch 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** POSitouch configuration imports items using the **Sales** category.** Alternatively, the integration can be configured to use either the **Major** or **Minor** category. **The **default** POSitouch configuration imports tips entered in the POS as paid outs.** Alternatively, the integration can be configured to exclude tips from paid out totals. **The **default** POSitouch configuration imports combined taxes.** Alternatively, the integration can be configured to break out taxes by tax number. **The **default** POSitouch configuration imports discounts individually.** Alternatively, the integration can be configured to bundle discounts by sales category. **The **default** POSitouch configuration excludes tax exempt sales.** Alternatively, the integration can be configured to include tax exempt sales. **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 POSitouch POS:** | Name | Description | | --- | --- | | Zero guest count | Accepts tickets with a guest count of 0. | | Extended item descriptions | Adds an extra description field to imported menu items. | | Split tax by category | Splits taxes into four tax categories, using category names defined in Names.dbf. | | Ignore taxes for comps | Excludes tax amounts from fully comped items, including comps that import as menu items or create balancing adjustments. | | Exclude comps from sales details | Excludes comps that import as a sales category from sales detail reporting to prevent balancing issues. | | Deduplicate discount payments | Removes duplicate discount entries when the same discount name and amount appear more than once on a check, preventing balance adjustments. | | Menu price for negative combo items | In combination with Deduplicate discount payments, uses the absolute menu price of negative-price combo items to calculate the discount payment amount, eliminating balancing adjustments caused by these items being excluded from the sales detail. | | Modify charge types | Adds the customer name to house account charges for configured payment categories such as the "HOUSE CHG" payment category. | | Specify cash drawers | Identifies specific cash drawers and routes deposits according to the configured drawers. | | Override DBF folder location | Overrides the default DBF folder location for imports and uses the specified folder path instead. | ### Add On Integrations The POSitouch POS integration supports the following add on integrations: - **[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. --- ## Connect a POSitouch POS to R365 Follow the instructions to [Connect a Local Install POS](/doc/docs/connect-a-local-install-pos).