Title: Message Title
|
|
|
|
|
|
To reach parity with Mifos 2.x, we need the following support for defining fees/ charges at the client level:
* one-time fees: can be collected at next meeting or at time of posting
* periodic fees: the recurrence of these should be defined in terms of weeks and/or months (do we need days?)
* up-front fees
Mifos 2.x had a limitation with one-time fees not being able to be collected till next meeting (this gap was address in Mifos 2.1) but let's ensure fees can be assessed and collected at the same time.
Some additional requirements from discussions with SECDEP :
- Added option to collect client fees via collection sheet
- Recurring client level fees – if due for more than one cycle – shows only 1 cycle due (and does not show total due – so collecting via collection sheet is difficult)
When meeting date changes, the following have to happen:
- Client level fees – to be rescheduled accordingly
Questions:
* Are partial payment of fees out of scope for this?
|
|
|
|
|
|
|
|
------------------------------------------------------------------------------
Dive into the World of Parallel Programming. The Go Parallel Website,
sponsored by Intel and developed in partnership with Slashdot Media, is your
hub for all things parallel software development, from weekly thought
leadership blogs to news, videos, case studies, tutorials and more. Take a
look and join the conversation now. http://goparallel.sourceforge.net/
_______________________________________________
Mifos-issues mailing list
Mifos-issues@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mifos-issues
