[jira] [Commented] (FINERACT-652) Deliver status is not getting updated to 'Delivered' (status:300) even message is delivered to the mobile

2019-03-14 Thread Collins Wayig Chwabo Carl (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-652?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793119#comment-16793119
 ] 

Collins Wayig Chwabo Carl commented on FINERACT-652:


I would love to work on this Issue. 

> Deliver status is not getting updated  to 'Delivered' (status:300) even 
> message is delivered to the mobile
> --
>
> Key: FINERACT-652
> URL: https://issues.apache.org/jira/browse/FINERACT-652
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Affects Versions: 1.1.0
>Reporter: Santosh Math
>Assignee: Shruthi  M R
>Priority: Critical
>  Labels: GSOC, Volunteer, p1
> Fix For: 1.4.0
>
>
> The following are the sms status:
> Pending: 100
> Waiting for Delivery Report: 150
> Sent sms: 200
> Delivered sms: 300
> Failed sms: 400
> Even sms is delivered to given mobile number the status in the database is 
> not getting updating from 150 to 300. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-408) When closing Savings account and Withdraw Balance option is enabled, only cash withdrawal is possible, not able to withdraw to a GL Account by Voucher

2019-03-14 Thread Collins Wayig Chwabo Carl (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793116#comment-16793116
 ] 

Collins Wayig Chwabo Carl commented on FINERACT-408:


Thanks Ed. I will do just that.
ᐧ

On Thu, Mar 14, 2019 at 10:54 PM Edward Cable (JIRA) 



> When closing Savings account and Withdraw Balance option is enabled, only 
> cash withdrawal is possible, not able to withdraw to a GL Account by Voucher
> --
>
> Key: FINERACT-408
> URL: https://issues.apache.org/jira/browse/FINERACT-408
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Savings
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: Fineract-CN, gsoc, p3
>
> As a system admin, i should be able to close a savings account and make 
> Balance withdrawal to a GL Account (Contra Account) and payment type for this 
> should be restricted to by Voucher only.
> If Withdraw Balance is not to a GL Account then Cash Payment Type.
> Extend this functionality of Withdraw Balance to Share Accounts too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Resolved] (FINERACT-684) Create and approve loan in batch mode with transaction true fails

2019-03-14 Thread Vishwas Babu A J (JIRA)


 [ 
https://issues.apache.org/jira/browse/FINERACT-684?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Vishwas Babu A J resolved FINERACT-684.
---
   Resolution: Fixed
Fix Version/s: (was: 1.4.0)
   1.3.0

> Create and approve loan in batch mode with transaction true fails
> -
>
> Key: FINERACT-684
> URL: https://issues.apache.org/jira/browse/FINERACT-684
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Affects Versions: 1.1.0
>Reporter: sapana
>Priority: Major
>  Labels: p1
> Fix For: 1.3.0
>
> Attachments: BatchRequest.txt
>
>  Time Spent: 1h 10m
>  Remaining Estimate: 0h
>
> For pre-approved loans, requirement is to create, approve and disburse loan 
> as part of single batch request with transaction set to true. It fails with 
> Nil pointer exception. 
> Couple of observations:
> 1. if enclosingTransaction=true is not specified, the request works. Only 
> fails with transaction mode on
> 2. If enclosingTransaction=true is specified, and the batch request is to 
> create loan, and approve a pre-existing loan, it works.
>  sample request attached.
> error msg recieved:
> [
> {
> "statusCode": 400,
> "body": "Transaction is being rolled back. First erroneous request: 
> \n{\"requestId\":3,\"statusCode\":500,\"headers\":[{\"name\":\"Content-type\",\"value\":\"text/html\"}],\"body\":\"{\\\"Exception\\\":
>  java.lang.NullPointerException}\"}"
> }
> ]



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-408) When closing Savings account and Withdraw Balance option is enabled, only cash withdrawal is possible, not able to withdraw to a GL Account by Voucher

2019-03-14 Thread Collins Wayig Chwabo Carl (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-408?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16793070#comment-16793070
 ] 

Collins Wayig Chwabo Carl commented on FINERACT-408:


Hello [~edcable], [~santoshmath], [~Ippez] 

I would love to work on this Improvement. Please Can you help me with more 
background information on this which may be of help to me. On my own part I 
will do more research on this and begin working on it. Will give you feedback 
of my progress.

Thanks 

Carl Collins 

 

