Aging in Arrears table inaccurate
Description
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.
Environment
Activity
As part of data warehouse work we will build summary table(s) to collect this information.
Note: In initial datawarehouse analysis, I didn't find a reason to show aging in arrears as other than "loan is 6 weeks in arrears" (loan level aging) which is the current mifos approach. Not saying the other approach talked about here can't be done (installment level aging) just that I'm not seeing it as the typical aging in arrears approach.
Assign to me to figure out correct way to collect arrears
Update Data Warehouse with this other way of arrears, will create a new issue to update reports with this
Haven't started this yet kay. Is it okay if we move this to next iteration? Am doing incremental etl work first mifosbi-47.
Assignee
Reporter
Labels
URL
Story Points
Team
Scheduled For
Epic
Notify
productboard URL
Man Day Estimate
Components
Fix versions
Priority
