https://bugs.koha-community.org/bugzilla3/show_bug.cgi?id=36029 Bug ID: 36029 Summary: Add the ability to backdate a transaction in POS Change sponsored?: --- Product: Koha Version: master Hardware: All OS: All Status: NEW Severity: enhancement Priority: P5 - low Component: Fines and fees Assignee: koha-bugs@lists.koha-community.org Reporter: barbara.johnson@bedfordtx.gov QA Contact: testopia@bugs.koha-community.org We've been using the POS (Point of sale) feature since August 2023. During that time we have encountered some issues that we believe could be solved by adding the ability to backdate a POS transaction. Here is our use case: Sometimes staff forget to enter the sale in POS. This usually happens for credit card sales when the staff member does the credit card transaction, the patron signs, a receipt is given and then the staff member is interrupted by someone/something else causing the sale to never be entered into Koha. We have a large number of funds because our library takes care of not only fees for copies, ILLs, faxes, etc. but also Friends & Foundation sales for earbuds, flash drives, tote bags, book sales, pumpkins, event tickets, to name a few. Each of these sales goes to a different account per our City Finance dept. Staff will sometimes select the wrong debit code which is especially bad when the funds collected should have gone to a different entity, such as the Friends. The Finance dept. wants an exact recording of sales on the day they happened. However, these issues are often not detected until staff reconciles the drawer each morning. At that time they have to enter the missed/incorrect sales into the POS. That can cause issues with reporting since these transactions are now being entered on the wrong date. Being able to enter a transaction and backdate it would help solve this problem for the library, keep our Finance staff happy and make our reports accurate. I think this would need to be covered by a permission since we would only want certain staff to be able to do this. -- You are receiving this mail because: You are the assignee for the bug. You are watching all bug changes.