Bug 28599 - Add ability to void purchase in point of sale
Summary: Add ability to void purchase in point of sale
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: Main
Hardware: All All
: P5 - low normal (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on: 23354
Blocks:
  Show dependency treegraph
 
Reported: 2021-06-18 13:31 UTC by Andrew Fuerste-Henry
Modified: 2024-03-22 16:48 UTC (History)
2 users (show)

See Also:
Change sponsored?: ---
Patch complexity: ---
Documentation contact:
Documentation submission:
Text to go in the release notes:
Version(s) released in:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Fuerste-Henry 2021-06-18 13:31:32 UTC
If one enters a purchase incorrectly in the point of sale module, one can refund the payments on that purchase in order to correct Koha's understanding of the amount of money the library has taken in. However, those refunds don't do anything to correct the record of how many items were sold. That means that accurate reporting on number of items sold needs to be verifying that none of the payments tied to the purchase have been refunded.

It'd be better to be able to just void the whole sale, setting the amounts on the original purchase(s) and payments all to zero, zeroing out the note in the purchase (since we're using that for the quantity of the sale), and giving them a VOID status.
Comment 1 Martin Renvoize 2024-02-08 17:36:46 UTC
Interesting ideas here.

We always intended to add some simple stock tracking to point of sale, but funding/interest didn't materialise so that work was never taken on.

I do like the idea of a void option for some use cases, there are certainly occasions where a void is more appropriate than a refund.

I'd be happy to take these in, but unfortunately the amount of work coming in these days necessitates I put paying developments first.  If anyone wants to sponsor this it might bump it up the queue.
Comment 2 Barbara Johnson 2024-03-22 16:48:13 UTC
+1 

Just want to add my 2 cents - our use case is that we sell over 30 different types of items via the Point of Sale (POS) system. Those may be for the Library, the Friends Group, or the Foundation. And it's possible that the transactions may be cash, credit/debit card or check. Staff sometimes select the wrong fund or wrong payment type. We have to correct the fund codes so that the correct amount of money is then distributed to the three different entities. And our Finance department needs to have accurate accounting of payment types.  

A void option would allow us to correct those transactions and re-enter them as they should have been originally entered. Right now we have to use the Refund button since there is no other option. But we aren't really issuing a refund, we're making a correction, so the void option would be more appropriate.