[jira] [Commented] (FINERACT-164) tranche change is not recalculating interest for the installments before the new tranche date.

[Santosh Math (JIRA)]

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

Santosh Math commented on FINERACT-164:
---

Tested it. The issue still exists. 

> tranche change is not recalculating interest for the installments before the 
> new tranche date.
> --
>
> Key: FINERACT-164
> URL: https://issues.apache.org/jira/browse/FINERACT-164
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Sachin Kulkarni
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: after.png, before.png
>
>
> tranche change is not recalculating interest for the installments before the 
> new tranche date.
> for example refer the attached 
> (the loan is 2 tranche loans with 1st tranche disbursed)
> in the attachment 2nd tranche was on 14th june
> so the installment had the interest computed based on 14th tranche 
> principle(Refer "before" screenshot)
> later i will change the tranche date from 14th june to 27th july.
> at this time all the installments from 14th june to 27th july interest will 
> be same as before.(Refer "after" screenshot)
> it should have been recomputed this interest.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-226) If the Center meeting date is modified before submitting JLG loan application then repayment schedule generated is not proper

[Santosh Math (JIRA)]

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

Santosh Math commented on FINERACT-226:
---

The issue is still open

> If the Center meeting date is modified before submitting JLG loan application 
> then repayment schedule generated is not proper
> -
>
> Key: FINERACT-226
> URL: https://issues.apache.org/jira/browse/FINERACT-226
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p2
> Attachments: Change center meeting date.png
>
>
> 1. Create a Center and attache meeting on 01 July 2016 with weekly on Friday, 
> Click on modify meeting and change the meeting day as Wednesday.
> 2. Create a Group under that Center and Create a Client under that group.
> 3. Submit new JLG loan application for a client on 06 July 2016. with weekly 
> loan, approve and disburse on 06 July 2016.
> 4. Click on the repayment schedule
> It is displaying first repayment entry on 08 July 2016, which was previous 
> meeting date. It should display first repayment date as from 13 July 2016



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-219) Edit Data table Entry for client, date format displayed is improper

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-219.
-
Resolution: Fixed

Santosh tested on 16.12.01.RELEASE and working as expected. 

> Edit Data table Entry for client, date format displayed is improper
> ---
>
> Key: FINERACT-219
> URL: https://issues.apache.org/jira/browse/FINERACT-219
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: Github
> Attachments: Edit datable entry.png
>
>
> 1. Create data table for a client. with the data sets as mentioned in the 
> attachment,
> 2. Click on clients-> any created client -> Click on the data table created 
> -> enter the valid inputs and save the page.
> 3. Click on the edit button in the same page.
> > Date and time format displayed is not proper



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-213) Not able to foreclose the loan on current system date moves to Overpaid state.

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-213.
-
Resolution: Fixed

Santosh tested on 16.12.01.RELEASE and working as expected

> Not able to foreclose the loan on current system date moves to Overpaid state.
> --
>
> Key: FINERACT-213
> URL: https://issues.apache.org/jira/browse/FINERACT-213
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> 1. Create a loan product (without interest recalculation), Create a client.
> 2. Disburse loan for  a client on 01 August 2016.
> 3. Fore close the loan on current system date.
> > Loan should get closed but moving to overpaid state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-219) Edit Data table Entry for client, date format displayed is improper

[Santosh Math (JIRA)]

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

Santosh Math commented on FINERACT-219:
---

tested it. This bug is fixed. 

> Edit Data table Entry for client, date format displayed is improper
> ---
>
> Key: FINERACT-219
> URL: https://issues.apache.org/jira/browse/FINERACT-219
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: Github
> Attachments: Edit datable entry.png
>
>
> 1. Create data table for a client. with the data sets as mentioned in the 
> attachment,
> 2. Click on clients-> any created client -> Click on the data table created 
> -> enter the valid inputs and save the page.
> 3. Click on the edit button in the same page.
> > Date and time format displayed is not proper



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-174) Can't select "Escheat Liability" account for deposit products

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-174.
-
Resolution: Fixed

Santosh tested on 16.12.01.RELEASE and it is working as expected. 

> Can't select "Escheat Liability" account for deposit products
> -
>
> Key: FINERACT-174
> URL: https://issues.apache.org/jira/browse/FINERACT-174
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
> Environment: Product Server (https://demo4.openmf.org)
>Reporter: Edward Cable
>Assignee: subramanyasn
>  Labels: confirm, p2
> Attachments: Screen Shot 2016-06-15 at 2.07.47 PM.png
>
>
> Not sure if this is a bug within Fineract or the Community App (perhaps in 
> selection of the account). 
> While attempting to test out the dormant/inactive savings account feature and 
> the ability to escheat funds after a given number of days, I was unable to 
> configure the general ledger account mapping for the Escheat Liability 
> account  for the savings product I was editing.
> To repro, log in to https://demo4.openmf.org with credentials, 
> Mifos/MifosAdmin
> Go to Products >> Savings Products >> Basic Savings Account >> Edit >> 
> Attempt to select an account for Escheat Liability (I newly created Escheated 
> Deposits).
> Click Submit
> See error message that gets displayed:
> field is required
> error.msg.productToAccountMapping.not.found



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: Stretch Parameter -groupId

[Sampath Kumar G]

Hi Zayyad,

I have modified the previous script, you can use the below one.

INSERT INTO `stretchy_parameter` (`parameter_name`, `parameter_variable`,
`parameter_label`, `parameter_displayType`, `parameter_FormatType`,
`parameter_default`, `special`, `selectOne`, `selectAll`, `parameter_sql`,
`parent_id`) VALUES ('GroupnameDependOnStaff', 'groupId', 'Group Name',
'select', 'number', '0', NULL, 'Y', NULL, 'SELECT mg.id id, mg.display_name
name FROM m_group mg WHERE mg.level_id = 2 AND mg.status_enum =300 AND
mg.staff_id = ${loanOfficerId}', (SELECT sp.id from stretchy_parameter sp
where sp.parameter_name = 'loanOfficerIdSelectAll'));

Thanks and regards,
Sampath


​
*Conflux Technologies Pvt Ltd  *

#304, 2nd Floor, 7th Main Road

HRBR Layout 1st Block

Bengaluru, Karnataka, 560043 INDIA


Disclaimer: The information contained in this e-mail message and any
files/attachment transmitted with it is confidential and for the sole use
of the intended recipient(s) or entity identified. If you are not the
intended recipient, please email: supp...@confluxtechnologies.com and
destroy/delete all copies and attachment thereto along with the original
message. Any unauthorised review, use, disclosure, dissemination,
forwarding, printing or copying of this email or any action taken in
reliance on this e-mail is strictly prohibited and is unlawful. The
recipient acknowledges that Conflux Technologies Private Limited or its
subsidiaries and associated companies are unable to exercise control or
ensure or guarantee the integrity of/over the contents of the information
contained in e-mail transmissions. Before opening any attachments, please
check.

On Wed, Jan 18, 2017 at 11:57 PM, Zayyad A. Said <
zay...@intrasofttechnologies.com> wrote:

