Add reimbursements #3712
Labels
app:moneybirdsynchronization
Issues regarding the Moneybird synchronization
board
Need to involve the board
feature
Issues regarding a complete new feature
request-for-comments
Author wants to have other people respond for their opinion
This is very similar to the example issue we made for the Technicie workshop. It seems like an actual good idea for the real concrexit as well.
What?
Within Thalia, members often need to request reimbursements from the treasurer:
When a committee spends money to organize something that will be funded by Thalia, the committee fills in a paper form, attaches the receipt from a payment they made, and hands the filled in form to the treasurer. The treasurer then checks whether the reimbursement form is correct, and approves it. Then, Thalia transfers money back to the committee(member) that spent some money.
Here is the form that is currently used: https://thalia.nu/association/documents/document/58/.
I think it would be great if people can submit their reimbursement requests online.
Why?
Printing out the form, and filling it in on paper is tedious. You need to print, which is a pain on campus, and most students don't have printers in their room. It's also not practical for the treasurer to keep the books on paper.
So if we can do it on Thalia's website, that would make many peoples' lives a little bit easier.
The next thing that makes this more valuable, is that we may be able to automate processing them on moneybird a little bit more. The current process is:
Assuming that we already get digital versions of the reimbursement request, we can automate this partially as follows:
Now, the attachments are visible on moneybird which means the treasurer doesn't need to look in the paper book to check things.
How?
Deviating slightly from the tutorial variant of this issue, I think for our real implementation it would be better to stay entirely within the admin. People without any permissions have no business making reimbursement requests, so keeping active member stuff in the admin is a slightly better separation of concerns IMO.
So:
reimbursements
app.ReimbursementRequest
model with the necessary fields. We add either astatus
(awaiting review, appproved, processed) or onlyis_approved
field. One (pdf or image) document can and must be attached. Maybe we also want to support multiple attachments.review reimbursement
permission to approve the request or maybe to otherwise change its status.review reimbursement
permission see all requests.@nvoers @JobDoesburg what do you guys think about this? And just to be sure, do you agree this would be good enough to be able to get rid of the paper form entirely?
The text was updated successfully, but these errors were encountered: