|
||||||||||||||
|
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 |
||||||||||||||
------------------------------------------------------------------------------ Precog is a next-generation analytics platform capable of advanced analytics on semi-structured data. The platform includes APIs for building apps and a phenomenal toolset for data science. Developers can use our toolset for easy data analysis & visualization. Get a free account! http://www2.precog.com/precogplatform/slashdotnewsletter
_______________________________________________ Mifos-issues mailing list Mifos-issues@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/mifos-issues
Vishwas, whilst looking at code around payment types for loans I noticed that you are entering 'event information' such as interest applied (on disbursement of loan) into the m_loan_transaction table.
This is clearly to support integration with 'accrual accounting'.
First off I think that the scope of worked needed around 'accounting integration' is only that of CASH ACCOUNTING - Musoni only require this for first version of their m-lite product and I believe thats all that mifos supports right now also (even in new MIFOS_ACC accounting module) so theres no need for support of 'accrual accounting' just yet.
Secondly, I am not sure of mixing the responsibilities of the m_loan_transaction table to hold both 'real transactions' information and also other information to enable accrual accounting e.g. 'events such as interest applied'