> Hi Sampath,
>
>
>
> Having executed the script it inserted the field of groupId in
> stretchy_parameter table, however I noticed that when you select Loan
> Officer it populates all groups of the organization instead of filtering
> only the groups handled by that particular officer.
>
>
>
> Is there a way we could modify this script to be filtering the groups as
> is the behaviour with Loan Officer when you select an Office?
>
>
>
> On the same note, kindly also assist with a script I can populate data for
> groups within a center.
>
>
>
> Kindly advise.
>
>
>
> Thanks,
>
>
>
>
>
> *
>
> *Zayyad A. Said | Chairman & C.E.O*
>
>
>
> Cell No.: +254 716 615274 | Skype: *zsaid2011*
>
> Email: zay...@intrasofttechnologies.com
>
>
>
> [image: Email banner]
>
>
>
> *From:* Sampath Kumar G [mailto:samp...@confluxtechnologies.com]
> *Sent:* 18 January 2017 20:41
> *To:* Zayyad A. Said
> *Cc:* Mifos software development; dev@fineract.incubator.apache.org
> *Subject:* RE: Stretch Parameter -groupId
>
>
>
> Zayyad,
>
>
>
> The file is attached to that mail. I dnt no why you can't find it.
>
> Anyhow, I have pasted the same here. Let me know if any issue.
>
>
>
>
>
> INSERT INTO `stretchy_parameter` (`parameter_name`, `parameter_variable`,
> `parameter_label`, `parameter_displayType`, `parameter_FormatType`,
> `parameter_default`, `special`, `selectOne`, `selectAll`, `parameter_sql`,
> `parent_id`) VALUES ('Group name', 'groupId', 'groupId', 'select',
> 'number', '0', NULL, 'Y', NULL, 'SELECT mg.id id, mg.display_name name
> FROM m_group mg WHERE mg.level_id = 2 AND mg.status_enum =300', NULL);
>
>
>
> On Jan 18, 2017 10:05 PM, "Zayyad A. Said"  com> wrote:
>
> Hi Sampath,
>
>
>
> No attachment was in your email, kindly resend.
>
>
>
> Regards;
>
>
>
>
>
> *
>
> *Zayyad A. Said | Chairman & C.E.O*
>
>
>
> Cell No.: +254 716 615274 | Skype: *zsaid2011*
>
> Email: zay...@intrasofttechnologies.com
>
>
>
> [image: Email banner]
>
>
>
> *From:* Sampath Kumar G [mailto:samp...@confluxtechnologies.com]
> *Sent:* 18 January 2017 08:04
> *To:* dev@fineract.incubator.apache.org
> *Cc:* Mifos software development
> *Subject:* Re: Stretch Parameter -groupId
>
>
>
> Hi Zayyad,
>
>
>
> Please find the attachment, insert script for the group as a parameter.
>
>
> Thanks and regards,
>
> Sampath
>
>
>
>
>
> ​
>
> *Conflux Technologies Pvt Ltd  *
>
> #304, 2nd Floor, 7th Main Road
>
> HRBR Layout 1st Block
>
> Bengaluru, Karnataka, 560043 INDIA
>
>
>
> Disclaimer: The information contained in this e-mail message and any
> files/attachment transmitted with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorised review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies ar

RE: Stretch Parameter -groupId

[Zayyad A. Said]

Hi Sampath,

 

Having executed the script it inserted the field of groupId in 
stretchy_parameter table, however I noticed that when you select Loan Officer 
it populates all groups of the organization instead of filtering only the 
groups handled by that particular officer.

 

Is there a way we could modify this script to be filtering the groups as is the 
behaviour with Loan Officer when you select an Office?

 

On the same note, kindly also assist with a script I can populate data for 
groups within a center.

 

Kindly advise.

 

Thanks,

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

Email banner

 

From: Sampath Kumar G [mailto:samp...@confluxtechnologies.com] 
Sent: 18 January 2017 20:41
To: Zayyad A. Said
Cc: Mifos software development; dev@fineract.incubator.apache.org
Subject: RE: Stretch Parameter -groupId

 

Zayyad,

 

The file is attached to that mail. I dnt no why you can't find it.

Anyhow, I have pasted the same here. Let me know if any issue.

 

 

INSERT INTO `stretchy_parameter` (`parameter_name`, `parameter_variable`, 
`parameter_label`, `parameter_displayType`, `parameter_FormatType`, 
`parameter_default`, `special`, `selectOne`, `selectAll`, `parameter_sql`, 
`parent_id`) VALUES ('Group name', 'groupId', 'groupId', 'select', 'number', 
'0', NULL, 'Y', NULL, 'SELECT mg.id id, mg.display_name name FROM m_group mg 
WHERE mg.level_id = 2 AND mg.status_enum =300', NULL);

 

On Jan 18, 2017 10:05 PM, "Zayyad A. Said"  
wrote:

Hi Sampath,

 

No attachment was in your email, kindly resend.

 

Regards;

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

Email banner

 

From: Sampath Kumar G [mailto:samp...@confluxtechnologies.com] 
Sent: 18 January 2017 08:04
To: dev@fineract.incubator.apache.org
Cc: Mifos software development
Subject: Re: Stretch Parameter -groupId

 

Hi Zayyad,

 

Please find the attachment, insert script for the group as a parameter.




Thanks and regards,

Sampath

 

 

​

  Conflux Technologies Pvt Ltd 

#304, 2nd Floor, 7th Main Road 

HRBR Layout 1st Block

Bengaluru, Karnataka, 560043 INDIA

  

 

 

Disclaimer: The information contained in this e-mail message and any 
files/attachment transmitted with it is confidential and for the sole use of 
the intended recipient(s) or entity identified. If you are not the intended 
recipient, please email:   
supp...@confluxtechnologies.com and destroy/delete all copies and attachment 
thereto along with the original message. Any unauthorised review, use, 
disclosure, dissemination, forwarding, printing or copying of this email or any 
action taken in reliance on this e-mail is strictly prohibited and is unlawful. 
The recipient acknowledges that Conflux Technologies Private Limited or its 
subsidiaries and associated companies are unable to exercise control or ensure 
or guarantee the integrity of/over the contents of the information contained in 
e-mail transmissions. Before opening any attachments, please check.

 

On Tue, Jan 17, 2017 at 7:38 PM, Zayyad A. Said 
 wrote:

Devs,

 

I am trying to develop a report which contains groups.

 

I need to set Group as parameter to pass to Pentaho as we need report per group.

 

I don’t see groupId in the table stretchy_parameter, how then can I use Group 
as parameter in my report?

 

Kindly but urgently advise on this.

 

Thanks & Regards;

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

 

 

RE: Stretch Parameter -groupId

[Sampath Kumar G]

Zayyad,

The file is attached to that mail. I dnt no why you can't find it.
Anyhow, I have pasted the same here. Let me know if any issue.


INSERT INTO `stretchy_parameter` (`parameter_name`, `parameter_variable`,
`parameter_label`, `parameter_displayType`, `parameter_FormatType`,
`parameter_default`, `special`, `selectOne`, `selectAll`, `parameter_sql`,
`parent_id`) VALUES ('Group name', 'groupId', 'groupId', 'select',
'number', '0', NULL, 'Y', NULL, 'SELECT mg.id id, mg.display_name name FROM
m_group mg WHERE mg.level_id = 2 AND mg.status_enum =300', NULL);

On Jan 18, 2017 10:05 PM, "Zayyad A. Said" 
wrote:

> Hi Sampath,
>
>
>
> No attachment was in your email, kindly resend.
>
>
>
> Regards;
>
>
>
>
>
> *
>
> *Zayyad A. Said | Chairman & C.E.O*
>
>
>
> Cell No.: +254 716 615274 | Skype: *zsaid2011*
>
> Email: zay...@intrasofttechnologies.com
>
>
>
> [image: Email banner]
>
>
>
> *From:* Sampath Kumar G [mailto:samp...@confluxtechnologies.com]
> *Sent:* 18 January 2017 08:04
> *To:* dev@fineract.incubator.apache.org
> *Cc:* Mifos software development
> *Subject:* Re: Stretch Parameter -groupId
>
>
>
> Hi Zayyad,
>
>
>
> Please find the attachment, insert script for the group as a parameter.
>
>
> Thanks and regards,
>
> Sampath
>
>
>
>
>
> ​
>
> *Conflux Technologies Pvt Ltd  *
>
> #304, 2nd Floor, 7th Main Road
>
> HRBR Layout 1st Block
>
> Bengaluru, Karnataka, 560043 INDIA
>
>
>
> Disclaimer: The information contained in this e-mail message and any
> files/attachment transmitted with it is confidential and for the sole use
> of the intended recipient(s) or entity identified. If you are not the
> intended recipient, please email: supp...@confluxtechnologies.com and
> destroy/delete all copies and attachment thereto along with the original
> message. Any unauthorised review, use, disclosure, dissemination,
> forwarding, printing or copying of this email or any action taken in
> reliance on this e-mail is strictly prohibited and is unlawful. The
> recipient acknowledges that Conflux Technologies Private Limited or its
> subsidiaries and associated companies are unable to exercise control or
> ensure or guarantee the integrity of/over the contents of the information
> contained in e-mail transmissions. Before opening any attachments, please
> check.
>
>
>
> On Tue, Jan 17, 2017 at 7:38 PM, Zayyad A. Said <
> zay...@intrasofttechnologies.com> wrote:
>
> Devs,
>
>
>
> I am trying to develop a report which contains groups.
>
>
>
> I need to set Group as parameter to pass to Pentaho as we need report per
> group.
>
>
>
> I don’t see groupId in the table stretchy_parameter, how then can I use
> Group as parameter in my report?
>
>
>
> Kindly but urgently advise on this.
>
>
>
> Thanks & Regards;
>
>
>
>
>
> *
>
> *Zayyad A. Said | Chairman & C.E.O*
>
>
>
> Cell No.: +254 716 615274 | Skype: *zsaid2011*
>
> Email: zay...@intrasofttechnologies.com
>
>
>
>
>
>
>

RE: Stretch Parameter -groupId

[Zayyad A. Said]

Hi Sampath,

 

No attachment was in your email, kindly resend.

 

Regards;

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

Email banner

 

From: Sampath Kumar G [mailto:samp...@confluxtechnologies.com] 
Sent: 18 January 2017 08:04
To: dev@fineract.incubator.apache.org
Cc: Mifos software development
Subject: Re: Stretch Parameter -groupId

 

Hi Zayyad,

 

Please find the attachment, insert script for the group as a parameter.




Thanks and regards,

Sampath

 

 

​

  Conflux Technologies Pvt Ltd 

#304, 2nd Floor, 7th Main Road 

HRBR Layout 1st Block

Bengaluru, Karnataka, 560043 INDIA

  

 

 

Disclaimer: The information contained in this e-mail message and any 
files/attachment transmitted with it is confidential and for the sole use of 
the intended recipient(s) or entity identified. If you are not the intended 
recipient, please email:   
supp...@confluxtechnologies.com and destroy/delete all copies and attachment 
thereto along with the original message. Any unauthorised review, use, 
disclosure, dissemination, forwarding, printing or copying of this email or any 
action taken in reliance on this e-mail is strictly prohibited and is unlawful. 
The recipient acknowledges that Conflux Technologies Private Limited or its 
subsidiaries and associated companies are unable to exercise control or ensure 
or guarantee the integrity of/over the contents of the information contained in 
e-mail transmissions. Before opening any attachments, please check.

 

On Tue, Jan 17, 2017 at 7:38 PM, Zayyad A. Said 
 wrote:

Devs,

 

I am trying to develop a report which contains groups.

 

I need to set Group as parameter to pass to Pentaho as we need report per group.

 

I don’t see groupId in the table stretchy_parameter, how then can I use Group 
as parameter in my report?

 

Kindly but urgently advise on this.

 

Thanks & Regards;

 

 

***

Zayyad A. Said | Chairman & C.E.O

 

Cell No.: +254 716 615274 | Skype: zsaid2011

Email: zay...@intrasofttechnologies.com 

 

 

 

[jira] [Updated] (FINERACT-316) Should allow to add loan transactions after Account Closure date

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-316:
--
Labels: confirm p1  (was: )

> Should allow to add loan transactions after Account Closure date
> 
>
> Key: FINERACT-316
> URL: https://issues.apache.org/jira/browse/FINERACT-316
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: 111.png, 112.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2241
> Original Description:
> 1. Disburse the loan on 05 August 2014 and make repayment till 18 August 2015.
> 2. Create Account Closing entries on 02 September 2015 and then make 
> repayment which is due on 01 September 2015.
> > Not allowing to make repayment displayed error message as "Accounting has 
> > been closed for this branch as of `2015-09-02`." - Working as expected.
> 3. Make repayment on 03 September 2015 - it should allow to make repayment 
> but it is not allowing there also.
> 4. Make repayment on current system date - then it is allowing to make 
> repayment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-313) For Multiple tranche Loans with Equal Principal Payments after submitting the loan application Principal due is not calculating properly

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-313:
--
Labels: confirm p1  (was: )

> For Multiple tranche Loans with Equal Principal Payments after submitting the 
> loan application Principal due is not calculating properly
> 
>
> Key: FINERACT-313
> URL: https://issues.apache.org/jira/browse/FINERACT-313
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: 42.png
>
>
> Reported by Subramanya  at https://mifosforge.jira.com/browse/MIFOSX-2130
> Original Description:
> 1. Create a Loan product with following datasets
> Repayment Strategy:RBI (India)
> Repayments:12 every 1 Months
> Amortization:Equal principal payments
> Interest:12 per annum (1% Per month):Declining Balance
> Interest Calculation Period:Daily
> Interest Type:Declining Balance
> Recalculate Interest Yes
> Days in year: Actual
> Days in month: Actual
> Interest recalculation compounding on:None
> Advance payments adjustment type:Reduce number of installments
> Frequency for recalculate Outstanding Principal: Every -1 days
> Max Tranche Count:2,
> 2.Submit new loan application for a client on 01 January 2015 with first 
> tranche on same date and 2nd Tranche on 01 March 2015, each with 5000 amount.
> > For 01 February 2015 and 01 March 2015 the principal due should be 416.67 
> > (ie 5000/12). and From 01 April2015 to 01 January 2016 principal due should 
> > be 916.66 (ie 9166.6/10).
> But here it is calculating differently as a result for the last installment 
> principal due is more.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-312) For Loan with interest recalculation periodic accrual with respect to current date is not getting modified after repayment in Transaction page

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-312:
--
Labels: p1  (was: )

> For Loan with interest recalculation periodic accrual with respect to current 
> date is not getting modified after repayment in Transaction page
> --
>
> Key: FINERACT-312
> URL: https://issues.apache.org/jira/browse/FINERACT-312
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: 35.png, 36.png, 37.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2119
> Original Description:
> 1. Create a loan product with following datasets:
> Principal: 1, no. of Installments: 12, repaid every 1 month, Nominal 
> interest rate: 1%pm,Amortization: Equal installments, Interest Method: 
> Declining Balance, Interest Calculation Period: Same as repayment 
> period,Repayment Strategy:RBI (India),Recalculate Interest: Yes,Advance 
> payments adjustment type: Reduce number of installments, Pre-closure interest 
> calculation rule: Calculate till pre closure date, Interest recalculation 
> compounding on:None, Frequency for recalculate Outstanding Principal: Same as 
> repayment period, with accounting enabled for periodic accrual.
> 2. Submit new loan application for a client on 01 March 2015 approve and 
> disburse on same date.
> 3. Click on Admin -> system -> Scheduler job - run scheduler job "Add 
> Periodic Accrual Transactions".
> 4. Navigate back to Transactions page and verify the accrued interest as on 
> current date.
> 5. Make first repayment on exact due date then verify the transaction page 
> the accrued interest as on current date is not modified.
> > The accrued interest as on current date is not getting modified even after 
> > multiple repayments. 
> Please refer the screen shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-311) Issue With 'Payment Due On Non Working Days'

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-311:
--
Labels: p1  (was: )

