|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
------------------------------------------------------------------------------ AlienVault Unified Security Management (USM) platform delivers complete security visibility with the essential security capabilities. Easily and efficiently configure, manage, and operate all of your security controls from a single console and one unified framework. Download a free trial. http://p.sf.net/sfu/alienvault_d2d
_______________________________________________ Mifos-issues mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/mifos-issues
Keith, for now accounting is handling all fees similarly (I was not sure if the default mapping should have separate heads for two different types of fees).
I have a couple of questions regarding how fees are implemented
1) We have two fees "withdrawal" and "Annual" fees for which we want separate account heads (the fees themselves identified by a Transaction Type..a java side enum)
2) Most organization would have additional fees associated with Savings (Account opening fees, New Passbook fees etc). So going forward we might need to be adding support for fees the way it is present in Loans (arbitrary fees can be added)
So would need a way in the loan/saving transaction table to identify which "fee" is being paid (without it being in a transaction Type).
Then the "advanced accounting" API could kick in (for mapping any of the individual fee to separate Income accounts at the time of loan product definition)