> When closing Savings account and Withdraw Balance option is enabled, only 
> cash withdrawal is possible, not able to withdraw to a GL Account by Voucher
> --
>
> Key: FINERACT-408
> URL: https://issues.apache.org/jira/browse/FINERACT-408
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Savings
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: Fineract-CN, gsoc, p3
>
> As a system admin, i should be able to close a savings account and make 
> Balance withdrawal to a GL Account (Contra Account) and payment type for this 
> should be restricted to by Voucher only.
> If Withdraw Balance is not to a GL Account then Cash Payment Type.
> Extend this functionality of Withdraw Balance to Share Accounts too.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (FINERACT-419) Non-Person Client codes can not be updated to blank

2019-03-14 Thread Santosh Math (JIRA)


 [ 
https://issues.apache.org/jira/browse/FINERACT-419?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-419.
-
Resolution: Cannot Reproduce

[~tonic...@gmail.com] , I am not able to reproduce. Do you check latest code in 
the following instance?

[https://staging.openmf.org|https://staging.openmf.org/]

 

> Non-Person Client codes can not be updated to blank
> ---
>
> Key: FINERACT-419
> URL: https://issues.apache.org/jira/browse/FINERACT-419
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client
>Reporter: Brian C Cooke
>Assignee: Markus Geiss
>Priority: Major
>  Labels: Volunteer, p2
>
> Steps to reproduce:
> 1. Create a client with Legal Form=Entity and assign this client a value from 
> the Main Business Line. Save.
> 2. Edit this client and try to remove Main Business Line (assign back to 
> --Select Main Business Line).  Save.
> 3. Edit again and observe Main Business Line is still assigned.  
> Seems to be an issue for Client Nonperson domain object, as other drop downs 
> related to Client domain object are working as expected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-433) Transactions done by cashier for one teller is replicating in other teller with same cashier but different time duration.

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-433?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792541#comment-16792541
 ] 

Santosh Math commented on FINERACT-433:
---

Yes Ed. It's about moving cashier from one teller to another.

> Transactions done by cashier for one teller is replicating in other teller 
> with same cashier but different time duration.
> -
>
> Key: FINERACT-433
> URL: https://issues.apache.org/jira/browse/FINERACT-433
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Major
>  Labels: GSOC, gci, p2, volunteer
> Fix For: 1.4.0
>
>
> 1. Create a 'Teller 1' with 'cashier A'  with time duration 9am to 1pm.
> 2. Create another 'Teller 2', with same 'cashier A' and time duration 2pm to 
> 5pm
> 3. Create an user with employee as 'cashier A' with valid credentials and 
> permissions.
> 4. Login with the credentials of the user for  cashier A and do all 
> disbursements and repayments,etc. for the time duration between 9am to 1pm
> >If you check the transactions for Teller 1 and Teller 2, both have same 
> >transactions  though same cashier is assigned with different time duration.
> > The transactions done by cashier for specific teller(say Teller 1) at 
> > specific time duration must be highlighted only to that teller , not in 
> > other teller . 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-250) Place Guarantor Funds On Hold

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792539#comment-16792539
 ] 

Santosh Math commented on FINERACT-250:
---

It's never worked on. Only documented it.

> Place Guarantor Funds On Hold
> -
>
> Key: FINERACT-250
> URL: https://issues.apache.org/jira/browse/FINERACT-250
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Major
>  Labels: gsoc, p3
>
> Functional Spec:  
> https://cwiki.apache.org/confluence/display/FINERACT/Blocking+Funds+in+Guarantor+Account



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (FINERACT-242) Transaction history doesn't show occured transactions inside the "View standing instructions" for a client account

2019-03-14 Thread Santosh Math (JIRA)


 [ 
https://issues.apache.org/jira/browse/FINERACT-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-242.
-
Resolution: Cannot Reproduce

Not able to reproduce. 

> Transaction history doesn't show occured transactions inside the "View 
> standing instructions" for a client account
> --
>
> Key: FINERACT-242
> URL: https://issues.apache.org/jira/browse/FINERACT-242
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Client, Savings
> Environment: Amazon AMI - Mifos X Release Version: 16.09.01.RELEASE
>Reporter: Auguste Niragira
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: Volunteer, gsoc, p3
>
> I noticed that when you go to
> Client account > More > View standing instructions > Select standing 
> instruction from list > View transaction history
> There are no transactions listed, although I know for a fact the automated 
> transactions were successful.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-263) "Add Notes" for Centers permission is missing

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792483#comment-16792483
 ] 

Santosh Math commented on FINERACT-263:
---

[~edcable] , Yes there is no control to give permission for Add Notes in 
Center. 

> "Add Notes" for Centers permission is missing
> -
>
> Key: FINERACT-263
> URL: https://issues.apache.org/jira/browse/FINERACT-263
> Project: Apache Fineract
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: Volunteer, fineract-gci, gsoc, p2
> Fix For: 1.4.0
>
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-1080
> Original Description:
> Now user can add notes to centers with out permissions. Permission should be 
> assigned separately for Read, Create, Edit and Delete options. See 
> permissions for group for example.
> Comments
> Shashvat Tripathi Documentation for the notes API can be found at 
> https://demo.openmf.org/api-docs/apiLive.htm#notes
> From a microfinance perspective, clients can be aggregated for applying Joint 
> liability principles. Such a collection of clients is called a Group. Some 
> organizations would want to further extend this aggregation, so you have 
> collections of Groups which are called Centers etc.
> In Mifosx, Centers were originally modeled as specializations of Groups 
> (centers are also stored in m_group table with level_id set to 1, the 
> level_id for groups is 2), for easier use through the API though, separate 
> API's were created for Centers 
> https://demo.openmf.org/api-docs/apiLive.htm#centers, which are mostly 
> abstraction over the Group API with new center specific permissions.
> subramanya Talks about now extending notes API to have a center specific 
> abstractions (with its own permissions), so we need a new notes api which 
> would look like
>  centers/{centerId}/notes/{noteId} 
> , also the existing group notes API i.e
> groups/{groupId}/notes
> should no longer work for centers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FINERACT-263) "Add Notes" for Centers permission is missing

2019-03-14 Thread Santosh Math (JIRA)


 [ 
https://issues.apache.org/jira/browse/FINERACT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-263:
--
Fix Version/s: 1.4.0

> "Add Notes" for Centers permission is missing
> -
>
> Key: FINERACT-263
> URL: https://issues.apache.org/jira/browse/FINERACT-263
> Project: Apache Fineract
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: Volunteer, fineract-gci, gsoc, p2
> Fix For: 1.4.0
>
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-1080
> Original Description:
> Now user can add notes to centers with out permissions. Permission should be 
> assigned separately for Read, Create, Edit and Delete options. See 
> permissions for group for example.
> Comments
> Shashvat Tripathi Documentation for the notes API can be found at 
> https://demo.openmf.org/api-docs/apiLive.htm#notes
> From a microfinance perspective, clients can be aggregated for applying Joint 
> liability principles. Such a collection of clients is called a Group. Some 
> organizations would want to further extend this aggregation, so you have 
> collections of Groups which are called Centers etc.
> In Mifosx, Centers were originally modeled as specializations of Groups 
> (centers are also stored in m_group table with level_id set to 1, the 
> level_id for groups is 2), for easier use through the API though, separate 
> API's were created for Centers 
> https://demo.openmf.org/api-docs/apiLive.htm#centers, which are mostly 
> abstraction over the Group API with new center specific permissions.
> subramanya Talks about now extending notes API to have a center specific 
> abstractions (with its own permissions), so we need a new notes api which 
> would look like
>  centers/{centerId}/notes/{noteId} 
> , also the existing group notes API i.e
> groups/{groupId}/notes
> should no longer work for centers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Updated] (FINERACT-263) "Add Notes" for Centers permission is missing

2019-03-14 Thread Santosh Math (JIRA)


 [ 
https://issues.apache.org/jira/browse/FINERACT-263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math updated FINERACT-263:
--
Affects Version/s: 1.1.0

> "Add Notes" for Centers permission is missing
> -
>
> Key: FINERACT-263
> URL: https://issues.apache.org/jira/browse/FINERACT-263
> Project: Apache Fineract
>  Issue Type: Bug
>Affects Versions: 1.1.0
>Reporter: Edward Cable
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: Volunteer, fineract-gci, gsoc, p2
>
> Migrated over from https://mifosforge.jira.com/browse/MIFOSX-1080
> Original Description:
> Now user can add notes to centers with out permissions. Permission should be 
> assigned separately for Read, Create, Edit and Delete options. See 
> permissions for group for example.
> Comments
> Shashvat Tripathi Documentation for the notes API can be found at 
> https://demo.openmf.org/api-docs/apiLive.htm#notes
> From a microfinance perspective, clients can be aggregated for applying Joint 
> liability principles. Such a collection of clients is called a Group. Some 
> organizations would want to further extend this aggregation, so you have 
> collections of Groups which are called Centers etc.
> In Mifosx, Centers were originally modeled as specializations of Groups 
> (centers are also stored in m_group table with level_id set to 1, the 
> level_id for groups is 2), for easier use through the API though, separate 
> API's were created for Centers 
> https://demo.openmf.org/api-docs/apiLive.htm#centers, which are mostly 
> abstraction over the Group API with new center specific permissions.
> subramanya Talks about now extending notes API to have a center specific 
> abstractions (with its own permissions), so we need a new notes api which 
> would look like
>  centers/{centerId}/notes/{noteId} 
> , also the existing group notes API i.e
> groups/{groupId}/notes
> should no longer work for centers



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Closed] (FINERACT-230) After Waive interest the installment amount is displaying with the previous amount (before waive installment) in collection sheet

