lghs / accounting Goto Github PK

There needs to be a page where an admin can see all movements that have not been assigned a category.

There should be logic to try and guess which category a movement falls in (easy enough for subscriptions and reimbursement, the most common).

That feature should be easily doable with keyboard only and allow bulk edition (really, it's the most annoying part, let's make it as simple as possible).

Allow uploading coda files.
Each coda file imported is saved so it's impossible to upload it twice.
The wizard shows a list of all movements to be encoded with the fields pre-filled, guessing when possible what the content of each field should be.

Allow members to transfer money to the hackerspace that they can use in the space to pay consumables (food, drinks, plastic for printers...).

Ability to manually encode movements between accounts.

A movement contains many fields, I probably forgot some.

• from (either internal [account] or external [IBAN + Bank + name of sender])
• to (same as from)
• amount
• description
• communication type (structured, unstructured)
• communication
• date sent
• date received
• transaction code

Prepare accounting app for oAuth to LDAP switch

This will be obsoleted by #21, but in the meantime, users have to be inserted manually.

Not all users should have access to all features.

I think everyone should be able to read everything, but account numbers should probably be anonymised.

Normal users should only have read only access to the different features.

An account can be split into virtual accounts.
A movement can be targeted from and/or to a virtual account instead of a classical account.
Content of virtual accounts still counts in the classical account.

"My Data" section is accessible without logged in.

We should speak to the members first, but I'd like the dashboard with the current total amounts, graphs and amount of months of rent we can still afford to be accessible to everyone without login.

Clean forms, fix responsive, ...

A basic spring-boot app with a local and dev configuration, a database and a login through members.
Basic permission system.

Members should be able to connect using their sign-in account.

All branches and PRs should get built, pushing into master should auto-deploy.

Still a blurry idea, but members should have the possibility to earn virtual money and vote on budgets based on their earnings.

An easy way to classify movements for reporting that's not the legal categories (food, consumables, machines, donation, covid...).

Should be free form text (maybe max length), any number per movement.

Documents like bills and receipts and such.

Depends on #3

Currently, the membership fee payments are tracked in the member directory, it would be easier to track them in the accounting app since we have all the information available to automate it here.

Ability to archive accounts.
Archived accounts are listed after other accounts and grayed out so it's clearly visible they are archived.

They are kept because we want to keep a log of the movements, but visually out of the way because the account should not be used.

There should be a warning when trying to touch movements of an archived account.

• A summary of each account (numbers).
• A line graph showing the amount stored in the account over time
• A pie chart per classical account showing the distribution in each virtual account (depends on #28)
• A table of the last X movements

Allow members to ask for reimbursments when they buy something for the hackerspace (food, consummables, travel expenses).

Should make it clear what's needed (documents/tickets, reason, bank account).

A code should be generated so that when the coda containing the reimbursment movement is imported, the reimbursment is automatically marked as closed.

Creating, listing and editing of accounts.
For now, an account has a name, and a description. Further fields will be added in future developments

It happens that a wire transfer contains money from multiple categories. I.e. food and subscription.
The UI should allow splitting that into two movements while keeping all the information (coda id and sequence number).

An API to allow developing apps in the space to consume or credit member accounts (rfid plans).

Users should receive a notification when their subscription expire.

• This should be made so the mail isn't sent if the subscriptions have not been encoded
• Per user setting to disable it for each subscription type (monthly / yearly)

When a movement is linked to a subscription, the user should at least be made aware when splitting it that it has a side effect. So far the issue has not risen because I split before assigning, but it's easy to do by mistake or if you don't know about it.

Account numbers must be validated manually before users see updated statistics, but admins don't get notified...