> Issue  With 'Payment Due On Non Working Days'
> -
>
> Key: FINERACT-311
> URL: https://issues.apache.org/jira/browse/FINERACT-311
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: System
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
> Attachments: paymentDueOnNonWorkingDay.png
>
>
> 1. Go To Admin>>Organization and click on Working Days
> 2.  Un-check Sunday.
> 3. Change  'Payment Due On Non Working Days' from 'same day' to 'Move to Next 
> Working Day' or any other parameters.
> 4. Click on Submit button.
> 5. Go Back to Admin>>Organization>>Working Days
> You can observe that   'Payment Due On Non Working Days' remains as 'same 
> day' though we changed it to other parameters like 'Move to Next Working Day' 
> , etc.
> Note: This issue doesn't appear every time but still exists. You can check it 
> by frequently changing 'Payment Due On Non Working  Days'



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FINERACT-310) Editing 'Product Mix' Not Working

[Edward Cable (JIRA)]

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

Edward Cable resolved FINERACT-310.
---
Resolution: Fixed

Fix is complete, shipping in upcoming release. 

> Editing  'Product  Mix' Not  Working
> 
>
> Key: FINERACT-310
> URL: https://issues.apache.org/jira/browse/FINERACT-310
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
> Attachments: EditProductMix.png
>
>
> 1. Go to Admin>>Products and click on 'Product Mix'
> 2. Create a product mix for a given loan product with allowed and restricted 
> product access.
> 3. And  then  Edit  the  product mix with different allowed and restricted 
> products access and click on 'Submit' button.
> Clicking  on  'Submit' button doesn't show any effect. 
> Check the screenshot attached with this issue. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-306) After Late repayment - interest is not computing properly in Repayment schedule page for the loan with interest recalculation

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-306:
--
Labels: confirm p1  (was: )

> After Late repayment - interest is not computing properly in Repayment 
> schedule page for the loan with interest recalculation
> -
>
> Key: FINERACT-306
> URL: https://issues.apache.org/jira/browse/FINERACT-306
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: 21.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2086
> Original Description:
> 1. Create Loan product with following data-sets:
> Principal:10,000,
> Number of Repayments: 12
> Repay Every:  1  Months
> Nominal Interest Rate:1  Per month
> Minimum days between disbursal and first repayment date   
> Settings:
> Amortization: Equal installments
> Interest Method: Declining Balance
> Interest Calculation Period:  Daily
> Repayment Strategy: RBI (India)
> Days in year: Actual
> Days in month:Actual
> Principal Threshold (%) for Last Installment: 0
> Allow fixing of the installment amount:No
> Interest Recalculation
> Recalculate Interest: Yes
> Advance payments adjustment type: Reduce EMI amount
> Pre-closure interest calculation rule:Calculate till pre-closure date
> Interest recalculation compounding on:None
> Frequency for recalculate Outstanding Principal:  Daily
> Frequency Interval for recalculation: 1
> Frequency Date for recalculation: 01-Jan-15
> Is Arrears recognization based on original schedule:No
> Loan Tranche Details  
> Enable Multiple Disbursal:TRUE
> Maximum Tranche count:1
> Maximum allowed outstanding balance:1
> 2. Create a Client and submit new loan application for a client on 01 January 
> 2015, with tranche details as date 01 January 2015 and amount 1 -> 
> Approve and disburse on 01 January 2015.
> 3. Make repayment on 15 February 2015 (repayment due on 01 February 2015 but 
> made late repayment).
> > Interest calculated after 1st repayment is not proper.
> Please refer the screen shot attached.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-307) Accruals accounting does not accrue income on loans closed prematurely

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-307:
--
Labels: p1  (was: )

> Accruals accounting does not accrue income on loans closed prematurely
> --
>
> Key: FINERACT-307
> URL: https://issues.apache.org/jira/browse/FINERACT-307
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-2093
> Original Description:
> If a customer makes the final payment before the end of the loan schedule the 
> loan status changes to closed, and the balance reports 0, which is correct. 
> These loans are non-recalculating and accrue interest in line with their 
> schedules (periodic). As such all interest portions are booked into the 
> Interest Receivable account.
> However because of the closed status the accruals batch job no longer 
> generates the periodic accruals for this loan (query excludes any status 
> which is not active). As a result a part of this income will remain in the 
> Interest receivable account indefinitely, which is not the expected 
> behaviour. We would either expect the accruals to continue in line with the 
> schedule, or for the accrual to be generated alongside the final (closing) 
> transaction of the loan.
> The quick-fix for this is to adjust the batch job to look not just look at 
> loan status but also at any loan where the interest accrual date is smaller 
> than the expected maturity date.
> As a permanent fix we should investigate whether new accounting types/rules 
> need to be defined for this scenario to also book this prepaid income as a 
> liability instead of an asset account, such as Prepaid Interest received.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-304) Issue with Maximum allowed outstanding balance in loans

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-304:
--
Labels: beginner confirm p2  (was: beginner p2)

> Issue with Maximum allowed outstanding balance in loans
> ---
>
> Key: FINERACT-304
> URL: https://issues.apache.org/jira/browse/FINERACT-304
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: beginner, confirm, p2
>
> Reported by Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2077
> Original Description:
> Create a new tranche loan application.
> With Principal as 10,000 and maximum allowed outstanding balance as 9,000.
> Enter the first tranche with tranche amount as 10,000.Still able to submit.
> Tranche amount should not exceed maximum allowed outstanding balance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-304) Issue with Maximum allowed outstanding balance in loans

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-304:
--
Labels: beginner p2  (was: )

> Issue with Maximum allowed outstanding balance in loans
> ---
>
> Key: FINERACT-304
> URL: https://issues.apache.org/jira/browse/FINERACT-304
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: beginner, p2
>
> Reported by Chandrika at https://mifosforge.jira.com/browse/MIFOSX-2077
> Original Description:
> Create a new tranche loan application.
> With Principal as 10,000 and maximum allowed outstanding balance as 9,000.
> Enter the first tranche with tranche amount as 10,000.Still able to submit.
> Tranche amount should not exceed maximum allowed outstanding balance.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-303) "% Loan Amount + Interest or %Amount" if collected as disbursement fees it is not working as expected

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-303:
--
Labels: confirm p1  (was: )

> "% Loan Amount + Interest or %Amount" if collected as disbursement fees it is 
> not working as expected
> -
>
> Key: FINERACT-303
> URL: https://issues.apache.org/jira/browse/FINERACT-303
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: Scr-689.png, Scr-690.png
>
>
> Reported  by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-2056
> Original  Description:
> 1. Create a charge of 1% as Disbursement fees as "% Loan Amount + Interest or 
> % Approved Amount".
> 2. Create a loan product with 2 tranche and amount as 1 and add above 
> mentioned charge to it.
> 3. Create a client and submit new loan application with above mentioned loan 
> product on 01 May 2015 with 2 tranches added
> first tranche on 01 May 2015 and amount as 5000.
> Second tranche on 15 May 2015 and amount as 5000.
> 4. Approve and disburse first tranche on 01 May 2015.
> > Since charge applied on %loan amount total+interest, it should collect 
> > charge as 109.39,
> but it is collecting 59.39.
> 5. After making the second disbursement on 15 May 2015 it is getting 
> collected 109.39,
> but in charges it is displaying as 50 outstanding.
> 6. If the disbursement amount is modified during loan approval then in 
> repayment schedule the charge is not getting updated. (eg. submit loan 
> application with first tranch 5000 and second tranch 5000, during approval 
> change amount as 4000 and 4000 for first and second tranch. then %amount 
> charge is displaying with respect to first tranche amount only.)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-302:
--
Labels: fineract-gci p2  (was: fineract-gci)

> 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
>  Labels: fineract-gci, p2
> Attachments: Scr-664.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
(v6.3.4#6332)

[jira] [Updated] (FINERACT-301) Force password reset days is not working as expected

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-301:
--
Labels: confirm p2  (was: )

> Force password reset days is not working as expected
> 
>
> Key: FINERACT-301
> URL: https://issues.apache.org/jira/browse/FINERACT-301
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> Reported by Sangamesh at https://mifosforge.jira.com/browse/MIFOSX-2022
> Original Description:
> Existing: 
> On enabling "force-password-reset-days" in configuration, it takes the 
> default value(days) which is 0(zero). If the user logs out and tries to 
> login, it wont allow user to login. This was raised by Frank from "Jambo 
> capital Initiative".
> Expected: 
> Should not allow to change from enable to disable if the value is 0(zero). If 
> it should be allowed, then it should allow to change the password immediately 
> at the time of login.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-300) Not able to submitting the collection sheet on repayment rescheduled date if the repayment date falls on Holiday

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-300:
--
Labels: p2  (was: )

