[
https://issues.apache.org/jira/browse/FINERACT-200?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16791098#comment-16791098
]
Edward Cable commented on FINERACT-200:
---------------------------------------
[~santoshmath] Should we keep this or mark as unresolved and ensure that in
Fineract CN, current accounts get labeled distinctly from savings accounts?
> Separate Current Accounts from Savings Accounts
> -----------------------------------------------
>
> Key: FINERACT-200
> URL: https://issues.apache.org/jira/browse/FINERACT-200
> Project: Apache Fineract
> Issue Type: Improvement
> Components: Savings
> Reporter: Dayna Harp
> Assignee: Markus Geiss
> Priority: Minor
> Labels: gsoc, p3
>
> https://mifosforge.jira.com/browse/MIFOSX-1361
> Current Accounts and Savings accounts are two different category of deposit
> products. At least at the User Interface, these should be treated as two
> different products. At the platform level, we should have a field that
> differentiate these (perhaps m_savings.product.deposit_type_enum and
> m_savings_account.account_type_enum)
> Savings accounts should not allow overdraft and hence the parameters
> associated to overdraft can be defaulted to null.
> Current accounts allow overdraft and overdraft limits and charges/interest
> for overdrafts. Also they usually have zero interest rate, but we should
> retain the interest rate fields for current account.
> Fees - should be separated out for current accounts and savings accounts.
> Also, need to be evaluated how this will impact savings reports.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