2019-03-14 Thread Santosh Math (JIRA)


 [ 
https://issues.apache.org/jira/browse/FINERACT-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Santosh Math closed FINERACT-230.
-
Resolution: Cannot Reproduce

Cannot reproduce in latest version. 

> After Waive interest the installment amount is displaying with the previous 
> amount (before waive installment) in collection sheet
> -
>
> Key: FINERACT-230
> URL: https://issues.apache.org/jira/browse/FINERACT-230
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>Priority: Major
>  Labels: Volunteer, gsoc, p2
>
> 1. Create a loan product, Create a Center and attache Group to it, Attache 
> weekly meeting from 01 June 2016 on friday.
> 2. Create a client under above group and attache JLG loan on 01 June 2016 
> with synk repayment with meeting.
> 3. Approve and disburse the loan
> 4. Waive interest on 03 June 2016.
> 5. Go to collection sheet and enter valid inputs and generate collection 
> sheet for 03 June 2016.
> > Though the interest is waived for first repayment it is still displaying 
> > the previous amount(Before waive).



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-277) No option to writeoff Overdraft account in Client savings account page

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-277?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792416#comment-16792416
 ] 

Santosh Math commented on FINERACT-277:
---

[~edcable] , Whenever the savings account is overdrawn(that is client's 
liability)  and the client never makes the deposit, there is no option to close 
the savings account. 

 

> No option to writeoff Overdraft account in Client savings account page
> --
>
> Key: FINERACT-277
> URL: https://issues.apache.org/jira/browse/FINERACT-277
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Major
>  Labels: gsoc, p3
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1363
> Original Description: 
> Write off option in overdraft account (in savings) is not present. It should 
> be implemented.
> In Saving product creation page for cash based accounting writeoff is 
> introduced under Expense heading



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-302) Principal Threshold (%) for Last Instalment is not working as expected

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792398#comment-16792398
 ] 

Santosh Math commented on FINERACT-302:
---

Did you undestand the description? 

> Principal Threshold (%) for Last Instalment is not working as expected
> --
>
> Key: FINERACT-302
> URL: https://issues.apache.org/jira/browse/FINERACT-302
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Major
>  Labels: Volunteer, fineract-gci, gsoc, p1
> Fix For: 1.5.0
>
> Attachments: Scr-664.png, Screenshot from 2018-12-23 22-13-02.png, 
> Screenshot from 2018-12-23 22-14-34.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2031
> Original Desription:
> 1. Create loan product with out mentioning any thing in the "Principal 
> Threshold (%) for Last Instalment" - by default it is getting set to zero
> Instead it should get set to 50%
> 2, Create a client and submit new loan application wit the above mentioned 
> loan product on 01 Jan 2015 with interest recalculation -> Approve and 
> disburse on same date.
> 3. The last installment is getting collected more amount than EMI.
> If the "Principal Threshold (%) for Last Instalment" is set to zero then then 
> the last installment should never be combined with the previous installment 
> even if the last installment amount is of a very small value.
> But here it is displaying the amount>last installment amount



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-269) Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and Recuring Deposit Account

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-269?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792402#comment-16792402
 ] 

Santosh Math commented on FINERACT-269:
---

[~Ippez] , I didn't understand the description. 

 

[~edcable] , the label is FINERACT-CN?? 

> Add Info Base on Clients Account - Loans, Shares, Fixed Deposit, Loans and 
> Recuring Deposit Account
> ---
>
> Key: FINERACT-269
> URL: https://issues.apache.org/jira/browse/FINERACT-269
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Client
>Reporter: Ippez Roberts
>Assignee: Markus Geiss
>Priority: Major
>  Labels: Fineract-CN, gsoc, p2
> Attachments: Infobase.pdf
>
>
> Infobase
> This allows you to add free-form descriptions or notes to certain accounts. 
> These notes can be unlimited in size and can be used to provide all kind of 
> additional information about any account or its owner.
> Later then whenever this account will be accessed this information will be 
> displayed on the screen as in following example.
> See attachment for visual explanation
>  



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-314) If Tranche disbursement charge payment mode is Account transfer then after first disbursement the charge collection is improper

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-314?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792395#comment-16792395
 ] 

