Description: Review System Settings affecting End of Day in QSR & Delivery below. All of the settings below are accessed by logging into the POS system and navigating to Admin > Config Tools, and selecting System + Station Settings.

System Settings: Business

There are two settings underneath the Business section that affect the End of Day, Sales, Cash Drawer reports, and employee sales and labor reporting. These settings are shown below and involve how the system handles an employee who has not clocked out as well as checks left open when the End of Day is performed. These settings should always be set to 0 = No.

If either of these options are left on, you could have inaccurate reporting and no way to prove otherwise. If these settings are set to option 2 = Prompt, when the EOD is run, any employee currently clocked in or open checks will prompt the EOD user to handle them or skip them. With the prompt, 99% of the time, employees click on the Skip button, which allows them to pass through the screen. The major issue here is how it affects reporting. QSR migrates all current-day data/sales over to the History database once the EOD is performed. If the option is set to 2 = Prompt, it allows the user to skip clocking employees out who are still clocked in. If you proceed without actually clocking them out, the system will drop that employee’s shift for that day and any of their server reports that they may have had.

Checks are to be closed before the EOD is run, and if they are left open, and the system is set to 2 = Prompt it will alert the user but allow them to continue. If you continue with open checks, those checks will be dropped from the system for that current business date, making the sales inaccurate because it will show less than it should. The payments for these tickets/checks, however, will still report to the Batch/Cash Drawer.

End Of Day “Business” > Employees

0 = No: this means that they will not be able to proceed without first closing checks or clocking employee out (SHOULD BE SET)
1 = Yes: this means it will allow the user to proceed without even letting them know there are open checks or employees clocked in (never use this)
2 = Prompt: this will alert the EOD user that there are open checks/clocked-in employees, but it allows them to pass through (should not be set)

End Of Day “Business” > Checks

0 = No: this means that they will not be able to proceed without first closing the check or clocking the employee out (SHOULD BE SET)
1 = Yes: this means it will allow the user to proceed without even letting them know there are open checks or employees clocked in (never use this)
2 = Prompt: this will alert the EOD user that there are open checks/clocked-in employees but allows them to pass through (should not be set)

System Settings: Cash Drawers

There is one setting under the Cash Drawer header in the System Settings called Force Check Payment Before Settlement. This setting is almost always, if not always, set to Yes. If this is not set to Yes, then a person may settle the cash drawer with open checks. These open checks are then not accounted for in the sales reports and can cause problems with losing the payments.

However, if there was a credit card payment on an Open ticket that did not get closed/fully paid before settling the drawer, the Credit Card payment will be in the batch but not accounted for in the sales for the day. As described above, similarly, the ticket will be dropped at the EOD, and no sales are reported, but the payments (if any) will be accounted for.

Force Check Payment Before Settlement

Yes: this will require all payments to be settled before the drawer can be settled (SHOULD BE SET)
No: this will allow you to settle the cash drawer without first settling the payments/tips (usually, do not use this)

System Settings: Drivers

This setting dictates how the driver handles the ‘Cash Due Restaurant’ value on the Driver report. Because QSR assumes that the credit card tips are removed from the Cash Due Restaurant and paid to the employee at the end of their shift, this value will be removed from any cash delivery payment which was taken by the driver during their shift.

By default, this setting is turned On. This setting tells the machine that once the driver is settled, the money that he/she owes the restaurant will be migrated to the cash drawer once the driver is settled. This setting is important to understand because it amends the value of the cash drawer. The cash drawer should be settled after the Drivers and/or Servers have all been settled. The next section will speak about Table Service and settling servers.

DriverDropToCashDrawer

No: ‘Cash Due Restaurant’ will not be amended to the cash drawer
Yes: ‘Cash Due Restaurant’ will be amended to the cash drawer, changing the drawer’s expected cash total

System Settings: Table Service

This setting dictates how settling the server handles the ‘Cash Due Restaurant’ value on the Server report. Because QSR assumes that the credit card tips are removed from the Cash Due Restaurant and paid to the employee at the end of their shift, this value will be removed from any cash payment which was taken by the server during their shift. By default, this setting is turned On.

This setting tells the machine that once the server is settled, the money that he/she owes the restaurant will be migrated to the cash drawer once the server is settled. This setting is important to understand because it amends the value of the cash drawer. The cash drawer should be settled after the Drivers and/or Servers have all been settled.

ServerDropToCashDrawer

No: ‘Cash Due Restaurant’ will not be amended to the cash drawer
Yes: ‘Cash Due Restaurant’ will be amended to the cash drawer, changing the drawer’s expected cash total

System Settings: Security

There are two system settings under the Security header which can affect how the Cash Drawer is managed. You may prefer to log the ability to account for overages and shortages of your cash drawers. There is one setting here that directly affects how that is handled. By default, users typically have this setting set to “0” (No), which shows no logging of the overages and shortages. Depending on what you want, you may need to set it to 1, 2, or 3. The other security option is the logging of Cash Drawer activity, which should be turned on.

Force Enter of Over/Short

0 = No: This will not trigger the Over/Short logging at all
1 = Cash Drawers: This will prompt the user to enter values after settling the cash drawer(s)
2 = End Of Day: This will prompt the user to enter values during the End of Day process
3 = C/D and EOD: This will prompt the user to enter values when settling the cash drawer(s) AND during the End of Day process

Log Cash Drawer Activity

Yes: Turns all cash drawer activity logging on
No: Turns all cash drawer activity logging off

What Can We Help You With?

System Settings Affecting End of Day in QSR & Delivery