> Not able to submitting the collection sheet on repayment rescheduled date if 
> the repayment date falls on Holiday
> 
>
> Key: FINERACT-300
> URL: https://issues.apache.org/jira/browse/FINERACT-300
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p2
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1953
> Original Description:
> 1. Create Center and attach meeting to it on 01 March 2015 every 1 month.
> 2. Create group and Client under that center
> 3. Create holiday on 01 April 2015 and reschedule repayment on 31 March 2015.
> 4. Submit new JLG loan for the client on 01 March 2015 repaid every 1 month 
> so that first repayment falls on 01 April 2015 -> Approve and disburse the 
> loan
> 4. Click on collection sheet and enter date as 31 March 2015
> > Not able to submit the collection sheet as error message displayed as 
> > "Selected calendar date is not a valid recurrence date".
> 5. If in the collection sheet the date is selected as 01 April 2015 able to 
> submit the collection sheet but in the repayment schedule it will display 
> paid date as 01 April 2015.
> Ideally if Interest recalculation with daily rest frequency since repayment 
> is rescheduled on 31 March the interest should get calculated up to 30 March 
> and get collected on 31 March. But here the interest is getting collected 
> upto 31st of March.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-299) "Advance search" functionality broken

[Edward Cable (JIRA)]

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

Edward Cable closed FINERACT-299.
-
Resolution: Duplicate

> "Advance search" functionality broken
> -
>
> Key: FINERACT-299
> URL: https://issues.apache.org/jira/browse/FINERACT-299
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Surveys, System
>Reporter: Santosh Math
>Assignee: Markus Geiss
>
> Reported by Vishwas Babu at https://mifosforge.jira.com/browse/MIFOSX-1901
> Original Description:
> This functionality no longer seems to be working, the following changes need 
> to be made for the same
> 1) remove from shortcuts as this is not a commonly used functionality
> 2) The original aim of this functionality was to allowing mapping fund 
> sources to loan accounts in bulk (very useful for organizations where loans 
> are usually funded by Banks etc)
> Move the same under Organization tab with the heading "Fund Mapping" and 
> description "Bulk entry screen for mapping fund sources to loans"
> 3) The entire functionality seems to be broken, fix the same



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-336) Fund Mapping page Points to Advanced Search page

[Edward Cable (JIRA)]

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

Edward Cable commented on FINERACT-336:
---

See comments from Vishwas:

Reported by Vishwas Babu at https://mifosforge.jira.com/browse/MIFOSX-1901
Original Description:
This functionality no longer seems to be working, the following changes need to 
be made for the same
1) remove from shortcuts as this is not a commonly used functionality
2) The original aim of this functionality was to allowing mapping fund sources 
to loan accounts in bulk (very useful for organizations where loans are usually 
funded by Banks etc)
Move the same under Organization tab with the heading "Fund Mapping" and 
description "Bulk entry screen for mapping fund sources to loans"
3) The entire functionality seems to be broken, fix the same

> Fund Mapping page Points to Advanced Search page
> 
>
> Key: FINERACT-336
> URL: https://issues.apache.org/jira/browse/FINERACT-336
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Organization
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Critical
> Attachments: fundmapping.png
>
>
> Reported by Ed Cable at https://mifosforge.jira.com/browse/MIFOSX-2795
> Original Description:
> Hi all,
> I think this bug has been existent for several months now as we actually 
> documented it as intended functionality at 
> https://mifosforge.jira.com/wiki/display/docs/Fund+Mapping
> If you got to Admin >> Organization >> Fund Mapping, clicking the link takes 
> you to
> https://demo4.openmf.org/#/advsearch
> rather than the intended page on fund mapping (i'm not sure which it is).
> On a similar note, I don't think this advance search link is accessible from 
> the search menu although it should be there or in the quick links.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-298) If more charge is paid in Individual collection sheet is getting collected as advance for the next repayments

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-298:
--
Labels: confirm p3  (was: )

> If more charge is paid in Individual collection sheet is getting collected as 
> advance for the next repayments
> -
>
> Key: FINERACT-298
> URL: https://issues.apache.org/jira/browse/FINERACT-298
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p3
> Attachments: Scr-557.png, Scr-558.png, Scr-559.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1867
> Original Description:
> 1. Submit new loan application for a client on 01 November 2014 -> Approve 
> and Disburse on same date, attache a specified due date charge on 05 November 
> 2014 and amount as 100.
> 2. Run Individual collection sheet in which enter meeting calendar date as 01 
> December 2014 -> Click on collection sheet.
> 3. In same page total due and charges displayed for 01 December 2014.
> 4. In charges field enter amount as 200 (edit 100) and click on submit button.
> 5. Navigate back to repayment schedule page of that particular client loan.
> In Loan repayment page the amount get repaid on 01 December 2014, but the 
> charges paid excess (100 more than defined) is getting collected as advance 
> for the next repayment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-298) If more charge is paid in Individual collection sheet is getting collected as advance for the next repayments

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-298:
--
Component/s: Loan

> If more charge is paid in Individual collection sheet is getting collected as 
> advance for the next repayments
> -
>
> Key: FINERACT-298
> URL: https://issues.apache.org/jira/browse/FINERACT-298
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
> Attachments: Scr-557.png, Scr-558.png, Scr-559.png
>
>
> Reported by Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1867
> Original Description:
> 1. Submit new loan application for a client on 01 November 2014 -> Approve 
> and Disburse on same date, attache a specified due date charge on 05 November 
> 2014 and amount as 100.
> 2. Run Individual collection sheet in which enter meeting calendar date as 01 
> December 2014 -> Click on collection sheet.
> 3. In same page total due and charges displayed for 01 December 2014.
> 4. In charges field enter amount as 200 (edit 100) and click on submit button.
> 5. Navigate back to repayment schedule page of that particular client loan.
> In Loan repayment page the amount get repaid on 01 December 2014, but the 
> charges paid excess (100 more than defined) is getting collected as advance 
> for the next repayment.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-297) cannot remove all Mapping Fees,Penalties to Income Accounts

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-297:
--
Labels: confirm p2  (was: )

> cannot remove all Mapping Fees,Penalties to Income Accounts
> ---
>
> Key: FINERACT-297
> URL: https://issues.apache.org/jira/browse/FINERACT-297
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Accounting
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> Reported by  andrewDzakpasu at https://mifosforge.jira.com/browse/MIFOSX-1864
> Original Description:
> create a loan product or go to a loan product to edit.
> Go to Advanced Accounting Rule now add Map Penalties to Specific Income 
> Accounts, add two mappings and save.
> Now edit the same product and remove the two mappings and save.
> Now go back to the product and you will see that the two mappings are still 
> there no changes has happened. This could be due to the empty array of the 
> mappings sent to the api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-297) cannot remove all Mapping Fees,Penalties to Income Accounts

[Edward Cable (JIRA)]

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

Edward Cable commented on FINERACT-297:
---

View comments on original issue and apply fix suggested by Andrew and Emmanuel. 

> cannot remove all Mapping Fees,Penalties to Income Accounts
> ---
>
> Key: FINERACT-297
> URL: https://issues.apache.org/jira/browse/FINERACT-297
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Accounting
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> Reported by  andrewDzakpasu at https://mifosforge.jira.com/browse/MIFOSX-1864
> Original Description:
> create a loan product or go to a loan product to edit.
> Go to Advanced Accounting Rule now add Map Penalties to Specific Income 
> Accounts, add two mappings and save.
> Now edit the same product and remove the two mappings and save.
> Now go back to the product and you will see that the two mappings are still 
> there no changes has happened. This could be due to the empty array of the 
> mappings sent to the api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-297) cannot remove all Mapping Fees,Penalties to Income Accounts

[Edward Cable (JIRA)]

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

Edward Cable commented on FINERACT-297:
---

See:
andrew andrewDzakpasu added a comment - 26/Feb/15 12:35 PM Chandrika can you 
fix this bug on this public void updatePaymentChannelToFundSourceMappings by 
changing this if (paymentChannelMappingArray != null && 
paymentChannelMappingArray.size() > 0) to if (paymentChannelMappingArray != 
null )

> cannot remove all Mapping Fees,Penalties to Income Accounts
> ---
>
> Key: FINERACT-297
> URL: https://issues.apache.org/jira/browse/FINERACT-297
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Accounting
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p2
>
> Reported by  andrewDzakpasu at https://mifosforge.jira.com/browse/MIFOSX-1864
> Original Description:
> create a loan product or go to a loan product to edit.
> Go to Advanced Accounting Rule now add Map Penalties to Specific Income 
> Accounts, add two mappings and save.
> Now edit the same product and remove the two mappings and save.
> Now go back to the product and you will see that the two mappings are still 
> there no changes has happened. This could be due to the empty array of the 
> mappings sent to the api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-295) Unable to Inactivate Annual (or any other recurring fees) fees under certain conditions

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-295:
--
Labels: confirm fineract p2  (was: fineract)

> Unable to Inactivate Annual (or any other recurring fees) fees under certain 
> conditions
> ---
>
> Key: FINERACT-295
> URL: https://issues.apache.org/jira/browse/FINERACT-295
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, fineract, p2
>
> Reported by Vishwas Babu at https://mifosforge.jira.com/browse/MIFOSX-1841
> Original Description:
> The restriction put in for waiving annual fees (or any other recurring fee is 
> that the fee should not already be due before it can be waived)
> So, for example, I create an annual fee applicable on 15th January, the 
> following workflow results in an error
> 1) Create a savings account on 2012
> 2) Try to waive the fee as of today (todays date is 14th Jan 2015). I should 
> not be able waive the fee since two instances of the fee 15th Jan 2013 and 
> 15th Jan 2014 have already been applied
> 3) Next pay the fees for 2013 and 2014
> 4) Now the next due fee is as of tomorrow (Jan 15 2015). So If I inactivate 
> the fee today, i.e on 14th Jan we see an error saying the fee cannot be 
> inactivated as it has already been applied. The error is invalid as the next 
> due date of the fee is tomorrow, so the fee has not yet become due
> subramanya Can you please test this out on 1.26 and ensure that you are able 
> to reproduce the same.
> Finally before making the issue as fixed, test out this bit of functionality 
> in entirety as there could be regression issues



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-297) cannot remove all Mapping Fees,Penalties to Income Accounts

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-297:
--
Summary: cannot remove all Mapping Fees,Penalties to Income Accounts  (was: 
cannot remove all Mappping Fees,Penalties to Income Accounts)

