[
https://issues.apache.org/jira/browse/FINERACT-1917?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17730249#comment-17730249
]
James Dailey commented on FINERACT-1917:
----------------------------------------
Rob - yes, this code is not well labeled and the concept is essentially a
“current account”. A savings account could be seen as a current account w
some limitations like number of free withdrawals per month. Savings account
and current accounts also can offer interest. Both or considered liabilities
of the Bank, but savings often have additional regulations and compliance
reporting.
> Major improvement to Savings Account
> ------------------------------------
>
> Key: FINERACT-1917
> URL: https://issues.apache.org/jira/browse/FINERACT-1917
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Savings
> Reporter: James Dailey
> Assignee: James Dailey
> Priority: Major
> Labels: BeanSalad
> Fix For: 1.9.0, 1.8.4
>
>
> 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.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
