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.
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 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).
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 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 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 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.
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 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 R356 Support 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 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. |
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 ID for check number | Uses the Id field as the check number instead of IdEncoded, and falls back to Id when IdEncoded is null. |
Use item display price | Uses the item’s display price. |
Ignore zero sales checks | Ignores checks with zero sales. |
Use item groups | Imports the ItemGroups.Name value instead of the generic “Menu Item” name. |
Separate void by reason | Separates voids by reason using the format $"Void {reason}". |
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 toys | Enables polling of Toy Adjustments. |
Set toy price | Sets the toy price for Toy Adjustments. |
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”. |
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. |
Cleared tickets | Processes tickets that have the isCleared flag set. |
Block cleared tickets | Blocks cleared tickets when used with the Cleared tickets setting. |
Allow 24 hour punches | Allows twenty-four-hour shifts to be imported so managers can correct punches when no clock-out is recorded. |
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. |
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. |
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. |
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. |
Till deposit calculation with skim payout | Calculates over/short values using the formula (OverShort × -1) + Skims + Paidouts. |
Future order - exclude specified destination IDs | Excludes items with the specified destination IDs. |
Skip future orders | Skips all future orders that are not yet closed during future order processing. |
Add On Integrations
The Brink 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.
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.
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 provides a complete workflow from till monitoring to deposit verification, ensuring cash is properly tracked, balanced, and recorded each day.
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.
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.
POS Employee Management (beta)
POS employee management integrations send employee records from R365 to the POS. Employees created or updated in R365 are pushed to the POS with their mapped jobs and locations, reducing manual entry and aligning employee details across systems. Adding this to an existing standard POS sales and labor integration allows R365 to become 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 must:
Have a payroll ID
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 which are mapped to POS system jobs (if assigning jobs)
Learn more about creating employees with a POS employee management integration.
Updating Employee Information
The following employee details can be updated in the POS from changes made in R365:
Email address
Phone number
Active/inactive status
Job assignments
Name changes, Payroll ID changes, and location changes are not supported by Brink POS employee management integrations. A new employee record must be created and synced to reflect these changes in Brink.
Learn more about syncing a POS employee management integration.
In Beta
This feature is in beta. 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 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.
If location names are different in R365 and Brink, please provide a list of matching names when filling out the Location Add-On form.