Santosh Math commented on FINERACT-314:
---

[~edcable] , Yes this issue still exists. 

> If Tranche disbursement charge payment mode is Account transfer then after 
> first disbursement the charge collection is improper
> ---
>
> Key: FINERACT-314
> URL: https://issues.apache.org/jira/browse/FINERACT-314
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Minor
>  Labels: gsoc, p2
> Fix For: 1.5.0
>
> Attachments: 91.png, 93.png
>
>
> Reported by  Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2194
> Original Description:
> 1. Create Tranche disbursement charge with Charge Payment Mode as Account 
> transfer.
> 2. Create Tranche loan product with 2 tranches and above created charge 
> attached
> 3. Create Savings product and create a client with active savings product 
> above created.
> 4. For the same above client submit new loan application with the above 
> savings account and Tranche disbursement charge attached while submitting the 
> application, tranche attached on 01 August 2015 and amount is 5000, 2nd 
> tranche on 01 September 2015 and amount is 5000 -> Approve and disburse the 
> first tranche on 01 August 2015.
> > In Summary page displaying as both tranche disbursement charges as due
> > In Repayment schedule is displaying properly
> > In Transactions page and In Charges page both Tranche disbursement charges 
> > are displaying as collected.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-302) Principal Threshold (%) for Last Instalment is not working as expected

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-302?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792397#comment-16792397
 ] 

Santosh Math commented on FINERACT-302:
---

[~sanyam96], I didn't undestand your doubt. 

> Principal Threshold (%) for Last Instalment is not working as expected
> --
>
> Key: FINERACT-302
> URL: https://issues.apache.org/jira/browse/FINERACT-302
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Major
>  Labels: Volunteer, fineract-gci, gsoc, p1
> Fix For: 1.5.0
>
> Attachments: Scr-664.png, Screenshot from 2018-12-23 22-13-02.png, 
> Screenshot from 2018-12-23 22-14-34.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2031
> Original Desription:
> 1. Create loan product with out mentioning any thing in the "Principal 
> Threshold (%) for Last Instalment" - by default it is getting set to zero
> Instead it should get set to 50%
> 2, Create a client and submit new loan application wit the above mentioned 
> loan product on 01 Jan 2015 with interest recalculation -> Approve and 
> disburse on same date.
> 3. The last installment is getting collected more amount than EMI.
> If the "Principal Threshold (%) for Last Instalment" is set to zero then then 
> the last installment should never be combined with the previous installment 
> even if the last installment amount is of a very small value.
> But here it is displaying the amount>last installment amount



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)


[jira] [Commented] (FINERACT-322) Rewarding Early Repayment

2019-03-14 Thread Santosh Math (JIRA)


[ 
https://issues.apache.org/jira/browse/FINERACT-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16792392#comment-16792392
 ] 

Santosh Math commented on FINERACT-322:
---

[~vishwasbabu] , I created the scenario here:

[https://staging.openmf.org/#/viewloanaccount/188]

If we use loan product with flat interest and Interest Recalculation enabled, 
and try to 'Prepay  loan' (1 Feb 2019) , the interest is calculated until 1 Feb 
only , not for full 6 months.

I didn't understand the meaning of the last line of the reporter of this ticket 
in description:

"I would like to see interest outstanding being stopped once the principal has 
been repaid in full."

 

> Rewarding Early Repayment
> -
>
> Key: FINERACT-322
> URL: https://issues.apache.org/jira/browse/FINERACT-322
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Minor
>  Labels: gsoc, p2
>
> Reported by Shepard Chihoro at https://mifosforge.jira.com/browse/MIFOSX-2520
> Original Description:
> MIFOSX does not reward customers who make early repayments on a flat interest 
> calculation method.My normal client contract is has a maximum repayment 
> period of 6 months and a minimum repayment period of 3 months.On 
> disbursement,MIFOSX calculates the interest for the entire 6 months and makes 
> principal and interest for 6 months outstanding.In the event that the 
> customer repays the full principal in 3 months,the customer`s account remains 
> with 3 months interest due.I would like to see interest outstanding being 
> stopped once the principal has been repaid in full.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)