[
http://mifosforge.jira.com/browse/MIFOS-3305?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=58857#action_58857
]
Sam Birney commented on MIFOS-3305:
-----------------------------------
Thanks Emily. The previous MIS here adds it to the loan as a
"remainder/overpayment". Marking the loan with that info (for reporting &
accounting) and then crediting the client account sounds right. There should
be some way to refund the overpayment or apply it towards the next loan for the
client. An overpayment should probably have its own GL code. The transaction
import should treat this the same as the UI (if any).
We considered creating "overpayment" savings accounts for clients as a
workaround, since it is essentially a way of holding onto money from the
clients, but that idea was rejected because the import plugin cannot be used
for that and there are so many that we need to automate it, so we are trying
the workaround of a new plugin that writes this info to a separate table (as
well as penalties and write-backs). Perhaps if the transaction import could be
extended to savings accounts that would be a better way. We are hoping when
the mobile money feature is released there will be some mechanism to handle it
or at least a standard accepted workaround that can deal with the number of
occurrences that come up.
> handling overpayments
> ---------------------
>
> Key: MIFOS-3305
> URL: http://mifosforge.jira.com/browse/MIFOS-3305
> Project: mifos
> Issue Type: New Feature
> Components: Loan Account
> Reporter: Sam Birney
> Assignee: pmqueue
> Priority: Major
> Fix For: Gazelle Backlog
>
>
> 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.
--
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
------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
Mifos-issues mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/mifos-issues
