Description
This ticket is to capture any additional design ideas around the improvements to misnamed "savings" account. While this started as "Savings" account, where an interest rate may be assumed, it also now includes the idea of a payment transaction account or checking account or wallet. Thus, the more genericized version of this "should be" Current Account, or Payment Account.
Setting that naming issue aside, please upload any design documents you may have to enhanced "savings accounts" in fineract. I understand that other implementations have forked the code and built entirely new stuff, so it would be good to get your ideas here. If all you can do is share requirements, please do so in attachments to this ticket. Internal deadline for sharing is April 30th.
Peter has created a set of tickets - please comment on those directly if you have specific concerns or ideas for them.
Tickets in Peter's Order (Peter - please edit for clarity)
1751 DONE (batch API related)
1912 in progress
1910 in progress
1943
1939
1931
1938
1911 in progress
1915
1916
1917
1831
1921
1929
1909
webapp:
1721
1727
1726
1722
Attachments
Issue Links
- is a parent of
-
FINERACT-1939 Hold Amount - should be debit
- Resolved
-
FINERACT-1916 Data Table query - Advanced result set
- Open
-
FINERACT-1970 Assign Data Table to Transaction (General)
- Open
-
FINERACT-1910 Data Table query - Advanced
- Resolved
-
FINERACT-1912 Transaction query - Advanced
- Resolved
-
FINERACT-1911 Assign Data Table to Transaction (Savings)
- Resolved
-
FINERACT-1915 Transaction query - considering assigned data table
- Resolved
-
FINERACT-1960 Periodic Accrual Accounting for Savings product
- In Progress
-
FINERACT-1943 Transaction query - Advanced - Extend filtering with submittedOnDate
- Resolved
- links to