Bug 25746 - Don't prefill "amount tendered" when paying charges
Summary: Don't prefill "amount tendered" when paying charges
Status: NEW
Alias: None
Product: Koha
Classification: Unclassified
Component: Fines and fees (show other bugs)
Version: Main
Hardware: All All
: P5 - low enhancement (vote)
Assignee: Bugs List
QA Contact: Testopia
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-14 11:28 UTC by Katrin Fischer
Modified: 2020-06-14 11:37 UTC (History)
1 user (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 Katrin Fischer 2020-06-14 11:28:18 UTC
When dealing with paying charges, the "Amount tendered" is prefilled with the expected total. I think this doesn't really work well.

It assumes, that the charge is paid in full and that you will receive the correct amount from the patron. Both are assumptions are not safe.

When a partial amount is paid, you have to change the amount tendered manually.

When the patron gives you a different amount than preset, you need to change it manually.

I believe that it would be better to leave this field empty making the change warning etc. optional.

In this case libraries could only set the "Amount tendered" when a different amount to the exact amount is given to trigger the change to give modal.

A lot of libraries might prefer to not fill the field in and just deal with the exchange without the extra clicks and inputs.

Making the field optional or required could be a system preference. At the moment it's required, but not visually marked as such.

To test:
- Add a charge of any count
- Click on pay selected
- Verify the workflow for paying only a partial of it using "Pay selected"
- Try leaving the amount tendered empty - required error shows
Comment 1 Katrin Fischer 2020-06-14 11:37:31 UTC
I had originally described the problem on bug 22359, see bug 22359 comment #5 and bug 22359 comment #9.