> cannot remove all Mapping Fees,Penalties to Income Accounts
> ---
>
> Key: FINERACT-297
> URL: https://issues.apache.org/jira/browse/FINERACT-297
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Accounting
>Reporter: Santosh Math
>Assignee: Markus Geiss
>
> Reported by  andrewDzakpasu at https://mifosforge.jira.com/browse/MIFOSX-1864
> Original Description:
> create a loan product or go to a loan product to edit.
> Go to Advanced Accounting Rule now add Map Penalties to Specific Income 
> Accounts, add two mappings and save.
> Now edit the same product and remove the two mappings and save.
> Now go back to the product and you will see that the two mappings are still 
> there no changes has happened. This could be due to the empty array of the 
> mappings sent to the api



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-292) Collection sheet - loan charge is not working as expected

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-292:
--
Labels: p2  (was: )

> Collection sheet - loan charge is not working as expected
> -
>
> Key: FINERACT-292
> URL: https://issues.apache.org/jira/browse/FINERACT-292
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p2
>
> Reported by Sangamesh at https://mifosforge.jira.com/browse/MIFOSX-1792
> Original Description:
> Existing:
> In collection sheet:
> If there is a loan charge & if it is collected at the time disbursement. Then 
> it is showing in the total of the collection sheet page, but it is not 
> displaying for which client.
> Expected: 
> If there is a loan charge & if it is collected at the time disbursement. Then 
> a) It should show for the amount in respect client. then in the total. 
> b) But it should not only display the charges. It should also display the 
> respective loan disbursement amount. Otherwise the charges should also not to 
> be displayed. Since this creates a confusion for doing the collection sheet.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-289) Unable to view general ledger report even with correct permissions

[Edward Cable (JIRA)]

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

Edward Cable commented on FINERACT-289:
---

See comments from [~rajuan] on thread at 
https://www.mail-archive.com/mifos-users@lists.sourceforge.net/msg05975.html

> Unable to view general ledger report even with correct permissions
> --
>
> Key: FINERACT-289
> URL: https://issues.apache.org/jira/browse/FINERACT-289
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: confirm, fineract-gci, p3
> Attachments: Screen Shot 2016-12-09 at 2.32.35 AM.png, Screen Shot 
> 2016-12-09 at 2.33.15 AM.png
>
>
> There is a permission code mismatch regarding the General Ledger report as 
> reported by Upendo and discussed on the lists.
> Expected Behavior 
> Accountant with necessary permissions to view general ledger report should be 
> able to view it.
> On the Demo Server (https://demo3.openmf.org) with credentials 
> mifos/password, the following has been done.
> 1) Navigated to System >> Roles and Permissions >> Created new role called 
> accountant with permissions to "view general ledger report" under "report" 
> and "read report" under "configuration" 
> 2) Created New user with user id - accountant and password nonsecure has been 
> created and given 
> 3) Logged in as accountant
> 4) Clicked reports and accounting to view general ledger report. I should see 
> General Ledger Report, be able to click and then input parameters to be able 
> to run and view general ledger report. 
> Actual Behavior
> * Nothing is displayed when clicking Accounting under Reports tab so don't 
> have proper permissions to view GL report. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-289) Unable to view general ledger report even with correct permissions

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-289:
--
Labels: confirm fineract-gci p3  (was: fineract-gci p3)

> Unable to view general ledger report even with correct permissions
> --
>
> Key: FINERACT-289
> URL: https://issues.apache.org/jira/browse/FINERACT-289
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: confirm, fineract-gci, p3
> Attachments: Screen Shot 2016-12-09 at 2.32.35 AM.png, Screen Shot 
> 2016-12-09 at 2.33.15 AM.png
>
>
> There is a permission code mismatch regarding the General Ledger report as 
> reported by Upendo and discussed on the lists.
> Expected Behavior 
> Accountant with necessary permissions to view general ledger report should be 
> able to view it.
> On the Demo Server (https://demo3.openmf.org) with credentials 
> mifos/password, the following has been done.
> 1) Navigated to System >> Roles and Permissions >> Created new role called 
> accountant with permissions to "view general ledger report" under "report" 
> and "read report" under "configuration" 
> 2) Created New user with user id - accountant and password nonsecure has been 
> created and given 
> 3) Logged in as accountant
> 4) Clicked reports and accounting to view general ledger report. I should see 
> General Ledger Report, be able to click and then input parameters to be able 
> to run and view general ledger report. 
> Actual Behavior
> * Nothing is displayed when clicking Accounting under Reports tab so don't 
> have proper permissions to view GL report. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-289) Unable to view general ledger report even with correct permissions

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-289:
--
Labels: fineract-gci p3  (was: fineract-gci)

> Unable to view general ledger report even with correct permissions
> --
>
> Key: FINERACT-289
> URL: https://issues.apache.org/jira/browse/FINERACT-289
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: fineract-gci, p3
> Attachments: Screen Shot 2016-12-09 at 2.32.35 AM.png, Screen Shot 
> 2016-12-09 at 2.33.15 AM.png
>
>
> There is a permission code mismatch regarding the General Ledger report as 
> reported by Upendo and discussed on the lists.
> Expected Behavior 
> Accountant with necessary permissions to view general ledger report should be 
> able to view it.
> On the Demo Server (https://demo3.openmf.org) with credentials 
> mifos/password, the following has been done.
> 1) Navigated to System >> Roles and Permissions >> Created new role called 
> accountant with permissions to "view general ledger report" under "report" 
> and "read report" under "configuration" 
> 2) Created New user with user id - accountant and password nonsecure has been 
> created and given 
> 3) Logged in as accountant
> 4) Clicked reports and accounting to view general ledger report. I should see 
> General Ledger Report, be able to click and then input parameters to be able 
> to run and view general ledger report. 
> Actual Behavior
> * Nothing is displayed when clicking Accounting under Reports tab so don't 
> have proper permissions to view GL report. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-287) Unnecessary reversal of transactions when making 2 recovery payments on same day

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-287:
--
Labels: confirm p1  (was: fineract-gci)

> Unnecessary reversal of transactions when making 2 recovery payments on same 
> day
> 
>
> Key: FINERACT-287
> URL: https://issues.apache.org/jira/browse/FINERACT-287
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> Reported  by Sander at https://mifosforge.jira.com/browse/MIFOSX-1637
> Original Description: 
> When you make 2 recovery payments into the same (written-off) loan on the 
> same day, the second payment will (unnecessarily) reverse the first one and 
> then book it again. This is not necessary and clutters up the journal 
> entries. This might also apply to other actions, such as regular repayments.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-283) Loan if Closed (as rescheduled) then no journal entries are getting created

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-283:
--
Labels: p2  (was: )

> Loan if Closed (as rescheduled) then no journal entries are getting created
> ---
>
> Key: FINERACT-283
> URL: https://issues.apache.org/jira/browse/FINERACT-283
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p2
>
> Reported by  Subramanya at https://mifosforge.jira.com/browse/MIFOSX-1521
> Original Description:
> 1. Disburse a loan for a client with cash based accounting - Journal entries 
> got created for the loan after disbursement.
> 2. If the same loan is Closed (As rescheduled) then there is no Journal 
> entries got created for that loan, and from accounting point of view still 
> loan is in active state.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-282) Backdate before Interest Waiver corrupts loan balances

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-282:
--
Labels: confirm p1  (was: )

