Restaurant365 integrates with Sicom 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 Sicom to R365
R365 uses an application installed on a local Sicom 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 Sicom 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 Sicom 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 Sicom data include:
Receipt number
Date
Service type (Dine In, Take out, Drive-Thru, Delivery)
Guest count (calculated at 1 sale = 1 guest)
Menu items, including modifiers
Tax
Payments
Discounts
Voids
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 Sicom employee needs to be imported immediately, repoll the latest DSS.
Employee records created from Sicom include:
Full name (first, middle, and last)
Address
Phone number
POS ID number
Payroll ID number
Active/Inactive status
Job records created from Sicom include:
Job title
Job code
Labor details created from Sicom time punches are polled with a 30 day labor lookback window to capture updates made in the POS after the initial import. However, Sicom only stores up to the last 2 pay periods of labor data. Once a new pay period starts, only the previous 14 days of labor are retrievable from Sicom.
This means that changes made in Sicom to labor data from the current and previous pay period 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 Sicom on Tuesday, the shift in R365 will automatically update on Wednesday when the DSS imports, or by repolling the Monday DSS.
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
Sicom POS Integration Configurations
R365 Support uses the default polling configuration when setting up a new location. If other Sicom 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 Sicom configuration includes the following settings:
Name | Description |
|---|---|
Import Kiosk Payments | Allows the import of kiosk payments. |
Block Parent Kiosk Tenders | Imports child kiosk tenders and excludes parent kiosk tenders. |
Enable Non-Taxable Accrual For Tax Exempt Sales Items | Enables non-taxable accrual for tax-exempt sales items. |
Include Toy Adjustments | Polls toy adjustments from BK locations. |
Import Without Deleted Tenders | Imports tickets without deleted tenders to prevent balancing adjustments created by voided or deleted tenders. |
Zero Out Deleted Discount | Blocks deleted discount amounts from affecting balancing adjustments. |
Import Waste Modifiers | Imports modifiers attached to waste items on waste tickets to keep tickets in balance. |
Import Overring Tickets | Imports overring items and payments to keep tickets and validations accurate. |
Convert Value Meals To Negative Sales | Converts value meals to negative sales items instead of positive payments. |
Sales V2 | Calculates sales using the Sicom sales V2 logic. |
Use Discount Quantity | Calculates discount amounts using the discount quantity. |
The following alternative polling configurations are available for Sicom POS:
Name | Description |
|---|---|
Import Gl Account For Paid Out Descriptions | Imports paid out descriptions using the Sicom GL Account value. |
Import Promos Instead Of Discounts | Imports transactions with type ID “18” as promos instead of labeling them as discounts. |
Define Menu Items Based On PLU | Prepends the PLU number to the menu item short name to define menu items based on PLU instead of by name. |
Exclude Overring Transactions | Excludes overring transactions from import. |
Allow Breaks To Import | Imports employee break data. |
Import Breaks As Shift | Imports punches marked as a “break” as a worked shift. |
Check Hourly Sales And Labor Details | Verifies labor detail minutes against hourly sales minutes. |
Use Kiosk Service Type | Sets the sale’s service type to Kiosk based on matching terminal-level kiosk configuration. |
GZ File De Compressor | Decompresses and processes compressed GZ data files. |
File ID | Uses the second part of the data file name after the import date as the file ID. |
Folder Path | Uses a specifically configured folder path to locate Sicom data files. |
Allow Extended Polling | Polls dates earlier than the standard 30-day lookback period. |
SSN As Payroll Id | Uses the employee SSN value to populate the payroll ID. |
Zero Dollar Till Imports | Skips importing tills whose amounts equal zero. |
Use Alternate Tills | Uses the value from plu_id 3 in inserted tills as the till amount. |
Handle Recycled Check Numbers From Third Parties | Imports duplicated check numbers by appending “ - {incremented number}” to create a new unique check number. |
Zero Out Waste | Sets waste check amounts to $0 to prevent balancing adjustments. |
Add On Integrations
The Sicom POS integration supports the following add on integrations:
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 and R365 Intelligence Dashboards to display real-time performance alongside forecasted values
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.
Till Management provides a complete workflow from till monitoring to deposit verification, ensuring cash is properly tracked, balanced, and recorded each day.
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 Sicom POS to R365
Follow these steps to connect a Sicom POS to R365:
Click steps to expand for additional information and images.
1) Obtain the Sicom API Key for each location.
The API Keys from Sicom can be located on the Sicom web site:
2) Follow the instructions to Connect a Local POS.
Include API Key(s) from step 1 in step 5 when submitting the Location Add-On form.