I don't think this is new for 704n5 but this is the one used to test.
This ones simple.
On a register set to NOT Allow Cash Back a salesperson can exploit a feature which allows Credit Card amounts greater than the Balance Due. In turn the transaction completes and gives the overage on the credit card as change although its not apparent by what method. But If you look at the Close Register Report you will see that the Change Due was taken out of the Total Cash In Register line. And of course not recorded on the Cash Back line.
How to do it:
To keep it simple, create a fresh install and configure the POS with 2. Run this register in minimal mode with 6% tax rate. Set NO cash back on credit cards.
Enter $100 dollar as the Opening Cash Amount.
Ring up a $10.00 item. With 6% tax would have a balance due of $10.60.
Choose 3. Credit Card and enter in $20.00.
The register simply shows $9.40 Change Due.
Now look at the Close Register Report.
Code: Select all
CASH SALE: 0.00
CHECK SALE: 0.00
CREDIT SALE: 10.00
.............
.............
NET SALES: 10.00
TOTAL TAX: 0.60
GROSS SALES: 10.60
TIPS: 0.00
CASH BACK: 0.00
SUB REG CASH: -9.40
CASH DROPS/PULLS: 0.00
+ CASH FUND: 100.00
CASH IN REG: 90.60
CHECKS IN REG: 0.00
CREDIT IN REG: 20.00In a single sale like this, you could take a moment and see that the CC trans was $10, the CC in Reg is $20, and conclude something needs looking into. On high volume sales this could fly under the radar and escape notice. Especially if the amount overcharged to the CC is in the range of the salespersons lunch money. If you just focused on the actual cash count in drawer, it of course would match the closeout report, but someone got a free lunch out of a register that was set to not allow cash back.
For extended testing try it with Cash Back turned on. Do a sale with cash back and also enter a CC amount greater than the total due. The Register Close Report gets more confusing to understand what happened.
Based on other scenarios or POS configuration maybe there is something I haven't thought of. But I would think If Credit is selected to pay the Balance Due, the amount entered at the prompt cannot be greater than the Balance Due. This would be true even for multi payment types. And even if the register is program to allow cash back (prompted for Cash Back and Total Due is updated), the logic would still be the same. The same apply to Debit.
Adding this logic to the CC/Debit payment types would keep the money "Change Due" from disappearing from the CASH IN REG line in the Register Close Report and keep someone from getting cash out from a register configured otherwise.
CC/Debit prompt amount (Equal To OR Less Than Balance Due) AND (Greater Than OR Equal To Cash Back Amount)
If you need me I'll be in the food court,
