101 - BreakPoint End-of-Shift Cashout
The purpose behind CASHOUT1 and CASHOUT2 is to provide simple and easy-to-use end-of-shift routines for cashiers and managers. By programming these keys to perform a specific sequence of operations, system operators can enforce a sophisticated end-of-shift procedure without concern for excessive cashier training or operator mismanagement.
There are two separate cashout operations which can be programmed independently of each other, to allow for two different end-of-shift operations. This will accomodate differences between a midday end-of-shift cashout operation and an end-of-day cashout operation, for example.
The steps which can be programmed for the End of Shift Cashout Operations are as follows:
- Mandatory Tender Declaration: This step involves the declaring of actual in-drawer tender counts prior to report printing, usually for the purpose of enforcing operator integrity. Operators are prompted for tender declarations as the first step in the Cashout operation.
- Credit/Debit Authorization: This step includes printing of CR/DB transaction listings, force posting of unposted transactions, Summary Report printing, and Detail Report Printing, to facilitate proper end of shift balancing of all online Credit/Debit Authorization processing.
- Chain Reporting: This step offers execution of either CHAIN1, CHAIN2, or both, as the final step in the cashout opertion.
- System Logoff: This step includes the closing of all files, logging off of all clerks, and presenting of the CLOSED status screen message.
Step 1: Mandatory Tender Declaration
To program Mandatory Tender Declaration, operators must be concerned with the following system flags:
- TS 23 - Mandatory Tender Declaration during Cashout.
- GS 199 - Perform Mandatory Tender Declarations with Cashout 1.
- GS 210 - Perform Mandatory Tender Declarations with Cashout 2.
The cashier will be presented with a Mandatory Tender Declaration window for each of the tenders for which the flag has been set. Once the Mandatory Tender Declaration(s) has been entered by the cashier, the system will proceed to the next step of the Cashout operation.
Step 2: Credit/Debit Authorization
The Credit/Debit Authorization finalization procedure has several steps, each of which is invoked optionally by system flag. These flags permit the system operators to dictate which of these steps will be included with each Cashout operation.
To program Credit/Debit Authorization end-of-shift finalization options, operators must be concerned with the following system flags:
- GS 200 - Print Posted CR/DB Listing with Cashout 1.
- GS 201 - Print Unposted CR/DB Listing with Cashout 1.
- GS 202 - Perform CR/DB Force Posting with Cashout 1.
- GS 203 - Print CR/DB Summary Report with Cashout 1.
- GS 204 - Print CR/DB Detail Report with Cashout 1.
- GS 205 - Print CR/DB Detail Report on Misbalance Only with Cashout 1.
- GS 211 - Print Posted CR/DB Listing with Cashout 2.
- GS 212 - Print Unposted CR/DB Listing with Cashout 2.
- GS 213 - Perform CR/DB Force Posting with Cashout 2.
- GS 214 - Print CR/DB Summary Report with Cashout 2.
- GS 215 - Print CR/DB Detail Report with Cashout 2.
- GS 216 - Print CR/DB Detail Report on Misbalance Only with Cashout 2.
Each of these flags invokes a different step in the Credit/Debit Authorization finalization procedure.
Global System Flags #200 and #211 produce a printed listing of CR/DB transactions recorded by BreakPoint which have been successfully posted during that shift.
Global System Flags #201 and #212 produce a printed listing of CR/DB transactions recorded by BreakPoint which remain unposted from that shift and may require force posting. These reports are internal to BreakPoint only, produced from internal maintenance files of posted and unposted CR/DB transaction entries recorded by BreakPoint. They are not required to be printed but are offered as an option to ensure that operators are able to balance figures stored by BreakPoint to figures reported by the Credit/Debit Authorization host system, right down to the individual transaction details.
Global System Flags #202 and #213 determine if the unposted CR/DB transactions are to be force posted during the Cashout operation. If these flags are set to YES, then records found in the Unposted Transaction File being maintained by BreakPoint will be force posted to the Credit/Debit Authorization host system. As with all CR/DB posting, a report will be produced indicating the success or failure of that force posting operation. If the posting is successful, the Unposted Transaction File will be cleared for the next shift. Any Unposted Transaction File which is not successfully posted during the Cashout operation will be retained until the next force posting operation is performed.
Global System Flags #203, 204, 205, 214, 215, and 216 control the printing of various reports which can be requested from the Credit/Debit Authorization host system. These reports are normally requested to permit end-of-shift balancing of the cashier totals to the reported totals of the host system. If these flags are set to YES, then the specified report will be requested from the host system and printed. In the case of the Detail Report, it may be not printed at all, by setting both flags #204 and #205 to NO, it may be printed all of the time, by setting flag #204 to YES and #205 to NO, or printed only in the case that the cashier totals stored in BreakPoint do not match the reported totals of the host system, by setting flag #204 to YES and #205 to YES.
Step 3: Chain Reporting
The Chain Report routines permit a sequence of steps to be programmed into a single report operation, including a variety of report printing, clearing of totals, and producing of ASCII file data. There are a series of system flags which must be programmed to determine what operations will be performed for CHAIN1 or CHAIN2, as outlined in the Technical Reference Newsletter entitled Chain Report Programming.
To program Cashout operation Chain Report options, operators must be concerned with the following system flags:
- GS 207 - Perform CHAIN1 Report Operation with Cashout 1.
- GS 208 - Perform CHAIN2 Report Operation with Cashout 1.
- GS 218 - Perform CHAIN1 Report Operation with Cashout 2.
- GS 219 - Perform CHAIN2 Report Operation with Cashout 2.
If you wish to have the CHAIN1 Report operation performed with the Cashout procedure, set flags #207 and/or #218 to YES. Accordingly, if you wish to have the CHAIN2 Report operation performed with the Cashout procedure, set flags #208 and/or #219 to YES. Both flags may be set to YES, such that CHAIN1 will be immediately followed by CHAIN2 and both sets of reports will be produced with the Cashout procedure, or both set to NO, in which case no reports will be printed.
Step 4: System Logoff
The System Logoff includes the closing of system files and presenting of the CLOSED status message on the screen and rear-pole display. This step is intended to notify future operators of the BreakPoint workstation that it has been properly closed off by means of a Cashout operation. Any person wishing to operate the BreakPoint workstation after this point would be required to perform a proper Clerk Logon.
The System Logoff is the final step of the Cashout operation. From the perspective of the cashier, a single key is pressed to activate the Cashout operation, mandatory tender declarations are entered (if applicable), a series of reports are printed, and the system presents the CLOSED message. Other than the mandatory tender declarations, there are no entries or decisions required of the cashier during the Cashout operation.
From the perspective of the store operators, there may be several other functions which are being performed which are invisible to the cashier. Subsequent to the entering of the mandatory tender declarations, all of the finalization of the Credit/Debit Authorization System will have processed according to the settings of the system flags. As well, all report printing, totals clearing, and ASCII file generation will have been performed, so that the BreakPoint System will have concluded any and all preparations required for overnight processing. And finally, BreakPoint will have closed all files and logged out all clerks as it presents the final CLOSED status rear-pole and screen-save messages.
The Cashout operations may be programmed to require Manager Authorization. To invoke Manager Authorization control over the Cashout operations, operators must be concerned with the following flags:
- GS 209 - Cashout 1 Operation Under Manager Authorization
- GS 220 - Cashout 2 Operation Under Manager Authorization
If these flags are set to YES, the cashier will be required to enter an acceptable Manager Authorization before proceeding with the Cashout operation.