m (→Input methods) |
m (→Input methods) |
||
Line 18: | Line 18: | ||
* Manual (date, amount, post, member (if applicable), description/note) | * Manual (date, amount, post, member (if applicable), description/note) | ||
* Automatic: import a CSV, XML or MT940 export file from the bank account and assign all lines to a post | * Automatic: import a CSV, XML or MT940 export file from the bank account and assign all lines to a post | ||
** Additionally: a "learning" system where credit mutations from specific bank accounts are automatically recognised as monthly payments for a specific member for the next unpaid month | ** Additionally: a "learning" system where credit mutations from specific bank accounts are automatically recognised as monthly payments for a specific member for the next unpaid month and recurring debit payments (like the rent) are also recognised. | ||
== Administrative features == | == Administrative features == |
Latest revision as of 21:27, 31 March 2014
Wat dis?
On this page we can make a list of wishes for a finances/book-keeping system.
Current system
The current system is an Excel-sheet with a tab for every year. On each year-tab the pennymaster (FwD) keeps track of payments per month (horizontal) per member (vertical). Additionally the expenses are noted per month, separated into rent, banking costs and "other". This "other" comprises of various expenses like bought tools, renting a van or subscriptions to things like a VoIP-service.
Since our finances are relatively simple we should be able to keep them in a slightly more "interfaceable" system like a database with an administration system.
Desired features
Input
- Monthly payments per member.
- Monthly rent cost
- Monthly (or periodical) cost for the bank account
- Ad hoc expenses
- Recurring expenses (subscriptions/accounts)
Input methods
- Manual (date, amount, post, member (if applicable), description/note)
- Automatic: import a CSV, XML or MT940 export file from the bank account and assign all lines to a post
- Additionally: a "learning" system where credit mutations from specific bank accounts are automatically recognised as monthly payments for a specific member for the next unpaid month and recurring debit payments (like the rent) are also recognised.
Administrative features
- Separate book keeping for the stichting and optionally other books like the bar
Interfaces
- An interface for inputting manual mutations
- A system for inputting automatic mutations (files)
- An interface to the LDAP to associate members and their payments with their LDAP accounts
- An interface for members to see their payment status
- Optionally: integrate their fees/dues with their bar balance in the same overview