The Sales Integration allows R365 to bring in sales data from the POS, such as:
Menu items
Time of sale
Server
Tenders (cash, credit card, gift card, etc.)
Discounts
Coupons
Sales Tax
Paid Outs
Deposits
Revenue Centers
The Sales data available varies by POS. Please contact your CSM or R365 Support for additional information on what Sales data is available for your POS.
Sales Tickets
The integration ingests daily sales data and creates a sales ticket record for each transaction at that location on a single day.
Sales ticket records include identifying information such as:
Receipt number
Date
Time
Location
Server
Service type
Sales integrations create employee records in R365 in order to match 'Server' data to the sales ticket record. This also supports scheduling when there is no labor integration.
The sales details imported with each ticket include:
Quantities sold
Sales amounts
Tax
Tip
Payment details include:
All cash, credit card and gift card payments
All other electronic payments (such as payments tendered through third-party delivery services)
Discounts
Comps
Voids
Sales and Payment Type Accounts
Details from the sales ticket create and are automatically mapped to Sales Accounts and Payment Type Accounts.
By default, sales accounts combine the POS category of the menu item with the service type (for example, 'Burgers - Dine In'). When revenue center data is available in the POS, the Sales Account Import Type can be adjusted to include either or both the service type and revenue center in the account name.
Some POS systems include different levels of categorization, and, depending on the POS, R365 may be able to switch the category level used to generate sales accounts. To learn more, contact R365 Support.
Payment type accounts match the name of the payment on the sales ticket and are manually assigned to the correct payment group (for example, cash, discount, House Account, etc.). When revenue center data is available in the POS, the Payment Type Import Type can be adjusted to include this in the account name.
Daily Sales Summary
The integration creates a Daily Sales Summary (DSS) for each day at a specific restaurant location. It represents the complete record of a location’s daily sales and serves as the foundation for accounting entries, reporting, and analysis within R365.
Paid Outs and House Accounts
The transactions section of the DSS displays the breakdown of comps and promotions, as well as paid outs and house account activity. Paid out types are mapped to gl accounts, and the POS Track Paid Out system setting can be used to automatically map regular paid out types.
House account transactions are mapped to customer records to track invoices and payments.
Deposits
Deposits entered in the POS appear on the DSS and are subtracted from the total amount of cash payments recorded to calculate the cash over/short line item.
If used, a petty cash account can be configured in the location record settings to incorporate cash brought in or cashed out of petty cash.
DSS Journal Entry
Sales and payment type accounts are in turn mapped to General Ledger accounts in R365 using the POS Mapping Tool. Daily sales data is recorded in the DSS Journal Entry, where sales accounts determine the credit side of the entry and payment type accounts determine the debit side of the entry.
Customization
Sales integrations can be customized to control how data is imported and reported in R365 through a combination of system- and location-specific settings, and add on integrations like Till Management and Revenue Center Splits. Learn more about add on integrations and POS integration setup.
Sales Summary Integration
Some POS systems only provide summary-level information. In these cases, POS Summary Integrations use aggregated financial data from the POS to create a DSS designed for accounting and reconciliation. Summary integrations do not include item- or order-level detail, limiting them to financial rather than operational reporting.
Labor Integrations
The Labor Integration allows R365 to bring in Labor data from the POS, such as employee details, job codes and pay rates, and clock-in and clock-out times. Labor integrations can operate independently from sales integrations. Labor and sales data may originate from the same POS or from separate systems entirely.