Fees/Fines (UXPROD-792)

[UXPROD-106] Refund paid fees/fines and create report (mostly finished in Q3 2020 but not released) Created: 18/Jan/18  Updated: 31/Aug/21  Resolved: 14/Oct/20

Status: Closed
Project: UX Product
Components: Fees/Fines
Affects versions: None
Fix versions: R1 2021
Parent: Fees/Fines

Type: New Feature Priority: P1
Reporter: Cate Boerema (Inactive) Assignee: Holly Mistlebauer
Resolution: Done Votes: 0
Labels: cap-mvp, feesfines, po-mvp, q2-2020-at-risk, q3-2020-spillover, q4-2019-at-risk, q4-2019-spillover, resourceaccess, split
Remaining Estimate: Not Specified
Time Spent: Not Specified
Original estimate: Not Specified

Attachments: PNG File Refund Fees_Fines - Pay Other FFs.png     PNG File Refund Fees_Fines - Processing.png     PNG File Refund Fees_Fines - Transaction.png    
Issue links:
Blocks
blocks UXPROD-1876 Refund enhancement: Implement issue c... Draft
is blocked by UXPROD-2445 Refactoring of Fees/Fines Actions Closed
Cloners
is cloned by UXPROD-2717 Refund paid fees/fines and create rep... Closed
Defines
is defined by MODFEE-38 Refund fees/fines Closed
is defined by UIU-1139 Refund fees/fines: Enter refund Closed
is defined by MODFEE-56 [SPIKE] Fees/fines refactoring estima... Closed
Duplicate
is duplicated by UXPROD-844 Fees/Fines in-app report: Refunds to ... Closed
Relates
relates to UXPROD-2717 Refund paid fees/fines and create rep... Closed
Potential Workaround: Holly: I split UXPROD-106 Refund paid fees/fines into two issues (UXPROD-106 Refund paid fees/fines and UXPROD-1876 Use fee/fine refund to pay other fees/fines). This part of the refund feature is very basic and will be done without any fluff. We have already made this process quite basic by producing a report (UXPROD-844) to identify who to give refunds to rather than setting up some automated process. For the MVP the refunding of bursar-paid fees/fines will also be handled manually.
Holly: I plan to also remove the Refund button from the Open/Closed/All Fees/Fines page. This will eliminate the need for extra code to process multiple refunds at one time. Instead, refunds will be handled one at a time via the ellipsis, just as Errors are. I will add back a feature to allow multiple refunds at one time, but I'm not sure it will be needed.
Epic Link: Fees/Fines
Front End Estimate: Small < 3 days
Front End Estimator: Darcy Branchini
Front-End Confidence factor: Medium
Back End Estimate: Medium < 5 days
Back End Estimator: Darcy Branchini
Estimation Notes and Assumptions: Darcy's BE and FE estimates were Very Small (VS) < 1day as of July 20. Holly added the refund report to this UXPROD, so she increased the estimates.
Development Team: Vega
PO Rank: 97
Rank: Chalmers (Impl Aut 2019): R5
Rank: Chicago (MVP Sum 2020): R1
Rank: Cornell (Full Sum 2021): R1
Rank: Duke (Full Sum 2021): R1
Rank: 5Colleges (Full Jul 2021): R1
Rank: FLO (MVP Sum 2020): R1
Rank: GBV (MVP Sum 2020): R2
Rank: hbz (TBD): R1
Rank: Hungary (MVP End 2020): R1
Rank: Lehigh (MVP Summer 2020): R1
Rank: Leipzig (Full TBD): R1
Rank: Leipzig (ERM Aut 2019): R5
Rank: MO State (MVP June 2020): R1
Rank: TAMU (MVP Jan 2021): R1
Rank: U of AL (MVP Oct 2020): R1

 Description   
Merged on July 20, 2020

UXPROD-844 Closed (Fees/Fines in-app report: Refunds to process manually) was merged with UXPROD-106 Closed (Refund paid fees/fines) to create UXPROD-106 Closed (Refund paid fee/fines and create report). Note: This was done because of the constant misunderstanding that the report wasn't a high priority although it was part of the thin-thread workflow.

On July 11, 2019 UXPROD-106 Closed Refund paid fees/fines was split into two issues:
* UXPROD-106 Closed Refund paid fees/fines (this is a basic refund, including a patron notice but excluding an automated feed to the bursar)
* UXPROD-1876 Draft Use fee/fine refund to pay other fees/fines

Some details...

  • Attachment Refund Fees_Fines - Processing.png contains the details of this feature as determined by the RA SIG to date. We will be revisiting this feature before the user stories are written.
  • A refund will be started by locating the fee/fine to refund starting from User Information and going to Fee/Fine History. The fee/fine to refund (or can do several at once) will be selected and then the refund modal will appear (as shown by attached image Refund Fees_Fines - Transaction.png).
  • If the patron owes other fees/fines they will be presented as for possible payment using the refund (as shown by attached image Refund Fees_Fines - Pay Other FFs.png).


 Comments   
Comment by Anya [ 29/Mar/19 ]

Comment from the March Meeting : no-one handes cash - want to credit - could split this out

Comment by Erin Nettifee [ 15/Jul/19 ]

I'm just wanting to make sure of something since I didn't see it in the attachments. There's language about outstanding fees/fines, but a paid fine would be closed. So if we need to give a refund for a fine that is closed, is that included here?

Comment by Holly Mistlebauer [ 01/Aug/19 ]

Erin Nettifee: Yes, closed fees/fines would be able to be refunded here. You would also be able to refund partial payments (which wouldn't be closed) on fees/fines that get cancelled because they were discovered to be errors.

Comment by Holly Mistlebauer [ 01/Aug/19 ]

Anya: No one is planning to do cash refunds. It is up to each library to determine how they want to do the refund. Most of the US libraries issue checks for everything. Issuing credit card refunds works too.

Comment by Cate Boerema (Inactive) [ 17/Dec/19 ]

Holly Mistlebauer is this blocked by any other features? When do you expect to have the stories written?

Comment by Cate Boerema (Inactive) [ 27/Mar/20 ]

Darcy Branchini I just updated the estimates on this feature so it matches what we discussed putting in the cap plan.

Comment by Darcy Branchini [ 16/Jul/20 ]

Cate Boerema, I just spoke with Vega about this and they believe most of this will be completed in scope of the refactoring feature UXPROD-2445 Closed but they wanted to leave this on the board for informational purposes.

Comment by Cate Boerema (Inactive) [ 16/Jul/20 ]

Okay, that's fine by me. Thanks for the update, Darcy Branchini!

Generated at Fri Feb 09 00:05:47 UTC 2024 using Jira 1001.0.0-SNAPSHOT#100246-sha1:7a5c50119eb0633d306e14180817ddef5e80c75d.