Dealing with failure to close POS properly

[ARBaart]

A common mistake people make is not closing the POS software properly, leaving the totals in it open. Since there is no practice of checking this on opening, this leads to combined totals being attributed to the next night.
Exactly how this messes up the totals for the first night and whether this includes missing one of the receipts is unknown to me.

Would there be a possibility to check this in screen 4? Perhaps the mistake can be detected among the data retrieved to populate the POS totals.

[casperboone]

Since there is no practice of checking this on opening, this leads to combined totals being attributed to the next night.

Just FYI, this is actually expected, and is also mentioned in the manual (maybe even in the software). (which of course doesn't mean it always gets done)

Exactly how this messes up the totals for the first night and whether this includes missing one of the receipts is unknown to me.

You cannot close without getting a receipt. So it would mean wrong totals and a missing receipt indeed.

---

It's a bit hard to create a check for this I think. We can retrieve dates of opening/closing the POS software from its database I think. A new session is directly started after closing the previous one.
Soo... I wouldn't really know what we could check for. One thing could be no close in the last 24 hours, but that wouldn't work on a Tuesday. The only way that's fixable is by adding a lot of knowledge about our weekly events, but since that changes sometimes, that's not a very flexible solution.

Do you have any other ideas?