Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id B5105200B65 for ; Wed, 17 Aug 2016 13:56:25 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id B3B0B160A8C; Wed, 17 Aug 2016 11:56:25 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 05DA5160A86 for ; Wed, 17 Aug 2016 13:56:24 +0200 (CEST) Received: (qmail 41449 invoked by uid 500); 17 Aug 2016 11:56:24 -0000 Mailing-List: contact dev-help@fineract.incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@fineract.incubator.apache.org Delivered-To: mailing list dev@fineract.incubator.apache.org Received: (qmail 41438 invoked by uid 99); 17 Aug 2016 11:56:24 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2016 11:56:24 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id BA26EC7FF1 for ; Wed, 17 Aug 2016 11:56:23 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.739 X-Spam-Level: X-Spam-Status: No, score=-3.739 tagged_above=-999 required=6.31 tests=[KAM_ASCII_DIVIDERS=0.8, KAM_LAZY_DOMAIN_SECURITY=1, RCVD_IN_DNSWL_HI=-5, RCVD_IN_MSPIKE_H3=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-0.519] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id LdTidBnhTCfG for ; Wed, 17 Aug 2016 11:56:22 +0000 (UTC) Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with SMTP id AD6935FC32 for ; Wed, 17 Aug 2016 11:56:21 +0000 (UTC) Received: (qmail 41223 invoked by uid 99); 17 Aug 2016 11:56:20 -0000 Received: from arcas.apache.org (HELO arcas) (140.211.11.28) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2016 11:56:20 +0000 Received: from arcas.apache.org (localhost [127.0.0.1]) by arcas (Postfix) with ESMTP id B5C932C02AD for ; Wed, 17 Aug 2016 11:56:20 +0000 (UTC) Date: Wed, 17 Aug 2016 11:56:20 +0000 (UTC) From: "subramanyasn (JIRA)" To: dev@fineract.incubator.apache.org Message-ID: In-Reply-To: References: Subject: [jira] [Commented] (FINERACT-131) Allow new loans to clear balances of existing loans (Top Up Loans) MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 archived-at: Wed, 17 Aug 2016 11:56:25 -0000 [ https://issues.apache.org/jira/browse/FINERACT-131?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15424362#comment-15424362 ] subramanyasn commented on FINERACT-131: --------------------------------------- @ Dayna, Weather top up loans should allow for equal or 1$ greater than the existing loan? Eg. 1. If the Loan (without interest recalculation) is disbursed on 01 January 2016, and amount is 10000. Interest accumulated is 600 2. If the top up loan is equal to 10000+600 = 10600 (or even amount of 10601) should it allow or not? > Allow new loans to clear balances of existing loans (Top Up Loans) > ------------------------------------------------------------------ > > Key: FINERACT-131 > URL: https://issues.apache.org/jira/browse/FINERACT-131 > Project: Apache Fineract > Issue Type: Improvement > Reporter: Dayna Harp > Assignee: Markus Geiss > Priority: Minor > > https://mifosforge.jira.com/browse/MIFOSX-439 > Essentially this is a very straight forward implementation of the top-up loans principle, whereby the current loan will be paid off using the balance of the top up loan (once approved/disbursed). The disbursed amount of the top-up loan will therefore be reduced by the outstanding balance (P+I) of the old loan. The remainder is treated as a completely new product with a new schedule. > A proposed way to implement this might be to specify whether a certain product is eligible for topping up and if so, to pull in a list of active loans from the same client as part of the loan template when setting up the product. -- This message was sent by Atlassian JIRA (v6.3.4#6332)