[
http://mifosforge.jira.com/browse/MIFOS-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jakub Sławiński updated MIFOS-3305:
-----------------------------------
Description:
Mifos is currently designed to reject any payment greater than remaining
balance of the loan (an overpayment). This can happen for various reasons:
* As we have MFIs who do not collect repayments directly, but rather through
banks or post offices, it becomes a common scenario for clients to overpay the
remainder of their loan, since these other locations do not know how much is
left on the loan.
* Another case where it commonly occurs is after migrating accounts from
another MIS when there are small rounding differences between the two
schedules, so that closing an account in the old system may result in an
overpayment in the Mifos schedule, which no clear way to track that.
* I suspect with the addition of mobile money, this scenario will be common for
those customers as well.
Sometimes it is only a few dollars over, sometimes an entire extra installment
is mistakenly paid. Ideally the MIS will track this so that action can be
taken to return the overpayment portion to clients in future.
New specification:
Overpayments:
1. Overpayment situation only happens when repaying the last payment of a loan
2. System detects an Overpayment during bulk payment upload,
3. The system closes the loan account and makes an entry in the new database
table with
details such as loan account number, overpayment amount, date and time, status
of the
overpayment and payment id(to be able to track the overpayment is linked to
which
payment)
4. On the loan page, the system will display the amount of the overpayment.
Adjacent to
this, there will be a button labeled 'Clear' that will be made available for a
user to
manually clear the amount in case the last repayment was adjusted for some
reason. The
click of this button will allow user to specify how much amount they would want
to clear
off.
5. Each loan can have more than one overpayment
was:
Mifos is currently designed to reject any payment greater than remaining
balance of the loan (an overpayment). This can happen for various reasons:
* As we have MFIs who do not collect repayments directly, but rather through
banks or post offices, it becomes a common scenario for clients to overpay the
remainder of their loan, since these other locations do not know how much is
left on the loan.
* Another case where it commonly occurs is after migrating accounts from
another MIS when there are small rounding differences between the two
schedules, so that closing an account in the old system may result in an
overpayment in the Mifos schedule, which no clear way to track that.
* I suspect with the addition of mobile money, this scenario will be common for
those customers as well.
Sometimes it is only a few dollars over, sometimes an entire extra installment
is mistakenly paid. Ideally the MIS will track this so that action can be
taken to return the overpayment portion to clients in future.
Affects Version/s: Release H
Fix Version/s: (was: Unscheduled)
Release H
Assignee: mifosdeveloperqueue (was: pmqueue)
> handling overpayments of remaining loan balance
> -----------------------------------------------
>
> Key: MIFOS-3305
> URL: http://mifosforge.jira.com/browse/MIFOS-3305
> Project: mifos
> Issue Type: New Feature
> Components: Loan Account
> Affects Versions: Release H
> Reporter: Sam Birney
> Assignee: mifosdeveloperqueue
> Priority: Major
> Labels: almajmoua
> Fix For: Release H
>
>
> Mifos is currently designed to reject any payment greater than remaining
> balance of the loan (an overpayment). This can happen for various reasons:
> * As we have MFIs who do not collect repayments directly, but rather through
> banks or post offices, it becomes a common scenario for clients to overpay
> the remainder of their loan, since these other locations do not know how much
> is left on the loan.
> * Another case where it commonly occurs is after migrating accounts from
> another MIS when there are small rounding differences between the two
> schedules, so that closing an account in the old system may result in an
> overpayment in the Mifos schedule, which no clear way to track that.
> * I suspect with the addition of mobile money, this scenario will be common
> for those customers as well.
> Sometimes it is only a few dollars over, sometimes an entire extra
> installment is mistakenly paid. Ideally the MIS will track this so that
> action can be taken to return the overpayment portion to clients in future.
> New specification:
> Overpayments:
> 1. Overpayment situation only happens when repaying the last payment of a loan
> 2. System detects an Overpayment during bulk payment upload,
> 3. The system closes the loan account and makes an entry in the new database
> table with
> details such as loan account number, overpayment amount, date and time,
> status of the
> overpayment and payment id(to be able to track the overpayment is linked to
> which
> payment)
> 4. On the loan page, the system will display the amount of the overpayment.
> Adjacent to
> this, there will be a button labeled 'Clear' that will be made available for
> a user to
> manually clear the amount in case the last repayment was adjusted for some
> reason. The
> click of this button will allow user to specify how much amount they would
> want to clear
> off.
> 5. Each loan can have more than one overpayment
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
http://mifosforge.jira.com/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
