--- title: "Brink POS Integration" slug: "brink-pos-integration-2" description: "R365 and Brink POS integration: connection requirements, data flow, and configuration details." status: "update" updated: 2026-10-22T17:26:24Z published: 2026-10-22T17:26:24Z canonical: "docs.restaurant365.com/brink-pos-integration-2" --- > ## 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. # Brink POS Integration Restaurant365 integrates with Brink 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 Brink to R365 R365 connects directly to Brink POS's cloud service through an API. Once authorized, data flows automatically into R365. Learn more about [connecting](/docs/brink-pos-integration-2#connect-a-vendor-pos-to-r365) Brink 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 Brink 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 Brink data include:** - Receipt number - Date (order close time) - Server - Service type/revenue center (destination ID) - Guest count - Menu items, including modifiers - Tax - Charge tips - Declared cash tips - Payments - Discounts - Credit card fees - Voids Learn about [alternative polling configurations](/docs/brink-pos-integration-2#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 Brink employee needs to be imported immediately, repoll the latest DSS. ****Employee records** created from Brink include:** - First, middle, and last name - Address - Phone number - Email address - Hire date - Payroll ID - Birth date ****Job records** created from Brink include:** - Job code (Job ID in Brink) - Pay rate ****Labor details** created from Brink time punches are polled with a **21 day labor lookback** window to capture updates made in the POS after the initial import.** This means that changes made in Brink to labor data from the last 21 days 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 Brink on Tuesday, the shift in R365 will automatically update on Wednesday when the DSS imports, or by repolling the Monday DSS. ****Labor detail**s created from Brink time punches include **breaks**.** - **Paid breaks** count toward worked hours - **Unpaid breaks** cause the time punch to be split into separate pairs - **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 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 ### Brink POS Integration Configurations R365 Support uses the default polling configuration when setting up a new location. If other Brink 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** Brink configuration imports discounts as they are named in the POS.** The integration can alternatively be configured to import **discounts by category**. **The **default** Brink configuration includes the following setting:** | **Name** | **Description** | | --- | --- | | Always import labor | Imports labor regardless of sales. | **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 Brink POS:** | Name | Description | | --- | --- | | Net vs gross sales intraday | Enables both net and gross calculations in the intraday data flow so the Ops Dashboard can use either value. | | Exact guest count, allowing 0 | Allows zero as a valid guest count. | | Use ID for check number | Uses the Id field as the check number instead of IdEncoded, and falls back to Id when IdEncoded is null. | | Ignore zero sales checks | Ignores checks with zero sales. | | Separate void by reason | Separates voids by reason using the format $"Void {reason}". | | Cleared tickets | Processes tickets that have the isCleared flag set. | | Block cleared tickets | Blocks cleared tickets when used with the Cleared tickets setting. | | Use POS value for net and gross sale for sales order | Uses Daily Sales Summary (DSS) mapping to determine gross or net ticket sales and supports POS-provided values when enabled. | | Add PLU to item name | Prepends the item's PLU to the item name. | | Concatenate combo | Concatenates the items that make up the choices in a combo meal. | | Use item display price | Uses the item's display price. | | Use item groups | Imports the [ItemGroups.Name](http://ItemGroups.Name) value instead of the generic "Menu Item" name. | | Use toys | Enables polling of Toy Adjustments. | | Set toy price | Sets the toy price for Toy Adjustments. | | Discounted toy adjuster | In combination with 'Set toy price', subtracts item-level discounts from the configured toy price before importing toy SalesDetail entries. Use instead of 'Use toys' when toy items may have discounts applied at the POS. | | Import gift card category by revenue center | Imports gift cards based on Revenue Center instead of the hard-coded "Gift Card" category, and falls back to the default category when no match is found. | | Ignore none prefix for donotdelete menu item | Prevents importing the "None - do not delete" modifier name for modifiers with modifier ID zero, resulting in menu item names such as "Coke" instead of "None - Do Not Delete Coke". | | Append " - tax exempt" | Appends " - Tax Exempt" to the item category when applicable. | | Breakdown tax and display details | Breaks tax totals into category-level sales details per ticket and applies an offset adjustment when required. | | Apply MPF prefix to third-party taxes | In combination with 'Breakdown tax and display details,' prefixes 'MPF' to the name of each tax paid by a third party on the Daily Sales Summary. | | Use virtual tills | Creates an additional virtual till with an amount equal to the sum of cash payments where POSTILLID is null, and replaces POSTILLID = null with POSTILLID = "Virtual Till". | | Use prepaid card types | Sets tenders with the tender type "App Prepaid Card Type" to use the name from the payment data name/value pair. | | Till deposit calculation with skim payout | Calculates over/short values using the formula (OverShort × -1) + Skims + Paidouts. | | Use order deposit reversal | Processes reversed deposits (IsReversal = true) as refund orders, imports only the refund data, and ensures proper offsets for both the refund payment and the refunded "Future Deposit" sales detail. | | Deposit refund prefix | Prepends 'Refund' to deposit-related tender and category names for reversed future order deposits, enabling accurate account mapping in R365. | | Void reversed deposits | In combination with 'Deposit refund prefix,' skips voided future orders where all deposits have been reversed, preventing them from being imported as refunds. Orders where only some deposits are reversed are still imported, with the reversed deposit pairs excluded from payment mapping. | | Future order - exclude specified destination IDs | Excludes items with the specified destination IDs. | | Skip future orders | Skips future orders that are not yet closed during future order processing. | | Skip all future orders | Skips every future order, open or closed, when importing sales so the order date does not create a duplicate ticket alongside the deposit. | | Future order cancellation lookback days | Sets the number of prior business days (0–7) to search for future orders that were placed on an earlier date and cancelled on the current import date, so that deposit reversals are recorded on the correct date. | | Allow 24 hour punches | Allows twenty-four-hour shifts to be imported so managers can correct punches when no clock-out is recorded. | | Refund category prefix | Prepends "Refund - " to the sales category of voided or refunded items and modifiers so refunds can map to a separate GL account. | ### Add On Integrations The Brink 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. - **[Schedule Writeback](/doc/docs/scheduling-schedule-writeback)** Schedule Writeback sends schedules that are created in R365 to the POS when published, providing a time frame for employees to clock in for their Scheduled start time. This allows locations to use the schedule enforcement features in their POS system to prevent employees from clocking in early. > [!NOTE] > - The scheduling feature in Brink must be enabled to use R365 Schedule Writeback. Contact your POS representative to confirm scheduling is enabled. > - Schedule enforcement settings are managed in Brink. - **[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. - **[Revenue Center Splits](/doc/docs/revenue-center-split)** Revenue Center Split enables businesses with distinct service areas — such as bars, dining rooms, or patios— to treat each area as a separate location in R365. This allows for more accurate reporting and improved sales tracking by isolating data by service area. ![](https://cdn.us.document360.io/5c9d1111-0c69-4e96-8910-d7f2750fdc9d/Images/Documentation/image-AZ2U4603.png?sv=2026-02-06&spr=https&st=2026-10-31T09%3A58%3A24Z&se=2026-10-31T10%3A58%3A24Z&sr=c&sp=r&sig=nyyZGCeJJyG2yqzQ1xcufzLYzN34Z42xEFNIdrdKS7k%3D) - **[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. - **[POS Employee Management](/doc/docs/pos-employee-management-integrations) *(beta)*** POS employee management integrations send employee records from R365 to the POS. The integration pushes employees you create or update in R365 to the POS with their mapped jobs and locations. Adding this to an existing [standard POS sales and labor integration](https://docs.restaurant365.com/doc/docs/pos-integration-overview) makes R365 the **source of record** for employee data in the POS. **Creating Employees in Brink** To successfully push R365 employee records to Brink, the [employee record](/doc/docs/employee-record) must: - Have a payroll ID - > [!NOTE] > This will be the **PIN** used by the employee to clock in with Brink. If the R365 payroll ID is updated, the Brink PIN **will not** change when the integration syncs. - Be active - Be assigned to an R365 location with an active Brink POS sales & labor integration - Have R365 jobs [mapped to POS system jobs](/doc/docs/connect-a-toast-employee-management-integration#initial-mapping) (if assigning jobs) Learn more about [creating employees with a POS employee management integration](/doc/docs/map-employees-pos-employee-management-integrations). **Updating Employee Information** The integration updates the following [employee details](/doc/docs/employee-record) in the POS when changed in R365: - Email address - Phone number - Active/inactive status - Job assignments > [!NOTE] > Brink POS employee management integrations do **not** support name changes, Payroll ID changes, or location changes. A new employee record must be [created and synced](/doc/docs/map-employees-pos-employee-management-integrations#create-a-new-employee-record) to reflect these changes in Brink. Learn more about [syncing a POS employee management integration](/doc/docs/connect-a-toast-employee-management-integration#manually-sync-employee-details). In Beta This feature is in [beta](/doc/docs/user-research). Contact your CSM to learn more. --- ## Connect a Brink POS to R365 Follow these steps to connect a Brink POS to R365: *Click steps to expand for additional information and images.* ****1)** Email [brinkapitokenrequest@partech.com](mailto:brinkapitokenrequest@partech.com) and request authorization for R365 to use your Brink Tokens.** In the email, request that Brink authorize and send R365 the location API tokens and Brink API URL. ****2)** Follow the instructions to [**Connect a Cloud POS**](/doc/docs/connect-a-cloud-pos).** If location names are different in R365 and Brink, please provide a list of matching names when filling out the Location Add-On form.