You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "Awasum Yannick (Jira)" <ji...@apache.org> on 2019/12/21 08:49:00 UTC

[jira] [Assigned] (FINERACT-549) CLOSED LOANS DISPLAYED AS ACTIVE LOANS

     [ https://issues.apache.org/jira/browse/FINERACT-549?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Awasum Yannick reassigned FINERACT-549:
---------------------------------------

    Assignee:     (was: Markus Geiss)

> CLOSED LOANS DISPLAYED AS ACTIVE LOANS
> --------------------------------------
>
>                 Key: FINERACT-549
>                 URL: https://issues.apache.org/jira/browse/FINERACT-549
>             Project: Apache Fineract
>          Issue Type: Bug
>          Components: Accounting, Client, Loan, Savings
>         Environment: Ubuntu 14.04
>            Reporter: Jimmy Jubha Mayala 
>            Priority: Critical
>              Labels: newbie
>         Attachments: Temp-Liability Transfer (Temp).pdf, balance sheet.pdf, cash in hand by 31octb17.pdf, interest received from borrowers not right.pdf, print screen.docx, trial balance.pdf
>
>
> We have been using Mifosx 16.12.0 then we found some errors in interest receivables account , interest received from borrowers account and Saving account. where the reference of saving in Asset was not the same with the real Saving amount in Liability, also Interest received from customers was not the same figure as what we have in our manual entry (in hard copies) we traced this for a one day transaction. Interest Receivable was in negative figures also. 
> Then we decided to upgrade to fineract 17.07 but after upgrading we found some of the closed loans displays as active loans. Kumaranath Fernando helped us switch back to mifos 16.12.01 so as we can follow the right steps to upgrade to higher version, we have the backup already. 
> After switching back to mifosx 16.12.01 we also saw the closed loans diplayed as active loans appears also. so we did not go on as the error seems to be in this mifosx 16.12.0
> As Ed Cable adviced as to log an issue in here, we have done that and we real appreciate for  any kind of support we may get! we attached print screens of the errors. 



--
This message was sent by Atlassian Jira
(v8.3.4#803005)