--- title: "Sicom POS Integration" slug: "sicom-pos-integration" description: "R365 and Sicom POS integration: connection requirements, data flow, and configuration details." updated: 2026-06-03T22:31:57Z published: 2026-06-03T23:16:58Z canonical: "docs.restaurant365.com/sicom-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. # Sicom POS Integration 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](/doc/docs/pos-integration-overview). ## 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](/doc/docs/sicom-pos-integration#connect-a-sicom-pos-to-r365) 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)](/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 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](/docs/sicom-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 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. ****Labor details** created from Sicom time punches do not include **breaks** by default.** Learn more about [alternative polling configurations](/doc/docs/sicom-pos-integration#sicom-pos-integration-configurations) to import breaks below. ### 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 ### 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 | | --- | --- | | Sales v2 | Calculates sales using the Sicom sales V2 logic. | | 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. | | Include toy adjustments | Polls toy adjustments from BK locations. | | Import waste modifiers | Imports modifiers attached to waste items on waste tickets to keep tickets in balance. | | Enable non-taxable accrual for tax exempt sales items | Enables non-taxable accrual for tax-exempt sales items. | | Zero out deleted discount | Blocks deleted discount amounts from affecting balancing adjustments. | | Use discount quantity | Calculates discount amounts using the discount quantity. | | Import kiosk payments | Allows the import of kiosk payments. | | Block parent kiosk tenders | Imports child kiosk tenders and excludes parent kiosk tenders. | | Import without deleted tenders | Imports tickets without deleted tenders to prevent balancing adjustments created by voided or deleted tenders. | **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 Sicom POS:** | Name | Description | | --- | --- | | Exclude overring transactions | Excludes overring transactions from import. | | Use kiosk service type | Sets the sale's service type to Kiosk based on matching terminal-level kiosk configuration. | | 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. | | Allow extended polling | Polls dates earlier than the standard 30-day lookback period. | | Skip transaction type | Filters specified transaction types from sales detail mapping during import, preventing non-revenue items from creating check imbalances. | | 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. | | Import promos instead of discounts | Imports transactions with type ID "18" as promos instead of labeling them as discounts. | | 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. | | Import gl account for paid out descriptions | Imports paid out descriptions using the Sicom GL Account value. | | 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. | | SSN as payroll ID | Uses the employee SSN value to populate the payroll ID. | | 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. | | | | ### Add On Integrations The Sicom POS integration supports the following add on integrations: - **[Intraday Polling](/doc/docs/intraday-polling)** 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](https://docs.restaurant365.com/doc/docs/smart-ops-release-operations-dashboard) and [R365 Intelligence Dashboards](https://docs.restaurant365.com/doc/docs/r365-intelligence-creating-a-dashboard) to display real-time performance alongside forecasted values > [!NOTE] > 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](/doc/docs/tills)** Till Management provides a complete workflow from till monitoring to deposit verification, ensuring cash is properly tracked, balanced, and recorded each day. - **[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 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: ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-JG48W5FN.png?sv=2026-02-06&spr=https&st=2026-11-09T20%3A57%3A36Z&se=2026-11-09T21%3A57%3A36Z&sr=c&sp=r&sig=zQW3Eyq2w6M5vlkCFNrm35dpTZfGLMD8XUSog9h8vKI%3D) ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-WYJTFRYJ.png?sv=2026-02-06&spr=https&st=2026-11-09T20%3A57%3A36Z&se=2026-11-09T21%3A57%3A36Z&sr=c&sp=r&sig=zQW3Eyq2w6M5vlkCFNrm35dpTZfGLMD8XUSog9h8vKI%3D) ****2)** Follow the instructions to [**Connect a Local POS**](/doc/docs/connect-a-local-install-pos).** Include API Key(s) from step 1 in step 5 when submitting the Location Add-On form.