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.

How?

Let's add a new reimbursements 'app' to the website to contain the new functionality.

This app should:

• Have a model that describes a reimbursement (request). This model would have to contain all of the data that can be filled in on the paper form, and some additional information.

  To keep it simple, it's fine to leave out payment details (the bank account or cash box part)

• Allow normal users to create reimbursements.

• Allow the treasurer to 'approve' a reimbursement from the 'admin'.

• Keep track of who created and approved a reimbursement.

• Show a list of reimbursements that have been created by the user.

To help you get started, we've already created an empty reimbursements app, with some pointers. There's also an example solution (#2), and a branch with some more hints.
You can now get started. Here are some resources:

• Perhaps something in this feature request is unclear. If so, it's best to solve that before actually implementing things.
• Any documentation you need can be found in https://docs.djangoproject.com/en/4.2/contents/.
• Ask the Technicie for more precise pointers when you don't feel like searching through all of the docs.
• Really, we're here to help!