> Backdate before Interest Waiver corrupts loan balances
> --
>
> Key: FINERACT-282
> URL: https://issues.apache.org/jira/browse/FINERACT-282
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p1
> Attachments: Screenshot 1.png, Screenshot #2.png, Screenshot #3.png, 
> Screenshot #4.png
>
>
> Reported by Sander at https://mifosforge.jira.com/browse/MIFOSX-1498
> Original Description:
> When waiving interest on a loan the outstanding interest and balance is 
> reduced by clearing outstanding interest on past instalments and if 
> applicable future instalments (as expected). However when a payment is now 
> backdated to a date before the interest waiver, interest is that was waived 
> on those instalments is 'activated' again and the payment is allocated to it.
> In the attached screenshot #1 is the 'clean' schedule of the loan with 4.11 
> in interest due. The total due on the loan is 254.11. In the screenshot #2 
> the interest has been waived per the 1st of June, leaving a loan balance of 
> 235.32 (screenshot #3).
> Now when a new transaction is entered, for the 15th of May (so before 
> waiver), of 15$ , the expected loan balance would be 220.32, however the 
> payment 'reopens' the interest for the instalments it is covering (see 
> screenshot #4) and repays them. As a result the total outstanding is 220.48 
> (one instalment interest has been paid, but was not part of the balance 
> before). And also when the sum of all transactions is made manually it no 
> longer adds up (screenshot #5) to the system generated balances.
> Because of the way MifosX handles the loanschedules and transactions, the 
> waiver has automatically been reversed when processing the backdated payment 
> (which is chronologically before the later payment) and then applies the 
> waiver again later, at which point the interest due is fewer than the waiver 
> is for. This results in an adjustment of the overall loan, and also brings up 
> a situation whereby the loan summary data is no longer aligned with the 
> transactions. And the accounting data is also out of sync, as the accrued 
> interest no longer adds up to the waived + paid interest on the loan.
> As the waiving of interest normally is a process that can work both backwards 
> (open installments from before) and forwards (future installments), we would 
> expect that the interest for the prior installments would remain waived.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-278) The new deposit and withdraw buttons at the client detail screen are not affected when assigning user rules and permissions

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-278:
--
Labels: confirm p1  (was: fineract-gci)

> The new deposit and withdraw buttons at the client detail screen are not 
> affected when assigning user rules and permissions
> ---
>
> Key: FINERACT-278
> URL: https://issues.apache.org/jira/browse/FINERACT-278
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> Reported by Ronnie at https://mifosforge.jira.com/browse/MIFOSX-1477
> Original  Description:
> The new deposit and withdraw buttons at the client detail screen are not 
> affected when assigning user rules and permissions. there is no way of 
> blocking users from accessing these buttons and a user with deposit, 
> withdraw, loan payment, disbursement etc can access these restricted area 
> through these buttons.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-277:
--
Issue Type: Improvement  (was: Bug)

> 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
>  Labels: 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
(v6.3.4#6332)

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

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-277:
--
Labels: p3  (was: fineract-gci)

> 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
>  Labels: 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
(v6.3.4#6332)

[jira] [Updated] (FINERACT-276) Job scheduler timezones not handled correctly

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-276:
--
Labels: p1  (was: )

> Job scheduler timezones not handled correctly
> -
>
> Key: FINERACT-276
> URL: https://issues.apache.org/jira/browse/FINERACT-276
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>  Labels: p1
>
> Reported by Sander  at  https://mifosforge.jira.com/browse/MIFOSX-1269
> Original Description:
> When investigating some issues with the overdue loan portfolio we found out 
> that the current way the jobs are handled can cause differences in the 
> figures for tenants by not picking up the correct date.
> The server has the timezone set to UTC/GMT. When a cronjob is added with a 
> cron entry to run at 0:01 every day, the java scheduler converts this into 
> the timezone of the tenant (UTC+3 in this example). In this case this results 
> in the actual schedule to be kicked off at 21:01 the day before.
> When the job then triggers it on 21:01 on 01-06-2014 it uses the mysql 
> CURDATE() feature to decide on the current date, but this returns in UTC, 
> therefore reporting everything against 01-06-2014, instead of 02-06-2014 
> which was the expected (based on timezone UTC+3).
> In this case the arrears are updated incorrectly, but same applies to 
> prepayments and all other jobs that happen in the gap between UTC and the 
> tenant timezone.
> Workaround: Update the cronjob entry to run at 03:01 (UTC+3) by default, this 
> then gets converted into 0:01 (UTC) and therefore it uses 02-06-2014 as the 
> date.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-259) Repaid every setting can't be edited without restarting loan application

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-259:
--
Labels: confirm p3  (was: confirm)

> Repaid every setting can't be edited without restarting loan application
> 
>
> Key: FINERACT-259
> URL: https://issues.apache.org/jira/browse/FINERACT-259
> Project: Apache Fineract
>  Issue Type: Bug
> Environment: https://demo3.openmf.org
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: confirm, p3
> Attachments: Screen Shot 2016-11-22 at 9.08.28 AM.png
>
>
> When attempting to create a new loan account (an instance of a loan product), 
> when you modify the repaid every setting from monthly to weekly and then 
> switch back to weekly, it still retains monthly setting and can't be 
> submitted. 
> Steps to Reproduce
> 1. Navigate to Allen E Client
> 2. Add new Loan Account
> 3. Fill out parameters
> 4. Modify Repaid every by changing it from weeks to months and then specify 
> fourth Wednesday of the month.
> 5. Revert this change by switching repaid every back to 1 weeks
> 6. Click Submit
> Error message gets displayed saying frequency day of week type must be 
> provided when frequency nth day type is fourth.
> See attached screenshot.
> The loan form seems to think repaid monthly is still selected even though 
> it's repaid weekly. The only way to submit the loan would be to start over 
> the loan application from scratch. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-259) Repaid every setting can't be edited without restarting loan application

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-259:
--
Labels: confirm  (was: )

> Repaid every setting can't be edited without restarting loan application
> 
>
> Key: FINERACT-259
> URL: https://issues.apache.org/jira/browse/FINERACT-259
> Project: Apache Fineract
>  Issue Type: Bug
> Environment: https://demo3.openmf.org
>Reporter: Edward Cable
>Assignee: Markus Geiss
>  Labels: confirm, p3
> Attachments: Screen Shot 2016-11-22 at 9.08.28 AM.png
>
>
> When attempting to create a new loan account (an instance of a loan product), 
> when you modify the repaid every setting from monthly to weekly and then 
> switch back to weekly, it still retains monthly setting and can't be 
> submitted. 
> Steps to Reproduce
> 1. Navigate to Allen E Client
> 2. Add new Loan Account
> 3. Fill out parameters
> 4. Modify Repaid every by changing it from weeks to months and then specify 
> fourth Wednesday of the month.
> 5. Revert this change by switching repaid every back to 1 weeks
> 6. Click Submit
> Error message gets displayed saying frequency day of week type must be 
> provided when frequency nth day type is fourth.
> See attached screenshot.
> The loan form seems to think repaid monthly is still selected even though 
> it's repaid weekly. The only way to submit the loan would be to start over 
> the loan application from scratch. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-257) Scorecards never get returned

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-257:
--
Labels: confirm p2  (was: )

> Scorecards never get returned
> -
>
> Key: FINERACT-257
> URL: https://issues.apache.org/jira/browse/FINERACT-257
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Surveys
>Reporter: Markus Geiss
>Assignee: Markus Geiss
>  Labels: confirm, p2
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-257) Scorecards never get returned

[Edward Cable (JIRA)]

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

Edward Cable commented on FINERACT-257:
---

[~mgeiss] Did this get resolved with the recent work you did on surveys?

> Scorecards never get returned
> -
>
> Key: FINERACT-257
> URL: https://issues.apache.org/jira/browse/FINERACT-257
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Surveys
>Reporter: Markus Geiss
>Assignee: Markus Geiss
>  Labels: confirm, p2
>




--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-249) PortfolioProductType.SAVING and PortfolioProductType.CLIENT have the same value

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-249:
--
Labels: p1  (was: )

> PortfolioProductType.SAVING and PortfolioProductType.CLIENT have the same 
> value
> ---
>
> Key: FINERACT-249
> URL: https://issues.apache.org/jira/browse/FINERACT-249
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Emmanuel Nnaa
>Assignee: Markus Geiss
>  Labels: p1
>
> PortfolioProductType.SAVING and PortfolioProductType.CLIENT have the same 
> value.
> {code}
> LOAN(1, "productType.loan"), SAVING(2, "productType.saving"), CLIENT(2, 
> "productType.client"), PROVISIONING(3,
> "productType.provisioning"), SHARES(4, "productType.shares");
> {code}



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-244) New Repayment Schedule Not Populating

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-244:
--
Labels: p3  (was: )

> New Repayment Schedule Not Populating
> -
>
> Key: FINERACT-244
> URL: https://issues.apache.org/jira/browse/FINERACT-244
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: p3
>
> Mifos - View Loan Account - More Drop Down - Reschedule
> After complete Reschedule Loan Screen - Press Submit
> View Loan reschedule request - then select View new Repayment Schedule
> New Repayment Schedule Screen does not populate any information for 
> verification prior to accepting the change.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

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

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-242:
--
Priority: Minor  (was: Major)

> 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: 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
(v6.3.4#6332)

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

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-242:
--
Labels: p3  (was: )

> 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: 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
(v6.3.4#6332)

[jira] [Updated] (FINERACT-241) Include "Add Note" to Deposit and Withdrawal screen in savings account

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-241:
--
Labels: beginner p3  (was: )

> Include "Add Note" to Deposit and Withdrawal screen in savings account
> --
>
> Key: FINERACT-241
> URL: https://issues.apache.org/jira/browse/FINERACT-241
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: beginner, p3
>
> https://mifosforge.jira.com/browse/MIFOSX-2620
> Refer to MIFOSX for images
> Include "Add Note" to Deposit and Withdrawal screen in savings account so 
> that narration can be added especially name of the person who has deposited 
> which may not be necessarily the account holder. Its good for controls and 
> follow ups.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-241) Include "Add Note" to Deposit and Withdrawal screen in savings account

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-241:
--
Issue Type: Improvement  (was: Bug)

> Include "Add Note" to Deposit and Withdrawal screen in savings account
> --
>
> Key: FINERACT-241
> URL: https://issues.apache.org/jira/browse/FINERACT-241
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: beginner, p3
>
> https://mifosforge.jira.com/browse/MIFOSX-2620
> Refer to MIFOSX for images
> Include "Add Note" to Deposit and Withdrawal screen in savings account so 
> that narration can be added especially name of the person who has deposited 
> which may not be necessarily the account holder. Its good for controls and 
> follow ups.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-236) Savings product configuration changes should affect existing accounts

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-236:
--
Labels: p3 requirements  (was: )

> Savings product configuration changes should affect existing accounts
> -
>
> Key: FINERACT-236
> URL: https://issues.apache.org/jira/browse/FINERACT-236
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: p3, requirements
>
> https://mifosforge.jira.com/browse/MIFOSX-2510
> If an institution changes a configuration in either a particular loans or 
> savings product, this change should be applied to already existing accounts 
> created. 
> E.g if during savings product creation, MFI sets Min Balance as 5,000 and 
> after some time decided to change it 10,000 then i think this should not be 
> applied to new accounts created after this change but rather cut across any 
> other existing account. This should apply to loan product configurations.
> These are some of the ways this can be achieved:-
> # This product configuration account values like Min Balance, Interest rate 
> etc should not be stored in the account table but rather a pointer can be set 
> to them
> # When a change is made to a product configuration, in the respective 
> accounts table i.e loan account table or savings account table depending on 
> the product type being modified, changes must be updated accounting like if 
> interest rate or min balance value is change, query should be include when 
> submitting these changes to effect them in the account table, some time like
> select * from m_savings_account where product_id = (product id being 
> modified), then update the necessary values in the table
> This should be for :-
> * Savings Product
> * Recurring Deposit
> * Fixed Deposit
> * Charges



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-236) Savings product configuration changes should affect existing accounts

[Edward Cable (JIRA)]

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

Edward Cable updated FINERACT-236:
--
Issue Type: Improvement  (was: Bug)

> Savings product configuration changes should affect existing accounts
> -
>
> Key: FINERACT-236
> URL: https://issues.apache.org/jira/browse/FINERACT-236
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>
> https://mifosforge.jira.com/browse/MIFOSX-2510
> If an institution changes a configuration in either a particular loans or 
> savings product, this change should be applied to already existing accounts 
> created. 
> E.g if during savings product creation, MFI sets Min Balance as 5,000 and 
> after some time decided to change it 10,000 then i think this should not be 
> applied to new accounts created after this change but rather cut across any 
> other existing account. This should apply to loan product configurations.
> These are some of the ways this can be achieved:-
> # This product configuration account values like Min Balance, Interest rate 
> etc should not be stored in the account table but rather a pointer can be set 
> to them
> # When a change is made to a product configuration, in the respective 
> accounts table i.e loan account table or savings account table depending on 
> the product type being modified, changes must be updated accounting like if 
> interest rate or min balance value is change, query should be include when 
> submitting these changes to effect them in the account table, some time like
> select * from m_savings_account where product_id = (product id being 
> modified), then update the necessary values in the table
> This should be for :-
> * Savings Product
> * Recurring Deposit
> * Fixed Deposit
> * Charges



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-142) In loan "Account Detail" page the maturity date is displayed is not proper

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-142.
-
Resolution: Fixed
  Assignee: subramanyasn  (was: Markus Geiss)

Santosh tested on 16.12.01.RELEASE and working as expected. 

