[
http://mifosforge.jira.com/browse/MIFOS-2914?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58061#action_58061
]
Nagananda Kumar commented on MIFOS-2914:
----------------------------------------
HI,
My definition of the issue:
Mifos has a batch job which calculates the loan_arrears and aging in number of
days and populates the same in the "loan_arrears_aging" table in Mifos.
though i donot know the actual calculation method used by mifos,
currently the number of days in arrears is working out to be like below:
1. it is the differance b/w the current date & Actiondate of first due
instalment which is still in overdue.
2. total overdue amount of that loan are taken into overdue_principal,
overdue_interest etc and the loan outstanding into unpaid_principal,
unpaid_interest etc.
Now the issue is that when the aging report is prepared or aging analysis is
done, the data required is as follows:
1. Aging bracket [ 0-7 days, 7-14 days, .......]
2. Overdue amount in that bracket
3. loanoutstanding in that bracket
Now, here, the overdue amount also has to be segregated according to the number
of days it has been past due which is currently not possible as mifos just
stores the total overdue amount from the first day of overdue for the loan
and not the overdue dates of each installment
Expected behaviour:
1. Mifos must store every installment overdue as a separate record in the
loan_arrears_aging instead of 1 record per loan account.
2. Overdue amount is the difference b/w the due amount and the actual paid
amount for that installment.
2. also the no. of days in arrears for each record has to be calculated as
difference b/w current date and the action_date for that instalment [in case
of 0 amount repaid till now on that installment]
3. the no. of days in arrears for each record has to be calculated as
difference b/w current date and the payment_date for that instalment [in case
of partial amount paid for that installment]
4. the unpaid principal or the loan outstanding of the overdue loans can be
stored as a separate record or separate table as this information is at the
loan level and not at the installment level. as storing these information for
every installment is irrelevant in the loan_arrears_aging table.
> Aging in Arrears table inaccurate
> ---------------------------------
>
> Key: MIFOS-2914
> URL: http://mifosforge.jira.com/browse/MIFOS-2914
> Project: mifos
> Issue Type: Bug
> Components: Database
> Reporter: emilytucker
> Assignee: emilytucker
> Priority: Critical
> Fix For: Shamim D
>
>
> According to Naganand the summary table in Mifos, Aging in Arrears (not sure
> the exact table name), is not being populated correctly.
> Scenario: Client has a weekly loan that has 3 missed installments of 100Rs
> each. The most overdue installment is 3 weeks late, the more recently missed
> installment is a few days late.
> Expected: In the aging in arrears table, these values should be populated
> like this:
> 1-7 Days in areas: 100Rs
> 7-14 days in arrears: 100Rs.
> 14-21 days in arrears: 100
> Actual
> 1-7 Days in areas: 0
> 7-14 days in arrears: 0.
> 14-21 days in arrears: 300
> Basically ALL overdue installments are appears in the aging bucket of the
> oldest/most late installment.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://mifosforge.jira.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
