Restaurant365 integrates with many POS systems. This article provides an overview of how integrating these systems allows data to flow freely between an organization’s POS system and the R365 platform. Learn more about POS Integration Settings.
Overview
System Requirements
If the POS system is cloud-based, there are no system requirements for the local device. Otherwise, the local device that is housing the integration must have at least .NET 4.6.1 and Internet Explorer 9+.
Setup
The POS Integration is governed by several settings in Restaurant365. These settings reside on various screens.
The following articles detail the screens where POS Integration Settings can be accessed and updated as needed:
Frequency
Integrations can be configured to run automatically each night, on-demand at the end of the day by one of the store managers, or intraday depending on the POS capabilities.
Data Flow
In most cases, data flows one-way, from the POS system to Restaurant365. Restaurant365 does not pass any information back to the POS system, except for the following systems:
PAR Brink POS
Brinks Smart Safes
Data
The integration pulls detail records from the POS into Restaurant365 each time the integration is run. Below is a sampling of the the type of data that can be transferred to Restaurant365.
Detailed sales ticket info
Menu items
Time of sale
Server
Tenders (cash, credit card, gift card, etc.)
Discounts
Coupons
Sales Tax
Etc.
Daily Totals
Guest Count
Average Check
Labor Details
Employee
Clock in time
Clock out time
Job Code
Overtime
Pay Rate
Daily Sales Summary Journal Entry
The integration creates a transaction in Restaurant365 called a Daily Sales Summary (DSS) for each day and each restaurant location. Part of the Daily Sales Summary transaction is a Journal Entry transaction that records the revenue, tenders, and discounts from the sales tickets in the POS system.
Restaurant365 maps the sales and receipt details from the POS system to General Ledger accounts using Sales Accounts and Payment Type Accounts (in Restaurant365). The Sales Accounts determine the credit side of the entry. Payment Type Accounts determine the debit side of the entry.
Journal Entry to Accrue for Hourly Labor
The integration creates a Journal Entry in Restaurant365 that accrues the labor expenses from time entries in the POS system.
R365 maps the time entry details from the POS system to General Ledger accounts using Job Titles (in R365). Job Titles determine the debit side of the accrual. The credit account (or liability) is set on the Location record.
POS Summary Integrations
POS Summary Integrations generate a Daily Sales Summary using summary data from the POS rather than individual sales ticket data. These integrations are designed primarily for accounting purposes, providing financial data without item-level or ticket-level detail. Instead, they focus on compiling data for a Daily Sales Journal Entry to support general ledger reporting and reconciliation. Operational insights, such as labor metrics or order-level details, are not included.