[Discussion]: What is needed for from the frontend for a good financial audit?

[JustSamuel]

During my 26 hours of fixing the bookkeeping, I had to use a lot of db queries, which was fine since I can access the db, but for years after me this information should be provided by the dashboard. Therefore, I am suggesting creating a "financial insights" tab / module that helps doing such an audit without db queries.

The main goal in this tab is to be able to quickly check numbers from our bookkeeping with those in SudoSOS. The scope is therefore mostly to present numbers for a bookyear / quartile.

The main numbers are

• The top-ups
• The total writeoffs
• The total payouts
• The total seller payouts
• The total amount of invoices
• The total amount of fines

These numbers together describe how the balance in SudoSOS changed.

To be able to also nicely check these numbers, we should be able to export these list to an csv, but that will be a backend issue.

[Jobbiesaus]

I completely agree with Samuel on this. He had to take time out of his "afstuderen" to help me get the correct numbers, I do not think the ABC should be involved in finances.

Furthermore, all of these should be possible to accessed with exact dates.

[tomudding]

As mentioned in the boardroom, I think this is an excellent idea and a wise thing to implement.

• The total amount of fines

Make sure that the amount of waived fines is also very clear to avoid any confusion in that regard.

I do not know whether it should be part of this overview or something else, but today, we noticed an issue in the fine -> transfer mapping because of a lack of foreign key constraints. That is also something you ideally want to be able to see (however, if we can ensure/be sure that this never happens again, we do not need such functionality).

Another thing: How would we represent refunds? We have not had to deal with that yet, but it is something to consider.