> In loan "Account Detail" page the maturity date is displayed is not proper
> --
>
> Key: FINERACT-142
> URL: https://issues.apache.org/jira/browse/FINERACT-142
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: subramanyasn
>Assignee: subramanyasn
>  Labels: confirm, p2
> Attachments: Maturity date.png
>
>
> 1. Create a loan product with interest recalculation enabled (Interest 
> calculation - daily and recalculation -daily). monthly repayment.
> 2. Submit new loan application for a client on 01 Jan 2015. Approve and 
> disburse loan on same date.
> 3. Click on the repayment schedule in which the new row with the  interest 
> accrued till current date is displayed.
> 4. Click on the Account detail page in which the loan maturity date is 
> displayed as today's system date.
> Expected:
> The loan maturity date should not get modified due to the new row created 
> with the interest accrued till current system date. It should be as per 
> original schedule.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Comment Edited] (FINERACT-380) S3 permission issue -- add system property

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain edited comment on FINERACT-380 at 1/18/17 12:37 PM:
-

Got the update from AWS and see the comments below

The current policy only allows actions on the bucket (like List), it does not 
allow actions on objects in the bucket. If this is required, you will need to 
update the IAM policy as follows:

{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::BUCKET_NAME",
"arn:aws:s3:::BUCKET_NAME/*"
],
"Effect": "Allow"
}
]
}
A similar example is shown here: 
http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_examples.html




was (Author: nazeer1100126):
Got the update from AWS and see the comments below

The current policy only allows actions on the bucket (like List), it does not 
allow actions on objects in the bucket. If this is required, you will need to 
update the IAM policy as follows:

{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::prd-prdbeta",
"arn:aws:s3:::prd-prdbeta/*"
],
"Effect": "Allow"
}
]
}
A similar example is shown here: 
http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_examples.html



> S3 permission issue -- add system property
> --
>
> Key: FINERACT-380
> URL: https://issues.apache.org/jira/browse/FINERACT-380
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: thynn win
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
>  Labels: p1
>
> Due to signature version 4 issue, I am unable to use S3 with Mifos.
> Amazon suggested we add a system property and could you please help us add 
> this in the next version?
> AWS Error Code: InvalidRequest, AWS Error Message: The authorization 
> mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-380) S3 permission issue -- add system property

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain commented on FINERACT-380:
---

Got the update from AWS and see the comments below

The current policy only allows actions on the bucket (like List), it does not 
allow actions on objects in the bucket. If this is required, you will need to 
update the IAM policy as follows:

{
"Version": "2012-10-17",
"Statement": [
{
"Action": [
"s3:*"
],
"Resource": [
"arn:aws:s3:::prd-prdbeta",
"arn:aws:s3:::prd-prdbeta/*"
],
"Effect": "Allow"
}
]
}
A similar example is shown here: 
http://docs.aws.amazon.com/IAM/latest/UserGuide/access_policies_examples.html



> S3 permission issue -- add system property
> --
>
> Key: FINERACT-380
> URL: https://issues.apache.org/jira/browse/FINERACT-380
> Project: Apache Fineract
>  Issue Type: Improvement
>Reporter: thynn win
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
>  Labels: p1
>
> Due to signature version 4 issue, I am unable to use S3 with Mifos.
> Amazon suggested we add a system property and could you please help us add 
> this in the next version?
> AWS Error Code: InvalidRequest, AWS Error Message: The authorization 
> mechanism you have provided is not supported. Please use AWS4-HMAC-SHA256.
> http://docs.aws.amazon.com/AmazonS3/latest/dev/UsingAWSSDK.html#specify-signature-version



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FINERACT-352) Penalties for last loan installment are not shown on summary

[Lionel Raymundi (JIRA)]

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

Lionel Raymundi resolved FINERACT-352.
--
Resolution: Fixed

> Penalties for last loan installment are not shown on summary
> 
>
> Key: FINERACT-352
> URL: https://issues.apache.org/jira/browse/FINERACT-352
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: Lionel Raymundi
>Assignee: Markus Geiss
>
> When penalties are configured for a loan, if the last installment is not paid 
> on term a new installment is created, where penalties should be applied. 
> It seems that the penalties are being correctly created, but on installment 
> summary they are not properly shown.
> There is an example of this on https://demo.openmf.org/#/viewloanaccount/399



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-137) Created parent GL account is not displaying properly in the dropdown while creating the GL Account

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-137.
-
Resolution: Fixed
  Assignee: subramanyasn  (was: Markus Geiss)

Santosh tested on 16.12.01.RELEASE and working as expected. 

> Created parent GL account is not displaying properly in the dropdown while 
> creating the GL Account
> --
>
> Key: FINERACT-137
> URL: https://issues.apache.org/jira/browse/FINERACT-137
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Accounting
>Reporter: subramanyasn
>Assignee: subramanyasn
>  Labels: confirm, p1
> Attachments: Create GL Account page.png
>
>
> 1. Create a GL account for Assets and Account usage as Header.
> 2. Create a GL account for Assets, account usage as Detail and parent as 
> created above.
> 3. It is allowing to create the GL account for assets with Account usage as 
> detail. 
> > If the Header is more than 12 in entities then it is not getting displayed 
> > in the drop down under Parent while creating the GL account.
> > The Header accounts created is getting displayed under Parent dropdown for 
> > all account types. it should get filtered according to the account types. 
> > Eg. If the account type is Equity only equity related header accounts 
> > should get displayed under parent.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-106) Not able to change week day in Center meeting with weekly meeting attached, displays Internal server error

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-106.
-
Resolution: Fixed
  Assignee: subramanyasn  (was: Markus Geiss)

Santosh tested on 16.12.01.RELEASE and working as expected. 

> Not able to change week day in Center meeting with weekly meeting attached, 
> displays Internal server error
> --
>
> Key: FINERACT-106
> URL: https://issues.apache.org/jira/browse/FINERACT-106
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: subramanyasn
>  Labels: confirm, p1
> Attachments: Edit Center meeting.png
>
>
> 1. Create a Center with weekly meeting attached from 01 March 2016 and every 
> week on Friday.
> 2. Click on edit meeting and change day in a week as Wednesday and click on 
> submit button.
> > Not able to save the page displays internal server error.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Re: [ANNOUNCE] Apache Fineract 0.6.0-incubating Release

[Myrle Krantz]

Hey Andy,

Fineract is made up of REST services.  The Mifos Initiative produces an
open source web app called "The Community App" which can serve as a front
end to Fineract.

Here's a youtube demo: https://www.youtube.com/watch?v=h61g9TptMBo (Demo
starts after the introduction at about 3:20).

If you'd like some information about where this is used in real life, one
company using Fineract in their financial inclusion products is Musoni.
They have some nice charts and use cases here:
https://musoni.co.ke/impact/

Conflux is another company using Fineract to produce a product they call
Finflux.

That's pretty introductory material; perhaps you had something more
specific in mind?

Greets,
Myrle



*Myrle Krantz*
Solutions Architect
RɅĐɅЯ, The Mifos Initiative
mkra...@mifos.org | Skype: mkrantz.mifos.org | http://mifos.org
  


On Tue, Jan 17, 2017 at 2:18 PM, Andy Wenk  wrote:

> Hey all,
>
> congrats for the new release ;-). I heard about Fineract the first time
> and had a look to the website and the wiki pages (just scanned a bit). It
> sounds interesting. I would love to read  more about real life usecases.
> Can anyone point me to some posts or info where I get an idea how to use
> this piece of software?
>
> Thanks a lot in advance!
>
> All the best
>
> Andy
>
> --
> Andy Wenk
> RockIt!
>
> Hamburg / Germany
>
> GPG public key: https://pgp.mit.edu/pks/lookup?op=get&search=
> 0x4F1D0C59BC90917D
>
> > On 17 Jan 2017, at 13:54, Nazeer Shaik  wrote:
> >
> > Hi all,
> >
> > The Apache Fineract team would like to announce the release of Apache
> Fineract 0.6.0-incubating with source and binary artifacts.
> >
> > Apache Fineract is an open source system for core banking as a platform.
> Fineract provides a reliable, robust, and affordable solution for
> entrepreneurs, financial institutions, and service providers to offer
> financial services to the world’s 2 billion under banked and unbanked.
> >
> > More details regarding Apache Fineract can be found at
> http://fineract.incubator.apache.org/
> >
> > The release artifacts can be downloaded here:
> > https://dist.apache.org/repos/dist/release/incubator/
> fineract/0.6.0-incubating/
> >
> > The release notes can be found here:
> > https://cwiki.apache.org/confluence/display/FINERACT/0.
> 6.0-incubating+Release-+Apache+Fineract
> >
> > Thanks!
> > The Apache Fineract Team
> > --- DISCLAIMER  Apache Fineract is an effort undergoing incubation at
> The Apache Software Foundation (ASF), sponsored by the Apache Incubator
> PMC. Incubation is required of all newly accepted projects until a further
> review indicates that the infrastructure, communications, and decision
> making process have stabilized in a manner consistent with other successful
> ASF projects. While incubation status is not necessarily a reflection of
> the completeness or stability of the code,it does indicate that the project
> has yet to be fully endorsed by the ASF.
> >
>
>

[jira] [Closed] (FINERACT-22) Adding Floating Interest Rate "Error" - cannot create floating rate

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-22.

Resolution: Fixed
  Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

Tested by Santosh and working as expected.

> Adding Floating Interest Rate "Error" - cannot create floating rate
> ---
>
> Key: FINERACT-22
> URL: https://issues.apache.org/jira/browse/FINERACT-22
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Dayna Harp
>Assignee: Shaik Nazeer Hussain
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2391 - see attachments
> When a user tries to add a new Floating rate, non-descript "Error" is 
> returned.
> 2nd MAJOR ISSUE: New Product cannot be created if Floating Rate not defined. 
> "Error
> The parameter `isLinkedToFloatingInterestRates` has been passed and is not 
> supported for this request." returned.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Closed] (FINERACT-21) Waive overdue charge is not working as expected

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain closed FINERACT-21.

Resolution: Fixed
  Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

Tested by Santosh and this issue is no more reproducible. 

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Shaik Nazeer Hussain
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-21) Waive overdue charge is not working as expected

[Santosh Math (JIRA)]

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

Santosh Math commented on FINERACT-21:
--

I tested it on 16.12.01.RELEASE and this  issue is resolved.

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Issue Comment Deleted] (FINERACT-21) Waive overdue charge is not working as expected

[Santosh Math (JIRA)]

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

Santosh Math updated FINERACT-21:
-
Comment: was deleted

(was: Considering the exact scenario, this issue is resolved. )

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-21) Waive overdue charge is not working as expected

[Santosh Math (JIRA)]

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

Santosh Math commented on FINERACT-21:
--

