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.
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 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).
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.
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 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.
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 in order to transfer the updated data to R365.
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 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 POSitouch POS:
Name | Description |
|---|---|
Extended Item Descriptions | Adds an extra description field to imported menu items. |
Override DBF Folder Location | Overrides the default DBF folder location for imports and uses the specified folder path instead. |
Specify Cash Drawers | Identifies specific cash drawers and routes deposits according to the configured drawers. |
Ignore Taxes For Comps | Excludes tax amounts from fully comped items, including comps that import as menu items or create balancing adjustments. |
Zero Guest Count | Accepts tickets with a guest count of 0. |
Modify Charge Types | Adds the customer name to house account charges for configured payment categories such as the “HOUSE CHG” payment category. |
Split Tax By Category | Splits taxes into four tax categories, using category names defined in Names.dbf. |
Exclude Comps From Sales Details | Excludes comps that import as a sales category from sales detail reporting to prevent balancing issues. |
Add On Integrations
The POSitouch POS integration supports the following add on integrations:
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.
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.