Considering the exact scenario, this issue is resolved. 

> Waive overdue charge is not working as expected
> ---
>
> Key: FINERACT-21
> URL: https://issues.apache.org/jira/browse/FINERACT-21
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Charges
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>  Labels: confirm, p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2392 - see attachments
> 1. Create overdue charge - 100 - Flat, Create a simple loan product and apply 
> the above created charge to it.
> 2. Submit new loan application for a client on 01 October 2015 approve and 
> disburse on same date.
> 3. Execute the scheduler job "Apply penalty for overdue loans",
> 4. Navigate back to the same loan account page and click on the charges and 
> waive charge on 01 November 2015.
> > Charge got waved, but in the repayment schedule wrong entries got created.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-221) After submitting the modify application the currency is not getting updated as per the new product

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain commented on FINERACT-221:
---

This issue is still open. 

> After submitting the modify application the currency is not getting updated 
> as per the new product
> --
>
> Key: FINERACT-221
> URL: https://issues.apache.org/jira/browse/FINERACT-221
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
>
> 1. Create 2 loan products, one with Indian rupees as currency and another 
> with US Dollar
> 2. Submit new loan application for a client with the loan prouduct1.
> 3. Click on modify application and modify to product2.
> 4. In the loan general page currency is not getting updated to US Dollar, 
> rather it is remaining as Indian Rupees only.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-221) After submitting the modify application the currency is not getting updated as per the new product

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain updated FINERACT-221:
--
Labels: p1  (was: confirm p1)

> After submitting the modify application the currency is not getting updated 
> as per the new product
> --
>
> Key: FINERACT-221
> URL: https://issues.apache.org/jira/browse/FINERACT-221
> Project: Apache Fineract
>  Issue Type: Bug
>Reporter: subramanyasn
>Assignee: Markus Geiss
>  Labels: p1
>
> 1. Create 2 loan products, one with Indian rupees as currency and another 
> with US Dollar
> 2. Submit new loan application for a client with the loan prouduct1.
> 3. Click on modify application and modify to product2.
> 4. In the loan general page currency is not getting updated to US Dollar, 
> rather it is remaining as Indian Rupees only.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Updated] (FINERACT-348) Issues when doing a "Close-As-Rescheduled" on a loan

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain updated FINERACT-348:
--
Issue Type: Improvement  (was: Bug)

> Issues when doing a "Close-As-Rescheduled" on a loan  
> -
>
> Key: FINERACT-348
> URL: https://issues.apache.org/jira/browse/FINERACT-348
> Project: Apache Fineract
>  Issue Type: Improvement
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: p1
>
> Reported by Binny at https://mifosforge.jira.com/browse/MIFOSX-1205
> Original Description:
> When closing a loan using the "Close (as Rescheduled)" button, the loan 
> account is closed, but there are no transactions or accounting entries made 
> for this closure. This not correct.
> The following should be done:
> 1) A new transaction should be visible to user under transactions to show 
> that the loan was closed as rescheduled rather than leaving the loan as is 
> without any changes. This means that Mifos X should mkae a new entry 
> m_loan_transaction table - with transaction_type_enum = 7 and amount as the 
> total outstanding amount (principal + interest + fees).
> 2) Ensure that the right accounting entries are made when closing the loan as 
> "closed (as rescheduled)". This involves:
> For loan products: capturing another General Ledger account head under 
> “Rescheduled in Suspense” – for example: “Rescheduled Loans Suspense Account”
> When closing as loan as rescheduled, passing the following entries:
> a) For Cash Accounting:
> Debit: Rescheduled Loan Suspense Account (with only principal outstanding 
> amount)
> Credit: Loan portfolio
> b) For Accrual (upfront):
> Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + 
> interest + fees + penalties)
> Credit: Loan portfolio (with principal outstanding amount)
> Credit: Interest Receivable (with interest outstanding amount)
> Credit: Fees Receivable (with fees outstanding amount)
> Credit: Penalties Receivable (with penalties outstanding amount)
> c) For Accrual (periodic):
> Debit: Rescheduled Loan Suspense Account (sum of outstanding principal + 
> interest receivable accounted + fees receivable accounted + penalties 
> receivable accounted)
> Credit: Loan portfolio (with principal outstanding amount)
> Credit: Interest Receivable (with interest receivable accounted)
> Credit: Fees Receivable (with fees receivable accounted)
> Credit: Penalties Receivable (with penalties receivable accounted)



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FINERACT-364) Submitting Collection Sheet through Maker Checker Throwing Error

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain resolved FINERACT-364.
---
Resolution: Fixed

With this PR https://github.com/apache/incubator-fineract/pull/276 issue will 
be resolved. 

> Submitting Collection Sheet through Maker Checker Throwing Error
> 
>
> Key: FINERACT-364
> URL: https://issues.apache.org/jira/browse/FINERACT-364
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Loan
>Reporter: Santosh Math
>Assignee: Shaik Nazeer Hussain
>Priority: Blocker
>  Labels: p1
> Attachments: 1.png, 2.png, Screen Shot 2017-01-09 at 9.40.16 AM.png
>
>
> 1. Enable Maker Checker in System>>Configuration.
> 2. Go to  System>>Configure Maker Checker Tasks and click on 'Edit', select 
> the center and check 'SAVECOLLECTIONSHEET CENTER'. (check attached screenshot)
> 3. Disburse JLG Loan to a client.
> 4. Go to collection sheet and fill the details and select the center name but 
> don't select the group name.
> 5. Click  on Submit button, which goes to Checker Inbox. 
> 6. When you try to approve it , it throws the error.
> "The parameter `loanTransactions` has been passed and is not supported for 
> this request.
> The parameter `SavingsTransactions` has been passed and is not supported for 
> this request."  
> Check the attached file/screenshots.
> The above same error is thrown when,
> > You select both center and group and submit collection sheet. 
> > We try to submit through 'productive collection sheet'.
> > We try to submit 'Individual Collection Sheet'. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Resolved] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain resolved FINERACT-16.
--
Resolution: Fixed

With this PR https://github.com/apache/incubator-fineract/pull/277 this issue 
will be closed

> Cannot close Savings Account when linked to a loan even when loan status is 
> closed
> --
>
> Key: FINERACT-16
> URL: https://issues.apache.org/jira/browse/FINERACT-16
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Dayna Harp
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
>  Labels: p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2293
> 1. Create and activate a client 
> 2. Create and activated a savings account for the client, deposit some amount 
> in the account
> 3. Link the above savings account to a new loan application and  Submit the 
> loan application, Don't approve, it close the loan.
> 4. Try to close the above savings account and check the Withdraw Balance
> _Error
> Closing savings account with id:11 is not allowed, since it is linked with 
> one of the active loans_
> The same error is got if even the loan account is paid all and closed.
> I think the cause is, when a loan account is closed, withdrawn, or rejected 
> the linked savings account remains linked.to the loan account hence this 
> error.
> This is very critical barrier



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Assigned] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain reassigned FINERACT-16:


Assignee: Shaik Nazeer Hussain  (was: Markus Geiss)

> Cannot close Savings Account when linked to a loan even when loan status is 
> closed
> --
>
> Key: FINERACT-16
> URL: https://issues.apache.org/jira/browse/FINERACT-16
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Dayna Harp
>Assignee: Shaik Nazeer Hussain
>Priority: Critical
>  Labels: p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2293
> 1. Create and activate a client 
> 2. Create and activated a savings account for the client, deposit some amount 
> in the account
> 3. Link the above savings account to a new loan application and  Submit the 
> loan application, Don't approve, it close the loan.
> 4. Try to close the above savings account and check the Withdraw Balance
> _Error
> Closing savings account with id:11 is not allowed, since it is linked with 
> one of the active loans_
> The same error is got if even the loan account is paid all and closed.
> I think the cause is, when a loan account is closed, withdrawn, or rejected 
> the linked savings account remains linked.to the loan account hence this 
> error.
> This is very critical barrier



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed

[ASF GitHub Bot (JIRA)]

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

ASF GitHub Bot commented on FINERACT-16:


GitHub user nazeer1100126 opened a pull request:

https://github.com/apache/incubator-fineract/pull/277

FINERACT-16-Cannot close Savings Account when linked to a loan even when 
loan status is closed



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/nazeer1100126/incubator-fineract FINERACT-16

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/incubator-fineract/pull/277.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #277






> Cannot close Savings Account when linked to a loan even when loan status is 
> closed
> --
>
> Key: FINERACT-16
> URL: https://issues.apache.org/jira/browse/FINERACT-16
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2293
> 1. Create and activate a client 
> 2. Create and activated a savings account for the client, deposit some amount 
> in the account
> 3. Link the above savings account to a new loan application and  Submit the 
> loan application, Don't approve, it close the loan.
> 4. Try to close the above savings account and check the Withdraw Balance
> _Error
> Closing savings account with id:11 is not allowed, since it is linked with 
> one of the active loans_
> The same error is got if even the loan account is paid all and closed.
> I think the cause is, when a loan account is closed, withdrawn, or rejected 
> the linked savings account remains linked.to the loan account hence this 
> error.
> This is very critical barrier



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

[jira] [Commented] (FINERACT-16) Cannot close Savings Account when linked to a loan even when loan status is closed

[Shaik Nazeer Hussain (JIRA)]

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

Shaik Nazeer Hussain commented on FINERACT-16:
--

Before approval, there is no option to close the loan. User has the option to 
delete the loan.
While deleting the loan, we are not deleting the existing accountAssociations. 
This is causing DataIntegrityVoilation.

> Cannot close Savings Account when linked to a loan even when loan status is 
> closed
> --
>
> Key: FINERACT-16
> URL: https://issues.apache.org/jira/browse/FINERACT-16
> Project: Apache Fineract
>  Issue Type: Bug
>  Components: Savings
>Reporter: Dayna Harp
>Assignee: Markus Geiss
>Priority: Critical
>  Labels: p1
>
> https://mifosforge.jira.com/browse/MIFOSX-2293
> 1. Create and activate a client 
> 2. Create and activated a savings account for the client, deposit some amount 
> in the account
> 3. Link the above savings account to a new loan application and  Submit the 
> loan application, Don't approve, it close the loan.
> 4. Try to close the above savings account and check the Withdraw Balance
> _Error
> Closing savings account with id:11 is not allowed, since it is linked with 
> one of the active loans_
> The same error is got if even the loan account is paid all and closed.
> I think the cause is, when a loan account is closed, withdrawn, or rejected 
> the linked savings account remains linked.to the loan account hence this 
> error.
> This is very critical barrier



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)